From: Joachim Foerster <mls.JOFT@gmx.de>
To: Cristian Axenie <cristian.axenie@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: USB Flash rootfs prep!
Date: Sat, 15 Nov 2008 09:18:59 +0100 [thread overview]
Message-ID: <1226737139.17218.14.camel@md40100b.ft> (raw)
In-Reply-To: <9c789a000811141705k245e4447k8a9be8e4f180c3f8@mail.gmail.com>
Hi Cristian,
On Sat, 2008-11-15 at 03:05 +0200, Cristian Axenie wrote:
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 156k init
> Warning: unable to open an initial console.
Device file /dev/console doesn't seem to exist in your rootfs.
> Failed to execute /bin/busybox. Attempting defaults...
> Kernel panic - not syncing: No init found. Try passing init= option
> to kernel.
It seems that you don't have an executable called /bin/busybox in your
rootfs. Your kernel command line seems to have "init=/bin/busybox"
included?
But, hmmm, it is very strange, at least in your uboot bootargs there is
no such string. Is it because of some default kernel command line (set
before compiling the kernel)?
> Rebooting in 180 seconds..
>
> Shall I explicitly give the init ? What should be ... init=/sbin/init,
> init=/bin/busybox ????
The rootfs which comes with ELDK "starts" with /sbin/init - it does not
use busybox, right (as far as I can remember)? So you need to specify
"init=/sbin/init" on your kernel command line.
Joachim
next prev parent reply other threads:[~2008-11-15 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 1:05 USB Flash rootfs prep! Cristian Axenie
2008-11-15 8:18 ` Joachim Foerster [this message]
[not found] ` <9c789a000811150112q3088a044ub8b38489b2119a60@mail.gmail.com>
2008-11-15 9:12 ` Cristian Axenie
2008-11-15 10:01 ` Nicholas Mc Guire
2008-11-15 10:17 ` Cristian Axenie
2008-11-15 10:40 ` Nicholas Mc Guire
2008-11-15 11:15 ` Cristian Axenie
2008-11-15 12:12 ` Cristian Axenie
[not found] ` <Pine.LNX.4.58.0811150700530.5061@vlab.hofr.at>
2008-11-16 14:21 ` Cristian Axenie
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=1226737139.17218.14.camel@md40100b.ft \
--to=mls.joft@gmx.de \
--cc=cristian.axenie@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).