I do not believe yaboot has in active development in a long time
upstream. The last set of commits were in 2008 see:
I think we are just stuck with make a separate ext2 /boot partition.
On Wed, Oct 12, 2016 at 12:02 PM, ernsteiswuerfel <erhar...@mailbox.org> wrote:
> Yes, Xenials daily iso of yesterday also worked.
> I even tried to get this upstream via yaboot-de...@lists.ozlabs.org as
> stated on https://lists.ozlabs.org/listinfo/ but there my message sits
> waiting to get approved by the list moderator since 2 weeks...
> May I bring this downstream bug reports to your attention:
> Seems yaboot 'lost' the ability to boot into current (newly formatted)
> ext4 partitions. Booting into ext2 partitions still works.
> You received this bug notification because you are subscribed to the bug
> unable to boot after 'entire disk' install (16.10, ppc)
> Status in yaboot package in Ubuntu:
> Status in yaboot package in Debian:
> Bug description:
> Just did an entire disk install from todays (24.07.2016) Yakkety
> daily. Installation procedure went fine, but the automatically created
> /etc/yaboot.conf seems faulty.
> 1st stage-boot runs fine, the boot options are displayed correctly,
> pressing "L" leaves me at the 2nd stage boot prompt where you can
> choose between "Linux" and "old" boot options. But either of them does
> not work, throwing the error message:
> "/pci@f4000000/ata-6@d/@0:3,/boot/vmlinux: unknown or corrupt
> To rule out other issues I did an openfirmware reset, wiped /dev/sda
> and tried a second time with a fresh mac partition table. But the
> problem stays the same, 16.10 is not bootable on my PowerBook 5,6. It
> did run 16.04 before.
> Partition layout is the standard created by "entire disk" install,
> /dev/sda4 is swap.
> /dev/sda2: LABEL="bootstrap" TYPE="hfs" PARTLABEL="untitled"
> /dev/sda3: UUID="b7bdb9a4-7316-4966-aa65-1d546b211204" TYPE="ext4"
> ## yaboot.conf generated by the Ubuntu installer
> append="quiet splash"
> append="quiet splash"
> ProblemType: Bug
> DistroRelease: Ubuntu 16.10
> Package: yaboot 1.3.16-4ubuntu1
> ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13
> Uname: Linux 4.4.0-31-powerpc-smp ppc
> ApportVersion: 2.20.2-0ubuntu1
> Architecture: powerpc
> CasperVersion: 1.376
> CurrentDesktop: MATE
> Date: Mon Jul 25 00:19:21 2016
> LiveMediaBuild: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha powerpc (20160724)
> PATH=(custom, no user)
> SourcePackage: yaboot
> UpgradeStatus: No upgrade log present (probably fresh install)
> To manage notifications about this bug go to:
You received this bug notification because you are a member of Ubuntu
PowerPC Architecture Team, which is subscribed to yaboot in Ubuntu.
unable to boot after 'entire disk' install (16.10, ppc)
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~ubuntu-powerpc
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~ubuntu-powerpc
More help : https://help.launchpad.net/ListHelp