Brief description: Two problems, one the resulting installation will not boot, I get a "no bootable device" message upon restart. Also, the 500MB boot partition's type code is EF00 (EFI Partition) instead of 8300 which would seem to be a bug.
100% reproducible. Steps for reproducing, starting with Fedora-16-Beta-x86_64-Live-Desktop.iso
1. Checksum of ISO and burned DVD-RW confirmed.
2. Boot from DVD.
3. dd if=/dev/zero of=/dev/sda bs=4096 count=34
4. yum install gdisk
5. In gdisk, create a new blank GPT, all unallocated space.
6. Run the installer, and choose default installation type "Replace Existing Linux Systems"
7. Accept the installer default partitioning scheme.
8. Accept the installer default bootloader installation setting to /dev/sda (the only HDD in the computer).
9. Check partition table with gdisk.
A. The 500MiB ext4 boot partition is set to type EF00 (and GUID) which is "EFI Partition" rather than 8300 for Linux partition. This seems wrong.
B. That same partition has no partition name.
C. Gray screen for 60 seconds follow by black screen containing text at the top only: No bootable device -- insert boot disk and press any key.
A. Repeated all steps above, but tried "Use All Space" and "Use Free Space" installation types instead; same result with 500MB boot partition getting a type code of EF00, and "no bootable device" on reboot.
B. Used gdisk to change partition type for the boot partition from EF00 to 8300 and reboot. Computer still won't boot.
C. F15 Final Live CD boots, installs and reboots. But of course this is MBR only partitioning, and Grub Legacy.
gdisk version 0.7.2
Hardware is Macbook Pro 4,1. This hardware's EFI support prevents EFI only booting if I want a GUI, so the use of the Live CD is intentional, forcing CSM/BIOS boot.
---------- Post added at 09:27 PM ---------- Previous post was at 09:13 PM ----------
The fact I get a "no bootable device" rather than a gray flashing folder with a question mark, tells me that this is probably a message from the CSM/BIOS. CSM boot should blind load GRUB2's boot.img from the first 512 bytes of the disk, then proceed to core.img which includes a rescue shell. But I'm not even getting that far which leads me to believe the problem is either in that first 512 bytes, or core.img isn't installed (correctly.)