Bug#270321: kernel-image-2.6.8-powerpc: PReP boot failure
On Wed, Sep 08, 2004 at 09:10:50PM -0500, Hollis Blanchard wrote:
> On Sep 7, 2004, at 1:29 PM, Jens Schmalzing wrote:
> >
> >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
Well, this seems the same error that Jens is also getting. The kernels get
loaded, the initrd also, and it is when the initrd tries to mount the root
filesystem to pivot_root to it, that there is the problem, altough i am not
happy with this error message, it used to be something else.
Could you edit /etc/mkinitrd/mkinitrd.conf (before creating the initrd when
installing the kernel) and set DELAY to 10 or so. Then you can interrupt the
initrd loading and come up in a real shell (don't remember if you have fbdev
console or something though, so this may be on the serial console), and
investigate a bit more.
Friendly,
Sven Luther
Reply to: