Kaby Lake và Amber Lake
config.plist cho hệ thống
Laptop Kaby Lake & Amber Lake Y
Initial macOS Support
macOS 10.12, Sierra
#Starting Point
So making a config.plist may seem hard, it's not. It just takes some time but this guide will tell you how to configure everything, you won't be left in the cold. This also means if you have issues, review your config settings to make sure they're correct. Main things to note with OpenCore:
All properties must be defined, there are no default OpenCore will fall back on so do not delete sections unless told explicitly so. If the guide doesn't mention the option, leave it at default.
The Sample.plist cannot be used As-Is, you must configure it to your system
DO NOT USE CONFIGURATORS, these rarely respect OpenCore's configuration and even some like Mackie's will add Clover properties and corrupt plists!
Now with all that, a quick reminder of the tools we need
Universal plist editor
For generating our SMBIOS data
Sample/config.plist(opens new window)
See previous section on how to obtain: config.plist Setup
WARNING
Read this guide more than once before setting up OpenCore and make sure you have it set up correctly. Do note that images will not always be the most up-to-date so please read the text below them, if nothing's mentioned then leave as default.
#ACPI

#Add
Info
This is where you'll add SSDTs for your system, these are very important to booting macOS and have many uses like USB maps (opens new window), disabling unsupported GPUs and such. And with our system, it's even required to boot. Guide on making them found here: Getting started with ACPI(opens new window)
For us we'll need a couple of SSDTs to bring back functionality that Clover provided:
Allows for native CPU power management on Haswell and newer, see Getting Started With ACPI Guide (opens new window)for more details.
Fixes both the embedded controller and USB power, see Getting Started With ACPI Guide (opens new window)for more details.
Creates a stub so VoodooI2C can connect, for those having troubles getting VoodooI2C working can try SSDT-XOSI (opens new window)instead. Note that Intel NUCs do not need this
Fixes brightness control, see Getting Started With ACPI Guide (opens new window)for more details. Note that Intel NUCs do not need this
Note that you should not add your generated DSDT.aml
here, it is already in your firmware. So if present, remove the entry for it in your config.plist
and under EFI/OC/ACPI.
For those wanting a deeper dive into dumping your DSDT, how to make these SSDTs, and compiling them, please see the Getting started with ACPI (opens new window)page. Compiled SSDTs have a .aml extension(Assembled) and will go into the EFI/OC/ACPI
folder and must be specified in your config under ACPI -> Add
as well.
#Delete
This blocks certain ACPI tables from loading, for us we can ignore this.
#Patch
Info
This section allows us to dynamically modify parts of the ACPI (DSDT, SSDT, etc.) via OpenCore. For us, we'll need the following:
OSI rename
This is required when using SSDT-XOSI as we redirect all OSI calls to this SSDT, this is not needed if you're using SSDT-GPIO
Enabled
Boolean
YES
Count
Number
0
Limit
Number
0
Find
Data
5f4f5349
Replace
Data
584f5349
#Quirks
Settings relating to ACPI, leave everything here as default as we have no use for these quirks.
#Booter

This section is dedicated to quirks relating to boot.efi patching with OpenRuntime, the replacement for AptioMemoryFix.efi
#MmioWhitelist
This section is allowing spaces to be pass-through to macOS that are generally ignored, useful when paired with DevirtualiseMmio
#Quirks
Info
Settings relating to boot.efi patching and firmware fixes. For most users, leave it as default.
ProtectMemoryRegions: YES
Fixes shutdown/restart on some Chromebooks that would otherwise result in a
AppleEFINVRAM
kernel panic.
#DeviceProperties

