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

[vicantu]

@vicantu,

Thank you for the detailed report; it's quite helpful. The SSDT you have already contains debug logging, but it's currently turned off. We can do the following:

• First, hot plug a Thunderbolt device then restart IORegistryExplorer to see if the device tree appears under DSB1.
• Next, to enable debug logging we just need to do this:
  • Download attached ZIP that contains 2 files.
  • Copy ACPIDebug.kext to CLOVER/kexts/Other
  • Copy SSDT-DTPG-V3.aml to CLOVER/ACPI/patched, but move the previous file (SSDT-DTPG-V2.aml) to CLOVER/misc
  • Reboot
• Thunderbolt logs can then be seen as follows (in Terminal): log show --last boot | grep ACPIDebug

Thank you, here is the sequence of the test and the result:

1. I completely shut down and reboot the NUC8 with no TB3 device connected and using your SSDT-TbtOnPCH-NUC-8-OSY86-V2.aml and SSDT-DTPG-V2.aml installed, this is what appeared:

2. Hot Plug a TB3 Drive an restarted IORegistryExplore, I don't see the device tree appearing under DSB1, I just see some changes under IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/RP05@1C,4/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0/AppleThunderboltHAL/AppleThunderboltNHIType3/IOThunderboltController/IOThunderboltPort@5/IOThunderboltSwitchType3/IOThunderboltPort@1

Like yesterday, the drive was not recognized or mounted by the Operative System

3. I completed all of the following Keeping the TB3 Drive connected:

• Copy ACPIDebug.kext to CLOVER/kexts/Other
• Copy SSDT-DTPG-V3.aml to CLOVER/ACPI/patched, but move the previous file (SSDT-DTPG-V2.aml) to CLOVER/misc
• Reboot

4: I run the Terminal command:

$ log show --last boot | grep ACPIDebug

2020-05-31 20:00:48.253519-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: Version 0.1.4 starting on OS X Darwin 19.4.
2020-05-31 20:00:48.253958-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "RSTR", 0x90039854, }
2020-05-31 20:00:48.254033-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "ROOT", 0xe00e4000, }
2020-05-31 20:00:48.254102-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "UPSB", 0xe0200000, }
2020-05-31 20:00:48.254188-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "DSB0", 0xe0300000, }
2020-05-31 20:00:48.254261-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "DSB1", 0xe0308000, }
2020-05-31 20:00:48.254329-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "DSB2", 0xe0310000, }
2020-05-31 20:00:48.254412-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "DSB4", 0xe0320000, }
2020-05-31 20:00:48.254480-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "NHI0", 0xe0400000, }
2020-05-31 20:00:48.254549-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: "TB3 _INI"
2020-05-31 20:00:48.254631-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: "Upstream VID/DID okay"
2020-05-31 20:00:48.254704-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "ICME 1", 0xffffffff, }
2020-05-31 20:00:48.254773-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: "Configure root"
2020-05-31 20:00:48.254851-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: "Configure UPSB"
2020-05-31 20:00:48.254917-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: "Wait for link training"
2020-05-31 20:00:48.254983-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: "Configure DSB"
2020-05-31 20:00:48.255048-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: "Wait for down link"
2020-05-31 20:00:48.255137-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: "Configure NHI"
2020-05-31 20:00:48.255204-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "NHI BAR", 0x90000000, }
2020-05-31 20:00:48.255271-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: "CNHI done"
2020-05-31 20:00:48.255351-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "ICME 2", 0x800001a7, }
2020-05-31 20:00:48.255419-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "ICME 3", 0x800001a7, }
2020-05-31 20:00:48.255486-0400 0xd3 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "ICME 4", 0x800001a7, }
2020-05-31 20:00:48.354227-0400 0x76 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "UGIO", 0xffffffffffffffff, 0xffffffffffffffff, }
2020-05-31 20:00:48.354387-0400 0x76 Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "UGIO finish", 0x0, 0x0, }
2020-05-31 20:00:48.355705-0400 0x11e Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "CRMW", 0x13e, 0x0, }
2020-05-31 20:00:48.355841-0400 0x11e Default 0x0 0 0 kernel: (kernel) ACPIDebug: { "CRMW", 0x23e, 0x0, }


