Oops! I didn't notice your secondary update until after I had replied. In your secondary update you state that the large-memory option is present in your /etc/lilo.conf file. This is further evidence that this is a duplicate of bug number 505609. lilo did *not* get run after the kernel update and before the reboot. The error message
Initial ramdisk loads below 4Mb; kernel overwrite is possible. indicates that lilo loaded the initial RAM file system *below* the 15M line. It would not have done that if the large-memory option had been present in /etc/lilo.conf at the time that lilo's map installer was last run. If it had been, it would have loaded the initial RAM file system above the 16M line and the above error message would not have been issued. Exactly when did you add the large-memory option to your /etc/lilo.conf? Did you add it *before* the kernel-upgrade or *after*? If it was present *before* the kernel upgrade, then this is proof that lilo did not get run during the kernel upgrade. If it was added *after* the kernel upgrade, we still don't know for sure. But if you go back to your original initial RAM file system and manually run lilo, and everything works, then we can be sure that this is a duplicate of 505609. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
