On Fri, 2011-12-02 at 12:08 +0100, Andreas Tunek wrote:
> As you all might know, it is currently impossible to boot the default
> install of F16 on Macs. It does not seem to matter if you use boot
> loaders such as reFit and Bootcamp or remove MacOS completely and try
> to boot. Apparently, if you somehow (how to use it is not very clear
> from the "Common F16 bugs" page,
>
http://fedoraproject.org/wiki/Common_F16_bugs#Incorrect_partition_type_as...)
> use the nogpt kernel parameter you might be able to install F16.
>
> There are a couple of bugs open regarding this,
>
https://bugzilla.redhat.com/show_bug.cgi?id=752548 and
>
https://bugzilla.redhat.com/show_bug.cgi?id=746895 are two examples.
>
> It seems like the boot procedure has changed quite a bit from F15 to
> F16, and not just the GRUB2 change. I am sure these were changed for
> the best of reasons, but it is very frustrating to not be able to use
> F16 on hardware that could run previous Fedoras very well. Also, there
> are a lot of Macs out in the wild, and by excluding them we shut out a
> large amount of (possible users).
>
> So what could be done about this? Would it be enough to have a visible
> nopgt option in Anaconda? Should we do special "Boot test days"? Or is
> something else needed?
So, revisiting this: right now it seems like the aim for F17 is to focus
on native EFI boot and install on Mac, not installation using BIOS
compatibility mode. We should aim to fix any remaining issues with
booting Macs via EFI and test throughout F17 cycle to ensure it works.
Will it be possible to do dualboot (MacOS + Fedora) and tripleboot
(MacOS + Windows + Fedora) with this method?
/Andreas
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel