Contribute
Register

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

i still hear and get told dont update to cat if you dont want to have problems with some plugs or programms xD
so i decided to stay on mojave
Ableton , Studio One
Uad , izo , korg , spectrasonics , NI , Serum and some other fx plugs

is the problem in the mojave hacki install ?
Catalina last version is pretty stable and enough to record produce mix mastering with all plugins you know (only 64bit versions of course because Catalina doesn't support 32bit)

I suggest you to make a fresh install of Catalina.
Wait Casey and the others to confirm if Vega 56 is full supported with Catalina, also about Catalina last version (10.15.5) and the Installation Guide

And sorry I can't help you with Mojave
 
I want to check in with my experiences with Titan Ridge cards and my 5k UltraFine display.

My hardware:
• Gigabyte Z390 Aorus Pro
• Gigabyte Titan Ridge Rev. 1 (Both unflashed and modified/flashed)
• An LG 5k UltraFine 27" Monitor
• Dual displayport output going from a 5700XT going to the Titan Ridge card.
• Catalina 10.15.5 with Opencore 0.5.9.

Behavior with an unmodified stock card on NVM 50:
1. On cold boot the BIOS and bootloader show immediately.
2. The visual/display portion of the monitor works fine when entering and using MacOS
3. None of the built-in accessories like the webcam, microphone, and even the USB-C ports work.
4. On reboot, BIOS, bootloader, and MacOS show and work, but none of the devices do.

Behavior with a pre-flashed card purchased on ebay* with a DSDT from this thread
*(I am not sure which firmware this board was flashed with. The seller only said "2nd revision of DSM2 firmware" :rolleyes: The SHA of the firmware is c608d7dec573bf385129299ef5bde21549113e46)
1. On cold boot neither the BIOS nor the bootloader show.
2. Once MacOS loads the monitor wakes up.
3. All connected devices like the webcam and USB-C ports work.
4. On reboot the BIOS and bootloader show, booting into MacOS works.

I have since bought flashing gear and the above behavior is also the same with Elias64's NVM23 firmware.

Question:
Is the behavior with the modified NVM 23 firmware and my 5K monitor the best case scenario right now? Or is there a way to get the display to turn on on cold boot AND get all of its included devices and USB ports to work?

Thank you to Elias64, CaseySJ and everyone else who has worked on getting thunderbolt 3 to work in hackintoshes.
 
Last edited:
HI @weachy and @CaseySJ

Not using just SSDT, but with the help of CaseySJ I successfully flashed one of my NUC8 and it works perfectly well... UNTIL it sleeps, after that the functionality is missing and I need to shutdown and disconnect the power cable in order to Thunderbolt work again, I don't know if any advance can be done to fix that.

Saludos

Hi @vicantu
You're not alone. I flashed my Nuc8 with "NUC8i7HNKpatched.bin", got same "Thunderbolt died after wake-from-sleep" issue here. And you're right, hot reboot won't help, I have to shutdown and re-connect power cable to let it work again.

Hi @CaseySJ
Is there any chance to let Thunderbolt3 work after wake-from-sleep? Thanks again!
 
CC: @ziggenpuss @bmoney @brousseau6933 @boob @verendus @evithoma @CaseySJ

Another update - the Inateck card is working fine, and doesn't crash when the onboard USB ports crash (currently posting this just after all of the onboard USB ports have stopped working). So I'm currently running everything from the two ports on the Inateck card. As I don't use much in the way of USB 3 devices other than the occasional SSD (which I can plug into the TB/USB-C ports if necessary) it looks like this is the way I'm going to go for the moment. Shame we can't find out the reason (@CaseySJ, could you point me towards how I discover which driver is loaded for the Inateck card, please? Maybe it's a driver issue?), but it seems to be stable, which is the most important thing!

TL;DR can recommend the Inateck 2 Port PCI-E USB 3.0 Express Card, Mini PCI-E USB 3.0 Hub Controller Adapter, with Internal USB 3.0 20-PIN Connector should you be having USB problems. It'll only leave you with 2 external USB ports (and those ports may not run at USB 3.0 speeds - you have been warned) but it should work.

@kellymac12 Would you mind posting shop links to the ones you're using? Think I'm going to take the plunge with these, Apple is apparently flat out denying it's a problem with MacBooks, so it's not looking great for a software fix :/
 
Try again please.


This is what I get now:
You forgot to update the CRC-32c.

Code:
open https://ravalian.com/thunderbolt/index.php
# 0) click "(OPTIONAL) Generate new Thunderbolt DROM for Z390 Designare" to change UID
# 1) click "STEP 1", to place the .dsl code in the clipboard
# 2) then paste into a new plain text file with dsl suffix (or paste into MaciASL.app)
# 3) repeat to change UID
#=========================================================================================
source /Volumes/Work/Programming/ThunderboltProjects/Scripts/ThunderboltUtil.sh
loaddslfile /Volumes/Work/Programming/ThunderboltProjects/Notes/examples/Inqnuamscriptresult.dsl
listdroms

1)
thedrom=2E0065297684880000DF1C090501690001000D00010008818002800000000882900180000000088380048001000008849003800100000585500000058650000002870B88200100640000000000038980058A504000058B5040000B0147494741425954450011025A3339302044455349474E41524500
sources:
/Volumes/Work/Programming/ThunderboltProjects/Notes/examples/Inqnuamscriptresult.dsl:\_SB.PCI0.RP05.UPSB.DSB0.NHI0._DSM:ThunderboltDROM

usedromnum 1
dumpdrom

