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 23:03:49 -0500 [thread overview]
Message-ID: <1233633829.13156.3.camel@penguin> (raw)
In-Reply-To: <20090202232422.GB30540@cloud.net.au>
On Tue, 2009-02-03 at 10:24 +1100, Hamish Moffatt wrote:
> On Mon, Feb 02, 2009 at 05:29:05PM -0500, jeff angielski wrote:
> >
> > 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?
>
> You have the /dev entries but no driver for device 4, 1 etc in the
> kernel.
You are correct. At some point while I was trying to get my serial
port, /dev/ttyCPM0, up and running as the serial console in buildroot I
must have inadvertently disabled Virtual Terminals in the kernel config
file. Once I enabled them again all was well.
Thanks for the info.
--
Jeff Angielski
The PTR Group
www.theptrgroup.com
next prev parent reply other threads:[~2009-02-03 4:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 22:29 [Buildroot] can't open /dev/tty No such device or address jeff angielski
2009-02-02 23:24 ` Hamish Moffatt
2009-02-03 4:03 ` jeff angielski [this message]
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=1233633829.13156.3.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.