From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test7 with recent modutils vs. module symbols
Date: Mon, 13 Oct 2003 14:03:59 +0900 [thread overview]
Message-ID: <316f01c39147$8f4a1b90$5cee4ca5@DIAMONDLX60> (raw)
On a Red Hat 7.3 system with old modutils, I installed modutils-2.4.21-18
from an RPM. The new modutils work fine under kernels 2.6.0-test1 through
test7 as well as kernel 2.4.18.
On a SuSE 8.1 system with old modutils, I had trouble installing the new
modutils from an RPM, and then had trouble building it by hand. The result
could do modprobe and rmmod and lsmod, but a boot time error said that
module symbols were unavailable because modules weren't enabled. Booting
kernel 2.4.19 yielded no such error.
On a SuSE 8.2 system with modutils-2.4.22-33, fortunately something stopped
me just in time from downgrading to modutils-2.4.21-18. The distro's
modutils-2.4.22-33 can do modprobe and rmmod and lsmod, but the same boot
time error says that module symbols are unavailable because modules aren't
enabled. Booting kernel 2.4.20 yields no such error.
What is it about the combination of 2.6.0-test[1-7] and SuSE that has this
error, while other combinations do not?
Here is part of /var/log/messages:
Oct 12 21:09:23 diamondpana kernel: Inspecting /boot/System.map-2.6.0-test7
Oct 12 21:09:25 diamondpana kernel: Loaded 25702 symbols from
/boot/System.map-2.6.0-test7.
Oct 12 21:09:25 diamondpana kernel: Symbols match kernel version 2.6.0.
Oct 12 21:09:25 diamondpana kernel: No module symbols loaded - kernel
modules not enabled.
reply other threads:[~2003-10-13 5:05 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='316f01c39147$8f4a1b90$5cee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--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
all inboxes | Powered by JetHome®