I noticed the same problem, fortunately before reboot, so I ran lilo manually.
My /etc/kernel-img.conf has do_bootloader = yes.
I compared postints scripts for kernel 2.6.18 and 2.6.24 and the important
thing is at line 38:
my $loader = "lilo"; # lilo, silo, quik, palo, vmelilo, nettrom, etc.
In 2.6.18 there is hardcoded default for lilo, while in 2.6.24 there is no
default at all:
my $loader = ""; # lilo, silo, quik, palo, vmelilo, nettrom, etc.
When I filled in lilo and run dpkg-reconfigure for 2.6.24 kernel it did run
lilo as expected.
Please fix the postinst script.
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com