Hi! This is my first time posting on the FreeBSD forums, so if there is any additional information I can provide or standard I overlooked please let me know. I am a Unix user and computer scientist, so feel free to get technical in any answers.
I am currently attempting to install FreeBSD on a 2011 8,2 MacBook Pro, with the goal of dual-booting alongside MacOS. I have previously successfully dual-booted Arch Linux on the same computer, and FreeBSD will be replacing Arch.
I have tried a few different things but have been unable to proceed beyond the 3rd stage of the boot process, the EFI loader.
I have been using a usb drive and the memstick (not bootonly) image as my installation media. I have not had any issues with booting the installation media or using the installer.
My first attempt was with 12.1-RELEASE. After completing installation using the auto-partitioner on the GPT main disk (efi, ufs, swap) alongside an existing MacOS installation, I rebooted and saw the something nearly identical to the following (exact taken from a later attempt using 11.2-RELEASE):
After some research around the forums, I attempted re-installation, manually creating a "freebsd-boot" partition. No luck. Additionally, I began encountering the "lua" loader bug and copied the loader from 11.2 and got back to the output above. Then, I switched over to using a 11.2-RELEASE image (default partitions, no freebsd-boot). Once again, I received the output above.
When I use the installation media as a LiveCD and mount the created partitions, I can see and access all files and the installation appears to be fully there, including created users. The EFI parition has both BOOTx64.efi and startup.nsh (which is located under disk1p4, seen using
From here I am not sure how to proceed with troubleshooting and addressing the issue. Any advice is greatly appreciated!
I am currently attempting to install FreeBSD on a 2011 8,2 MacBook Pro, with the goal of dual-booting alongside MacOS. I have previously successfully dual-booted Arch Linux on the same computer, and FreeBSD will be replacing Arch.
I have tried a few different things but have been unable to proceed beyond the 3rd stage of the boot process, the EFI loader.
I have been using a usb drive and the memstick (not bootonly) image as my installation media. I have not had any issues with booting the installation media or using the installer.
My first attempt was with 12.1-RELEASE. After completing installation using the auto-partitioner on the GPT main disk (efi, ufs, swap) alongside an existing MacOS installation, I rebooted and saw the something nearly identical to the following (exact taken from a later attempt using 11.2-RELEASE):
Code:
FreeBSD EFI boot block
Loader path: /boot/loader.efi
Initializing modules: ZFS UFS
BootCurrent: 0080
BootOrder: 0080[*]
Probing 11 block devices........*...+. done
ZFS found no pools
UFS found 2 partitions
Consoles: EFI console
Command line arguments: loader.efi
Image base: 0x85b12000
EFI version: 1.10
EFI Firmware: Apple (rev 1.10)
FreeBSD/amd64 EFI loader, Revision 1.1
(Fri Jun 22 04:20:29 UTC 2018 root@releng2.nyi.freebsd.org)
BootCurrent: 0080
BootOrder: 0080[*]
Setting currdev to disk1p4
Setting currdev to disk1p1
Setting currdev to disk1p2
Setting currdev to disk1p3
Setting currdev to disk1p4
Setting currdev to disk1p5
Failed to find bootable partition
press any key to interrupt reboot in 4 seconds
can't load 'kernel'
After some research around the forums, I attempted re-installation, manually creating a "freebsd-boot" partition. No luck. Additionally, I began encountering the "lua" loader bug and copied the loader from 11.2 and got back to the output above. Then, I switched over to using a 11.2-RELEASE image (default partitions, no freebsd-boot). Once again, I received the output above.
When I use the installation media as a LiveCD and mount the created partitions, I can see and access all files and the installation appears to be fully there, including created users. The EFI parition has both BOOTx64.efi and startup.nsh (which is located under disk1p4, seen using
ls disk1p4:/efi/boot
from the loader "OK" prompt.From here I am not sure how to proceed with troubleshooting and addressing the issue. Any advice is greatly appreciated!
Last edited by a moderator: