From: jeff angielski <jeff@theptrgroup.com>
To: buildroot@busybox.net
Subject: [Buildroot] can't open /dev/tty No such device or address
Date: Mon, 02 Feb 2009 17:29:05 -0500 [thread overview]
Message-ID: <1233613745.7613.23.camel@penguin> (raw)
I am getting the following errors when trying to boot a CRAMFS image on
my PowerPC target.
can't open /dev/tty1: No such device or address
can't open /dev/tty2: No such device or address
can't open /dev/tty3: No such device or address
<repeats over and over>
If I log into the system through my serial port (/dev/ttyCPM0) you can
see that the char devs exist in the fileystem.
crw-rw-rw- 1 root root 4, 1 Dec 31 17:00 tty1
crw-rw-rw- 1 root root 4, 2 Dec 31 17:00 tty2
crw-rw-rw- 1 root root 4, 3 Dec 31 17:00 tty3
The node info matches the device_table.txt.
Any idea what is going on here? Anybody else seeing this?
--
Jeff Angielski
The PTR Group
www.theptrgroup.com
next reply other threads:[~2009-02-02 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 22:29 jeff angielski [this message]
2009-02-02 23:24 ` [Buildroot] can't open /dev/tty No such device or address Hamish Moffatt
2009-02-03 4:03 ` jeff angielski
2009-02-03 7:01 ` Peter Korsgaard
2009-02-03 13:25 ` jeff angielski
2009-02-03 14:28 ` Peter Korsgaard
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=1233613745.7613.23.camel@penguin \
--to=jeff@theptrgroup.com \
--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