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

[CaseySJ]

I’ll create a Sleep Troubleshooting Post that consolidates all the advice and feedback that’s contained in this thread.

Sleep related issues have been plaguing this thread for the past few weeks. Like a broken record, it’s also getting a bit tiresome.

So we’ll consolidate every piece of sleep related advice into a single post and link it from Post 1 and from the Catalina Mini-Guide. If that post cannot help resolve the problem, then it would be advisable to open a thread in the general Catalina Desktop Support forum so that a wider set of eyes can shine a light into probable cause.

 

[telepati]

@CaseySJ do you know how we can test NVRAM is working or not?

 

[P1LGRIM]

do you know how we can test NVRAM is working or not?

Native NVRAM Available?

If you don't know what NVRAM is, according to Wikipedia: Non-volatile random-access memory (NVRAM) is random-access memory that retains its information when power is turned off (non-volatile). This is in contrast to dynamic random-access memory (DRAM) and static random-access memory (SRAM)...

www.tonymacx86.com

 

[telepati]

Native NVRAM Available?

If you don't know what NVRAM is, according to Wikipedia: Non-volatile random-access memory (NVRAM) is random-access memory that retains its information when power is turned off (non-volatile). This is in contrast to dynamic random-access memory (DRAM) and static random-access memory (SRAM)...

www.tonymacx86.com

I read that thread. But I am using New CloverDaemon is still need the RC Script?

 

[CaseySJ]

*** Consolidated List of Sleep Aids for Gigabyte Z390 Designare ***​

This is a consolidated list of possible solutions for a variety of sleep/wake issues that may arise. We'll try to keep this post updated when new information becomes available. If you're facing sleep/wake issues, please proceed through the list of sleep aids below. You may perform one or more tasks at a time (probably best to perform only one at a time).

If your sleep/wake problem cannot be fixed despite every suggestion provided in this post, then please open a new thread in the Mojave Desktop Support or Catalina Desktop Support forum.

Clover Based Solutions:

• Add 300-Series RTC patch to config.plist --> ACPI section as follows:
  • Find* [HEX] = A00A9353 54415301
  • Replace* [HEX] = A00A910A FF0BFFFF
  • Comment = Fix 300-series RTC Bug
• If your MSR 0xE2 is locked (this is the default condition for this motherboard), ensure that either EmuVariableUefi.efi or EmuVariableUefi-64.efi is present in the CLOVER drivers folder, as follows:
  • Clover 5xxx: CLOVER/drivers/UEFI
  • Clover 4xxx: CLOVER/drivers64UEFI
• If your MSR 0xE2 is unlocked (this happens if you follow the Native NVRAM guide), ensure that neither EmuVariableUefi.efi nor EmuVariableUefi-64.efi is present in the CLOVER drivers folder.
• Check acidanthera Githubwebsite for latest versions of Lilu, WhateverGreen, and AppleALC.
  • Update to latest versions.
    • If these kexts are installed in both CLOVER/kexts/Other and /Library/Extensions, update them in both places.
    • If these kexts are installed only in CLOVER/kexts/Other, update them there only.
  • Whenever a file is updated, deleted, or added to /Library/Extensions, run Kext Utility to rebuild the kernel cache and repair permissions. This is mandatory.

General Solutions:

• System Preferences --> Energy Saver --> Wake for Network Access --> unchecked
  • In Catalina 10.15.4 and higher, Wake for Network Access works properly. Specifically, WiFi speed is no longer severely degraded after wake-from-sleep.
• System Preferences --> Energy Saver --> Enable Power Nap --> unchecked (try both checked and unchecked)
• Reduce memory speed to 2933MHz or 2666MHz. This can be done either by:
  • Disabling XMP Profile 1 in firmware (BIOS) or
  • Setting System Memory Multiplier to 26.66 or 29.33 in firmware (BIOS)
• Owners of certain AMD RX 5700 series GPUs may be at risk of sudden reboots.
  • Replace the RX 5700 with an older AMD GPU or a natively supported NVidia GPU.
  • If an alternative GPU is not available, use iGPU instead (fully remove the 5700-series GPU).
    • This requires changing Platform ID to 0x3E9B0007.
    • This can be done by following the first spoiler under Compilation of Patches for Various Motherboards located here.
      • You may apply either the Gigabyte Designare Z390 V1 or V2 patch. This will also enable the HDMI port on rear IO panel.
• Type the following in Terminal if your system falls asleep, but regularly wakes up by itself. Credit: @ncrispi based on this post: sudo pmset -a tcpkeepalive 0
• The F_USB header is currently set for Internal USB devices only. This means we should not connect the USB 2 cable from a computer case, because USB ports on the case are External. We can change the USB SSDT to define F_USB as External. Ask for help if this affects you.
• Note that certain Maintenance Wakes are perfectly normal. We can check for these in Terminal by typing: sudo pmset -g log | grep Maintenance
• Some Maintenance Wakes are due to scheduled events such as firing of notifications at 9am. We can check for these by typing: sudo pmset -g sched
• Some Maintenance Events may be due to Dark Wake (checking email, running Time Machine, etc.) without fully waking up the system. These can be stopped by disabling Power Nap in System Preferences --> Energy. One can also add the Boot Argument: darkwake=0
• During long periods of sleep, the system can switch automatically from sleep to hibernate to conserve more power. This is especially true in Europe due to energy regulations. To disable this feature, we can type: sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0
• We can also disable proximity wake, which is affected by nearby devices that are signed on to the same iCloud ID: sudo pmset -a proximitywake 0
• Instead of the RTC patch in Clover, we can copy the attached file 0-SSDT-RTC0.aml to CLOVER/ACPI/patched. A reboot is required to enable the file.
• To examine the real sleep/wake log, we use the following command: pmset -g log. Or better yet, we can save the log to a simple text file: pmset -g log > ~/Documents/Sleep-Log.txt. This will create a file in the Documents folder called Sleep-Log.txt, which can be examined by oneself or compressed and posted with a request for help.
• Some persistent wakes (or dark wakes) are due to Find My Mac. If you would like to prevent any kind of automatic wake, try disabling Find My Mac from System Preferences --> Internet Settings --> iCloud.

