• Become a Premium Member for $25/year with no ads to improve your community experience. Upgrade to Pro Account for faster response and no wait times!

GUIDE Troubleshooting macOS Installation [Clover/OpenCore]

EliteMacx86

Administrator
Staff member
Joined
Jul 22, 2018
Messages
9,074
Motherboard
Supermicro X11SPA-T
CPU
Intel Xeon W-3275 28 Core
Graphics
2xAMD RX 580 8GB
OS X/macOS
13.x
Bootloader
  1. OpenCore (UEFI)
Mac
  1. Mac mini
  2. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
Troubleshooting macOS Installation [Clover/OpenCore]

This troubleshooting guide is for users who are having issues with booting OpenCore, macOS, or issues under macOS. If you're confused regarding what process you're stuck at, consider reading the macOS Boot Process for more information.

QUICK INFO:
  • If your issue is not covered here, please go through the OpenCore Official documentation. This document includes way more technical details regarding OpenCore and its functionality.

This section is divided into 4 main categories of Troubleshooting and consists of the following
 
Boot Issues

Grey screen after booting the macOS Installer


If you have not followed the OpenCore Installation guide correctly, you might end up getting a blank grey screen after booting the macOS Installer. This issue can be seen from macOS Big Sur.
 
Last edited:
Installation Issues

This section covers troubleshooting issues that tend to appear once you have booted off the macOS/OS X installer. The problems listed here are likely to be experienced by users once they have booted the macOS/OS X installer, however, it totally depends on what the user has missed or how well the installation and EFI were configured.

This is not a troubleshooting thread. Please do not ask questions regarding your specific issue in this thread. If you're having an issue, create a separate thread. If you're having a problem to report or have a workaround to resolve the problems listed here, regarding the installation or function in macOS Ventura, you can reply to this thread.

Grey screen after booting the macOS Installer


If you have not followed the OpenCore Installation guide correctly, you might end up getting a blank grey screen after booting the macOS Installer. This issue can be seen from macOS Big Sur.

No Keyboard and Mouse


macOS Installer in Russian


No Disk in Disk Utility


If you don't see the target disk in Disk Utility, you should check for the following:
  • Compatible SATA/NVMe Drive. Intel Optane, VMD, and RAID (usually unsupported) are not supported on macOS/OS X. Refer to Storage Compatibility for more information.
  • SATA Mode set to AHCI.
Note that some SATA Controllers are unsupported in macOS and therefore you need an injector Kext to enable SATA support. To fix this issue, you'll need to use CtlnaAHCIPort.kext.

Failed to Erase Disk

macOS Installer is damaged

Your Mac needs a firmware update in order to install to this volume

Stuck at 2 minutes remaining

The recovery server could not be contacted

Scrambled Screen on Laptops

Black screen after I

Black screen after on Desktops

System freeze before login
 
Last edited:
Post-installation Issues
This section covers troubleshooting issues that tend to appear once macOS/OS X is installed. The problems listed here are likely to be experienced by users once they have installed macOS/OS X, however, it totally depends on what the user has missed or how the installation and post-installation were configured.

This is not a troubleshooting thread. Please do not ask questions regarding your specific issue in this thread. If you're having an issue, create a separate thread. If you're having a problem to report or have a workaround to resolve the problems listed here, regarding the installation or function in macOS Ventura, you can reply to this thread.

Internal PCI Drives (NVMe/M.2) seen as External Drives


A very common issue with the AMD systems. On most of the AMD systems, this is a very common issue.



TRIM not Enabled

Slow Read and Write Speeds on SSD


If you're having an SSD and still have not the approximately same speed as specified by the manufacturer, you should check for the following:
  • If using SATA SSD, use SATA III (6Gb/s) port.
  • Ensure SATA (Data) Cable is healthy and of SATA III (6Gb/s) standard.
  • Ensure there are no bad sectors
  • If using SATA SSD, SATA Mode set to AHCI
  • Install the latest Firmware, if available.
  • TRIM Enabled
  • Ensure SMART status has no errors and the disk is healthy

Note that there are known SSDs with bad TRIM functions which can cause slower Read and Write speeds on macOS/OS X. Refer to Storage Compatibility for more information.



BIOS Reset after Restart or Shut Down


On a few Desktop systems, whenever you restart from macOS or Shut Down the system and start it next time, you may notice that the BIOS is reset every time and an error message appears



Slow boot with APFS and TRIM

Starting with macOS High Sierra, Apple has introduced APFS File System which is much more sensitive to SSD hardware and firmware compatibility with regards to TRIM than HFS+ (Journaled). Any incompatibility will result in a slower boot and other problems such as battery status not showing, and trackpad preference not showing may arise.

