[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [pcmcia-problem] kernel-image-2.4.20-bf2.4 -5



Eduard Bloch <edi@gmx.de> wrote:

> We have a problem: something is broken with the modules in the
> pcmcia-modules or with cardmgr. I think about reporting a grave bug
> against pcmcia-cs because of this:

The source of your problems is that there are two sets of modules named
orinoco.o and hermes.o.  Check under /lib/modules/2.4.20...  You'll find
that one resides under pcmcia, the other kernel/drivers/net/wireless.
Unfortunately, modprobe is loading the wrong set of modules.

Observe:

> Mar 11 02:00:50 debian cardmgr[2632]: socket 1: Intersil PRISM2 11 Mbps ...
> Mar 11 02:00:50 debian cardmgr[2632]: executing: 'modprobe hermes'
> Mar 11 02:00:51 debian kernel: hermes.c: 5 Apr 2002 David Gibson ...
> Mar 11 02:00:51 debian cardmgr[2632]: executing: 'modprobe orinoco'
> Mar 11 02:00:51 debian kernel: orinoco.c 0.11b (David Gibson ...
> Mar 11 02:00:51 debian cardmgr[2632]: executing: 'modprobe orinoco_cs'
> Mar 11 02:00:51 debian kernel: orinoco_cs.c 0.11b (David Gibson ...

    Same version numbers (0.11b = 0.11b): Success

> Mar 11 22:27:22 debian cardmgr[381]: socket 1: Intersil PRISM2 11 Mbps ...
> Mar 11 22:27:22 debian cardmgr[381]: executing: 'modprobe hermes'
> Mar 11 22:27:22 debian kernel: hermes.c: 4 Dec 2002 David Gibson ...
> Mar 11 22:27:23 debian cardmgr[381]: executing: 'modprobe orinoco'
> Mar 11 22:27:23 debian kernel: orinoco.c 0.13b (David Gibson ...
> Mar 11 22:27:23 debian cardmgr[381]: executing: 'modprobe orinoco_cs'

    Different version numbers (0.13b != 0.11b): Failure

The orinoco_cs module is version 0.11b, whereas the orinoco module is
version 0.13b.  Obviously, the kernel orinoco driver is being loaded
instead of the driver from pcmcia-cs.

The 2.4.20 kernel source (in the kernel-source package) has version
0.11b (I think that 2.4.18 also has this version), which is why this
problem doesn't appear more frequently.  What patches did you apply to
this kernel?  Where did the newer driver come from?

One way to fix this would be to use insmod to explicitly load the
correct drivers, or to delete the orinoco and hermes drivers under the
kernel subdirectory and run depmod.  The real problem is that there
should not be two modules with the same name.

- Brian



Reply to: