[BusyBox] no shell after booting
Nick Popoff
busybox at tre.bloodletting.com
Tue Nov 26 17:21:03 UTC 2002
mitu at qmx.de wrote:
> but then there is only one message more:
> "Freeing unused kernel memory 64k freed"
I could be wrong about this, but I think this is the last message
printed by the Linux kernel before execution is handed off to /sbin/init
and userland. Very very often when problems occur this is the last line
to appear. In my experience it points to a bad /sbin/init, bad C
library in /lib, or Linux is unable to find the filesystem to run
/sbin/init.
When I built my first Busybox system I banged my head against exactly
this for several days before realizing I was using a i686 libc on a i486
and /sbin/init was not running because of it. Thus... dead system with
"memory freed..." as the last output. I replaced the library with an
unoptimized libc and it worked fine.
This seems like a potential FAQ... I know I see this question all time
time on this and other Linux mailing lists.
More information about the busybox
mailing list