How to Enable AMD Graphics on CPUs with no AVX 2.0 Support on macOS
An EliteMacx86 Exclusive Guide - This guide covers the implementation of supported AMD GPU on CPUs with no AVX2.0 support on macOS. By following this guide, you'll be able to enable AMD Graphics on CPUs that lacks AVX2.0 support on macOS using Clover or OpenCore Bootloader with full QE/CI.Overview
Apple has been using a wide range of AMD Graphics Card for a long time. However, with the release of macOS Ventura, Apple has removed the support for the last Mac (Mac Pro6,1) that lacked the AVX2.0 CPU instruction. This means, CPUs that lacks AVX2.0 instruction, can no longer boot macOS Ventura natively as Apple has stripped the legacy non-AVX2.0 dyld shared caches from macOS Ventura. Due to removal of the legacy non-AVX2.0 support, the AMD Graphics drivers (Polaris, Vega and Navi) won't load on macOS Ventura on CPUs that lacks AVX 2.0 CPU instruction set. Starting with macOS Ventura, you'll require a CPU with AVX2.0 instruction support. This means you need atleast Haswell CPU in Intel lineup to boot macOS Ventura natively and to have acceleration for AMD Graphics.As a workaround, Cryptexfix does half of the job and then you'll have to use OCLP to patch the system in order to enable the graphics acceleration.
Requirements
Following are the requirements for enabling AMD Graphics on macOS. Please ensure you meet the requirements before proceeding with this guide.| CPU | macOS compatible CPU. See CPU Compatibility for more information. |
| Graphics | macOS Compatible AMD GPU. See AMD Graphics Compatibility for more information. |
| Kexts | Original Graphics kexts in S/L/E |
| macOS Version | macOS Ventura and later |
| Tools |
|
For CPUs with AVX2.0 support, see below:
GUIDE - How to Enable AMD Graphics in macOS [Clover/OpenCore]
How to Enable AMD Graphics in macOS An EliteMacx86 Exclusive Guide - This guide covers the implementation of supported AMD GPU on macOS. By following this guide, you'll be able to enable AMD Graphics on macOS using Clover or OpenCore Bootloader. Overview Apple has been using a wide range of...
elitemacx86.com
Enabling AMD Graphics on CPUS with no AVX2.0 Support on macOS
Following are the steps to enable AMD graphics on CPUs with no AVX2.0 support on macOS:STEP 1: Setup BIOS
The very first step is to set up BIOS to have the AMD GPU Enabled on your System. Follow the steps below to set up your BIOS for enabling AMD GPU.1. On your target computer, boot to BIOS. Refer to your motherboard's user manual for the BIOS Key.
2. Adjust the following settings described below:
| Settings | Value | Notes |
|---|---|---|
| Initial PCIe Output Display | PCIe/Auto/Enabled | Use one of the values available, depending on your BIOS options. This is usually present as VGA Priority on enterprise grade servers and workstations. |
| Intel Processor Graphics | Disabled/Enabled | If your processor has a compatible IGPU that is supported under macOS and you're using a compatible SMBIOS, then its recommended to set the IGPU to Enabled for the QuickSync feature. This is usually present as Internal Graphics option in BIOS. |
| CSM | Disabled | |
| PCIE ROM | UEFI/UEFI ROM only | This is usually present on enterprise grade servers and workstations and is available under PCIe/PCI/PnP Configuration option. |
| Above 4G Decoding | Enabled | If you're using an enterprise grade servers and workstation, it is recommended to Disable this option and use npci flag instead. |
| Re-Size BAR | Disabled | |
| Boot Mode Select | UEFI |
NOTES:
- The above settings are for Graphics only. See BIOS Settings for more information.
- If your system does not have any of the above settings in BIOS, ignore such settings.
- If your BIOS has Legacy Option ROMs, set it to UEFI/UEFI Only.
3. Save & Exit Setup
STEP 2: Cleanup old work
Once you have set up the BIOS, the next step is to remove the kexts, injections, and ACPI renames that can interfere with the Graphics implementation. To remove such, follow the steps below:Kexts Removal
If you're using any of these kexts listed below, it is recommended to remove them. See notes below.1. Mount your ESP.
2. Remove the following kexts:
- IntelGraphicsFixup.kext
- NvidiaGraphicsFixup.kext
- CoreDisplayFixup.kext
- Shiki.kext
- IntelGraphicsDVMTFixup.kext
- AzulPatcher4600.kext
- AppleBacklightFixup.kext,
- FakePCIID_Intel_HD_Graphics.kext
- FakePCIID_Intel_HDMI_Audio.kext
- FakePCIID.kext
NOTES:
- If you're using OpenCore, you'll also need to remove the kext entries from your kernel section in your config.plist
- For macOS Catalina and prior, make sure these kexts don't exist in Library/Extensions or System/Library/Extensions.
- Do not remove FakePCIID.kext if you're using any other FakePCIID plugins.
Clover Properties and Injections
If you're using Clover, you need to disable Clover properties and injections.1. Mount your ESP.
2. Open your config.plist and disable and/or remove the following from their respective sections as described below:
Disable DSDT Fixes
The DSDT fixes can be disabled in
Acpi>Fixes section.- AddHDMI
- FixDisplay
- FixIntelGfx
- AddIMEI
- FixHDA
- AddPNLF
The Fake IDs can be disabled in the
Devices>Fake ID section.- ATI
- IntelGFX
- NVidia
- IMEI
The injection properties can be disabled in the
Devices>Properties section.- Inject
- UseIntelHDMI
- HDMIInjection
- SetIntelBacklight
- SetIntelMaxBacklight
The Graphics injection can be disabled in the Graphics section
- ATI
- Intel
- NVidia
The ig-platform-id can be removed in the Graphics section
ACPI Renames
If you're using any ACPI renames, you'll need to disable or delete the ACPI renames as these can conflict with WhateverGreen's automatic renames.1. Mount your ESP.
2. Open your config.plist and remove the following ACPI renames. For Clover, it's in
Acpi>DSDT>Patches section, and for OpenCore, it's under ACPI>Patch section:- GFX0 to IGPU
- PEGP to GFX0
- HECI to IMEI
- MEI to IMEI
- HDAS to HDEF
- B0D3 to HDAU
STEP 3: Add Required Kexts
The next step is to add the required kexts to enable AMD Graphics. WhateverGreen doesn't work standalone. WhateverGreen and Lilu are needed together to work in conjunction in order to enable AMD Graphics and prevent any errors.1. Download Lilu, CryptexFixup, WhateverGreen.
2. Mount your ESP.
For Clover:
If you're using Clover, copy Lilu.kext, CryptexFixup.kext, and WhateverGreen.kext to the
EFI/Clover/Kext/Others directory.For OpenCore:
1. If you're using OpenCore, copy Lilu.kext, CryptexFixup.kext, and WhateverGreen.kext to the
EFI/OC/Kexts.2. Open your config.plist using any XML editor and add
Lilu.kext, CryptexFixup.kext, and WhateverGreen.kext entries in the Kernel>Add section of your config.plist:NOTES:
- Download the latest version for better support.
- Download only the RELEASE.zip file.
- If the kext is already present in the directory, replace them with a new version.
- Do not use WhateverGreen.kext.dSYM, WhateverName.app and Lilu.kext.dSYM.
STEP 4: Disable Secure Boot Model
Once you have added the required kexts, the next step is to disable the Secure Boot Model. To disable the Secure Boot Model, follow the steps below:1. Assuming the config.plist is still open, set the SecureBootModel to
Disabled under the Misc>Security section of your config.plist:
STEP 5: Add Required Boot Args
Once you have added the kexts, the next step is to add the required boot args. To add the boot args, follow the steps below:For Clover:
Assuming the config.plist is still open, add
-amd_no_dgpu_accel and agdpmod=pikera to the Boot Arguments under the Boot>Argument section of your config.plist.For OpenCore:
Assuming the config.plist is still open, add
-amd_no_dgpu_accel and agdpmod=pikera to the boot-args key under the 7C436110-AB2A-4BBB-A880-FE41995C9F82 UUID list in the NVRAM section of your config.plist.NOTE:
agdpmod=pikera is only required for AMD 5000 and 6000 series GPUs.STEP 6: Disable Apple Mobile File Integrity (AMFI)
Once you have disabled the Secure Boot Model and added the boot args, the next step is to disable the Apple Mobile File Integrity (AMFI). You can either use a kext or boot arg to disable the AMFI (never both). Depending on your choice, choose one from below:I. Using Kext
To disable AMFI using kext, follow the steps below:1. Assuming the ESP is still mounted, copy
AMFIPass.kext to the EFI/OC/kexts directory.
2. Assuming the config.plist is still open, add
AMFIPass.kext entry in the Kernel>Add section of your config.plist. In addition, you'll need to specify the MinKernel and MaxKernel as shown below to ensure that the kext only loads on the appropriate version of macOS, if using the same EFI for booting multiple macOS versions.
II. Using Boot Args
To disable the AMFI using boot args, you can follow the steps below:1. Assuming the config.plist is still open, add
amfi=0x80 to the boot-args key under the 7C436110-AB2A-4BBB-A880-FE41995C9F82 UUID list in the NVRAM section of your config.plist.
QUICK INFO: When using amfi=0x80 boot arg, certain applications may not respond and eventually crash (such as Firefox) as reported by @svan71. However, AMFIPass.kext is more suitable in such case scenarios.STEP 7: Disable System Integrity Protection (SIP)
Once you have added the required boot args, the next step is to disable the System Integrity Protection. To disable the SIP, follow the steps below:1. Assuming the config.plist is still open, set the csr-active-config to
03080000 as the DATA value for root patching:
2. Save your config.plist.
CAUTION: Do NOT enable the SIP after root patching, else the WiFi will not longer function. The SIP must remain either partially or completely disabled for the downgraded kexts and required frameworks to load.STEP 8: Boot using the new Configuration
After performing all the above steps, you'll need to boot with the updated configuration. Simply restart your system for the applied changes to take effect. It is recommended to reset NVRAM twice at least.STEP 9: Uninstall OCLP
If you have made any previous attempt in order to fix the WiFi and have run root patching, its recommended to run the uninstaller first to remove the stale .plist, launchagents and also prevent the OCLP from halting when executing OCLP to patch the system volume. To uninstall OCLP, follow the steps below:1. Download OpenCore Legacy Patcher (OCLP) Uninstaller.
2. Run the Uninstaller
3. When prompted, enter your password and continue with the uninstallation:
4. Once uninstalled, click on Close.
STEP 10: Install OCLP
The next step is to install OCLP. To install OCLP, follow the steps below:1. Download OpenCore Legacy Patcher (OCLP).
2. Run the OCLP installer.
3. When prompted, enter your password and continue with the installation:
4. Once installed, click on Close.
STEP 11: Patch System Volume
The next step is to patch the system volume using OCLP in order to downgrade the network kexts and frameworks that is required for the functioning of the Intel WiFi, so that the AirportItlwm can load. To patch the system using OCLP, follow the steps below:2. Navigate to the Applications directory and right-click on OpenCore-Patcher.app and select Show Original.
3. Right-click on OpenCore-Patcher and click on Open and you'll see something similar to the screenshot attached below:
3. Click on Post Install Root Patch and you'll see something similar to the screenshot attached below:
As you can see, the OCLP has automatically detected what patch to apply.
QUICK INFO: If the SIP is enabled, you may notice a message stating "SIP is Enabled". If you notice that, make sure to disable it as described in STEP #1.Click on Start Root Patching and it will start patching the system volume. You'll see something similar to the screenshot attached below:
Once OCLP finishes patching the system volume, it will prompt to reboot. When OCLP asks you to reboot, click on Ignore and do not reboot the system yet.
Click on Return to Main Menu and Quit OCLP.
STEP 12: Restart your System
After performing all the above steps, you'll need to restart your system for the applied changes to take effect. It is recommended to reset NVRAM twice at least.Verifying your Card
Look for the information of your card under About this Mac and verify the VRAM. For more information about your Card, navigate to System Information and navigate to Graphics/Displays Tab.NOTES:
|
Last edited:
