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

[CaseySJ]

I don't know what the different is between Thunderbolt Bus enabled vs just hot plug, sorry.

Regardless, adding SSDT's doesn't make any difference on my system. It doesn't add hotplug or help with stability in any way (that I can tell). Results have been the same for every SSDT I've tried, which includes SSDT-TB3-Designare-X299-EX.aml you provided on March 16, 2021, and March 15th, 2021, and SSDT-TbtOnPch-Designare-X299-EX.aml from May 13th 2020.

I'm actually not even using any SSDT's at the moment, all I have are a couple of ACPI hotpatches, which seem to be helping with sleep/wake stability. Without these the TB3/USB-C devices will eject during sleep/wake:

• _E23 to XE23
• RP05 --> _INI() to RP05 --> XINI()

Here's what I'm experiencing with the above patches:

• Booting inconsistent (random KP’s during boot)
• TB and/or USB-C devices plugged in during boot show up in macOS
• TB3 & USB-C devices are not hot-pluggable. Once disconnected, they will not re-appear
• Sleep/wake occasionally KP’s
• OWC & G-RAID appear in IORegistryExplorer, but I think the device might be broken (image attached)
• G-RAID does not show up in System Information
• USB devices connected to OWC dock can send wake events, despite my GPRW patch
• OWC Dock can be daisy-chained to G-RAID, but not the other way around
• Slow USB3 speeds on OWC dock

Note: I've also tried using TbtForcePower.efi & ThunderboltReset.kext, but they don't make any difference.

I'm attaching the IOReg & a few screenshots, hope that helps.

Thank you

These ACPI patches (_E23 to XE23 and _INI to XINI) should not be used by themselves. They are only meant to be used with SSDT-TbtOnPch-Designare-X299-EX.aml, which is the "complicated" SSDT that enables Thunderbolt Bus.

Summary:

• Option 1: SSDT-TbtOnPch-Designare-X299-EX.aml
  • Requires SSDT-DTPG.aml
  • Requires _E23 --> XE23 ACPI patch
  • Requires RP05._INI() --> RP05.XINI() ACPI patch
  • This tries to enable Thunderbolt Bus, which can be verified by going to System Information --> Thunderbolt.
• Option 2: SSDT-TB3-Designare-X299-EX.aml
  • Requires SSDT-DTPG.aml
  • Do not use _E23 --> XE23 patch
  • Do not use RP05._INI() --> RP05.XINI() patch
  • This does not enable Thunderbolt Bus, but only enables hot plug. System Information --> Thunderbolt will say "No drivers are loaded".
• Option 3: No Thunderbolt SSDT
  • In this case do not apply any ACPI patches

Additionally, TbtForcePower.efi & ThunderboltReset.kext should not be used.

If the only issue is that drives eject during sleep, try the following:

• Disable XMP Memory Profile 1 in BIOS (we can also set memory speed to either 2666MHz or 2933MHz maximum)
• If that does not help, try Jettison app as previously mentioned

 

[gabevf]

These ACPI patches (_E23 to XE23 and _INI to XINI) should not be used by themselves. They are only meant to be used with SSDT-TbtOnPch-Designare-X299-EX.aml, which is the "complicated" SSDT that enables Thunderbolt Bus.

Summary:

• Option 1: SSDT-TbtOnPch-Designare-X299-EX.aml
  • Requires SSDT-DTPG.aml
  • Requires _E23 --> XE23 ACPI patch
  • Requires RP05._INI() --> RP05.XINI() ACPI patch
  • This tries to enable Thunderbolt Bus, which can be verified by going to System Information --> Thunderbolt.
• Option 2: SSDT-TB3-Designare-X299-EX.aml
  • Requires SSDT-DTPG.aml
  • Do not use _E23 --> XE23 patch
  • Do not use RP05._INI() --> RP05.XINI() patch
  • This does not enable Thunderbolt Bus, but only enables hot plug. System Information --> Thunderbolt will say "No drivers are loaded".
• Option 3: No Thunderbolt SSDT
  • In this case do not apply any ACPI patches

Additionally, TbtForcePower.efi & ThunderboltReset.kext should not be used.

If the only issue is that drives eject during sleep, try the following:

• Disable XMP Memory Profile 1 in BIOS (we can also set memory speed to either 2666MHz or 2933MHz maximum)
• If that does not help, try Jettison app as previously mentioned

Thanks for the reply, @CaseySJ

Just wanted to clarify a few things for the sake of figuring out what's wrong with my TB situation:

• Option 1: enabling Thunderbolt Bus with SSDT-TbtOnPch-Designare-X299-EX.aml + ACPI Patches
  • TB & USB-C devices visible during warm or cold boot
  • Nothing shows up in System Information --> Thunderbolt.
  • Hot-plug doesn't work
  • Sleep sort-of works: devices don't get ejected, but occasionally USB devices connected to the OWC dock randomly wake the machine, which can send it into a kernel panic.
    • Q: How do I keep devices connected to the dock from randomly waking up the computer? If I can extend the GPRW patch to work with Thunderbolt, I think this will fix all my issues.
