From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP
Date: Tue, 2 Sep 2008 10:58:37 +1000 [thread overview]
Message-ID: <20080902005836.GA1637@cloud.net.au> (raw)
In-Reply-To: <ed4892840808311857w6532170co3ae626bb8dae34a2@mail.gmail.com>
On Mon, Sep 01, 2008 at 09:57:49AM +0800, Steven Woody wrote:
> After guess and guess and build and burn, my rootfs still can not
> boot, it always get "Can't open /dev/tty1[2,3...]" after kernel loaded
> just load it. I attached the full boot message and my buildroot
> .config, I hope, with best regards, someone could help me.
I couldn't work out where your target_skeleton and device table are
coming from based on your config. Do you have a device table, and does
it have those /dev/tty1,2,3,4 devices?
Maybe you could post the output of the build process.
> VFS: Mounted root (cramfs filesystem) readonly.
> Freeing init memory: 84K
> mkdir: cannot create directory '/dev/pts': Read-only file system
> mount: mounting devpts on /dev/pts failed: No such file or directory
Your inittab is obviously trying to make directories in a read-only file
system which isn't going to work. Not that it's related.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-09-02 0:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 1:57 [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP Steven Woody
2008-09-02 0:58 ` Hamish Moffatt [this message]
2008-09-02 1:39 ` Steven Woody
2008-09-02 6:24 ` Emil Kruper
2008-09-02 10:27 ` Steven Woody
2008-09-02 11:29 ` Steven Woody
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=20080902005836.GA1637@cloud.net.au \
--to=hamish@cloud.net.au \
--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