On Sun, 25 Aug 2019 09:32:22 -0700
Lonni J Friedman <netllama(a)gmail.com> wrote:
OK, i filed a bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1745355
All of the work arounds in the Centos bug are for people who have
already installed the OS, but can no longer boot it. I can't even
install Fedora. I'd have to somehow edit the install image, and
rebuild it to attempt those work arounds. That's significantly more
effort than I'm willing to put forth to install an OS. I'll just
install a different Linux distro, and move on with my life.
A caveat. Other distros will work if they have either the patched new
version (unlikely, if not CentOS), or the old version. The good news
is that if it is using the old version, if / when they update to the
latest version, you will know what to do when your system no longer
boots.
What I got from the workaround thread is that old macs can't use uefi.
So, if you get the fedora netinstall image, and choose legacy boot (MBR)
during the install, it should install and boot just fine. The same
should be true for any other distro. Then this problem won't happen in
the future, regardless of what the distro does with uefi.
I am not familiar enough with macs to know if they have a bios setting
that tells the system to boot in non-uefi mode. If they do, you should
be able to boot the F30 image as non-uefi, and have no issues, because
it isn't possible to install a uefi system from a non-uefi boot. The
images default to uefi because that is best for new systems. When I
booted the netinstall image, I hit the Del or F2 key, got to the
firmware boot menu screen, and was able to explicitly select legacy
boot for the image. You could try that before going to the trouble of
downloading a new image.