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

[CaseySJ]

Hi, it's earlier in this thread but I am not able to get Thunderbolt working through the monitor or directly through the port with a TB3 device. Do you have a working TB3 config with the Designare? Thinking I might fresh install and try again...

Please check the following:

• BIOS —> Thunderbolt Security —> No Security
• BIOS —> GPIO3 Force Pwr —> Yes or Enabled
• CLOVER/ACPI/patched folder —> Do you have DTPG.aml?

If Thunderbolt still fails, please run IORegistryExplorer and select File —> Save As... and upload the saved file. Reinstalling the O/S will not fix Thunderbolt because the problem is most likely somewhere in BIOS or the EFI folder.

 

[CaseySJ]

Preaching to the choir...

 

[CaseySJ]

Sometimes we need to press two keys on keyboard.

First keypress —> wakes the PC hardware
Second keypress —> wakes the monitor

Setting “darkwake=0” in Boot Arguments can reduce it to a single keypress.

If wake does not work despite this, please check whether EmuVariableUefi-64 is installed in CLOVER/drivers64Uefi or CLOVER/drivers/UEFI.

 

[WilliamHarp]

In preparation for a dual boot build I wanted to see if there was any disadvantage to installing Windows first? I'd like to avoid unplugging all of my drives after I get macOS working just to install Windows.

I intend to put both operating systems on NVMe's (separate of course) and after reading through this thread it seems like it *works* just a has a few quirks with windows being a bully to the macOS EFI when it comes to updating?

Is there any specific method of installing windows that makes it more copasetic in a macOS environment?

Thanks guys!

 

[CaseySJ]

In preparation for a dual boot build I wanted to see if there was any disadvantage to installing windows first? I'd like to avoid unplugging all of my drives after I get macOS working just to install windows.

I intend to put both operating systems on NVMe's (separate of course) and after reading through this thread it seems like it *works* just a has a few quirks with windows being a bully to the macOS EFI when it comes to updating?

Is there any specific method of installing windows that makes it more copasetic in a macOS environment?

Thanks guys!

It’s a good idea to install Windows first (in the absence of any other OS) and also to install the Windows NVMe into the upper M2M slot. MacOS installer is better designed and affects only the drive it’s assigned to. MacOS can be installed alongside an existing Windows drive, but not vice-versa.

 

[Stork]

In preparation for a dual boot build I wanted to see if there was any disadvantage to installing Windows first? I'd like to avoid unplugging all of my drives after I get macOS working just to install Windows.

I intend to put both operating systems on NVMe's (separate of course) and after reading through this thread it seems like it *works* just a has a few quirks with windows being a bully to the macOS EFI when it comes to updating?

Is there any specific method of installing windows that makes it more copasetic in a macOS environment?

Thanks guys!

See the sticky threads in the Multi Boot forum section.

Multi Booting

www.tonymacx86.com

 

[JayShay]

Please check the following:

• BIOS —> Thunderbolt Security —> No Security
• BIOS —> GPIO3 Force Pwr —> Yes or Enabled
• CLOVER/ACPI/patched folder —> Do you have DTPG.aml?

If Thunderbolt still fails, please run IORegistryExplorer and select File —> Save As... and upload the saved file. Reinstalling the O/S will not fix Thunderbolt because the problem is most likely somewhere in BIOS or the EFI folder.

Casey,

Thanks for the tips.

• BIOS —> Thunderbolt Security —> No Security - YES, SET
• BIOS —> GPIO3 Force Pwr —> Yes or Enabled YES, SET
• CLOVER/ACPI/patched folder —> Do you have DTPG.aml? YES - SSDT-DTPG.aml

I appreciate you looking into this further. Also, side note, my LG UltraFine 5K is not just reporting at 4K resolution. It had been in 5K before but seems like deleting NVRAM or something else kicked it out of 5K mode.

 

[JayShay]

Casey,

Thanks for the tips.

• BIOS —> Thunderbolt Security —> No Security - YES, SET
• BIOS —> GPIO3 Force Pwr —> Yes or Enabled YES, SET
• CLOVER/ACPI/patched folder —> Do you have DTPG.aml? YES - SSDT-DTPG.aml

