From: Sabri Altunbas <sabri.altunbas@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot needs a root pasword, why ??
Date: Sat, 25 May 2013 16:18:36 +0200 [thread overview]
Message-ID: <2C98102DFACA44FEA5801B0188B74651@M58p> (raw)
In-Reply-To: <20130525151830.68bca681@skate>
Hi,
> Von: Thomas Petazzoni [mailto:thomas.petazzoni at free-electrons.com]
> Gesendet: Samstag, 25. Mai 2013 15:19
Thomas, fein to meet you.
>
> > On 2013-05-24 22:57 +0200, Sabri Altunbas spake thusly:
> > > If I press ENTER I get this error message
> > >
> > > Welcome to Buildroot
> > > buildroot login: root
> > > Password:
> > > Login incorrect
> > > buildroot login:
>
> On what serial port device are you running the login prompt? Is this
> serial port listed in /etc/securetty?
Inittab
..
..
# Put a getty on the serial port
ttyAMA0::respawn:/sbin/getty -L ttyAMA0 115200 vt100 # GENERIC_SERIAL
..
..
securetty
..
..
ttyS0
ttyS1
ttyS2
ttyS3
ttyAMA0
ttyAMA1
ttyAMA2
ttyAMA3
..
..
I selected sourcery toolchain. In attachement is my .config
Regards, S.Altunbas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/octet-stream
Size: 24824 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130525/5e4c503b/attachment-0001.obj>
next prev parent reply other threads:[~2013-05-25 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 17:36 [Buildroot] buildroot needs a root pasword, why ?? Sabri Altunbas
2013-05-24 17:43 ` Yann E. MORIN
[not found] ` <B2E777BEED5E4FB9A7E403CE15ED3A4A@M58p>
2013-05-24 21:30 ` Yann E. MORIN
2013-05-25 13:18 ` Thomas Petazzoni
2013-05-25 14:18 ` Sabri Altunbas [this message]
2013-05-30 9:44 ` Sabri Altunbas
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=2C98102DFACA44FEA5801B0188B74651@M58p \
--to=sabri.altunbas@gmx.de \
--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.