The new APFS file system is much more sensitive to SSD hardware/firmware compatibility with regards to TRIM than HFS+J. Incompatibility will result in slow boot and other problems (battery status not showing, trackpad prefpane not showing, etc).

Two solutions available:
- disable the any TRIM patch you may be using (eg. no TRIM support for your SSD in that case)
- or, install on HFS+J

For installing on HFS+J, read here:
https://www.tonymacx86.com/threads/...n-high-sierra-update-or-fresh-install.232855/

No IGPU Acceleration


It's very likely possible that you may not have the IGPU acceleration working if you have not followed the guide correctly, even for a supported Graphics model. The reason is either no framebuffer patching has been done or it is not proper. Refer to the guide linked below for more information.

In addition, there are a few Graphics models which are not supported by the latest macOS version and must be patched using OCLP. As per the IGPU Compatibility list, if you find that your Graphics is capable of patching on the new macOS version, refer to the guide linked below for more information.

Similarly, the same applies if you have NVIDIA and AMD Graphics

In addition, GPUs from certain vendors such as HIS, XFX, HIS, and VisionTek require a cross VBIOS flashing to work under OS X/macOS. See How to Flash AMD VBIOS for more information.

Problems booting the macOS installer on Dual GPU Systems


Starting with macOS High Sierra, when booting the installer on dual GPU systems, the installer hangs as there is an issue with the VESA drivers. Both Desktops and Laptops are affected and using the boot arg nv_disable=1 to disable NVIDIA Graphics will not help in such a case. This workaround no longer works and you'll need to use -radvesa boot arg for AMD Graphics and for NVIDIA, you can use

Another approach is to disable the Discrete Graphics by patching the ACPI. Refer to the guide linked below for more information.

Black screen after booting


Few KBL, CFL, and ICL Laptops need fixing of backlight registers otherwise such devices will end in a black screen when booting to macOS. To fix this issue, you'll need to use the enable-backlight-registers-fix property to IGPU. Refer to the guide linked below for more information.

System Freezing and Crashing issue with AMD RX VEGA 56/64 and Radeon VII Graphics


It's very likely possible that you may have freezing and crashing issues with AMD RX VEGA 56/64 and Radeon VII Graphics. This is mostly due to XMP. To fix this issue, you'll need to disable XMP. Refer to the guide linked below for more information.


No Brightness Control


On non-Apple computers with macOS/OS X installed, the brightness control does not work by default. To enable the brightness, you need to fix the graphics acceleration and attach a PNLF device to the IGPU. Refer to the guide linked below for more information.

No Brightness Hotkeys


It's very likely possible that you may not have the Brightness Hotkeys working on your Laptop even when a Brightness Control (slider in SysPrefs->Displays). To enable the Brightness Hotkeys, you need to map the Brightness Hotkeys. Refer to the guide linked below for more information.

No Keyboard Backlight and HotKeys


On a few Laptops, the Keyboard Backlight and the HotKeys may function out of the box. However, it's very likely possible that you may not have the Keyboard Backlight (especially ASUS). To enable the Keyboard Backlight, you'll need to patch the ACPI. Enabling Keyboard Backlight will also enable Hotkey. Refer to the guide linked below for more information.


No HDMI/mDP OutPut


It's very likely possible that you may not have the HDMI/mDP OutPut working from your Laptop when using IGPU. The reason is either no framebuffer patching has been done or it is not proper. Refer to the guide linked below for more information.

No Display after Wake


Since Skylake, the Sleep/Wake function is broken on Desktops with IGPU. Luckily, the Mobile platform works as expected. However, on a few systems (especially Coffee Lake), the display fails to wake. A workaround is to use igfxonln=1 in boot-arg.

No Audio Hotkeys


The Audio Hotkeys will be enabled automatically, once you enable the built-in Audio. Refer to the guide linked below for more information.



Intel HD 3000 not working
Since macOS Mojave, Apple removed support for Intel HD Graphics 3000. However, on a newer version of macOS, the Graphics can be patched and made to work. Refer to the guide linked below for more information.

Skylake Graphics (Intel HD Graphics 515) not working
Like Intel HD 3000 and 4000, Skylake support was removed by Apple since macOS Ventura. However, a workaround is to spoof SKL Graphics as KBL Graphics. But due to this spoof, there are random flickers. A more robust workaround is to patch the system and use the old SKL Graphics kexts. The patching can be done using OpenCore Legacy Patcher. Refer to the guide linked below for more information.


No built-in Audio


After reaching the desktop, it might be very likely that you don't have the built-in audio working. To fix the audio, there is already a separate guide. Refer to the guide linked below for more information.

Audio Distortion or Crackling from Headphone Port


