1. Kernel For Mac Os X Amd Intel
2. Kernel For Mac Os X Amd Desktop

1. Some AMD Radeon cards wont boot without it, PCIRootUID=1 or PCIRootUID=0. Arch=i386 Forces Mac OS X to boot into 32-bit mode. Useful for older PC’s if CPU or graphics card isn’t fully supported in OSX 64 bit mod. No longer works in OS X Mountain Lion which is 64 bit only. Arch=x8664 Allows Mac OS X to boot into 64-bit mode.
2. This page is a list of patched kernels for OS X. You are encouraged to add any missing information to help make this list complete! Please only add kernel-CPU combinations you or someone else have tested; don't just add a a CPU or kernel because it exists. Two types of patches exist: binary and source.
3. AMD Kernel for OS X Mavericks was Compiled as a joint effort from AnV, Bronya, and Sinetek. This kernel allows full x64 support on all AMD CPUs. Ryzen CPUs Support is not confirmed. This Kernel can be used with following versions of OS X Mavericks.
4. Darwin is an open-source Unix-like operating system first released by Apple Inc. It is composed of code developed by Apple, as well as code derived from NeXTSTEP, BSD, Mach, and other free software projects. Darwin forms the core set of components upon which macOS (previously OS X and Mac OS X), iOS, watchOS, tvOS, and iPadOS are based. It is mostly POSIX-compatible, but has never.

AMD Kernel for OS X Lion was Compiled by Bronya this kernel allows full x64 support on all AMD CPUs except Ryzen CPUs. This Kernel can be used with following versions.

# 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

• ProperTree
  • Universal plist editor
• GenSMBIOS
  • For generating our SMBIOS data
• Sample/config.plist
  • See previous section on how to obtain: config.plist Setup