I hope this helps solve the mistery, ready to proceed to test anything you want.

Thank you

 

[Ploddles]

Damn! Broke? Lucky it was under warranty.

Yep, working away and the PC crashes. Can see a red light in the case indication a CPU fault. A 'resistor' or something had just fallen off. See here.

 

[elfcake]

If you need Thunderbolt Bus (most folks don't) on the Designare Z390, then there are at least two choices:

• Flash the on-board Thunderbolt firmware chip or (not 'and')
• Flash the Thunderbolt firmware on a GC-Titan Ridge add-in-card.

A third option is to use an Alpine Ridge add-in-card and activate Thunderbolt Bus using SSDT alone, although this might be the most convenient, but least functional/reliable of the three options.

Yes, the latter is what I have done. No hot plug but I don't care. The only other thing is constant wake from sleep that I suspect is the AIC but I cannot verify that that is the cause and have decided to live with it too. I also suspect that the Wifi/Bluetooth AIC may be the suspect but I have tried three different card. The wifi works, Bluetooth woks but the Magic Mouse does not connect. I guess if the Designare also has the same problems with TB3 then I should probably save the money. I told my wife of the plans and she said, "I keep telling you to abandon Hackintosh and get an iMac... "Resistance is futile".

 

[NCMacGuy]

Yes, the latter is what I have done. No hot plug but I don't care. The only other thing is constant wake from sleep that I suspect is the AIC but I cannot verify that that is the cause and have decided to live with it too. I also suspect that the Wifi/Bluetooth AIC may be the suspect but I have tried three different card. The wifi works, Bluetooth woks but the Magic Mouse does not connect. I guess if the Designare also has the same problems with TB3 then I should probably save the money. I told my wife of the plans and she said, "I keep telling you to abandon Hackintosh and get an iMac... "Resistance is futile".

@elfcake

What type of CPU cooler do you use? I use a Corsair H115i hydro cooler that had a USB plug to interface with Windows for settings. When I had the USB plugged in, the hack wouldn't sleep because the Corsair was continually polling via the USB even when the pump wasn't running. I just disconnected the USB and the hack slept. If I need to reset something in the Corsair via Windows, I can plug the USB in, and when done unplug it again. Not the greatest solution, but the USB cable has been unplugged for months.

 

[CaseySJ]

Couple of Volunteers Needed:

• Purpose:
  • To test wake-from-sleep for Thunderbolt monitors
• Qualification:
  • You must have a Thunderbolt monitor that is not currently waking from sleep
• Prerequisites:
  • Designare Z390 Hackintosh (only this motherboard at this time)
  • Flashed Thunderbolt firmware either (a) on the on-board controller or (b) on an add-in GC-Titan Ridge
  • A flashed GC-Alpine Ridge also qualifies
  • Thunderbolt monitor
    • DisplayPort cable must be connected from AMD GPU to DisplayPort-IN
• Chances of success:
  • Slim
  • This will be a very brief exercise; Thunderbolt monitor will either wake from sleep or not wake from sleep
  • This exercise is based on a file from Elias64Fr, but may not work at all on this motherboard

To participate, please provide:

• Make / model of Thunderbolt monitor
• Make / model of AMD GPU
• Slot number of the AMD GPU (e.g. top long slot, middle long slot, bottom long slot)
• Thunderbolt SSDT for your flashed Thunderbolt controller (from CLOVER/ACPI/patched folder)

 

[elfcake]

@elfcake

What type of CPU cooler do you use? I use a Corsair H115i hydro cooler that had a USB plug to interface with Windows for settings. When I had the USB plugged in, the hack wouldn't sleep because the Corsair was continually polling via the USB even when the pump wasn't running. I just disconnected the USB and the hack slept. If I need to reset something in the Corsair via Windows, I can plug the USB in, and when done unplug it again. Not the greatest solution, but the USB cable has been unplugged for months.

@NCMacGuy , A Cryorig A-Series 280mm. It does not use USB for the pump, rather the header for pump/fan.

 

[mathgeek]

If you need Thunderbolt Bus (most folks don't) on the Designare Z390, then there are at least two choices:

• Flash the on-board Thunderbolt firmware chip or (not 'and')
• Flash the Thunderbolt firmware on a GC-Titan Ridge add-in-card.

A third option is to use an Alpine Ridge add-in-card and activate Thunderbolt Bus using SSDT alone, although this might be the most convenient, but least functional/reliable of the three options.

@CaseySJ, I may have missed this in earlier guides/discussion, but why is it not an 'and'?

 

[CaseySJ]

@CaseySJ, I may have missed this in earlier guides/discussion, but why is it not an 'and'?

Context is king. That post was a specific reply to a specific question; namely, whether a flashed Titan Ridge on the motherboard also requires installation of a flashed Titan Ridge add-in-card. However, after rereading the post I can see that I completely misunderstood the question.

Will update my previous reply.

 

[mathgeek]

Context is king. That post was a specific reply to a specific question; namely, whether a flashed Titan Ridge on the motherboard also requires installation of a flashed Titan Ridge add-in-card. However, after rereading the post I can see that I completely misunderstood the question.

Will update my previous reply.

Ah, got it. I thought for some reason flashing both would be a problem. Thanks for clarifying.

 

[CaseySJ]

Thank you, here is the sequence of the test and the result:

1. I completely shut down and reboot the NUC8 with no TB3 device connected and using your SSDT-TbtOnPCH-NUC-8-OSY86-V2.aml and SSDT-DTPG-V2.aml installed, this is what appeared:

2. Hot Plug a TB3 Drive an restarted IORegistryExplore, I don't see the device tree appearing under DSB1, I just see some changes under IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/RP05@1C,4/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0/AppleThunderboltHAL/AppleThunderboltNHIType3/IOThunderboltController/IOThunderboltPort@5/IOThunderboltSwitchType3/IOThunderboltPort@1

Like yesterday, the drive was not recognized or mounted by the Operative System

3. I completed all of the following Keeping the TB3 Drive connected:

• Copy ACPIDebug.kext to CLOVER/kexts/Other
• Copy SSDT-DTPG-V3.aml to CLOVER/ACPI/patched, but move the previous file (SSDT-DTPG-V2.aml) to CLOVER/misc
• Reboot

4: I run the Terminal command:

$ log show --last boot | grep ACPIDebug
...
I hope this helps solve the mistery, ready to proceed to test anything you want.

Thank you

@vicantu,

The log files from you and @NCMacGuy are quite helpful. I'm attaching two different versions of the SSDT:

• SSDT-TbtOnPCH-NUC-8-OSY86-V3
  • Please try this first. Remove the previous V2.
  • Continue to use both ACPIDebug.kext and SSDT-DTPG-V3 just like last time.
  • Also continue to use the same ACPI rename (_E40 to XE40).
  • This one enhances the UGIO method to enable/disable Thunderbolt power dynamically.
• SSDT-TbtOnPCH-NUC-8-NO-PWR-V1
  • Then remove the above V3 SSDT and replace with this one.
  • Continue to use both ACPIDebug.kext and SSDT-DTPG-V3 just like last time.
  • Also continue to use the same ACPI rename (_E40 to XE40).
  • This version removes power management functions.

We should conduct the same test again, namely:

• Boot without Thunderbolt devices connected.
• Then hot-plug a Thunderbolt device.
• Run IORegistryExplorer to see if the device tree appears under DSB1 or DSB4. If not, restart IORegistryExplorer.
• Get the ACPIDebug logs: log show --last boot | grep ACPIDebug
• Post screenshot of System Information --> Thunderbolt.