Thunderbolt 3 Modified Firmware Custom SSDT Discussion

[athedog11]

On X99 systems it is very likely that there are 2 default devices under RP01. You've identified and removed one of them (D074), but if you look at the system DSDT, you might find a second one. That, too, needs to be removed.

On my Asus X99 Deluxe II, for example, we have to remove:

• D07C
• H000

Lines 30-38 show how this is done.

View attachment 454159

Thanks to you both NorthAmTransAm and CaseySJ for your advise.

I tried the ssdt posted from NorthAmTransAm with my values but no dice.

Regarding CaseySJ's comment about removing the devices.
My system DSDT show here only the 1 device D074 but for the other pcibridge it shows nothing.



This is what the acpi path looks like in windows device manager if helpful.

Would I need to assign a name to the 2nd pci bridge so that it can be removed?

Thanks!

 

[mm2margaret]

So, @scottkendall et al:

I've been following this thread and the conversation in @CaseySJ's thread on Thunderbolt 3.

I have a Asus Sage (non-10g) motherboard with a Titan Ridge card, and everything works for TB3, cold plug, hot plug, USB, etc. It works in ICM mode (basically Windows mode).

I also have an Asus Z370 with an Alpine Ridge card, which I haven't worked on much.

My question is this: on the Titan Ridge card on my Asus Sage, I have all cables connected per Gigabyte's recommendation. Same for the Alpine Ridge on the Z370.

But you have said that the "..TB HDR cable causes thunderbolt to not function..". I don't understand that, because my Titan Ridge works well, and I'm pretty sure I have the TB HDR cable connected.

Also, you said that "....3 – 5 Jumper for force power...". Can you explain that in a bit more detail?

I have a custom modded TB SSDT and tbtforcepower.efi, and in my bios I have Boot TB devices turned on, and yes, I can boot from TB devices (on the Sage with the Titan Ridge).

So, these two issues are confusing me. Sorry to ask, but can you give some explanation to these? Or just some referrals to where these are explained? That might be easier to do......

 

[CaseySJ]

Thanks to you both NorthAmTransAm and CaseySJ for your advise.

I tried the ssdt posted from NorthAmTransAm with my values but no dice.

Regarding CaseySJ's comment about removing the devices.
My system DSDT show here only the 1 device D074 but for the other pcibridge it shows nothing.

View attachment 454188

This is what the acpi path looks like in windows device manager if helpful.

View attachment 454189

Would I need to assign a name to the 2nd pci bridge so that it can be removed?

Thanks!

In that case you might be missing SSDT-DTPG.aml. If so, just copy the attached file into CLOVER/ACPI/patched and reboot.

 

[CaseySJ]

So, @scottkendall et al:
...
My question is this: on the Titan Ridge card on my Asus Sage, I have all cables connected per Gigabyte's recommendation. Same for the Alpine Ridge on the Z370.

If both the Asus Sage and Asus Z370 motherboards contain a 5-pin THB_C Thunderbolt header and that header is connected to the add-in-card, then that is, in my view, the ideal situation.

But you have said that the "..TB HDR cable causes thunderbolt to not function..". I don't understand that, because my Titan Ridge works well, and I'm pretty sure I have the TB HDR cable connected.

On my Asus X99 Deluxe II there is a THB_C Thunderbolt header and I have it connected to a flashed GC-Titan Ridge. Result: It works very well. Not perfect, but close.

Also, you said that "....3 – 5 Jumper for force power;...". Can you explain that?

If the motherboard lacks a THB_C header then the Thunderbolt add-in-card will most likely not power on in macOS. By connecting pins 3 and 5 of the J1 Header on the add-in-card, we can force power on.

 

[mm2margaret]

If both the Asus Sage and Asus Z370 motherboards contain a 5-pin THB_C Thunderbolt header and that header is connected to the add-in-card, then that is, in my view, the ideal situation.

On my Asus X99 Deluxe II there is a THB_C Thunderbolt header and I have it connected to a flashed GC-Titan Ridge. Result: It works very well. Not perfect, but close.

If the motherboard lacks a THB_C header then the Thunderbolt add-in-card will most likely not power on in macOS. By connecting pins 3 and 5 of the J1 Header on the add-in-card, we can force power on.

Thanks!

 

[NorthAmTransAm]

@CaseySJ, can you think of any reason why I can't get anything at all to load under DSB2? Also thanks for your input on the thread!

UPDATE
It's firmware related.

 

[CaseySJ]

@CaseySJ, can you think of any reason why I can't get anything at all to load under DSB2? Also thanks for your input on the thread!

DSB2.RHUB.XHC2 will only power up if a USB-C device is connected during boot. This is, I believe, one of the issues that @maleorderbride is trying to resolve. Please see his post here:

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

@CaseySJ Ok, I got my head around the patching! If Asus is kind enough to email me the firmware for the cards (v18 and v16) then I now know what to try after looking at what Osy did in his/her versions against the Mac firmwares. In case you ever need to look through those firmwares I still have...

www.tonymacx86.com

 

[athedog11]

In that case you might be missing SSDT-DTPG.aml. If so, just copy the attached file into CLOVER/ACPI/patched and reboot.

Thanks. Unfortunately that did not change anything in IO reg.

With this SSDT (I can't remember where from)
Honestly, I'm slowly learning more about editing SSDTs and this was me seeing what would happen if I took a piece from 2 separate ssdts.

The path manages to show up in IO reg but no hotplug as well as DSB1, DSB2 ect showing as "pcibridge"

 

[CaseySJ]

Thanks. Unfortunately that did not change anything in IO reg.

With this SSDT (I can't remember where from)
Honestly, I'm slowly learning more about editing SSDTs and this was me seeing what would happen if I took a piece from 2 separate ssdts.

The path manages to show up in IO reg but no hotplug as well as DSB1, DSB2 ect showing as "pcibridge"

View attachment 454207

• SSDT-10-TbtOnPch IO SHOWS.aml has a number of problems. Please remove it for now.
• Then copy attached SSDT-TBOLT3-RP01.aml to the CLOVER/ACPI/patched folder.
• Confirm that SSDT-DTPG.aml is still present in CLOVER/ACPI/patched.
• Reboot.

 

[scottkendall]

So, @scottkendall et al:

I've been following this thread and the conversation in @CaseySJ's thread on Thunderbolt 3.

I have a Asus Sage (non-10g) motherboard with a Titan Ridge card, and everything works for TB3, cold plug, hot plug, USB, etc. It works in ICM mode (basically Windows mode).

We are not using ICM mode and I could never get hot plug or my egpu it to work with or without cables or tbtforcepower or other wise in ICM mode.

I also have an Asus Z370 with an Alpine Ridge card, which I haven't worked on much.

My question is this: on the Titan Ridge card on my Asus Sage, I have all cables connected per Gigabyte's recommendation. Same for the Alpine Ridge on the Z370.

But you have said that the "..TB HDR cable causes thunderbolt to not function..". I don't understand that, because my Titan Ridge works well, and I'm pretty sure I have the TB HDR cable connected.

Also, you said that "....3 – 5 Jumper for force power...". Can you explain that in a bit more detail?

Pretty much the same thing as above we are using a modified firmware not ICM mode. For me and this maybe different for someone else on a z370/90 board but when I connect the header to the board I get not functioning TB3. When I put the jump on 3-5 pin it seems to work.

IF it is working for you in ICM mode great don't mess with it but for me that was not the case. Cold plug always worked with or without SSDT for me but Hotplug never worked right, USB did not work at all, and sleep would crash my system.

Now I have a working alpine ridge with both ports Hotplug, USB and it all works after it wakes from sleep.