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

[CaseySJ]

Hello everyone and big thumbs up to CaseySJ for this wonderfull guide! My system is running properly without any big issues but i do have two small problems. Hope someone can help me a bit...

- JPEG Preview does not work. Tried using NoVPAjpeg.kext without any success.

- I think USB3 drives are not working properly. I followed all the guide steps with no success.

Im running Mojave .4 last version. My specs are: i7-9700K, 32GBRAM Crucial Ballistix Sport, Gygabite Z390 Gaming X, IGPU active, dGPU Nvidia GTX650 (for now.... Natively supported by OSX). Two 970 standard NVME drives.

Thank you in advance !

Hello @isoa,

Regarding JPEG Preview:

• Sysdef: Macmini8,1?
• Platform ID: ? (0x3E9B0007 or 0x3E980003 or ...)
• Device-ID: ? (0x3E92, 0x3E9B, 0x3E98, blank, or ...)
• Please run IORegistryExplorer and scroll down to IGPU in the large device tree on the left side. Below that do you see AppleIntelFrameBuffer... ?
  
  

Regarding USB3 drives:

• The custom USB SSDT (SSDT-UIAC-DESIGNARE-Z390-V5.aml) is not compatible with the Gigabyte Z390 Gaming X. You may create a custom USB SSDT by following this NEW GUIDE by @UtterDisbelief :
  • https://www.tonymacx86.com/threads/a-beginners-guide-to-creating-a-custom-usb-ssdt.272505/
  • Doing so is highly recommended.
• You also have the option of installing the following 3 USB port limit patches for 10.14.4. These patches will most likely break when 10.14.5 -- and every version thereafter -- is released.
  • https://www.tonymacx86.com/threads/mojave-10-14-4-port-limit-removal-patch.274052/
  • Creating a custom USB SSDT is still recommended. This patch is a temporary band-aid.

 

[CaseySJ]

HI @[B]CaseySJ[/B], I'm using RX580 and Z390 (UHD630) as well, after the Mojave 10.14.4 update, it seems the system can not recognize the UHD630 properly. I'm using Orinoco as FrameBuffer controller and properties key (AAPL,ig-platform-id) = 07009B3E, however can't get the full acceleration. But it worked well when it was Mojave 10.14.3. Any comments?

Hello @kasing,

Probably the best thing is to upload the config.plist from EFI partition of your Mojave SSD. You may remove serial numbers from SMBIOS.

 

[maverik884]

Hello @isoa,

Regarding JPEG Preview:

• Sysdef: Macmini8,1?
• Platform ID: ? (0x3E9B0007 or 0x3E980003 or ...)
• Device-ID: ? (0x3E92, 0x3E9B, 0x3E98, blank, or ...)
• Please run IORegistryExplorer and scroll down to IGPU in the large device tree on the left side. Below that do you see AppleIntelFrameBuffer... ?
  
  View attachment 398204

Regarding USB3 drives:

• The custom USB SSDT (SSDT-UIAC-DESIGNARE-Z390-V5.aml) is not compatible with the Gigabyte Z390 Gaming X. You may create a custom USB SSDT by following this NEW GUIDE by @UtterDisbelief :
  • https://www.tonymacx86.com/threads/a-beginners-guide-to-creating-a-custom-usb-ssdt.272505/
  • Doing so is highly recommended.
• You also have the option of installing the following 3 USB port limit patches for 10.14.4. These patches will most likely break when 10.14.5 -- and every version thereafter -- is released.
  • https://www.tonymacx86.com/threads/mojave-10-14-4-port-limit-removal-patch.274052/
  • Creating a custom USB SSDT is still recommended. This patch is a temporary band-aid.

Thanks Casey! Do you think following these steps will fix my lack of Thunderbolt problem too? I've still had no luck

 

[CaseySJ]

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

Fortunately there's no need to run Windows to "wake up" the Thunderbolt controller on this motherboard.

 

[CaseySJ]

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.

I noticed you have VirtualSMC-64 in your drivers64UEFI folder. Any particular reason or benefit that you're seeing from it?

 

[CaseySJ]

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.

Good question:

• The build guide has been updated with a modified SSDT-Z390-DESIGNARE-TB3HP-V4.aml that deletes HS01 and HS02. Turns out that these ports don't exist on the XHC5 controller.
• The two Thunderbolt USB-C ports are mapped as follows:
  • XHC5 --> SSP1. This is for USB 3.x devices plugged into the upper TB port 1.
  • XHC5 --> SSP2. This is for USB 3.x devices plugged into the lower TB port 2.
  • XHC --> HS08. This is for USB 2.0 devices plugged into the upper TB port 1.
  • XHC --> HS13. This is for USB 2.0 devices plugged into the lower TB port 2.
• However we have disabled HS08 and HS13 in order to make room for other USB ports. Because there is a limit of 15 ports -- and all 15 have already been designated -- we did not have room left over for HS08 and HS13.
  • Why would anyone want to connect slow USB 2.0 devices to state-of-the-art Thunderbolt 3 USB-C ports?

 

[CaseySJ]

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.

If the Wacom tablet is using USB 2 protocol over USB-C cable then it won't work when connected to one of the Thunderbolt 3 ports. Per post #3355 above, this is because we've disabled USB 2 devices from operating on the two TB3 ports by omitting HS08 and HS13 from the USB SSDT.

If you need to use the Wacom over USB-C and are willing to give up one of the other USB 2 ports, I can modify the USB SSDT for you. Just let me know which one (or two) USB 2 ports you're willing to give up. You can choose from any of the Blue, Red, Yellow, and Black ports. I would suggest choosing from the Blue, Red, and Yellow ports because USB 3 devices will still work on them (only USB 2 will not).

 

[CaseySJ]

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

Several comments:

• You should disable all 3 of the USB port limit patches in Kernel and Kext Patches by clicking the checkboxes under the Disabled column.
• Standard FakeSMC should work!
• SSP1 and SSP2 are permanently connected to XHC5.
• The new SSDT-Z390-DESIGNARE-TB3HP.V4.aml disables HS01 and HS02 from XHC5.
• Here's a snapshot of my IORegistry showing that Thunderbolt 3 is working fine without any HS01 or HS02 device in the system.

Perhaps you should compress and upload the CLOVER folder from your Mojave SSD (remove serial numbers from SMBIOS). On the Designare Z390 if the build guide is truly followed in a strict manner there should be no such problem with Thunderbolt activation. This might mean removing any extra SSDTs from CLOVER/ACPI/patched and using standard FakeSMC at least temporarily to see if that makes a difference.

 

[KevSea]

Do I need to use a different FakeSMC in order to see CPU Temps? System Monitor app I've used in the past isn't displaying CPU temp. Not really an issue for me though. Overclocked to 5Ghz just for fun but I'm currently air cooled so won't be running that way

 

[maverik884]

Do I need to use a different FakeSMC in order to see CPU Temps? System Monitor app I've used in the past isn't displaying CPU temp. Not really an issue for me though. Overclocked to 5Ghz just for fun but I'm currently air cooled so won't be running that way

Wow! Awesome score!! I'm trying to OC mine as well but the options on my motherboard are grayed out. I just updated to the latest BIOS as well. How did you OC yours?