Updating lilo conf
It's exactly the same that this old bug report: #360011 "large-memory" was already in the regards -- Xavier [email protected] a standard security/stability upgrade of lenny I witnessed the same problem as Xavier, namely that lilo would stop with: lilo Loading Linux EBDA is big; kernel setup stack overlaps LILO second stage (I am not sure whether there were any points after "lilo". Removing package linux-image-2.6.18-6-686 The link /is a damaged link Removing symbolic link Unless you used the optional flag in lilo, you may need to re-run your boot loader[lilo] The link /ol is a damaged link Removing symbolic link ol Unless you used the optional flag in lilo, you may need to re-run your boot loader[lilo] Removing configuration directory of package linux-image-2.6.18-6-686 ... Now everything was fine and I could boot into the new 2.6.26 kernel without lilo complaining.
I think not, but if there were, then there were only very few - i.e. Configuring package linux-image-2.6.26-2-686 (2.6.26-21) ... Running lilo from the command line would show me the bootable kernels: # lilo Added 2618-6-hda5 Added 2626-hda5 Added windows # ls -l / [...] - boot/vmlinuz-2.6.26-2-686 It seems that even if is half broken - i.e.
The fact that the user was able to boot his old de-installed kernel is proof of this.
The /boot/map file still pointed to the blocks in the file system which formerly contained the old kernel and its initial RAM file system image.
See also, for example, linux-image-2.6.26-2-s390.postinst, where zipl is assigned as the bootloader on line 38. This appears to be a problem in lenny, where by default neither the kernel postinst nor the initramfs builder runs lilo. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. do_bootloader = yes in /etc/means "run the historic boot loader for this platform".
Simply install the script in /etc/kernel/preinst.d, /etc/kernel/prerm.d, /etc/kernel/postinst.d, or /etc/kernel/postrm.d.Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-10 Severity: critical I've did an upgrade on 2008-11-09, on a new installed system, upgrading kernel 2.6.26-09 to 22.214.171.124. I've seen nothing strange during upgrade and in the apt and dpkg logs. When reboting I obtain this message from Lilo: "Loading Linux EBDA is big; kernel setup stack overlaps LILO second stage". -- Kras the Klingon, "Friday's Child", stardate 3497.2 problem? ) 2.6.18-6 kernel and allthough the bootprocess complained about a lot of missing kernel modules (or ?