Re: [IPCop-devel] 1.4.0a10 possiable bugs

[Brendan B. <ya...@ih...>]

On Sat, 2004-01-31 at 21:32, Alan Hourihane wrote:

--snip --
> It's also worth switching to VT3 (press ALT+F3) and then do
> 
> cat /proc/kmsg
> 
> to look at what the kernel is doing.
--snip--

System: 	IBM 760XL
Proc:		Pentium 166
Mem:		86

Okay, when I /cat/kmsg while running modprobe, it rolls through all the
pcmcia drivers and seems to skip 'em all, although it gets a strike on
xircom_cb.

Any debug info I can get to write to the hdd's /tmp directory I'll
attach at end of email to give you something to go through..

Dumped /proc/modules & /proc/kmsg to files ok..

I'm going to try to modprobe yenta_socket (to reflect what should have
happened at boot time) to see if that allows the auto-probe to work.

Ok, still no joy. Erm, I just finished loading everything for pcmcia
short of psnet_cs, and it's just done an autoprobe fine!

Weird!

I know that my laptop dosn't support cardbus too well, it works fine
with cardbus, just not all O/S's support it.

I'll attach the output logs I managed to get for review..

Sorry I can't be any more helpfull! Though, unless the log files point
to something else, the PCMCIA sockets being identified, just not insmod
/ modprobe'd initially is going to make the rest fail.

Soon as the yenta_socket is loaded, and pcmcia_core load, it seems to be
able to make sense of what's plugged in...

-- 
regards,

Brendan Borlase

> yanis at ihug dot com dot au