From: simon <simon.guinot@laposte.net>
To: Donald Duckie <schipperke2000@yahoo.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: insmod: unresolved symbol
Date: Thu, 16 Sep 2004 03:11:53 +0200 [thread overview]
Message-ID: <4148E859.70303@laposte.net> (raw)
In-Reply-To: <20040916001442.45760.qmail@web53605.mail.yahoo.com>
Donald Duckie wrote:
> hi!
hello donie
>
> 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?
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 majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-09-16 1:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 0:14 insmod: unresolved symbol Donald Duckie
2004-09-16 1:11 ` simon [this message]
2004-09-16 5:36 ` Donald Duckie
2004-09-16 12:28 ` Richard Adams
2004-09-16 2:16 ` chuck gelm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4148E859.70303@laposte.net \
--to=simon.guinot@laposte.net \
--cc=linux-newbie@vger.kernel.org \
--cc=schipperke2000@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox