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

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

@fabiosun
I've try to skip the second "mmio", i've noted some little improving, but i don't able to solve the shutdown/restart and boot issue. How do you suggest me to proceeded for enable all mmio and doing several test?
The usb ports now are all mapped using "USB-Map Master".

Thank you in advance 🙏
 
I've try to skip the second "mmio", i've noted some little improving, but i don't able to solve the shutdown/restart and boot issue
I do not think it is MMIO related this problem
How do you suggest me to proceeded for enable all mmio and doing several test?
Post all your MSI board bios settings (all pages)

The usb ports now are all mapped using "USB-Map Master".
you should post also a page like this one below :

1746851455741.png
 
I do not think it is MMIO related this problem

Post all your MSI board bios settings (all pages)


you should post also a page like this one below :

View attachment 16981
This is alla screens. Now i’d try random all mmio for detect those nocive, for solve shutdown/restart dortania suggest to patch an ssdt, i’ve try but don’t working for me.
 

Attachments

  • IMG_3639.jpeg
    IMG_3639.jpeg
    3.6 MB · Views: 19
  • IMG_3641.jpeg
    IMG_3641.jpeg
    2.4 MB · Views: 13
  • IMG_3642.jpeg
    IMG_3642.jpeg
    2.6 MB · Views: 11
  • IMG_3643.jpeg
    IMG_3643.jpeg
    2.5 MB · Views: 11
  • IMG_3644.jpeg
    IMG_3644.jpeg
    2.3 MB · Views: 11
  • IMG_3645.jpeg
    IMG_3645.jpeg
    2.4 MB · Views: 11
  • IMG_3646.jpeg
    IMG_3646.jpeg
    2.4 MB · Views: 15
Integrated Peripherals?
Wake Up Event Setup?
ACPI Settings?
Click Bios settings?
Graphichs card detection? set to PCIE if available
Resize bar is disabled, your config plist is set to -1 or to 0 for that option?

All image for bios settings means all :P

Check if your board has internal peripherals like serial or paralle ports and if so disable them

i know it is boring but you can do this only by yourself

About MMIO ( i cant express in better way sorry) use for now disable Write variable without reassignig any MMIO to skip 1 (put disable/false all and enable devirtualizemmio and disable write variable.
 
Integrated Peripherals?
Wake Up Event Setup?
ACPI Settings?
Click Bios settings?
Graphichs card detection? set to PCIE if available
Resize bar is disabled, your config plist is set to -1 or to 0 for that option?

All image for bios settings means all :P

Check if your board has internal peripherals like serial or paralle ports and if so disable them

i know it is boring but you can do this only by yourself

About MMIO ( i cant express in better way sorry) use for now disable Write variable without reassignig any MMIO to skip 1 (put disable/false all and enable devirtualizemmio and disable write variable.
This is the last options required about bios. This bios don’t me permise to set some of theese values. Resize bar is set to “-1” because if i eneable the Bios option don’t boot into macOS.
 

Attachments

  • IMG_3648.jpeg
    IMG_3648.jpeg
    2.2 MB · Views: 15
  • IMG_3649.jpeg
    IMG_3649.jpeg
    2.4 MB · Views: 14
  • IMG_3650.jpeg
    IMG_3650.jpeg
    2.2 MB · Views: 15
Wake up event bios or what?

About resize bar
if you use MMIO (second areat set to skip 1) enabling or diabling it could change MMIO value to put
For this (maybe)system does not start
Also for this i suggest from the start to use DisableWite variable quirk togheter DevirtualizeMMIO to boot safely and then when you solved ypur problem do a proper MMIO area declaration
 
Wake up event bios or what?

About resize bar
if you use MMIO (second areat set to skip 1) enabling or diabling it could change MMIO value to put
For this (maybe)system does not start
Also for this i suggest from the start to use DisableWite variable quirk togheter DevirtualizeMMIO to boot safely and then when you solved ypur problem do a proper MMIO area declaration
This is the “Wake-up” bios screen.
Ok, than now i’ve put false in all mmio and enable “DevirtualiseMmio” & “DisableVariableWrite” right?

Thank in advance 🙏
 

Attachments

  • IMG_3651.jpeg
    IMG_3651.jpeg
    2.2 MB · Views: 12
Ok, than now i’ve put false in all mmio and enable “DevirtualiseMmio” & “DisableVariableWrite” right?
yes

for above screen section try OS
If system has problem as before, usually it gives when it boots well again some system report
read there if it shows some usuful data
 
Ok, later l’ii updating you. And if the issue persist i post last “Boot-Log”.

Thank you 🙏
no need of the boot log which is not so useful now, if possible post a photo or an OSX report after the system reboot/hang
 
no need of the boot log which is not so useful now, if possible post a photo or an OSX report after the system reboot/hang
Ok, i read that about AMD system it’s possible that i’d to set in boot-args “npci=0x2000” if i enable “4G Decoding” on bios?

Furthermore, hackintool suggest me to apply all this patch, there is a way that i’ve solve something if apply this boot/shutdown?
 

Attachments

  • IMG_3654.jpeg
    IMG_3654.jpeg
    6 MB · Views: 11
  • IMG_3653.jpeg
    IMG_3653.jpeg
    5.6 MB · Views: 10
  • IMG_3652.jpeg
    IMG_3652.jpeg
    5.2 MB · Views: 12
boot-args “npci=0x2000” if i enable “4G Decoding” on bios?
or the boot arg or the bios parameter (are quite similar, i never used the bootarg and in my case system boots without also with 4g on/off)
i cant say if all those patches (hackingtool) are useful or not for AMD system, i used always some ssdt produced by SSDTTime corpnewt script
Sorry!
 
Most of those ‘fixes’ in Hackintool are old and are not used with OpenCore. The patches/fixes will have very little in common with an AMD system. They are more likely to cause issues when used, than they are to help. The odd rename patch might be of use, but even then you would need to check if the ACPI really required the patch. They are best left unused, as none of the reports you have provided have shown any reason for them to be added to your OC setup.

When you use the ‘npci=0x2000’ or ‘npci=0x3000’ boot argument you should not have ‘Above 4G Decoding’ enabled in your bios. These boot arguments are provided for systems where the bios doesn’t contain an accessible ‘Above 4G Decoding’ option.

If you have ‘Above 4G Decoding’ enabled in your bios, then you shouldn’t use either of these boot arguments.

The above is clearly stated in the NVRAM section of the Dortania Ryzen guide.

Npci=0x3000 boot arg.png
 
  • Like
Reactions: Katanoko1221
Most of those ‘fixes’ in Hackintool are old and are not used with OpenCore. The patches/fixes will have very little in common with an AMD system. They are more likely to cause issues when used, than they are to help. The odd rename patch might be of use, but even then you would need to check if the ACPI really required the patch. They are best left unused, as none of the reports you have provided have shown any reason for them to be added to your OC setup.

When you use the ‘npci=0x2000’ or ‘npci=0x3000’ boot argument you should not have ‘Above 4G Decoding’ enabled in your bios. These boot arguments are provided for systems where the bios doesn’t contain an accessible ‘Above 4G Decoding’ option.

If you have ‘Above 4G Decoding’ enabled in your bios, then you shouldn’t use either of these boot arguments.

The above is clearly stated in the NVRAM section of the Dortania Ryzen guide.

View attachment 17000
I’ve “4G” acetivate in the bios, Anyway it’s only an “ACPI” settings.
 
Anyway it’s only an “ACPI” settings.
Your system won't work with macOS if the ACPI settings are wrong.

Regarding your MmioWhitelist issues, have you read and followed this guide?


At this point, it's not a question of Kext or patch but only of Bios, Acpi, mmio.
You are as likely to have an incomplete or incorrect custom USB configuration as any other issue, when you see the shutdown/wake issue.

The most common reason for the Shutdown/Wake issue on a Hack is a power call on one of the USB ports, which happens when a USB port has been set with the wrong connector type.

Post a copy of your current USBMap.kext or UTBMap.kext so we can see exactly what you are using for your custom USB configuration.

This is the way you should be setting your USB port connector types, when creating a custom USB kext.
  1. USB2 (0) - Physical USB2 ports on rear I/O plate, these ports always have a Black coloured tang.
  2. USB3 (3) - Physical USB3 ports on rear I/O plate, these ports can have a Red, Blue, Cyan or Yellow coloured tang.
    1. Virtual USB2 ports - served from physical USB3 ports) should be set with the same connector type as the physical port
  3. USB3 (3) - Motherboard Header, usually serving the case front USB3 ports.
    1. Virtual USB2 ports - served from physical USB3 ports) should be set the same as the physical port
  4. Internal (255) - Motherboard USB2 header, this will be any device served from a header port, such as Bluetooth module, case front USB2 ports, case front card reader etc.
    1. Internal connector type should also be used for any Bluetooth USB connection from a built-in M.2 connector (on the Rear I/O plate).
  5. Type-c+sw (9) - Type-C connector on Rear I/O plate, will only show two ports being available,
    1. when the Type-C device is inserted, removed, flipped 180° and reinserted, 1 x Physical Type-C and 1 x virtual USB2 port.
  6. Type-c (10) - Type-C (E) motherboard header, will show four ports being available from a single Type-C connector,
    1. when the Type-C device is inserted, removed, flipped 180° and reinserted, 2 x Type-C and 2 x USB2.
