Contribute
Register

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

The only other thing I can think of are the alternative SMC kexts you’re using. Have you tried the standard FakeSMC?

I tried the standard fakeSMC + "Copy-to-Library-Extensions" files and it wouldn't boot. Attached are the error screens. When I initially followed the guide and used the "Post Install Files" on my first build attempt last week I ran into the same dead end. Went back to my vanilla install backup and got it working again, but still no TB.
 

Attachments

  • IMG_2729.JPG
    IMG_2729.JPG
    3.5 MB · Views: 73
  • IMG_2728.JPG
    IMG_2728.JPG
    3.7 MB · Views: 63
I had this same problem with everything working except TB3. I traced the problem to an inactivated HS01. Once I re-did this (I posted the changes here), then the TB3 ports began working. To see if this is your problem, run IORegistryExplorer and look in the same location that I posted. If you see the same, then you can use the SSDT that I uploaded in that same post.

Followed your steps and no luck on TB yet. Do you see anything out of the ordinary in these photos?
 

Attachments

  • Screenshot 2019-04-07 13.53.20.png
    Screenshot 2019-04-07 13.53.20.png
    1.4 MB · Views: 60
  • Screenshot 2019-04-07 13.53.41.png
    Screenshot 2019-04-07 13.53.41.png
    868.8 KB · Views: 77
  • Screenshot 2019-04-07 14.25.07.png
    Screenshot 2019-04-07 14.25.07.png
    1 MB · Views: 91
CaseySJ,

Thanks again for keeping this thread up-to-date and so helpful!

Preface:
I made another Hackintosh this past weekend for my son. Unlike my recent build based on your work but using the Aorus Xtreme Waterforce, an i9 9900K and a Vega 64, I used the same mobo Designare Z390) and processor (i7 9700K) as you did.

My main deviation was trying to salvage an un-returnable XFX RX-590, which I only too late found does not work on a Hackintosh. Other RX-590s work, like one from PowerColor, but not the XFX model. After some research, I was able to flash the PowerColor BIOS via Windows 10, allowing the XFX RX-590 to work in Mojave (but it took even more effort to get Mojave graphic settings to work). Boot drive is an NVMe PCIe NAND, WD Black SN750 1TB (here); an Alphacool Eisbaer AIO CPU cooler was used (here), with Corsair 32GB RAM (here). Internal backup drive was a Samsung 860 EVO 1TB (here). PS was 750W (here), all inside a small, inexpensive case (here).

BTW, I started the process with a SuperDuper clone of my iMac18,3 system, converting it to a MacMini8,1. The config file is attached (less SNs). Mojave is 14.4.

Problem:
My main point of this, is that I got everything working, including WiFi/BT, except for TB3. I know that in my other system, the iMac18,3, TB3 works just fine. I finally got TB3 to work tonight, but I had to re-do your USB designations in the SSDT-UIAC-DESIGNARE-Z390-V5 file, and I needed to add a Clover Boot argument exclusion: uia_exclude=HS04;HS08;HS12;HS13;HS14;SS04;SS08;SS09;SS10;USR1;USR2 (some of these changes were simply for my personal convenience).

Solution:
The main change to get TB3 to work, was activating HS01 (and I think, HS02). Once I added HS01, not only did the UAD Apollo immediately connect via TB3, but I was then able to connect a USB-c drive to the other TB3 port (SSP2, show below). I attached the modified SSDT as ~v5-b, below.

Also attached are which USB ports I left active, and a few tests showing how the RX-590 works.

Rookie question, but do I still need to install a windows partition and "wake up" the TB ports on windows before MacOC will see them? I dont have a windows partition installed
 
Followed your steps and no luck on TB yet. Do you see anything out of the ordinary in these photos?

It's close but not exactly what I'm seeing on my set up.

If you collapse the XHC section, I see the attached image with HS01,02,03,05,07,09,10,11 and SS01,02,03,05,06,07 active. However, yours start at HS03, so I think HS01 and HS02 are not activated. Until I got those activated in the XHC section of IORegistryExplorer, TB3 and USB-c didn't work.

Attached are images of the KEXTs I've installed in the L/E folder and in the Clover's Other folder, as well as the *.efi files and the patched folder. (The -b suffix doesn't matter; I left to make certain there was no mistake, confusing it with CaseySJ's original file.) Are you certain that you're not still using the original version? If you are, this would explain why HS01 and HS02 are not showing up as active in the XHC section.
 

Attachments

  • Screen Shot 2019-04-07 at 3.05.37 PM.png
    Screen Shot 2019-04-07 at 3.05.37 PM.png
    90.1 KB · Views: 66
  • Screen Shot 2019-04-07 at 3.14.37 PM.png
    Screen Shot 2019-04-07 at 3.14.37 PM.png
    245 KB · Views: 65
  • Screen Shot 2019-04-07 at 3.14.12 PM.png
    Screen Shot 2019-04-07 at 3.14.12 PM.png
    104.5 KB · Views: 68
  • Screen Shot 2019-04-07 at 3.13.06 PM.png
    Screen Shot 2019-04-07 at 3.13.06 PM.png
    104.4 KB · Views: 69
  • Screen Shot 2019-04-07 at 3.19.04 PM.png
    Screen Shot 2019-04-07 at 3.19.04 PM.png
    162.1 KB · Views: 79
