[In progress] SSDT for Thunderbolt 3 Hotplug

[misterwiggles]

OMG: Update! I just went into IOReg to take a screen shot and share it here based on my last post. When I loaded IOReg and went to the TB3 RP21 location I suddenly saw a bunch of new entries that were never there before. See screenshot attached. BUT I HAD REMOVED ALL THE SSDT FILES FROM CLOVER as they hadn't worked! So I am running none of the SSDT files and now I appear to have array access to the disks. And IOReg is dynamically updating as I type this. I just formatted the two disks for HFS+ and they are on my desktop. Again, NO SSDT files! The ONLY change I made during one of my many reboots was to just change one Thunderbolt BIOS setting that I hadn't set before because I had read it didn't make any difference. I set the "Thunderbolt Boot" (or something close to that) option to "Boot Once" instead of "Disabled". Is it possible that this one change has resulted in my TB3 now working with no SSDT files? Don't know what to say.

 

[misterwiggles]

And why would Windows 10 see the array just fine without this BIOS change? I'm assuming it must be the BIOS change as I literally changed nothing else other than removing the SSDTs and rebooting. I just don't understand.

 

[joevt]

OMG: Update! I just went into IOReg to take a screen shot and share it here based on my last post. When I loaded IOReg and went to the TB3 RP21 location I suddenly saw a bunch of new entries that were never there before. See screenshot attached. BUT I HAD REMOVED ALL THE SSDT FILES FROM CLOVER as they hadn't worked! So I am running none of the SSDT files and now I appear to have array access to the disks. And IOReg is dynamically updating as I type this. I just formatted the two disks for HFS+ and they are on my desktop. Again, NO SSDT files! The ONLY change I made during one of my many reboots was to just change one Thunderbolt BIOS setting that I hadn't set before because I had read it didn't make any difference. I set the "Thunderbolt Boot" (or something close to that) option to "Boot Once" instead of "Disabled". Is it possible that this one change has resulted in my TB3 now working with no SSDT files? Don't know what to say.

You can't boot from a Thunderbolt device unless EFI sets up Thunderbolt to enumerate the devices and allocate resource for them. Setting "Boot Once" makes that happen in EFI, and they remain setup when macOS starts.

And why would Windows 10 see the array just fine without this BIOS change? I'm assuming it must be the BIOS change as I literally changed nothing else other than removing the SSDTs and rebooting. I just don't understand.

Windows 10 can setup and enumerate thunderbolt devices like EFI does for the "Boot Once" option.

The SSDTs are supposed to make macOS do what EFI and Windows does.

 

[LeleTuratti]

OMG: Update! I just went into IOReg to take a screen shot and share it here based on my last post. When I loaded IOReg and went to the TB3 RP21 location I suddenly saw a bunch of new entries that were never there before. See screenshot attached. BUT I HAD REMOVED ALL THE SSDT FILES FROM CLOVER as they hadn't worked! So I am running none of the SSDT files and now I appear to have array access to the disks. And IOReg is dynamically updating as I type this. I just formatted the two disks for HFS+ and they are on my desktop. Again, NO SSDT files! The ONLY change I made during one of my many reboots was to just change one Thunderbolt BIOS setting that I hadn't set before because I had read it didn't make any difference. I set the "Thunderbolt Boot" (or something close to that) option to "Boot Once" instead of "Disabled". Is it possible that this one change has resulted in my TB3 now working with no SSDT files? Don't know what to say.

Use the BIOS settings that I posted a few posts back. Then go to the "Power" section of your BIOS, and if you have the ERP active, disable it.
Now start MacOS, and add the SSDT V4, unplug and reconnect your TB Dock, if you have Arbitrary inject on Clover, remove them. Now restart your computer.
Is the TB Dock now recognized?

 

[misterwiggles]

You can't boot from a Thunderbolt device unless EFI sets up Thunderbolt to enumerate the devices and allocate resource for them. Setting "Boot Once" makes that happen in EFI, and they remain setup when macOS starts.

Windows 10 can setup and enumerate thunderbolt devices like EFI does for the "Boot Once" option.

The SSDTs are supposed to make macOS do what EFI and Windows does.

That set “Boot Once” ends up being a critical step is making this Titan Ridge card work at all. I never found that info in any of the searching and reading on getting TB3 working. Understandably, most of what I found was Alpine Ridge related and perhaps things work a bit differently with this BIOS F11 and the newer TR card.

Without that Boot Once BIOS setting none of the SSDTs in this thread, nor the newest ones provided by @LeleTuratti worked. So at this point I assume that I can just leave the BIOS setting and only use the SSDTs as part of trying to get hot plugging working? I rebooted several times with just the BIOS setting and the TB3 array was found every time.

 

[misterwiggles]

Use the BIOS settings that I posted a few posts back. Then go to the "Power" section of your BIOS, and if you have the ERP active, disable it.
Now start MacOS, and add the SSDT V4, unplug and reconnect your TB Dock, if you have Arbitrary inject on Clover, remove them. Now restart your computer.
Is the TB Dock now recognized?

I will try this. Just to be clear, I don’t have most of those TB BIOS settings in my F11 BIOS. I only up to the memory listings but none of the more detailed ones. My BIOS didn’t have the Boot Once setting as indicated by your BIOS settings and that change caused all this to work without the SSDTs. But now that I have my OWC array working, I’ll move on to debugging hot plugging using your instructions.

 

[Consigliere]

I use the F10 BIOS and the hotplug works perfectly with the SSDT of METHOD 2.

My point being that for Gaming 5 the next bios is even better since you can't even mess with the settings that broke yours and mine. I use the one being:

1. Optimized for Intel® 9th Gen Core™ Processors.

I thought you also tried that one out and didn't have any problems. For me the one before:

1. Update CPU microcode for upcoming CPU
2. Improve windows boot time

Didn't work for me... and eventually blew my alpine card because I couldn't keep my hands off the forbidden settings

 

[NorthAmTransAm]

Will this new Mac Mini with 8th gen intel help us at all with getting thunderbolt running a little more...natively?

 

[wonderfilm]

I've got a z170x ud5th (bios f22d) board with a 7700k processor. I've had thunderbolt without hotplug working for years. Looking through this thread, I'm not positive if my board would be one that I could achieve this with or not. Anyone with a similar setup have any thoughts? Thanks and apologies if I missed something obvious.

 

[comed78]

I've got a z170x ud5th (bios f22d) board with a 7700k processor. I've had thunderbolt without hotplug working for years. Looking through this thread, I'm not positive if my board would be one that I could achieve this with or not. Anyone with a similar setup have any thoughts? Thanks and apologies if I missed something obvious.

HI, WonderFilm
I have same mobo and bios ver.
I'm reading very carefuly read and trying method.
But Unfortunately I did not get a positive result.
@LeleTuratti 's ssdt-v2 is device tree and hotplug doing well, but wake after sleep all device detatched.
This is our mobo z170x-ud5 th's problem.