MacBook (with T2 Chip) EFI Boot Issue: Haiku R1/beta5 fails with black screen and reboots

[Dmitry]

Steps to Reproduce:

1. Boot Haiku R1/beta5 on a MacBook Pro via EFI Boot menu.
2. Select any of the available "EFI Boot" icons for Haiku.

Expected Behavior: Haiku boot loader should appear and proceed to system boot.

Actual Behavior: After selecting Haiku in the EFI Boot menu, the screen turns black and nothing happens.

Additional Information:

• Hardware: "MacBookPro16,1"; MacBook Pro 16-inch, 2019; 2,3 GHz 8-Core Intel Core i9; AMD Radeon Pro 5500M/Intel UHD Graphics 630; 2 x (8 GB DDR4 2667 MHz RAM); SSD 1 TB.
• Security: Apple T2 Security Chip is present.
• Holding Shift during boot does not open the Safe Mode menu.
• Older versions, such as Haiku R1/beta4 and the 32-bit version, also fail to boot on this device.

[kim1963]

With some hardware, you'll have to make sure USB keyboards are enabled in the BIOS. On computers that use UEFI for booting instead of the classic BIOS, you need to use the SPACEBAR instead of SHIFT.

​https://www.haiku-os.org/docs/userguide/en/bootloader.html

[Dmitry]

Replying to kim1963:

With some hardware, you'll have to make sure USB keyboards are enabled in the BIOS. On computers that use UEFI for booting instead of the classic BIOS, you need to use the SPACEBAR instead of SHIFT.

​https://www.haiku-os.org/docs/userguide/en/bootloader.html

I tried entering the Boot Loader Options as described in the user guide, using the SPACEBAR to access the menu on my UEFI MacBook. Unfortunately, it didn’t work — the black screen persists, and no boot menu appears.

Let me know if there are other steps I can try or additional information I can provide.

[waddlesplash]

Duplicate of #14453. But please test with a nightly image and see if you get anything different (and comment there if so.)

[Dmitry]

Thank you for pointing this out. I’ve tested with a nightly image, but unfortunately, the behavior remains the same — the screen stays black, and the system does not boot. I’ll comment on the related bug report as well. Thanks again for your help!