• Option 2: Hot-plug only with SSDT-TB3-Designare-X299-EX.aml (no ACPI patches)
  • TB & USB-C devices visible during warm or cold boot
  • Hot-plug doesn't work
  • Sleep/wake causes devices to unmount and are no longer visible in System Information or IOReg <--- Q: Is this the scenario you recommend I use the Jettison App?
  • Q: What's the difference between the March 15th and March 16th versions linked in my previous post?
• Option 3 (No SSDT's)
  • Same behavior as Option 2.
  • I tried disabling XMP to prevent devices from un-mounting but that didn't work.
• Option 4: ACPI patches only (incorrect)
  • Gives me the same behavior as Option 1

• Q: My IOReg shows a PC00 device root path, but the SSDT's are all using PCI0, is that right?
  
  • I tried replacing PCI0 for PC00 but the system KP's during boot.
• Q: If none of the SSDT's are doing what they're supposed to do, what can we do to troubleshoot it?

 

[pagimamaun]

Hi everyone
Just a small post to aware of not upgrading the bios to last F9
It not only break Thunderbolt USB on OSX but even in Windows and Linux
I own a LG 27md5k that worked well in those 3 OS in dual monitor with another 4K Asus
Actually LG still working but I lost build in camera, audio and usb Hub
USB fonction no more working on 2 USB C port.
I have oculus quest 2 that was recognized on those both USB port with F9i Bios. And actually a lot of peripheral I tried are not working.

I tried multiple bios settings on Thunderbolt with no change Even deactivated Thunderbolt let them on.
I’m waiting for a feedback from gigabyte support.

 

[loghound]

Hi All

There are a lot of great mini-guides and documentation and I've really tried to read them but I'm kind of stuck.

I have a pretty much stock 'golden build' as described in this post (Z390, vega56, Fenvi wireless, no thunderbolt periphials) and it's worked well for a few years.... Right now I'm on Catalina and Clover with most things working.

I've recently decided to upgrade to a new macOS version and the first instructions seem to be to move from clover to Open core. I think I'm doing it right but I'm sort of stuck.

0) I'm using the newest hackindrom (v2.0.8) downloaded two days ago (I think it was built in Late December), bios f9i, currently running catalina, cfg lock disabled and otherwise tried to exactly follow the miniguides
1) per the mini guide I created a USB boot drive, configured for my settings and the only plist changes I've set SecureBootModel to disabled, verbose mode on and I've played with one other op -- the USB drive is to test open core.
2) I boot into the opecore USB stick and select my Catalina boot drive. It get's 'about' half way there but fails pretty consistently after it loads the Apple Security Model. Typical output looks like this

calling mpo_policiy_init for ASP
Security policy loaded: Apple SYtem Policy (ASP)
com.apple.AppleFSCompressionTypeZlib load succeed
com.apple.AppleFSCompressionTypeDataLess load succeeded
Smal

3) It seems to have stalled right after that 2nd load as it's printing out 'smal' (I'm not sure what letter comes next!)

4) I've tried clearing NVRAM (from the opencore bootloader), I've verified CFG Lock is disable (I'm running bios F9i) and for what it's worth my clover boot still works fine... It's just starting from Opencore/USB Flash drive.

5) The other piece of information -- I'm trying to assign a new serial number as part of this build... I did try using my current ones and that (didn't?) seem to matter but I thought I would mention I 'generated' new rom/serial number/etc. from Hackindrom.

-John

 

[bluestarstudios]

Let's examine this problem more broadly:

• On which version of macOS is this happening?

macOS Catalina 10.15.7

• Did (or does) it happen on a previous version of macOS (even a previous minor release of the same major version)?

Yes. It was happening exactly the same on every version of Mojave before.

• If this problem was not experienced in a previous minor release of the same major version of macOS, consider performing a fresh installation of that earlier release on a cheap spare SATA SSD. Does the sluggishness still exist?
• If problem persists, list the makes and modelsof all devices connected to the system:
  • All PCIe cards
  • All Thunderbolt peripherals
  • All internal and external USB devices including keyboard and mouse
  • All NVMe SSDs
  • All SATA SSDs
  • All SATA HDDs

Build Hardware:

• Intel Core i9-9900K 3.6 GHz Eight-Core LGA 1151 Processor.
• Motherboard: Z390 Designare.
• Case: Fractal Design Define R6 USB-C.
• Power Supply: EVGA 750 G3.
• Graphics Card: Radeon RX580.
• SATA Drives: 2x Samsung SSD 860 EVO 1TB + 1x Samsung SSD 860 EVO 4TB
• RAM: HyperX Predator 4x16GB 3600MHz DDR4.
• Cooler: NH-D15S.
• Fenvi FV-T919 wireless network adapter.
• 3x 27” 2k LED Acer monitors.

