Red Hat Bugzilla – Bug 72202
Incorrect /etc/lilo.conf after install
Last modified: 2007-04-18 12:45:47 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809
Description of problem:
lilo.conf (and installed lilo boot info) missing linux entry
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install null on a 7.3 system
Actual Results: I selected to update the bootloader (which is lilo) during
installation. It created a new lilo.conf that contained only a single entry -
for booting my windows partition (which was present in the old lilo.conf file).
There was no entry for either the old or new linux kernels. lilo was used to
write the config - hence I could not boot into linux on initial restart after
install. Luckily I opted to created a boot disk. The boot disk correctly
identified the linux boot partition.
Also, a minor note - I also has a couple other commented out entries in
lilo.conf for previously tried kernels. The comments were not carried over into
the new lilo.conf.
Thankfully, the install saved the lilo.conf to a .rpmsave file.
Expected Results: Should have been an appropriate entry in the lilo.conf.
Could you attach your old lilo.conf?
Created attachment 72106 [details]
The pre-installation lilo.conf (that the install renamed to lilo.conf.rpmsave)
Did /boot/vmlinuz-2.4.17 and /boot/initrd-2.4.17.img actually exist? Also, do
you still have the lilo.conf that was written out by the install?
Yes, /boot/vmlinuz-2.4.17[.img] were existing (that is the kernel that was in
use before the install). Sorry, I don't have the lilo.conf written by the
install. From memory, it was the header parts followed by the windows entry -
that's it. No comments in the file either.
Fixed in mkinitrd-3.4.27-1
Verified fixed in latest code.