Ryzen 7000 Testing

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:

D7EF561C-F273-4F0E-8AF7-0DFF7B22E561.jpeg

and a few seconds later this:

1930E6B2-D8E2-4EBE-A6A7-C8705B352D96.jpeg

and then back to the OpenCore selection screen

On the second try it showed this:
99122F4D-55A5-47EE-9579-75E1B5471E12.jpeg

that was in Ventura....

and in Monterey this comes out:

560D135A-BEBF-4865-9A35-591C69D4DC88.jpeg
 
  • Like
Reactions: 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
 
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 (y)

Monterey:

D95E9D53-A517-4F3D-B930-38C99CA19FBD.jpeg

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

178ABB45-436D-4222-8C82-0D2AA6284A57.jpeg

Sysreport has not generate with last EFI
 
Last edited:
  • Like
Reactions: ExtremeXT
If I have tried it right now... I am attaching some screenshots from my mobile, one second (y)

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
 
EB|LOG:EXITBS:START usually means you need to add -no_compat_check to the boot-arg to bypass.
 
  • Like
Reactions: 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
 

Attachments

@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 🤷‍♂️
 

Attachments

@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
 
  • Like
Reactions: 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 😆
 
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.
 

Attachments

  • Like
Reactions: PoMpIs
@ExtremeXT

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

0AB5A8A3-FCF3-412F-80D2-0A08ABA43764.jpeg

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 (y)
 
  • Like
Reactions: ExtremeXT
It takes a long time to return to the OpenCore selection screen... but now I've caught a screenshot...

this is with Monterey:

ED0D0FFA-CB26-4AE7-9DBB-842F23CD0C43.jpeg

A835EF17-3CFA-4B19-809D-C7D8BBD08D94.jpeg
 

Attachments

@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
 

Attachments

  • Screenshot_18.png
    Screenshot_18.png
    26.2 KB · Views: 32
  • EFI.zip
    EFI.zip
    7 MB · Views: 18
  • Like
Reactions: craighazan
  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.