PCIe cards:

• Radeon RX580
• Fenvi FV-T919 wireless network adapter.

Thunderbolt peripherals: none.

USB devices:

• Apogee Duet audio interface
• Native Instruments Komplete Kontrol S88 keyboard
• Apple Magic Keyboard with Numeric Keypad
• 9 external USB 3 drives connected to a few powered 4-Port USB 3.0 Hubs (sluggishness happens without any of these connected as well).

Note Apple Magic Mouse is connected via Bluetooth.

NVMe SSDs: none.

SATA SSDs:

• 2x Samsung SSD 860 EVO 1TB
• 1x Samsung SSD 860 EVO 4TB

SATA HDDs:

• RAID 0 using 2x WDC WD4005FZBX 4TB (Western Digital Black Performance HDD - 7200 RPM)

Additional SATA peripherals

• Memorex BDBurner 800L v1

• Also check how much disk space is free on every NVMe and SATA SSD in the system. Are any of these SSDs nearly full?

No, they all have plenty of space. Boot Macintosh HD drive has 70% free space.

• Which version of BIOS is installed?

F6

• Run a disk speed test utility such as Black Magic Disk Speed Test to see if any NVMe or SATA SSD is performing poorly.

All of them are performing well.

• Also post a copy of your config.plist with serial numbers removed from PlatformInfo --> DataHub section.

My config.plist doesn't seem to have such a section in the file itself. But I removed:
BoardSerialNumber, SerialNumber, and SmUUID.


Thanks a ton for your time and help @CaseySJ

 

[CaseySJ]

macOS Catalina 10.15.7

Yes. It was happening exactly the same on every version of Mojave before.

Build Hardware:

• Intel Core i9-9900K 3.6 GHz Eight-Core LGA 1151 Processor.
• Motherboard: Z390 Designare.
• Case: Fractal Design Define R6 USB-C.
• Power Supply: EVGA 750 G3.
• Graphics Card: Radeon RX580.
• SATA Drives: 2x Samsung SSD 860 EVO 1TB + 1x Samsung SSD 860 EVO 4TB
• RAM: HyperX Predator 4x16GB 3600MHz DDR4.
• Cooler: NH-D15S.
• Fenvi FV-T919 wireless network adapter.
• 3x 27” 2k LED Acer monitors.

PCIe cards:

• Radeon RX580
• Fenvi FV-T919 wireless network adapter.

Thunderbolt peripherals: none.

USB devices:

• Apogee Duet audio interface
• Native Instruments Komplete Kontrol S88 keyboard
• Apple Magic Keyboard with Numeric Keypad
• 9 external USB 3 drives connected to a few powered 4-Port USB 3.0 Hubs (sluggishness happens without any of these connected as well).

Note Apple Magic Mouse is connected via Bluetooth.

NVMe SSDs: none.

SATA SSDs:

• 2x Samsung SSD 860 EVO 1TB
• 1x Samsung SSD 860 EVO 4TB

SATA HDDs:

• RAID 0 using 2x WDC WD4005FZBX 4TB (Western Digital Black Performance HDD - 7200 RPM)

Additional SATA peripherals

• Memorex BDBurner 800L v1

No, they all have plenty of space. Boot Macintosh HD drive has 70% free space.

F6

All of them are performing well.


My config.plist doesn't seem to have such a section in the file itself. But I removed:
BoardSerialNumber, SerialNumber, and SmUUID.


Thanks a ton for your time and help @CaseySJ

Looks like you're using Clover instead of OpenCore. Have you considered upgrading to OpenCore?

 

[bluetoy]

Hi, I have an ASUS Z390 designare based system + I9 9900k + RX580 working fine with Catalina and Big Sur with opencore 0.7.6.
I have never used Thunderbolt before on this hack, but now I would like to use an Apollo x6. I have USB-C already working fine with an HDD ( even if no hot swap) and I also have installed SSDT-Z390-DESIGNARE-TB3HP-V4.aml.
Should I have to install anything else or maybe flashing the TB3 firmware? Or maybe the system could work just connecting the TB3 audio interface? Thanks

 

[CaseySJ]

Hi, I have an ASUS Z390 designare based system + I9 9900k + RX580 working fine with Catalina and Big Sur with opencore 0.7.6.
I have never used Thunderbolt before on this hack, but now I would like to use an Apollo x6. I have USB-C already working fine with an HDD ( even if no hot swap) and I also have installed SSDT-Z390-DESIGNARE-TB3HP-V4.aml.
Should I have to install anything else or maybe flashing the TB3 firmware? Or maybe the system could work just connecting the TB3 audio interface? Thanks

