Re: [IPCop-devel] 1.4.0a10 possiable bugs

On Sat, 2004-01-31 at 20:55, Alan Hourihane wrote:
> On Sat, Jan 31, 2004 at 08:46:14PM +1030, Brendan Borlase wrote:
> > On Sat, 2004-01-31 at 20:07, Alan Hourihane wrote:
> > > On Sat, Jan 31, 2004 at 07:22:28PM +1030, Brendan Borlase wrote:
> > > > On Sat, 2004-01-31 at 19:05, Brendan Borlase wrote:
> > > > > PCMCIA is borked as well.. try as I might, i can't work out the right
> > > > > steps to get a pcmcia card working..
> > > > 
> > > > hah! I have it - load master Alan H's dummy driver, AFTER fireing up
> > > > modprobe in a second session with required drivers...
> > > 
> > > No, you shouldn't have to load the dummy driver.
> > 
> > Yes, I know that.. I _should_ be able to autoprobe & have IPCOP do all
> > the work and load everything. Failing that, I _should_ be able to
> > manually choose the PCMCIA card, and everything will work fine.. It's
> > not, and this is the first release with PCMCIA more or less complete.. I
> > don't expect it to work out of the box..
>  
> It does work out of the box as I've tried it with some PCMCIA cards.
> You can't manually choose a PCMCIA card either, it will auto-load it 
> regardless. Only Cardbus is allowable to manually select.
> 

Indeed.

> > > I have checked that PCMCIA works, but haven't tried a Cardbus card yet
> > > due to lack of equipment. But I can and will today, and report back here.
> > 
> > Define "PCMCIA works".. neither a cardbus, nor normal PCMCIA card were
> > detected correctly.. I don't think that exactly qualifies as working, if
> > are going to get picky! :P
>  
> Maybe they weren't detected on your machine, but it is on mine. And if
> you provide the debug output we'll be able to find out why it's not
> on yours. I can always not bother to help either, so stop getting shitty.

Alan, I'm not getting shitty, just making a point. We're not all skilled
programmers.. so we don't all know where to look.. I'm a System Admin by
trade. Your tone of "voice" simply sounded tired and annoyed with yet
annoying IPCOP user.. I apologise. 

> > > Please obtain information from VT2 to say what's happening and post the
> > > results here.

Will try to do that.. it's running now, however it's not yet being used,
will reboot, get you the specific errors I see in VT2 (sorry, it makes
perfect sense now.. see my comment below, re silly questions, as it
happens I was using VT3 for the manual firing of modprobe -- chalk it up
to a blond moment? ;-)

-- snip --
> > 
> > While I haven't been directly writing PCMCIA support for this, I am
> > getting pretty familiar with _how_ ipcop handles the inital setup
> > routine, so I can at least see what IPCOP is _trying_ to do, and
> > sidestep it, till I can work out WHAT that particular step was that
> > IPCOP couldn't handle..  
> 
> Feel free to contribute code.

Your going to start getting a moderate number of people identify stuff
going south with PCMCIA.. I'm certain some will be fine, others won't.

I'm not a programmer, I'm just a Joe Schmoe who happens to like IPCOP..

I'll endeavour to get the details on the exact SOCSxxxxx related errors
for you. As I have suggested, the yenta_socket modprobe dosn't appear to
have been fired correctly prior to the initial green configuration. I
suspect that were it fine (like your laptop identifying and loading
correctly) we'd not even be having this convo.

You'll probably end up with several "debug" snippets..

I'll try with straight auto-probe (and publish the errors) then I'll try
firing up modprobe yenta_socket (which should make PCMCIA at least act
like it would, were IPCOP detecting it right).. this'll give you the
'oops busy' debug messages I suspect..

I'm very sorry about sounding shitty, but I have read more than one
thread, where some of the IPCOP community have gone spastic at someone
for asking, granted what appears on the surface to be a silly question,
but to the person asking, it wasn't, yet they still get a rough deal..

-- 
regards,

Brendan Borlase

> yanis at ihug dot com dot au