Post a copy of the whole EFI folder that you are currently using, as the OpenCore log shows a few errors, which I would like to examine.
You seem to have a number of drives present in your system. It would be best if you were to remove all internal drives except the drive on which you plan to install macOS. So you only have the external USB installer and the internal macOS drive present and working.
These other drives can be reconnected after you have installed macOS.
Hi Edhawk, I am attaching the EFI folder I'm using as well as OpenCore log and SysReport folder. I followed all your advises and removed all internal drives except the SSD I am using for mac OS install. Unfortunately again without success
First thing of note when reviewing you EFI folder contents is that you have a few elements with different dates, i.e. drivers, tools, OpenCore.efi & BOOTx64.efi are not from the same OpenCore release. This is a big No-No when using OpenCore.
This is a view of your current EFI folder contents.
You have a spurious entry in the Drivers folder, Archive.zip, which shouldn't be there.
You have an SSDT-Basic-AM5.aml table.
Which appears to duplicate three of the custom SSDT's in your ACPI folder.
SSDT-EC.aml,
SSDT-PLUG-ALT.aml and
SSDT-USBX.aml.
It also contains a number of USB power options, which while similar to the SSDT-USB-Reset.aml table contents aren't a complete match for your USB port controllers.
This custom ACPI table, if not correct will only cause unnecessary boot issues, so it might be best to remove it and see if the others can deal with the boot process without any clashes with this table.
Were I to create an EFI folder for you, it would contain the following: Revised & cleaned up EFI folder contents, using OpenCore v1.0.3 with latest kexts etc.
I need to go though your config.plist, before attaching the revised EFI folder. That will be in the post below.
Hi, it is the one i use
it is not flagged in his config and for him i used standard SSDT
I have no idea why his system hangs in that way..but it shouldnt be an EFI problem (IMHO)
It is obviusly not perfect but it allows (with little modifications ) to boot different systems
I have gone through your config.plist and created a new one based on the revised EFI folder contents and what I think will be a better fit for your AM5 system. Copy of the revised EFI is attached below.
Do not change anything in the EFI. Try it as it stands, if a kernel panic happens, take a photo of the verbose text and post a copy here, of I can see what needs attention.
Simply copy the revised EFI (after renaming it 'EFI') to your USB installation drives EFI partition.
Boot the OC EFI
When you get to the OC boot screen, should be the GUI not the picker list, press the spacebar.
This will unhide the drivers in your OC setup, select ResetNvram and the system should automatically reboot.
Boot to OC and select installer for macOS.
Remember you should only have the USB installer and the proposed macOS drive present in the system when installing macOS.
I think there might be a small difference between your ASUS Pro Art board and the Gigabyte X870 A/E board used by hinkin, specifically with one of the USB controller ACPI names/paths. I don't have a copy of the X870 system DSDT.aml table to check this but based on the SSDT-USB-Reset.aml table contents there is definitely something not quite right.
So depending on which USB controller is different, and which USB port is being used for the installation a kernel panic might not be so unexpected.
Apologies if you felt I was in anyway saying anything was wrong with your EFI, that was never my intention.
I very much doubt that the EFI I have created is perfect either, but hopefully it will help.
yep..you miss an important aspect, MMIO Devirtualize quirk is mandatory to boot with a proper MMIO Whithelist area set (Area is set fine but not useful without quirk)
If you want try without MMIO whitelist area set you have to flag DisableVariableWrite (but usually is not advisable
SSDT-basic - AM5 is for my previous Asus x670E Hero board (works luckily also in this Asus X870E proart, but as you said could be not good also for my new motherboard)
Thank you very much for your time, work and willingness to help me. I followed all the steps using rev1 and rev2.
The problem I'm facing is at the very beginning. I'm attaching a few screenshots, which I hope are sufficient. Unfortunately the installation stops at the very beginning and that's all I see.
Solution 1 (using MMIO whitelist as i see in Edhawk's rev2 EFI
DevirtualiseMmio = on
EnableWriteUnprotector=off
Solution 2 (using same EFI but i suggest to use solution 1)
Same all Booter/quirk
DevirtualiseMmio = on
DisableVariableWrite=on
I permit to say you, to check EFI i posted which allows you to see installation part (almost some steps forward you achieve with latest EFI tries)
I would only correct ACPI/SSDT with standard ones (i use one for my old x670E hero wich work also with my x870e Proart
Other critcal part is ACPI / Patches
SSDTtime produces one for your Gigabyte
I would try also to use another disk type for your OSX installation
attached my Booter and Kernel quirks:
you can off here Aquantia
and these are kernel patches i use (Visual patches are not usefull for you)
I tried Solution 1 with Edhawk's rev2 EFI with the settings bellow(see screen 1)
DevirtualiseMmio = on
EnableWriteUnprotector=off
For the Solution 2 I used the same EFI applying these settings and again got an error (see screen 2).
DevirtualiseMmio = on
DisableVariableWrite=on
Finaly did the same settings as the ones attached from your Booter and Kernel quirks ticked on the screens but again with no success.
I may have misunderstood something or done it incorrectly. I am applying rev2 EFI with the last changes I have made.
I suggest to revisit my initial EFI which allowed you to see OSX installer menu and use on that EFI SSDT proposed in this EFI (Rev 2)
i would add only your ethernet kext and disable from bios WIFI and BT devices
I tried your initial EFI which allowed me to see the OSX installer. I also enabled M5 platform as on the picture. The installation started Ok but when it reached 12 minutes everything stopped end finally an error message came up.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
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.