Hello @bluetoy,

Welcome to the forum! Do note, however, that Z390 Designare is by Gigabyte, not Asus.

Your Apollo should be able to connect and work without flashing the firmware. We recommend setting BIOS --> Thunderbolt --> Thunderbolt Boot Support to Boot Once.

 

[CaseySJ]

Hi All

There are a lot of great mini-guides and documentation and I've really tried to read them but I'm kind of stuck.

I have a pretty much stock 'golden build' as described in this post (Z390, vega56, Fenvi wireless, no thunderbolt periphials) and it's worked well for a few years.... Right now I'm on Catalina and Clover with most things working.

I've recently decided to upgrade to a new macOS version and the first instructions seem to be to move from clover to Open core. I think I'm doing it right but I'm sort of stuck.

0) I'm using the newest hackindrom (v2.0.8) downloaded two days ago (I think it was built in Late December), bios f9i, currently running catalina, cfg lock disabled and otherwise tried to exactly follow the miniguides
1) per the mini guide I created a USB boot drive, configured for my settings and the only plist changes I've set SecureBootModel to disabled, verbose mode on and I've played with one other op -- the USB drive is to test open core.
2) I boot into the opecore USB stick and select my Catalina boot drive. It get's 'about' half way there but fails pretty consistently after it loads the Apple Security Model. Typical output looks like this

calling mpo_policiy_init for ASP
Security policy loaded: Apple SYtem Policy (ASP)
com.apple.AppleFSCompressionTypeZlib load succeed
com.apple.AppleFSCompressionTypeDataLess load succeeded
Smal

3) It seems to have stalled right after that 2nd load as it's printing out 'smal' (I'm not sure what letter comes next!)

4) I've tried clearing NVRAM (from the opencore bootloader), I've verified CFG Lock is disable (I'm running bios F9i) and for what it's worth my clover boot still works fine... It's just starting from Opencore/USB Flash drive.

5) The other piece of information -- I'm trying to assign a new serial number as part of this build... I did try using my current ones and that (didn't?) seem to matter but I thought I would mention I 'generated' new rom/serial number/etc. from Hackindrom.

-John

Hello John,

Please have a look at this guide for switching from Clover to OpenCore. If you have any trouble with it, we'll try to help.

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

The Hackintosh plugins are all in the OpenCore 0.6.2 update zip that CaseySJ made or you can just download them individually on Github. I have reinstalled fxfactorty version 7.1.7.. the spinning ball issue is still there in fcp title tab and sometimes in os also..it is annoying. Clover is my...

www.tonymacx86.com

 

[CaseySJ]

Thanks for the reply, @CaseySJ

Just wanted to clarify a few things for the sake of figuring out what's wrong with my TB situation:

• Option 1: enabling Thunderbolt Bus with SSDT-TbtOnPch-Designare-X299-EX.aml + ACPI Patches
  • TB & USB-C devices visible during warm or cold boot
  • Nothing shows up in System Information --> Thunderbolt.
  • Hot-plug doesn't work
  • Sleep sort-of works: devices don't get ejected, but occasionally USB devices connected to the OWC dock randomly wake the machine, which can send it into a kernel panic.
    • Q: How do I keep devices connected to the dock from randomly waking up the computer? If I can extend the GPRW patch to work with Thunderbolt, I think this will fix all my issues.
• Option 2: Hot-plug only with SSDT-TB3-Designare-X299-EX.aml (no ACPI patches)
  • TB & USB-C devices visible during warm or cold boot
  • Hot-plug doesn't work
  • Sleep/wake causes devices to unmount and are no longer visible in System Information or IOReg <--- Q: Is this the scenario you recommend I use the Jettison App?
  • Q: What's the difference between the March 15th and March 16th versions linked in my previous post?
• Option 3 (No SSDT's)
  • Same behavior as Option 2.
  • I tried disabling XMP to prevent devices from un-mounting but that didn't work.
• Option 4: ACPI patches only (incorrect)
  • Gives me the same behavior as Option 1

• Q: My IOReg shows a PC00 device root path, but the SSDT's are all using PCI0, is that right?
  
  • I tried replacing PCI0 for PC00 but the system KP's during boot.
• Q: If none of the SSDT's are doing what they're supposed to do, what can we do to troubleshoot it?

Your are quite right that PC00 should be used instead of PCI0. The system should not crash when using PC00. Attached are modified versions of the (a) simple and (b) complex versions of the Thunderbolt SSDT. As before:

• Simple --> must disable the two ACPI patches (SSDT-TB3-Designare-X299-EX.aml)
• Complicated One --> must enable the two ACPI patches (SSDT-TbtOnPch-Designare-X299-EX.aml)

Please perform a cold boot after installing either one of these SSDTs and when switching between them. This is necessary in order to put the Thunderbolt controller into the correct starting condition.