Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

For NVRAM, I've decided to enable RC Scripts in Clover, so I'll update that section of the Catalina Mini-Guide as well. I'll post a separate How-To for this shortly below.
I've installed Clover v5099 on 10.15.1 with RC scripts, but this doesn't fix NVRAM unfortunately (running OcQuirks and FwRuntimeServices). Might be unrelated to Clover, as NVRAM also doesn't work on OpenCore 0.5.3
 
I've installed Clover v5099 on 10.15.1 with RC scripts, but this doesn't fix NVRAM unfortunately (running OcQuirks and FwRuntimeServices). Might be unrelated to Clover, as NVRAM also doesn't work on OpenCore 0.5.3
Native NVRAM on Z390 motherboards does not work, but Emulated NVRAM in combination with EmuVariableUefi and RC Scripts should suffice for most purposes.
 
** Catalina Mini-Guide STEP 3 (Post-Installation) has been updated **
 
Native NVRAM on Z390 motherboards does not work, but Emulated NVRAM in combination with EmuVariableUefi and RC Scripts should suffice for most purposes.

One last thing to fix is NVRAM, since it seems that I don't have it (tested by setting a random "foo" variable that isn't there anymore after restart).

Emulated NVRAM with EmuVariableUefi and FwRuntimeServices does not work, variables (as mentioned by @arvids) don't survive a reboot.
 
Last edited:
Emulated NVRAM with FwRuntimeServices does not work, variables (as mentioned by @arvids) don't survive a reboot.
FYI: I'm unable to boot with EmuVariableUefi so I wasn't able to test that
May I ask what problem you're facing that requires the nvram command to function?
 
Here are the screen shots. Everything after Graphics is the same, I think. It doesn't show because I'm (sadly still) using a (pathetically low resolution) TV as my primary monitor.

It's not urgent or all that important, really... it's just annoying me since everything else works!
Yes it seems HWMonitorSMC2 v2.4.9 is not functioning correctly in Catalina (AMD GPU Info is not correct). Here's what I see:
Screen Shot 2019-12-10 at 3.10.23 AM.png
 
Thank you for the reply, but im a little confused with this. I've read through and walked through the directions on the first post about 4 times (or more) now, and I dont see anything about dropping files into the ACPI->patched folder. Where am I missing this step?

edit: I see where he is adding to that acpi folder but that is all in POST installation... i can't get the installer to start. Do these files need to be there PRE installation as well (if so, it's not mentioned in the guide).
Because you have two 32GB DIMMs, the problem might be related to memory. Suggestions:
  • Remove one DIMM and run the macOS installer.
  • If it still fails, do you have 8GB or 16GB DDR4 DIMMs?
    • If so, try those instead of 32GB modules.
  • Let us know if it still fails.
Also, support for 32GB DIMMs was first added in BIOS F6 so also check that you're on F6 or newer.

Screen Shot 2019-12-10 at 8.06.17 AM.png
 
Last edited:
Using prerelease WEG did not work when testing actual Netflix and Amazon Prime (not trailers, actual movies), and in some cases instantly froze my machine when attempting to use DRM.
 
May I ask what problem you're facing that requires the nvram command to function?
I'm a bit scared to continue with things like Messages, iCloud, FaceTime before nvram functions as it should. Furthermore, I need nvram to fully get OpenCore to work
 
I'm a bit scared to continue with things like Messages, iCloud, FaceTime before nvram functions as it should. Furthermore, I need nvram to fully get OpenCore to work
Messages, FaceTime, and iCloud are working with Clover + EmuVariableUefi. Because EmuVariableUefi is incompatible with OpenCore, I agree that NVRAM is an issue there.
 
Back
Top