Need help with macOS Sequoia on Ryzen 9 9950X (OpenCore Boot Failure)

P

pvford55

New member
AMD OS X Member
Aug 20, 2025
11
0
1
United States - Texas, the humid part
CPU:
AMD Ryzen 9 9950X
Hello everyone,

This has become the installation from hell for me, as I have been working months off and on, trying to get this to work via Proxmox, and now I am trying just using OpenCore.

I’m trying to run macOS Sequoia installer using OpenCore on an AMD Ryzen 9 9950X (ASUS ROG X870E-E Gaming motherboard, 64 GB RAM, RX 6900 XT).

I’ve followed Gabriel Luchina’s osx-proxmox script and also tried customizing my config.plist with OpenCore. However, when I boot, I always get stuck with the following error:

BootKernelExtensions.kc.development not found

Steps I’ve tried so far:

  • Enabled DisableIoMapper, AppleCpuPmCfgLock, AppleXcpmCfgLock
  • Reordered kexts (Lilu → VirtualSMC → WhateverGreen)
  • Enabled AM5 PCI hotplug patch
  • Disabled SecureBootModel and set ScanPolicy=0
  • Tried both MacPro7,1 and iMacPro1,1 SMBIOS
But the error persists.

Questions:
  1. Do I need a specific AMD Zen 4 kernel patch set for Sequoia / Ventura?
  2. Are there recommended quirks for AM5 systems (X870E)?
  3. Is there a working sample config.plist for Ryzen 9 9950X + RX 6900 XT?

I’ve attached my config.plist if anyone is willing to review.


Thank you in advance for any guidance!


— Patrick
 

Attachments

pvford55 said:
Hello everyone,

This has become the installation from hell for me, as I have been working months off and on, trying to get this to work via Proxmox, and now I am trying just using OpenCore.

I’m trying to run macOS Sequoia installer using OpenCore on an AMD Ryzen 9 9950X (ASUS ROG X870E-E Gaming motherboard, 64 GB RAM, RX 6900 XT).

I’ve followed Gabriel Luchina’s osx-proxmox script and also tried customizing my config.plist with OpenCore. However, when I boot, I always get stuck with the following error:

BootKernelExtensions.kc.development not found

Steps I’ve tried so far:

  • Enabled DisableIoMapper, AppleCpuPmCfgLock, AppleXcpmCfgLock
  • Reordered kexts (Lilu → VirtualSMC → WhateverGreen)
  • Enabled AM5 PCI hotplug patch
  • Disabled SecureBootModel and set ScanPolicy=0
  • Tried both MacPro7,1 and iMacPro1,1 SMBIOS
But the error persists.

Questions:
  1. Do I need a specific AMD Zen 4 kernel patch set for Sequoia / Ventura?
  2. Are there recommended quirks for AM5 systems (X870E)?
  3. Is there a working sample config.plist for Ryzen 9 9950X + RX 6900 XT?

I’ve attached my config.plist if anyone is willing to review.


Thank you in advance for any guidance!


— Patrick
Click to expand...
your system could work..but your EFI is a disaster!
:P

it misses many parts mandatory to have the chance to boot and ProxMox route is very different to vanilla way!

1) DevirtualizeMMIO quirk and relative MMIO Whitelist area set (or without setting it enabling also a quirk like disableVariableWrite)
2) quirks you have to use are pretty the same of previous x670e platform
3) your Asus could need of additional ACPI patches for your DSDT

So, you should build (without hiring no one
:)
) an Opencore debuf EFI enabling SYSReport to extract your DSDT and post on AMD OSX Discord server to the attention of CorpGost (AKA CorpNewt)
Usually he produces patches (if you need them) very fast

if you like i suggest to read this thread:

https://macos86.it/topic/7055-asus-rog-crosshair-x870e-hero-ryzen-9950x/

https://macos86.it/topic/6542-bug-fix-for-am5-new-firmware-motherboards-dsdt-fix/#comments

and similar ones you can find here
 
Thank you for the information. "Disaster" is actually a polite means of describing my experience. Frankly, buying a working computer and installed Hackintosh would have been cheaper, given how much I am paid per hour.
 
@pvford55
Realtek 5Gb Ethernet is not compatible with any OSX for now, in this EFI you missed again DevirtualiseMMIo quirk and other stuff mandatory to boot in AMD X670/x870E platform, and you had also a pleteroa of ethernet kexts
So to install you have to build a full installer for OSX or use an installed OSX
Your kexts section has many unusefull ethernet kext for intel, realtek and other ethernet you do not have on board

Your sysreport should be uploaded here:
discord.com

Discord - Group Chat That’s All Fun & Games

Discord is great for playing games and chilling with friends, or even building a worldwide community. Customize your own space to talk, play, and hang out.
discord.com discord.com
so CorpGhost could help you for some mandatory ACPI DSDT patches Asus motherboard needs
When your system will boot it will miss of ethernet so you have to add a compatible one ethernet adapter

If you like you can try this EFI and see if your system does a step forward:
 

Attachments

@fabiosun

Thank you for the information. I do have a "Install macOS Sonoma" USB where I installed the EFI in the EFI directory using "EFI Mounter v3.app ".
Re: ethernet - I ran into this issue when I was trying to use Proxmox to run MacOS X. I ended up buying a Belkin USB-C to Ethernet adapter which typically uses a Realtek RTL8153 chipset. I have a copy of RealtekRTL8111.kext, which may work, but should I track down RealtekRTL8153.kext?
​

 
No, as the USB -C to Ethernet adapter uses a native USB Apple driver, not a third-party Ethernet driver/kext.
 