On a few Laptops, with a few Audio Codecs, there is an audio distortion or crackling from the Headphone/Combo Jack port. A simple workaround is to use VoodooHDA, however, with VoodooHDA, the quality is quite bad and lower when compared with Windows. A more robust solution is to use the JackFix script. Refer to the guide linked below for more information.

Audio Stuttering on AMD Systems


Audio Stuttering, Distortion, Lags, Delays and Crackling Audio with AMD CPUs are pretty common. To fix this issue, you need to change the PCIe Generation to Generation 3. Refer to the guide linked below for more information.


No HDMI/DP Audio


It's very likely possible that you may not have the HDMI/DP Audio working, especially if you're using IGPU on a Laptop. Usually, on Desktops with discrete Graphics, (mostly AMD), there is nothing much required. However, when using IGPU, this requires choosing a correct ig-platform-id and connector patching. The most common reason for the non-working of HDMI/DP Audio is because of incorrect Framebuffer patching. A separate guide is available for both of them. Refer to the guide linked below for more information.

For IGPU


For NVIDIA and AMD


No Chime Sound at Startup


On Non-Apple computers, the Boot Chime isn't enabled by default. Enabling Boot Chime sound requires a little configuration. Refer to the guide linked below for more information.

No Volume/Brightness Control on External Monitors


Unfortunately, macOS/OS X does not allow control of DP/HDMI Audio from the system (No volume, no mute, no balance). You need to control it from the DP/HDMI Device itself. A workaround is to use a third-party app such as MonitorControl.

Adobe Apps crashing on AMD

USB Ports not working


Likely, some of your ports may not work, or if it works, it may not work with its correct speed. To fix this issue, you need to enable the USB ports first and then map the USB Ports. Refer to the guide linked below for more information.

AMD CPU Power Management not working


As AMD CPUs are not officially supported by Apple, it's very likely that you may not have the AMD CPU Power Management working on your system. To fix this, you need to use SSDT-PLUG and a third-party kext. Refer to the guide linked below for more information.

CPU Power Management not working on Intel X79/C606


Typically, if you're using an X79 based system with either Sandy Bridge-E/EP or Ivy Bridge-E/EP CPU, the CPU Power Management will not work by default. Due to the non-working of CPU Power Management, the system utilization will be always at 100% load. To fix this issue, you'll need to patch the CPU Power Management. Refer to the guide linked below for more information.

Graphics Power Management not working


Like CPU Power Management, Graphics Power Management is also important. Normally, the IGPU and AMD Graphics Power Management may work OOTB, if it has been set up correctly. However, when it comes to NVIDIA, you need to implement Graphics Power Management. Refer to the guide linked below for more information.



Battery Status not showing


A very few Laptops can have the Battery status without a correctly patched ACPI, just by using the ACPIBatteryManager.kext or SMCBatteryManager.kext and this is due to the fields defined in the ACPI which either does not needs patching or very minimal. However, for most of the Laptops, ACPI Patching is required to enable battery status. Refer to the guide linked below for more information.

On a few Laptops with macOS 10.13, the battery status will not be detected at startup even with a correctly patched ACPI. The workaround is when at the login screen, unplug the AC Adapter, and plug it back (Vice-versa, if starting on battery power). Note that this workaround may not work for every Laptop and is rare. Note that this has also a relation to the non-Apple SSDs and TRIM and on NVMe drives, the TRIM is always enabled, so you don't have the option to disable TRIM. Another workaround is to disable TRIM and use HFS+ (Journaled). However, this timing issue can be fixed by increasing the delay time by using abm_firstpolldelay=XXXX in your boot-arg, where X represents the delay value. For example, to set to 16000ms (16 sec), use kernel flag: abm_firstpolldelay=16000. This might solve the status issues once you find the right value. Note that this is only supported by ACPIBatteryManager.kext and not SMCBatteryManager kext. For ACPIBatteryManager.kext, use v1.81.4 or later.

No Trackpad


Usually, to enable the Trackpad, you need to use a compatible Trackpad kext according to the Trackpad variant (either PS/2 or I2C). However, there can be certain cases, where the Trackpad does not work even when using the right kext. This could be due to several issues and a separate guide is available for this. Note that with I2C variants of the Trackpad, this issue is more common. However, with I2C Trackpads, the process is much more complex as it involves ACPI Patching. Refer to the guide linked below for more information

No Trackpad Gestures


It might be possible that you have the Trackpad working in some way but either few or none of the gestures work. This could be due to outdated or incompatible kext being used. Note that depending on the Trackpad model your Laptop uses, the gestures can be limited when using macOS/OS X. Refer to the guide linked below for more information

Trackpad Preferences not showing


You may have noticed that your Trackpad is working but no Trackpad preference is available in System Preferences>Trackpad. This is very common and the workaround is to patch the ACPI for Battery Status. Once the battery status is enabled, the trackpad preferences should be available. Refer to the guide linked below for more information.