#Add
Sets device properties from a map.
PciRoot(0x0)/Pci(0x2,0x0)
This section is set up via WhateverGreen's Framebuffer Patching Guide (opens new window)and is used for setting important iGPU properties.
The config.plist doesn't already have a section for this so you will have to create it manually.
When setting up your iGPU, the table below should help with finding the right values to set. Here is an explanation of some values:
AAPL,ig-platform-id
This is used internally for setting up the iGPU
Type
Whether the entry is recommended for laptops (ie. with built-in displays) or for Intel NUCs (ie. standalone boxes)
Generally follow these steps when setting up your iGPU properties. Follow the configuration notes below the table if they say anything different:
When initially setting up your config.plist, only set AAPL,ig-platform-id - this is normally enough
If you boot and you get no graphics acceleration (7MB VRAM and solid background for dock), then you likely need to try different
AAPL,ig-platform-id
values, add stolenmem patches, or even add adevice-id
property.
00001B59
Laptop
Recommended for HD 615, HD 620, HD 630, HD 640 and HD 650
00001659
Laptop
Alternative value to 00001B59
if you have acceleration issues, and recommended for all HD and UHD 620 NUCs
0000C087
Laptop
Recommended for Amber Lake's UHD 617 and Kaby Lake-R's UHD 620
00001E59
NUC
Recommended for HD 615
00001B59
NUC
Recommended for HD 630
02002659
NUC
Recommended for HD 640/650
#Configuration Notes
In some cases where you cannot set the DVMT-prealloc of these cards to 64MB or higher in your UEFI Setup, you may get a kernel panic. Usually they're configured for 32MB of DVMT-prealloc, in that case add these values to the iGPU properties:
framebuffer-patch-enable
Data
01000000
framebuffer-stolenmem
Data
00003001
framebuffer-fbmem
Data
00009000
For all UHD 620 users (Kaby Lake-R), you'll need a device-id spoof:
device-id
Data
16590000
HD 6xx users (UHD 6xx users are not concerned) may have some issues with output where plugging in a display out would cause a lock up (kernel panic); here are some patches to mitigate that (credit RehabMan). If you're having these lock ups, try the following sets of patches (try both, but only one set at a time):
con1 as 105, con2 as 204, both HDMI
KeyTypeValueframebuffer-con1-enable
Data
01000000
framebuffer-con1-alldata
Data
01050A00 00080000 87010000
framebuffer-con2-enable
Data
01000000
framebuffer-con2-alldata
Data
02040A00 00080000 87010000
con1 as 105, con2 as 306, HDMI and DP
KeyTypeValueframebuffer-con1-enable
Data
01000000
framebuffer-con1-alldata
Data
01050A00 00080000 87010000
framebuffer-con2-enable
Data
01000000
framebuffer-con2-alldata
Data
03060A00 00040000 87010000
PciRoot(0x0)/Pci(0x1b,0x0)
layout-id
Applies AppleALC audio injection, you'll need to do your own research on which codec your motherboard has and match it with AppleALC's layout. AppleALC Supported Codecs (opens new window).
You can delete this property outright as it's unused for us at this time
For us, we'll be using the boot argument alcid=xxx
instead to accomplish this. alcid
will override all other layout-IDs present. More info on this is covered in the Post-Install Page(opens new window)
#Delete
Removes device properties from the map, for us we can ignore this
#Kernel

#Add
Here's where we specify which kexts to load, in what specific order to load, and what architectures each kext is meant for. By default we recommend leaving what ProperTree has done, however for 32-bit CPUs please see below:
#Emulate
Needed for spoofing unsupported CPUs like Pentiums and Celerons
Cpuid1Mask: Leave this blank
Cpuid1Data: Leave this blank
#Force
Used for loading kexts off system volume, only relevant for older operating systems where certain kexts are not present in the cache(ie. IONetworkingFamily in 10.6).
For us, we can ignore.
#Block
Blocks certain kexts from loading. Not relevant for us.
#Patch
Patches both the kernel and kexts.
#Quirks
Info
Settings relating to the kernel, for us we'll be enabling the following:
AppleXcpmCfgLock
YES
Not needed if CFG-Lock
is disabled in the BIOS
DisableIoMapper
YES
Not needed if VT-D
is disabled in the BIOS
LapicKernelPanic
NO
HP Machines will require this quirk
PanicNoKextDump
YES
PowerTimeoutKernelPanic
YES
XhciPortLimit
YES
Disable if running macOS 11.3+
#Scheme
Settings related to legacy booting(ie. 10.4-10.6), for majority you can skip however for those planning to boot legacy OSes you can see below:
#Misc

