Re: Trying to run 2.6.0-test3

Norman Diamond
2003-08-18T10:55:08Z

"Russell King" <rmk@arm.linux.org.uk> replied to me:

> > 2.6.0-test3 gets it wrong:
> > Aug 17 16:39:01 diamondpana cardmgr[540]: socket 1: KME KXLC005 CD-ROM
> > Aug 17 16:39:01 diamondpana cardmgr[540]: executing: 'modprobe -v ide_cs'
> > Aug 17 16:39:02 diamondpana cardmgr[540]: + insmod /lib/modules/2.6.0-test3/kernel/drivers/ide/legacy/ide-cs.ko
> > Aug 17 16:39:02 diamondpana cardmgr[540]: bind 'ide_cs' to socket 1 failed: Invalid argument
>
> Not quite. This is an old problem dating back several years to early 2.4
> times. Back in the dark old days, ide-cs used to use the name "ide_cs" to
> bind the driver to the device. It now uses "ide-cs" for binding.

Yes the problem is reminiscent of early 2.4 days, but how is it that 2.4.19
doesn't have the problem and 2.6.0-test3 does have the problem on the same
machine?

> Make sure that "ide_cs" isn't mentioned in /etc/pcmcia/config - if it
> is, change it to "ide-cs".

I will hope to have time to check this next weekend, but I'm sure the 2.4
name ide-cs is used. I was startled to see 2.6.0-test3 load a module named
ide_cs instead of ide-cs, but there it was. It was listed that way by
lsmod, but failing in the bind as shown above. Notice that modprobe used
the same name as lsmod showed.