Hi there, maximilian attems wrote:
> On Tue, Sep 16, 2008 at 02:40:39AM -0700, Edward Buck wrote: >> >> After installing the security update for >> linux-image-2.6.24-etchnhalf.1-686 dated Sept. 11, 2008, the system >> failed to boot the updated kernel. I use Lilo on this particular >> machine and on reboot, the system froze on the 'Loading Linux...' >> line. >> >> I had previously updated other systems with the same kernel >> successfully, so I focused on the differences between those systems >> and this one. Since Lilo (instead of grub) was an obvious one, I >> manually ran the 'lilo' command to see if that would fix things. >> Sure enough, it did. > > fix your /etc/kernel-img.conf to have do_bootloader = yes set As far as I can tell, there's nothing wrong with my /etc/kernel-img.conf. $ cat /etc/kernel-img.conf # Do not create symbolic links in / Do_Symlinks = Yes The default for do_bootloader is YES according to the man page for kernel-img.conf. > woody had no preinstalled linux images yet, so please read release > notes on upgrading from such old boxes. thanks It has been years since this machine was upgraded from woody. It has also been years since it was upgraded from sarge (to etch). I'm pretty sure I read the release notes (as I usually do) when doing those upgrades. Something seemingly changed in the most recent kernel to cause this bug. I don't recall ever having to run lilo manually before. IIRC, there's usually a prompt to run the boot loader at the end of the kernel installation, which did not appear. Thanks for your help. Regards, Ed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