No Temperature and Fan Sensor Output


Unlike Apple computers, non-Apple computers do not have a native temperature and fan sensor output. So, it is very likely that after installing any temperature reading App will not read out the sensor data. Refer to the guide linked below for more information.

No Apple VT-D


The VT-d function is required for DMA protection, for Thunderbolt and related devices. As VT-d is CPU and Motherboard dependent, it is not possible to enable VT-d on every system. Please note that on some systems (generally non-HEDT systems), may need memory mapping (fixing DMAR table) or the network (Ethernet and WiFi) may result in an infinite link-up and down state. Refer to the guide linked below for more information.

No Thunderbolt


The Thunderbolt implementation requires a compatible Thunderbolt and some BIOS Settings. For Unsupported Motherboards, there is a different workaround. Refer to the guide linked below for more information.

No Thunderbolt HotPlug


It might be possible that you have the Thunderbolt working but not the Thunderbolt HotPlug. Usually, the Thunderbolt HotPlug requires ACPI patching and firmware patching (if necessary). Refer to the guide linked below for more information.

Antelope, PreSonus, Slate Digital, Focusrite, Apogee Interface, and Drobo NAS not connecting


Usually, these devices require Apple VT-d and Thunderbolt Bus. The VT-d function is limited by the CPU and Motherboard. And on Non-Apple computers, you need to go through an extra route to implement these two. Refer to the guide linked below for more information.

No Daisy Chain

No Thunderbolt AVB


Usually, the Thunderbolt Audio Video Bridging feature requires Thunderbolt Bus ID Activation. Refer to the guide linked below for more information.

No Thunderbolt Network Capability


Usually, the Thunderbolt networking feature requires Thunderbolt Bus ID Activation. Refer to the guide linked below for more information.


No Thunderbolt Information in System Report>Thunderbolt/USB4


Usually, it's very normal that you may only see "No Drivers are loaded" instead of Thunderbolt information. The reason you don't see the Thunderbolt information is due to the lack of Thunderbolt Bus, which typically requires flashing the Thunderbolt chip with custom firmware that activates the Thunderbolt Bus ID. For more information, refer to the guide linked below.

No Ethernet


Usually, the Ethernet requires a compatible Kext according to the Chip. However, even with the right Kext, the ethernet may not work in some cases such as Intel I225-V and AQuantia. For users on macOS Ventura, you must enable VT-d to use Intel I225-V and Aquantia Ethernet.

Ethernet Link Up and Link Down State Infinite loop


On a few systems, enabling VT-d can result in a link-up and link-down state with an infinite loop. The reason is due to the memory mapping which needs to be corrected (DMAR Table). Refer to the guide linked below for more information.


No WiFi Network

On a few hardware (especially Laptops), you may need to mask the PINS to activate WiFi.

Atheros WiFi detected but no Signal


On a few Laptops, the Atheros WiFi is detected but no signal. This isn't the case with every Laptop equipped with Atheros WiFi. To fix this issue, you'll need to use VoodooI2C.kext

No Bluetooth on macOS Monterey and above


It's very likely possible that even with the USB ports mapped, the Bluetooth may not work if you're on macOS Monterey and above. The Bluetooth may appear in System Preferences but will not work. Both, Broadcom and Intel Cards are affected. To fix this issue, you'll need to map your USB ports first and also add BlueToolFixup.kext. Refer to the guide linked below for more information.

No AirDrop

No Handoff and Continuity

No AirPlay

No SideCar

No H.264/H.265 Encoding


H.264/H.265 has some specific hardware requirements. In addition, a compatible SMBIOS must be set to activate H.264/H.265. Refer to the guide linked below for more information.





Preboot entry showing in Clover


With the APFS setup, you may see extra boot entries (preboot and prebooter) in the Clover boot picker. Refer to the guide linked below for more information.


Cannot Write to macOS System Partition


Starting with macOS Catalina, Apple has split the OS and user data into two volumes where the system volume is "read-only" by default which prevents modification of the system root volume. To fix the audio, there is already a separate guide. Refer to the guide linked below for more information.


Cannot boot to Windows from OpenCore Picker

You shut down your computer because of a problem error


Since Monterey, there have been a lot of reports from users regarding this error. Refer to the guide linked below for more information.

Reboot after patching the system using OCLP

It's very likely that after patching the system using OCLP (generally for Legacy Graphics) when booting, there is an instant reboot. To fix this issue, you'll need to set SecureBootModel to Disabled under the Misc>Security section of your config.plist. SecureBootModel must be disabled on some systems after patching using OCLP to prevent instant reboot when booting from the patched system drive.
 
Last edited:

Latest posts

Forum statistics

Threads
2,084
Messages
19,451
Members
29,552
Latest member
felipepedrosa