On Mon, 2007-03-19 at 13:57 +0100, maximilian attems wrote: > On Mon, Mar 19, 2007 at 01:09:38PM +0100, Svante Signell wrote: > > I have also run lilo manually several times, e.g lilo -v shows: ... > > # Specifies the boot device. This is where Lilo installs its boot > > # block. It can be either a partition, or the raw device, in which > > # case it installs in the MBR, and will overwrite the current MBR. > > # > > boot=/dev/hda1 > > shouldn't boot be /dev/hda?
This setup has worked for years now! I don't want to try changing without having a boot CD available. It is also a hassle to rewrite LILO from a booted CD. I don't think this is the problem, all other kernels from 2.2 onwards have booted properly on this box. I did a reinstall of the kernel and initrd.img changed size, but still no successful boot :( -rw------- 1 root root 1204645 2007-02-27 23:12 initrd.img-2.6.18-4-686 -rw------- 1 root root 1221818 2007-03-19 19:33 initrd.img-2.6.18-4-686 #> apt-get install --reinstall linux-image-2.6.16-4-686 ... Unpacking replacement linux-image-2.6.18-4-686 ... Setting up linux-image-2.6.18-4-686 (2.6.18.dfsg.1-11) ... Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-4-686/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-4-686/source Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. Not updating initrd symbolic links since we are being updated/reinstalled (2.6.18.dfsg.1-11 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.18.dfsg.1-11 was configured last, according to dpkg) You already have a LILO configuration in /etc/lilo.conf Running boot loader as requested Testing lilo.conf ... Testing successful. Installing the partition boot sector... Running /sbin/lilo ... Installation successful. #> dpkg -S /usr/sbin/mkinitrd.yaird yaird: /usr/sbin/mkinitrd.yaird #> dpkg -l yaird ii yaird 0.0.12-18 Yet Another mkInitRD #>dpkg -l module-init-tools ii module-init-to 3.3-pre4-2 tools for managing Linux kernel modules > maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]