Search results

No. Search GitHub for a suitable EFI yourself. I am happy to help people, but I don’t expect them to take the Micky.

No, I haven't been using High Sierra for a number of years. So I don't have an AMD EFI that would work for you.

No. That was the last version of the Nvidia Web Drivers issued by Nvidia for macOS High Sierra. There are no newer or alternative drivers. I assume the following: You have WhateverGreen.kext installed in your OC setup. That you have disabled the Nvidia boot argument or Nvram entry you used...

Yes. You need to uninstall the previous version of the Nvidia Web Drivers, reboot the system, reset NVRAM and then install these new drivers.

Not. It is a post install application for installing the third-party Nvidia Web Drivers. It is not part of the OS installation process.

If the OpenCore EFI boots High Sierra, then to problem is going to be with the version of the Nvidia Web Drivers you are using. The Certificate for the Nvidia Web Drivers were revoked back in 2022. An alternative set of drivers were then released by Nvidia. You need to be using these...

The correct boot argument is revpatch=cpuname. I have added the relevant RestrictEvents NVRAM entries for your AMD CPU to the revised config. Replacing the incorrect RestrictEvent boot arguments. I have cleaned up and fixed some errors in your config.plist. NVRAM section from revised...

Try this revised EFI, see if it gets you any further along the macOS Installation path.

The RTL8852AEis not compatible with any version of macOS. You need to physically remove it and install a new Broadcom WiFi/BT card.

First you need to clarify the make and model of your WiFi/BT card. Most Realtek and Mediatek cards aren’t compatible with macOS, as there are very few kexts/drivers for these makes of card. You would probably be best served replacing the current card with a Broadcom card, one from the list on...

Welcome to the forum.

USBMap.kext shouldn’t be used with USBToolBox.kext. UTBMap.kext is to be created and used with USBToolBox.kext.

OK, that is an old/obsolete fix, which isn't used any more. You aren't relying on this 'fix' now are you? You are now using the CPU core count patches in your setup, yes?

Have you mapped the USB ports correctly on either motherboard? As the reboot on shutdown error is common for those that haven't configured the USB ports. A USB power call tells the system to restart instead of shutting down. All it takes is one USB port to be configured incorrectly and this...

What Speedkeeper apps are you using in macOS? I thought they were Android applications!

You need to read this section of the OpenCore guide. https://dortania.github.io/OpenCore-Multiboot/

Have you read this guide for B650 systems? https://forum.amd-osx.com/threads/asus-x670e-gene-efi-adaptable-to-other-x670-x670e-b650-and-b650e-boards.4160/

Yes, based on the CPU it would be compatible with macOS. See this thread for a similar Mini PC Hack using a similar CPU/IGPU. https://forum.amd-osx.com/threads/amd-mini-pc-gen-machine-ren7000.5006/

Yes, MacPro7,1 will be the best SMBIOS for an AMD system running macOS Tahoe. As it lacks an IGPU. The alternatives are iMac20,1 or iMac20,2 both use an IGPU to provide Decoding & Encoding processes. The other Tahoe compatible Macs aren't of any use to us.

The order of kexts in your config.plist isn't ideal. You have Lilu.kext in position 3 and VirtualSMC.kext in position 9. I normally set Lilu.kext first and VirtualSMC.kext second in the Kernel > Add section of the config.plist. With the others following as sorted by ProperTree. As you are...