[Debootloaders-yaboot] Bug#641215: linux-image-3.0.0-1-powerpc: After pata_macio replaced ide_pmac the system doesn't boot

[Cyril Hrubis]

> > * The second problem is that yaboot fails to boot after this change
> 
> What do you mean by "yaboot fails to boot"? At which point the boot
> procedure failed? What did you see on the screen? Did you get the yaboot
> prompt at all? If you did, what happened after that? Did you get a shell
> prompt?

Sorry the description would better be that the kernel failed to find rootfs so
the booting stops in the initramfs (again). 

> > 
> > Which is strange as the dist is identified by UUID in the yaboot conf.
> > 
> > Similar workaround for yaboot:
> > 
> > mount -t ext3 /dev/sda3 /root/
> > mount -t proc none /root/proc
> > mount -o loop /dev /root/dev/
> > chroot /root/ /bin/bash
> > # change root to /dev/sda3 in /etc/yaboot.conf
> > ybin -v
> > Ctrl+d
> > reboot
> > 
> > After this the system boots fine.
> 
> 
> What the yaboot.conf looked like before you changed it? Try to change it
> back and run 'ybin -v'. Is it working fine?

Strange it seems to work now.

The rootfs lines looked like:

# root = /dev/hda3
root = "UUID=58...."

I've chaged that to:

root = /dev/sda3
# root = "UUID=58...."

And did ybin -v and it booted.

Changing it back and doing ybin -v again doesn't seem to break things now.

cat /proc/cmdline after changing things back shows:

root="UUID=58...." ro

> I was not able to reproduce this problem on my PowerBook G3. Can you
> reproduce this "yaboot" problem again? How do you do it?

Sorry, couldn't reproduce anymore.

> If you do, what 'cat /proc/cmdline' shows? What 'ls -l
> /dev/disk/by-uuid' shows?

All seems to be in place now. The /proc/cmdline shows root="UUID=58..." ro and
ls /dev/disk/by-uuid shows to UUID and one of them match the root kernel
parameter.

> What happens if you type "old" at the yaboot prompt after the upgrade?

Before changing yaboot back to root = "UUID=58..." the boot failed as the
kernel was unable to mount rootfs. After root was set back to the UUID both old
(2.6.39-2) and the current (3.0.0-1) boots fine (tried several times). So this
must have been some temporal glitch.