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

[Katanoko1221]

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.

 

[Katanoko1221]

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

The change of setting about that value of the bios I thought had solved the start -up problma, but nothing to do.
At next time i try to take a pics or video about the issue, but now i'd guess these issues could be caused also about wrong usb mapping.

Thank for your effort

 

[Edhawk]

You need to re-discover all the ports on your system. Set aside your current UTBMap.kext and start afresh.

If you can boot in to macOS, use Corpnewt's USBMap script, as that is what USBToolBox Tool is derived from. Do not use the Hackintool app.

 

[unclesam]

@unclesam if the solution is to use different Fix pat than the Shaneee zormeister one..it is a not good solution because you loose so muche GPU performance in many tasks

If you use AppleALC kext the good solution is to test different layout id for your audio, till you find the right one

@fabiosun
Thanks for the reminder! I later switched to Shaneee's version of PAT and noticed a significant boost in game performance. For example, a game that originally ran at only 30 FPS can now reach 55–60 FPS with Shanne's PAT. It's truly amazing.
I love AMD, and I love all of you!

By the way, is it possible to use a similar approach for a AMD GPU on an Intel-based Hackintosh? From what I’ve read, this method is mostly intended for AMD Ryzen Hackintosh — is that correct?

 

[Katanoko1221]

You need to re-discover all the ports on your system. Set aside your current UTBMap.kext and start afresh.

If you can boot in to macOS, use Corpnewt's USBMap script, as that is what USBToolBox Tool is derived from. Do not use the Hackintool app.

Ok, thank you!!!
I'll update you after re-mapping...

 

[Katanoko1221]

@Edhawk

I tried to map but it doesn't show all the ports. Can you explain to me briefly what options I should select?

Another strange thing, after I reset and put the “Dump-Kext” the macOS HD from “Ryzentosh HD” as I had called it, automatically changed its name to this one in the photo, how could it have happened

Thank in advance

 

[fabiosun]

