Red Hat Bugzilla – Bug 488936
boot fedora on g5 with fedora living on second disk
Last modified: 2009-08-14 11:49:54 EDT
Description of problem:
i have a g5 with two disks and installed fedora on the SECOND disk. installation went fine, but anaconda generates obviously an /etc/yaboot.conf without a "device="-line and therefore i was not able to boot my fresh installed fedora, as yaboot tried to find my kernel on the first disk (where macosx lives).
after booting into rescue-mode an adding the correct device-line everything works as expected.
When you did the installation, did you tell anaconda which device to write the bootloader to? Can you attach the generated /etc/yaboot.conf file?
i startet the install with video=ofonly as parameter. the installation itself went with its defaults. the bootloader itself was correctly installed, but that device-line was missing.
will take some time to get /etc/yaboot.conf from that system, as i no longer have direct access.
thanks for investigating.
the following is my yaboot.conf, which works now AFTER i added
the rest is as generated by anaconda, with one small modification (the init-message).
# yaboot.conf generated by anaconda
init-message="Welcome to MUI Fedora!\nHit <TAB> for boot options"
append="video=ofonly rhgb quiet root=/dev/VolGroup00/LogVol00"
append="video=ofonly rhgb quiet root=UUID=31453155-de1c-4a7c-b0d1-edb43f413f35"
I don't think we have the ability in the current anaconda to determine what the OF path to a disk is. I know right now we definitely do not write out a device= line under any circumstances, so it's not like we are failing to just in your case. Barring the knowledge of how to do that, I don't believe there's much we can do for you here.