From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Login troubles
Date: Sun, 7 Mar 2010 16:04:02 +0100 [thread overview]
Message-ID: <20100307160402.09f0825a@surf> (raw)
In-Reply-To: <4B93A1AE.8070406@iwtech.com.au>
Hi Paul,
On Sun, 07 Mar 2010 23:53:02 +1100
Paul Jones <paul.jones@iwtech.com.au> wrote:
> I've just built a basic buildroot for my mini2440 ARM board and it
> successfully boots to the buildroot login: prompt.
> My problem is that I can't seem to login - I haven't touched any of
> the config files and looking at /etc/passwd|shadow the login should
> be root with a blank password?
Right, no password, just press enter.
> I've tried to login both from the serial console (which I set in the
> buildroot menu to /dev/ttySAC0) and the normal console with a usb
> keyboard - no luck.
> buildroot login: root
> Password:
> Login incorrect
Are you sure that you haven't made any change to /etc/securetty ? It
must contain at least /dev/ttySAC0 to allow login as root from this
console. The default target skeleton has a /etc/securetty that
contains /dev/ttySAC0, so it should be ok, unless you made any change
to the skeleton, of course, or used a different skeleton.
Regards,
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-03-07 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 12:53 [Buildroot] Login troubles Paul Jones
2010-03-07 15:04 ` Thomas Petazzoni [this message]
2010-03-07 23:13 ` Paul Jones
[not found] ` <A88EA622BD87C74AB5D6195ECDD53AB4035F163A@iwt-server.iwt.local>
2010-03-09 10:06 ` Paul Jones
2010-05-17 15:21 ` Robert Urban
2010-05-17 15:26 ` Casey Carr
-- strict thread matches above, loose matches on Subject: below --
2010-05-19 10:23 Paul Jones
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=20100307160402.09f0825a@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 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.