I appreciate you looking into this further. Also, side note, my LG UltraFine 5K is not just reporting at 4K resolution. It had been in 5K before but seems like deleting NVRAM or something else kicked it out of 5K mode.

UPDATE:

It's working now. Here's what I just did....

1.) Booted Hackintish into Windows (have separate SSD with Win10 install)

2.) Installed Windows Thunderbolt software from Gigabyte's website

3.) Verified that Thunderbolt capabilities worked in Windows - it does - camera, USB, audio etc

4.) Then updated LG 5K UltraFine drivers via the LG Mac store app on my real MacBook Air 2018. The software was out of date so updated.

5.) Plugged back into Hackintosh, rebooted into Mojave and working now.


My guess is this is related to the monitor driver update but who knows. There is a lot of talk about Thunderbolt, Windows, warm booting, cold booting etc. Will continue to test...

UPDATE 2:

So there is something to this booting into Windows... Cold booted (shut down, turned off power) and booted back into Mojave - Bam - Thunderbolt NOT working on monitor. So warm booted back into windows, approved the LG 5K in Windows Thunderbolt software, warm booted back into Mojave, and Thunderbolt working again. I swear I don't have security on in the BIOS so I don't understand this behavior 100%.

Attached is an image of the Windows Thunderbolt software

UPDATE 3:

Yes, I can do this repeatedly. Now, I haven't heard of anyone else reporting that they had to go into Windows and approve the device to get it seen in macOS. Maybe this is exclusive to the 5K LG idk.

 

[JayShay]

Hi JayShay,

Got LG Ultrafine 5K via RX580->Designare->Monitor. Camera, USB on the back, audio - everything works perfectly. Been seeing two displays instead of one, but fixed it with making iGPU headless. BIOS also shows up on screen. hotplugging the display after boot doesn't work as far as I remember (don't need it). Custom USB map via Hackintool, but everything worked with USBInjectAll before. Don't have any other Thunderbolt devices to check.

Can you confirm that you are seeing true 5K from your monitor? Unfortunately I am not any more. I had it working at first, but something changed. Thought maybe it was Whatevergreen (word is you don't need this with Radeon VII) but tested and doesn't work with or without.

You can see my attached screenshot running at 5K - On my real MacBook Air this is running 5K UHD.

Also, are you running SSDT-Z390-DESIGNARE-TB3HP-V4.aml ?

 

[CaseySJ]

UPDATE:

It's working now. Here's what I just did....

1.) Booted Hackintish into Windows (have separate SSD with Win10 install)

2.) Installed Windows Thunderbolt software from Gigabyte's website

3.) Verified that Thunderbolt capabilities worked in Windows - it does - camera, USB, audio etc

4.) Then updated LG 5K UltraFine drivers via the LG Mac store app on my real MacBook Air 2018. The software was out of date so updated.

5.) Plugged back into Hackintosh, rebooted into Mojave and working now.


My guess is this is related to the monitor driver update but who knows. There is a lot of talk about Thunderbolt, Windows, warm booting, cold booting etc. Will continue to test...

UPDATE 2:

So there is something to this booting into Windows... Cold booted (shut down, turned off power) and booted back into Mojave - Bam - Thunderbolt NOT working on monitor. So warm booted back into windows, approved the LG 5K in Windows Thunderbolt software, warm booted back into Mojave, and Thunderbolt working again. I swear I don't have security on in the BIOS so I don't understand this behavior 100%.

Attached is an image of the Windows Thunderbolt software

UPDATE 3:

Yes, I can do this repeatedly. Now, I haven't heard of anyone else reporting that they had to go into Windows and approve the device to get it seen in macOS. Maybe this is exclusive to the 5K LG idk.

Booting into Windows has the effect of initializing the Titan Ridge TB3 controller via the Windows drivers. When we subsequently warm-boot into macOS, the effect lingers. So the behavior you're describing is "scientific". Various Thunderbolt add-in-cards on other motherboards require their owners to cold-boot into Windows and warm-boot into macOS.