TABLE of CONTENTS (click to reveal)
In this Section, you can:
- Add Audio Layout IDs
- Fix USB issues
- Add Fake IDs to enable otherwise unsupported devices
- Add or modify Devices (via
Devices>Properties) - Add Framebuffer Patches (via
Devices>Properties)
A group of parameters for masking your devices as natively supported ones by macOS.
Examples:
-
AMD RadeonHD 7850 has the DeviceID=
0x6819, which is not supported by OSX 10.8, but it supports DeviceID=0x6818instead. So add0x6818to theATIfield to change its ID. Next, it's necessary to inject this fake somehow. For video cards there are two ways: under "Graphics", enableInject ATIor under "ACPI" enableFixDisplay. -
NVidia GTX 660: DeviceID=
0x1183. The card works, but there is noAGPM(Apple Graphics Power Management) for it. Add ID0x0FE0in theNVidiafield and enabled theFixDisplaypatch to inject it into theDSDT. -
WiFi: A Dell Wireless 1595 card has the DeviceID=
0x4315, but the real one is by Broadcom, which supports chips 4312, 4331 and some others. So enter the device ID of a supported card and enable theFixAirportpatch in theACPIsection to inject the fake ID into theDSDT. -
The common Marvell 80E8056 Network Card (DeviceID=
0x4353) just doesn't work, but it works with theAppleYukon2driver if you change the ID to0x4363. Combine withFixLanto enable it. -
IMEI: This device works with Intel HD3000 and HD4000 iGPUs. However, it is not certain that your chipset has the correct ID. The substitutions are as follows (combine withAddIMEIFix):- Sandy Bridge =
0x1C3A8086 - Ivy Bridge =
0x1E3A8086 - Haswell =
0x8C3A8086
This mask works in two ways: when injecting or with the
DSDTpatch. However, if you don't want to fully inject it in the way Clover does it, you can use theNoDefaultPropertiesoption instead. - Sandy Bridge =
Injects USB properties if enabled. Leave disabled if you want to inject them yourself via Properties.
Enable to prevent the USB controller from waking the system involuntarily. If you want to wake the system via USB mouse, disable it. But be prepared that your computer will wake up spontaneously, e.g. from a built-in camera, etc.
In order for the USB controller to work in macOS, it has to be disconnected from the BIOS first, before the Darwin kernel is started. Since this is only required for legacy boot, this option is disabled by default – it is not required for UEFI boot, since UEFI based systems usually have an option for enabling XHCI/EHCI handoff. But there are cases where you cannot enable XCHI/EHCI handoff in the BIOS (usually on Laptops) where FixOwnership comes in handy. For Desktops PCs it's usually not needed since XHCI/EHCI handoff can be enabled in the BIOS.
In OpenCore you find this setting under UEFI/Quirks/ReleaseUSBOwnership.
Increases current on a USB controller to charge devices – disabled by default. Irrelevant for macOS 10.11 and newer. For Skylake and newer CPUs, add SSDT-USBX instead (usually integrated in SSDT-EC-USB).
No information available in documentation.
Enter/set the Layout-ID for AppleALC.kext. See the documentation for your mainboard to find out which CODEC is used and then check the list of supported CODECS to pick the correct Layout-ID. Not necessary when VoodooHDA.kext is used.
Other options available from the dropdown menu are:
No: Nothing is injected. For example, if you set the Layout-ID yourself via DevicePropertiesDetect: Automatic detection of an installed sound card in order to use its ID as a layout. Actually nonsense, but very popular.
Affects the AppleHDA driver and seems to solve the problem with clicks and pops after waking up. There is little evidence of the effectiveness of the patch, though.
Initialize the audio codec, if enabled. This behavior can be observed after rebooting from Windows to Mac. In OpenCore, the equivalent feature is located under UEFI/Audio/ResetTrafficClass.
This is where Clover and Clover Configurator get really confusing. Because there are were 4 different ways to inject device Properties. These are were:
AddProperties- Properties [HEX]
Arbitrary (Tab)- Devices/Properties (Tab)
IMPORTANT: With the release of Clover r5146, AddProperties and Arbitrary were retired, since using Devices/Properties has become the de facto standard method to add device properties. Existing entries in Arbitrary and AddProperties will still be applied if present, but it's recommended to convert them to regular Device Properties instead.
I think removing the unused methods was a good choice since it will reduce confusion and makes transferring device properties between OpenCore and Clover configs a lot easier
Nowadays, using the Devices > Properties tab next to Arbitrary tab – which is displayed by default (which sucks) is the recommended and de facto standard method for adding device properties.
This method is used for injecting properties of devices into macOS based on their PCI path. It can be utilized for injecting all sorts of parameters, including: Device IDs (so macOS sees the device), Framebuffer patches for on-board Graphics Cards, Audio layouts for sound cards, Wi-Fi and Ethernet Cards, configuring Active State Power Management (ASPM), etc. It works exactly the same way as the DeviceProperties section in OpenCore.
In a plist editor, the structure and hierarchy of this section looks like this:
In Clover Configurator, this hierarchy is represented by a split view:
On the left, you can add entries as PCI paths (as <dict>). On the right, you can add properties for said devices (as <Data>, <String> or <Number>) which will then be applied to them on boot. On the bottom, there's also a handy dropdown menu with a list of common PCI Devices to choose from, so you don't have to jump through hoops to find out the PCI path of your iGPU for example.
This field creates a simple string in the config in the Devices Section if a hex value is entered:
Note
As soon as you add a Device under to the Properties Tab (next to Arbitrary), this key will be deleted.
Adding entries to this list creates an <Array> AddProperties and a <Dictionary> for the listed device. This is how the actual structure of the array looks like when viewed with a Plist Editor:
The value has to be entered either as a <data> or a hex string. So instead of alphanumerical values (ABC...) you have to use hex (0x414243). Convert via Plist Editor or Xcode. The first Device key determines which device this property will be added to.
The Arbitrary section is an array of dictionaries, each corresponding to one device with a given PCI address. To describe each device, a CustomProperties array consisting of Key/Value pairs is used. These Properties can be disabled by ticking the Disabled checkbox. You can enable or disable a property dynamically in the Clover menu.
Keymust be a<string>.Valuecan be a<string>,<integer>or<data>.
If enabled, all internal injection is replaced by entering a single string of properties, which corresponds to the Apple's APPLE_GETVAR_PROTOCOL injection method. A string could like this one which is used on real Macs: GUID={0x91BD12FE, 0xF6C3, 0x44FB, {0xA5, 0xB7, 0x51, 0x22, 0xAB, 0x30, 0x3A, 0xE0}}. Old hackers called these EFIstrings.
Prohibits the injection of default properties that are triggered when enabling the Inject feature. When set to true, the line for the injection is created, but does not contain any properties yet. This property could be a FakeID for example.
When combined with Inject → ATI, NoDefaultProperties will prevent the injection of most keys except those that are required for a FakeID to be applied to an AMD/ATI GPU (and probably iGPU).
Note
This method of injecting a FakeID is outdated. Use the Devices/Properties tab is recommended.
This parameter affects the injection properties of the sound transmitted over HDMI, as well as the DSDT patch. However, both VoodooHDA and AppleHDA sound drivers, do not fully work with HDMI Output. According to new information, VoodooHDA only works with NVIDIA's HDMI output, and as for AMD, Apple has created a new AppleGFXHDA.kext driver in 10.13+ systems.
Disable the injection of HDMI device properties altogether. Starting with r3262, there is a new way of injecting device properties not by name, but by their location on the PCI Bus.
Force enables High Precision Event Timer on systems where there isn't an option in the BIOS to enable it.
The key was introduced in r3298. In previous systems, the screen brightness was controlled by IntelBacklight.kext or ACPIBacklight.kext, but they didn't work in El Capitan. But it turned out to be very easy to do this in Clover at the stage of system startup, so no additional cakes were needed.
Note
This doesn't work with current macOS versions. Use a SSDT-PNLF.amlinstead. You can find one in the Samples Folder of the OpenCore Package.
By default, the built-in property is injected for the NIC. This parameter can be used to disable the injection.
AAPL,slot-name is a key which can be used in the Devices/Properties section. It allows device to be listed in the System Profiler. Adding this key is mostly cosmetic but some users swear that it's required for certain devices. This property that usually injected by the DSDT or property strings but this is a wrong way to do it.
The AAPL,slot-name property is set by the AppleSMBIOS system kext based on the _SUN (Slot User Number) ACPI property and DMI tables. That is, _SUN specifies an ID in the range of 0-255, where the SMBIOS type 9 table with the corresponding ID is located, from where the slot name and other properties are pulled from.