Ryzen 7000 Testing

[PoMpIs]

@PoMpIs Can you try this DEBUG EFI? Boot macOS and when it gets stuck again take a screenshot, boot back to another OS and zip the log file + the SysReport file at the root of the EFI partition.

- ExtremeXT

Result of this EFI:

 

[PoMpIs]

Definitely seems to be TSC related I think. Give this a go.

With this EFI in the first attempt this came out on the screen:



and a few seconds later this:



and then back to the OpenCore selection screen

On the second try it showed this:


that was in Ventura....

and in Monterey this comes out:

 

[ExtremeXT]

With this EFI in the first attempt this came out on the screen:

View attachment 7460

and a few seconds later this:

View attachment 7459

and then back to the OpenCore selection screen

On the second try it showed this:
View attachment 7461

that was in Ventura....

and in Monterey this comes out:

View attachment 7462

Prohibited sign is good news, as it means that we passed the error. Did it have text on the left of it? Can you try the latest EFI I sent too?

- ExtremeXT

 

[ExtremeXT]

Result of this EFI:

View attachment 7458

Please leave it running until macOS loads, it's slow because it's writing things to the log.

- ExtremeXT

 

[PoMpIs]

Prohibited sign is good news, as it means that we passed the error. Did it have text on the left of it? Can you try the latest EFI I sent too?

- ExtremeXT

If I have tried it right now... I am attaching some screenshots from my mobile, one second

Monterey:



in ventura it restarts in 3 seconds, this is what i had time to capture:



Sysreport has not generate with last EFI

 

[ExtremeXT]

If I have tried it right now... I am attaching some screenshots from my mobile, one second

Monterey:

View attachment 7463

in ventura it restarts in 3 seconds, this is what i had time to capture:

View attachment 7464

Sysreport has not generate with last EFI

Okay, I know how to fix non monotonic time, I'll send a new EFI in a bit.

- ExtremeXT

 

[Middleman]

EB|LOG:EXITBS:START usually means you need to add -no_compat_check to the boot-arg to bypass.

 

[ExtremeXT]

@Middleman
The only thing -no_compat_check does is bypass the SMBIOS check, as they're using MacPro7,1, it won't do anything.

@PoMpIs
Please try this one.

- ExtremeXT

 

[PoMpIs]

@ExtremeXT

My apologies, I have generated the Sysreport again, the first time I tried it when I saw that it did not progress, I restarted the computer ... my fault, sorry

Now it is complete

 

[PoMpIs]

@Middleman
The only thing -no_compat_check does is bypass the SMBIOS check, as they're using MacPro7,1, it won't do anything.

@PoMpIs
Please try this one.

- ExtremeXT

tested this last efi

Ventura:



Monterey:

 

[ExtremeXT]

tested this last efi

Ventura:

View attachment 7467

Monterey:

View attachment 7468

Can you make an USB map? Send the UTBMap file here.

GitHub - USBToolBox/tool: the USBToolBox tool

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

github.com

- ExtremeXT

 

[PoMpIs]

Can you make an USB map? Send the UTBMap file here.

GitHub - USBToolBox/tool: the USBToolBox tool

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

github.com

- ExtremeXT

Yes of course, it's what I use for my other hacks

It has a lot of usb

 

[PoMpIs]

@ExtremeXT

Is that okay?? or do I have to remove more ports?

I have tried them all except the Type-C that I do not use

 

[ExtremeXT]

@PoMpIs
Your log file is still not complete, you have to boot macOS too, wait until it gets stuck with the DEBUG EFI.

Your map is fine as you're under the 15 ports limit. You shouldn't remove any unless you are above 15 ports per controller.

- ExtremeXT

 

[PoMpIs]

@PoMpIs
Your log file is still not complete, you have to boot macOS too, wait until it gets stuck with the DEBUG EFI.

Your map is fine as you're under the 15 ports limit. You shouldn't remove any unless you are above 15 ports per controller.

- ExtremeXT

The EFI that generates the LOG does not go beyond there, at the end it returns to the OpenCore selection screen, it does nothing else

i will try again, It is fun

 

[ExtremeXT]

The EFI that generates the LOG does not go beyond there, at the end it returns to the OpenCore selection screen, it does nothing else

i will try again, It is fun

OK, try this one.

 

[PoMpIs]

OK, try this one.

Testing......

I leave you while another report, this one must be full

 

[PoMpIs]

@ExtremeXT

well, with this last efi it stops here for two minutes



and then the screen goes black and after 5 minutes it returns to the OpenCore selection screen... I have started Ventura and this time it has come much further, but when i was going to take the picture it restarted..

I'm going to try again to see if I get the picture

 

[PoMpIs]

It takes a long time to return to the OpenCore selection screen... but now I've caught a screenshot...

this is with Monterey:

 

[ExtremeXT]

@PoMpIs I got the log, no need for more DEBUG stuff.

Looks like Zen 4 will require extra setup like Threadripper.

In the EFI I sent, scroll down to MmioWhitelist and you will see this (Image 1). You will notice that the first entry is set to True. What MmioWhitelist does is it whitelists MMIO Spaces from being devirtualized by DevirtualizeMmio. Problematic boards like TRx40 will require us to only devirtualize some MMIO spaces, else it will get stuck at PCI. Basically you have to try to whitelist each one and see if it gets past preboot or gets memory corruption. Try to boot with the first one being whitelisted, if it gets stuck again at PCI (or boots?) then leave it whitelisted, if it gets stuck at preboot unwhitelist it (set Enabled to false). Repeat this for each of the 5 entries in MmioWhitelist and let me know the results (which ones have to be whitelisted).

- ExtremeXT