From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hamish Moffatt Date: Tue, 2 Sep 2008 23:07:49 +1000 Subject: [Buildroot] Login exited In-Reply-To: References: Message-ID: <20080902130749.GA12634@cloud.net.au> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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