Process of Elimination:

• Some sleep/wake problems are due to certain USB devices attached to the system. Typically we find that smart power supplies or all-in-one liquid coolers that connect to the F_USB internal header can lead to sleep/wake problems.
• However, any misbehaving USB device can cause sleep/wake problems.
• Therefore we need to isolate the offending USB device or determine that USB devices are not the problem. We do this through a simple process of elimination:
  • Disconnect all internal and external USB devices (yes, including anything connected to F_USB internal USB 2 header on motherboard), but keep keyboard and mouse connected if keyboard and mouse are simple USB devices. Some USB mice are known to have problems (see Post #1).
  • Reboot the computer and check sleep/wake behavior. If sleep/wake still fails, then we can conclude that USB devices are not to blame, and we can STOP.
  • However, if sleep/wake works correctly, then it's likely that one of the USB devices we removed was causing the sleep/wake problem.
    • Now reconnect one USB device at a time and check sleep/wake.
    • If sleep/wake works, reconnect the next USB device and check sleep/wake.
    • If sleep/wake fails, you've just identified the offending USB device. STOP.

Untested Solution (applies only to systems without Native NVRAM enabled):

• Clover "rc" scripts contain one file in particular that may prevent the system from waking up periodically during longer periods of sleep.
• The name of this rc script is 70.disable_sleep_proxy_client.local.disabled, and it's placed in /etc/rc.boot.d folder.
• If your system is experiencing periodic wake from sleep (automatic wake from sleep), you may try copying this file (attached) into your /etc/rc.boot.d folder and rebooting.
• After copying the file, ensure it has "file-execute" permission by typing:
  

  cd /etc/rc.boot.d
  sudo chmod +x 70.disable_sleep_proxy_client.local.disabled

Suggestions Contributed by Users:

• Disabling all maintenance wake events during long periods of sleep by @hamzab.
• Try disabling AppleALC by adding -alcoff to your Boot Arguments.Reboot and check sleep/wake behavior. If no change, simply remove this boot flag. But if disabling AppleALC seems to fix sleep/wake problems, it will be necessary to use an external audio/sound device.
  • Contributed by @FormerUser-50757
• In some cases removing WhateverGreen.kext (WEG) from CLOVER/kexts/Other has been shown to fix certain sleep/wake/crash problems. If WEG is removed, it is necessary to rename GFX0 to IGPU (if IGPU is enabled in BIOS) and PEGP to GFX0. These renames can be accomplished either with an SSDT or simply via Clover or OpenCore ACPI renames. Certain video ports on the GPU will be unusable so please see the following posts for more details:
  • Post #1
  • Post #2

If you can think of other possible sleep/wake remedies, please let me know. For additional information, see this post.

 

[steve3d]

for how long after the computer wakes up is the time frozen?

like for few minutes to hours, I think the longest sleep would be two or three hours. and they are same,

And I have another z390 board, which is z390 aorus master, this board don't have this problem.

 

[P1LGRIM]

But I am using New CloverDaemon is still need the RC Script?

You asked how to test for NVRAM, the linked thread tells you how to do that.

 

[telepati]

You asked how to test for NVRAM, the linked thread tells you how to do that.

Ok. Here is the new question. is RcScript still need it while using CloverDaemonNew?

 

[P1LGRIM]

Ok. Here is the new question. is RcScript still need it while using CloverDaemonNew?

Not to do the test, no.

 

[iLikeHackintosh]

Recommended WiFi/BT Wireless Cards
https://www.newegg.com/Product/Product.aspx?Item=9SIADXZ7GS4848
https://www.newegg.com/fenvi-fv-hb1200-pci-express/p/0XM-00JK-00062?Description=fenvi%20WiFi&cm_re=fenvi_WiFi-_-9SIADXZ9CS9385-_-Product
The Fenvi FV-T919 and Fenvi FV-HB1200 provide both WiFi and Bluetooth, and work very well in a x1 slot with the SSDT-DESIGNARE-Z390-NO-CNVW.aml copied to the CLOVER/ACPI/patched folder on the EFI partition of the Mojave SSD. Instructions for copying the SSDT are provided in the spoiler labeled Final Steps in Post-Installation. (Gigabyte AORUS Xtreme owners must install these cards in one of the long slots.) The FV-T919 is the faster of the two cards and more expensive. The FV-HB1200 is slightly slower, but lower priced. Both will work out-of-the-box with no drivers needed

HI @CaseySJ

I have Fenvi FV-T919 installed also USB cable connected to the F_USB and Wifi works aout of the box. But I have issue with Blutooth. No Bluetooth device recognized on Catalina 10.15.2 (19C57). Do you have any suggestions?

BCM94360CS2 WiFi/BT module must be installed onto a PCIe x1 adapter card and inserted into an available PCIe x1 slot on motherboard. See Components section for exact specifications.

I have FV-T919 installed on PCIEX1_2 as graphics card covers PCIEX1_1.