[Buildroot] Login exited

[Buildroot] Login exited

[Steven Woody]

Hi,

The buildroot I am using is the 080831 snapshot. Now I see the boot
prompt finally!  But I can't login:

---
Welcome to uClibc
uClibc login: root
Dec 31 17:01:05 nlmt auth.info login[195]: root login on 'ttyS0'
Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L
ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart.
Dec 31 17:0


Welcome to uClibc
uClibc login: default
Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L
ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart.
Dec 31 17:0
---

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)
---

I think I am so near to success, please help me! Thanks.

-
narke

[Buildroot] Login exited

[Steven Woody]

Hi,

The buildroot I am using is the 080831 snapshot, the busybox is
1.11.2. Now I see the boot
prompt finally!  But I can't login:

---
Welcome to uClibc
uClibc login: root
Dec 31 17:01:05 nlmt auth.info login[195]: root login on 'ttyS0'
Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L
ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart.
Dec 31 17:0

Welcome to uClibc
uClibc login: default
Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L
ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart.
Dec 31 17:0
---

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)
---

I think I am so near to success, please help me! Thanks.

-
narke

[Buildroot] Login exited

[Emil Kruper]

Alter the device table file you have selected in your buildroot config (for
example target/generic/device_table.txt) and rebuild your system. By default
these files don't fit your needs.

In particular have a look at the section # Normal system devices, I think
this could be the origin of your problems.

Best regards,

Emil Kruper


-----Ursprungliche Nachricht-----
Von: buildroot-bounces at uclibc.org
[mailto:buildroot-bounces at uclibc.org]Im Auftrag von Steven Woody
Gesendet: Dienstag, 2. September 2008 02:47
An: buildroot at uclibc.org; busybox at busybox.net
Betreff: Re: [Buildroot] Login exited


Hi,

The buildroot I am using is the 080831 snapshot, the busybox is
1.11.2. Now I see the boot
prompt finally!  But I can't login:

---
Welcome to uClibc
uClibc login: root
Dec 31 17:01:05 nlmt auth.info login[195]: root login on 'ttyS0'
Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L
ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart.
Dec 31 17:0

Welcome to uClibc
uClibc login: default
Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L
ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart.
Dec 31 17:0
---

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)
---

I think I am so near to success, please help me! Thanks.

-
narke
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot

[Buildroot] Login exited

[Steven Woody]

On Tue, Sep 2, 2008 at 2:24 PM, Emil Kruper
<e.krueper@solcon-systemtechnik.de> wrote:
> Alter the device table file you have selected in your buildroot config (for
> example target/generic/device_table.txt) and rebuild your system. By default
> these files don't fit your needs.
>
> In particular have a look at the section # Normal system devices, I think
> this could be the origin of your problems.


Emil,

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,
the original inittab file gives a wrong option to 'mount -t tmpfs'.
That's the origin of the problem --  the /dev did not created
successfuuly, so no /dev/ttySxxx can be opened.

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.

Did you ment to say that the login problem itself has something to do
with my device_table.txt?  I belive the /dev/ttyS0 has already created
properly anyhow, otherwise I should not get the login prompt, am I
right?

I still need your help.


>
> Best regards,
>
> Emil Kruper
>
>
> -----Ursprungliche Nachricht-----
> Von: buildroot-bounces at uclibc.org
> [mailto:buildroot-bounces at uclibc.org]Im Auftrag von Steven Woody
> Gesendet: Dienstag, 2. September 2008 02:47
> An: buildroot at uclibc.org; busybox at busybox.net
> Betreff: Re: [Buildroot] Login exited
>
>
> Hi,
>
> The buildroot I am using is the 080831 snapshot, the busybox is
> 1.11.2. Now I see the boot
> prompt finally!  But I can't login:
>
> ---
> Welcome to uClibc
> uClibc login: root
> Dec 31 17:01:05 nlmt auth.info login[195]: root login on 'ttyS0'
> Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L
> ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart.
> Dec 31 17:0
>
> Welcome to uClibc
> uClibc login: default
> Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L
> ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart.
> Dec 31 17:0
> ---
>
> 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)
> ---
>
> I think I am so near to success, please help me! Thanks.
>
> -
> narke
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>

[Buildroot] Login exited

[Hamish Moffatt]

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>

[Buildroot] Login exited

[Steven Woody]

On Tue, Sep 2, 2008 at 9:07 PM, Hamish Moffatt <hamish@cloud.net.au> wrote:
> 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.

Sorry for the careless.  The correct one should be:
   ::sysinit:/bin/mount -t tmpfs none /dev
That is, without any option.

>
>> 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?

Okay, I will try next when I go office.

>
>> > 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.

I will put an eye to the decompressing error, but by far I have not
figure out why the root files system is possibly incomplete.

-
narke

[Buildroot] Login exited

[Steven Woody]

On Tue, Sep 2, 2008 at 11:09 PM, Steven Woody <narkewoody@gmail.com> wrote:
> On Tue, Sep 2, 2008 at 9:07 PM, Hamish Moffatt <hamish@cloud.net.au> wrote:
>> 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.
>
> Sorry for the careless.  The correct one should be:
>   ::sysinit:/bin/mount -t tmpfs none /dev
> That is, without any option.
>
>>
>>> 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?
>
> Okay, I will try next when I go office.

