Hello
@passmore,
Welcome to the forum and glad you found us (somehow)! I've added a link to that guide in the
Quick Reference spoiler in Post 1.
View attachment 511974
It is recommended to "do the HackinDROM thing" in order to create a custom Thunderbolt DROM. Every DROM contains a unique ID (UID) that acts somewhat like an Ethernet MAC address to ensure that no two devices have the same address. In a home environment, a custom DROM is not strictly necessary, but still worth doing.
If you're already using a Thunderbolt SSDT and you're seeing
UPSB,
DSB0,
NHI0,
DSB2, etc. in your Thunderbolt device tree (IORegistryExplorer) then you're in good shape.
As for ways to make this thread more easily searchable and indexable, there is a good Search function at the very top right of the page. What ideas did you have in mind?
Hey Casey,
Thanks for the quick response there. I'm afraid it seems like I spoke too soon. The reality is that since following the steps in the guide, sometimes I boot that machine and have full thunderbolt with Bus and local node, sometimes it loads only in PCI, and sometimes thunderbolt doesn't work at all. It seems to be unrelated to anything I do in config.
Here's my OC>ACPI
And here's the config
I've flashed the custom bios you provided for this board and enabled the GPIO3 Force Power and ACPI Removal Object Support settings. I also tried setting 'TableSignature' to DSDT and also SSDT on the ACPI patches. Also tried an NVRAM reset.
I can provide IORegistry, but it changes depending on whether thunderbolt decides to work fully, partially or not at all on each particular bootup. Do you think the fact that I have pcie cards in the machine could be causing the issue? I have a firewire card and a UAD card in there.
EDIT: Here's what it looks like when the bus is working, looks like DSB1 & 2 & 4 are not in the tree.
EDIT 2: in spite of it being under DSB1, my thunderbolt focusrite interface shows up under thunderbolt in profiler (when it decides to work)
Is flashing the thunderbolt firmware a possibility on this board? I poured through this thread but couldn't find patched firmware for it and I'm not sure I know where to start with patching it myself. I do however have a flasher, so if there is suitable firmware that might be the best route.
Sorry - appreciate you're probably busy so only get back to me if you can!
Regarding publicising the info, i meant we could put together a website dedicated to enabling thunderbolt 3 on hacks with all the info you've discovered.
EDIT 3: I've realised that the DROM thing is already done in the SSDT i'm using which I got from your post on this thread here -
https://www.tonymacx86.com/threads/...erbolt-3-i7-9700k-amd-rx-580.267551/page-2083
EDIT 4: There is less randomness than I originally thought. Basically it seems that everything works perfectly until i try to change port on the back of the machine or cold boot. If i do either of these things, i loose thunderbolt and don't get it back until I
1. Kill AC power to both device and computer
2. Turn on device first, then computer
3. reboot the computer once - thunderbolt works in PCI
4. reboot the computer twice - thunderbolt works in thunderbolt bus.
Not sure if this is the best that can be achieved or if there is something else wrong at my end. I've always had trouble with thunderbolt on this machine if the order of power on is adjusted or the port is switched. If flashing the tbt chip with compatible patched firmware is an option I'm very open to trying that (and accept the risks yadda yadda). Alternatively if you think it's an opencore or SSDT issue I am all ears!