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:

image=/vmlinuz
label = Linux
read-only

vmlinuz points to /boot/vmlinuz-2.4.18.

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

image=/vmlinuz.old
label = LinuxOLD
read-only

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?

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.

# lilo -t -v

gives the output:

MAX_IMAGES = 27
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.

could you post your entire
/etc/lilo.conf
file and the contents of
/
to see kernels