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

[CaseySJ]

I've installed Big Sur with OpenCore, but Thunderbolt 3 has never been driven. I use LG 34wk95u 5K*2K monitor, but now I can only connect it with DP cable, and the separation rate is only 3840x1620 and cannot be connected through the Thunderbolt 3 interface. How can I fix this problem now? Thank you very much.

Hello @MajorArc,

I am hesitant to troubleshoot problems with Thunderbolt monitors as stated in Note 7c at the top of Post 1. But I can provide some general comments:

• We should ignore System Information --> Thunderbolt. It will always say No drivers are loaded unless we flash the controller (which should only be done if absolutely necessary).
• To connect a Thunderbolt monitor via Thunderbolt, a DisplayPort cable from your Vega 56 must be connected to DP In port on the rear IO panel. Then connect monitor to the Thunderbolt port closest to HDMI port (but try both).

 

[manofscience]

This most likely indicates a problem with the EFI memory driver. Please post the EFI folder or a screenshot of the Clover folder with “drivers” and “drivers64UEFI” folders fully open.

I don't have a drivers folder in this Clover Configuration for some odd reason.

 

[CaseySJ]

I don't have a drivers folder in this Clover Configuration for some odd reason.View attachment 514203

It might be best to start over, but with OpenCore instead of Clover. It's quite straightforward, as follows...

** Mini-Guide: Fresh Install of Mojave, Catalina, or Big Sur with OpenCore **
This mini-guide assumes that macOS installer has been downloaded and installed on a USB flash disk
Please do not quote this mini-guide in its entirety. Post a link instead​

1. First, install BIOS F9g from here.
2. Then configure BIOS parameters according to Post 1.
3. Locate the USB flash disk that was used to install macOS (the USB install disk).
4. Connect it to a working Mac, mount the EFI partition, rename the existing EFI folder to EFI-CLOVER.
5. Download the OpenCore 0.6.6 (not the newer 0.6.7) EFI folder from here.
   • It's always possible to update OpenCore later.
6. When the file unzips, all of the contents will be in a folder called OC-066-DESGINARE-Z390.
   • Rename this top level folder to EFI.
7. Now move this EFI folder to the EFI partition of the USB install disk.
8. In Finder, navigate to this new EFI folder on the USB install disk.
9. Now we'll generate a new OpenCore config.plist as follows:
   • Go to https://hackindrom.zapto.org (this is the HackinDROM website)
   • Follow the screenshots below.

• When the new config.plist has been downloaded, it should be in the Downloads folder.
• Copy this file to the EFI/OC folder on the USB install disk (EFI partition).
• Now the USB flash disk is ready for Mojave installation.
  • There is no post-install procedure with this method!
• Safely eject the USB flash disk and insert it into the Hackintosh.
• Boot the Hackintosh and press F12 to open the BIOS Boot Menu.
• Select the USB flash disk.
• When the OpenCore GUI appears, select the option to Install macOS Mojave (or "Catalina" or "Big Sur" depending on the version you're installing)
  • This particular boot option must not be selected again during the 2 or 3 reboots that will occur.
• Each time the system reboots, press F12 at the BIOS splash screen to open the BIOS Boot Menu and choose the USB flash disk.
• But from now on, macOS will automatically select the right boot volume.
  • If you have any questions about this, please ask.

When macOS Welcome screen appears, follow the wizard to complete the installation. Again, there is no post-installation procedure.

 

[jiffyslot]

Regarding:

Methodology:
1. I only use Hex Fiend tool with UEFITool to result check
2. Replace all volume with GUID : AFDD39F1-19D7-4501-A730-CE5A27E1154B from F9i by F9j one (from 0xA70000 0xD70000 to 0xE3FFFF). This volume include new Microcodes.
3. At the end of volume 61C0F511-A691-4F54-974F-B9A42172CE53 and also the end of file, I change 32bits data from F9i by F9j one at 0xFFFFC0 address. This data is the Fixed Data address of raw file B52282EE-9B66-44B9-B1CF-7E5040F787C1 (moved because of micro codes size is bigger than previous one)
4. Now, to be flashable with Q-Flash, I have done following modifications on freeform with GUID 56E14F88-234B-4C34-B204-299670447247 (found on Win-Raid website forum):

@Elias64Fr Are you describing what you did to modify the BIOS, or are these parameters that still need to be changed after loading your altered BIOS?

 

[CaseySJ]

Regarding:

Methodology:
1. I only use Hex Fiend tool with UEFITool to result check
2. Replace all volume with GUID : AFDD39F1-19D7-4501-A730-CE5A27E1154B from F9i by F9j one (from 0xA70000 0xD70000 to 0xE3FFFF). This volume include new Microcodes.
3. At the end of volume 61C0F511-A691-4F54-974F-B9A42172CE53 and also the end of file, I change 32bits data from F9i by F9j one at 0xFFFFC0 address. This data is the Fixed Data address of raw file B52282EE-9B66-44B9-B1CF-7E5040F787C1 (moved because of micro codes size is bigger than previous one)
4. Now, to be flashable with Q-Flash, I have done following modifications on freeform with GUID 56E14F88-234B-4C34-B204-299670447247 (found on Win-Raid website forum):

@Elias64Fr Are you describing what you did to modify the BIOS, or are these parameters that still need to be changed after loading your altered BIOS?

He's describing what he did. The new BIOS is fully ready for use.

 

[joevt]

I've installed Big Sur with OpenCore, but Thunderbolt 3 has never been driven. I use LG 34wk95u 5K*2K monitor, but now I can only connect it with DP cable, and the separation rate is only 3840x1620 and cannot be connected through the Thunderbolt 3 interface.

What's wrong with using the DP cable (besides needing a second cable for USB)?
Your screenshot shows that you are using a 3840x1620 HiDPI mode. What mode do you want to use? You can probably use a HiDPI mode up to 4096x1728 if there's a 8192x3456 scaled mode. Create scaled modes using SwitchResX.

Your screenshot doesn't show the output resolution and timing and pixel format (it only shows the frame buffer size 7680x3240 and the frame buffer pixel format). Use SwitchResX to show the output resolution and timing. Use the AGDCDiagnose command to show all that and connection type (should by four lanes of HBR3) and output pixel format.
/System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose -a > AGDCDiagnose_a.txt 2>&1

 

[Cellubab]

Hello to you all, just a reminder if there are any news regarding TB3 with Antelope Audio Devices. In the meantime I had to buy a 2018 Mac Mini to fully implement the device in my workflow. Frustrating.

 

[CaseySJ]

Hello to you all, just a reminder if there are any news regarding TB3 with Antelope Audio Devices. In the meantime I had to buy a 2018 Mac Mini to fully implement the device in my workflow. Frustrating.

I'm following-up with them. Might take a day or two for a reply.

 

[simple.user]

I'm following-up with them. Might take a day or two for a reply.

Hello, Casey.
I'm just one more interested person.
And for your information, I also already have a Zen Tour Synergy Core audio interface.
It's working together perfectly with my Hackintosh based on your build via USB connection.
But I'm highly interested in the TB3 connection.

 

[Cellubab]

I'm following-up with them. Might take a day or two for a reply.

Ok, REALLY a good notice to know something is moving! Again, thank you for your efforts!