For debugging or single user purposes you do not need to run init or
have an inittab.
There have been several sugestions that there may be a hardware
problem - there are a number that are possible.
I was stalled here for some time because my UartDriver was
accidentally using the physical IO address instead of the virtual one
and I had created a temporary phys=virtual entry in the tbl that was
conveniently getting blow away just here.
You can try to isolate your problem by changing your boot ramdisk
(inramfs or initrd)
Eliminate or rename /init /sbin/init /linuxrc and any of the other
permutations that linux tries to execute in init/main.c they are all
listed very near where you stopped.
make sure you have /bin/sh
reboot on that ramdisk if you have an "init" related problem then
you should get a standalone shell.
If you have a hardware problem you will likely still stop at the
same place.
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii at dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too
numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
