Re: Problems at booting

[Craig Hollabaugh <craig@hollabaugh.com>]

On Wed, 2005-12-21 at 14:05 +0100, Paula Saameño wrote:
> INIT: version 2.86 booting
> /etc/init.d/rcS:
> INIT: Entering runlevel: 2
> INIT: Id "1" respawning too fast: disabled for 5 minutes
> INIT: Id "3" respawning too fast: disabled for 5 minutes
> INIT: Id "2" respawning too fast: disabled for 5 minutes
> INIT: Id "5" respawning too fast: disabled for 5 minutes
> INIT: Id "4" respawning too fast: disabled for 5 minutes
> INIT: Id "6" respawning too fast: disabled for 5 minutes
> INIT: Id "T0" respawning too fast: disabled for 5 minutes
> INIT: no more processes left in this runlevel


> 1:2345:respawn:/sbin/getty 38400 tty1
> 2:23:respawn:/sbin/getty 38400 tty2
> 3:23:respawn:/sbin/getty 38400 tty3
> 4:23:respawn:/sbin/getty 38400 tty4
> 5:23:respawn:/sbin/getty 38400 tty5
> 6:23:respawn:/sbin/getty 38400 tty6


Paula,

It looks like your getty is not running correctly (maybe a lib or bin
problem). Do you have a statically linked shell, like ash, on your
system? Get that running first with

7:23:respawn:/bin/ash

then in ash
run the getty to see the error that keeps it from running. 

Running a statically linked shell helps to get your system up with
having to rely upon libraries and linker.

You can also pass ash on the kernel command line from your bootloader to
avoid running /sbin/init altogether.

kernel root=/dev/??? init=/bin/ash ro

Hope that helps.

Craig



-- 
------------------------------------------------------------
Dr. Craig Hollabaugh, craig@hollabaugh.com, 970 325 0509
Author of Embedded Linux: Hardware, Software and Interfacing
www.embeddedlinuxinterfacing.com