insmod: unresolved symbol
hi!
has anyone ever tried compiling and running snull on Linux2.4.18-sh?
i tried compiling snull(without any modification) on Linux2.4.18-sh.
upon running snull_load, i got the following:
Using /lib/modules/2.4.18-sh/kernel/drivers/net/snull.
insmod: unresolved symbol kmalloc_R93d4cfe6
insmod: unresolved symbol skb_under_panic_R69955398
insmod: unresolved symbol register_netdev_R09e03f58
insmod: unresolved symbol eth_type_trans_R0a4e7a1c
insmod: unresolved symbol unregister_netdev_R98eda3f8
insmod: unresolved symbol printk_Rdd132261
insmod: unresolved symbol __udivsi3_i4
insmod: unresolved symbol memcpy_R11f7ce5e
insmod: unresolved symbol jiffies_R0da02d67
insmod: unresolved symbol alloc_skb_R0177038c
insmod: unresolved symbol softnet_data_R258cb892
insmod: unresolved symbol cpu_raise_softirq_R4d09166c
insmod: unresolved symbol __kfree_skb_R1741771d
insmod: unresolved symbol memset_R2bc95bd4
insmod: unresolved symbol kfree_R037a0cba
insmod: unresolved symbol netif_rx_R8316ccd0
insmod: unresolved symbol ether_setup_R586ea93a
insmod: unresolved symbol skb_over_panic_R4bb59969
can someone please tell me what's wrong with this, and how to fix this without chaning Linux versions?
thank you for you help in advance :-)
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 1 line · Donald Duckie
hi!
hello donie
Quoted 27 lines
has anyone ever tried compiling and running snull on Linux2.4.18-sh?
i tried compiling snull(without any modification) on Linux2.4.18-sh.
upon runningsnull_load, i got the following:
Using/lib/modules/2.4.18-sh/kernel/drivers/net/snull.
insmod: unresolved symbolkmalloc_R93d4cfe6
insmod: unresolved symbolskb_under_panic_R69955398
insmod: unresolved symbolregister_netdev_R09e03f58
insmod: unresolved symboleth_type_trans_R0a4e7a1c
insmod: unresolved symbolunregister_netdev_R98eda3f8
insmod: unresolved symbolprintk_Rdd132261
insmod: unresolved symbol__udivsi3_i4
insmod: unresolved symbolmemcpy_R11f7ce5e
insmod: unresolved symboljiffies_R0da02d67
insmod: unresolved symbolalloc_skb_R0177038c
insmod: unresolved symbolsoftnet_data_R258cb892
insmod: unresolved symbolcpu_raise_softirq_R4d09166c
insmod: unresolved symbol__kfree_skb_R1741771d
insmod: unresolved symbolmemset_R2bc95bd4
insmod: unresolved symbolkfree_R037a0cba
insmod: unresolved symbolnetif_rx_R8316ccd0
insmod: unresolved symbolether_setup_R586ea93a
insmod: unresolved symbolskb_over_panic_R4bb59969
Quoted 2 lines
can someone please tell me what's wrong with this, and how to fix this without chaning Linux versions?
remove CONFIG_MODVERSIONS of your kernel is in my opinion a good idea...
are you using the original Makefile ?
your compilation line must look like that...
gcc -D MODVERSIONS -include /usr/src/linux/include/linux/modversion.h...
if it is already the case... i suggest you to verify that "modversion.h" is compliant with your running kernel...
you can take a look on the chapter 11 of "Device Driver 2nd edition" it is just talking about that...
simon
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
hi simon & chuck!
thank you very much for the information that you have sent.
i have some confirmation though, because the information confuses me: removing the CONFIG_MODVERSIONS might not change anything. well, i tried it, but the result was indeed still the same.
anyway, here was what was done:
i compiled the snull source file on 2.4.18-sh which i got from
http://www.oreilly.com.tw/editor_column/a138_read.html.
it was mentioned in that site that snull was compiled with 2.4.24.
anyway, compilation with 2.4.18-sh was successful, but upon running insmod on 2.4.18-sh, i got those unresolved errors.
any help/information are very much welcome.
and with depmod (since i am cross-compiling):
i also tried running "depmod
-a" prior to compilation, but depmod wrote into /lib/modules/2.4.24, instead of /lib/modules/2.4.18-sh. both directories exists. do i really need to run depmod? how will i made it update the /lib/modules/2.4.18-sh directory instead of the /lib/modules/2.4.24 directory?
again, thanks for the help guys . ..
Quoted 55 lines · --- simon
Quoted 1 line · Donald Duckie
hi!
hello donie
Quoted 2 lines
has anyone ever tried compiling and running snull
on
Quoted 3 lines
Linux2.4.18-sh?
i tried compiling snull(without any modification)
on
Quoted 3 lines
Linux2.4.18-sh.
upon runningsnull_load, i got the following:
Using
/lib/modules/2.4.18-sh/kernel/drivers/net/snull.Quoted 2 lines
insmod: unresolved symbol
kmalloc_R93d4cfe6
insmod: unresolved symbol
skb_under_panic_R69955398Quoted 1 line
insmod: unresolved symbol
register_netdev_R09e03f58Quoted 2 lines
insmod: unresolved symbol
eth_type_trans_R0a4e7a1c
insmod: unresolved symbol
unregister_netdev_R98eda3f8Quoted 7 lines
insmod: unresolved symbol
printk_Rdd132261
insmod: unresolved symbol__udivsi3_i4
insmod: unresolved symbolmemcpy_R11f7ce5e
insmod: unresolved symboljiffies_R0da02d67
insmod: unresolved symbolalloc_skb_R0177038c
insmod: unresolved symbolsoftnet_data_R258cb892
insmod: unresolved symbol
cpu_raise_softirq_R4d09166cQuoted 9 lines
insmod: unresolved symbol
__kfree_skb_R1741771d
insmod: unresolved symbolmemset_R2bc95bd4
insmod: unresolved symbolkfree_R037a0cba
insmod: unresolved symbolnetif_rx_R8316ccd0
insmod: unresolved symbolether_setup_R586ea93a
insmod: unresolved symbolskb_over_panic_R4bb59969can someone please tell me what's wrong with this, and how to fix this without chaning Linux
versions?
removeCONFIG_MODVERSIONSof your kernel is in my
opinion a good idea...are you using the original
Makefile?your compilation line must look like that...
gcc -D MODVERSIONS -include/usr/src/linux/include/linux/modversion.h...if it is already the case... i suggest you to verify that "
modversion.h"
is compliant with your running kernel...
Quoted 6 lines
you can take a look on the chapter 11 of "Device
Driver 2nd edition"
it is just talking about that...simon
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 17 lines · Donald Duckie
hi simon & chuck!
thank you very much for the information that you have sent.
i have some confirmation though, because the information confuses me: removing the
CONFIG_MODVERSIONSmight not change anything. well, i tried it, but the result was indeed still the same.anyway, here was what was done:
i compiled the snull source file on 2.4.18-sh which i got from
http://www.oreilly.com.tw/editor_column/a138_read.html.
it was mentioned in that site that snull was compiled with 2.4.24.
Quoted 8 lines
anyway, compilation with 2.4.18-sh was successful, but upon running insmod on 2.4.18-sh, i got those unresolved errors.
any help/information are very much welcome.
and with depmod (since i am cross-compiling):
Meaning.???
Quoted 5 lines
i also tried running "depmod
-a" prior to compilation, but depmod wrote into/lib/modules/2.4.24, instead of/lib/modules/2.4.18-sh. both directories exists. do i really need to run depmod?
If you had taken the trouble to have answered the few questions i asked you in my reply on the other thread, you could have gotten an answer here strait away from me, however you choose not to so you still have problems. depmod with the -a option will write modules.dep to the directory which matches the results of the command, 'uname -r', so seeing that depmod wrote to 2.4.18 we can presume you are getting mixed up with 2.4.18-sh and 2.4.18, as i said in a previous mail, the directroy containg the linux source code (which is linked to "linux" with a symlink) is simply a name, the name of the resulting kernel is taken from the topdir Makefile lines 1,2,3 and 4, 4 is optional.
Quoted 3 lines
how will i made it
update the/lib/modules/2.4.18-shdirectory instead of the/lib/modules/2.4.24directory?
I think its time you answered the questions i and others have asked, then and only then could one get to the bottom of the problem you are having. I am convinced its got nothing to do with kernel 2.4.18 (see my comments in other mails).
Quoted 1 line
again, thanks for the help guys . ..
Signature · 14 lines
If the Linux community is a bunch of theives because they try to imitate windows programs, then the Windows community is built on organized crime. Regards Richard [email protected] http://people.zeelandnet.nl/pa3gcu/ - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 28 lines · Donald Duckie
hi!
has anyone ever tried compiling and running snull on Linux2.4.18-sh?
i tried compiling snull(without any modification) on Linux2.4.18-sh.
upon runningsnull_load, i got the following:
Using/lib/modules/2.4.18-sh/kernel/drivers/net/snull.
insmod: unresolved symbolkmalloc_R93d4cfe6
insmod: unresolved symbolskb_under_panic_R69955398
insmod: unresolved symbolregister_netdev_R09e03f58
insmod: unresolved symboleth_type_trans_R0a4e7a1c
insmod: unresolved symbolunregister_netdev_R98eda3f8
insmod: unresolved symbolprintk_Rdd132261
insmod: unresolved symbol__udivsi3_i4
insmod: unresolved symbolmemcpy_R11f7ce5e
insmod: unresolved symboljiffies_R0da02d67
insmod: unresolved symbolalloc_skb_R0177038c
insmod: unresolved symbolsoftnet_data_R258cb892
insmod: unresolved symbolcpu_raise_softirq_R4d09166c
insmod: unresolved symbol__kfree_skb_R1741771d
insmod: unresolved symbolmemset_R2bc95bd4
insmod: unresolved symbolkfree_R037a0cba
insmod: unresolved symbolnetif_rx_R8316ccd0
insmod: unresolved symbolether_setup_R586ea93a
insmod: unresolved symbolskb_over_panic_R4bb59969
Quoted 5 lines
can someone please tell me what's wrong with this, and how to fix this without chaning Linux versions?
thank you for you help in advance :-)
Did you run 'depmod -a' ?
HTH, Chuck
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs