Bootin beagle board and Angstrom

HI thanks for the help I am new on Beagleboard

I want to test the latest Kernel from

make -j5 ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap2plus_defconfig
make -j5 ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage

boot args

setenv bootargs console=ttyO2,115200n8 noinitrd root=/dev/mmcblk0p2
rootfstype=ext2 rw rootdelay=1 nohz=off

it boots fine with the FS from google code

ALSA-FS.tar.gz Busy Box Filesystem with ALSA libraries

but when i tried to boot with Angrstrom FS from

it hangs on

Starting Dropbear SSH server: dropbear.
Starting advanced power management daemon: No APM support in kernel
Starting syslogd/klogd: done
* Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
INIT: Id "S" respawning too fast: disabled for 5 minutes

and nothing happen

Am I doing something wrong ?

Should I change something on the default configuration ??

I have tested the same set up with the uImage that comes with the tar
ball from Narccisus and it works perfect

Thanks a lot for your help


Victor Rodriguez

I don't use the specific binaries you are so what I'm about to suggest
is based on common knowledge of how these things work.

First, the make target you use is unfamiliar to me. So far I've only
used omap3_beagle_defconfig and omap3_defconfig. I'm using a C4 board.
It's possible the kernel you built is not appropriate for your board
because you used a configuration intended for a different board. It
won't hurt to try one of the ones I use, just to see if it helps.

INIT: Id "S" respawning too fast: disabled for 5 minutes

You can mount the image on a Linux box and look at etc/inittab for an
entry that has "S" in the first column. It should also have "respawn"
in the third field. Whatever that is trying to do is failing, but the
init process is trying to restart it repeatedly. It never gets past
that during the boot process so you never get a login prompt. You have
to figure out why it isn't working, and that could be for a lot of

My complete guess here is that the single user mode boot script, which
probably runs before anything else, is dying and is causing init to be
run again (re: respawned). You'll have to look at that script and try
to figure out what its trying to do and why it is failing.

Also, the console may need to be on ttyS2 instead of ttyO2, but I
vaguely remember someone saying it changed from "S" to "O" recently. I
still use S2 and it works for me.

... >= 2.6.37 will need tty02 (unless the user goes out of their way
to patch it back..)