Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Login exited
Date: Tue, 2 Sep 2008 23:07:49 +1000	[thread overview]
Message-ID: <20080902130749.GA12634@cloud.net.au> (raw)
In-Reply-To: <ed4892840809020426s36489484t7ca0a5dd2863733e@mail.gmail.com>

On Tue, Sep 02, 2008 at 07:26:44PM +0800, Steven Woody wrote:
> I think the origin of the "can't open /dev/ttySxxx" problem is differ
> with the origin of the "getty exited" problem.  And, for the former, I
> think it has nothing to do with my device_table.txt,  since if I
> comment out the following line in etc/inittab:
>    ::sysinit:/bin/mount -t tmpfs -o size=64k,mode=0755 none /dev
> and replace it with
>    ::sysinit:/bin/mount -t tmpfs -o size=64k,mode=0755 none /dev
> then, the "can't open /dev/ttySxxx" problem gone away.  so I think,

What is the difference between these two lines? I don't see one.

> But, as you know, this problem had been resoved, I finally get the
> login problem and the system is waiting for me to login.  My new
> problem is that I can not login.  When I type in user name 'root' at
> the prompt, I got the on-console log message:
>     Dec 31 17:24:45 ffcplus daemon.info init: init: process
> '/usr/bin/tail -f /var/log/messages' (pid 7568) exited. Scheduling for
> restart.

Maybe you could boot your system with the command line "init=/bin/sh" so
that it skips all start up scripts and see what happens?

> > And, I got see a suspicious messages just after the kernel booted:
> > ---
> > VFS: Mounted root (cramfs filesystem) readonly.
> > Freeing init memory: 84K
> > Error -3 while decompressing!
> > c0925384(-7384812)->c3e38000(4096)
> > ---

Yes I wonder if your root image has not loaded properly by the boot
loader and hence your root file system is incomplete.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2008-09-02 13:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01  8:02 [Buildroot] Login exited Steven Woody
2008-09-02  0:47 ` Steven Woody
2008-09-02  6:24   ` Emil Kruper
2008-09-02 11:26     ` Steven Woody
2008-09-02 13:07       ` Hamish Moffatt [this message]
2008-09-02 15:09         ` Steven Woody
2008-09-02 15:10           ` Steven Woody
2008-09-03  1:00             ` Hamish Moffatt
2008-09-03  0:59           ` Hamish Moffatt
2008-09-03  3:55             ` Steven Woody
     [not found]   ` <200809031950.49148.vda.linux@googlemail.com>
2008-09-04  1:50     ` Steven Woody
2008-09-04  2:00       ` Hamish Moffatt
2008-09-04  5:34         ` Steven Woody
2008-09-04 14:29           ` Hamish Moffatt
2008-09-04 15:49             ` Steven Woody
2008-09-05  1:07               ` Hamish Moffatt
2008-09-05  7:38                 ` Steven Woody
2008-09-05 13:09                   ` Hamish Moffatt
2008-09-07  5:44                     ` Steven Woody

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=20080902130749.GA12634@cloud.net.au \
    --to=hamish@cloud.net.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