Contribute
Register

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

I didn't read the post good..my bad

is this what you need?

Thanks @vipermachine. That's part of it. It seems that script did not capture the Thunderbolt DROM
The script should have saved the firmwares in the same folder as the thunderboltinfo.txt file. You need kernel 5.11 to get the adapter type for each Thunderbolt port (shows which port is the NHI, etc.).
 
Last edited:
It does not work, even unbootable. Maybe I should try Gigabyte GC-Alpine Ridge add-in-card. Does that card work well with USB 3.1 hotplug?
By the way, I also tried to hot plug my Android phone, and data in the phone could be recognized by Android File Transfer. It also appeared as a USB 2.0 device in the system information. But another Android phone did work that way. Interesting!
 
Yes. But keep in mind that there will be some “eccentricities” with any flashed controller. It won’t be perfect.
I tested Thunderbolt ports with a Thunderbolt device (portable hard disk). Hot plug worked and the link speed was great. The only problem is that the Thunderbolt device can not be recognized with cold-boot. I have to re-plug the cable to get it to work.
How to get the device recognized when cold-boot?
 
It does not work, even unbootable. Maybe I should try Gigabyte GC-Alpine Ridge add-in-card. Does that card work well with USB 3.1 hotplug?
Yes.
 
The script should have saved the firmwares in the same folder as the thunderboltinfo.txt file. You need kernel 5.11 to get the adapter type for each Thunderbolt port (shows which port is the NHI, etc.).
From this link posted earlier regarding USB4 in latest Linux kernel:

“A connection manager can be implemented either in firmware or software. Typically PCs come with a firmware connection manager for Thunderbolt 3 and early USB4 capable systems. Apple systems on the other hand use software connection manager and the later USB4 compliant devices follow the suit.

The Linux Thunderbolt driver supports both and can detect at runtime which connection manager implementation is to be used. To be on the safe side the software connection manager in Linux also advertises security level user which means PCIe tunneling is disabled by default.”

If my interpretation is correct, this is a significant enhancement in Linux, but one that appears to be mandated by the USB4 spec. Historically, Linux has only supported firmware connection mode, which is why our flashed controllers (which require software connection mode) are problematic in Linux.

But now Linux supports both firmware and software connection modes. So flashed controllers should work just as well (“well” is arguable) under Linux as they do in macOS.

If USB4 mandates support for both firmware and software connection modes, this means Windows must support software connection mode as well.
 
Last edited:
Hello Mr CaseySJ,
I am planning to buy a Titan Ridge card (v 1.0 or 2.0) for a Z390 M Gaming. Do you think that I can use "HackinDROM (Internet) OC Titan Ridge (1 or 2) option" to generate a TB3 SSDT without having previously flashed the card and with this motherboard ?
 
Hello Mr CaseySJ,
I am planning to buy a Titan Ridge card (v 1.0 or 2.0) for a Z390 M Gaming. Do you think that I can use "HackinDROM (Internet) OC Titan Ridge (1 or 2) option" to generate a TB3 SSDT without having previously flashed the card and with this motherboard ?
Yes, no problem.
 
Thank you. I'll try it and will come back. Just a little doubt. Do you know if I need to make the DROM again after reflashing?
I'm back, but with sad news.
I' ve flashed V1 and tested, but the "Thunderbolt/USB4" field in System report shows me "No drivers loaded", I've tried with V2 and the same.
In the BIOS, with the original firmware and V1 appears "Thunderbolt" settings under "Peripheals", useng v2 and v3, in "Peripheals" the "Thunderbolt" field is no longer visible.

I will go back to V3.
Besides, do you know if Im putting the jumpers right? (Attached an image found on internet of a Titan ridge card that I've used to guide myself on my alpine ridge.)
 

Attachments

  • 5900-received763002367385823.jpeg
    5900-received763002367385823.jpeg
    77.2 KB · Views: 56
I've modified the Thunderbolt SSDT based on the real DROM. As mentioned earlier, this is not likely to make a difference, but we might as well try for the sake of completeness.

If this does not help, it may be justified to flash the firmware. You can still use this SSDT with the flashed firmware. The modified firmware was created for @S1lla, but I did not receive confirmation that it works. So if you decide to flash it (again, please be mindful of the risks involved) you'll be our beta tester. The modified firmware is attached here for convenience.
Hi @CaseySJ

I Flashed the firmware and all went good. (I made a backup of the original FW)
However, Thunderbolt is completely gone in macOS and in Linux.


Do I have to put the original FW back?

Attached the confirmation of the flash.

Cheers!
 

Attachments

  • Screenshot 2021-03-20 at 22.35.15.png
    Screenshot 2021-03-20 at 22.35.15.png
    2.3 MB · Views: 55
Hi @CaseySJ

I Flashed the firmware and all went good. (I made a backup of the original FW)
However, Thunderbolt is completely gone in macOS and in Linux.


Do I have to put the original FW back?

Attached the confirmation of the flash.

Cheers!
Please compress and post the original firmware. I would like to modify it from scratch. There appear to be some errors in the previous modified file.
 
Back
Top