Contribute
Register

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

I followed his guide precisely. I'm on Mo


@CaseySJ & @ZHENGQINLONG, thanks for your answers. I'm using the TB2 version with an Apple TB2/TB3 dongle. Apollo Twin Mk2.
Even if I have the Apollo unplugged the UAD software gives me the driver error. Usually it should say something like "no device connected" i think... I'll go through the whole installation process one by one again and see if I messed up something...
I'll see if I can test other ThunderBolt devices to make sure that is running correctly or if it's the UAD software.

I use latest UAD drivers with my Apollo X6. I have no problems (in fact, I use the Apollo as my only speaker source, driving my desk monitors: no Apollo, no sound). It will auto boot up just fine if Apollo already turned on. If Apollo is off and I turn it on, the drivers recognize it and load within 10 seconds or so.

Once in a while, they won't connect. Then, I simply un-plug and re-plug one or both of the TB cables in the Plugable Thunderbolt 3 Docking Station (here) and the drivers auto-load and all is working again in just a few seconds. (I see this same behavior when I dual boot into Win 10 with the same hardware, so maybe not so much an OS issue.)
 
That's a good idea. Also check that "SSDT-DTPG.aml" is copied to CLOVER/ACPI/patched folder. The Thunderbolt SSDT will not function properly without it.
I use latest UAD drivers with my Apollo X6. I have no problems (in fact, I use the Apollo as my only speaker source, driving my desk monitors: no Apollo, no sound). It will auto boot up just fine if Apollo already turned on. If Apollo is off and I turn it on, the drivers recognize it and load within 10 seconds or so.

Once in a while, they won't connect. Then, I simply un-plug and re-plug one or both of the TB cables in the Plugable Thunderbolt 3 Docking Station (here) and the drivers auto-load and all is working again in just a few seconds. (I see this same behavior when I dual boot into Win 10 with the same hardware, so maybe not so much an OS issue.)

Thanks a lot for your reply. I’ll mess around with everything more tonight. I just realized i have a silver face apollo twin, so thunderbolt 1, i think that could be it
 
Absolutely agree. I just needed SATA card for old dudes like DVD ROM and for a couple of old HDDs which does not make sense for them to go to Thuderbolt bay
For this a x1 PCIe 2.0 card with 4 SATA ports will work well.
 
Double checked all you mentioned above but still have that phantom display...

I'm running a PowerColor VGA - AXRX 580 8GBD5-3DH/OC connected to an LG UltraFine 5k which is connected to the motherboard TB out...
Here's something to try:
  • The internal UHD 630 can drive the LG UltraFine 5K as well.
  • If you're using a headless platform ID (0x3E920003 or 0x3E910003), try switching back to non-headless: 0x3E9B0007.
  • Disconnect the cable from RX 580 to Motherboard DP-In Port.
  • Keep the Thunderbolt cable connected between the motherboard and the LG UltraFine.
  • No need to change SMBIOS (I hope!).
  • Reboot.
Then check:
  • Do you get a 5K or 4K display on the LG UltraFine?
  • Do you get the same ghost desktop?
 
Here's something to try:
  • The internal UHD 630 can drive the LG UltraFine 5K as well.
  • If you're using a headless platform ID (0x3E920003 or 0x3E910003), try switching back to non-headless: 0x3E9B0007.
  • Disconnect the cable from RX 580 to Motherboard DP-In Port.
  • Keep the Thunderbolt cable connected between the motherboard and the LG UltraFine.
  • No need to change SMBIOS (I hope!).
  • Reboot.
Then check:
  • Do you get a 5K or 4K display on the LG UltraFine?
  • Do you get the same ghost desktop?
Where does the platform ID go? In the SMBIOS section?
 

Attachments

  • Screen Shot 2019-03-22 at 3.30.59 PM.png
    Screen Shot 2019-03-22 at 3.30.59 PM.png
    778.1 KB · Views: 58
Where does the platform ID go? In the SMBIOS section?
The platform ID is specified in Devices --> Properties. The procedure is listed here. If you're not comfortable editing the config.plist manually, simply upload your file (you may remove serial numbers from SMBIOS) and I'll modify it.

Also note that your SMBIOS currently says "Macmini7,1" instead of "Macmini8,1". This should actually be the first thing to fix.
 
The platform ID is specified in Devices --> Properties. The procedure is listed here. If you're not comfortable editing the config.plist manually, simply upload your file (you may remove serial numbers from SMBIOS) and I'll modify it.

Also note that your SMBIOS currently says "Macmini7,1" instead of "Macmini8,1". This should actually be the first thing to fix.
I had changed to "Macmini8,1" earlier this week and couldn't get the App Store & Message's working. Being pressed for time I fell back to my "Macmini7,1" configuration... Not sure if there was something I had done incorrectly in my SMBIOS settings... Seems to make sense that if the Product Name changes that for all intents and purposes this would be a new Mac from that perspective. Maybe I re-used my prior serial number and that was the problem.

Here is my config.plist.

Thanks Casey!!!
 
Last edited:
I had changed to "Macmini8,1" earlier this week and couldn't get the App Store & Message's working. Being pressed for time I fell back to my "Macmini7,1" configuration... Not sure if there was something I had done incorrectly in my SMBIOS settings... Seems to make sense that if the Product Name changes that for all intents and purposes this would be a new Mac from that perspective. Maybe I re-used my prior serial number and that was the problem.

Here is my config.plist.

Thanks Casey!!!
Please try the attached file. The SMBIOS name is still Macmini7,1 however. Therefore:
  • Try this version anyway (restore your serial numbers in SMBIOS) and check:
    • RX580 --> DP-In followed by TB3 --> LG 5K
      • Still see the ghost desktop?
    • Disconnect RX580 --> DP-In, (reboot optional), check if TB3 --> LG 5K displays a signal.
      • Still see the ghost desktop?
  • Change SMBIOS name to Macmini8,1 and repeat steps above.
    • When you do this, Clover Configurator will generate new serial numbers. In fact, new numbers will be populated into all of the SMBIOS boxes. So it's advisable to backup the original config.plist and then copy-and-paste the old Serial Number and Board Serial Number into the new file (also paste the original Board Serial Number into RtVariables --> MLB).
 

Attachments

  • tom_config-v2.plist
    9.3 KB · Views: 122
Casey, thanks so much for making my introduction into the world of hackintosh this smooth...

Thanks to this whole forum on which I've spent countless hours before committing :)

The one and only thing I just can't figure out is my Apollo Twin... The problem i'm having (i think) has nothing to do with the apollo itself, but moreso with the UAD software... I get a "Driver Not Installed Correctly" error when trying to open the UAD Software. What I've found is that after installing the software and a restart you should be able to grant permission in Security & Privacy to the UAD software. That should solve the problem... unfortunately that granting of permission never shows up for me. UAD says reinstalling and rebooting should solve the issue which it doesn't for me.

Did anybody get their UAD software running on Mojave 10.14.3?


@soundsgerman, I think it was you that PM'd me on ****** but I figured I'd copy over my response.

Do you see "UA Mixer Engine" in System Preferences > Security & Privacy > Accessibility?

394551


If not maybe try clicking the little lock on the lower left, enter your password, press "+" and add "UA Mixer Engine".

"UA Mixer Engine" should be located in HD > Library > Application Support > Universal Audio > Apollo

Hope that helps!

Edit: Just caught up with the thread and it seems like you're using TB1 so that could also be another issue even if the software permissions are properly granted.
 
Last edited:
Back
Top