-   Debian (
-   -   No new kernel-option in LILO after editing lilo.conf (

corwax 08-23-2003 12:10 PM

No new kernel-option in LILO after editing lilo.conf
Some days ago I installed Debian 3.0 with kernel 2.2.20. I've just compiled a 2.4.18-kernel using the kernel-compile package. The problem is that LILO won't give me an option for booting the new kernel. I've checked lilo.conf, and things seem to be OK:

label = Linux

vmlinuz points to /boot/vmlinuz-2.4.18.

Still, the old 2.2.20-kernel boots. I've tried adding this to lilo.conf:

label = LinuxOLD

This makes no change. The only options at boot-time still are Linux and Dos. And yes; I remembered to run 'lilo' after editing the config file.

It seems that LILO doesn't react to the changes made in lilo.conf. What could be the problem?

ppuru 08-23-2003 12:47 PM

If you run lilo with the flags

# lilo -t -v

lilo will not commit any changes and will show you what exactly it is going to do.

corwax 08-23-2003 01:33 PM

# lilo -t -v

gives the output:

Warning: LBA32 addressing assumed
Warning: COMPACT may conflict with LBA32 on some systems
Reading boot sector from /dev/hda3
Merging with /boot/boot.b
Boot image: /vmlinuz -> boot/vmlinuz-2.4.18
Added Linux *

I can't see something unusual here.

penguin_warrior 08-26-2003 09:55 PM

could you post your entire
file and the contents of
to see kernels

All times are GMT -5. The time now is 05:54 AM.