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

[datadl]

Just to confirm: Samsung EVO and EVO Pro NVMe drives are compatible and even quite popular, but EVO Plus appears to have a firmware issue that Samsung is supposedly working on.

Sorry for my mistake, you are totally right!

@CaseySJ => huge shoutout for this incredibly well made guide. It took me less than 1 hour to do it and I got a perfect running machine!!! You deserve gallons of good beer!

 

[CaseySJ]

I went through the guide again, but in the guide the boot install is suppose to disappear.... idk why mine is still there.... lol. Should I try a reinstall? Or is there a way to manually remove it?

When Clover initializes itself during boot, it scans all connected hard drives:

• NVMe
• Internal SATA
• External drives (eSATA, USB, Thunderbolt, etc.)

If any of these drives contains a valid EFI partition, it will appear as a boot option in the Clover Boot Menu. During macOS installation we have the following drives and partitions:

• USB install disk --> Clover will show "Boot macOS Install from Install MacOS Mojave"
• Mojave SSD --> Clover will show "Boot macOS Install from Mojave"

When installation is completed (including post-installation), we should remove the USB flash disk and reboot. In this case we should see:

• Mojave SSD --> "Boot macOS from Mojave" (the word "install" is gone)
• You will also see Mojave Recovery, PreBoot, and possibly FileVault boot options.

In your case:

• Power down the machine and unplug from the wall for 10 seconds to clear CMOS.
• Remove the USB install disk.
• Temporarily remove all other USB and Thunderbolt disks.
• Boot the machine and press F12 at the BIOS splash screen. The BIOS will display a list of bootable devices. Capture and upload a photo.
• Select your Mojave SSD from this BIOS boot menu.
• At the Clover Boot Menu, capture/upload a photo showing all of the available (bootable) disks.
• Ensure that you have BIOS version F4 or later, preferably F6.

 

[CaseySJ]

Sorry for my mistake, you are totally right!

@CaseySJ => huge shoutout for this incredibly well made guide. It took me less than 1 hour to do it and I got a perfect running machine!!! You deserve gallons of good beer!

Or one vintage magnum Lafite Rothschild.

 

[qmediaservices]

Because you're using HDMI, you can also test the HDMI cable by connecting it to the HDMI port on the rear IO panel of the motherboard. Are you using platform ID 0x3E9B0007 (non-headless)? And SMBIOS name Macmini8,1 or iMac18,3?

The on-board HDMI port can be enabled by following this part of the guide. However, this port supports maximum of 4K at 30Hz.

Im Back, the new HDMI cable is working wiht any more flickering, so It was the HDMI. I will keep using the XR580 as normal card, the fans still on and off, no problems alt all.
I will make this changes this weekend,
Two suggestions based on your IOReg:

1. Your iGPU is configured properly in headless mode, but with macOS 10.14.4 it is better to use Platform ID 0x3E980003 instead of 0x3E910003 (for headless operation).
2. I recommend updating the Thunderbolt SSDT in CLOVER/ACPI/patched folder with the new version in Post-Install Files.zip. The new file is SSDT-Z390-DESIGNARE-TB3HP-V4.aml.

Hey man thanks again for all your help, I will be around posting my updates.
LQ
Hye @CaseySJ you rock the community man.






Like Quote Reply

 

[CaseySJ]

Hey Casey,

Got my thunderbolt adaptor in and can confirm that the Blackmagic Multidock works great using the thunderbolt port. I have the Thunderbolt 2 version (looks like they updated it with proper USB-C) so I needed the converter cable.

The discs show up as internal though. Is this an issue?

FYI, just added the Blackmagic Multidock to Thunderbolt 3 Experiences. Thanks!

 

[JimSalabim]

Now a friend of mine has a problem with his BCM943602CS, too (also same motherboard, exact same configuration, only difference is that he has a Vega 56, not a Vega 64). His Hackintosh won’t stay in sleep mode, it will always wake up again immediately. When he disconnects the Bluetooth jack from the card, it’s working fine. Any ideas how he could fix this? Or is it likely that he will need a different card, too, as the BCM943602CS seems to cause lots of problems anyway?

We were able to fix it now: The internal USB header (HS11/HS12) showed up as USB 2.0 instead of Internal. So I changed the SSDT-UIAC-DESIGNARE-Z390-V5.aml file and replaced "Zero" with "0xFF" for HS11/HS12. Now it’s working!

 

[Stork]

FYI. MultiBeast v11.2.0 has been released. See > https://www.tonymacx86.com/threads/multibeast-11-2-0-update.275271/

 

[CaseySJ]

We were able to fix it now: The internal USB header (HS11/HS12) showed up as USB 2.0 instead of Internal. So I changed the SSDT-UIAC-DESIGNARE-Z390-V5.aml file and replaced "Zero" with "0xFF" for HS11/HS12. Now it’s working!

Interesting. Sounds like the definition of internal is built-in or permanently attached.

Let's say we connect our F_USB header to two USB 2.0 ports on the front panel of a PC case. In this case, we expect various USB devices to be plugged in and ejected at will.

• Hence connector type 0x00 (not internal; removable devices)

But if we connect permanent devices such as Bluetooth and CPU Cooler (devices that we will not be ejecting or hot-swapping), then the ports should be treated as Internal.

• Hence connector type 0xFF (internal; permanent devices)

For this system it makes sense to treat the F_USB as internal and therefore not suitable for outside USB ports. (USB 3.1 Gen 1 and USB 3.1 Gen 2 headers on this motherboard are configured as external because they're typically connected to ports on the PC case.)

I'll update the guide with V6 of the SSDT later this evening.

Thank you for identifying this problem.

 

[JimSalabim]

Interesting. Sounds like the definition of internal is built-in or permanently attached.

Let's say we connect our F_USB header to two USB 2.0 ports on the front panel of a PC case. In this case, we expect various USB devices to be plugged in and ejected at will.

• Hence connector type 0x00 (not internal; removable devices)

But if we connect permanent devices such as Bluetooth and CPU Cooler (devices that we will not be ejecting or hot-swapping), then the ports should be treated as Internal.

• Hence connector type 0xFF (internal; permanent devices)

For this system it makes sense to treat the F_USB as internal and therefore not suitable for outside USB ports. (USB 3.1 Gen 1 and USB 3.1 Gen 2 headers on this motherboard are configured as external because they're typically connected to ports on the PC case.)

I'll update the guide with V6 of the SSDT later this evening.

Thank you for identifying this problem.

Nice!
On my machine the F_USB was recognized as internal without this change. So what does it mean then if there‘s „Zero“ set instead of „0x00“ or „0xFF“? Does it mean unspecified?

 

[MACAK]

@CaseySJ "Buy a new high quality USB 3.0 flash disk from a reputable manufacturer." was one the best instruction sentences on your Golden Build. I bought a new Samsung BAR Plus 32GB - 200MB/s USB 3.1 Flash Drive Champagne Silver and I shocked how fast it builded the installer. Thanks so much for all the good advice.