Summary of Fedora bootloading bugs:
BIOS, preexisting Windows: reliably has a working boot entry created.
For other combinations all bets are off:
BIOS or UEFI, preexisting Linux using LVM: boot entries not created
because preexisting OS's LV's aren't activated by the installer, so
os-prober/grub2-mkconfig don't find the preexisting OS. Two year old
bug, finger pointing, no agreement on who should fix it.
UEFI, preexisting Windows:, boot entry either not created for Windows
or it doesn't work.
## Year old bug.
## This bug was
rejected as an F20 blocker on the basis that the release criteria for
Windows only applies to BIOS.
UEFI, preexisting Linux no-LVM: boot entry does not work. This is a
Fedora GRUB specific bug, over a year old, was rejected for freeze
exception so it stands to reason it would have been rejected as a
blocker as well.
UEFI, preexisting OS X: boot entries don't work, have never worked for
me in 3+ years. Two 18 month old bugs.
## Kernel panic
might now be fixed by upstream, but upstream's solution is flaky and
prone to breakage every time Apple makes a kernel change. Upstream
insists on using their own bootloader rather than Apple's for unknown
## Described fix by
adding GRUB xnu modules to grubx64.efi has not been implemented.
Secondary problem is that there are two superfluous entries that don't
work due to confusion resulting from Fedora's mactel-boot support
(os-prober thinks the Fedora boot entries are an OS X installation).
Am I alone in thinking we should block final on all of these? We're
delayed so much already that it seems like it might be best to take care
of these once and for all. Especially if we are going to pretend that
Fedora is a good alternative to Mac; we should not pretend that if we
cannot boot on Macs.
A nonfunctional installer is a really big problem. At the worst, the
installer should be able to detect these situations in advance and warn