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

[DJ4MC]

I've just verified *.jpg Quick Look:

• iMac18,3 / iMac18,2: doesn't work
• imacPro1,1: works

but in comparison to macMini8,1 sleep/wake doesn't work anymore. For all three models I get the same results (see S4.png and S5.png)

Does it possibly depend on the PCIe slot used for the RX 580?

What are your BIOS Settings for Initial Display Output?

Initial Display Output
Specifies the first initiation of the monitor display from the installed PCI Express graphics card or the onboard
graphics.
IGFX Sets the onboard graphics as the first display.
PCIe 1 Slot Sets the graphics card on the PCIEX16 slot as the first display. (Default)
PCIe 2 Slot Sets the graphics card on the PCIEX8 slot as the first display.
PCIe 3 Slot Sets the graphics card on the PCIEX4 slot as the first display.

 

[ripe_md]

I've just tried SMBIOS macMini8,1 with the following values in the config.plist:

• Devices: IntelGFX = 0x0
• Devices: Devices* = PCIRoot(0x0)/Pci(0x2,0x0)
  • Properties
    • Key = framebuffer-patch-mode , Value = 01000000 , Type = Data
    • Key = AAPL,ig-platform-id , Value = 0300923E , Type = Data
    • Key = device-id , Value = 9B3E0000 , Type = Data
• Graphics: FB Name = Orinoco
• Graphics: ig-platform-id = 0x (empty / no value)
• Graphics: Inject Intel = false
• Graphics: Inject ATI = false

Result:

• FCPX works
• JPG Quick Look works
• Sleep/wake works

See the attachments for Geekbench, VideoProc and System Report values.

I have no idea why in my case it works with macMini8,1 and others need to use for example iMac18,3.

 

[CaseySJ]

thanks for replay , I checked video proc, it shows that I have H264 and HEVC enabled, but in Graphic it shows the Intel UHD Graphic 630

Having ruled out most of the obvious causes, maybe it's time to look at the more obscure ones:

• If you disconnect the PCI power cable from the nVidia GTX1080 and restart the machine, does it make any difference to video playback in VLC?
• If you have iStat Menus, you could check GPU and CPU load during video playback. You can see which GPU is carrying the load and how much the load is distributed between the CPU and the GPU. Can "Activity Monitor" do this? (I'm not in front of a Mac at the moment, so cannot check.)

 

[xanderevo]

I have Orinoco and iMacPro 1,1 here also everything works, I don't know how to inject Iriri or Kamarang for the Vega64 just to "test" because they aren't in clover, and I am not sure on how to do it / if I will have benefits from it / don't want to mess with my system.

 

[tsamy]

Having ruled out most of the obvious causes, maybe it's time to look at the more obscure ones:

• If you disconnect the PCI power cable from the nVidia GTX1080 and restart the machine, does it make any difference to video playback in VLC?
• If you have iStat Menus, you could check GPU and CPU load during video playback. You can see which GPU is carrying the load and how much the load is distributed between the CPU and the GPU. Can "Activity Monitor" do this? (I'm not in front of a Mac at the moment, so cannot check.)

Thank you for your great support, I’m using RX 580 with my Z390 motherboard. I will add GTX 1080 Ti to my build when I make sure every thing working fine. I changed my config to iMacPro 1.1, and I feel the video player getting better by 90% still not 100%. I also change my FB-Patcher value, and I feel it improve the build. I tried different media player all the same.

 

[KaseyRamge]

Hi, CaseySJ. Your SSDT-DTPG.aml file are made from @kgp. he doesn't fix anything just renames Author name. How about comparison what's different as it?

 

[CaseySJ]

Hi, @CaseySJ. Your SSDT-DTPG.aml file are made from @kgp. he doesn't fix anything just renames Author name. How about comparison what's different as it?

In the build guide (Post #1) user KGP is clearly acknowledged as the creator of the SSDT. His SSDT was modified to work on this motherboard. This was done by modifying the IOReg device paths and changing slot number information.

 

[AlexD]

To anyone who's still interested in my story with Apple Thunderbolt Display and Gigabyte Z390 Designare.
Today I got a response from Gigabyte's support team. And it was absolutely shocking to me.

They basically said, that, since JHL7540 is Thunderbolt 3 controller, it means it is not validated to work with any Thunderbolt 1/2 devices through an adapters. Also, no Apple products can be used with it.

In my mind, this is absolutely ridiculous response and complete lie from their side. The same monitor and the same adapter worked perfectly through the previous generations of TB chips and motherboard chipsets. And now it suddenly stopped to work at all because ..., because it is "Thunderbolt 3"? Seriously? Okay.

I strongly believe that JHL7540 as modern Titan Ridge Thunderbolt 3 controller should be fully able to communicate with previous generation of Thunderbolt devices. It is rooted in DNA of Thunderbolt technology.

Can't believe Gigabyte ruined Thunderbolt generations compatibility and are trying to say now that it is all due to the Intel's Thunderbolt chip design, so that's not their fault.

Very disappointing news. Just wanted to share with you guys, how Intel's great Thunderbolt technology is being implemented by vendors.

 

[CaseySJ]

I strongly believe that JHL7540 as modern Titan Ridge Thunderbolt 3 controller should be fully able to communicate with previous generation of Thunderbolt devices. It is rooted in DNA of Thunderbolt technology.

Agreed. Here's a proven case of using Universal Audio Octo Satellite with a Thunderbolt 3 to Thunderbolt 2 adapter on this very motherboard. So maybe the adapter is not at fault, but Apple's Thunderbolt Display is at fault??

https://www.tonymacx86.com/threads/...390-with-i7-9700k.266065/page-25#post-1876949

 

[AlexD]

Agreed. Here's a proven case of using Universal Audio Octo Satellite with a Thunderbolt 3 to Thunderbolt 2 adapter on this very motherboard. So maybe the adapter is not at fault, but Apple's Thunderbolt Display is at fault??

https://www.tonymacx86.com/threads/...390-with-i7-9700k.266065/page-25#post-1876949

Honestly, I'm not sure how Apple Thunderbolt Display can be at fault when it is just simple plain TB2 Hub device with display, sound, camera and internal usb/firewire/ethernet ports. So we may even consider it as TB dock if we want. I can't believe that might be too hard for Titan Ridge to handle it.

Gigabyte advertises up to 12 Thunderbolt devices, 4k/8k, and enormous 40gbps speeds and all that new whistles, but they can't make simple legacy devices (1440p) to work fine with their hardware. That's funny at least.

And if it worked fine with previous generations of TB chips and motherboard chipsets – that means that something is really wrong in Gigabyte Z390 Designare BIOS / TB firmware. They definitely ruined and/or forgot about Thunderbolt displays at all. Honestly, there are not so many of them in the world to not to care about them. And Apple Thunderbolt Displays still widely used in creative industry. I personally really love it.

But again, as I already stated in my previous posts, there's a difference between thunderbolt displays and, for example, audio interfaces. I think you can agree with me, that Thunderbolt display will require significantly more bandwidth and pci resources than audio device.

Maybe Gigabyte's engineers included support for DisplayPort via USB-C but for some reason didn't "tell" TB controller how to properly switch and recognize native Thunderbolt displays (requires native TB out not just DP stream via TB/USB-C port).