> What am I doing wrong?
> The files /vmlinuz and /vmlinuz.old are symbolic links to
> /boot/vmlinuz-2.4.18-k7 and /boot/vmlinuz-2.2.20-idepci, respectively,
> so according to lilo.conf, the default kernel should be 2.4.18,
> but instead my machine boots to 2.2.20-idepci.
> What am I doing wrong?
> Here are some more details. The file /initrd.img is a symbolic
> link to /boot/initrd.img-2.4.18-k7. The full contents of /boot
> $ ls -F /boot
> System.map-2.2.20-idepci boot.0300 map
> boot-bmp.b chain.b vmlinuz-2.2.20-idepci
> boot-compat.b config-2.2.20-idepci vmlinuz-2.4.18-k7
> boot-menu.b config-2.4.18-k7
> boot-text.b initrd.img-2.4.18-k7
ls -F /boot/
boot.0200 boot-text.b map System.map-2.4.20tbls
So I would say either you need to create the proper symlinks or
configure lilo.conf to use something more in line with the
following. This is from a redhat system and may cause problems if
you cut and paste into your lilo.conf file.
!!! YOU HAVE BEEN WARNED !!!
Confucius: He who play in root, eventually kill tree.
Registered with the Linux Counter. http://counter.li.org
>Did you run lilo -v after modifying the lilo.conf ?
LILO only reads 'lilo.conf' at INSTALL time, never at BOOT time.
/sbin/lilo is the boot installer. (boot.b, or similar, is the actual boot
loader). The function of the boot installer is to create /boot/map, the
sector map of kernel sectors to load (& initrd & other=...).
>>What am I doing wrong?
> Did you run lilo -v after modifying the lilo.conf ?
(stuck using my Windows 98se until AT&T gets my cable modem back up)
...10 days and counting...
I wonder if anyone knows what's going on. I've upgraded my kernel to a
newer one, and I went to change my /etc/lilo.conf file to get it to boot
into it correctly. So far so good, the online documentation was fine.
So now I had Windows, the older kernel and the newer kernel as options. So
far so good.
Then I decided to delete the older kernel. I deleted any of the files that
had anything related to the older kernel from /boot. I then changed
lilo.conf to remove the entry for the older kernel aswell.
I restart my computer and I get the exact same boot options - Windows,
Older kernel and new kernel.
After a bit of digging, I found there was a different file called
/etc/lilo.conf~ which had my old settings to boot. So this file was
probably the one it was using to choose my boot options. Why is that?
Also, it's weird because this old lilo.conf~ file which has the old kernel
still as an option runs fine.
When I select "linux" from Lilo, it boots into Linux fine, even there is no
"/boot/vmlinuz-2.4.2-1", (not even a hidden file of that name).
Here's a copy of linux.conf~ file in all its entirity:
(the linux.conf file is the same, just without the /boot/vmlinuz-2.4.2-2
Any help appreciated,