Hi,
I am using kernel 2.2.18 and pcmcia-cs-3.1.25. I installed the drivers of the Teletronics wl24 2mbit card drivers. But this gives errors. What is the meaning of this error
"unresolved symbol dev_kfree_skb_any"

What is the problem with the card.
This is what the logs show.

Jun 13 23:48:00 linux cardmgr[415]: starting, version is 3.1.25
Jun 13 23:48:00 linux cardmgr[415]: watching 2 sockets
Jun 13 23:48:00 linux cardmgr[415]: initializing socket 0
Jun 13 23:48:00 linux cardmgr[415]: socket 0: Teletronics WL2400 2Mbit Wireless LAN
Jun 13 23:48:01 linux cardmgr[415]: executing: 'modprobe wl24_cs'
Jun 13 23:48:01 linux cardmgr[415]: + /lib/modules/2.2.18/pcmcia/wl24_cs.o: unresolved symbol dev_kfree_skb_any
Jun 13 23:48:01 linux cardmgr[415]: + ds: Device or resource busy
Jun 13 23:48:01 linux cardmgr[415]: modprobe exited with status 1
Jun 13 23:48:01 linux cardmgr[415]: executing: 'insmod /lib/modules/2.2.18/pcmcia/wl24_cs.o'
Jun 13 23:48:01 linux cardmgr[415]: + /lib/modules/2.2.18/pcmcia/wl24_cs.o: unresolved symbol dev_kfree_skb_any
Jun 13 23:48:01 linux cardmgr[415]: insmod exited with status 1
Jun 13 23:48:02 linux cardmgr[415]: get dev info on socket 0 failed: Resource temporarily unavailable
Jun 13 23:48:00 linux rc: Starting pcmcia succeeded

regards
RKris

this is usually due to building the driver on the wrong kernel source. the current kernel is 2.2.18 then the kernel source tree in /usr/src/linux should be the same kernel.

if you did not build it then you may need to.

It's already pointing to the 2.2.18 kernel source
.The /usr/src/linux points to /usr/src/linux/linux-2.2.18. Its a symbolic link.

regards
RKris

sorry I mean
./usr/src/linux-2.2.18

regards
RKris

Another thing to note is that linus insists that you should always use the source tree that your libs were built on for programs. It seems that most people have disregarded that recomendation and continue to upgrade their kernel source tree. It seems to be a problem because modules need to use the current kernel where programs may need to us the same source that the libs are built on. This suggests to me that you should rebuild the libs when you do a kernel upgrade, or have the old source tree that you would link to when building apps and the new one for kernel modules.

What I have done on some of my systems is to build in the kernel support for the hardware so there are no modules, and keep the old source tree.

There is a possibility that something is causing a conflict. Some hardware may be supported by the kernel where if the hardware you have is similar it may try to use the driver for it. This would actually require removing the support from the kernel. The only such problem I have seen so far is with my new motherboard which has a raid controller which would not work correctly because it was identified as something else.

Hi,
Thanks I am now trying with the 2.4.3 kernel with pcmcia 3.1.25. I am compiling this on a RedHat6.2 machine.

regards
RKris