Am So, den 07.03.2004 schrieb Peter Boy um 13:21:
> After updating to kernel 2.4.22-1.2174.nptl and (unfortunately) update
> to the current version of madwifi CVS I get the following error messages
> when I try to load the modules:
>
> [root@little madwifi]# insmod wlan/wlan.o
> wlan/wlan.o: unresolved symbol eth_type_trans
> wlan/wlan.o: unresolved symbol __kfree_skb
> wlan/wlan.o: unresolved symbol alloc_skb
> wlan/wlan.o: unresolved symbol skb_under_panic
> wlan/wlan.o: unresolved symbol create_proc_entry
> wlan/wlan.o: unresolved symbol unregister_netdev
> wlan/wlan.o: unresolved symbol skb_copy
> wlan/wlan.o: unresolved symbol proc_mkdir
> wlan/wlan.o: unresolved symbol register_netdev
> wlan/wlan.o: unresolved symbol dev_queue_xmit
> wlan/wlan.o: unresolved symbol ___pskb_trim
> wlan/wlan.o: unresolved symbol remove_proc_entry
> wlan/wlan.o: unresolved symbol netif_rx
> wlan/wlan.o: unresolved symbol skb_over_panic
> wlan/wlan.o: unresolved symbol proc_net
> wlan/wlan.o: unresolved symbol irq_stat
> wlan/wlan.o: unresolved symbol skb_copy_expand
>
> Did anybody get the same messages or does someone has madwifi
> operational using the current kernel?
>
>
> Thanks
> Peter
Do not use insmod! Use modprobe to give the process the change to
preload other needed kernel modules using the dependency list in
modules.dep. This will prevent such failures if all is proper set up.
Remind that you need to rebuild modules.dep after adding custom kernel
modules to the modules tree, use "depmod -ae -F /boot/System.map". If
already that call produces unresolved symbol error messages something
went wrong with building the custom module(s).
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2174.nptl
Sirendipity 18:32:30 up 16 days, 20:06, load average: 1.10, 1.23, 1.19
[ ÎÎÏÎÎ Ï'ÎÏÏÎÎ - gnothi seauton ]
my life is a planetarium - and you are the stars
