Yaboot does not set correct OF path on PowerMac 9.1 (G5 tower single).

Bug #32295 reported by globetrotterdk
This bug report is a duplicate of:  Bug #18474: ofpath handles SATA disks incorrectly. Edit Remove
6
Affects Status Importance Assigned to Milestone
yaboot (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Yaboot does not set the correct OpenFirmware path on my PowerMac 9.1 (G5 tower single). I install (K)Ubuntu on my first SATA drive. OS X resides on SATA drive #2. This bug is present in both Breezy and in Dapper Flight 3 & 4 and in both Kubuntu and Ubuntu.

Revision history for this message
globetrotterdk (globetrotterdk) wrote :

This is still an issue with Ubuntu Dapper Flight 5. I am surprised that this bug still has the status of "unconfirmed".

Revision history for this message
Colin Watson (cjwatson) wrote :

Please attach a tarball of /proc/device-tree to this bug. Thanks.

Changed in yaboot:
status: Unconfirmed → Needs Info
Revision history for this message
globetrotterdk (globetrotterdk) wrote :

Despite Ubuntu being my favorite distro, I no longer have it installed as there was no reply to this bug for a very long time. Here is part of a posting on Ubuntu Users:

> Hi Larry,
>
> Nice to hear from you again. I have the yaboot.conf issue solved, Here was the solution for that:
>
> ofpath /dev/sda
> /ht@0,f2000000/pci@3/k2-sata-root@c/k2-sata@0/disk@0:
>
> ofpath /dev/sdb
> /k2-sata@0/disk@0:
>
> sudo mv /usr/sbin/ofpath /usr/sbin/ofpath.orig
>
> cd /usr/sbin
>
> sudo wget -P . http://people.redhat.com/pnasrat/ofpath
>
> chmod 755 ofpath

Ah, so the problem was with the ofpath binary distributed by Ubuntu? Hopefully Dapper gets a less buggy version. Did you file this bug on Malone, along with your solution?

> sudo ofpath /dev/sda
> /ht@0,f2000000/pci@3/k2-sata-root@c/k2-sata@0/disk@0:
>
> sudo ofpath /dev/sdb
> /ht@0,f2000000/pci@3/k2-sata-root@c/k2-sata@1/disk@0:
>
> sudo ybin -v
>
> Unfortunately, I haven't figured out how to get yaboot to boot default into OS X yet. I tried "default=macosx", but no luck.

You might check the yaboot manpage and see if it is possible to use an open firmware path in the "default=..." line. The "default" option may work if you can specify an of path rather than use the shorthand "macosx".

> With regards to the kernel issue, I see two possibilities as I believe we have talked about before:
>
> 1) The patch that you are talking about. I don't know what the patch would be called. Maybe something with windfarm_9.1.

Revision history for this message
Colin Watson (cjwatson) wrote :

This bug has been fixed in Dapper, and will be part of the next milestone release (it was too late for Flight CD 6). See the bug of which this bug is marked as a duplicate for more information.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for yaboot (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.