sorry, I forgot to ask: where to put the command line?

[Buildroot] Login exited

[Hamish Moffatt]

On Tue, Sep 02, 2008 at 11:09:25PM +0800, Steven Woody wrote:
> On Tue, Sep 2, 2008 at 9:07 PM, Hamish Moffatt <hamish@cloud.net.au> wrote:
> > 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.
> 
> Sorry for the careless.  The correct one should be:
>    ::sysinit:/bin/mount -t tmpfs none /dev
> That is, without any option.

That's strange, because those options for tmpfs are valid. The only
problem I can see is that 64k might not be large enough. I don't know
how much space device nodes take - they don't have data but they do have
meta-data of course.

> I will put an eye to the decompressing error, but by far I have not
> figure out why the root files system is possibly incomplete.

Incomplete because of the decompression error, I mean.

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

[Buildroot] Login exited

[Hamish Moffatt]

On Tue, Sep 02, 2008 at 11:10:27PM +0800, Steven Woody wrote:
> On Tue, Sep 2, 2008 at 11:09 PM, Steven Woody <narkewoody@gmail.com> wrote:
> >> 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?
> >
> > Okay, I will try next when I go office.
> 
> sorry, I forgot to ask: where to put the command line?

Your boot loader should allow you to specify the command line to the
kernel. Or the default is set as a kernel configuration option - run
"make linux-menuconfig" etc.

Which boot loader are you using? U-Boot, RedBoot, ... ?

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

[Buildroot] Login exited

[Steven Woody]

On Wed, Sep 3, 2008 at 8:59 AM, Hamish Moffatt <hamish@cloud.net.au> wrote:
> On Tue, Sep 02, 2008 at 11:09:25PM +0800, Steven Woody wrote:
>> On Tue, Sep 2, 2008 at 9:07 PM, Hamish Moffatt <hamish@cloud.net.au> wrote:
>> > 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.
>>
>> Sorry for the careless.  The correct one should be:
>>    ::sysinit:/bin/mount -t tmpfs none /dev
>> That is, without any option.
>
> That's strange, because those options for tmpfs are valid. The only
> problem I can see is that 64k might not be large enough. I don't know
> how much space device nodes take - they don't have data but they do have
> meta-data of course.

I tried size=256k, the result is the same, /dev can not be created successfully.

>
>> I will put an eye to the decompressing error, but by far I have not
>> figure out why the root files system is possibly incomplete.
>
> Incomplete because of the decompression error, I mean.

I can not image there is any reason that can cause the rootfs image
file corrupt.  If it is corrupted when in build stage, the xxx.cramfs
would not be created. If it is corrupted in rootfs downloading stage,
the bootloader (mine is vivi) should say somthing.


Is there a method that can let me print debug information on the
screen before the login prompt and after the last kernel loading
message?  I tried add something like
  null:sysinit: .... :/bin/ls /dev
or
  null:sysinit: .... :/bin/echo hello
But I see nothing.

I want to do some debug to find more information.


Again, below is my full message for you consideration:


---------------
Freeing init memory: 84K
mount: mounting configfs on /config failed: No such device
Error -3 while decompressing!
c021ac2c(-8656788)->c3e6e000(4096)
Dec 31 17:00:02 nlmt syslog.info syslogd started: BusyBox v1.12.0
Dec 31 17:00:02 nlmt daemon.info init: init: starting pid 205, tty
'/dev/null': '/sbin/klogd -n'
Dec 31 17:00:02 nlmt user.notice kernel: klogd started: BusyBox
v1.12.0 (2008-09-02 20:51:05 CST)
Dec 31 17:00:02 nlmt user.notice kernel: Linux version 2.6.16.4
(root at haohuibin) (gcc version 3.3) #638 Mon Aug 4 11:59:45 CST 2008
Dec 31 17:00:02 nlmt user.warn kernel: CPU: ARM920Tid(wb) [41129200]
revision 0 (ARMv4T)
Dec 31 17:00:02 nlmt user.warn kernel: Machine: LMT
Dec 31 17:00:02 nlmt user.debug kernel: Converting old-style param
struct to taglist
Dec 31 17:00:02 nlmt user.warn kernel: Memory policy: ECC disabled,
Data cache writeback
Dec 31 17:00:02 nlmt user.debug kernel: On node 0 totalpages: 16384
Dec 31 17:00:02 nlmt user.debug kernel:   DMA zone: 16384 pages, LIFO batch:3
Dec 31 17:00:02 nlmt user.debug kernel:   DMA32 zone: 0 pages, LIFO batch:0
Dec 31 17:00:02 nlmt user.debug kernel:   Normal zone: 0 pages, LIFO batch:0
Dec 31 17:00:02 nlmt user.debug kernel:   HighMem zone: 0 pages, LIFO batch:0
Dec 31 17:00:02 nlmt user.warn kernel: CPU S3C2440A (id 0x32440001)
Dec 31 17:00:02 nlmt user.warn kernel: S3C2440: core 399.651 MHz,
memory 99.912 MHz, peripheral 49.956 MHz
Dec 31 17:00:02 nlmt user.info kernel: S3C2410 Clocks, (c) 2004 Simtec
Electronics
Dec 31 17:00:02 nlmt user.warn kernel: CLOCK: Slow mode (2.116 MHz),
fast, MPLL on, UPLL on
Dec 31 17:00:02 nlmt user.warn kernel: CPU0: D VIVT write-back cache
Dec 31 17:00:02 nlmt user.warn kernel: CPU0: I cache: 16384 bytes,
associativity 64, 32 byte lines, 8 sets
Dec 31 17:00:02 nlmt user.warn kernel: CPU0: D cache: 16384 bytes,
associativity 64, 32 byte lines, 8 sets
Dec 31 17:00:02 nlmt user.warn kernel: Built 1 zonelists
Dec 31 17:00:02 nlmt user.notice kernel: Kernel command line:
root=/dev/mtdblock3 console=ttyS0
Dec 31 17:00:02 nlmt user.warn kernel: irq: clearing pending ext status 00000020
Dec 31 17:00:02 nlmt user.warn kernel: irq: clearing subpending status 00000003
Dec 31 17:00:02 nlmt user.warn kernel: irq: clearing subpending status 00000002
Dec 31 17:00:02 nlmt user.warn kernel: PID hash table entries: 512
(order: 9, 8192 bytes)
Dec 31 17:00:02 nlmt user.warn kernel: timer tcon=00500000, tcnt a29d,
tcfg 00000200,00000000, usec 00001ebf
Dec 31 17:00:02 nlmt user.warn kernel: Console: colour dummy device 80x30
Dec 31 17:00:02 nlmt user.warn kernel: Dentry cache hash table
entries: 16384 (order: 4, 65536 bytes)
Dec 31 17:00:02 nlmt user.warn kernel: Inode-cache hash table entries:
8192 (order: 3, 32768 bytes)
Dec 31 17:00:02 nlmt user.info kernel: Memory: 64MB = 64MB total
Dec 31 17:00:02 nlmt user.notice kernel: Memory: 62604KB available
(1880K code, 230K data, 84K init)
Dec 31 17:00:02 nlmt user.debug kernel: Calibrating delay loop...
199.47 BogoMIPS (lpj=498688)
Dec 31 17:00:02 nlmt user.warn kernel: Mount-cache hash table entries: 512
Dec 31 17:00:02 nlmt user.info kernel: CPU: Testing write buffer coherency: ok
Dec 31 17:00:02 nlmt user.info kernel: NET: Registered protocol family 16
Dec 31 17:00:02 nlmt user.warn kernel: S3C2440: Initialising architecture
Dec 31 17:00:02 nlmt user.warn kernel: S3C2440: IRQ Support
Dec 31 17:00:02 nlmt user.warn kernel: S3C2440: Clock Support, UPLL
47.980 MHz, DVS off
Dec 31 17:00:02 nlmt user.notice kernel: SCSI subsystem initialized
Dec 31 17:00:02 nlmt user.info kernel: usbcore: registered new driver usbfs
Dec 31 17:00:02 nlmt user.info kernel: usbcore: registered new driver hub
Dec 31 17:00:02 nlmt user.warn kernel: S3C2410 DMA Driver, (c)
2003-2004 Simtec Electronics
Dec 31 17:00:02 nlmt user.warn kernel: DMA channel 0 at c4800000, irq 33
Dec 31 17:00:02 nlmt user.warn kernel: DMA channel 1 at c4800040, irq 34
Dec 31 17:00:02 nlmt user.warn kernel: DMA channel 2 at c4800080, irq 35
Dec 31 17:00:02 nlmt user.warn kernel: DMA channel 3 at c48000c0, irq 36
Dec 31 17:00:02 nlmt user.warn kernel: yaffs Aug  4 2008 11:57:59 Installing.
Dec 31 17:00:02 nlmt user.info kernel: io scheduler noop registered (default)
Dec 31 17:00:02 nlmt user.warn kernel: Console: switching to mono
frame buffer device 20x20
Dec 31 17:00:02 nlmt user.info kernel: fb0: s3c2410fb frame buffer device
Dec 31 17:00:02 nlmt user.warn kernel: S3C2410 RTC, (c) 2004 Simtec Electronics
Dec 31 17:00:02 nlmt user.info kernel: s3c2410-rtc s3c2410-rtc: rtc
disabled, re-enabling
Dec 31 17:00:02 nlmt user.info kernel: Serial: 8250/16550 driver
$Revision: 1.90 $ 2 ports, IRQ sharing disabled
Dec 31 17:00:02 nlmt user.info kernel: serial8250: tts0 at MMIO
0xe1500000 (irq = 18) is a 16550A
Dec 31 17:00:02 nlmt user.info kernel: serial8250: tts1 at MMIO
0xe1500008 (irq = 19) is a 16550A
Dec 31 17:00:02 nlmt user.info kernel: s3c2440-uaDec 31 17:00:02 nlmt
user.info kernel: s3c2440-uDec 31 17:00:02 nlmt user.notice kernel:
cmdlineDec 31 17:00:02 nlmt user.notice kernel: RedBootDec 31 17:00:02
nlmt user.info kernel: Scanning Dec 31 17:00:02 nlmt user.info kernel:
s3c2410-oDec 31 17:00:02 nlmt user.info kernel: usbcore: Dec 31
17:00:02 nlmt user.info kernel: NET: RegiDec 31 17:00:02 nlmt
user.info kernel: TCP reno Dec 31 17:00:02 nlmt user.info kernel: usb
1-1: Dec 31 17:00:02 nlmt user.warn kernel: Error -3


Welcome to the Erik's uClibc development environment.
nlmt login:   Vendor: Teclast   Model: CoolFlash         Rev: 0.00
  Type:   Direct-Access                      ANSI SCSI revision: 02
Dec 31 17:00:06 nlmt user.notice kernel:   Vendor: Teclast   Model:
CoolFlash SCSI device sda: 1007616 512-byte hdwr sectors (516 MB)
        Rev: 0.00
Dec 31 17:00:06 nlmt user.notsda: Write Protect is off
sda: assuming drive cache: write through
ice kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
Dec 31 17:00:06 nlmt user.notice kernel: SCSI device sda: 10076SCSI
device sda: 1007616 512-byte hdwr sectors (516 MB)
16 512-byte hdwr sectors (516 MB)
Dec 31 17:00:sda: Write Protect is off
sda: assuming drive cache: write through
 sda:06 nlmt user.notice kernel: sda: Write Protect is off
Dec 31 17:00:06 nlmt user.debug kernel: sda: Mode Sense: 00 00 00 00
Dec 31 17:00:06 nlmt user.err kernel: sda: assuming drive cache: write through
Dec 31 17:00:06 nlmt user.notice kernel: SCSI device sda: 1007616
512-byte hdwr sectors (516 MB)
Dec 31 17:00:06 nlmt user.notice kernel: sda: Write Protect is off
Dec 31 17:00:06 nlmt user.debug kernel: sda: Mode Sense: 00 00 00 00
Dec 31 17:00:06 nlmt user.err kernel: sda: assuming drive cache: write through
Dec 31 17:00:06 nlmt user.info kernel:  sda:
 sda1
sd 0:0:0:0: Attached scsi removable disk sda
Dec 31 17:00:06 nlmt user.info kernel:  sda1
Dec 31 17:00:06 nlmt user.notice kernel: sd 0:0:0:0: Attached scsi
removable disk sda
Dec 31 17:00:06 nlmt user.debug kernel: usb-storage: device scan complete



Welcome to the Erik's uClibc development environment.
nlmt login: root
Dec 31 17:00:29 nlmt auth.info login[203]: root login on 'ttyS0'
Dec 31 17:00:29 nlmt daemon.info init: init: process '/sbin/getty -L
ttyS0 115200 vt100' (pid 203) exited. Scheduling for restart.
Dec 31 17:0


Welcome to the Erik's uClibc development environment.
nlmt login:

[Buildroot] Login exited

[Steven Woody]

On Thu, Sep 4, 2008 at 1:50 AM, Denys Vlasenko <vda.linux@googlemail.com> wrote:
> On Tuesday 02 September 2008 02:47, Steven Woody wrote:
>> The buildroot I am using is the 080831 snapshot, the busybox is
>> 1.11.2. Now I see the boot
>> prompt finally!  But I can't login:
>>
>> ---
>> Welcome to uClibc
>> uClibc login: root
>> Dec 31 17:01:05 nlmt auth.info login[195]: root login on 'ttyS0'
>> Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L
>> ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart.
>> Dec 31 17:0
>>
>> Welcome to uClibc
>> uClibc login: default
>> Dec 31 17:01:05 nlmt daemon.info init: init: process '/sbin/getty -L
>> ttyS0 115200 vt100' (pid 195) exited. Scheduling for restart.
>> Dec 31 17:0
>> ---
>>
>> 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)
>
> Coming from kernel's fs/cramfs/uncompress.c:
>
> err:
>        printk("Error %d while decompressing!\n", err);
>        printk("%p(%d)->%p(%d)\n", src, srclen, dst, dstlen);
>        return 0;
>
>> I think I am so near to success, please help me! Thanks.
>
> Your filesystem image seems to be damaged.

Okay, we leave this 'decompressing' error for a moment.  I rebuilt
(mostly using default options from buildroot) a very small rootfs
image, 780k cramfs.  This time, it boots without the 'decompressing'
error message, I still can not login in.  It's same: whatever user
name I inputed, the getty restarted and I get nothing but another
prompt.

If you experts can not guess what's is going on here, I hope you can
tell me how to debug this kind of problem.  Tks.

> --
> vda
>

[Buildroot] Login exited

[Hamish Moffatt]

On Thu, Sep 04, 2008 at 09:50:01AM +0800, Steven Woody wrote:
> Okay, we leave this 'decompressing' error for a moment.  I rebuilt

Actually on second reading I think that is a result of trying to mount
configfs on /config, and nothing to do with the root filesystem itself.

> (mostly using default options from buildroot) a very small rootfs
> image, 780k cramfs.  This time, it boots without the 'decompressing'
> error message, I still can not login in.  It's same: whatever user
> name I inputed, the getty restarted and I get nothing but another
> prompt.
> 
> If you experts can not guess what's is going on here, I hope you can
> tell me how to debug this kind of problem.  Tks.

Did you try booting with init=/bin/sh as I suggested two days ago? Or
modify your inittab to present you with a shell without needing to
login? This will help to break down the problem dramatically.

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

[Buildroot] Login exited

[Steven Woody]

On Thu, Sep 4, 2008 at 10:00 AM, Hamish Moffatt <hamish@cloud.net.au> wrote:
> On Thu, Sep 04, 2008 at 09:50:01AM +0800, Steven Woody wrote:
>> Okay, we leave this 'decompressing' error for a moment.  I rebuilt
>
> Actually on second reading I think that is a result of trying to mount
> configfs on /config, and nothing to do with the root filesystem itself.
>
>> (mostly using default options from buildroot) a very small rootfs
>> image, 780k cramfs.  This time, it boots without the 'decompressing'
>> error message, I still can not login in.  It's same: whatever user
>> name I inputed, the getty restarted and I get nothing but another
>> prompt.
>>
>> If you experts can not guess what's is going on here, I hope you can
>> tell me how to debug this kind of problem.  Tks.
>
> Did you try booting with init=/bin/sh as I suggested two days ago? Or
> modify your inittab to present you with a shell without needing to
> login? This will help to break down the problem dramatically.

I did init=/bin/sh as you suggested and reported the result to the
list.  Again, the result is:  there is nothing I can do after rootfs
was loaded by kernel.  I can type in characters can see the echo of
what I typed on the screen, but no any other outputs.  Does this has
something to do with my read-only file system type (cramfs)?

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

[Buildroot] Login exited

[Hamish Moffatt]

On Thu, Sep 04, 2008 at 01:34:14PM +0800, Steven Woody wrote:
> On Thu, Sep 4, 2008 at 10:00 AM, Hamish Moffatt <hamish@cloud.net.au> wrote:
> > Did you try booting with init=/bin/sh as I suggested two days ago? Or
> > modify your inittab to present you with a shell without needing to
> > login? This will help to break down the problem dramatically.
> 
> I did init=/bin/sh as you suggested and reported the result to the
> list.  Again, the result is:  there is nothing I can do after rootfs
> was loaded by kernel.  I can type in characters can see the echo of
> what I typed on the screen, but no any other outputs.  Does this has
> something to do with my read-only file system type (cramfs)?

I didn't see your posting. Do you get a prompt? Do you get any messages
at all after the kernel loads, loads the RAM disk, etc? Please post the
whole log.

No I don't see how the root file system being read-only would be
significant. cramfs is always read-only. I build cramfs here with
buildroot and it works just fine.

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

[Buildroot] Login exited

[Steven Woody]

On Thu, Sep 4, 2008 at 10:29 PM, Hamish Moffatt <hamish@cloud.net.au> wrote:
> On Thu, Sep 04, 2008 at 01:34:14PM +0800, Steven Woody wrote:
>> On Thu, Sep 4, 2008 at 10:00 AM, Hamish Moffatt <hamish@cloud.net.au> wrote:
>> > Did you try booting with init=/bin/sh as I suggested two days ago? Or
>> > modify your inittab to present you with a shell without needing to
>> > login? This will help to break down the problem dramatically.
>>
>> I did init=/bin/sh as you suggested and reported the result to the
>> list.  Again, the result is:  there is nothing I can do after rootfs
>> was loaded by kernel.  I can type in characters can see the echo of
>> what I typed on the screen, but no any other outputs.  Does this has
>> something to do with my read-only file system type (cramfs)?
>
> I didn't see your posting. Do you get a prompt? Do you get any messages
> at all after the kernel loads, loads the RAM disk, etc? Please post the
> whole log.
>
> No I don't see how the root file system being read-only would be
> significant. cramfs is always read-only. I build cramfs here with
> buildroot and it works just fine.
>
> Hamish

Hi, Hamish

Below are the whole boot message, and I like to say sorry to other
peoples here for the reposting.

