Contribute
Register

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

Please try the two attached files one by one. Ideally we should boot without a Thunderbolt device connected, login, then hot plug a TB device to see if it works.

@CaseySJ

I tested each SSDT file starting each without a TB device connected. Both had similar results as shown below. The only difference I noticed was that the INI-3 SSDT in IORegistryExplorer showed an IOThunderboltPort@5 with values, while the NEW-DROM SSDT contained no values. Both IORegistryExplorer zipped files are attached.

Sequence of tests:

1) Cold start without TB3 device plugged in
2) System Report - NO TB Driver, NO PCI TB3
3) Hot plugged TB3 Drive
4) No TB3 drive in Finder, System Report - NO TB Driver, NO PCI TB3
5) Reboot with TB3 drive plugged in
6) TB3 drive in Finder, System Report - Partial TB Driver, YES PCI TB3
7) Saved IORegistryExplorer file(s) - attached.
8) Eject TB3 drive in Finder and unplug drive - YES TB Driver (screenshot below for NEW-DROM), YES PCI TB3

TB Bus - NEW-DROM.png
The only time I see the full System Information TB Bus is after I do a hot plug -> restart -> eject/unplug TB device. Strange, but it probably makes sense to you.

I'll be happy to keep testing SSDT revisions until we strike gold!
 

Attachments

  • NUC7-INI-3.zip
    607.6 KB · Views: 61
  • NUC7-NEW-DROM.zip
    608.2 KB · Views: 60
How about posting your patch? As a sample, for instance?

It's in the repository :)


@CaseySJ I just looked at the z370a and z370a-II sections of the repository and the SSDT's are identical. Also, the name changes are a lot more concise and clean in the Z370a spoiler. Mine (version 2) was...superfluous.

I other words z370a-II can be removed and z370a can be used for both. I don't won't to clutter your repo :)
 
Last edited:
Hi Casey
I have Gigabyte GC-Titan Ridge add-in-card-PCIe card in X299 WU8 System.
I see your post #16,393
Please recommend a guide for how to Flashing to GC-TITAN-RIDGE-NVM23-Elias64Fr.bin pathed Fimware toGC-Titan Ridge add-in-card?
Thanks for your amazing job.
 
Hi Casey
I have Gigabyte GC-Titan Ridge add-in-card-PCIe card in X299 WU8 System.
I see your post #16,393
Please recommend a guide for how to Flashing to GC-TITAN-RIDGE-NVM23-Elias64Fr.bin pathed Fimware toGC-Titan Ridge add-in-card?
Thanks for your amazing job.

Head over to Post 1!
Screen Shot 2020-05-15 at 9.28.26 AM.png
 
hi, i have a running system 14.5.4 and have to update to 14.5.6 to use the new logic update .... month were passed and i have to find out what i have to do again ;-)

is it possible to update directly to 14.5.6 with skipping 14.5.5 ? if it is possible - where can i find the pages relating to this ( in this huge thread ) ? ;-)
 
Are you using a Thunderbolt SSDT? Does the BIOS have an option called “GPIO3 Force Pwr”? Is Thunderbolt Security set to either None or Legacy?

Z170X-Designare bios does not list GPIO3 Force Pwr as an option under Thunderbolt. Thunderbolt Security is listed, and yes, set to none is the way to get partial TB3 support (devices plugged in at boot only, no howstwap) with this board.

I have attached the Z-170X-Designare bios (that works more stable than the latest) if anyone wants to take a stab at modding it.
 

Attachments

  • mb_bios_ga-z170x-designare_f23b (1).zip
    5.7 MB · Views: 62
Last edited:
What is the make/model of the keyboard?

Do you have a USB-C to USB Type A cable? If so, have you tried plugging that into one of the two black USB ports on the rear IO panel?

MassDrop CTRL keyboard. It works fine when connected to a type-A port. It just doesn't work when connected to a hub via thunderbolt (type-a or otherwise), but it is my only USB2 device that has issues; except for other keyboards. Any keyboard connected via the Thunderbolt hub stops working as soon as MacOS starts loading.
 
I can not get it there is always not recognized under Windows what can I do I have it with the programCH341A with AsProgrammer
 

Attachments

  • Gigabyte-Z390-Designare-TB3-ROM.bin.zip
    244.9 KB · Views: 54
I doubt the hardware is at fault, but who knows?
Just had the same issue again. I checked with IORegistryExplorer what was going on while replugging HS11 (Bluetooth) and HS12 (front USB). Didn't get bluetooth back to work, but noticed an oddity in HS11: it showed "UsbConnector 0x0", just like HS12..
Checked the usb SSDT, which defined HS11 as 0xff. It's really weird. Just to test, I replaced 0xff with 255. Upon rebooting bluetooth worked again and HS11 showed up as 0xff, but I'll just have to wait and see I guess.. ?
If you're running Catalina, did you have Mojave on the same SSD before (i.e. you upgraded from Mojave to Catalina)? If so, please do this:
  • Post a screenshot of /Library/Extensions
  • Run this command in Terminal kextstat | grep -v apple and post a screenshot of the result
  • Then mount EFI partition of macOS SSD, select USBInjectAll.kext from CLOVER/kexts/Other and choose Get Info from the the Finder. What is the version of USBInjectAll.kext?
 
Back
Top