Last edited: Febuary 14, 2020
This section is for gathering miscellaneous files for booting macOS, we do expect you to know your hardware well before starting and hopefully made a Hackintosh before as we won't be deep diving in here.
What's the best way to figure out if my hardware is supported?
See the supported hardware section for some better insight into what macOS requires to boot, hardware support between Clover and OpenCore are quite similar.
These are the drivers used by OpenCore, for the majority of systems you only need 3 .efi drivers to get up and running:
Needed for seeing APFS volumes(ie. macOS)
For legacy users:
Used for OpenCore picker on legacy systems running DuetPkg, not recommended and even harmful on UEFI(Ivy Bridge and newer)
Used for Haswell and older when no NVMe driver is built into the firmware, not needed if you're not using an NVMe drive
Used for Sandy Bridge and older when no XHCI driver is built into the firmware, not needed if you're not using a USB 3.0 expansion card
For a full list of compatible drivers, see 11.2 Properties in the OpenCorePkg Docs. These files will go in your Drivers folder in your EFI
A kext is a kernel extension, you can think of this as a driver for macOS, these files will go into the Kexts folder in your EFI
All kext listed below can be found pre-compiled in the Kext Repo. Kexts here are compiled each time there's a new commit.
Emulates the SMC chip found on real macs, without this macOS will not boot
Alternative is FakeSMC which can have better or worse support, most commonly used on legacy hardware.
A kext to patch many processes, required for AppleALC and WhateverGreen and recommended for VirtualSMC
Used for monitoring CPU temperature, doesn't work AMD CPU based systems
Used for monitoring fan speed, doesn't work AMD CPU based systems
Used for the ambient light sensor on laptops, desktops can ignore
Do not use if you don't have an ambient light sensor, can cause issues otherwise
Used for measuring battery readouts on laptops, desktops can ignore
Do not use until battery has been poperly patched, can cause issues otherwise
Used for graphics patching DRM, boardID, framebuffer fixes, etc, all GPUs benefit from this kext.
Used for AppleHDA patching, used for giving you onboard audio. AMD 15h/16h may have issues with this and Ryzen/Threadripper systems rarely have mic support
WiFi and Bluetooth:
Used for patching non-Apple Broadcom cards, will not work on intel, Killer, Realtek, etc
Used for uploading firmware on broadcom bluetooth chipset, required for all non-Apple Airport cards.
To be paired with BrcmFirmwareData.kext
BrcmPatchRAM3 for 10.14+ (must be paired with BrcmBluetoothInjector)
BrcmPatchRAM2 for 10.11-10.14
BrcmPatchRAM for 10.10 or older
The order in
Kernel -> Add should be:
AMD CPU Specific kexts:
Thanks to OpenCore 0.5.5, we have a much better solution known as
DummyPowerManagement found under
Kernel -> Quirks
USB fix for AMD FX systems, no effect on Ryzen
Audio for FX systems and front panel Mic+Audio support for Ryzen system, do not mix with AppleALC. Audio quality is noticably worse than AppleALC on Zen CPUs
Useful starting with Catalina to disable the AppleMCEReporter kext which will cause kernel panics on AMD CPUs and dual-socket systems
Needed for syncing TSC on some of Intel's HEDT and server motherboards, without this macOS may be extremly slow or even unbootable. Skylake-X should use TSCAdjustReset instead
On Skylake-X, many firmwares including Asus and EVGA won't write to all cores. So we'll need to reset the TSC on cold boot and wake. Compiled version can be found here: TSCAdjustReset.kext. Note that you must open up the kext(ShowPackageContents in finder,
Contents -> Info.plist) and change the Info.plist ->
IOKitPersonalities -> IOPropertyMatch -> IOCPUNumber to the number of CPU threads you have starting from
0(i9 7980xe 18 core would be
35 as it has 36 threads total)
Used for fixing power management and initialization on non-Apple NVMe, requires macOS 10.14 or newer
Please refer to Kexts.md for a full list of supported kexts
So you see all those SSDTs in the AcpiSamples folder and wonder whether you need any of them. For us, we will be going over what SSDTs you need in your specific ACPI section of the config.plist, as the SSDTs you need are platform specific. With some even system specific where they need to be configured and you can easily get lost if I give you a list of SSDTs to choose from now.
Getting started with ACPI has an extended section on SSDTs including compiling them on different platforms.
A quick TL;DR of needed SSDTs(This is source code, you will have to compile them into a .aml file):
Intel HEDT Config.plist