---------------
Freeing init memory: 84K
mount: mounting configfs on /config failed: No such device
Error -3 while decompressing!
c021ac2c(-8656788)->c3e6e000(4096)
Dec 31 17:00:02 nlmt syslog.info syslogd started: BusyBox v1.12.0
Dec 31 17:00:02 nlmt daemon.info init: init: starting pid 205, tty
'/dev/null': '/sbin/klogd -n'
Dec 31 17:00:02 nlmt user.notice kernel: klogd started: BusyBox
v1.12.0 (2008-09-02 20:51:05 CST)
Dec 31 17:00:02 nlmt user.notice kernel: Linux version 2.6.16.4
(root at haohuibin) (gcc version 3.3) #638 Mon Aug 4 11:59:45 CST 2008
Dec 31 17:00:02 nlmt user.warn kernel: CPU: ARM920Tid(wb) [41129200]
revision 0 (ARMv4T)
Dec 31 17:00:02 nlmt user.warn kernel: Machine: LMT
Dec 31 17:00:02 nlmt user.debug kernel: Converting old-style param
struct to taglist
Dec 31 17:00:02 nlmt user.warn kernel: Memory policy: ECC disabled,
Data cache writeback
Dec 31 17:00:02 nlmt user.debug kernel: On node 0 totalpages: 16384
Dec 31 17:00:02 nlmt user.debug kernel:   DMA zone: 16384 pages, LIFO batch:3
Dec 31 17:00:02 nlmt user.debug kernel:   DMA32 zone: 0 pages, LIFO batch:0
Dec 31 17:00:02 nlmt user.debug kernel:   Normal zone: 0 pages, LIFO batch:0
Dec 31 17:00:02 nlmt user.debug kernel:   HighMem zone: 0 pages, LIFO batch:0
Dec 31 17:00:02 nlmt user.warn kernel: CPU S3C2440A (id 0x32440001)
Dec 31 17:00:02 nlmt user.warn kernel: S3C2440: core 399.651 MHz,
memory 99.912 MHz, peripheral 49.956 MHz
Dec 31 17:00:02 nlmt user.info kernel: S3C2410 Clocks, (c) 2004 Simtec
Electronics
Dec 31 17:00:02 nlmt user.warn kernel: CLOCK: Slow mode (2.116 MHz),
fast, MPLL on, UPLL on
Dec 31 17:00:02 nlmt user.warn kernel: CPU0: D VIVT write-back cache
Dec 31 17:00:02 nlmt user.warn kernel: CPU0: I cache: 16384 bytes,
associativity 64, 32 byte lines, 8 sets
Dec 31 17:00:02 nlmt user.warn kernel: CPU0: D cache: 16384 bytes,
associativity 64, 32 byte lines, 8 sets
Dec 31 17:00:02 nlmt user.warn kernel: Built 1 zonelists
Dec 31 17:00:02 nlmt user.notice kernel: Kernel command line:
root=/dev/mtdblock3 console=ttyS0
Dec 31 17:00:02 nlmt user.warn kernel: irq: clearing pending ext status 00000020
Dec 31 17:00:02 nlmt user.warn kernel: irq: clearing subpending status 00000003
Dec 31 17:00:02 nlmt user.warn kernel: irq: clearing subpending status 00000002
Dec 31 17:00:02 nlmt user.warn kernel: PID hash table entries: 512
(order: 9, 8192 bytes)
Dec 31 17:00:02 nlmt user.warn kernel: timer tcon=00500000, tcnt a29d,
tcfg 00000200,00000000, usec 00001ebf
Dec 31 17:00:02 nlmt user.warn kernel: Console: colour dummy device 80x30
Dec 31 17:00:02 nlmt user.warn kernel: Dentry cache hash table
entries: 16384 (order: 4, 65536 bytes)
Dec 31 17:00:02 nlmt user.warn kernel: Inode-cache hash table entries:
8192 (order: 3, 32768 bytes)
Dec 31 17:00:02 nlmt user.info kernel: Memory: 64MB = 64MB total
Dec 31 17:00:02 nlmt user.notice kernel: Memory: 62604KB available
(1880K code, 230K data, 84K init)
Dec 31 17:00:02 nlmt user.debug kernel: Calibrating delay loop...
199.47 BogoMIPS (lpj=498688)
Dec 31 17:00:02 nlmt user.warn kernel: Mount-cache hash table entries: 512
Dec 31 17:00:02 nlmt user.info kernel: CPU: Testing write buffer coherency: ok
Dec 31 17:00:02 nlmt user.info kernel: NET: Registered protocol family 16
Dec 31 17:00:02 nlmt user.warn kernel: S3C2440: Initialising architecture
Dec 31 17:00:02 nlmt user.warn kernel: S3C2440: IRQ Support
Dec 31 17:00:02 nlmt user.warn kernel: S3C2440: Clock Support, UPLL
47.980 MHz, DVS off
Dec 31 17:00:02 nlmt user.notice kernel: SCSI subsystem initialized
Dec 31 17:00:02 nlmt user.info kernel: usbcore: registered new driver usbfs
Dec 31 17:00:02 nlmt user.info kernel: usbcore: registered new driver hub
Dec 31 17:00:02 nlmt user.warn kernel: S3C2410 DMA Driver, (c)
2003-2004 Simtec Electronics
Dec 31 17:00:02 nlmt user.warn kernel: DMA channel 0 at c4800000, irq 33
Dec 31 17:00:02 nlmt user.warn kernel: DMA channel 1 at c4800040, irq 34
Dec 31 17:00:02 nlmt user.warn kernel: DMA channel 2 at c4800080, irq 35
Dec 31 17:00:02 nlmt user.warn kernel: DMA channel 3 at c48000c0, irq 36
Dec 31 17:00:02 nlmt user.warn kernel: yaffs Aug  4 2008 11:57:59 Installing.
Dec 31 17:00:02 nlmt user.info kernel: io scheduler noop registered (default)
Dec 31 17:00:02 nlmt user.warn kernel: Console: switching to mono
frame buffer device 20x20
Dec 31 17:00:02 nlmt user.info kernel: fb0: s3c2410fb frame buffer device
Dec 31 17:00:02 nlmt user.warn kernel: S3C2410 RTC, (c) 2004 Simtec Electronics
Dec 31 17:00:02 nlmt user.info kernel: s3c2410-rtc s3c2410-rtc: rtc
disabled, re-enabling
Dec 31 17:00:02 nlmt user.info kernel: Serial: 8250/16550 driver
$Revision: 1.90 $ 2 ports, IRQ sharing disabled
Dec 31 17:00:02 nlmt user.info kernel: serial8250: tts0 at MMIO
0xe1500000 (irq = 18) is a 16550A
Dec 31 17:00:02 nlmt user.info kernel: serial8250: tts1 at MMIO
0xe1500008 (irq = 19) is a 16550A
Dec 31 17:00:02 nlmt user.info kernel: s3c2440-uaDec 31 17:00:02 nlmt
user.info kernel: s3c2440-uDec 31 17:00:02 nlmt user.notice kernel:
cmdlineDec 31 17:00:02 nlmt user.notice kernel: RedBootDec 31 17:00:02
nlmt user.info kernel: Scanning Dec 31 17:00:02 nlmt user.info kernel:
s3c2410-oDec 31 17:00:02 nlmt user.info kernel: usbcore: Dec 31
17:00:02 nlmt user.info kernel: NET: RegiDec 31 17:00:02 nlmt
user.info kernel: TCP reno Dec 31 17:00:02 nlmt user.info kernel: usb
1-1: Dec 31 17:00:02 nlmt user.warn kernel: Error -3


