[Buildroot] Unable to boot via initrd

[Bart J. Smit]

Hi Arnout,

That fixed it and it no longer needs the external compression of the root filesystem. These steps did the trick:

make menuconfig
Filesystem images --->
Only select 'initramfs for initial ramdisk of linux kernel'

This sets it to gzipped cpio automagically.

Bedankt!

Bart...

-----Original Message-----
From: Arnout Vandecappelle [mailto:arnout at mind.be] 
Sent: 10 July 2012 23:30
To: Bart J. Smit
Cc: 'buildroot at busybox.net'
Subject: Re: [Buildroot] Unable to boot via initrd

On 07/10/12 23:24, Bart J. Smit wrote:
> Another buildroot newbie looking at this. I'm looking to create a PXE boot for generic x86.
>
> I've created the initial ramdisk with:
>   mount -o loop rootfs.ext2 ../initrd
>   cd ../initrd
>   find . | cpio -o -H newc | gzip>  ../initrd.img

  An easier way to create the initrd is to choose the CPIO image from the buildroot menuconfig.

> When I PXE boot the client, it gets to:
>    VFS Cannot open root device, please append a correct root= boot option; here are the available partitions
>    Kernel panic - not syncing: VFS; Unable to mount root fs on 
> unknown-block(2,0)

  Does the kernel have support for gzipped initramfs?  Do you give a root= option on the kernel command line?  (Shouldn't be necessary, since your initramfs is the final root filesystem.)


  Regards,
  Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F