Your MSI X870 motherboard contains the following USB ports & headers.
  • 4x USB 2.0 (Rear) - USB2.0 (0) connector type
  • 4x USB 2.0 (Front) - Internal (255) connector type
  • 2x USB 5Gbps Type A (Rear) - USB3 (3) connector type
  • 2x USB 5Gbps Type A (Front) - USB3 (3) connector type
  • 2x USB 10Gbps Type A (Rear) - USB3 (3) connector type
  • 1x USB 10Gbps Type C (Front) - Likely to be Type-c (10) Connector type
  • 1x USB 20Gbps Type C (Rear) - Likely to be Type-c+sw (9) Connector type
  • 1x USB 40Gbps Type C (Rear) - Likely to be Type-c+sw (9) Connector type
This means you could have 28 x USB ports available in your AMD system. Probably split between 3 or more USB controllers.

You need to remember that the 15 x USB port limit is PER CONTROLLER, not an aggregate of all USB controller ports. As Intel motherboards tend to only have 1 x USB controller (XHC) that limits Intel systems. AMD system are not the same, they can have multiple USB controllers allowing for a larger number of ports to be active at the same time.

As an example my X570 system contains 3 x USB controllers and this allows me to activate 28 x USB ports across the 3 x controllers.

Screenshot 2025-05-12 at 00.27.16.png X570 motherboard with 28 x USB ports active, viewed in Hackintool.

Just remember that Hackintool is as likely to mess up the USB configuration on an AMD system, as it is to show it correctly. As it is aimed at working with simpler Intel USB configurations.
 
  • Like
Reactions: Katanoko1221
Regarding your MmioWhitelist issues, have you read and followed this guide?
I allow myself a playful joke with you
of that guide I recommend reading the last chapter first (resources)
;)
From there you can better see the help that the Opencore developers (vit and DF) gave me to do a serious debugging of one of the Threadripper platform (sTrx4 and not x399)

On Am5 the story of the MMIO is a bit different and the goal of reassigning them as much as possible to UEFI/bios is no longer (perhaps) the correct path

For the rest I completely agree with your suggestions and the problem of working in the bios settings I said in my first posts

personally I do not know if one of the user components can have problems with OSX, but investigating the USB part could help him better to understand
 
Yes your guide is a good link, but maybe a little more in depth than the OP can deal with. I was trying to keep it as simple as possible.

We will see what is what, when the OP provides a copy of their current USB configuration. I would put a lot of money down as a bet that there are multiple issues in the USB configuration.
 
  • Like
Reactions: fabiosun
Yes your guide is a good link, but maybe a little more in depth than the OP can deal with. I was trying to keep it as simple as possible.

We will see what is what, when the OP provides a copy of their current USB configuration. I would put a lot of money down as a bet that there are multiple issues in the USB configuration.
This is my USB map kext and Acpi.

Thank or your effort 🙏
 

Attachments

Your UTBMap.kext/Contents/Info.plist shows you are trying to activate 18 x USB ports. What happened to the other 10 x USB ports in your system, are you not using them?

You need to add 'Nicknames' (comments) to each port so it is clear which port is being activated when you are doing the Port Discovery in USBToolBox Tool. As an example I have attached a screenshot showing the UTBMAp.kext/Contents/Info.plist from one of my Dell OptiPlex Micro systems.

Screenshot 2025-05-12 at 14.10.54.png Example of Info.plist with #comments for each port, confirming type and position of each port.

Your Info.plist has none of this information, so it is impossible to tell which port on the rear I/O plate or which internal Header the USB port is served from.

Screenshot 2025-05-12 at 14.14.38.png Screenshot 2025-05-12 at 14.14.55.png The Info.plist from your UTBMap.kext

There are 11 x ports under the XH00 controller, there should be an even number probably 14 x ports.

The only controller that looks correct is the XHC1 controller, as this has 4 x ports servers from one of the Type-C ports and one USB3 port on the Rear I/O plate.

Why is there only 1 x USB port under the XHC2 controller, there should be 2 x ports as a minimum (more likely to be 4 x ports to match with XHC0 and XHC1), especially if these are two of the physical USB2 ports from the Rear I/O plate.

Using these two screenshots showing the ports on the Rear I/O plate and the header ports on the motherboard layout might help when it comes to adding a description/comment/nickname to each port in USBToolBox Tool.

Screenshot 2025-05-12 at 14.16.23.png

Screenshot 2025-05-12 at 14.16.42.png USB headers highlighted
Type-C/E header - Cyan
USB3 header - Yellow
2 x USB2 headers - Red
 
@Edhawk
Thank you for your clear explanation about "USB ports".
Anyway, in this case what do you suggest to me to doing?
This is result by using "USB-map tool" used on Win 11, the four rear "USB 2.0" come display me like a unique hub with 4 ports, and the port "USB-C 40G" i don't know why the tool don't detect it...
This is my first time that i've doing a Ryzentosh and i've discover something of new about this wonderfull build config!!!

Thank for your efforts 🙏
 
  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.