Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sunr2007 <ravilinux4u@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot]  unable to login to buildroot
Date: Thu, 25 Mar 2010 11:11:36 -0700 (PDT)	[thread overview]
Message-ID: <28032853.post@talk.nabble.com> (raw)


Hi all,
i built a jffs2 filesystem by using make at91sam9261ek_config for
buildroot.2010.02 . everything went fine 
but im unable to login on to my target board :(

when i type root and press enter 
it is redirecting me back to the login

 and when i press any other name , it asks for password but again come back
to login when i press enter 



"Welcome to Buildroot

buildroot login: root


Welcome to Buildroot

buildroot login: ravi
Password: 


Welcome to Buildroot

buildroot login: "


below is my /etc/inittab file  any idea what might be wrong?

# /etc/inittab
#
# Copyright (C) 2001 Erik Andersen <andersen@codepoet.org>
#
# Note: BusyBox init doesn't support runlevels.  The runlevels field is
# completely ignored by BusyBox init. If you want runlevels, use
# sysvinit.
#
# Format for each entry: <id>:<runlevels>:<action>:<process>
#
# id        == tty to run on, or empty for /dev/console
# runlevels == ignored
# action    == one of sysinit, respawn, askfirst, wait, and once
# process   == program to run

# Startup the system
null::sysinit:/bin/mount -o remount,rw /
null::sysinit:/bin/mount -t proc proc /proc
null::sysinit:/bin/mount -a
null::sysinit:/bin/hostname -F /etc/hostname
null::sysinit:/sbin/ifconfig lo 127.0.0.1 up
null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
# now run any rc scripts
::sysinit:/etc/init.d/rcS

# Set up a couple of getty's
#tty1::respawn:/sbin/getty 38400 tty1
#tty2::respawn:/sbin/getty 38400 tty2

# Put a getty on the serial port
ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100


# Logging junk
null::sysinit:/bin/touch /var/log/messages
null::respawn:/sbin/syslogd -n -m 0
null::respawn:/sbin/klogd -n
tty3::respawn:/usr/bin/tail -f /var/log/messages

# Stuff to do for the 3-finger salute
::ctrlaltdel:/sbin/reboot

# Stuff to do before rebooting
null::shutdown:/usr/bin/killall klogd
null::shutdown:/usr/bin/killall syslogd
null::shutdown:/bin/umount -a -r
null::shutdown:/sbin/swapoff -a

any idea what is wrong ? how to debug this?
warm regards,
Ravi Kulkarni.

-- 
View this message in context: http://old.nabble.com/unable-to-login-to-buildroot-tp28032853p28032853.html
Sent from the BuildRoot mailing list archive at Nabble.com.

             reply	other threads:[~2010-03-25 18:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 18:11 sunr2007 [this message]
2010-03-26 11:37 ` [Buildroot] unable to login to buildroot Yury Luneff
  -- strict thread matches above, loose matches on Subject: below --
2011-02-24  9:48 [Buildroot] Unable " Guillaume Dargaud
2011-02-24  9:54 ` Baruch Siach
2011-02-24 10:55   ` Guillaume Dargaud
2011-02-24 11:30 ` Daniel Nyström
2011-02-24 12:59   ` Guillaume Dargaud
2011-02-24 13:28     ` Baruch Siach
     [not found]     ` <4D665ADD.10608@daccii.it>
2011-02-24 14:16       ` Guillaume Dargaud
2011-02-24 15:15         ` Williams, Michael
2011-02-24 15:57           ` Guillaume Dargaud
2011-02-24 11:53 ` Peter Korsgaard
2011-02-24 14:56   ` Guillaume Dargaud

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=28032853.post@talk.nabble.com \
    --to=ravilinux4u@gmail.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