On Wed, Dec 7, 2016 at 3:16 AM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > > On Tue, Dec 6, 2016, 9:47 AM Jack Howarth <howarth.mailing.lists@xxxxxxxxx> > wrote: >> >> On Sun, Dec 4, 2016 at 1:56 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> >> wrote: >> > On Sun, Dec 4, 2016 at 11:22 AM, Jack Howarth >> > <howarth.mailing.lists@xxxxxxxxx> wrote: >> >> While evaluating various Linux distributions for repurposing a >> >> MacBook Pro 2,1 as a Linux box, I was pleasantly surprised to find >> >> that not only was Fedora unique in producing a bootable disk without >> >> resorting to the presence of an OS x partition with eEFind, but that >> >> it was unique in being about to boot the x86_64 linux kernel from >> >> EFI-32 firmware. >> > >> > No. There's no 32-bit UEFI bootloader stuff being built in Fedora. If >> > it's booting, I suspect that the EFI compatibility support module >> > (CSM-BIOS) is being triggered, and this is actually a legacy BIOS >> > boot. If you get it booted, you can do 'efibootmgr -v' and post the >> > results. Basically if you get some lines that look like entries, then >> > it's a UEFI boot, and if you get an error then it's a BIOS boot. >> >> No luck with that on the >> https://support.apple.com/kb/DL76?locale=en_US firmware... >> >> [howarth@localhost ~]$ efibootmgr -v >> EFI variables are not supported on this system. > > > > It's a CSM-BIOS boot then. It you boot holding down the option key, you > probably get a hard drive icon labeled Windows as one of the options. > Yes, when I hold down the option key, only a single volume appears labelled Windows which oddly boots Linux. Perhaps this has something to do with how I installed this machine. I started with 2 partitions in MBR created with OS X's Disk Utility, The first OS that I installed was Windows 10 Pro in the second partion. I then booted the Fedora 25 Live DVD and using gparted removed all the partitions other than the main Windows 10 one (ie its booter partitions). Then I installed Fedora 25 x86_64 into this section of spare partition space on the drive. FYI, I have found that the automatic partitioning in Fedora gets easily confused and errors out if any prior booter partitions are present. I normally make sure that there is no remaining partitions between the start of the disk and the second OS partition (Windows 10). Is this expected behavior? I would have thought anaconda would cope with using the free partition space between the Windows 10 booter partitions and the Windows 10 main partition, no? >> >> >> >> >> >> http://matthew-brett.github.io/docosx/booting_macs.html >> > >> > >> > >> > >> > -- >> > Chris Murphy >> > _______________________________________________ >> > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx >> > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx >> _______________________________________________ >> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
