- May 29, 2013
- Gigabyte Z390 M Gaming
- i9-9900K OC'd @ 5.1GHz
- Radeon VII
- Classic Mac
- , ,
- Mobile Phone
Yeah, the NVRAM is what really makes Z390 a pain. Lots of thing can cause inconsistent boot. I think that's just something that Z390 users have to live with because, as far as I know, the problem is with the AMI BIOSes and the hackintosh devs have pretty much given up trying find workarounds.THANK YOU!
I'm experimenting with Aptiofix drivers and with my Asus Z390 Prime A, and it seems that AptioMemoryFix is working just fine (Clover v. 5070); everything else is working fine too: sleep/wake, USB ports (with devices that survive correctly to sleep/wake cycles). I'm installed EMUVariableUEFI and related RC script on boot volume. The only thing is that:
Another thing I've noted is that your config has a lot of patches in ACPI->DSDT section and, also, much more Fixes enabled than mine's. But I don't know if those are related strictly to your motherboard or if they are more related to the "Z390" world.
- if I chance something in BIOS then I'm unable to boot (HALT on boot). Then I have to press F11 to clean up NVRAM and then everything is going fine again. Which is pretty disappointed, are you experiencing the same with your GA Z390?
- I've experienced a couple of random freezes in MacOS, both after the wakeup.. but I really don't know what they could be related to...
Here is my config attached (I just strip out the serial's related info). Please have a look. Thanks!
I also had problems with waking when using AptioMemoryFix. I have not had any wake problems with OsxAptioFix3Drv.
The ACPI DSDT patches I have should work for most Z390 users. Whatever patches aren't needed shouldn't cause any damage.
In your config.plist, you have ECH1 to EH01 and ECH2 to EH02. Are you sure you need those?