Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stéphane Mancini" <stephane.mancini@grenoble-inp.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Login on a ttyS fails
Date: Tue, 16 Sep 2008 17:31:48 +0200	[thread overview]
Message-ID: <1221579108.7973.21.camel@chip.lis.inpg.fr> (raw)

Hi,
I'm trying to set up linux on a Xilinx platform.
The boot starts but the root login fails 
after prompting :


I've made some prompt in login.c (busybox) and I have the following

################ LOG ######################
boot stuff 
init started: BusyBox v1.12.0 (2008-09-16 16:37:51 CEST)
command='/bin/mount -t proc proc /proc' action=1 tty='/dev/null'

command='/etc/init.d/rcS' action=1 tty=''

command='/sbin/getty -L ttyUL0 57600 vt100 ' action=2 tty='/dev/ttyUL0'

command='/bin/touch /var/log/messages' action=1 tty='/dev/null'

command='/sbin/reboot' action=32 tty=''

command='/sbin/swapoff -a' action=64 tty='/dev/null'

Welcome to the Erik's uClibc development environment.
(none) login: root
Dec 31 17:00:12 login[169]: root login succeeded  on the TTY : 'ttyUL0'
-> /bin/ash
Dec 31 17:00:12 login[169]: Run t


Welcome to the Erik's uClibc development environment.
(none) login: 

#######

I've modified the login.c text to be sure of which code is executing.

It appears that it goes up to the call to the shell. But, then, nothing
happens. 
I've put a 
	syslog(LOG_INFO, "Get to the shell ash!!\n");
at the begining of ash.c:ash_main(int argc UNUSED_PARAM, char **argv)
It's never displayed !

I've also modified inittab to execute "ash" instead of "/init" but
nothing happen also.

It seems that there's a trouble with the shell......

I'm using the Xilinx UARTLITE and the driver comming with linux 2.6.26.2

Maybe there's something wrong with this device but it seems to work
perfectly since I can see all the boot process !

Please, can you tell me :
 what are the configuration parameters to be set to run a a shell on
this tty properly ?
To mean, in buildroot, busybox, libc, linux, etc ....

I set the console on ttyUL0. Is it correct ?

Greetings !

St?phane Mancini


-- 
|St?phane Mancini   Ma?tre de Conference ENSIMAG/GIPSA-lab DIS
| Tel : 04 76 57 43 58
| 961 rue de la Houille Blanche
| Domaine universitaire - BP 46
| 38402 Saint Martin d'H?res cedex
| Email : stephane.mancini at grenoble-inp.fr
| http://www.lis.inpg.fr/pages_perso/mancini
================================================
Join us for the DASIP'08 Conference
ULB, Bruxelles, Belgique
Visit http://www.ecsi.org/dasip/
================================================

             reply	other threads:[~2008-09-16 15:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 15:31 Stéphane Mancini [this message]
2008-09-16 18:37 ` [Buildroot] Login on a ttyS fails Peter Korsgaard
2008-09-17 10:48   ` Stéphane Mancini
2008-09-17 10:55     ` Flemming Madsen
2008-09-17 11:31     ` Peter Korsgaard
     [not found]       ` <1221652957.30276.16.camel@chip.lis.inpg.fr>
2008-09-17 12:24         ` Stéphane Mancini
2008-09-17 12:34           ` Peter Korsgaard
2008-09-17 14:09             ` Stéphane Mancini
2008-09-17 14:20               ` Peter Korsgaard

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=1221579108.7973.21.camel@chip.lis.inpg.fr \
    --to=stephane.mancini@grenoble-inp.fr \
    --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