@Katanoko1221 i see Luca..Italian?
I advice to do that mapping on windows because OSX does not see USB4 asmedia controller (if you have)
then you must put in every your USB ports different USB sticks (usb 2/3 Type C and comment every port as requested
i put a (bad) example of what you should have then if you check your mapping:

 

[Katanoko1221]

@Katanoko1221 i see Luca..Italian?
I advice to do that mapping on windows because OSX does not see USB4 asmedia controller (if you have)
then you must put in every your USB ports different USB sticks (usb 2/3 Type C and comment every port as requested
i put a (bad) example of what you should have then if you check your mapping:
View attachment 17016

Yes I'm italian!!!
Ok, therefore, i use the tool on windows, put usb stick on each port and comment every port detected, ex."usb 2.o rear", Right?

Thank for you effort

 

[fabiosun]

Yes I'm italian!!!
Ok, therefore, i use the tool on windows, put usb stick on each port and comment every port detected, ex."usb 2.o rear", Right?

Thank for you effort

Si per tutte le porte inserisci le diverse usb e aspetti che vengano ri conosciute e puoi nominarle come vedi dalla mia foto
Yes
For all usb Ports and you have to wait tool recognized them
Then you can name it as you see in my picture

 

[Katanoko1221]

Si per tutte le porte inserisci le diverse usb e aspetti che vengano ri conosciute e puoi nominarle come vedi dalla mia foto
Yes
For all usb Ports and you have to wait tool recognized them
Then you can name it as you see in my picture

Ok, perfect. This week-end I'll to re-mapping usb port.
This is the video about "Boot-startup" issue, Video Boot-issue .
Maybe caused to an errate setting on a "config.plist"?

Thank you

 

[fabiosun]

Maybe caused to an errate setting on a "config.plist"

I do not think
Try to delete -v option (to see apple logo during boot part and no verbose output)

 

[Katanoko1221]

I do not think
Try to delete -v option (to see apple logo during boot part and no verbose output)

Today later I’ll go to re-map usb ports. I’ve read that “AppleAlc” kext in some case can create boot issue. Could be true this last???

Thank you

 

[Edhawk]

AppleALC.kext will only cause issues if you are using an old release, I.e. pre v1.9.3. As prior to that release builtin AMD audio was non-functional or very hit and miss, on most AMD boards. With users relying on VoodooHDA.kext to get their audio working.

If your board has USB audio, I.e. ALC4032 or similar then AppleALC.kext doesn’t work and needs to be replaced with AppleALCU.kext. I have a couple of Mini PC AMD systems that require the alternative audio kext. The USB Audio port also needs to be Included in your USB configuration, with connector type ‘Internal’.

 

[Katanoko1221]

AppleALC.kext will only cause issues if you are using an old release, I.e. pre v1.9.3. As prior to that release builtin AMD audio was non-functional or very hit and miss, on most AMD boards. With users relying on VoodooHDA.kext to get their audio working.

If your board has USB audio, I.e. ALC4032 or similar then AppleALC.kext doesn’t work and needs to be replaced with AppleALCU.kext. I have a couple of Mini PC AMD systems that require the alternative audio kext. The USB Audio port also needs to be Included in your USB configuration, with connector type ‘Internal’.

Ok, then is not AppleAlc cause to boot issue because I’ve the last release. At this point could be or “Usb-Map” or some “Kext or Acpi” to set better?

Thank you

 

[Katanoko1221]

You need to re-discover all the ports on your system. Set aside your current UTBMap.kext and start afresh.

If you can boot in to macOS, use Corpnewt's USBMap script, as that is what USBToolBox Tool is derived from. Do not use the Hackintool app.

I mapped the USB ports, the problem with powering on has improved a lot, but as far as turning off the PC is concerned, nothing has changed. I read that to solve these problems it is important to also set the Acpi and detect the DSDT via “macAsial” to solve the thing, how should I set it?

Thank you

 

[Edhawk]

What have you read and where did you read it?
Can you provide a link to what you read regarding ACPI & DSDT, as I am not sure what you are alluding to with the post above.

Can you post a copy of your new/revised USBPorts kext, so we can see what you have generated.

 

[Katanoko1221]

What have you read and where did you read it?
Can you provide a link to what you read regarding ACPI & DSDT, as I am not sure what you are alluding to with the post above.

Can you post a copy of your new/revised USBPorts kext, so we can see what you have generated.

Yes of course, i've follow your instruction to detect and rename usb ports with a "USB-Map script" on macOS and i've put all port detected without 15 port limit.
Later i'll try to repeat this operations also in Windows, why there is case that detection ports working better respect macOS.
I've follow this guide to fix "Shutdown/Restart" and set SSDT. Shutdown/Restart - Fix
I am attaching the "Kext USB" and the DSDT I generated, you know if there is a system to be able to send you the complete DSDT list detected with "macasial", I would not like to make a mistake to set some parameter...

Thank for your effort

 

[Edhawk]

Your USBMap.kext/Contents/Info.plist too me looks a mess! It is definitely not what I would expect to see when interrogating the active/disabled ports in your system.

You are disabling 13 x ports, which is more than you are activating (x 9). See the highlighted ports in the two screenshots below, all of them are disabled.

USBMap.kext/Contents/Info.plist screenshots

I would expect each of the smaller Controllers to contain at least 4 x USB ports (could be anything between 4 & 10 ports), all of which can be activated. The large Controller normally contains 14 x Ports. I wouldn't expect any of the controllers to exceed this number of ports.

I am not sure you know what you are doing when using the USBMap script.

I can only suggest you try following the guides linked below and see if you can generate a better, more suitable, USB configuration for your AMD system.

Simple guide - https://github.com/Mahasvan/UsbMapGuide

Dortania guide - https://dortania.github.io/OpenCore-Post-Install/usb/manual/manual.html#usb-mapping-the-manual-way

Just remember that EACH USB Controller can activate up to 15 x USB ports. As the limit is 15 x ports per controller not a maximum of 15 x ports over the 4 x Controllers.

So in theory your AMD system with 4 x USB Controllers could activate up to 60 x USB ports, not that your system will contain anywhere near than number but each controller can support 15 x active USB ports.

 

[Edhawk]

The FixShutdown-USB-SSDT.aml you provided is based on an old Intel Haswell fix. One I used many years ago when OS X Mountain Lion and Mavericks were first released.

It has been adapted to 'fix' one of the four USB controllers in your setup - XHC0. It would have no bearing on any of the other 3 x USB controllers in your system. So I would wonder at its usefulness.



Have you added the companion _PTS to ZPTS ACPI rename patch shown below to your config.plist? As without this ACPI patch the SSDT will do nothing.



You may need multiple SSDT's of this nature if you think this old Haswell fix is really necessary for your AMD USB ports, i.e. one for each Controller.

My opinion is that you are using something unnecessarily, that will ultimately do nothing for your USB Sleep/Wake issues. I have not heard of anyone else using this old Sleep Fix with a modern AMD motherboard.

 

[Katanoko1221]

@Edhawk Ok, thank for your reply.
Now i try to consult the guide that you suggest to me and this time i try to run the tool on Windows, like has told me @fabiosun.
Ok, now i've learned that issue is only about a wrong "usb-mapping". About "DSDT" i've apply both "Acpi & Patch" in below patch list. But now, i convicted that it's only a old useless method no valid about AMD.

Thank for your effort

 

[Katanoko1221]

@Edhawk
I am attaching the Kext of the last mapping and a screenshot where I pointed out the doors I detected with the different devices.
Also this time scarce results, but I am impracticing myself with this tools

Thank for your effort