On Mon, May 12, 2008 at 12:49 AM, maximilian attems <[EMAIL PROTECTED]> wrote:

> [ don't remove bug report from cc, this is *not* private communication
>  kthxbye ]
>
> On Sun, 11 May 2008, Angelo Puglisi wrote:
>
> > On Sun, May 11, 2008 at 12:09 PM, maximilian attems <[EMAIL PROTECTED]> 
> > wrote:
> >
> > I created againg initrd.img-2.6.24-1-amd64 with initramfs-tools and it
> seems
> > better, but it still don't work.
>
> how about if you'd report the failure of it?!
>
> > I attacched new diff file.
> > I did:
> > sh -x mkinitramfs -k -o /tmp/foo 2.6.24-1-amd64 &> /tmp/mkinitramfs.log
> >
> > and attacched the log.
>
> just looks fine and pretty sure that this initramfs contrare to your
> report is *not* 1mb big.
>
> send in:
> ls -l /boot
>
>
> --
> maks
>


The old initramfs was created by yaird and is the little one.
The new initramfs was created by initramfs-tools but it still don't work.
Waiting for root filesystem is the failure of last initramfs. The failure of
yaird made initramfs is lots of lines of:
/sys/block/hda/dev: No such file or directory
and after that a kernel panic.
It's obvious that I do not have logs because of the disk is not found.

Here the output of ls -l /boot as you asked:
-rw-r--r-- 1 root root   64816 24 apr 05:53 config-2.6.18-6-amd64
-rw-r--r-- 1 root root   79389 19 apr 01:13 config-2.6.24-1-amd64
drwxr-xr-x 2 root root    4096 11 mag 21:31 grub
-rw-r--r-- 1 root root 7068495 11 mag 11:04 initrd.img-2.6.18-6-amd64
-rw-r--r-- 1 root root 7491631 11 mag 15:19 initrd.img-2.6.24-1-amd64
-rw-r--r-- 1 root root  974070 24 apr 07:50 System.map-2.6.18-6-amd64
-rw-r--r-- 1 root root 1158727 19 apr 01:13 System.map-2.6.24-1-amd64
-rw-r--r-- 1 root root 1512415 24 apr 07:50 vmlinuz-2.6.18-6-amd64
-rw-r--r-- 1 root root 1668120 19 apr 01:12 vmlinuz-2.6.24-1-amd64

Reply via email to