I think you'll find that in Debian at the moment, "grub" is a better bootloader if you want things to just work when you install new kernel images. Try installing grub and see if that helps.
If you want to keep using lilo, and want help to fix it, please post your lilo.conf and the output of: ls / ls /boot to me or the list. If you don't understand exactly how lilo.conf works, you probably shouldn't use lilo; use grub. > 1. On a previous install of new image I used mkinitrd and it allowed > sarge to boot up but everything was broke except terminals. The > mkinitrd never completed without error and called up the option menu. I > have read the man mkinitrd and it seems definitely revelent but how to > use it not clear. You shouldn't have to run mkinitrd unless you build your own kernel, the kernel-image packages already include the appropriate initrd.img files. > 2. Ran fsck without unmounting and maybe that was a mistake. Made lots > of changes saying bad inodes and such. I don't really think anything > was wrong with the file system but fsck did. aargh! doesn't fsck warn you not to run it on a mounted filesystem? that was certainly a mistake. don't know how much significant damage it would have done, but I doubt it's the cause of your lilo problem. > 3. The last of the output from `apt-get install` was a warning about > installing a lilo block if you had another operating system installed. > I answered no several times, without helping, and then said yes to see > if it might fix things. It didn't. do you have another OS installed? if you've been able to boot it from lilo in the past, upgrading the kernel won't change that. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
