Hollis Blanchard writes:
Does this mean the ramdisk is bad?
Could well be. You can check its contents with 'fsck.cramfs -v /initrd.img'.
The ramdisk seems ok, at least fsck does not complain.
Any way I can get some debug output from it?
On the serial console? Put console=ttyS0 last in the kernel command line. Then /dev/console will point to the serial console, and you will get all console output, not only the kernel messages.
Here's what I got:
...
Freeing unused kernel memory: 164k init 60k pmac 4k chrp 8k openfirmware
initrd-tools: 0.1.74
NET: Registered protocol family 1
pivot_root: No sKernel panic: Attempted to kill init!
uch file or dire ctory
/sbin/ini<0>Rebooting in 180 seconds..t: 426: cannot open dev/console: No such file
For the record, root/dev/console does exist in the ramdisk.
The gzipped /boot/initrd.img-2.6.8-powerpc is 0x48e74e bytes, and we can see from the bootloader output that all of those bytes were found...
-Hollis
