Description of problem: Installing Fedora 18 on a PowerPC Mac G5, after the successful installation, during the first reboot, the secondary boot program (yaboot) reports "/ht@0,f20000000/pci@7/k2-sata-root@0/disk@0:3,vmlinuz-3.6.2-2.fc18.ppc64: Unknown or corrupt filesystem". Adding a "device=hd:" to the /boot/etc/yaboot.conf file allows the system to boot normally. Version-Release number of selected component (if applicable): yaboot-1.3.17-6.fc18.ppc How reproducible: Always. Steps to Reproduce: 1. Install F18 ppc64 (any nightly) on Mac G5 2. Reboot Actual results: Error message as described above. Expected results: Successful boot Additional info: The yaboot 1.3.17-2 (from Fedora 16) works fine to boot Fedora 17. The patch files for -6 appear to have added link_with_new_e2fsprogs patches that might contain the problem.
I can confirm this on my PowerMac G5 Quad. yaboot fails to access the ext4 boot partition where the kernel and boot files reside after installing Fedora 18. When using Fedora 17's yaboot, it works.
(In reply to comment #1) > I can confirm this on my PowerMac G5 Quad. yaboot fails to access the ext4 > boot partition where the kernel and boot files reside after installing > Fedora 18. When using Fedora 17's yaboot, it works. (Sorry, Fedora 16's yaboot, 1.3.17-2.fc16.)
I have also encountered the same problem on a PowerMac Quad G5. It would be great if this issue could be solved as we use Fedora on Quad G5 in university courses on performance programming in Lund (Sweden) starting mid March (two courses, one on C/computer architecture/tuning and the other on multicore --- both courses with focus on the Power architecture). If not possible, we will use Fedora 17, but it's always nice to let the students have the most recent version...
Created attachment 696676 [details] yaboot.conf created by Fedora18 install fails boot as in bug title editing this yaboot so: boot=/dev/sda2 instead of /dev/sdb2 and add a line: device=hd: resolves the issue. Install on G5 PowerPC 1.6 Ghz from dvd in superdrive to single internal SATA hard drive. No external drives were attached.
Created attachment 696678 [details] yaboot.conf created by installing Debian 7 next to Fedora18 In sussing this, I installed Debian 7 in free space next to Fedora18. The yaboot install there recognized and added Fedora allowing Fedora18 to boot by typing Fedora a second yaboot prompt. This yaboot.conf shows full open firmware path to devices. Attaching in hopes it helps someone see what is amiss.
I'm not familiar with what tool is generating the yaboot.conf at install time. I'll grab the anaconda sources and poke around. Either way to actually fix this will require a rebuild of the ISO. But we can certainly find a work around.
Does anyone know how to fix this error? I install Fedora 18 successfully but cannot boo afterwards. How do we need the yaboot.conf if we cannot mount it in a live cd? Is their a workaround at the yaboot command prompt that we could do as well?
I have the identical problem, adding the line: device=hd: in /etc/yabbot.conf in rescue session from cdrom boot solves the problem. Is this fixed in F19?
The same issue is present in Fedora 20 Beta, which contrary to documentation still installs yaboot as boot loader (I expected GRUB).
After installing Fedora 20 on a Late 2005 PowerMac G5, I encountered similar problem in Yaboot. In my case I needed to add the following line in /boot/etc/yaboot.conf: device=sd0: # when hard disk is installed in top drive bay or device=sd1: # when hard disk is installed in bottom drive bay Detailed instructions to fix yaboot.conf: 1) Boot from blessed Fedora 20 beta PPC64 CD (see bug report https://bugzilla.redhat.com/show_bug.cgi?id=1020112 to download) 2) At GRUB2 boot prompt, enter 'e', append 'rescue' to the linux command line, press Ctrl-X to continue booting 3) Let Anaconda mount partitions on /mnt/sysimage 4) Open command prompt and run: chroot /mnt/sysimage 5) Use vi to update /boot/etc/yaboot.conf by adding device=sd0: or device=sd1: 6) ybin -v -C /boot/etc/yaboot.conf 7) exit 8) reboot
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
still present, moving to F-20
booted f20 went through a whole two hour net install. All seemed OK with the install with fedora 20... and nothing: I get "unknown or corrupt filesystem": /ht@0,f20000000/pci@5/k2-sata-root@c/k2-sata@0/disk@0:3,vmlinuz-3.12.6-300.fc20.ppc64: Unknown or corrupt filesystem note all was working perfectly during the install. but upon first boot I got that error message Mac G5, SMP is the machine
now i cant boot off of the cd, nor any other media. Please help. I would still like to use this hardware instead of tossing it... all $2k of it. Ugh.
(In reply to Elmo from comment #14) > now i cant boot off of the cd, nor any other media. Please help. I would > still like to use this hardware instead of tossing it... all $2k of it. Ugh. If you can't boot off any media, the problem surely lies elsewhere. Investigate the state of the boot media, and the usability of your DVD drive. If nothing else will work, then it's possible to boot G5s from USB with a little work. Google will help you with the details...
Elmo, Never experienced this myself as I always was able to boot from CD even after PowerMac fails to boot the F20 from hard drive. You may try resetting the PRAM / NVRAM routine as described in http://support.apple.com/kb/ht1379 (you may need to try it a few times) Another option is to access Open Firmware prompt and boot CD from there (use your Google fu)
Following "Ronald Maas 2013-11-25 23:33:31 EST" post worked for me. Thanks all, and now I have a fully installed system.
Confirming bug and fix with F20 PPC final. Easy to fix, please do in F21. Just a one-line change. The fix is per Terje Røsten above, but with minor additions / corrections / augmentations: device=hd: (for internal SATA disks) device=ud: (for external USB disks) device=fw: (for external Firewire disks) These labels are visible in Open Firmware via 'devalias' command input. The actual yaboot file is /boot/etc/yaboot.conf while /etc/yaboot.conf is a mere symlink. The necessary changes for F20 can indeed be made from the F20 install CD using system rescue boot mode. The device line belongs in the global section above the yaboot menu item entry/ies.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.