Contribute
Register

Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

Although mine boots up at normal speed, there is a way to solve the slow boot time. We add the following in OpenCore as an ACPI patch (credit: @Elias64Fr) with Signature = DSDT:

Comment: disable \_GPE.TINI (Zero, RPS0, RPT0, Zero)
Find: FF5C2E5F 47504554 494E4900 52505330 52505430 00
Replace : FFA3A3A3 A3A3A3A3 A3A3A3A3 A3A3A3A3 A3A3A3A3 A3

Thanks. Can you be so kind to please point me to the relevant .AML file to do this?

And the slow boot time that I'm talking about is from when I push the power button to when the system finally gets to the opencore bootloader screen. Takes about 20 seconds... took only 5 prior to flashing. Will this DSDT that you reference fix the POST speed (i.e., before opencore loads)??

Thanks so much for helping us out!

Edit: I just read you said Opencore patch. Okay I'm going to try to implement this using my plist editor, but if you could be so kind so as to post the relevant plist code to implement this that'd be sweet. I've never implemented an ACPI patch before. I'm going to do some google-fu.

Edit again: I think I figured it out, it definitely spend less time at 'Read 62 Blocks of AML code' so something is working. Prior to the ACPI patch, the system would freeze on the 'Read 62 Blocks of AML code' line for approx 2-3 seconds. But the time to get from 'power button press to opencore screen' is still 20 seconds or so...
 
Last edited:
** Mini-Guide for Viewing, Editing and Verifying Thunderbolt DROM
with ThunderboltUtil **

 
...
Edit again: I think I figured it out, it definitely spend less time at 'Read 62 Blocks of AML code' so something is working. Prior to the ACPI patch, the system would freeze on the 'Read 62 Blocks of AML code' line for approx 2-3 seconds. But the time to get from 'power button press to opencore screen' is still 20 seconds or so...
Please compare your settings to this:
Screen Shot 2020-07-06 at 4.53.51 PM.png
P.S. You know it's a first world problem when we complain about having to wait for 20 seconds. :) But you can also try this experiment:
  • Disable Thunderbolt Support in BIOS.
  • How long does it take to boot to OpenCore?
 
Anyone having a recovered file folder on the recycle bin Each time you start the computer?
 
Last edited:
Please compare your settings to this:
View attachment 479439
P.S. You know it's a first world problem when we complain about having to wait for 20 seconds. :) But you can also try this experiment:
  • Disable Thunderbolt Support in BIOS.
  • How long does it take to boot to OpenCore?
lol @ first world problems. Will report back...
Edit: disabling the controller, the boot time (i.e., from power button press to the opencore screen) goes from 20+ seconds to 4 seconds...

Although I've yet to try this, is it possible to use Apple's bootcamp drivers to allow the flashed thunderbolt controller to work in Windows? Thunderbolt in Windows works just fine on a real Mac in bootcamp...
 
Last edited:
lol @ first world problems. Will report back...
Edit: disabling the controller, the boot time (i.e., from power button press to the opencore screen) goes from 20+ seconds to 4 seconds...
Does the delay occur only when Thunderbolt devices are connected?
Although I've yet to try this, is it possible to use Apple's bootcamp drivers to allow the flashed thunderbolt controller to work in Windows? Thunderbolt in Windows works just fine on a real Mac in bootcamp...
Thunderbolt should work in Windows if we first boot into macOS then warm boot into Windows. Bootcamp drivers may not work, but there might be another solution involving a change to the Thunderbolt SSDT. I'll work on it over the next day or two.
 
Does the delay occur only when Thunderbolt devices are connected?

No, once the Thunderbolt controller is enabled, there’s a significant delay. Irrespective of whether any device is connected at boot time. I’m not sure if it’s one of the various Thunderbolt settings and its interaction with the controller, but I tried various settings and the delay persists. At the end of the day it’s not a showstopper but is annoying when I need to go into the bios to tweak RAM settings, fan curves, CPU voltage/clock speed, etc.

Thunderbolt should work in Windows if we first boot into macOS then warm boot into Windows. Bootcamp drivers may not work, but there might be another solution involving a change to the Thunderbolt SSDT. I'll work on it over the next day or two.
Thanks. This is all so exciting. I feel like hackintoshing has forced me to have more of an appreciation for the hardware in our systems and how they were designed, and any limitations thereof. I’m hoping that, when USB4 comes, the quirks we see with Thunderbolt controllers fade away. But, then again, it’s not clear right now how USB4 will be implemented in hardware and whether macOS on Intel will even support it or if you can use a Thunderbolt3 device on a USB4 controller without the need for SSDTs, DROM, flashing, etc.
 
One-click Thunderbolt SSDT with Unique Identifier generator for GIGABYTE Z490 Vision D:

HackinDROM
Here is it!
This One-click tool provides you Thunderbolt SSDT with Unique Identifier.
You can change Vendor and Device name.

Supported Motherboards and PCIe devices:
Gigabyte Designare Z390
Gigabyte GC-Titan Ridge
Gigabyte GC-Alpine Ridge
Gigabyte Z390 AORUS Xtreme
Gigabyte Z490 Vision D
Asus ThunderboltEX 3
ASRock Z390/Z370 ITX/ac

If needed more options can be added in the future. (@CaseySJ waiting for yours suggestions)
Enjoy!

Please test and give me your feedback for:
Gigabyte Designare Z390 Confirmed
Gigabyte GC-Titan Ridge
Gigabyte GC-Alpine Ridge
Gigabyte Z390 AORUS Xtreme
Gigabyte Z490 Vision D
Asus ThunderboltEX 3
ASRock Z390/Z370 ITX/ac
 
Has anyone tried the iMacPro SMBIOS for this setup? I was testing exporting video files from Final Cut and can see that 90% of the time, the system is using the iGPU instead of the dGPU.

Hoping if I switch to SMBIOS of iMac Pro it will utilize the dGPU 100% of the time, thus a faster render?
 
Depending on your codec, dgpu may not be faster: for h.264/265, quicksync is very fast (igpu).
Real iMac Pro has t1/2 chip to do the 'quicksync' job and we don't have that. My guess is iMac is better than iMac Pro
if we are talking about H.264/265 footage.

Has anyone tried the iMacPro SMBIOS for this setup? I was testing exporting video files from Final Cut and can see that 90% of the time, the system is using the iGPU instead of the dGPU.

Hoping if I switch to SMBIOS of iMac Pro it will utilize the dGPU 100% of the time, thus a faster render?
 
Back
Top