mjg59 | Properly booting a Mac

This is mostly for my own reference, but since it might be useful to others:

By "Properly booting" I mean "Integrating into the boot system as well as Mac OS X does". The device should be visible from the boot picker menu and should be selectable as a startup disk. For this to happen the boot should be in HFS+ format and have the following files:

/mach_kernel (can be empty)
/System/Library/CoreServices/boot.efi (may be booted, if so should be a symlink to the actual bootloader)

/System/Library/CoreServices/SystemVersion.plist which should look something like

<xml version="1.0" encoding="UTF-8"?>
<plist version="1.0">
<dict>
        <key>ProductBuildVersion</key>
        <string></string>
        <key>ProductName</key>
        <string>Linux</string>
        <key>ProductVersion</key>
        <string>Fedora 16</string>
</dict>
</plist>

That's enough to get it to appear in the startup disk boot pane. Getting it in the boot picker requires it to be blessed. You probably also want a .VolumeIcon.icns in / in order to get an appropriate icon.

Now all I need is an aesthetically appealing boot loader.

Flat | Top-Level Comments Only

Do the bits you described get accessed by some OS X bootloader, or by EFI? If the former, can we replace it with some bootloader which knows how to boot OS X? If the latter, has anyone looked into what it would take to integrate additional EFI modules which could supplant the existing boot mechanism?

I have used rEFIt on several Intel iMacs in a triple-boot scenario and it works great.

It doesn't integrate sensibly with the boot picker and it doesn't work well if you ever touch the startup disk. Benefits and tradeoffs.

s/Linux/Fedora/ silly, that would be bad once Fedora supports multiple kernels.

Things that Fedora is unlikely to do include…

So does this mean that aside from the EFI system partition (FAT), and the BIOS boot partition, I'd need yet another bootstrap partition, this time in HFS+ format?

You don't need a BIOS boot partition in this setup. It does mean an additional HFS+ partition, yes.

How did you actually get this to work? There are quite of few pages out there how to boot Fedora on a macbook with EFI... but they all seem to say a different thing!?

I created a usb live cd image of fedora 16 (http://dummdida.blogspot.com/2011/10/efi-fedora.html)

I then booted to the live usb image and installed Fedora. Here's my partition table:

/dev/sda1 fat, /boot/efi
/dev/sda2 hfs+,
/dev/sda3 ext4, /
/dev/sda4 swap,
/dev/sda5 ext4, /home

I see that on the EFI System Partition it now has EFI/redhat/grub.efi but when I boot my macbook (pro 5,4) holding alt the only option to boot is Macintosh HD.

Is this extra hfs+ partition required to make my fedora install show up in the boot menu? Or did I install this wrong?

Thanks in advance for any advice you can shed on this. What did you do to get your fedora install to work?

Right now there's no automatic stuff to handle all this. With luck we'll be making things work properly in F17. The Apple boot picker menu ignores EFI boot variables - you need a blessed HFS+ partition to get that working.

Ok. Thanks. I'll wait for F17.

But for my own clarity... were my mounts correct from above? And this extra hfs+ partition should be mounted to /boot ? is that correct?

The extra HFS+ partition probably wants to be /boot/EFI, but we haven't figured that out for sure yet.

Sorry it this is a stupid question, but this hfs+ partition does not have any effect/is any good when single boot Linux on a mac (OS X not installed), right?

Probably not, no - there'd be nothing that'd interfere with your boot variables in that case.

This may be helpful to some people who read this post:

http://d.goodlad.net/articles/arch_linux_on_mba_42/

On which partition did you put the actual bootloader (the .efi file)?

If it's on the extra hfs partition: How did you get it there? As far as I know, Linux installation medias don't have a hfs file system driver, so you can't write the file to the partition during installation.

If it's anywhere else: How did you create the symlink? Symlinking to a file on an unmounted device doesn't sound very good, but you can't mount the partition at this point of the startup process, can you?

Maybe this is a stupid question, but I've searched for additional information on several other websites and most of them advise to use rEFIt, but your approach sounds a lot cleaner to me, so I'd be very happy, if you could clarify this point to me.

Our install media has an HFS+ driver.

hey simply disable journaling in the efi partition, works good i have done and works fantastic.

i use archlinux, i made the partition on osx with gpt fdisk, then formated the small hfs+ partition and disabled the journaling. in installed manually grub2 on the hfs+ partition during the installation, and wen rebooted on osx blessed the smal hfs+ partition.

----------------------------------------------------------------
3.0 KiB free space
1 200.0 MiB EFI System EFI System Partition
2 175.7 GiB Apple HFS/HFS+ mac
128.0 MiB free space
3 200.0 MiB Apple HFS/HFS+ Linux EFI
128.0 MiB free space
4 200.0 MiB Linux filesystem Boot
5 10.0 GiB Linux filesystem Root
6 43.0 GiB Linux filesystem Home
7 3.4 GiB Linux swap Swap

How does the BOOTCAMP partition appear in the boot-picker menu if it is not HFS and doesn't have those files?

Thank You

It's special-cased. Any bootable legacy partition will appear as "Windows".

Properly booting a Mac

no subject

rEFIt works great

Re: rEFIt works great

not Linux

Re: not Linux

yet another partition

Re: yet another partition

What's your setup?

Re: What's your setup?

Re: What's your setup?

Re: What's your setup?

Single boot?

Re: Single boot?

Arch Linux on Macbook Air 4,2

Bootloader installation

Re: Bootloader installation

Re: Bootloader installation

Re: Bootloader installation

Apple boot-picker menu

Re: Apple boot-picker menu