Contribute
Register

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

I can confirm that using VirtualSMC and AptioMemoryFix combo still does NOT work on a (my) system with multiple PCI cards installed. The combination did work if I disabled my iGPU.

So, Casey's comment here still holds true (for me anyway)-

I'm not sure I want to go through the hassle of changing my SMBIOS from iMac19,1 to iMacPro1,1 just to get rid of OsxAptioFix2Drv-free2000

Same findings here. 19,1, multiple PCIe cards, can only boot with AptioMemoryFix by disabling IGPU in BIOS.
 
Hi,

I've followed your guide and it works quite nicely, but I have some minor issues described below:
  • My Das Ultimate keyboarddoes not consistently work upon boot - sometimes it is required to plug it back into the same port to get it to register. My tests:
    • Cold boot: Mouse and keyboard work fine
    • Reboot 1: Mouse and keyboard still work
    • Reboot 2: Mouse works but keyboard must be unplugged + plugged back in for it to work. Not that the Das Keyboard has a USB hub - if the mouse is plugged into the Das Keyboard USB port, the mouse will work but the Das keyboard itself does not
    • Reboot 3 into Windows: Mouse works but keyboard must be unplugged + plugged back in for it to work.
    • Reboot 4 into macOS: Mouse and keyboard work fine

  • I recently got a SD5200T Thunderbolt 3 Dockand am trying to use it, but the USB peripherals are not powered/activated until macOS or Windows boots (can't use them in BIOS/Clover), but if I reboot after booting into Windows they do work at boot time. My tests:
    • Mouse plugged into Keyboard (USB Dock), Keyboard plugged into Thunderbolt 3 Dock
    • Cold boot: Both mouse and keyboard work in macOS but not in BIOS/Clover
    • Reboot 1: Both mouse and keyboard work in macOS but not in BIOS/Clover
    • Reboot 2: Mouse works in macOS but not in BIOS/Clover, Keyboard must be plugged back in for it to work with macOS
    • Reboot 3 into Windows, moused moved into proper USB port: Only mouse works in BIOS/Clover, keyboard plugged back into same port to work in Windows
    • Reboot 4 into macOS: Keyboard and mouse working at boot (somehow booting after a Windows shutdown, the dock behaves correctly)
    • Reboot 5 into macOS: Keyboard works in macOS but not in BIOS/Clover (left mouse into USB port so it worked)

This is reproducible with your base setup as well after I tried an SSDT for my USB ports as well as when all SS ports are disabled. Initially I thought it was a problem with the port mappings but the fact that the keyboard behaves the same way (where it stops working when plugged into the dock and when plugged into the computer itself) suggests its something wrong on the Kext/Driver side? Since this is only reproducible with macOS and not on Windows I don't think it's an issue with the keyboard itself.
 
Just wanted to chime in with a major thanks to @CaseySJ and some TB3 compatibility.

I've gotten a Decklink 4K Extreme 12G working with a Sonnet eGFX Breakaway Box. Used it to capture a ton of VHS tapes and it works exactly the same as having it inside my system.
Glad to hear it!
  • Was it necessary to remove the Thunderbolt SSDT from the CLOVER folder or to give up Thunderbolt hot-plug capability?
  • Or does this particular combination work normally with this motherboard (hot-pluggable)?
 
Hello again. I set CPU Type to 1005 on the config.plist you kindly sent me on page 358 in this thread and rebooted.
This resulted in that the clover bootloader screen became white instead of black as it normally would be.
It looks to be a fancy brand new version of Clover.
I tried to boot MacOS from Mojave as usual, but this results in panic. So I probably did something wrong again.
I used the Clover Configurator I used in april when I built this machine, but it said "me no work, please update" So I did.
Is there anyway to fix this without starting from scratch?
Update: I´ve tried to boot once more from MacOS from Mojave after rebooting. Clover is not white anymore. It is Clover 4862 and booting is stuck just after apple logo.
Apologies for the late reply. Some questions/comments:
  • Specifying Type 0x1005 should not affect bootloader behavior.
  • What you're describing ("screen became white instead of black as it normally would be") are two different Clover themes.
    • When we install Clover with TonyMac's UniBeast and MultiBeast, the default theme is the familiar black with a green clover. It's the tonymacx86 theme.
    • When we subsequently download and run Clover Installer package from the internet, that installer defaults to the embedded theme, which is white with gray text.
  • In any case, because Clover is installed into the EFI partition, you have the option of mounting the EFI partition from an earlier bootable backup and dragging-and-dropping that folder into the EFI partition of the Mojave SSD.
    • This will undo the changes made.
  • If you do not have an earlier backup, please compare all files and folders in the CLOVER folder against those shown in the spoiler Final Steps in Post-Installation (build guide, Post #1).
  • If the problem persists, you may compress and upload the CLOVER folder (but remove serial numbers from SMBIOS).
 
Glad to hear it!
  • Was it necessary to remove the Thunderbolt SSDT from the CLOVER folder or to give up Thunderbolt hot-plug capability?
  • Or does this particular combination work normally with this motherboard (hot-pluggable)?
Nope! Currently using your Thunderbolt SSDT and hot-plug works just fine. Blackmagic software is able to use it after every replug/power down of the Breakaway Box.

I assume that there's nothing really fancy going on with the way that the Decklink interfaces over Thunderbolt that differentiates it from plugging directly into a PCIe slot on the motherboard.
 
Hi,

I've followed your guide and it works quite nicely, but I have some minor issues described below:
  • My Das Ultimate keyboarddoes not consistently work upon boot - sometimes it is required to plug it back into the same port to get it to register. My tests:
    • Cold boot: Mouse and keyboard work fine
    • Reboot 1: Mouse and keyboard still work
    • Reboot 2: Mouse works but keyboard must be unplugged + plugged back in for it to work. Not that the Das Keyboard has a USB hub - if the mouse is plugged into the Das Keyboard USB port, the mouse will work but the Das keyboard itself does not
    • Reboot 3 into Windows: Mouse works but keyboard must be unplugged + plugged back in for it to work.
    • Reboot 4 into macOS: Mouse and keyboard work fine

  • I recently got a SD5200T Thunderbolt 3 Dockand am trying to use it, but the USB peripherals are not powered/activated until macOS or Windows boots (can't use them in BIOS/Clover), but if I reboot after booting into Windows they do work at boot time. My tests:
    • Mouse plugged into Keyboard (USB Dock), Keyboard plugged into Thunderbolt 3 Dock
    • Cold boot: Both mouse and keyboard work in macOS but not in BIOS/Clover
    • Reboot 1: Both mouse and keyboard work in macOS but not in BIOS/Clover
    • Reboot 2: Mouse works in macOS but not in BIOS/Clover, Keyboard must be plugged back in for it to work with macOS
    • Reboot 3 into Windows, moused moved into proper USB port: Only mouse works in BIOS/Clover, keyboard plugged back into same port to work in Windows
    • Reboot 4 into macOS: Keyboard and mouse working at boot (somehow booting after a Windows shutdown, the dock behaves correctly)
    • Reboot 5 into macOS: Keyboard works in macOS but not in BIOS/Clover (left mouse into USB port so it worked)

This is reproducible with your base setup as well after I tried an SSDT for my USB ports as well as when all SS ports are disabled. Initially I thought it was a problem with the port mappings but the fact that the keyboard behaves the same way (where it stops working when plugged into the dock and when plugged into the computer itself) suggests its something wrong on the Kext/Driver side? Since this is only reproducible with macOS and not on Windows I don't think it's an issue with the keyboard itself.
First of all, that's a seriously impressive keyboard. Incidentally, I really love the Keychron K1 with real Mac keycaps. I have the original and the new K1 version 2, both in 10-key less form factors.

Second of all, kudos for the clear description and the various diagnostic steps you took to characterize the problem ahead of time.

Because this keyboard contains a USB 3 hub, are you connecting it to one of the blue, red, or yellow USB 3 ports via a proper USB 3 cable?

In Clover Configurator --> Kernel and Kext Patches, please check that all USB port limit patches are disabled or deleted.

In the CLOVER/ACPI/patched folder, check that the following files are present:
  • SSDT-UIAC-DESIGNARE-Z390-V7.aml
  • SSDT-EC.aml
And lastly, in the CLOVER/kexts/Other folder and the /Library/Extensions folder, please check that USBInjectAll.kext is present.

I suspect the problem may be something else, but we do need to confirm first that the basic installation is correct.
 
Last edited:
Nope! Currently using your Thunderbolt SSDT and hot-plug works just fine. Blackmagic software is able to use it after every replug/power down of the Breakaway Box.

I assume that there's nothing really fancy going on with the way that the Decklink interfaces over Thunderbolt that differentiates it from plugging directly into a PCIe slot on the motherboard.
Wonderful. Added to Thunderbolt 3 Experiences.
 
First of all, that's a seriously impressive keyboard. Incidentally, I really love the Keychron K1 with real Mac keycaps. I have the original and the new K1 version 2, both in 10-key less form factors.

Second of all, kudos for the clear description and the various diagnostic steps you took to characterize the problem ahead of time.

Because this keyboard contains a USB 3 hub, are you connecting it to one of the blue, red, or yellow USB 3 ports via a proper USB 3 cable?

In Clover Configurator --> Kernel and Kext Patches, please check that all USB port limit patches are disabled or deleted.

In the CLOVER/ACPI/patched folder, check that the following files are present:
  • SSDT-UIAC-DESIGNARE-Z390-V7.aml
  • SSDT-EC.aml
And lastly, in the CLOVER/kexts/Other folder and the /Library/Extensions folder, please check that USBInjectAll.kext is present.

I suspect the problem may be something else, but we do need to confirm first that the basic installation is correct.
Haha, thanks. My favorite part is the volume knob, but not having key labels does kind of suck when trying to type passwords in one handed. The Keychron does look pretty sweet, especially the newer one.

Yep, I've got it in HS04/SS04 and the Clover patches were already disabled.

I've got my own SSDT (but can reproduce with yours as well), just added the SSDT-EC.aml and the kext into CLOVER/kexts/Other (wasn't in there initially), but I'm still seeing the issue even with those changes.
 
Back
Top