Closed nafallo closed 6 years ago
nafallo@wendigo:~$ sudo ./force_dell_tbt 1 Failed to force device to 1 (ret -1)
XPS 9370 Thunderbolt Controller DeviceId: d1e526ddd80960172adb13f64007a8e36aa742c5 Guid: 4eeb9d07-a96c-56d6-92d3-4a23ee7a6e4a Plugin: thunderbolt Flags: internal|updatable|supported|reported Version: 23.00 Created: 2018-02-27 Modified: 2018-02-27 UpdateState: failed UpdateError: device version not updated on success
[Release] RemoteId: lvfs Version: 28.00 Checksum: SHA1(296e0680554b3208326468041fe810eaaa167644) TrustFlags: none CpuArchitecture: x86_64 AppstreamGlibVersion: 0.7.4 KernelVersion: 4.15.0-10-generic FwupdVersion: 1.0.5 GUsbVersion: 0.2.11 BootTime: 1519719852 ThunderboltNative: False
Can you please try to manually force it back on using the WMI interface? Details are here: https://github.com/torvalds/linux/tree/master/Documentation/admin-guide/thunderbolt.rst
Hi Mario,
LTNS! Yeah, I've done so and it haven't helped either. I still have no device coming up. I'm on up-to-date Ubuntu 18.04 as well, so kernel 4.15. I went as far as trying to mainline kernel 4.17.2 yesterday to no avail. Is there a way to go even lower level to force a new firmware on to the controller?
That's about as low as you can go from the OS perspective. I would contact support at this point and request HW to be swapped out. :/
FWIW this could easily be from a bad type-C cable without pull up resistors frying the TBT controller or something else like that too, it's not necessarily a FW update caused issue.
Hi,
I have a failed flash of the controller in my fwupdmgr history, and now I never the any new entries in /sys/bus/thunderbolt/devices. There's also a message in dmesg after the thunderbolt module have been loaded (which incur a full freeze of the system for a few seconds); thunderbolt 0000:05:00.0: failed to send driver ready to ICM
Busted NVM firmware? Is there a way to force a new binary on their somewhere lower-level?
Cheers, Nafallo