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

[CaseySJ]

I’ve finally left Clover for OpenCore. @CaseySJ I did try your guide first but no luck. I got the Apple logo but no progress bar (even after an NVRAM reset) ...

But the following EFI did work out of the box (expect Bluetooth). His version seems more minimalist and less intrusive. Or am I missing some cool features with your EFI version?

GitHub - seven-of-eleven/designare-z390-opencore-efi: Gigabyte Designare z390 EFI - OpenCore

Gigabyte Designare z390 EFI - OpenCore. Contribute to seven-of-eleven/designare-z390-opencore-efi development by creating an account on GitHub.

github.com

Thanks

The OpenCore EFI in this guide has the following requirements:

• CFG-Lock must be disabled.
  • The best way is by installing BIOS F9g
  • See Quick Reference spoiler for download link
• Catalina is preferred.
• If using Mojave, we need to disable:
  • SSDT-USBW.aml
  • USBWakeFixup.kext

 

[CaseySJ]

Hi!

Anyone with this build is having issues with wakeup from sleep within Windows?

I'm new to windows, and only got it installed recently when I got myself a new RX580. My build works OK with Catalina with OpenCore, but at Windows, my computer won't wake up. My guess it's caused by some EFI settings?

As @roastable mentioned, it's best to isolate variables whenever troubleshooting. In this case:

• Press F12 at BIOS Splash Screen to boot Windows directly, hence bypassing OpenCore.
• Then check if Windows can sleep and wake.
• If system cannot wake, then the problem is due to something in Windows itself.

 

[phrfpeixoto]

Thanks @roastable and @CaseySJ. Yes, I was booting through OpenCore. I'll try the BIOS selector.
How can I remove the Windows entry from OpenCore?

 

[telicha]

pmset -g...

Well, I still had some random wakes tonight but at least the machine was only wake (at least report says so) for 17 seconds and went back to sleep a few times, I can live with that. I'll keep observing how it behaves and report.

Also, I noticed that in the WakeReason is listed:

2020-10-31 01:09:09 -0700 AppWakeReason AppWoke:com.apple.bluetoothd-blueavengers Reason:BlueAvengers: Toggle beacon state

I was wondering if someone has any idea how to disable this (though messing with the BlueAvengers might get the Hulk showing up very green and very angry at my doorstep ... I suppose I could try to turn off bluetooth and wifi before sleeping and turning it back on on wake, but automating this process can be tricky - not sure if it possible to distinguish between a "real" wake pressing a power button and a "fake" wake like the one above.

I have to add that except for this minor sleep nonsense going on, and the fact that every few hours my screen mysteriously goes dark for 3 seconds - my system is rock solid, with quite decent performance - Geekbench5 scores of 1161/6709 for CPU and 48848 Metal, and really want to thank CaseySJ and all the other people that helped me along the way to make that happen. It is my main workhorse now. I'm really happy I found and followed this thread. It helped me buying the Z390 Designare and all the other stuff mentioned here.

I probably will have to migrate to OpenCore when I decide to go for BigSur, but knowing Apple's history I will wait for BigSur 16.5 or something like that before migrating ... by then OpenCore itself might be a bit more straightforward and stable as well.

Thanks!

 

[brousseau6933]

Hi!

Anyone with this build is having issues with wakeup from sleep within Windows?

I'm new to windows, and only got it installed recently when I got myself a new RX580. My build works OK with Catalina with OpenCore, but at Windows, my computer won't wake up. My guess it's caused by some EFI settings?

Maybe because of OpenCore? I know that (sometimes), OC and Windows don’t play well together. However, maybe some experts (more than me...) will chime in.

**Sorry, already answered by Casey and another user...

 

[Lkevin30]

I want to flash my designare thunderbolt or I put the .bin file to execute it I put it in the flashrom folder

 

[gazzmanzx6]

I want to flash my designare thunderbolt or I put the .bin file to execute it I put it in the flashrom folder

Did you read the instructions?
The file path or name is clearly wrong.

 

[CaseySJ]

I want to flash my designare thunderbolt or I put the .bin file to execute it I put it in the flashrom folder

Please copy DESIGNARE-Z390-NVM33.bin into the ~/Desktop/Documents/Designare/flashrom-master directory and repeat the same command.

Alternatively, use the full pathname to the bin file, like this:

sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2048 -w /the/full/path/to/DESIGNARE-Z390-NVM33.bin

 

[jiffyslot]

Are you booting Windows using OpenCore? If so, I wouldn’t recommend it even though some users have it working fine. Just use your BIOS boot selector.

If you are using the BIOS, it could be a multitude of solely Windows-related issues and have nothing to do with hackintosh. My laptop doesn’t wake up from sleep after a fresh install last week.

FWIW, my (separate SSD) setups featuring Windows 10 (GPT/UEFI only, CSM off, VT-d enabled, all the latest updates) alongside the OS 10.14.6 (SIP enabled, no sleep) all work perfectly booting with OpenCore 0.6.2. My BIOS (F9i) settings are password-locked so that Windows 10 doesn't try to fix" anything when it boots. I no longer have to disconnect the Mojave boot drive when starting Windows. The fear is gone.

This is the most stable Pro Tools system I've ever owned, and I've owned several since Pro Tools v4. Here are some settings I'm using:

Boot = OpenCore 0.6.2 0.6.3 via the MacOS SSD EFI is the only boot option. After that, only Mojave –or Windows on its own SSD.
Base Clock = 4 GHz
BCLK = 100
Max Turbo Settings = 4.8 GHz on all cores.
Enhanced MultiCore = Enabled (I have a delidded Silicon Lottery 4.9 GHz i9 9900KS)
Vcore = Auto (BIOS F9i) Auto in F9i is working properly. Finally.
RAM speed=2666
XMP = Off
RTH = Off
Temperature Protection = Auto
CSM = Disabled
Sleep on every type of setup and system is completely disabled except for display sleep after ~45 minutes.
Bluetooth = Off
WiFi = Off
Thunderbolt = Unflashed. Hotswap/Powerswap works great.

I can attribute a lot of this to perseverance, respect for the thermal limits of the CPU ( erring on the side of a reduced clock speed), and the great underdog that is seldom discussed: A robust powersupply connected to a robust, voltage-regulating UPS.
Never cheap-out on a power supply. You'll thank me later...

 

[wiiwelshman]

We generally use ghost plugs with many (most?) Thunderbolt monitors if the Thunderbolt monitor is the only monitor connected to the system. As you discovered, the Thunderbolt monitor is blank during boot, but when a second monitor is present, then the Thunderbolt monitor may turn on. The ghost plug is designed to act as a phantom second monitor. But if you are already using a real second monitor, then the ghost plug will provide no added benefit.

I got the ghost plug. It doesn't seem to work that well. I only have one monitor. Are there any bios settings that I should make?