From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] cannot log to my build root
Date: Tue, 14 Dec 2010 16:05:58 +0100 [thread overview]
Message-ID: <20101214160558.325cddcb@surf> (raw)
In-Reply-To: <AANLkTikOXep3YnuzHai4fzM-QEGb8BqSZvPsdRvQ_Hkc@mail.gmail.com>
On Tue, 14 Dec 2010 16:54:00 +0200
Diego Iastrubni <diegoiast@gmail.com> wrote:
> VFS: Mounted root (nfs filesystem) on device 0:12.
> Freeing init memory: 152K
> Populating /dev using udev: done
> Initializing random number generator... read-only file system
> detected...done
> Starting network...
> ip: RTNETLINK answers: File exists
> GPIO_M: init
> usbcore: registered new interface driver fjveincam
> v2.21:USB PalmVeinCam driver
> net eth0: MAC Address: 00:11:22:33:44:57
> */bin/sh: can't access tty; job control turned off*
>
> The line before comes from some S90* init.d script (this is OK). I don't
> understand where does it come from.
This last line "can't access tty; job control turned off" means that
the shell has been started directly on /dev/console, which is normal is
you start a shell directly from an init.d script, because those scripts
are executed with /dev/console as the standard input, standard output,
standard err.
You really having *nothing* else on the serial line after what you
sent ?
According to your Buildroot configuration, your /etc/inittab should
contain a line :
ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL
and you should see a login prompt on this serial line.
It's the /etc/inittab file that decides on which terminals a login
prompt should appear, by starting a getty program on those terminals.
What does your /etc/inittab look like ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-12-14 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 13:06 [Buildroot] cannot log to my build root Diego Iastrubni
2010-12-14 13:25 ` Thomas Petazzoni
2010-12-14 13:39 ` Diego Iastrubni
2010-12-14 14:05 ` Thomas Petazzoni
2010-12-14 14:38 ` Diego Iastrubni
2010-12-14 14:42 ` Thomas Petazzoni
2010-12-14 14:54 ` Diego Iastrubni
2010-12-14 15:05 ` Thomas Petazzoni [this message]
2010-12-14 15:28 ` Diego Iastrubni
2010-12-14 15:37 ` Thomas Petazzoni
2010-12-14 15:56 ` Diego Iastrubni
2010-12-14 16:00 ` Thomas Petazzoni
2010-12-14 15:50 ` William Wagner
2010-12-14 16:00 ` Thomas Petazzoni
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=20101214160558.325cddcb@surf \
--to=thomas.petazzoni@free-electrons.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