Re: LiloCan't Boot vmlinuz-2.6.26-1-amd64
Andrei Popescu wrote: On Sun,31.Aug.08, 15:12:14, Thomas H. George wrote: [...] The attached listing of initrd.img file sizes shows only a slight increase from kernel to kernel. Tom Script started on Sun 31 Aug 2008 11:20:06 AM EDT Phoenix:/var/state# ls -l /boot/initrd.* -rw--- 1 root root 7657200 2008-08-29 09:36 [00m/boot/initrd.img-2.6.24-1-amd64 -rw--- 1 root root 7804926 2008-08-29 09:36 [00m/boot/initrd.img-2.6.25-2-amd64 -rw--- 1 root root 7872304 2008-08-29 09:37 [00m/boot/initrd.img-2.6.26-1-amd64 Script done on Sun 31 Aug 2008 11:20:47 AM EDT Yes, but the bug has been triggered by even smaller images. Did you try my suggestion with MODULES=dep? Regards, Andrei Yes with the same result. The new initrd.img is much smaller, 5067418. This image was created with the command update-initramfs -c -k 2.6.26-1-amd64. I first tried the command mkinitrd -o initrd.img-2.6.26-1-amd64 vmlinuz-2.6.26-1-amd64 which failed with a message cp: cannot stat '(0x0007fff853fe000)' : No such file or directory. I tried unsuccessfully to determine what was to be copied with strace. Then, using the man pages I learned update-initramfs with -c will create a new initrd.img with the result given above. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LiloCan't Boot vmlinuz-2.6.26-1-amd64
On Fri,29.Aug.08, 21:24:21, Thomas H. George wrote: Indeed the problem appears to be with kernels as kernel panic occurs after a message that no ramdisk is found at 0. During the dist-upgrade mkinitrd is automatically run for each of the three kernel images mentioned above. When the system is booted with any of the three kernel images the initial installation of the kernel completes with no difficulty. It is after this that the newer kernels cannot find the ram disk. The vmlinuz-2.6.24-1-amd64 kernel does not have this problem and completes the boot up successfully. There is a bug in lilo that prevents it to load too big initrds. Please show the output of 'ls -la /boot' to check for this. If this is the case you can only try to make a smaller initrd. Setting MODULES=dep in /etc/initramfs-tools/initramfs.conf might help. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: LiloCan't Boot vmlinuz-2.6.26-1-amd64
Andrei Popescu wrote: On Fri,29.Aug.08, 21:24:21, Thomas H. George wrote: Indeed the problem appears to be with kernels as kernel panic occurs after a message that no ramdisk is found at 0. During the dist-upgrade mkinitrd is automatically run for each of the three kernel images mentioned above. When the system is booted with any of the three kernel images the initial installation of the kernel completes with no difficulty. It is after this that the newer kernels cannot find the ram disk. The vmlinuz-2.6.24-1-amd64 kernel does not have this problem and completes the boot up successfully. There is a bug in lilo that prevents it to load too big initrds. Please show the output of 'ls -la /boot' to check for this. If this is the case you can only try to make a smaller initrd. Setting MODULES=dep in /etc/initramfs-tools/initramfs.conf might help. Regards, Andrei The attached listing of initrd.img file sizes shows only a slight increase from kernel to kernel. Tom Script started on Sun 31 Aug 2008 11:20:06 AM EDT Phoenix:/var/state# ls -l /boot/initrd.* -rw--- 1 root root 7657200 2008-08-29 09:36 [00m/boot/initrd.img-2.6.24-1-amd64 -rw--- 1 root root 7804926 2008-08-29 09:36 [00m/boot/initrd.img-2.6.25-2-amd64 -rw--- 1 root root 7872304 2008-08-29 09:37 [00m/boot/initrd.img-2.6.26-1-amd64 Script done on Sun 31 Aug 2008 11:20:47 AM EDT
Re: LiloCan't Boot vmlinuz-2.6.26-1-amd64
On Sun,31.Aug.08, 15:12:14, Thomas H. George wrote: [...] The attached listing of initrd.img file sizes shows only a slight increase from kernel to kernel. Tom Script started on Sun 31 Aug 2008 11:20:06 AM EDT Phoenix:/var/state# ls -l /boot/initrd.* -rw--- 1 root root 7657200 2008-08-29 09:36 [00m/boot/initrd.img-2.6.24-1-amd64 -rw--- 1 root root 7804926 2008-08-29 09:36 [00m/boot/initrd.img-2.6.25-2-amd64 -rw--- 1 root root 7872304 2008-08-29 09:37 [00m/boot/initrd.img-2.6.26-1-amd64 Script done on Sun 31 Aug 2008 11:20:47 AM EDT Yes, but the bug has been triggered by even smaller images. Did you try my suggestion with MODULES=dep? Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
re: LiloCan't Boot vmlinuz-2.6.26-1-amd64
Replying from Mutt has failed - damn nuisance - so I have patched together the messages and reposted from iceape. The new problem is not Mutt but something related to Postfix. I'll try to track it down tomorrow. Tom On 08/29/2008 02:03 PM, Thomas H. George wrote: dist-upgrade installed vmlinuz-2.6.26-1-amd64, ran mkinitrd and lilo which reported two warnings (mbr on different harddrive, assuming LBA32 addressing) but no fatal problems. Attempted boot to new kernel ended in kernel panic. I confess the same was true of vmlinuz-2.6.25-2-amd64 so I saveed vmlinuz-2.6.24-1-amd64 which lilo can boot with no problems. I had hoped the problem would go away with the next kernel image upgrade but it hasn't. Perhaps switching to grub would resolve this problem? If need be I will try to switch but as I have been happy with lilo until now it would be nice to be sure this will resolve the problem. Tom Make sure you've specified the initrd correctly. I never gotten an initrd (initial root disk) to work with LILO; however, you may succeed since LILO claims to support this. Perhaps you need to post your lilo.conf so others can help you. Indeed the problem appears to be with kernels as kernel panic occurs after a message that no ramdisk is found at 0. During the dist-upgrade mkinitrd is automatically run for each of the three kernel images mentioned above. When the system is booted with any of the three kernel images the initial installation of the kernel completes with no difficulty. It is after this that the newer kernels cannot find the ram disk. The vmlinuz-2.6.24-1-amd64 kernel does not have this problem and completes the boot up successfully. Tom
