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!

 

[fabiosun]

@JohnFante
I used now your last working EFI backup
This EFI couldnt work for latest OS for three main reasons
New AMD kernel patches, new MMIO changed with latest bios you use and SecureBootModel setting
Let see now
i disabled some kexts for now till you will be able to pass that hang
Edit
I updated Opencore bootloader and kexts used
I left the same acpi patch and SSDT you used before
if we had again ACPI errors we had to use the new ones

 

[JohnFante]

Success It lives!!!!

It takes a bit to load - but it BOOTS. Will test more in depth over the weekend and transfer the EFI to the NVME where Sonoma is located.

Do you have an idea of why creating a new EFI did not work?

Thank you very, very much for all your help.

 

[fabiosun]

I suggest to try to leave only the second mmio enabled and see if it boots fast
If you have all stuff i see in your signature maybe some devices slow your boot

 

[JohnFante]

A minor thing.

My NVME partitions - Sonoma and the EFI is showing up on the desktop. I would like to have them hidden. Is'nt innie the kext to use for that anymore?

 

[Edhawk]

Innie.kext is used to make Internal drives appear correctly. Are these two icons from an internal drive or a USB?

 

[JohnFante]

Innie.kext is used to make Internal drives appear correctly. Are these two icons from an internal drive or a USB?

It is the internal NVME where the EFI and Sonoma are installed. Used innie before to hide the drives, and it is, as far as I can see, enabled. Not a big thing. Just wondering.

BTW: Copied the EFI from the USB to the internal EFI partition. That gave the boot some more speed. Super stable system so far.

 

[fabiosun]

t is the internal NVME where the EFI and Sonoma are installed. Used innie before to hide the drives, and it is, as far as I can see, enabled. Not a big thing. Just wondering.

i use Device Properties to bypass orange icon for internal drive
you could try the same
you could also try with external icons quirk
I prefer Device Properties and use less kext i can

 

[fabiosun]

@JohnFante if you like to use innie kext as before and you had success with my last EFI, enable it again
usually i disable all not mandatory stuff to resolve booting problem

 

[JohnFante]

@JohnFante if you like to use innie kext as before and you had success with my last EFI, enable it again
usually i disable all not mandatory stuff to resolve booting problem

Thought it was added Did that and now it works. Thank you!

 

[JohnFante]

@JohnFante if you like to use innie kext as before and you had success with my last EFI, enable it again
usually i disable all not mandatory stuff to resolve booting problem

Just a couple of final questions. Everyting is running fine.

Should I add my USB mapping via UTBMap.kext together with USBToolBox.kext?

And are there any other kext's that I should consider? See list.

And finally: I continue to get debug output when I boot even thou I have switched it all off. Anything I am missing?

Thank you for all your help!

 

[fabiosun]

Should I add my USB mapping via UTBMap.kext together with USBToolBox.kext?

yes

And finally: I continue to get debug output when I boot even thou I have switched it all off. Anything I am missing?

you have to change also opencore.efi from debug to a non debug version
and remove also -v bootarg from your config.plist (nvram section)

 

[JohnFante]

you have to change also opencore.efi from debug to a non debug version

I am having an issue that I am not sure what is causing.

My BIOS is set to booting from OpenCore.

When I boot it goes into the picker as it should. However quite often (fifty-fifty) when I select Sonoma it stops immediately and shows the picture below. Then I reset and after a try or two it boots normal. No complaints about errors or anything afterwards.

I can see that you used a beta (?) version of OC - 1.04 - in the EFI you posted in post 41 and that fixed my initial problem. Is that the repo found here?

Can the issue I am having be due to OC being 1.04? I have not tried updating yet. Want to be sure that it is the right repo I am taking it from.

Thank you in advance!

 

[fabiosun]

@JohnFante Proihibit sign could be related to usb problems.
did you do what i suggest some message ago about MMIO?
You enabled 4 MMIO areas, have you tried to leave enabled only one (the second one in your MMIO list)?
Opencore is not a problem and you could update from a release version to a dev version as you like

 

[JohnFante]

@JohnFante Proihibit sign could be related to usb problems.
did you do what i suggest some message ago about MMIO?
You enabled 4 MMIO areas, have you tried to leave enabled only one (the second one in your MMIO list)?
Opencore is not a problem and you could update from a release version to a dev version as you like

Did not change MMIO. Yet.
If it broken do not try ... and so on. I was just glad it booted.
Will experiment with MMIO

 

[JohnFante]

@JohnFante Proihibit sign could be related to usb problems.
did you do what i suggest some message ago about MMIO?
You enabled 4 MMIO areas, have you tried to leave enabled only one (the second one in your MMIO list)?
Opencore is not a problem and you could update from a release version to a dev version as you like

You were right! :-D

Enabling only the second MMIO did the trick. Rock solid boot!

Now I "only" need to get my AMD Wi-Fi 6E RZ616 WIFI-bluetooth to work! Do not need the wifi part. Sadly, as far as I am aware, it is not supported atm.

Thank you for all your help!