Red Hat Bugzilla – Bug 50691
Incorrect operation following upgrade to kernel-2.4.3-12
Last modified: 2007-03-26 23:47:35 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Description of problem:
During upgrade of kernel
Error: /removal of /lib/modules/2.4.2-2/modules.usbmap failed: No such
file or directory
( error repeated for modules.pcimap, modules.parportmap,
modules.isapnpmap, and modules.generic_string )
Steps to Reproduce:
1. Install RH7.1
2.install new kernel ( kernel-2.4.3-12 ) ( rpm -v -F kernel-2.12.3-
Actual Results: On reboot get a number of error, including no networking.
Bootup errors include:
modprobe:Can't open dependencies file /lib/modules/2.4.2-2/modules.dep (
no such file or directory ).
depmod: Can't opens /lib/modules/2.4.2-2/modules.dep .......
At login prompt on console, kernel still reported as 2.4.2-2
Also rpm -qa | grep kernel, also still reports 2.4.2-12
Expected Results: No errors during upgrade
Reboot work fine ( as before )
I was installing several of the security advisory and bug fix rpms at the
same time ( ie I did rpm -v -F *.rpm ).
The order they installed was
( several other gcc ones )
error: removal of /lib/modules .... ( as listed above )
1) kernel's shouldn't be "rpm -U'd" but installed first, so that you can always
2) You most likely forgot to rerun lilo so lilo tried to boot the old kernel!
for more information on how to upgrade kernels.
Error messages still exist when installing rpm, but errors on subsequent reboot
due to forgetfulness on my part !! ( lilo -v !!!! - remembered to change
lilo.conf, forgot about outputting it to boot sector !! ).
Can't lilo.conf be updated from rpm ( even lilo -v run ), or is it not done
because want administrator to check everything OK from install before
committing it ??
Have downgraded priority and severity !!
I've fixed the modules.usbmap errormessage for the next build. Thanks for the
report on that one.
We don't run lilo for several reasons, the most important one being that people
just don't expect it as a side-effect of rpm -i (it also sucks if you're running
the up2date tool will do lilo, but is VERY VERY careful about it, and will only
ADD new kernels, and will not remove old ones.