I need to help with and install issue with Ryzen 9 9900x

K

Katanoko1221

Member
AMD OS X Member
Apr 7, 2025
92
8
8
Italy
CPU:
Ryzen 9 9900X
Hi everyone!!!
This is my first Ryzentosh build and i've the each problem; When i select "installMacOS" in OC boot menù, the install rest stuck after few second.
I attach EFI, System report and the boot-log containing the error.
I hope there is someone who can fix the efi so I can install macOS!!!

Thanks in advance 🙏🙏🙏

Pc configuration:
Cpu: Ryzen 9 9900x
Gpu: Amd Rx6600
Mbo: MSI x870 Gaming Plus
Ram: Crucial 64 Gb
NvMe: (M2) Crucial P3 plus.
 

Attachments

Sort by date Sort by votes
No it is not enough to just replace the OpenCore.efi file.

You need to replace the following:
  1. OpenCore.efi
  2. Bootx64.efi
  3. All Drivers & Tools you have in your OC sub-folders.
All of the above have to be from the same OC release version. Otherwise you will have issues booting the system.

Plus you may need to make some changes to the config.plist, depending on whether the OC developers made changes to the latest release. Best to use ocvalidate to check the config.plist isn’t missing anything.
 
Upvote 0 Downvote
Ciao @Katanoko1221 talking in the past with shaneee it seems that no mod needed to boot with 9900 cpu
To stay safe, maintain a solid backup of your working Efi
 
Upvote 0 Downvote
fabiosun said:
Ciao @Katanoko1221 talking in the past with shaneee it seems that no mod needed to boot with 9900 cpu
To stay safe, maintain a solid backup of your working Efi
Click to expand...
@Edhawk
I always make a triple backup of the EFI!!!
So, I don't quite understand, to update OC to 1.0.5 I just need to transfer the file "Opencore.efi" containing the patch for my CPU along with the rest of the content from the other folders?

As for the rest, I have resolved the previous issues with startup and shutdown. I excluded the harmful USB ports that were causing the reboot and by enabling SIP and changing the HDMI cable, I solved the problem of the black screen during system startup.
 
Upvote 0 Downvote
Katanoko1221 said:
So, I don't quite understand, to update OC to 1.0.5 I just need to transfer the file "Opencore.efi" containing the patch for my CPU along with the rest of the content from the other folders
Click to expand...
No
You must download opencore1.05 release from acidanthera GitHub o where you like
Then overwrite opencore.efi, bootx64.efi
And all uefi driver you use with the newest one you find in opencore 1.05 zip file

Edit
By the way, you quoted me then tag edhawk🥹
 
  • Like
Reactions: Katanoko1221
Upvote 0 Downvote
Katanoko1221 said:
So, is enough replace the “Opencore.efi” in the new “OC folders” without modd this?

Thank in advance 🙏
Click to expand...
No, all .efi files within the "Drivers" section of your config.plist need to mach the release date of Opencore.efi or you won't get t the boot menu. If you haven't heard of OCAT or OCAuxillaryTools check out Github, it makes updating OpenCore versions and kexts easy. Use your verified bootable USB Drive to be safe and then mount the config.plist on it and load that into OCAT. It will update everything in the EFI folder you ask it to, save it will check for errors. There must be a guide available somewhere online on how to use i....up to you.
 
Upvote 0 Downvote
fabiosun said:
No
You must download opencore1.05 release from acidanthera GitHub o where you like
Then overwrite opencore.efi, bootx64.efi
And all uefi driver you use with the newest one you find in opencore 1.05 zip file

Edit
By the way, you quoted me then tag edhawk🥹
Click to expand...
Ok, grazie ora mi è tutto chiaro!!!
Ok, thank you, now i've understand!!!
 
Upvote 0 Downvote
leesurone said:
No, all .efi files within the "Drivers" section of your config.plist need to mach the release date of Opencore.efi or you won't get t the boot menu. If you haven't heard of OCAT or OCAuxillaryTools check out Github, it makes updating OpenCore versions and kexts easy. Use your verified bootable USB Drive to be safe and then mount the config.plist on it and load that into OCAT. It will update everything in the EFI folder you ask it to, save it will check for errors. There must be a guide available somewhere online on how to use i....up to you.
Click to expand...
Ok, thank you for your suggest.
But I preffer doing this operations manually.
 
  • Like
Reactions: leesurone
Upvote 0 Downvote
Upvote 0 Downvote
@Shaneee
Update about OC version:

Today I've try to update OC to last version "1.0.5" following this steps but nothing. I've replaced "Opencore.efi, Bootx64.efi", updated the driver and transfer my "config.plist but nothing. OC showing again "1.0.4" dubug. I think that we need to copy cpu patch into a new "Opencore.efi" for version "1.0.5 release"; anyway showing again the debug version and not release.

Thanks in advance 🙏
 
Upvote 0 Downvote
You need to clear the NVRAM.
 
Upvote 0 Downvote
Post a copy of your Current EFI folder, the whole EFI folder, so we can see exactly what you are using.
 
Upvote 0 Downvote
I’ll have a look at your EFI folder tomorrow (Friday).

Katanoko1221 said:
copy the patch in a new file compatible with "OC 1.0.5 Release
Click to expand...
I am still not sure what you mean when you say this.

Which patch?
Why wouldn’t the patch assuming it works for other OpenCore releases work in the latest?
How does the OpenCore release affect the patch?
 
Upvote 0 Downvote
Edhawk said:
I’ll have a look at your EFI folder tomorrow (Friday).


I am still not sure what you mean when you say this.

Which patch?
Why wouldn’t the patch assuming it works for other OpenCore releases work in the latest?
How does the OpenCore release affect the patch?
Click to expand...
For run macOS on my Cpu, @Shaneee have doing a specific patch contains inside “Opencore.efi”. Hope you understand now!!!
 
Upvote 0 Downvote
Quick question about the ACPI/DSDT patches by CorpGhost:
  • Are these patches needed only by most recent versions of macOS such as Sequoia and Tahoe, but not needed by Sonoma?
  • @mrfatcatt has a Gigabyte X570S that boots Sonoma, but we're not successful in booting Sequoia or Tahoe; should we rule out DSDT/ACPI patches or could they be a possible cause of the problem?
 
Upvote 0 Downvote
Katanoko1221 said:
For run macOS on my Cpu, @Shaneee have doing a specific patch contains inside “Opencore.efi”. Hope you understand now!!!
Click to expand...
<IT>
Ciao
Sembra invece che non serva nessuna patch particolare per il 9900 (e questo e' emerso anche parlandone con Shaneee)
<\IT>
<EN>
Hi
it seems your 9900 does not need any different patch (and this was also discussed in private with Shaneee sometime ago)
<\EN>
 
Upvote 0 Downvote
CaseySJ said:
Are these patches needed only by most recent versions of macOS such as Sequoia and Tahoe, but not needed by Sonoma?
Click to expand...
No, in my case also in ventura
they are useful to boot(without it many acpi errors and system hangs)
@CaseySJ if you are talking about ACPI patches useful for different board and manufacturer as your ASUS and mine)
 
Last edited:
  • Like
Reactions: CaseySJ
Upvote 0 Downvote
Clone the GitHub repository and fork it to make your changes…

Are you sure you want to rewrite OpenCore rather than defining patches in the config.plist?
 
Upvote 0 Downvote
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.