Contribute
Register

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

Hi @CaseySJ,

I'm about to attempt flashing the SPI ROM on my GC-Titan Ridge but I just have two questions beforehand that I can't seem to find answers to;

1. Is there a particular reason why a Raspberry Pi 1 B+ wouldn't work instead of a 3B or a 4? I only have access to that model at the moment.

2. Does this procedure enable the GC-Titan Ridge alongside the onboard Titan Ridge controller of the Designare for a total of four Thunderbolt 3 ports? Or does it disable the onboard controller?

Much thanks to you and @Elias64Fr for the tremendous amount of work you guys have done!
 
@CaseySJ @Elias64Fr

Any advice? Is it possible there is a configuration issue?
Are you using WEG? Try removing it if you are, and use pike R black screen patch.

P.S. I have noticed, and I think also the boys with the Apple Thunderbolt displays only get a post on the Thunderbolt Display on a warm boot.
 
Are you using WEG? Try removing it if you are, and use pike R black screen patch.

P.S. I have noticed, and I think also the boys with the Apple Thunderbolt displays only get a post on the Thunderbolt Display on a warm boot.
I am currently using WEG. I experimented with not using it while trying out RadeonBoost. Could not get multiple monitors working without it. That was before my TB3 monitor though. I will give that a go on my next round.
 
Hi. Just a short note on Thunderbolt3 devices. Presonus Quantum 2626 TB3 works flawlessly with the Z390 Designare. Running Logic X Pro.. very low latency, good quality preamps.
Wonderfull!! If you are looking for a Thunderbolt Audio interface fit for a hackintosh, here it is. Presonus Quantum 2626.
Glad to hear it -- added to Thunderbolt 3 Experiences in Post #1.
 
Hi @CaseySJ,

I'm about to attempt flashing the SPI ROM on my GC-Titan Ridge but I just have two questions beforehand that I can't seem to find answers to;

1. Is there a particular reason why a Raspberry Pi 1 B+ wouldn't work instead of a 3B or a 4? I only have access to that model at the moment.

2. Does this procedure enable the GC-Titan Ridge alongside the onboard Titan Ridge controller of the Designare for a total of four Thunderbolt 3 ports? Or does it disable the onboard controller?

Much thanks to you and @Elias64Fr for the tremendous amount of work you guys have done!
Hello @roastable,

1. According to Wikipedia, the Raspberry Pi Model 1 B+ has the full set of GPIO pins we need (SPI pins) so you should be able to use it.

2. Flashing the firmware of GC-Titan Ridge will only enable Thunderbolt Bus on GC-Titan Ridge. Fortunately this PCIe card is easy to flash. The Designare Z390 has its own separate Thunderbolt controller and hence its own separate firmware chip for that controller. Flashing the Designare is more difficult.
 
@CaseySJ, I've got a few clues to add to the pile for the sleep problem with Patched-Firmware-Thunderbolt setups.

Earlier today I fixed a USB Power issue where it would sporadically not load the USBX properties under EC. Sometimes they were there, sometimes they weren't. I found that it was due to them loading from SSDT-USBX.aml and USBPorts.kext. I removed the properties from the kext and that solved it.

After doing a few ThunderboltROM and SSDT test (attempted to patch SSDT-6.aml...whomp) I noticed that when I attempt sleep and break Thunderbolt and reboot, I lose the USBX properties in EC. Only a power drain can fix that.

Hope it helps!
 
@CaseySJ, I've got a few clues to add to the pile for the sleep problem with Patched-Firmware-Thunderbolt setups.

Earlier today I fixed a USB Power issue where it would sporadically not load the USBX properties under EC. Sometimes they were there, sometimes they weren't. I found that it was due to them loading from SSDT-USBX.aml and USBPorts.kext. I removed the properties from the kext and that solved it.

After doing a few ThunderboltROM and SSDT test (attempted to patch SSDT-6.aml...whomp) I noticed that when I attempt sleep and break Thunderbolt and reboot, I lose the USBX properties in EC. Only a power drain can fix that.

Hope it helps!
I see what you mean:
  • USB power properties are not showing under EC after flashing Thunderbolt firmware.
  • However, SSDT-USBX is still injecting them, and high current devices such as my 2018 iPad Pro 11-inch are still connecting and charging. It's receiving all the power it needs from the USB-C port on the front of my computer case.
  • Moreover, using a USB-3 rated USB-C cable we can see that it's actually connecting at 10 Gbps. Only iPad Pros connect at that speed.
Screen Shot 2020-05-09 at 3.37.54 PM.png

Screen Shot 2020-05-09 at 3.35.53 PM.png
 
I see what you mean:
  • USB power properties are not showing under EC after flashing Thunderbolt firmware.
  • However, SSDT-USBX is still injecting them, and high current devices such as my 2018 iPad Pro 11-inch are still connecting and charging. It's receiving all the power it needs from the USB-C port on the front of my computer case.
  • Moreover, using a USB-3 rated USB-C cable we can see that it's actually connecting at 10 Gbps. Only iPad Pros connect at that speed.
View attachment 468496

View attachment 468495
Can you look under the EC sub device AppleBusPowerController in IOReg and see if they load there?

To elaborate, they are loading there (AppleBusPowerController) except when I break TB via sleep attempts.
 
Can you look under the EC sub device AppleBusPowerController in IOReg and see if they load there?

To elaborate, they are loading there (AppleBusPowerController) except when I break TB via sleep attempts.
As you can see in the first screenshot of previous post, AppleBusPowerController is missing, but bus power properties seem to be in effect.
 
As you can see in the first screenshot of previous post, AppleBusPowerController is missing, but bus power properties seem to be in effect.

Whoops! I assumed it was how you searched for EC or you were filtered.

Interesting nonetheless!
 
Back
Top