| Summary: | RuntimeError: Error running mkofboot: No such file or directory | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Karsten Hopp <karsten> | ||||
| Component: | lorax | Assignee: | Martin Gracik <mgracik> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 17 | CC: | bcl, dmach, g.kaviyarasu, jonathan, kmonroe, knight, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | powerpc | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:c30888e46e234aca2e78a7ec90f0fe3e72219e1462658a44e90f264aa71a70c5 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-01-20 16:21:50 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Karsten Hopp
2012-04-05 17:03:15 UTC
Created attachment 575498 [details]
File: anaconda-tb-2Q1z6a
yaboot provides mkofboot, it is a symlink to ybin, are either of those present? The yaboot.spec shows: /boot/efika.forth /sbin/ofpath /sbin/ybin /sbin/yabootconfig /sbin/mkofboot /usr/lib/yaboot/addnote /usr/lib/yaboot/ofboot /usr/lib/yaboot/yaboot /usr/lib/yaboot/yaboot.debug Are all of those there? *** Bug 811972 has been marked as a duplicate of this bug. *** We've switched to grub2 on PPC, so yaboot shouldn't be installed at all. Grub2 works fine on IBM Power systems, it is just on PowerMac where this problem shows up due to the way the firmware works. I'll try to figure out what needs to be chenged in anaconda. It can be done, as I've had reports that even G4 machines can be booted with grub2. I haven't seen this issue again for quite a while now, so we can safely assume that this has been fixed |