I have a Asus NUC 15 PRO and a QNAP QNA-UC10G1SF USB/TB4 10G SFP NIC.
I can get it up and running after a hot-plug and subsequent warm reboot, but it won't come up when already plugged in on a coldboot.
I have tried on the 6.8 kernel from Prox8 and the 6.14.8-2 kernel from Prox9.
My buddy CGPT and I have been digging for days, and have concluded that force_power is not exposed for the Thunderbolt NHI's, and that is really what would be needed to manually kick these awake.
The thing is that I installed Win11 to see if the problem persisted, but it had no problem bringing up the interface on a cold boot. So how is this achieved?
I have read about others' previous issues that were solved by setting the bios thunderbolt security to "legacy" (which this bios does not have).
But, it looks like it's not even getting to the security check level because "boltctl list" shows the device as authorized, but disconnected.
Barring ASUS modifying the Bios for more granular TB4 control, anyone have any ideas?
I can get it up and running after a hot-plug and subsequent warm reboot, but it won't come up when already plugged in on a coldboot.
I have tried on the 6.8 kernel from Prox8 and the 6.14.8-2 kernel from Prox9.
My buddy CGPT and I have been digging for days, and have concluded that force_power is not exposed for the Thunderbolt NHI's, and that is really what would be needed to manually kick these awake.
The thing is that I installed Win11 to see if the problem persisted, but it had no problem bringing up the interface on a cold boot. So how is this achieved?
I have read about others' previous issues that were solved by setting the bios thunderbolt security to "legacy" (which this bios does not have).
But, it looks like it's not even getting to the security check level because "boltctl list" shows the device as authorized, but disconnected.
Barring ASUS modifying the Bios for more granular TB4 control, anyone have any ideas?