You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I try to load the macOS installer with OpenCore, it gets stuck on the Apple logo screen with no loading bar. If I load in verbose mode, the last message before it gets stuck is [EB|#LOG:EXITBS:START]
Screenshots
Device (please complete the following information):
macOS Version: Monterey, but same thing happens with Big Sur and Catalina
EFI Version: 1.7.2
EFI type (regular or HeliPort): regular
T440p with i5-4300M and Nvidia graphics, 8GB RAM, 500GB WD Blue SATA SSD
Additional context
I have tried everything from resetting my BIOS and configuring it according to the tutorial again, changing from com.apple.recovery.boot to two partitions, trying different SMBIOS configurations and even different macOS versions, the issue still persists.
The text was updated successfully, but these errors were encountered:
Flip the values around to match older fw. See troubleshooting section.
EnableWriteUnprotector
Another issue may be that macOS is conflicting with the write protection from CR0 register, to resolve this we have 2 options:
If your firmware supports MATs(2018+ firmwares):
EnableWriteUnprotector -> False
RebuildAppleMemoryMap -> True
SyncRuntimePermissions -> True
For older firmwares:
EnableWriteUnprotector -> True
RebuildAppleMemoryMap -> False
SyncRuntimePermissions -> False
Describe the bug
When I try to load the macOS installer with OpenCore, it gets stuck on the Apple logo screen with no loading bar. If I load in verbose mode, the last message before it gets stuck is
[EB|#LOG:EXITBS:START]
Screenshots
Device (please complete the following information):
Additional context
I have tried everything from resetting my BIOS and configuring it according to the tutorial again, changing from
com.apple.recovery.boot
to two partitions, trying different SMBIOS configurations and even different macOS versions, the issue still persists.The text was updated successfully, but these errors were encountered: