Can not get DevirtualiseMmio to output MMIO with OC debug

[JohnFante]

I am trying to revive an old Sonoma install with a new EFI using this: https://github.com/mikigal/ryzen-hackintosh as base.

It does not work atm. Crashes very rapidly after trying to boot Sonoma. See picture of crash. As a solution I was recommend to setup MMIO with DevirtualiseMmio using debug version of OpenCore.

The procedure (using OC 1.03) and the instructions here produces the attached logfile but no MMIO info in it

Anyone seeing anything wrong in the config.plist for MMIO logging? I am pretty sure I followed the instructions but can have done something wrong . Just edited the config.plist and replaced OpenCore.efi with the debug version. Only that. (Should I copy the complete package?)

My hardware is the as described in my signature. That should be supported out of the box for that example EFI.

Thank you in advance!

 

[JohnFante]

Have you tried my config.plist?

I did. And thank you very much for that,. Same result. At least as I can see it. I can send til log form the Edhawk's and your version. As I see it they are similar. But I am not an ekspert in any way

 

[fabiosun]

@JohnFante if you like try this config (rename it before) and let see if you do a step forward
in this config i have bypassed (for now ) mmio whitelist to see if your config has oter problems than MMIO!
Post a photo or a video where it hangs

 

[JohnFante]

@JohnFante if you like try this config (rename it before) and let see if you do a step forward
in this config i have bypassed (for now ) mmio whitelist to see if your config has oter problems than MMIO!
Post a photo or a video where it hangs

Thank you! Here is where I got to. Log and screenshot.

Had to find the SSDT-EC-USBX-AMD.aml in an old EFI. Hope it is the one you meant.

 

[fabiosun]

@JohnFante i see always an important ACPI error
This means your DSDT must be patched better (via ACPI patches)
i sent your DSDT to CorpNewt and he will take a look on it whwn he has time

 

[JohnFante]

@JohnFante i see always an important ACPI error
This means your DSDT must be patched better (via ACPI patches)
i sent your DSDT to CorpNewt and he will take a look on it whwn he has time

Aha. Thank you for doing that. Interresting if that is where the issues are Standing by.

 

[fabiosun]

@JohnFante
I wonder if you update your motherboard bios from when you had a working sonoma in this system
If not, it is weird ifyou didnt use acpi patches or dsdt patched before

 

[JohnFante]

@JohnFante
I wonder if you update your motherboard bios from when you had a working sonoma in this system
If not, it is weird ifyou didnt use acpi patches or dsdt patched before

I have updated my bios. And did that several times, when the Sonoma install was working. I am now on F33: https://www.gigabyte.com/Motherboard/X670E-AORUS-MASTER-rev-1x/support#support-dl-bios. There have been a massive number of improvement in the bios.

I was on F33 when things went haywire because I decided (not smartly) to update OC and the kexts. Using OCAT. That broke the EFI.

Since the old install I was running was not running smoothly I decided to try to build a new EFI. The old EFI took ages to boot the system and the fans were way to loud.

 

[fabiosun]

Since the old install I was running was not running smoothly I decided to try to build a new EFI. The old EFI took ages to boot the system and the fans were way to loud.

could you post only ACPI section of that config.plist (the working one i mean)

 

[fabiosun]

@JohnFante with the help of CorpNewt from AMD OSX Discord channel he understood that some SSDT was not proper for your system
try this EFI
then if system does a step forward we will try to adjust MMIO Area
if you have 4G option in your BIOS set it to on

 

[JohnFante]

@JohnFante with the help of CorpNewt from AMD OSX Discord channel he understood that some SSDT was not proper for your system
try this EFI
then if system does a step forward we will try to adjust MMIO Area
if you have 4G option in your BIOS set it to on

Thank you very much to you and CorpNewt!

Unfortunately it does not go any further.

Attached is the log and a screenshot of where it stops.

I am not sure if this in any way helps but along the way of solving this I found the @CaseySJ 's thread about "Asus X670E Gene EFI -- Adaptable to Other X670, X670E, B650 and B650E Boards".

In post 30 he post an EFI that creates a SysReport. I did that and it is attached in can help in some way or form.

 

[fabiosun]

@JohnFante
Are you sure you are using Efi i posted above?

 

[JohnFante]

@JohnFante
Are you sure you are using Efi i posted above?

99,99 pct. I will redownload and test again tomorrow.

I am trying to download the EFI again but the server is very slow atm., so I will try tomorrow morning again.

 

[fabiosun]

99,99 pct. I will redownload and test again tomorrow.

I am trying to download the EFI again but the server is very slow atm., so I will try tomorrow morning again.

Johnfante, use this EFI
you should see a different graphic in boot menu
Let see if we win
I used latest data from your SysReport folder and all the patches SSDTTime does for your system also used a minimal set of kext..if it will work then you have to add other kexts and map your USB port

 

[JohnFante]

That was definately a new EFI

It was not an debug OC - at least as I see it - it loaded fast and there was nothing in the log.

It crashed very rapidly with this output.

 

[fabiosun]

That was definately a new EFI

It was not an debug OC - at least as I see it - it loaded fast and there was nothing in the log.

It crashed very rapidly with this output.

Using the same EFI only change this config.plist
Let see if it does some good results
Clean Nvram (as usual)

 

[JohnFante]

Using the same EFI only change this config.plist
Let see if it does some good results
Clean Nvram (as usual)

Replaced config.plist. Booted from USB and reset NVRAM. Got this far. Picture and log.

 

[fabiosun]

Mmhhh now no ACPI error (it seems so) but no boot
could you try this and if it is the same hang try to change only usb port you are trying to boot?

 

[JohnFante]

Mmhhh now no ACPI error (it seems so) but no boot
could you try this and if it is the same hang try to change only usb port you are trying to boot?

I replaced the config.plist. Reset nvram. Boot from USB3 front port - as usual. Crash. log (USB3 in the end) and crash picture attached.
I then changed to USB2 front port. Crash. Log (USB2 in the end) and crash picture attached.

I have allways used the frontports to boot USB EFIs. Normally no issues there.

 

[fabiosun]

@JohnFante I am short of ideas to try
I bypassed MMIO stuff using DisableVariable quirk and ACPI patches are there for your Gigabyte
I am very curious to see your previous working config.plist with Sonoma (and old bios version if i understood well your message because it is weird we havent success yet)
Edit:
in the past if i remeber well a gigabyte user had the same or similar problem with latest motherboard bios..if you can only to try, disable wifi or ethernet from motherboard bios and see if it hangs in the same place or boots

 

[JohnFante]

I replaced the config.plist. Reset nvram. Boot from USB3 front port - as usual. Crash. log (USB3 in the end) and crash picture attached.
I then changed to USB2 front port. Crash. Log (USB2 in the end) and crash picture attached.

I have allways used the frontports to boot USB EFIs. Normally no issues there.

The same here.

I have attached two EFI's. The one I messed up, and that started all this, when I updated to a newer version of OC via OCAT. Before the updated it booted. Slow. But it booted. After the crash I used WinEFIMounter to get to it.

Also included are an old backup EFI that I am almost sure is a backup of a the working one before an update of OC. It does not boot any more.

This can maybe be BIOS related.

In version F32 of the BIOS I had issues. More precisely I could not get it to accept the BIOS settings needed for MacOS. It would just not start. No Aorus BIOS logo just a black screen. And I had to reset the BIOS settings to get it to boot. With F33 that changed. I could now set it to the needed settings. I then booted and updated the OC version and messed things up.