busybox sh does not run and cannot login when eabi enabled

Denys Vlasenko vda.linux at googlemail.com
Sun Jan 8 21:41:55 UTC 2012


On Sunday 08 January 2012 22:24, cytan299 at netzero.net wrote:
> Hi guys,
>    I have successfully compiled (using buildroot-2011.11.tar.gz), linux-2.6.39.4, busybox-1.19.3 with OABI and all the scripts in init.d/rcS runs fine and I can log into my embedded system.
> 
>    However, when I eabled EABI in buildrroot, I can no longer log into my embedded system. My suspicion is that /bin/sh is somehow not running because:
>        (a) the rcS scripts which echo to stdout don't do so anymore (unlike in the OABI compiled system). And setting an echo in rcS does not print out anything.
>        (b) setting up inittab so that on ttySAC0 start and login, I can see messages. Here's the messages when I try to login as root before being bumped out (no password prompt is even shown!). And yes, securetty has ttyAMA0 entry.
> ------------------------------------------------------------------
> Dec 31 17:00:10 Hammer auth.info login[776]: root login on 'ttyAMA0'                                               
> Dec 31 17:00:10 Hammer daemon.info init: process '/sbin/getty -L ttySAC0 115200 vt100 ' (pid 776) exited. Scheduli.
> Dec 31 17:00:10 Hammer daemon.info init: starting pid 789, tty '/dev/ttySAC0': '/sbin/getty -L ttySAC0 115200 vt10'
> Dec 31 17:00:11 Hammer daemon.info init: process '/usr/bin/tail -f /var/log/messages' (pid 779) exited. Scheduling.
> Dec 31 17:00:11 Hammer daemon.info init: starting pid 790, tty '/dev/ttySAC0': '/usr/bin/tail -f /var/log/messages'
> ----------------------------------------------------------------------
> 
> 
>        (c) replacing /linuxrc which points to /bin/busybox to a shell script does not echo or do anything.
> 
>        (d) Using rootfs that was compiled with oabi enabled *BUT* using linux compiled with eabi, I have no problems logging in.
> 
> I'm at a loss as to what's going on. Any help appreciated.

Somewhat relevant: http://busybox.net/FAQ.html#init

If you pass "hello world" step, try booting with init=/bin/sh,
where /bin/sh is a link to busybox binary. Does that work?

-- 
vda


More information about the busybox mailing list