From: Matthieu <matthieu.personnaz@wanadoo.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Unable to boot via initrd
Date: Mon, 2 Sep 2013 12:06:42 -0700 (PDT) [thread overview]
Message-ID: <1378148801760-50517.post@n4.nabble.com> (raw)
Hello,
I have just installed the 2013-08 version of buildroot and I do not succed
to boot via initrd.
I tried two solutions (described in the previous post "Creating initrd")
through the gui menuconfig. And neither solution seems succeed.
When I run:
1) for the solultion 1 (BR2_TARGET_ROOTFS_INITRAMFS=y)
kvm -kernel output/images/bzImage -initrd output/images/rootfs.cpio.bz2 -m
128
2) for the solution 2: (BR2_TARGET_ROOTFS_CPIO=y)
kvm -kernel output/images/bzImage -initrd output/images/rootfs.cpio.bz2
-initrd output/images/rootfs.cpio.bz2 -m 128
I always obtain:
VFS: Cannot open root device "(null)" .... error -6 ...
Please append a coorect "root)" boot option; here are the available
partitions: Kernel panic ....VFS: Unable to mount root fs on
unknown-block(0,0)
Please can you help me?
regards
Matthieu
--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Unable-to-boot-via-initrd-tp50517.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next reply other threads:[~2013-09-02 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 19:06 Matthieu [this message]
2013-09-03 16:11 ` [Buildroot] Unable to boot via initrd 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
-- strict thread matches above, loose matches on Subject: below --
2012-07-10 21:24 Bart J. Smit
2012-07-10 22:30 ` Arnout Vandecappelle
2012-07-11 13:54 ` Bart J. Smit
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=1378148801760-50517.post@n4.nabble.com \
--to=matthieu.personnaz@wanadoo.fr \
--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