Ubuntu will not boot via yaboot when installed on 2nd disk on G5 (PPC)

Bug #909 reported by Joey Stanford
This bug report is a duplicate of:  Bug #18474: ofpath handles SATA disks incorrectly. Edit Remove
4
Affects Status Importance Assigned to Milestone
yaboot (Ubuntu)
Incomplete
Medium
Colin Watson

Bug Description

Ubuntu fails to load when installed on the 2nd disk of a PPC G5 computer

Ubuntu fails to load when installed on the 2nd disk of a PPC G5 computer. Yaboot incorrectly specifies the drive mapping during config. There is no way to boot, even when editing the hfs boot disk.

Revision history for this message
Malcolm Gregson (malcolm-gregson) wrote :

I have been unable to get Ubuntu to boot from my (4th) disk.
I have a copy of Mac OSX on each of my first two disks (hda,hdb), Yellow Dog on a third (hdc), and Ubuntu on a fourth (hdd).
Yaboot gives me the MacOS and Yellow Dog options, but not Ubuntu.
The only way to boot into Ubuntu is via the graphical bootloader - hold down "alt" key on startup.

My machine is a Power Mac G4 1.25 Ghz Dual Processor.

Here is my /etc/yaboot.conf file, run from Yellow Dog using /sbin/ybin -v

# yaboot.conf generated by anaconda

boot=/dev/hdc2
init-message="Welcome to Yellow Dog Linux! Hit <TAB> for boot options."
partition=6
timeout=30
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot
delay=10
enablecdboot
macosx=/dev/hda3
macos=/dev/hda3
defaultos=macosx

image=/vmlinux-2.6.10-1.ydl.1smp
 label=linux
 read-only
 initrd=/initrd-2.6.10-1.ydl.1smp.img
 root=/dev/hdc3
 append="rhgb quiet"

image=/vmlinux-2.6.10-1.ydl.1
 label=linux-up
 read-only
 initrd=/initrd-2.6.10-1.ydl.1.img
 root=/dev/hdc3
 append="rhgb quiet"

image=/boot/vmlinux-2.6.10-5-powerpc
 label=ubuntu
 read-only
 device=/dev/hdd
 partition=3
 initrd=/boot/initrd.img-2.6.10-5-powerpc
 root=/dev/hdd3

I hope this may be helpful. I should be glad to hear of any further progress.

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

Please attach a tarball of /proc/device-tree/ and say which device /boot and / are on, so that I can investigate what ofpath is doing with them.

Changed in yaboot:
assignee: nobody → kamion
Colin Watson (cjwatson)
Changed in yaboot:
status: Unconfirmed → Needs Info
Revision history for this message
Colin Watson (cjwatson) wrote :

Although this one was filed earlier, I'm going to make this a duplicate of bug 18474, as that one contains more information. If you don't have SATA disks, please un-duplicate this bug again.

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.