From: Jeff McWilliams <Jeff.McWilliams@acetechnologies.net>
To: linux-kernel@vger.kernel.org
Cc: Jeff.McWilliams@acetechnologies.net
Subject: 2.4.3-pre8: unresolved symbols loading net modules
Date: Tue, 27 Mar 2001 09:16:02 -0500 [thread overview]
Message-ID: <3AC0A0A2.7080706@acetechnologies.net> (raw)
I recently built a 2.4.3-pre8 Kernel, because 2.4.2 couldn't properly
configure the AMI MegaRaid 428 card on the box. (The MegaRaid card
works fine under 2.2.13 and 2.4.3-pre8 on the same system).
When attempting to 'modprobe -v pcnet32' on 2.4.3-pre8 I get the
following results:
homer:/home/jjmcwill# modprobe -v pcnet32
/sbin/insmod /lib/modules/2.4.3-pre8/kernel/drivers/net/pcnet32.o
/lib/modules/2.4.3-pre8/kernel/drivers/net/pcnet32.o: unresolved symbol
init_etherdev
/lib/modules/2.4.3-pre8/kernel/drivers/net/pcnet32.o: unresolved symbol
ether_setup
/lib/modules/2.4.3-pre8/kernel/drivers/net/pcnet32.o: unresolved symbol
unregister_netdev
/lib/modules/2.4.3-pre8/kernel/drivers/net/pcnet32.o: insmod
/lib/modules/2.4.3-pre8/kernel/drivers/net/pcnet32.o failed
/lib/modules/2.4.3-pre8/kernel/drivers/net/pcnet32.o: insmod pcnet32 failed
The same thing happens with other ethernet drivers compiled as modules.
Ethernet card drivers compiled into the Kernel work fine.
Other modules such as lp, sg, st, vfat, modprobe without error.
The kernel was built on a Debian stable (potato) distribution and
installed on this box which also runs Debian stable. I've built
numerous kernels like this before without incident, so I'm assuming it's
a Kernel compile/configuration issue. However, Debian stable uses
modutils 2.3.11, while linux/Documentation/Changes recommends modutils
2.4.2. Could this be part of the problem?
Any ideas?
Please cc replies to Jeff.McWilliams@acetechnologies.net if possible.
I browse the Kernel archives daily but dont' subscribe to the list.
Thanks,
Jeff McWilliams
Jeff.McWilliams@acetechnologies.net
reply other threads:[~2001-03-27 14:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3AC0A0A2.7080706@acetechnologies.net \
--to=jeff.mcwilliams@acetechnologies.net \
--cc=linux-kernel@vger.kernel.org \
/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