Red Hat Bugzilla – Bug 157771
yaboot, Cann't load "second stage bootstrap"
Last modified: 2007-11-30 17:11:06 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; ja-jp) AppleWebKit/312.1 (KHTML, like Gecko) Safari/312 Description of problem: I completed install fc4t3-ppc on PowerMac G3 B&W. After reboot system. yaboot cann't load "second stage bootstrap". Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Install fc4t3. 2.reboot Additional info:
Can you boot into OF (cmd option O F) printenv boot-device
Sorry, Already I Installed Yellow Dog Linux 4 into HDD. Now I executed printenv command. Here is output message. 0 > printenv boot-device ------------ Partition: common -------- Signature: 0x70 ---------------- boot-device /pci@80000000/pci-bridge@d/pci-ata@1/@0/disk@0:2,¥¥:tbxi hd:,¥¥:tbxi ok 2month ago, I succeeded in installation of "Unofficial Fedora Core 3 PPC". I can boot kernel.
Can I assume it actually reads \\ rather than ¥¥ - eg hd:,\\:tbxi If yellow dog can boot the machine using yaboot, we should be able to. If you've overwritten the install which will have updated the nvram I can't really diagnose this. If fc3 worked and ydl worked I can't see why fc4t3 would have failed, could you try another install?
> If you've overwritten the install which will have updated the nvram I can't really diagnose this. I think so. > could you try another install? When I have time, I will try installation of fc4t3.
I believe this to be a duplicate of 157771 which can be worked around by setting to boot off the yaboot binary. I believe this to be an issue with your OF version and the ofboot.b script. Please ensure you are running most recent firmware update and note your firmware version in the bug http://docs.info.apple.com/article.html?artnum=86117 Please can you attach a listing of yellowdog's boot partition: mount -t hfs /dev/hda2 /mnt ls /mnt Could you also attach their ofboot.b script.
Correction related bug #158026 I'm closing this one as the other one has more debugging, please add details requested above to that bug. *** This bug has been marked as a duplicate of 158026 ***