Re: uefi boot on Apple Mac

From: Anders Bolt Evensen <andersbo87_at_icloud.com>
Date: Sun, 10 Aug 2014 10:44:24 +0200
If you're interested, you can try out the following ISO:
https://www.dropbox.com/s/srbunx0agrokcs3/freebsd-current-uefi-bios-amd64.iso

The image was built on Friday 8th of August for the amd64 platform.

I tested out the EFI part on VirtualBox (UEFI 2.X) and my MacBook Pro 17 
inch from 2011 (EFI 1.10), and as far as EFI goes, I successfully booted 
the image on both my Mac and VirtualBox (however, booting the image from 
BIOS using my Mac was a different story).

So, as I said, as far as (U)EFI goes, the image should work on UEFI 2.X 
based PC's and EFI 1.10 based Macs.

On 12/07/14 19:22, Nathan Whitehorn wrote:
> I'd point out that, as of last week, the standard -CURRENT ISOs (and 
> generate-release.sh script) make EFI-bootable media by default. All 
> the snapshots should have this done already, for instance.
> -Nathan
I wasn't aware of that, but thanks for the info. :)

>
> On 07/12/14 03:09, Anders Bolt-Evensen wrote:
>> I also got a message like that when I booted from a USB stick on a 
>> MacBookPro8,3 (17 inch, late 2011).
>>
>> I fixed it by creating a custom ISO image and burned that onto a DVD 
>> using an external DVD drive.
>> The UEFI installer boots fine from this external DVD drive.
>>
>> Here is how I did it:
>>
>> Genereste an ISO with the FreeBSD-CURRENT kernel, mount the ISO and 
>> copy all files from the root directory in the ISO and unmount
>>     > cd /usr/src/release
>>     > sh ./generate-release.sh # You may have to run “make 
>> buildworld” and be connected to the internet to install required ports.
>>     > mount -t cd9660 /scratch/R/release/FreeBSD-something-disc1.iso 
>> /mnt
>>     > mkdir freebsd_generic_installer
>>     #Files copied to the directory in the next command will be copied 
>> to a new ISO in step 3
>>     > cp -R /mnt/ freebsd_generic_installer/
>>     > umount /mnt
>> 2. Create a FAT filesystem image and place the loader in it in the 
>> default path that UEFI will look for (the following steps are copied 
>> from https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI):
>>     > dd if=/dev/zero of=efiboot.img bs=4k count=100
>>     > mdconfig -a -t vnode -f efiboot.img
>>     > newfs_msdos -F 12 -m 0xf8 /dev/md0
>>     > mount -t msdosfs /dev/md0 /mnt
>>     > mkdir -p /mnt/efi/boot
>>     > cp loader.efi /mnt/efi/boot/bootx64.efi
>>     > umount /mnt
>>     > mdconfig -d -u 0
>>
>> 3. Create the custom ISO image. Please make sure that the entry in 
>> freebsd_generic_installer/etc/fstab matches the label you choose in 
>> the command below.
>>     > makefs -t cd9660 -o bootimage='i386;efiboot.img' -o 
>> no-emul-boot -o rockridge -o label=“FREEBSD_UEFI_INSTALL" -o 
>> publisher="test" uefi-test.iso freebsd_generic_installer/
>>
>> To get the example in the command above to work, please make sure 
>> that the entry in freebsd_generic_installer/etc/fstab reads
>> "/dev/iso9660/FREEBSD_UEFI_INSTALL    /    cd9660    ro    0 0"
>>
>> 4. Burn the image to DVD, reboot your system and choose “EFI Boot”. 
>> Note that unless you are using a EFI console like rEFIt or rEFInd, 
>> you may have to kind of wait a couple of minutes while the kernel is 
>> loading before anything appears on the screen.
>>
>>
>> On 04/07/14 16:34, Huang Wen Hui wrote:
>>> Hi,
>>> On my MacbookPro11,3, I got this error message:
>>>
>>> http://sw.gddsn.org.cn/freebsd/uefi.jpg
>>>
>>> cheers,
>>>
>>> Huang WenHui
>>>
>>> 2014-07-04 22:13 GMT+08:00 Ed Maste <emaste_at_freebsd.org>:
>>>
>>>> On 24 May 2014 19:39, Rafael Espíndola <rafael.espindola_at_gmail.com> 
>>>> wrote:
>>>>> Yes, I got that in the mac laptops I tried, it worked on a Mac 
>>>>> Pro. It
>>>>> might be the frame buffer corruption that Ed Maste was mentioning.
>>>> I purchased a new MacBook Air yesterday (model identifier
>>>> MacBookAir6,2).  UEFI boot and vt(4) worked correctly.  (My image
>>>> included Rafael's patch; I haven't tried a boot without.)
>>>>
>>>> I also committed a change to display the framebuffer parameters
>>>> (address, dimensions, etc.) on boot, in order to help identify the
>>>> source of this issue.  If you have a moment can you build a new USB
>>>> stick image and give it a try?
>>>>
>>>> -Ed
>>>>
>>> _______________________________________________
>>> freebsd-current_at_freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to 
>>> "freebsd-current-unsubscribe_at_freebsd.org"
>>
>> _______________________________________________
>> freebsd-current_at_freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to 
>> "freebsd-current-unsubscribe_at_freebsd.org"
>>
>
Received on Sun Aug 10 2014 - 07:44:37 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:51 UTC