0x01) UID: 0x0000888476296500
0x0d) Device ROM Revision: 1
0x10) Vendor ID: 0x1
0x12) Device ID: 0xD
0x14) Device Revision: 0x1
0x15) EEPROM Revision: 0
0x16)   1: 800280000000
0x1e)   2: 900180000000
0x26)   3: 800480010000
0x2e)   4: 900380010000
0x36)   5: 500000
0x3b)   6: 500000
0x40)   7: 
0x42)   8: 200100640000000000
0x4d)   9: 80
0x50)   A: 504000
0x55)   B: 504000
0x5a)   1: "GIGABYTE"
0x65)   2: "Z390 DESIGNARE"
0x09) CRC32: 0x05091cdf (expected: 0x211fde47)
0x76) End

repairchecksums
makedromdsl

    "ThunderboltDROM",
    Buffer (0x76)
    {
        /* 0x00     */  0x2E,                                           // CRC8 checksum: 0x2E
        /* 0x01     */  0x00, 0x65, 0x29, 0x76, 0x84, 0x88, 0x00, 0x00, // Thunderbolt Bus 0, UID: 0x0000888476296500
        /* 0x09     */  0x47, 0xde, 0x1f, 0x21,                         // CRC32c checksum: 0x211FDE47
        /* 0x0D     */  0x01,                                           // Device ROM Revision: 1
        /* 0x0E     */  0x69, 0x00,                                     // Length: 105 (starting from previous byte)
        /* 0x10     */  0x01, 0x00,                                     // Vendor ID: 0x1
        /* 0x12     */  0x0D, 0x00,                                     // Device ID: 0xD
        /* 0x14     */  0x01,                                           // Device Revision: 0x1
        /* 0x15     */  0x00,                                           // EEPROM Revision: 0
        /* 0x16   1 */  0x08, 0x81, 0x80, 0x02, 0x80, 0x00, 0x00, 0x00, 
        /* 0x1E   2 */  0x08, 0x82, 0x90, 0x01, 0x80, 0x00, 0x00, 0x00, 
        /* 0x26   3 */  0x08, 0x83, 0x80, 0x04, 0x80, 0x01, 0x00, 0x00, 
        /* 0x2E   4 */  0x08, 0x84, 0x90, 0x03, 0x80, 0x01, 0x00, 0x00, 
        /* 0x36   5 */  0x05, 0x85, 0x50, 0x00, 0x00, 
        /* 0x3B   6 */  0x05, 0x86, 0x50, 0x00, 0x00, 
        /* 0x40   7 */  0x02, 0x87, 
        /* 0x42   8 */  0x0b, 0x88, 0x20, 0x01, 0x00, 0x64, 0x00, 0x00, 0x00, 0x00, 0x00, 
        /* 0x4D   9 */  0x03, 0x89, 0x80, // PCIe xx:04.0
        /* 0x50   A */  0x05, 0x8a, 0x50, 0x40, 0x00, 
        /* 0x55   B */  0x05, 0x8b, 0x50, 0x40, 0x00, 
        /* 0x5A   1 */  0x0b, 0x01, 0x47, 0x49, 0x47, 0x41, 0x42, 0x59, 0x54, 0x45, 0x00, // Vendor Name: "GIGABYTE"
        /* 0x65   2 */  0x11, 0x02, 0x5A, 0x33, 0x39, 0x30, 0x20, 0x44, 0x45, 0x53, 0x49, 0x47, 0x4E, 0x41, 0x52, 0x45, 0x00, // Device Name: "Z390 DESIGNARE"
    },
 
Do you suspect that the problem lies with USB? If you copy some of those music files from LaCie to an internal SSD and play them from the internal SSD, do the same freezes still occur?
@CaseySJ - At the moment I'm just trying a few various 'setups' on playback, with some USB on/off etc. will report back.
Try shutting down and unplugging the computer for a minute or so and see if that helps. Though not a solution, I had less frequent freezes after doing this which was usually after booting from windows.
@bmoney - Yeah, thanks but no joy on that.. tried that back in early April when this initially started for me with a Logitech webcam C920e [USB 2] and what I thought initially was the culprit a Softube Console 1 [USB 2].
 
Last edited:
(dumb noob question incoming)
i try now the *** Thunderbolt DROM Micro-Guide for Designare Z390 ***
i think i get the start:
i downloadet the SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390.aml
found the section with the tbDROM and tbConfig
but with the

Replace the 5 green numbers below with 5 randomly selected hex numbers

im little bit confused

should i choose any numbers from my head ?

and after that i replace the SSDT-Z390-DESIGNARE-TB3HP-V4.aml with the "modified" SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390.aml
and the DSDT from the same download from the micro guide ?

or do i need to modify any file and flash it to the winbond ?
 
(dumb noob question incoming)
i try now the *** Thunderbolt DROM Micro-Guide for Designare Z390 ***
i think i get the start:
i downloadet the SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390.aml
found the section with the tbDROM and tbConfig
but with the

Replace the 5 green numbers below with 5 randomly selected hex numbers

im little bit confused

should i choose any numbers from my head ?

and after that i replace the SSDT-Z390-DESIGNARE-TB3HP-V4.aml with the "modified" SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390.aml
and the DSDT from the same download from the micro guide ?

or do i need to modify any file and flash it to the winbond ?
  • Replace the 5 green numbers with 5 random hex numbers between 0x00 and 0xFF.
  • Then compute CRC-8 from the website linked in the guide.
  • Replace first byte with new CRC-8 value.
  • Then open the SSDT from the guide, find ThunderboltDROM section, and replace the first 9 bytes with the new bytes.
  • Save the file.
  • Replace the existing Thunderbolt SSDT with the new SSDT.
  • The Winbond chip does not have to be touched.
 
Back
Top