Opened 12 years ago
Closed 2 months ago
#9365 closed bug (duplicate)
Unable to boot on Thunderbolt-equipped Macs
Reported by: | bobrost | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | System/Boot Loader | Version: | R1/alpha4.1 |
Keywords: | Cc: | ||
Blocked By: | #14453 | Blocking: | |
Platform: | x86 |
Description
Apple Macintoshes with Thunderbolt ports (2011 and later models) are unable to boot Haiku.
Using ReFit as the boot manager, selecting the Haiku partition results in either a hung "other os" boot icon, or a black screen with white text "Unable to find boot device" (or similar). This applies to both my MacBook laptop and my Mac Mini desktop, whether attempting to boot from USB stick, CD, or internal disk partition.
This has been true for all alpha versions of Haiku I have tried, and is not new with alpha 4.
For reference, this was an issue with all Linux distros as well when these machines were first released, but a quick internet search shows that Linux now has either a workaround or a full solution. I expect the issue stems from changes in the OpenFirmware disk controller.
Change History (9)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
rEFIt hasn't been updated since 2010. Try rEFInd instead. http://www.rodsbooks.com/refind/
comment:3 by , 10 years ago
Platform: | x86-64 → x86 |
---|
comment:4 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:6 by , 12 months ago
I've tried booting on a mac mini 2012 and mac mini 2014 with a 64bit efi version.
I'm wondering if this is the issue I am encountering. I will try using refind to boot haiku and see if that works around it
comment:7 by , 12 months ago
(for reference, for both of those machines the kernel boot icon never lights up, but the image is drawn correctly)
comment:8 by , 2 months ago
Keywords: | mac thunderbolt boot removed |
---|
comment:9 by , 2 months ago
Blocked By: | 14453 added |
---|---|
Resolution: | → duplicate |
Status: | assigned → closed |
Is this still an issue?