Re: LiloCan't Boot vmlinuz-2.6.26-1-amd64

["Thomas H. George" <lists@tomgeorge.info>]

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