Welcome to the Erik's uClibc development environment.
nlmt login:   Vendor: Teclast   Model: CoolFlash         Rev: 0.00
 Type:   Direct-Access                      ANSI SCSI revision: 02
Dec 31 17:00:06 nlmt user.notice kernel:   Vendor: Teclast   Model:
CoolFlash SCSI device sda: 1007616 512-byte hdwr sectors (516 MB)
       Rev: 0.00
Dec 31 17:00:06 nlmt user.notsda: Write Protect is off
sda: assuming drive cache: write through
ice kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
Dec 31 17:00:06 nlmt user.notice kernel: SCSI device sda: 10076SCSI
device sda: 1007616 512-byte hdwr sectors (516 MB)
16 512-byte hdwr sectors (516 MB)
Dec 31 17:00:sda: Write Protect is off
sda: assuming drive cache: write through
 sda:06 nlmt user.notice kernel: sda: Write Protect is off
Dec 31 17:00:06 nlmt user.debug kernel: sda: Mode Sense: 00 00 00 00
Dec 31 17:00:06 nlmt user.err kernel: sda: assuming drive cache: write through
Dec 31 17:00:06 nlmt user.notice kernel: SCSI device sda: 1007616
512-byte hdwr sectors (516 MB)
Dec 31 17:00:06 nlmt user.notice kernel: sda: Write Protect is off
Dec 31 17:00:06 nlmt user.debug kernel: sda: Mode Sense: 00 00 00 00
Dec 31 17:00:06 nlmt user.err kernel: sda: assuming drive cache: write through
Dec 31 17:00:06 nlmt user.info kernel:  sda:
 sda1
sd 0:0:0:0: Attached scsi removable disk sda
Dec 31 17:00:06 nlmt user.info kernel:  sda1
Dec 31 17:00:06 nlmt user.notice kernel: sd 0:0:0:0: Attached scsi
removable disk sda
Dec 31 17:00:06 nlmt user.debug kernel: usb-storage: device scan complete



Welcome to the Erik's uClibc development environment.
nlmt login: root
Dec 31 17:00:29 nlmt auth.info login[203]: root login on 'ttyS0'
Dec 31 17:00:29 nlmt daemon.info init: init: process '/sbin/getty -L
ttyS0 115200 vt100' (pid 203) exited. Scheduling for restart.
Dec 31 17:0


Welcome to the Erik's uClibc development environment.
nlmt login

[Buildroot] Login exited

[Hamish Moffatt]

I've dropped the Cc to the busybox list and vda as it's unlikely to be a
busybox fault.

On Thu, Sep 04, 2008 at 11:49:38PM +0800, Steven Woody wrote:
> On Thu, Sep 4, 2008 at 10:29 PM, Hamish Moffatt <hamish@cloud.net.au> wrote:
> > I didn't see your posting. Do you get a prompt? Do you get any messages
> > at all after the kernel loads, loads the RAM disk, etc? Please post the
> > whole log.
> >
> > No I don't see how the root file system being read-only would be
> > significant. cramfs is always read-only. I build cramfs here with
> > buildroot and it works just fine.
> >
> > Hamish
> 
> Hi, Hamish
> 
> Below are the whole boot message, and I like to say sorry to other
> peoples here for the reposting.

Hi Steven,

I didn't see anything significant in the logs. It was badly line-wrapped
by gmail which didn't help - I suggest attaching a log file instead of
pasting it in in future. Thanks.

So what of my questions above?
> > I didn't see your posting. Do you get a prompt? Do you get any messages
> > at all after the kernel loads, loads the RAM disk, etc? 

Do you have a full log of the session where you booted with
init=/bin/sh?


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

[Buildroot] Login exited

[Steven Woody]

Hi, All

I am now pretty sure that is the ash (as busybox applet) exited
somewhere in the function ash_main(...).  I got know this by inserted
many debug messages in the source of getty.c run_shell.c and ash.c.

And, I  attached my boot messages you for analysis, please check it
out. One file is for normal boot, another is for boot with
"init=/bin/sh". I will provide some other related information about my
build process, but because the message size limits for the list. I
have to post them in many other successive messages. Please check them
out too.

PS.  I just noticed, there is an error line when I run 'make' to get
my rootfs image, it is:
 ...
 rootdir=/root/buildroot/project_build_arm/uclibc/root
 table='target/generic/mini_device_table.txt'
 /root/buildroot/build_arm/cramfs-1.1/mkcramfs: invalid option -- l
 rm -f /root/buildroot/project_build_arm/uclibc/.fakeroot*

I checked, there is no a -l option for mkcramfs, but the buildroot
does try to use it.  Anyway, the cramfs is created successfully, but I
am not sure it is not a problem.



Regards,
narke
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boot-msg.log
Type: application/octet-stream
Size: 4847 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080905/f48ba68a/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boot-msg-with-init=bin-sh.log
Type: application/octet-stream
Size: 4588 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080905/f48ba68a/attachment-0001.obj 

[Buildroot] Login exited

[Hamish Moffatt]

On Fri, Sep 05, 2008 at 03:38:31PM +0800, Steven Woody wrote:
> PS.  I just noticed, there is an error line when I run 'make' to get
> my rootfs image, it is:
>  ...
>  rootdir=/root/buildroot/project_build_arm/uclibc/root
>  table='target/generic/mini_device_table.txt'
>  /root/buildroot/build_arm/cramfs-1.1/mkcramfs: invalid option -- l
>  rm -f /root/buildroot/project_build_arm/uclibc/.fakeroot*
> 
> I checked, there is no a -l option for mkcramfs, but the buildroot
> does try to use it.  Anyway, the cramfs is created successfully, but I
> am not sure it is not a problem.

-l is for a little endian file system, so if it's producing a file
system with the wrong endianness, yes that's a big problem.

I'm assuming your target is little-endian. (By the way the
buildroot.config you attached to the next message was actually some sort
of configure log, not a buildroot configuration - so I couldn't check
that).

Your mkcramfs build must have got wrong, or you're missing the patches
or something. Specifically you must have
target/cramfs/cramfs-02-endian.patch - it's dated 2005 so I can't
believe it's just a case of an old version.

Can you check if you have that patch? Perhaps you can "make
cramfs-dirclean", then make again, and if you still see the problem then
post a build log from "make cramfs-dirclean cramfs".

It's unfortunate that mkcramfs doesn't bomb out when passed invalid
options..


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

[Buildroot] Login exited

[Steven Woody]

On Fri, Sep 5, 2008 at 9:09 PM, Hamish Moffatt <hamish@cloud.net.au> wrote:
> On Fri, Sep 05, 2008 at 03:38:31PM +0800, Steven Woody wrote:
>> PS.  I just noticed, there is an error line when I run 'make' to get
>> my rootfs image, it is:
>>  ...
>>  rootdir=/root/buildroot/project_build_arm/uclibc/root
>>  table='target/generic/mini_device_table.txt'
>>  /root/buildroot/build_arm/cramfs-1.1/mkcramfs: invalid option -- l
>>  rm -f /root/buildroot/project_build_arm/uclibc/.fakeroot*
>>
>> I checked, there is no a -l option for mkcramfs, but the buildroot
>> does try to use it.  Anyway, the cramfs is created successfully, but I
>> am not sure it is not a problem.
>
> -l is for a little endian file system, so if it's producing a file
> system with the wrong endianness, yes that's a big problem.
>
> I'm assuming your target is little-endian. (By the way the
> buildroot.config you attached to the next message was actually some sort
> of configure log, not a buildroot configuration - so I couldn't check
> that).
>
> Your mkcramfs build must have got wrong, or you're missing the patches
> or something. Specifically you must have
> target/cramfs/cramfs-02-endian.patch - it's dated 2005 so I can't
> believe it's just a case of an old version.
>
> Can you check if you have that patch? Perhaps you can "make
> cramfs-dirclean", then make again, and if you still see the problem then
> post a build log from "make cramfs-dirclean cramfs".
>
> It's unfortunate that mkcramfs doesn't bomb out when passed invalid
> options..
>
>
> Hamish
> --
> Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
>

Yes Hamish, I do have target/cramfs/cramfs-02-endian.patch. And when I
run 'file' command on the generated cramfs image, it reported that the
image is a little-endian.

Anyway, after I rebuit the cramfs using 'make cramfs-dirclean cramfs'
as you suggested, I did not get the warning about the '-l' option any
more. But that makes no difference, the newly generated rootfs image
still does not let me login as before.

Attached is the buildroot .config file.


Oh,  god ....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: buildroot.config
Type: application/octet-stream
Size: 16794 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080907/8242d040/attachment-0001.obj