• AMD Kernel Patches
  • Needed for booting macOS on AMD hardware(save these for later, we'll go over how to use them below)
  • Ryzen/Threadripper(17h) (Supports 10.13, 10.14, and 10.15)

And 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, 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

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 ACPIpage. 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

This section allows us to dynamically modify parts of the ACPI (DSDT, SSDT, etc.) via OpenCore. For us, our patches are handled by our SSDTs. This is a much cleaner solution as this will allow us to boot Windows and other OSes with OpenCore

# 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 passthrough to macOS that are generally ignored, useful when paired with DevirtualiseMmio

# Quirks

Info

Settings relating to boot.efi patching and firmware fixes, for us, we need to change the following:

• AvoidRuntimeDefrag: YES
  • Fixes UEFI runtime services like date, time, NVRAM, power control, etc
• EnableWriteUnprotector: NO
  • This quirk and RebuildAppleMemoryMap can commonly conflict, recommended to enable the latter on newer platforms and disable this entry.
  • 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 is due to missing the MEMORY_ATTRIBUTE_TABLE and such we recommend disabling RebuildAppleMemoryMap and enabling EnableWriteUnprotector. More info on this is covered in the troubleshooting section
• RebuildAppleMemoryMap: YES
  • Generates Memory Map compatible with macOS, can break on some laptop OEM firmwares so if you receive early boot failures disable this
• SetupVirtualMap: YES
  • Fixes SetVirtualAddresses calls to virtual addresses
  • B550, A520 and TRx40 boards should disable this quirk
• SyncRuntimePermissions: YES
  • Fixes alignment with MAT tables and required to boot Windows and Linux with MAT tables, also recommended for macOS. Mainly relevant for RebuildAppleMemoryMap users

# DeviceProperties

# Add

Sets device properties from a map.

By default, the Sample.plist has this section set for iGPU and Audio. We have no iGPU so PciRoot PciRoot(0x0)/Pci(0x2,0x0) can be removed from Add section. For audio we'll be setting the layout in the boot-args section, so removal of PciRoot(0x0)/Pci(0x1b,0x0) is also recommended from both Add and Block sections

TL;DR, delete all the PciRoot's here as we won't be using this section.

# 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:

The main thing you need to keep in mind is:

• Load order
  • Remember that any plugins should load after its dependencies
  • This means kexts like Lilu must come before VirtualSMC, AppleALC, WhateverGreen, etc

A reminder that ProperTree users can run Cmd/Ctrl + Shift + R to add all their kexts in the correct order without manually typing each kext out.

• Arch
  • Architectures supported by this kext
  • Currently supported values are Any, i386 (32-bit), and x86_64 (64-bit)
• BundlePath
  • Name of the kext
  • ex: Lilu.kext
• Enabled
  • Self-explanatory, either enables or disables the kext
• ExecutablePath
  • Path to the actual executable is hidden within the kext, you can see what path your kext has by right-clicking and selecting Show Package Contents. Generally, they'll be Contents/MacOS/Kext but some have kexts hidden within under Plugin folder. Do note that plist only kexts do not need this filled in.
  • ex: Contents/MacOS/Lilu
• MinKernel
  • Lowest kernel version your kext will be injected into, see below table for possible values
  • ex. 12.00.00 for OS X 10.8
• MaxKernel
  • Highest kernel version your kext will be injected into, see below table for possible values
  • ex. 11.99.99 for OS X 10.7
• PlistPath
  • Path to the info.plist hidden within the kext
  • ex: Contents/Info.plist

# Emulate

Info

Needed for spoofing unsupported CPUs like Pentiums and Celerons and to disable CPU power management on unsupported CPUs (such as AMD CPUs)

• CpuidMask: Leave this blank
  • Mask for fake CPUID
• CpuidData: Leave this blank
  • Fake CPUID entry
• DummyPowerManagement: YES
  • New alternative to NullCPUPowerManagement, required for all AMD CPU based systems as there's no native power management. Intel can ignore
• MinKernel: Leave this blank
  • Lowest kernel version the above patches will be injected into, if no value specified it'll be applied to all versions of macOS. See below table for possible values
  • ex. 12.00.00 for OS X 10.8
• MaxKernel: Leave this blank
  • Highest kernel version the above patches will be injected into, if no value specified it'll be applied to all versions of macOS. See below table for possible values
  • ex. 11.99.99 for OS X 10.7

# 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

This is where the AMD kernel patching magic happens. Please do note that KernelToPatch and MatchOS from Clover becomes Kernel and MinKernel/ MaxKernel in OpenCore, you can find pre-made patches by AlGrey(algrey#9303).

Kernel patches:

• Ryzen/Threadripper(17h) (10.13, 10.14, and 10.15)

To merge:

• Open both files,
• Delete the Kernel -> Patch section from config.plist
• Copy the Kernel -> Patch section from patches.plist
• Paste into where old patches were in config.plist

# Quirks

Info

Settings relating to the kernel, for us we'll be enabling the following:

• AppleCpuPmCfgLock: NO

  • Only needed when CFG-Lock can't be disabled in BIOS. AMD users can ignore

• AppleXcpmCfgLock: NO

  • Only needed when CFG-Lock can't be disabled in BIOS. AMD users can ignore

• AppleXcpmExtraMsrs: NO

  • Disables multiple MSR access needed for unsupported CPUs like Pentiums and certain Xeons

• CustomSMBIOSGuid: NO

  • Performs GUID patching for UpdateSMBIOSMode set to Custom. Usually relevant for Dell laptops
  • Enabling this quirk in tandem with `PlatformInfo -> UpdateSMBIOSMode -> Custom will disable SMBIOS injection into 'non-Apple' OSes however we do not endorse this method as it breaks Bootcamp compatibility. Use at your own risk.

• DisableIoMapper: NO

  • AMD doesn't have DMAR or VT-D support so irrelevant

• DisableLinkeditJettison: YES

  • Allows Lilu and others to have more reliable performance without keepsyms=1

• DisableRtcChecksum: NO

  • Prevents AppleRTC from writing to primary checksum (0x58-0x59), required for users who either receive BIOS reset or are sent into Safe mode after reboot/shutdown

• ExtendBTFeatureFlags NO

  • Helpful for those having continuity issues with non-Apple/non-Fenvi cards

• LapicKernelPanic: NO

  • Disables kernel panic on AP core lapic interrupt, generally needed for HP systems. Clover equivalent is Kernel LAPIC

• LegacyCommpage: NO

  • Resolves SSSE3 requirement for 64 Bit CPUs in macOS, mainly relevant for 64-Bit Pentium 4 CPUs(ie. Prescott)

• PanicNoKextDump: YES

  • Allows for reading kernel panics logs when kernel panics occur

• PowerTimeoutKernelPanic: YES

  • Helps fix kernel panics relating to power changes with Apple drivers in macOS Catalina, most notably with digital audio.

• XhciPortLimit: YES

  • This is actually the 15 port limit patch, don't rely on it as it's not a guaranteed solution for fixing USB. A more proper solution for AMD can be found here: AMD USB Mapping

# 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:

• FuzzyMatch: True

  • Used for ignoring checksums with kernelcache, instead opting for the latest cache available. Can help improve boot performance on many machines in 10.6

• KernelArch: x86_64

  • Set the kernel's arch type, you can choose between Auto, i386 (32-bit), and x86_64 (64-bit).
  • If you're booting older OSes which require a 32-bit kernel(ie. 10.4 and 10.5) we recommend to set this to Auto and let macOS decide based on your SMBIOS. See below table for supported values:
    • 10.4-10.5 — x86_64, i386 or i386-user32
      • i386-user32 refers 32-bit userspace, so 32-bit CPUs must use this(or CPUs missing SSSE3)
      • x86_64 will still have a 32-bit kernelspace however will ensure 64-bit userspace in 10.4/5
    • 10.6 — i386, i386-user32, or x86_64
    • 10.7 — i386 or x86_64
    • 10.8 or newer — x86_64

• KernelCache: Auto

  • Set kernel cache type, mainly useful for debugging and so we recommend Auto for best support

# Misc

# Boot

Settings for boot screen (Leave everything as default).

# Debug

Info

Helpful for debugging OpenCore boot issues(We'll be changing everything butDisplayDelay):

• AppleDebug: YES
  • Enables boot.efi logging, useful for debugging. Note this is only supported on 10.15.4 and newer
• ApplePanic: YES
  • Attempts to log kernel panics to disk
• DisableWatchDog: YES
  • Disables the UEFI watchdog, can help with early boot issues
• DisplayLevel: 2147483650
  • Shows even more debug information, requires debug version of OpenCore
• SerialInit: NO
  • Needed for setting up serial output with OpenCore
• SysReport: NO
  • Helpful for debugging such as dumping ACPI tables
  • Note that this is limited to DEBUG versions of OpenCore
• Target: 67
  • Shows more debug information, requires debug version of OpenCore

These values are based of those calculated in OpenCore debugging

# Security

Info

Security is pretty self-explanatory, do not skip. We'll be changing the following:

• AllowNvramReset: YES
  • Allows for NVRAM reset both in the boot picker and when pressing Cmd+Opt+P+R
• AllowSetDefault: YES
  • Allow CTRL+Enter and CTRL+Index to set default boot device in the picker
• ApECID: 0
  • Used for netting personalized secure-boot identifiers, currently this quirk is unreliable due to a bug in the macOS installer so we highly encourage you to leave this as default.
• AuthRestart: NO
  • Enables Authenticated restart for FileVault 2 so password is not required on reboot. Can be considered a security risk so optional
• BootProtect: Bootstrap
  • Allows the use of Bootstrap.efi inside EFI/OC/Bootstrap instead of BOOTx64.efi, useful for those wanting to either boot with rEFInd or avoid BOOTx64.efi overwrites from Windows. Proper use of this quirks is covered here: Using Bootstrap.efi
• DmgLoading: Signed
  • Ensures only signed DMGs load
• ExposeSensitiveData: 6
  • Shows more debug information, requires debug version of OpenCore
• Vault: Optional
  • We won't be dealing vaulting so we can ignore, you won't boot with this set to Secure
  • 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
• ScanPolicy: 0
  • 0 allows you to see all drives available, please refer to Security section for further details. Will not boot USB devices with this set to default
• SecureBootModel: Default
  • Enables Apple's secure boot functionality in macOS, please refer to Security section for further details.
  • Note: Users may find upgrading OpenCore on an already installed system can result in early boot failures. To resolve this, see here: Stuck on OCB: LoadImage failed - Security Violation

# 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 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

Booter Path, mainly used for UI Scaling

• UIScale:

  • 01: Standard resolution
  • 02: HiDPI (generally required for FileVault to function correctly on smaller displays)

• DefaultBackgroundColor: Background color used by boot.efi

  • 00000000: Syrah Black
  • BFBFBF00: Light Gray

4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102

OpenCore's NVRAM GUID, mainly relevant for RTCMemoryFixup users

• rtc-blacklist: <>
  • To be used in conjunction with RTCMemoryFixup, see here for more info: Fixing RTC write issues
  • Most users can ignore this section

7C436110-AB2A-4BBB-A880-FE41995C9F82

System Integrity Protection bitmask

• General Purpose boot-args:

• GPU-Specific boot-args:

• 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
  • Hint: prev-lang:kbd can be changed into a String so you can input en-US:0 directly instead of converting to HEX

# Delete

Info

Forcibly rewrites NVRAM variables, do note that Addwill not overwrite values already present in NVRAM so values like boot-args should be left alone. For us, we'll be changing the following:

• LegacyEnable: NO

  • Allows for NVRAM to be stored on nvram.plist, needed for systems without native NVRAM

• LegacyOverwrite: NO

  • Permits overwriting firmware variables from nvram.plist, only needed for systems without native NVRAM

• LegacySchema

  • Used for assigning NVRAM variables, used with LegacyEnable set to YES

• 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 application.

For this example, we'll choose the iMacPro1,1 SMBIOS but some SMBIOS play with certain GPUs better than others:

• iMacPro1,1: AMD RX Polaris and newer
• MacPro7,1: AMD RX Polaris and newer(Note that MacPro7,1 is also a Catalina exclusive)
• MacPro6,1: AMD R5/R7/R9 and older
• iMac14,2: Nvidia Kepler and newer

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:

The order is Product | Serial | Board Serial (MLB)

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 page on how to find your real MAC Address)

Reminder that you want either an invalid serial or valid serial numbers but those not in use, you want to get a message back like: 'Invalid Serial' or 'Purchase Date not Validated'

Automatic: YES

• Generates PlatformInfo based on Generic section instead of DataHub, NVRAM, and SMBIOS sections

# Generic

• AdviseWindows: NO

  • Used for when the EFI partition isn't first on the Windows drive

• SystemMemoryStatus: Auto

  • Sets whether memory is soldered or not in SMBIOS info, purely cosmetic and so we recommend Auto

• ProcessorType: 0

  • Set to 0 for automatic type detection, however this value can be overridden if desired. See AppleSmBios.h for possible values

• SpoofVendor: YES

  • Swaps vendor field for Acidanthera, generally not safe to use Apple as a vendor in most case

• UpdateDataHub: YES

  • Update Data Hub fields

• UpdateNVRAM: YES

  • Update NVRAM fields

• UpdateSMBIOS: YES

  • Updates SMBIOS fields

• UpdateSMBIOSMode: Create

  • Replace the tables with newly allocated EfiReservedMemoryType, use Custom on Dell laptops requiring CustomSMBIOSGuid quirk
  • Setting to Custom with CustomSMBIOSGuid quirk enabled can also disable SMBIOS injection into 'non-Apple' OSes however we do not endorse this method as it breaks Bootcamp compatibility. Use at your own risk

# 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

Settings related to the APFS driver, leave everything here as default.

# 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

# 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

# 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

# Quirks

Info

Relating to quirks with the UEFI environment, for us we'll be changing the following:

• DeduplicateBootOrder: YES

  • Request fallback of some Boot prefixed variables from OC_VENDOR_VARIABLE_GUID to EFI_GLOBAL_VARIABLE_GUID. Used for fixing boot options.

• RequestBootVarRouting: YES

  • Redirects AptioMemoryFix from EFI_GLOBAL_VARIABLE_GUID to OC_VENDOR_VARIABLE_GUID. Needed for when firmware tries to delete boot entries and is recommended to be enabled on all systems for correct update installation, Startup Disk control panel functioning, etc.

• UnblockFsConnect: NO

  • Some firmware block partition handles by opening them in By Driver mode, which results in File System protocols being unable to install. Mainly relevant for HP systems when no drives are listed

# 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

# Cleaning up

And now you're ready to save and place it into your EFI under EFI/OC.

For those having booting issues, please make sure to read the Troubleshooting section first and if your questions are still unanswered we have plenty of resources at your disposal:

Kernel For Mac Os X Amd Intel

Sanity check:

So thanks to the efforts of Ramus, we also have an amazing tool to help verify your config for those who may have missed something:

Note that this tool is neither made nor maintained by Dortania, any and all issues with this site should be sent here: Sanity Checker Repo

# AMD BIOS Settings

• Note: Most of these options may not be present in your firmware, we recommend matching up as closely as possible but don't be too concerned if many of these options are not available in your BIOS

# Disable

• Fast Boot
• Secure Boot
• Serial/COM Port
• Parallel Port
• Compatibility Support Module (CSM)(Must be off, GPU errors like gIO are common when this option in enabled)

Special note for 3990X users: macOS currently does not support more than 64 threads in the kernel, and so will kernel panic if it sees more. The 3990X CPU has 128 threads total and so requires half of that disabled. We recommend disabling hyper threading in the BIOS for these situations.

# Enable

• Above 4G decoding(This must be on, if you can't find the option then add npci=0x2000 to boot-args. Do not have both this option and npci enabled at the same time)
• EHCI/XHCI Hand-off
• OS type: Windows 8.1/10 UEFI Mode
• SATA Mode: AHCI

Due to the excellent work of Gabriel L.Somlo it is possible to run the emulated Mac OS X on Linux under Qemu/KVM. The changes seem to be minimal, and the operating system emulation works well – as long as you have the Intel CPU, that’s it.

Kernel For Mac Os X Amd Desktop

If you have only the AMD CPU, the emulation only works without the KVM, i.e. when you run qemu without the -enable-kvm option. With this option the emulation hangs on the grey screen with Apple logo. Enabling the verbose boot (-v option to Chameleon) shows an empty black screen instead.

This happens because Qemu does not properly pass the CPU vendor to the virtualized CPU when using KVM. For example, booting the Linux DVD installation with the following options:

and running cat /proc/cpuinfo | grep vendor prints the following:

As you see, despite your host CPU being AMD, qemu properly emulates the Intel CPU and sets the options correctly.

However if you add -enable-kvm switch, and run:

and run cat /proc/cpuinfo | grep vendor you’ll see a rather ridiculous picture:

So the CPU model does not change. Since Mac OS X is supposed to only run on Intel CPU, we can assume Mac OS gets really confused when it does cpuid, and halts.

Now, there is a reason why Qemu is doing this. The reason is that the syscall emulation uses different instructions on AMD and Intel CPUs. So if the virtualized guest is specific to the CPU, and This is likely a bug in qemu for which the patch is submitted, but until it makes it upstream, you can apply the patch yourself:

This patch forces the CPU vendor copy even when KVM is being used and a non-Qemu CPU is specified. With this patch Mac OS X installs and runs on the AMD CPU under kvm.

Update: the patch is not needed, as Hin-Tak Leung pointed out in comments,you can pass the vendor as string, and KVM would respect that: