This is due to missing the MEMORY_ATTRIBUTE_TABLE and such we recommend disabling RebuildAppleMemoryMap and enabling EnableWriteUnprotector. However, due to issues with OEMs not using the latest EDKII builds you may find that the above combo will result in early boot failures.This quirk and RebuildAppleMemoryMap can commonly conflict, recommended to enable the latter on newer platforms and disable this entry.Enables slide variables to be used in safe mode.Fixes UEFI runtime services like date, time, NVRAM, power control, etc.X470 and B450 with late 2020 BIOS updates also require this disabled Newer BIOS versions of X570 also require this off Note B550, A520 and TRx40 boards should disable this. Settings relating to boot.efi patching and firmware fixes, for us, we need to change the following: Quirk This section is allowing spaces to be passthrough to macOS that are generally ignored, useful when paired with DevirtualiseMmio # Quirks This section is dedicated to quirks relating to boot.efi patching with OpenRuntime, the replacement for AptioMemoryFix.efi # MmioWhitelist Settings relating to ACPI, leave everything here as default as we have no use for these quirks. This is a much cleaner solution as this will allow us to boot Windows and other OSes with OpenCore # Quirks For us, our patches are handled by our SSDTs. This section allows us to dynamically modify parts of the ACPI (DSDT, SSDT, etc.) via OpenCore. This blocks certain ACPI tables from loading, for us we can ignore this. aml extension(Assembled) and will go into the EFI/OC/ACPI folder and must be specified in your config under ACPI -> Add as well. So if present, remove the entry for it in your ist and under EFI/OC/ACPI.įor 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. Note that you should not add your generated DSDT.aml here, it is already in your firmware. You can find a prebuilt here: SSDT-CPUR.aml (opens new window) Guide on making them found here: Getting started with ACPI (opens new window) Required SSDTsįixes both the embedded controller and USB power, see Getting Started With ACPI Guide (opens new window) for more details.įixes CPU definitions with B550 and A520 motherboards, do not use if you don't have an AMD B550 or A520 system. And with our system, it's even required to boot. 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. 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. Supporting AMD Family 15h, 16h, 17h and 19hĪnd read this guide more than once before setting up OpenCore and make sure you have it set up correctly.Needed for booting macOS on AMD hardware(save these for later, we'll go over how to use them below).See previous section on how to obtain: ist Setup.Now with all that, a quick reminder of the tools we need DO NOT USE CONFIGURATORS, these rarely respect OpenCore's configuration and even some like Mackie's will add Clover properties and corrupt plists!.The ist cannot be used As-Is, you must configure it to your system.If the guide doesn't mention the option, leave it at default. All properties must be defined, there are no default OpenCore will fall back on so do not delete sections unless told explicitly so.This also means if you have issues, review your config settings to make sure they're correct. It just takes some time but this guide will tell you how to configure everything, you won't be left in the cold. # Ryzen and Threadripper(17h and 19h) Support Getting started with ACPI (opens new window).When, during context creation, CL_CONTEXT_OFFLINE_DEVICES_AMD is passed in the context properties, all supported devices, whether online or offline, are reported and can be used to create OpenCL binary images. To generate binary images offline, it is necessary to access the compiler for everyĭevice that the runtime supports, even if the device is currently not installed on the system. But what then? In AMD's OpenCL Programming User Guide, it says: Offline compilation for AMD and NVIDIA OpenCL Kernels without cards installedĪnd the answer suggesting I create the OpenCL context with CL_CONTEXT_OFFLINE_DEVICES_AMD. I want to compile an OpenCL kernel for a certain AMD GPU - which is not available on my machine -, so that later I'm able to just load and run it when that GPU is present.

Modify osx kernel for amd