ASUS PRIME Z390-A _Solved

[Ludox]

Hello everyone I recently updated my hardware, I changed my current motherboard (Asus Z87 Plus in signature) with ASUS PRIME Z390-A

Everything works great the hach is great, the only problem is the boot of Opencore, I'm using this currently, but I will try to make it work with Clover (always used this) I will explain the problem.
When I start everything is ok, while if I turn off or restart I get this startup (I attach a photo), while if I use windows or do a simulation with clover it does not happen everything is normal.
I was wondering if anyone has happened to it and how they solved it with OC

 

I also attach my EFI, it is possible that there is a wrong setting there that causes this problem.

 

Thanks

EFI.zip

[miliuco]

@Ludox

 

Have you been able to recover the boot process on the new motherboard? If you're stuck on that message and can't enter the BIOS menu, there are a few things you can try:

• Completely clear the CMOS chip to reset the BIOS: find out where are the two pins that need to be put in contact to clear CMOS -> turn off the PC -> remove the battery from the motherboard -> unplug the PC from the power by physically disconnecting the cable -> make contact for 1-2 seconds in the Clear CMOS pins -> reconnect the battery, plug the cable and restart.
• If this fails, you'll need to boot from a backup BIOS (which is copied to the main BIOS so it can boot). I believe your motherboard has two BIOSes, the main one and the recovery one. Each manufacturer implements this differently; I can't find detailed information about your motherboard, but these are some options.
  • Some motherboards activate the BIOS backup by holding Power and Reset for 10 seconds (try with the power cable in).
  • Others require you to turn the PSU switch off for a few seconds, flip it back on, press the power button on your case and, AS SOON* as the PC starts to power on, flip the PSU switch off. If it doesn't work the first time, do it 5 times in a row. Then it will start normally the 6th time, and it should attempt to flash.

AS SOON* Note: Unplugging the cable should be done as soon as possible after the motherboard boots up, almost immediately.

 

Tell me:

• dGPU model (if any, maybe the RX 6600 already owned?)
• CPU model (9 generation, I suppose)
• you have -liluslow in boot args, tell me why
• you have in ACPI -> Delete: SSDT iGPU table dropped, there is no OemTableId or TableSignature, what does it mean?

Edited April 19, 2025 by miliuco
typo

[Ludox]

1 hour ago, miliuco said:

@Ludox

 

Have you been able to recover the boot process on the new motherboard? If you're stuck on that message and can't enter the BIOS menu, there are a few things you can try:

• Completely clear the CMOS chip to reset the BIOS: find out where are the two pins that need to be put in contact to clear CMOS -> turn off the PC -> remove the battery from the motherboard -> unplug the PC from the power by physically disconnecting the cable -> make contact for 1-2 seconds in the Clear CMOS pins -> reconnect the battery, plug the cable and restart.
• If this fails, you'll need to boot from a backup BIOS (which is copied to the main BIOS so it can boot). I believe your motherboard has two BIOSes, the main one and the recovery one. Each manufacturer implements this differently; I can't find detailed information about your motherboard, but these are some options.
  • Some motherboards activate the BIOS backup by holding Power and Reset for 10 seconds (try with the power cable in).
  • Others require you to turn the PSU switch off for a few seconds, flip it back on, press the power button on your case and, AS SOON* as the PC starts to power on, flip the PSU switch off. If it doesn't work the first time, do it 5 times in a row. Then it will start normally the 6th time, and it should attempt to flash.

AS SOON* Note: Unplugging the cable should be done as soon as possible after the motherboard boots up, almost immediately.

 

Tell me:

• dGPU model (if any, maybe the RX 6600 already owned?)
• CPU model (9 generation, I suppose)
• you have -liluslow in boot args, tell me why
• you have in ACPI -> Delete: SSDT iGPU table dropped, there is no OemTableId or TableSignature, what does it mean?

• GPU model (if any, maybe the RX 6600 already owned?) yes installed
• CPU model (9 generation, I suppose) yes that one
• you have -liluslow in boot args, tell me why
• you have in ACPI -> Delete: SSDT iGPU table dropped, there is no OemTableId or TableSignature, what does it mean?

efi downloaded by a user who has the same motherboard

[strangeron]

<key>4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
            <dict>
                <key>rtc-blacklist</key>
                <data>WFk=</data>
            </dict>

and have you tried with DisableRtcChecksum=true

[Ludox]

14 hours ago, strangeron said:

<key>4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
            <dict>
                <key>rtc-blacklist</key>
                <data>WFk=</data>
            </dict>

and have you tried with DisableRtcChecksum=true

Solved
I added RTCMemoryFixup.kext, then on boot-arg rtcfx_exclude=00-FF is finally on NVRAM -> Add -> 7C436110-AB2A-4BBB-A880-FE41995C9F82
Thanks for the suggestions

[miliuco]

@Ludox

 

I'm glad it's working fine now.

Since it's a Z390 board, I didn't think it could be an RTC issue. I never had this issue on my Hack, which is also Z390 but different brand.

Whatever the case, enjoy your new machine.

[miliuco]

@Ludox

 

Your configuration prevents AppleRTC from writing to any area of RTC memory (from 0 to 255 or from 0x00 to 0xFF in hexadecimal). And it has fixed the bug that prevented the system from booting. You can operate like this and most likely won't have any issues with this setting.

However, Dortania recommends knowing which addresses or range(s) of addresses AppleRTC shouldn't write to and blocking only those regions. The downside is that it's a cumbersome task, requiring many reboots to find the bad regions. 

 

https://dortania.github.io/OpenCore-Post-Install/misc/rtc.html#fixing-rtc-write-issues