Red Hat Bugzilla – Bug 76216
New kernels always search for old modules
Last modified: 2014-03-16 22:31:49 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830
Description of problem:
After installing a new kernel (from 2.4.18-14custom shipped with RH8 to
Kernel.org kernels), at the first reboot the kernel loader searches always for
the old kernel modules shipped with the RH 8 kernel. Moreover, the symbolic link
System.map pointing to System.map-MYKERNEL changes at the first reboot in
System.map-2.4.18-14 (the original RH 8.0 installation).
This causes hangups (on my system, always at reboot and poweroff).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Compile a kernel (in menuconfig it's horrible to see)
2. Install the kernel, making symbolic links so System.map and vmlinuz
4. Look at the output
5. Try to reboot or poweroff
1. Failed to load come 2.4.18-14 (RH original installation) modules,
even if you didn't want them
2. System.map-YOURKERNEL changes to System.map-2.4.18-14 (RH original
3. Hangups, crashes.
Load the kernel and modules which you specified, from your kernel version, not
the redhat one.
Possibility to use other kernels different from the one shipped with the
My system is:
512 Mb DDR
ATA-100 41 Gb HDD
LG CDR/RW Burner 16-10-40
LG CD/DVD-ROM Reader
Abit Siluro GeForce2 MX GPU
Are you sure that your kernel was compiled correctly? Did you install all the
modules from it?
Yes, make clean, dep, bzImage, modules, modules_install worked properly. I tried
to install the kernel.org 2.4.19: no warnings, no errors... At the first reboot
it showed me some errors about loading modules for 2.4.18-14 (HID, USB keyboard,
USB mouse) which I did not compile in this kernel.
If it is trying to load modules out of the 2.4.18-14 directory
a) you miscompiled your kernel somehow (did you run make mrproper, or just make
b) you somehow booted a different kernel.
a) No, no miscompilation. I just ran make clean. Make mrproper is not so
different from clean (am I right?).
b) No, I'm not a newbie! ;)
No, you need to run make mrproper; the kernel-source package ships with symbols
by default for compiling modules against the shipped kernel. Failure to run make
mrproper can run into miscompiled modules.
I had this happen to me, too.
The problem is that the kernel-source package ships with a prebuilt version.h
file for a uname w/o the 'custom' extraversion.
If failing to run |make mrproper| before compilation results in miscompiled
modules, and the kernel-source package's job is basically for recompiling the
kernel, why isn't this done before packaging?
The same problem appears compiling an official kernel. I tried to boot with
2.4.18 and 2.4.19, but the kernel module loader always searches for 2.4.18-14.
Now I installed from the RH network the kernel 2.4.18-17.8.0-athlon and it works
fine. But why I can't boot from a self-compiled kernel... who knows... ;)
The reason that module symbols are included is for compiling external modules
against the running kernel.
firstname.lastname@example.org: the problem you have, since it also appears with kernels you
compile from upstream sources, it *sounds* like you have bootloader
configuration issues, and you're actually rebooting the old kernel. For example,
if you're running lilo, you need to add the proper stanza and re-run lilo, etc.
AFAICT, this does not represent any initscripts problem.