Need Help with EFI for macOS Tahoe on Ryzen 7 1800X + MSI Tomahawk B350 + RX 550

[ToeHold]

Hi everyone,
I’ve been trying for several days to fix my EFI configuration for macOS Tahoe on my system but haven’t had any success so far.
My hardware specs are:
• CPU: Ryzen 7 1800X
• Motherboard: MSI Tomahawk B350
• GPU: RX 550 4GB
• Storage: NVMe SSD
• Network: Realtek RTL8111 Ethernet
I have a working EFI for macOS Sonoma, but I need help adapting or fixing the EFI so that it can properly install and run macOS Tahoe on this setup.
I’m willing to share my current EFI files (including the Sonoma EFI) for anyone interested in helping improve or create a Tahoe-compatible EFI.
If anyone is experienced with Ryzen Hackintosh setups and macOS Tahoe, I would really appreciate your help!
Thank you in advance.

 

[Edhawk]

You have a few issues with your EFI, which will prevent you running Tahoe on your soup setup.

You are using the Sequoia AMD Kernel Patches (MaxKernel 24.99.99) in your config.plist. You need to replace these with the latest version which supports Tahoe (MaxKernel 25.99.99).

SSDT-PMC.aml is not meant for use with an AMD system, it is aimed at fixing issues on Intel 300-series motherboards. Remove it from your setup.

I am not sure you need the SSDT-GPRW.aml table and patch, as that is more commonly a fix for laptops.

Your USBMap.kext looks wrong, too many Physical USB2 ports are present, no Internal USB headers included and it doesn't support Tahoe.
You need to revise your USBMap.kext to activate the correct ports, with the correct USB connector type. Otherwise you may as well not use it.
You will need to convert your current USBMap.kext to include the new USB port and number requirements instigated by Apple with the release of Tahoe. Little point doing this if you don't first fix the issues in the kext.
You need to use the Kernel > Quirks > XhciPortLimit entry until you fix your USBMap.kext.

You need to clean out the unnecessary Drivers and Tools in your OC setup. These additional Tools and Drivers do nothing helpful.

Same with the DeviceProperties you are using that appear to have been lifted straight from Hackintool's PCIe tab/Export files. None of these DeviceProperties add anything new to the setup. They just regurgitate the information present in Hackintool. Anything they do generate is purely cosmetic with no additional function in macOS.

WhateverGreen.kext doesn't work during the Tahoe installation, it needs to be disabled or removed and only reinstated/Enabled once you get to the macOS Tahoe desktop. Otherwise you will see a kernel panic.

AppleALC.kext stopped working with the release of the Tahoe Beta, due to Apple removing support for AppleHDA.kext.
Before you get AppleALC working, you need to reinstall AppleHDA.kext and the associated files to Tahoe as a post install process. Do not have AppleALC present in your OC setup during installation.

You should remove any and all Sensor or non-essential kexts from your setup, as they are as likely to cause issues as they are to work in Tahoe.

I have amended your EFI folder as listed above, try the attached EFI and see if it works.

 

[ToeHold]

Thank you very much for your excellent work on the EFI file. It is perfectly done, and macOS Tahoe is running flawlessly on my system. I truly appreciate all your help.

I would also like to ask if you could share some post-installation tips for macOS Tahoe. Additionally, I’m curious whether Parallels Desktop will be compatible and work well on this setup.

Thanks again for your invaluable support!

 

[Edhawk]

No idea if Parallels desktop is compatible with Tahoe. You would need to have a look on their website to see if they have any updates available.

Post installation you need to undertake three main areas of study, before attempting any fixes.

Do you need to enable WhateverGreen.kext?

https://www.tonymacx86.com/threads/not-yet-using-whatevergreen-am-i-missing-out-big-time.312529/post-2246922

Do you need to add AppleALC.kext and AppleHDA to Tahoe for the builtin audio to work.

https://www.tonymacx86.com/threads/how-to-recover-applehda-under-tahoe.332294/

But most importantly you need to generate a new USBMap.kext that is compatible with Tahoe.

https://www.tonymacx86.com/threads/converting-usbports-kext-to-usbmap-kext-for-macos-tahoe.332341/

 

[ToeHold]

Hello again, I have a problem, everything was working perfectly until yesterday, the image started freezing and blurry and today I can't even log in, everything is blurry, could you help me solve this problem?

 

[Edhawk]

So, what changed?

Have you run any macOS updates? Which version of Tahoe are you using?

Did you run an Tahoe update and sign in to your iCloud account as part of the installation process? If you did then you have probably activated FileVault encryption on your macOS drive (this happens by default when you sign in to your iCloud account during the installation), which is known to cause sign in issues.

You may need to run a clean installation again, but make sure you don’t sign in to your iCloud account as part of the wizard, this will result in a separate screen appearing as part of the macOS setup wizard that will allow you to unselect/disable FileVault encryption.

 

[ToeHold]

It's highly likely that it updated itself to a newer version, but I don't think that's the problem. I can't even get to the start screen now. It freezes at the Apple logo and refuses to start. Previously, the screen would freeze and blur. Could it be a problem with the kexts or the graphics card?

 

[ToeHold]

I will also add that I inserted a second disk with macOS Sonoma installed and tried to start it and the same thing happened, whereas before everything worked

 

[Edhawk]

Assuming the system rebooted after the update, and that FileVault encryption was enabled as part of the installation then your config.plist would have an incorrect configuration for this feature. I would assume following the Ryzen guide that FileVault quirk is set as ‘Optional’.

This may be what causes the early reboot with no activity seen on the Apple progress bar.

Not sure why the Sonoma drive failed to boot. You may need to physically remove the Tahoe drive to get the Sonoma drive to boot from the USB pen drive you used to install Tahoe. Hopefully you will have kept this safe and easily accessible.

 

[ToeHold]

I reinstalled Tahoe on a new, separate drive using the EFi you provided earlier, but unfortunately the problem persists and I have no idea how to solve it.