@pvford55 in this EFI you have to put (and to change) only the section ACPI/Patches tha CorpNewt did for you on discord server
No need anymore to pu entire EFI or Sysreport (only a photo or video of your verbose output if system hangs or reboot
So take the file patches.plist done for your motherboard and replace ACPI/Patches you have now in above EFI
 
pvford55 said:
I am confused a bit. I added the ACPI/Patches that CorpNewt did, was I suppose to replace the "current" ones with his or just add them?
Click to expand...
replace completely them with the ones corpghost did for you :)
Edit
If you have problem post here only config.plist and patches.plist corpghost did for you
 
I have reached a point where I can boot into the installation section for Sonoma, but neither Disk Utility nor the Installer can see USB drives. I had the NVMe SSD drive attached via USB, mostly for convenience to move it to another computer. Once I placed it into the NVMe port, it worked and I am currently doing my first install.
However, I need information on how to set up OpenCore to see the USB ports on a ASUS ROG STRIX X870E-E Gaming WiFi.
If there are instructions regarding this, please let me know where they are located.
Thank you
PF
 
You need to map the USB ports for them to show in macOS.

This can be done using Corpnewt's USBMap script in macOS. This is my preferred option.

github.com

GitHub - corpnewt/USBMap: Python script for mapping USB ports in macOS and creating a custom injector kext.

Python script for mapping USB ports in macOS and creating a custom injector kext. - corpnewt/USBMap
github.com github.com


Alternatively, you can map the USB ports in Windows using USBToolBox Tool.

github.com

GitHub - USBToolBox/tool: the USBToolBox tool

the USBToolBox tool. Contribute to USBToolBox/tool development by creating an account on GitHub.
github.com github.com

 
I have succesfully booted in to Sonoma but I have several post installation issues.
If this is the wrong forum please tell where to go, and also which forum is appropriate.

The most significant issue that I know of, is after a certain amount of time, the system tries to reboot. I suspect there is a problem with sleeping and hibernation that trigers this.

Less serious, but annoying, is that I never see the Apple logo with the scroll bar, so it looks like the system hung.

Also I need to work on my USB ports. Some that I like to work don't, but at least I got the USB-C ethernet adapter working so I can access the internet. Enlcose Config.plist and 2 of the OpenCore Debug text clean up to remove excess <nulls>.

Thank you
 

Attachments

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 using USBMap.kext to configure your USB ports you don't want or need to have USBToolBox.kext in your OC Kexts folder. The USBToolBox.kext is only required for systems where the USB ports are configured via UTBMap.kext.

You are using USBWakeFixup.kext in your OC setup, but you don't have the accompanying SSDT-USBW.aml table in your ACPI folder or config.plist. You also don't have the alternative DeviceProperties entry. The DeviceProperties or SSDT are used to point at the USB XHCI controller to fix the poorly functioning wake call parameters. As it stands it probably does nothing useful. I am also pretty sure this is a fix that was designed for an Intel system.

You don't need all the Tools entries in your OpenCore setup. I would recommend deleting those you will never use. Normally I only leave three entries in this folder - CleanNvram.efi, OpenShell.efi and ResetSystem.efi.

Your boot arguments contain and error. revpatch=cpunam is misspelled it is missing an 'e' from the end of the cpuname entry.

The UEFI section of your config.plist is out of sort order, with Drivers being the first sub-section in this section. APFS should be first in this section of the config.

As you are still troubleshooting your system, you probably have too many drives attached. You should be booting with just the macOS drive installed, as you work through your USB, wake and graphics issues.
 
I attempted to make the appropriate changes as recommended by Edhawk, but I properly screwed it up.
(I assume there is a typo in "revpatch=cpunam" and the correct version is "repatch=cpuname" without the "V")

When I boot, I am now getting the following error:
16:236 00:001 AAPL: ***********************************************************
16:237 00:001 AAPL: This version of Mac OS X is not supported on this platform!
16:239 00:001 AAPL: ***********************************************************

Thank you
 

Attachments

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.

Screenshot 2025-09-10 at 17.57.00.png NVRAM section from revised config.plist.

Try the one attached config.plist with your current OC folder, don't change anything, see if that boots to the installer for Sequoia,
 

Attachments

I am trying to boot Sonoma. I tried the Edhawk config.plist, and I am still not booting and I see there is an:
03:646 00:001 AAPL: ***********************************************************
03:648 00:001 AAPL: This version of Mac OS X is not supported on this platform!
03:649 00:001 AAPL: ***********************************************************

I am enclosing the opencore debug output, SysReport folder as a zip file, a text file of the OC directory and the current config.plist.
It appears that OpenCore is not seeing MacPro7,1, but something else

Thank you
 

Attachments

If the system is setting another SMBIOS, not MacPro7,1, then are you sure you are editing the correct OpenCore EFI folder?

Do you have any other drives with EFI partitions present in your system?
If yes, then I would recommend you remove or detach the drives(s) while troubleshooting your Sonoma installation.
As you may have an incompatible EFI folder on one of the other drives.

Check your bios is booting from the correct USB drive.

Providing a copy of your EFI folder would be much better than the dir.txt and a separate config.plist, as they don't tell us the whole story for your setup.
 
There is only one boot drive and it is an NVMe M.2 drive. It is only used via USB when I am editing on another computer running MacOS 10.13.6

Enclosed is my EFI folder, with files I have been told to excluded placed in ZIP format. I refrained from previously uploading the entire EFI folder because on earlier negative comment made when I did.

Thank you for your help.
 

Attachments

You must log in or register to reply here.
Top Bottom
✖
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.