[In progress] SSDT for Thunderbolt 3 Hotplug

[LeleTuratti]

Sorry for the absence, I do not have much time as before now.

I would like to specify one thing: This is not a guide! But a starting point to solve a problem.

I performed a clean new installation and I took advantage of it to extract some information.
The solution to enable the hotplug for everyone is probably hidden here.

With the clean system I have inserted ONLY these minimal Arbitrary inject (First TB entry):

None SSDT!! Only Arbitrary!! In this way the values are the original ones and a comparison is possible.

And I saved these IORegs of my system:

1. GC-Alpine Ridge with THB_C cable connected an device connected [NO hotplug]: IOReg GC-AplineRidge with THB_C cable.zip
   
2. GC-Alpine Ridge without THB_C cable and without device connected: IOReg GC-AplineRidge without THB_C cable and device.zip
   
3. GC-Alpine Ridge without THB_C cable and with device connected [FULL hotplug]: IOReg GC-AplineRidge without THB_C cable - with device.zip

The THB_C cable helps the PCI card to be recognized by the system at boot, but it breaks the hotplug. Why? What values changes? I think it's the same for everyone, even on integrated cards, but here you can see the differences.
Now, find the differences and we will find the solution to this problem for everyone (most likely).

For now I have "solved" my problem with method 2 of post #1, but I hope that soon there are new developments!

 

[sumbutrule]

found this info, may help?
https://developer.apple.com/library...1.html#//apple_ref/doc/uid/TP40011138-CH5-SW1

 

[zipb]

Interesting. But requires a lot of knowledge about (OSX) drivers in general. Nice for specialists, which I am not.

 

[nmano]

Hi All
If anyone work sleep with TB3 please share your experience.
I try more restart wake up.
Thank you.

 

[Consigliere]

Sorry for the absence, I do not have much time as before now.

I would like to specify one thing: This is not a guide! But a starting point to solve a problem.

I performed a clean new installation and I took advantage of it to extract some information.
The solution to enable the hotplug for everyone is probably hidden here.

With the clean system I have inserted ONLY these minimal Arbitrary inject (First TB entry):
View attachment 329209
None SSDT!! Only Arbitrary!! In this way the values are the original ones and a comparison is possible.

And I saved these IORegs of my system:

1. GC-Alpine Ridge with THB_C cable connected an device connected [NO hotplug]: IOReg GC-AplineRidge with THB_C cable.zip
   
2. GC-Alpine Ridge without THB_C cable and without device connected: IOReg GC-AplineRidge without THB_C cable and device.zip
   
3. GC-Alpine Ridge without THB_C cable and with device connected [FULL hotplug]: IOReg GC-AplineRidge without THB_C cable - with device.zip

The THB_C cable helps the PCI card to be recognized by the system at boot, but it breaks the hotplug. Why? What values changes? I think it's the same for everyone, even on integrated cards, but here you can see the differences.
Now, find the differences and we will find the solution to this problem for everyone (most likely).

For now I have "solved" my problem with method 2 of post #1, but I hope that soon there are new developments!

Too bad for us that you have less time now. Hopefully someone else will take the torch for a while.
1. Can you just tell us your bios settings. Especially those regarding Thunderbolt.
2. When you say Method 2 and Hotplug... Do you mean that you are able to boot with your dock connected and after boot turn on your soundcards and they will be recognised?

Best Regards
Anders

 

[zipb]

I had sleep working at some point (builtin tb3), but lost USB-3 speeds/had other weird behaviour.

 

[LeleTuratti]

2. When you say Method 2 and Hotplug... Do you mean that you are able to boot with your dock connected and after boot turn on your soundcards and they will be recognised?

Exactly, it is explained in post #1 how to succeed.

The bios settings are basically the same for TB:

• Peripherals > Intel Thunderbolt Technology: Enable
• > Thunderbolt(TM) Support: Enable
• > Thunderbolt Boot Support: Enable
• > GPIO3 Force PWR: Enable
• > Skip PCI OptionRom: Disable
• > Security Level: No Security
• Power > ERP: Enable (for sleep/wake and shutdown)

I attach my config.plist. Check that you have selected: Darkwake=8

Usually shutdown and sleep/wake problems are caused by USB ports, check the "Wake Reason" log using a terminal command.

 

[nmano]

Exactly, it is explained in post #1 how to succeed.

The bios settings are basically the same for TB:

• Peripherals > Intel Thunderbolt Technology: Enable
• > Thunderbolt(TM) Support: Enable
• > Thunderbolt Boot Support: Enable
• > GPIO3 Force PWR: Enable
• > Skip PCI OptionRom: Disable
• > Security Level: No Security
• Power > ERP: Enable (for sleep/wake and shutdown)

I attach my config.plist. Check that you have selected: Darkwake=8

Usually shutdown and sleep/wake problems are caused by USB ports, check the "Wake Reason" log using a terminal command.

Thank you for update
Are you using any other DSDT/SSDT patches for sleep?

 

[LeleTuratti]

Thank you for update
Are you using any other DSDT/SSDT patches for sleep?

My TB devices are correctly recognized after sleep, but this happened right from the beginning without any procedure. It is not said that it works for everyone.
If your build does not go correctly in sleep the problem is another (perhaps caused by USB ports, in fact I do not use any patches for USB ports because I created my SSDT for USBInjectAll).

 

[nmano]

X99-UIAC-All.aml This SSDT supported both Conroller.

#Intel 99 Series Chipset Family USB xHC Host Controller

#USB-C Host Controller(Gigabyte Alpine ridge)

#You have to rename this 2 devies are same name to XHC .

#Install USBInjectAll.kext