Need assistance adapting EFI for macOS Tahoe (Ryzen 9 7950X3D + RX 6900 XT)

[hinkin]

Hi everyone,

I’ve been trying for several days to get my EFI configuration working for macOS Tahoe on my system, but I haven’t had any success so far.

Hardware Configuration​

• CPU: AMD Ryzen 9 7950X3D
• Motherboard: Gigabyte X870 AORUS ELITE WIFI7
• RAM: 64GB DDR5 5000MHz
• GPU: AMD Radeon RX 6900 XT 16GB
• Network: Realtek RTL8125B
• Wi-Fi/Bluetooth: Fenvi T919 PCIe WLAN Card

I currently have a fully working EFI for macOS Sequoia, but I need assistance in adapting or fixing it so that it can properly install and run macOS Tahoe on this setup.
I’m sharing my current EFI folder for anyone interested in helping improve or create a Tahoe-compatible version.

Any help or suggestions would be greatly appreciated.

Thank you in advance!

 

[Edhawk]

Copy of your current working EFI folder.

FYI. Your Fenvi T919 card isn't supported in Tahoe, as yet. We are waiting on a fix from the Developers of OCLP.

 

[hinkin]

Copy of your current working EFI folder.

FYI. Your Fenvi T919 card isn't supported in Tahoe, as yet. We are waiting on a fix from the Developers of OCLP.

Hi, I’m sending you a copy of my current working EFI folder as requested.
I’m also aware that the Fenvi T919 card isn’t supported in Tahoe yet and that we’re waiting for a fix.
Thank you for your help!

 

[Edhawk]

I have reviewed and amended your EFI folder to what I think will work with macOS Tahoe.

This includes the following:

1. Generated and added a number of custom SSDT's and ACPI patches using the ACPI tables you provided and Corpnewt's SSDTTime script.
   1. These ACPI tables and patches have been added to your OC/ACPI folder and config.plist.
2. Reduced the number of Kexts & Drivers in the respective OC folders.
3. Disabled the WhateverGreen.kext, as it will prevent the system booting macOS Tahoe if enabled during the early installation phase.
   1. WEG can be enabled for the final installation phase, i.e when you get to the part where you set the country, create the account etc.
   2. Alternatively it can be left disabled till you get to the macOS desktop.
4. I have removed your USBPorts.kext as it is not set correctly for macOS Tahoe.
   1. You need to create a new USBPorts.kext, using your current one as the base with Hackintool 4.1.3 or newer. As this version of Hackintool added a fix for Tahoe USB requirements.
   2. Alternatively you can try installing Tahoe without a USB config in place but would need to enable the XhciPortLimit quirk in the config.plist..
5. I have updated the AMD Kernel Patches in the config.plist to the latest release.
6. I have added entries for RestrictEvents.kext , so the AMD CPU is correctly named in macOS.

I would recommend you copy this revised EFI to the EFI partition on a spare USB pen drive, so as not to over write your current working EFI. You can see if it works to boot Sequoia, before you run the Tahoe installer. Obviously with the reduced number of kexts some features won't work in Sequoia with this EFI. But it should still allow you to boot the OS.

The revised EFI is attached. Rename if from 'EFI-Tahoe' to 'EFI' before use.

I have also attached a copy of the Results folder generated by SSDTime, this contains the SSDT's and ACPI patches used in the revised EFI.

I have added Verbose boot arguments to the config.plist, so you can post a photo of the text shown, should the system kernel panic.

Let me know how you get on with the revised EFI.

 

[hinkin]

I have reviewed and amended your EFI folder to what I think will work with macOS Tahoe.

This includes the following:

1. Generated and added a number of custom SSDT's and ACPI patches using the ACPI tables you provided and Corpnewt's SSDTTime script.
   1. These ACPI tables and patches have been added to your OC/ACPI folder and config.plist.
2. Reduced the number of Kexts & Drivers in the respective OC folders.
3. Disabled the WhateverGreen.kext, as it will prevent the system booting macOS Tahoe if enabled during the early installation phase.
   1. WEG can be enabled for the final installation phase, i.e when you get to the part where you set the country, create the account etc.
   2. Alternatively it can be left disabled till you get to the macOS desktop.
4. I have removed your USBPorts.kext as it is not set correctly for macOS Tahoe.
   1. You need to create a new USBPorts.kext, using your current one as the base with Hackintool 4.1.3 or newer. As this version of Hackintool added a fix for Tahoe USB requirements.
   2. Alternatively you can try installing Tahoe without a USB config in place but would need to enable the XhciPortLimit quirk in the config.plist..
5. I have updated the AMD Kernel Patches in the config.plist to the latest release.
6. I have added entries for RestrictEvents.kext , so the AMD CPU is correctly named in macOS.

I would recommend you copy this revised EFI to the EFI partition on a spare USB pen drive, so as not to over write your current working EFI. You can see if it works to boot Sequoia, before you run the Tahoe installer. Obviously with the reduced number of kexts some features won't work in Sequoia with this EFI. But it should still allow you to boot the OS.

The revised EFI is attached. Rename if from 'EFI-Tahoe' to 'EFI' before use.

I have also attached a copy of the Results folder generated by SSDTime, this contains the SSDT's and ACPI patches used in the revised EFI.

I have added Verbose boot arguments to the config.plist, so you can post a photo of the text shown, should the system kernel panic.

Let me know how you get on with the revised EFI.

Hi Edhawk, Thank you very much for your help!
I’ve placed your revised EFI on my Sequoia installation USB, and the installation booted successfully.
After that, I used the same EFI on my Tahoe installation USB but this time, I only got a black screen with the Apple logo. The installation process didn’t start at all, and even the keyboard backlight turned off.
Despite the added verbose boot arguments, there was no text displayed on the screen.

 

[Edhawk]

I have no idea why that would be the outcome of using the EFI to boot the Tahoe installer. Especially if it worked to boot Sequoia.

 

[hinkin]

I have no idea why that would be the outcome of using the EFI to boot the Tahoe installer. Especially if it worked to boot Sequoia.

Yeah, that’s what confused me too since the EFI boots Sequoia just fine, I expected at least some verbose output with the Tahoe installer.
Could it be something related to the installer itself? Maybe a missing driver, USB mapping issue, or kernel patch difference?
Do you think it’s worth recreating the Tahoe USB or enabling XhciPortLimit just to test?
I can share photos or logs if that helps.