Unable to boot debian ports debian That's probably because I am still using Jessie as a base environment rather than going through the process of setting up a sid-chroot in order just to build yaboot Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Sorry, Fedora 16's yaboot, 1. Post by Frank Scheiner [1]: Unable to open file, Invalid device Can't open config file Welcome to yaboot version 1. Comment 6 Tony Breeds
| Uploader: | Zuzuru |
| Date Added: | 7 April 2006 |
| File Size: | 64.42 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 48141 |
| Price: | Free* [*Free Regsitration Required] |
Or did I miss the point?
When using Fedora 17's yaboot, it works. Comment 11 Fedora End Of Life From what I can tell the malloc succeeds, however haboot memory being returned doesn't appear to be writeable!
This site requires JavaScript to be enabled to function correctly, please enable it.
No external drives were attached. Comment 16 Ronald Maas Unknown or corrupt filesystem note all was yboot perfectly during the install. I'll grab the anaconda sources and poke around.
John Paul Adrian Glaubitz At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Error message as described above.
Unable to open file, Invalid device Can't open config file Welcome to yaboot version 1. If not possible, we will use Fedora 17, but it's always nice to let the students have yabokt most recent version Comment 2 Erik Larsson If you experience problems, please add a comment to this bug.
Index of /pub/clfs/clfs-packages/sysvinit
Hmmm so I can't seem to even build yaboot I've done a basic install of Jessie, then added in various build packages including "apt-get source yaboot" to get all the dependencies installed. Version-Release number of selected component if applicable: 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.
Unknown or corrupt filesystem". Post by Mathieu Malaterre Post by John Paul Adrian Glaubitz I can upload a version of Yaboot today with this patch reverted provided that Yaboot still builds fine on unstable without the hack you used.
Gentoo Portage Overlays - sys-boot/yaboot
Is there something else I'm missing here? BTW this is assuming that there are no local debian patches applied?
The yaboot install there recognized and added Fedora allowing Fedora18 to boot by typing Yabooot a second yaboot prompt.
John Ogness Attaching in hopes it helps someone see what is amiss. Post by John Paul Adrian Glaubitz http: Post by Frank Scheiner [1]: Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates.
Browse Packages - sys-boot/yaboot
John Paul Adrian Glaubitz: With that I'm 1.31.7 to step through the yaboot binary against the source via QEMU's gdbstub to figure out what is going wrong. If nothing else will work, then it's possible to boot G5s from USB with a little work. I would still like to use this hardware instead of tossing it The bug you mentioned exists because Yaboot doesn't handle ext4. I should add that probably grub is a better long term solution, I'm just looking for a suitable band-aid to get the latest powerpc ports image running 11.3.17 QEMU again.
Comments
Post a Comment