- Sep 1, 2018
- Asus Prime Z370-A
- GTX 1050 Ti
Well, this sounds like voodoo to me, with all due respect. (BTW: OS is set to "Other", USB is "Enabled", as many other threads suggest this, but I will try without it, for sure...)I’d make sure you unplug for 30 seconds, boot OS, turn on Apollo, restart.
If nothing then see if turning off “Enable USB” in your bios under thunderbolt.
Also make sure you’ve got your OS set to other in bios for thunderbolt.
Just try one setting at a time and take your time.
In Windows I can hotplug, switch the device on/off, all works properly, there is no need for such convoluted procedures. This means that the hardware is capable of executing this as intended.
In OSX the IORegistryExplorer application sees the controller, the Thunderbolt and the USB3.0 port as well on the hardware, but there is no further action from the OS when the attached Thunderbolt device is turned on or off (or it is on when the machine boots). So to me this is a software issue, that should be possible to resolve by telling OSX what to do.
So I am looking for ideas how to tell the OS to see the same what the IOReg can see, so it can load the proper Thunderbolt kext(s) and configure what needs to be configured so the system reacts to IO changes on this port (like plugging in, switching on/off, etc.).