From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Unable to boot via initrd
Date: Wed, 11 Jul 2012 00:30:19 +0200 [thread overview]
Message-ID: <4FFCACFB.4030601@mind.be> (raw)
In-Reply-To: <07221C471CA1C044B6D10EC0D483C95708D30B6D@hercules.clumpton.homeip.net>
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
next prev parent reply other threads:[~2012-07-10 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 21:24 [Buildroot] Unable to boot via initrd Bart J. Smit
2012-07-10 22:30 ` Arnout Vandecappelle [this message]
2012-07-11 13:54 ` Bart J. Smit
-- strict thread matches above, loose matches on Subject: below --
2013-09-02 19:06 Matthieu
2013-09-03 16:11 ` Arnout Vandecappelle
2013-09-03 22:41 ` Matthieu
2013-09-04 7:50 ` Thomas Petazzoni
2013-09-04 11:38 ` Matthieu
2013-09-04 11:53 ` Matthieu
2012-01-11 9:02 Paul Kuntke
2012-01-11 14:04 ` Michael S. Zick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FFCACFB.4030601@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox