Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] busybox login problem on AT91SAM9263
Date: Wed, 21 Jan 2009 18:36:09 +0100	[thread overview]
Message-ID: <1232559369.11888.20.camel@elrond.atmel.com> (raw)
In-Reply-To: <8763k8uacw.fsf@macbook.be.48ers.dk>

ons 2009-01-21 klockan 13:11 +0100 skrev Peter Korsgaard:
> >>>>> "Robin" == Stridh, Robin ActeSE <robin.stridh@acteembedded.se> writes:
> 
> Hi,
> 
>  Robin> Hi Peter and thanks for your quick reply!
> 
> You're welcome.
> 
>  Peter> Then it's time to debug. Do you have an /etc/securetty on the target
>  Peter> and does it list ttyS0?
> 
>  Robin> Yes, ttyS0 is listed in /etc/securetty. The only change i made
>  Robin> from the non working to the working version is changing the
>  Robin> busybox version and rebuild buildroot.
> 
> Ok, are you using the default busybox config
> (package/busybox/busybox-1.13.x.config) or a custom one?

Last time I loaded the SAM9263 board was 10-12 days ago,
and at that time I managed to get the board running
without any such problem, 
- I might have upgraded the uclibc-config though.

BR
Ulf Samuelsson




>  Peter> If that's ok, then I would suggest you enable strace, boot with
>  Peter> init=/bin/sh and send the strace output of running login here to the
>  Peter> list.
> 
>  Robin> I tried passing init=/bin/sh to the kernel, but then I end up
>  Robin> without a shell.  The console is still responsive and echoes
>  Robin> everything I type and produces newlines when I hit return but
>  Robin> nothing more.
> 
> Strange, that doesn't sound right. What is you console= on the kernel
> cmdline set to?
> 

  parent reply	other threads:[~2009-01-21 17:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 10:00 [Buildroot] busybox login problem on AT91SAM9263 Stridh, Robin ActeSE
2009-01-21 11:02 ` Peter Korsgaard
2009-01-21 11:10   ` Stridh, Robin ActeSE
2009-01-21 12:11     ` Peter Korsgaard
2009-01-21 12:50       ` Stridh, Robin ActeSE
2009-01-21 12:50       ` Stridh, Robin ActeSE
2009-01-21 17:36       ` Ulf Samuelsson [this message]
2009-01-22 12:45         ` Stridh, Robin ActeSE
2009-01-22 13:02           ` Peter Korsgaard
2009-01-22 14:52             ` Stridh, Robin ActeSE
2009-01-22 15:11               ` Peter Korsgaard
2009-01-22 15:22                 ` Stridh, Robin ActeSE
2009-01-22 15:45                   ` Peter Korsgaard
2009-01-22 15:47                     ` Stridh, Robin ActeSE
2009-01-22 19:12                     ` Stridh, Robin ActeSE
2009-01-23 11:06                       ` Peter Korsgaard
2009-01-23 13:02                         ` Ulf Samuelsson
2009-01-23 13:01                           ` Stridh, Robin ActeSE
2009-01-23 14:30                           ` Sven Neumann
2009-01-23 14:50                             ` Ulf Samuelsson
2009-01-23 11:16                       ` Sven Neumann

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=1232559369.11888.20.camel@elrond.atmel.com \
    --to=ulf.samuelsson@atmel.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