Last edited:
If you collapse the XHC section, I see the attached image with HS01,02,03,05,07,09,10,11 and SS01,02,03,05,06,07 active. However, yours start at HS03, so I think HS01 and HS02 are not activated. Until I got those activated in the XHC section of IORegistryExplorer, TB3 and USB-c didn't work.
My thunderbolt ports work fine with the original SSDT-UIAC-DESIGNARE-Z390-V5. Are HS01 and HS02 the USB-C part of the Thunderbolt ports? I have Thunderbolt USB support enabled in BIOS and if I search "XHC" in IORegistryExplorer I get this:
Bildschirmfoto 2019-04-08 um 00.25.35.png

So HS01 and HS02 are actually enabled without your tweaked SSDT (V5-b)?
I have no issues at all here, but I would like to understand the problem.
 
Rookie question, but do I still need to install a windows partition and "wake up" the TB ports on windows before MacOC will see them? I dont have a windows partition installed

On my son's version, using the Designare mobo, it is a straight MacOS, no Windows. On my version using the Waterforce mobo, which I wrote about earlier in this thread, I did make it dual boot.

But I did not partition the drive. Instead I use two separate drives (one Black SN750 1TB for Win10 and one Samsung 970 PRO 1TB for MacOS). Using two drives is much safer, and I specifically used two different brands (or would recommend different sizes of the same brand) to avoid confusion when formatting or copying files.

In Windows, there are Intel drivers that you can download and install which automatically activate the TB3 ports. The internal Intel WiFi/BT section is automatically used by Windows. However, I manually use Device Manager in Windows to turn off ("disable") the PCI board that we use for WiFi/BT on the Mac side; analogous to turning off the Intel WiFi/BT when we're running MacOS by turning off HS14 (along with using CaseySJ's SSDT, ~NO-CNVW.aml file).

Remember, only one OS is working at a time (Win or MacOS) and the one that is running has no idea what works or doesn't work when the opposite OS is running (as it is dormant to the one that's running), so there is no conflict.
 
Last edited:
My thunderbolt ports work fine with the original SSDT-UIAC-DESIGNARE-Z390-V5. Are HS01 and HS02 the USB-C part of the Thunderbolt ports? I have Thunderbolt USB support enabled in BIOS and if I search "XHC" in IORegistryExplorer I get this:
View attachment 398181

So HS01 and HS02 are actually enabled without your tweaked SSDT (V5-b)?
I have no issues at all here, but I would like to understand the problem.

Please follow CaseySJ's instructions. They seem to work for almost everyone. I only added my findings for HS01 and HS02 as I was stuck without TB3 function. My IORegistryExplorer values at at DSB2 seem different than those of CaseySJ (but similar to those found by maverik884). I don't know why this is; maybe different mobo versions?

I found this out by happenstance while testing for USB-c functionality on the TB3 ports (which I'd already observed were not working on my build). This led me to wonder if HS01 and HS02 were tied into the lack of TB3 functionality on my particular build, since I could see that they were associated with DSB2 and SSP1 and SSP2.

Anyhow, if you have TB3 working, don't bother trying to activate HS01 and HS02 and ignore what I've written.
 
Last edited:
USB-C is my next task to get working correctly. I think by not having HS01 and HS02 enabled is what is causing by problem. I have a Wacom Mobilestudio Pro that has a 4K touch & pen screen that does not work on the Mac side but works under windows. Wacom calls it Hybrid mode which basically turns the tablet computer into their Cintiq touch & pen screen when connected directly through a USB-C port. In Mojave the Wacom driver doesn't even see the tablet therefore no function other than a 4k screen... I believe it needs the USB connection for the tablet functions. When used on a 2013 MBP with TB1/miniDP, you connect the tablet IN to a Wacom Link (adapter box) and the OUT uses a miniDP to DP cable and a USB type A cable to connect to the MBP.
 
It's close but not exactly what I'm seeing on my set up.

If you collapse the XHC section, I see the attached image with HS01,02,03,05,07,09,10,11 and SS01,02,03,05,06,07 active. However, yours start at HS03, so I think HS01 and HS02 are not activated. Until I got those activated in the XHC section of IORegistryExplorer, TB3 and USB-c didn't work.

Attached are images of the KEXTs I've installed in the L/E folder and in the Clover's Other folder, as well as the *.efi files and the patched folder. (The -b suffix doesn't matter; I left to make certain there was no mistake, confusing it with CaseySJ's original file.) Are you certain that you're not still using the original version? If you are, this would explain why HS01 and HS02 are not showing up as active in the XHC section.

Using -b and still can't get HS01,02 and SSP1,2 to move over
 

Attachments

  • Screen Shot 2019-04-07 at 8.46.22 PM.png
    Screen Shot 2019-04-07 at 8.46.22 PM.png
    885.4 KB · Views: 76
  • Screen Shot 2019-04-07 at 8.46.00 PM.png
    Screen Shot 2019-04-07 at 8.46.00 PM.png
    446.4 KB · Views: 71
  • Screen Shot 2019-04-07 at 8.59.20 PM.png
    Screen Shot 2019-04-07 at 8.59.20 PM.png
    1 MB · Views: 74
  • Screen Shot 2019-04-07 at 8.59.15 PM.png
    Screen Shot 2019-04-07 at 8.59.15 PM.png
    1.2 MB · Views: 84
  • Screen Shot 2019-04-07 at 8.59.32 PM.png
    Screen Shot 2019-04-07 at 8.59.32 PM.png
    1 MB · Views: 77
Last edited:
what files if any should reside in the clovers\drivers64 folder? ... Trying to clean up a bit, it looks like a have a few duplicates Image of both....

View attachment 398146
The drivers64 folder can be deleted because this motherboard is exclusively UEFI. There's no harm in keeping the folder.
 
Back
Top