That’s the problem - even though visible to Thunderbolt Control Center, and approved in it, the drive does not show up in Device Manager. There’s power to the drive (its light comes on, and it gets warm).
There doesn’t seem to be an option in Tb Control Center to set a low security mode - just “Always Connect” or “Connect Only Once” - I’ve tried both, to no avail.
If I boot up the computer with the Samsung X5 plugged into the Thunderbolt card, it doesn’t appear in Tb Control Center; but as soon as I take it out and plug it in again with the machine running, it does show up in Tb Control Center. But it still doesn’t show up as a disk in Device Manager.
I’m wondering if the lack of Thunderbolt configuration in the BIOS means that although there is a a Thunderbolt header on the motherboard, I’d need to treat the setup as though there wasn’t, and jumper pins 3 to 5 on the cable. I found a post from FurryJackman elsewhere on this board at
that said
"Yes, it is necessary to jumper the card on a unsupported motherboard without the header.
"However, on motherboards with the header, it only works in SPECIFIC slots because the PCH has to communicate with the controller to have it power on when a device is connected. With no devices connected, the default is to keep it powered down. Without BIOS configuration on unsupported boards, this means it’s impossible to wake the controller.
"To change settings on the controller itself, you need a fully supported board to change settings and ASUS Prime Intel boards are pretty much the go to for that.
“If you lack config settings in your UEFI, you may as well jumper your Titan Ridge controller rather than use the official header. The official header is to write configuration settings to the controller and to power on the controller on demand. If your UEFI can’t configure the controller, jumpering after configuring on an official board is better than using the official header.”
But then I have also seen stuff about needing to flash back to NVM 23 - my setup is using NVM50. And I have no idea whether the drivers from the Gigabyte website are DCH drivers that people tell you to avoid, or not…
So before I start trying to jumper cables, or flash the firmware back to NVM23, I thought I should seek the advice of people who know what they are doing, since I don’t here!