#Boot
Info
HideAuxiliary
YES
Press space to show macOS recovery and other auxiliary entries
#Debug
Info
Helpful for debugging OpenCore boot issues(We'll be changing everything but DisplayDelay
):
AppleDebug
YES
ApplePanic
YES
DisableWatchDog
YES
Target
67
#Security
Info
Security is pretty self-explanatory, do not skip. We'll be changing the following:
AllowSetDefault
YES
BlacklistAppleUpdate
YES
ScanPolicy
0
SecureBootModel
Default
Leave this as Default
for OpenCore to automatically set the correct value corresponding to your SMBIOS. The next page goes into more detail about this setting.
Vault
Optional
This is a word, it is not optional to omit this setting. You will regret it if you don't set it to Optional, note that it is case-sensitive
#Serial
Used for serial debugging (Leave everything as default).
#Tools
Used for running OC debugging tools like the shell, ProperTree's snapshot function will add these for you.
#Entries
Used for specifying irregular boot paths that can't be found naturally with OpenCore.
Won't be covered here, see 8.6 of Configuration.pdf (opens new window)for more info
#NVRAM

#Add
4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14
Used for OpenCore's UI scaling, default will work for us. See in-depth section for more info
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102
OpenCore's NVRAM GUID, mainly relevant for RTCMemoryFixup users
7C436110-AB2A-4BBB-A880-FE41995C9F82
System Integrity Protection bitmask
General Purpose boot-args:
-v
This enables verbose mode, which shows all the behind-the-scenes text that scrolls by as you're booting instead of the Apple logo and progress bar. It's invaluable to any Hackintosher, as it gives you an inside look at the boot process, and can help you identify issues, problem kexts, etc.
debug=0x100
This disables macOS's watchdog which helps prevents a reboot on a kernel panic. That way you can hopefully glean some useful info and follow the breadcrumbs to get past the issues.
keepsyms=1
This is a companion setting to debug=0x100 that tells the OS to also print the symbols on a kernel panic. That can give some more helpful insight as to what's causing the panic itself.
alcid=1
Used for setting layout-id for AppleALC, see supported codecs (opens new window)to figure out which layout to use for your specific system. More info on this is covered in the Post-Install Page(opens new window)
GPU-Specific boot-args:
-wegnoegpu
Used for disabling all other GPUs than the integrated Intel iGPU, useful for those wanting to run newer versions of macOS where their dGPU isn't supported
-igfxnotelemetryload
Prevents iGPU telemetry from loading. iGPU telemetry may cause a freeze during startup on certain laptops such as Chromebooks on macOS 10.15 and higher, see here (opens new window)for more information.
csr-active-config:
00000000
Settings for 'System Integrity Protection' (SIP). It is generally recommended to change this with
csrutil
via the recovery partition.csr-active-config by default is set to
00000000
which enables System Integrity Protection. You can choose a number of different values but overall we recommend keeping this enabled for best security practices. More info can be found in our troubleshooting page: Disabling SIP
run-efi-updater:
No
This is used to prevent Apple's firmware update packages from installing and breaking boot order; this is important as these firmware updates (meant for Macs) will not work.
prev-lang:kbd: <>
Needed for non-latin keyboards in the format of
lang-COUNTRY:keyboard
, recommended to keep blank though you can specify it(Default in Sample config is Russian):American:
en-US:0
(656e2d55533a30
in HEX)Full list can be found in AppleKeyboardLayouts.txt(opens new window)
Hint:
prev-lang:kbd
can be changed into a String so you can inputen-US:0
directly instead of converting to HEXHint 2:
prev-lang:kbd
can be set to a blank variable (eg.<>
) which will force the Language Picker to appear instead at first boot up.
prev-lang:kbd
String
en-US:0
#Delete
Forcibly rewrites NVRAM variables, do note that Add
will not overwrite values already present in NVRAM so values like boot-args
should be left alone.
LegacySchema
Used for assigning NVRAM variables, used with
OpenVariableRuntimeDxe.efi
. Only needed for systems without native NVRAM
WriteFlash: YES
Enables writing to flash memory for all added variables.
#PlatformInfo

