From: Rob Landley <rob@landley.net>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: initramfs for /dev/console with udev?
Date: Wed, 2 Nov 2005 21:40:24 -0600 [thread overview]
Message-ID: <200511022140.25268.rob@landley.net> (raw)
In-Reply-To: <20051102222030.GP23316@pengutronix.de>
On Wednesday 02 November 2005 16:20, Robert Schwebel wrote:
> Hi,
>
> If I understand Documentation/early-userspace/README correctly it should
> be possible to solve the "unable to open an initial console" problem by
> using a file like
>
> dir /dev 0755 0 0
> nod /dev/console 0600 0 0 c 5 1
> nod /dev/null 0600 0 0 c 1 3
> dir /root 0700 0 0
>
> and let CONFIG_INITRAMFS_SOURCE point to that file. The gpio archive is
> built correctly with that, but my kernel doesn't seem to use it.
1) You have no init in initramfs, so it goes ahead and mounts whatever root=
points to over it. I'm guessing that's where it's looking for /dev/console
from.
2) What's the directory /root for?
> Is anything else needed to use an initrd, like a command line argument?
> My kernel boots from a nfs partition, so it sets nfsroot=...
Note that initramfs and initrd and very different things.
> As I still get the "unable to open an initial console" message it looks
> like the initramfs is not extracted, mounted or however that works.
>
> Robert
Rob
next prev parent reply other threads:[~2005-11-03 3:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 22:20 initramfs for /dev/console with udev? Robert Schwebel
2005-11-03 3:40 ` Rob Landley [this message]
2005-11-03 6:47 ` Robert Schwebel
2005-11-03 17:38 ` Rob Landley
2005-11-03 18:51 ` Robert Schwebel
2005-11-03 19:13 ` Rob Landley
2005-11-03 19:57 ` Roland Dreier
2005-11-03 21:00 ` Rob Landley
2005-11-03 21:29 ` Rob Landley
2005-11-04 21:39 ` Martin Schlemmer
2005-11-04 23:10 ` Rob Landley
2005-11-04 23:11 ` Rob Landley
2005-11-05 0:26 ` Martin Schlemmer
2005-11-05 2:56 ` Rob Landley
2005-11-03 21:41 ` Rob Landley
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=200511022140.25268.rob@landley.net \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=r.schwebel@pengutronix.de \
/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