![]() Fixed MUP errors popped up with CVT2.0.1 The notification time has been extended to remain around 25 seconds at the minimum. Toast message on device connection changed to "New Thunderbolt™ device has been connected. ![]() ![]() Hotfix: Race condition between SW and FW while entering RTD3 and a device is connected at the same time (see fixed issue #2202117254) This document is the release notes for the Thunderbolt software version 17.4.77.400 Likewise, the pre-UWD Thunderbolt driver updates typically came with somewhat informative “Release Notes.txt” files: Thunderbolt(TM) Software Release Notes this from the file of the Asus ThunderboltEX 3 TbtFwUpdate_1.0.0.15_release Looking in the files of Thunderbolt firmware upgrades, you can sometimes see hardware distinctions referenced, e.g. I don’t know if SUBSYS and REV offer any good info through. Will give some additional PCI details, like this identifier for the Asus ThunderboltEX 3 in my current system: Get-PnpDevice -Class 'System' -FriendlyName 'Thunderbolt*' |fl These model numbers are unfortunately “just” the general devices’ identifiers, there can be several hardware revisions of the 15EB for Titan Ridge Thunderbolt 3, for example something like 15EB.1, 15EB.2 or 15EB.3 - but no way for a customer to see these details. I always wondered if maybe all the hidden Thunderbolt answers are hidden behind the login of the Thunderbolt Developers section. I had no luck, of course, and the worst was the official Intel online support forum washing their hands of any Thunderbolt support, and just pawning me off to the OEM (who stonewalled me.) My eye is twitching, and I’m having flashbacks to the Dell I had which had a Thunderbolt 3 port that didn’t work with the Apple TB3-TB2 Adapter – even though my Intel NUC6i7KYK and Asus ThunderboltEX 3 worked fine with it.ĭell enterprise support merely said, “sorry, it isn’t compatible” – and I spent endless hours searching for firmware updates, release notes, or any sort of insight into what the actual hardware problem was that made Thunderbolt® hardware incompatible with Thunderbolt® hardware. If I’m not mistaken Hector Martin’s (Marcan) work on his Asahi Linux and hypervisor project shows that the issue is lack of drivers and not PCI-E capabilities like some people theorized. I need to test with the SATA and PCI-E cards to confirm but I see no reason proper Thunderbolt is not working considering the device tree: Thunderbolt/USB4 Bus 0: You are right the ethernet is under the USB hub that is connected to the thunderbolt 3 system. Will test that as soon as the GC-Maple Ridge AICs become available in Germany.
0 Comments
Leave a Reply. |