Info
For setting up the SMBIOS info, we'll use CorpNewt's GenSMBIOS (opens new window)application.
For this Kaby Lake example, we'll chose the MacBookPro14,1 SMBIOS - this is done intentionally for compatibility's sake. The typical breakdown is as follows:
MacBookPro14,1
Dual Core 15W(Low End)
iGPU: Iris Plus 640
13"
No
MacBookPro14,2
Dual Core 15W(High End)
iGPU: Iris Plus 650
13"
Yes
MacBookPro14,3
Quad Core 45W
iGPU: HD 630 + dGPU: Radeon Pro 555X/560X
15"
Yes
iMac18,1
NUC Systems
iGPU: Iris Plus 640
N/A
No
Run GenSMBIOS, pick option 1 for downloading MacSerial and Option 3 for selecting out SMBIOS. This will give us an output similar to the following:
#######################################################
# MacBookPro14,1 SMBIOS Info #
#######################################################
Type: MacBookPro14,1
Serial: C02Z2CZ5H7JY
Board Serial: C02928701GUH69FFB
SmUUID: AA043F8D-33B6-4A1A-94F7-46972AAD0607
The Type
part gets copied to Generic -> SystemProductName.
The Serial
part gets copied to Generic -> SystemSerialNumber.
The Board Serial
part gets copied to Generic -> MLB.
The SmUUID
part gets copied to Generic -> SystemUUID.
We set Generic -> ROM to either an Apple ROM (dumped from a real Mac), your NIC MAC address, or any random MAC address (could be just 6 random bytes, for this guide we'll use 11223300 0000
. After install follow the Fixing iServices (opens new window)page on how to find your real MAC Address)
Reminder that you need an invalid serial! When inputting your serial number in Apple's Check Coverage Page (opens new window), you should get a message such as "Unable to check coverage for this serial number."
Automatic: YES
Generates PlatformInfo based on Generic section instead of DataHub, NVRAM, and SMBIOS sections
#Generic
#UEFI

ConnectDrivers: YES
Forces .efi drivers, change to NO will automatically connect added UEFI drivers. This can make booting slightly faster, but not all drivers connect themselves. E.g. certain file system drivers may not load.
#Drivers
Add your .efi drivers here.
Only drivers present here should be:
HfsPlus.efi
OpenRuntime.efi
#APFS
By default, OpenCore only loads APFS drivers from macOS Big Sur and newer. If you are booting macOS Catalina or earlier, you may need to set a new minimum version/date. Not setting this can result in OpenCore not finding your macOS partition!
macOS Sierra and earlier use HFS instead of APFS. You can skip this section if booting older versions of macOS.
APFS Versions
Both MinVersion and MinDate need to be set if changing the minimum version.
High Sierra (10.13.6
)
748077008000000
20180621
Mojave (10.14.6
)
945275007000000
20190820
Catalina (10.15.4
)
1412101001000000
20200306
No restriction
-1
-1
#Audio
Related to AudioDxe settings, for us we'll be ignoring(leave as default). This is unrelated to audio support in macOS.
For further use of AudioDxe and the Audio section, please see the Post Install page: Add GUI and Boot-chime(opens new window)
#Input
Related to boot.efi keyboard passthrough used for FileVault and Hotkey support, leave everything here as default as we have no use for these quirks. See here for more details: Security and FileVault(opens new window)
#Output
Relating to OpenCore's visual output, leave everything here as default as we have no use for these quirks.
#ProtocolOverrides
Mainly relevant for Virtual machines, legacy macs and FileVault users. See here for more details: Security and FileVault(opens new window)
#Quirks
Info
Relating to quirks with the UEFI environment, for us we'll be changing the following:
ReleaseUsbOwnership
YES
UnblockFsConnect
NO
Needed mainly by HP motherboards
#ReservedMemory
Used for exempting certain memory regions from OSes to use, mainly relevant for Sandy Bridge iGPUs or systems with faulty memory. Use of this quirk is not covered in this guide
Last updated