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

[CaseySJ]

Thanks Casey. I first did the points you mentioned at the bottom of your post [i.e a), b), c) and then d)] and can confirm that if I turn off iCloud completely, sleep works fine, however as soon as I sign back in, the Coreduet.Sync command comes back.

I also followed your above steps (re: Reminders) with the energy saver schedule trick, however alas, my sleep problems still remain.

Any other ideas before I try another reinstall?

Thanks!

And my powerd problem has resurfaced on Z490 Vision D. If the same is true on my 2020 MacBook Pro, I'll report the issue to Apple.

Do you have a real Mac? If so, does it exhibit the coreduet.sync problem? Apple's support forums contain several such complaints.

Here's another suggestion:

• From System Preferences --> Internet Accounts --> iCloud, disable each of the checkboxes one by one (not just iCloud Drive) and test sleep/wake. Perhaps one of those items in particular is causing the problem.

 

[hamzab]

And my powerd problem has resurfaced on Z490 Vision D. If the same is true on my 2020 MacBook Pro, I'll report the issue to Apple.

Do you have a real Mac? If so, does it exhibit the coreduet.sync problem? Apple's support forums contain several such complaints.

Here's another suggestion:

• From System Preferences --> Internet Accounts --> iCloud, disable each of the checkboxes one by one (not just iCloud Drive) and test sleep/wake. Perhaps one of those items in particular is causing the problem.

Thanks, I've got a few real Macs so will check if they have the same issue. Will also uncheck individual things within iCloud settings and report back.

Thanks!

 

[ncrispi]

Thanks, I've got a few real Macs so will check if they have the same issue. Will also uncheck individual things within iCloud settings and report back.

Thanks!

try turning TCPKEEPALIVE to 0 in terminal... sounds like part of the issue I was having prior to me turning that setting off

 

[hamzab]

And my powerd problem has resurfaced on Z490 Vision D. If the same is true on my 2020 MacBook Pro, I'll report the issue to Apple.

Do you have a real Mac? If so, does it exhibit the coreduet.sync problem? Apple's support forums contain several such complaints.

Here's another suggestion:

• From System Preferences --> Internet Accounts --> iCloud, disable each of the checkboxes one by one (not just iCloud Drive) and test sleep/wake. Perhaps one of those items in particular is causing the problem.

Hey Casey, quick update.

The CoreDuet issue always lasts 30/40 minutes after a fresh reboot, at which point it'll go to sleep just fine. Even after that (as in if I wake it and leave it), it'll go to sleep within 3 minutes of waking it no matter how many times I trigger this flow. This leads me to believe there's a 'timeout' somewhere that we could perhaps one day change.

Changing individual iCloud settings doesn't help, I think it's to do with the overall iCloud service. My real Macs don't have this issue, however they are MacBooks so won't always be apparent until I actually run the pmset -g log command. I also thought it may be related to my Printer/Bonjour service, but I have a fresh install right now and no printers connected/drivers installed.

 

[hyperx136]

Hey CaseySJ,

Is your 5700 XT is still working properly with OC 5.0.9 after 10.15.6 update? Mine has been giving black screen at boot since 10.15.5 after runing 10.15.3 and OC 5.0.7 for months with no problem. Only way to get my 5700 XT to boot right now on 10.15.6 and OC 0.5.9 is to take off WEG kext. I'm using your OC folder.

 

[Hackintoshron]

And here it is! Clover Configurator 5.15.0.0 with the settings needed for Z390 Designare.
View attachment 481032

For clarity, are all of those blue check boxes to be checked as well? When I open my config.plist, none of them are checked. By the way, I've been running Clover 5120 for three days without incident.

 

[CaseySJ]

Hey CaseySJ,

Is your 5700 XT is still working properly with OC 5.0.9 after 10.15.6 update? Mine has been giving black screen at boot since 10.15.5 after runing 10.15.3 and OC 5.0.7 for months with no problem. Only way to get my 5700 XT to boot right now on 10.15.6 and OC 0.5.9 is to take off WEG kext. I'm using your OC folder.

I'm using Clover on that system, but I can switch over to OC 0.5.9 later this evening.

 

[CaseySJ]

For clarity, are all of those blue check boxes to be checked as well? When I open my config.plist, none of them are checked. By the way, I've been running Clover 5120 for three days without incident.

We have to check those boxes ourselves if we use OcQuirks/OpenRuntime that ships with Clover v5120. Because you're using OcQuirks/OpenRuntime from this build guide, those boxes are not needed.

Looks like Clover 5120 has been re-released so I'll have more to say on this soon.

 

[CaseySJ]

Hey CaseySJ,

Is your 5700 XT is still working properly with OC 5.0.9 after 10.15.6 update? Mine has been giving black screen at boot since 10.15.5 after runing 10.15.3 and OC 5.0.7 for months with no problem. Only way to get my 5700 XT to boot right now on 10.15.6 and OC 0.5.9 is to take off WEG kext. I'm using your OC folder.

I'm using Clover on that system, but I can switch over to OC 0.5.9 later this evening.

Decided not to wait til evening...

This is being posted from the Designare Z390 with PowerColor Red Dragon RX 5700 XT booted with OpenCore 0.5.9 taken straight from the OpenCore mini-guide with serial numbers copied from Clover config.plist.

It's completely solid. No issues.

Using WhateverGreen 1.4.0 (same version that is included in the ZIP at the bottom of the mini-guide).

 

[CaseySJ]

*** Micro Guide for Installing Clover r5120 ***
Please do not quote this guide in its entirely. Post a link instead.

NOTICE 22-Jul-2020: OcQuirks/OpenRuntime that accompany Clover r5120 do not work on this board using the quirks that have worked for us in the past. This procedure has been modified.​

Background:
Clover r5120 integrates OpenCore's OpenRuntime memory driver for the first time! We have used OpenRuntime and its predecessor, FwRuntimeServices, for over a year -- this is what allowed us to discard OsxAptioFix2Drv-free2000 in favor of a reliable, modern memory driver. But we were installing two pieces of software separately: We were installing Clover first and then downloading and installing OcQuirks, which provides the bridge between Clover and OpenRuntime.

Clover r5120:
Clover r5120 can be downloaded by selecting the file highlighted below (Clover_r5120.pkg) from this link:

Installation:
This procedure is only for upgrading from earlier version of Clover 5xxx to Clover 5120+.

• Make a full bootable backup. No excuses.
• Launch the pkg file after it's been downloaded. If a security warning appears, go to System Preferences --> Security & Privacy --> General and allow macOS to launch the app from the bottom of that window.
• Choose your target disk (macOS internal SSD).
• IMPORTANT: Then select Customize...
  
• Then make sure that the first 2 options are selected:
  • Clover for UEFI booting only
  • Install Clover in the ESP (ESP = EFI System Partition)
• 
• Now expand the UEFI Drivers section and disable everything.
  
• Click the Install button to proceed with the installation.
• Now download Clover Configurator 5.15.0.0 or newer. This is helpful because it adds a new OcQuirks section that we may use in the future.