From: Paul Jones <paul.jones@iwtech.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] Login troubles
Date: Tue, 09 Mar 2010 21:06:01 +1100 [thread overview]
Message-ID: <4B961D89.6090106@iwtech.com.au> (raw)
In-Reply-To: <A88EA622BD87C74AB5D6195ECDD53AB4035F163A@iwt-server.iwt.local>
I've narrowed down the problem.
When I compile without WCHAR I login as root and never get asked for a
password.
When I compile with WCHAR I get the password prompt and pressing enter
does not work.
That is using buildroot from git.
I'm still using the kernel binary that was supplied with the board,
2.6.32.x Could that be causing the problem?
Paul.
On 8/03/2010 10:13 AM, Paul Jones wrote:
> I thought it might be something I did so I downloaded buildroot again
> and recompiled without changing anything except ARCH and the serial
> console port and got the same result.
>
>
> -----Original Message-----
> From: buildroot-bounces at busybox.net
> [mailto:buildroot-bounces at busybox.net] On Behalf Of Thomas Petazzoni
> Sent: Monday, 8 March 2010 2:04 AM
> To: buildroot at busybox.net
> Subject: Re: [Buildroot] Login troubles
>
> 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
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2010-03-09 10:06 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
2010-03-07 23:13 ` Paul Jones
[not found] ` <A88EA622BD87C74AB5D6195ECDD53AB4035F163A@iwt-server.iwt.local>
2010-03-09 10:06 ` Paul Jones [this message]
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=4B961D89.6090106@iwtech.com.au \
--to=paul.jones@iwtech.com.au \
--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