XPS 9370 Thunderbolt firmware gone missing #23
Comments
|
It looks like it got downgraded because of a failure report. I've promoted it back to testing, can you have a try? |
|
Thanks a lot, Mario, awesome to see you still at it after 10 years since UDS-L where we met :) It seems to work "as usual". After update and waiting at "Restarting device" I got: And then the Thunderbolt device was gone until reboot. After reboot however it's at 40.00 and functioning normally. This was also my experience with 28.00 -> 33.00, so I can understand there may be failure reports. Maybe with subpar update experience it's not wise to promote it to stable at least then, but after a reboot indeed it seems as fine as before. |
😎
What version of fwupd are you using that happened still? |
|
For what that's worth as I was trying to troubleshoot why my TB16 (w/ XPS 13 9370) disconnects USB devices all the time.. I found this issue and updated to 40.0 as well (from 28 - for some reason on windows i could never update properly, but with fwupdmgr no problem) After update ( Rebooting the dock and reconnecting it did not fix it, but rebooting the laptop worked and all devices are now visible/functional. Confirmed the laptop now runs version 40 and everything seems OK so far (unrelated to this issue: waiting to see if I still get USB disconnects ;-)
|
|
Well that's unfortunate to hear that TBT decided to take a hike even with brand new kernel and userland. Do you by chance have the kernel logs associated with your upgrade? If so, I think this needs a kernel bugzilla to figure out what is happening kernel side with the upgrade to prevent it from coming back. Please CC me (mario.limonciello@dell.com) |
|
Interesting bits are around |
|
I have to wonder if it was a timing thing that the ICM wasn't ready to boot yet. Can you please file the full dmesg to a bug on https://bugzilla.kernel.org/ ? |
sudo fwupdmgr --version I got the "failed to get device after update" after waiting several minutes when it seemed like it was just hanging, but eventually I got back to command prompt with that. The message was in the terminal output, not in any logs. (my unrelated issues I'm seeing if this could fix are 1) XPS 13 9370 only works well with 0.5m Belkin TB3 cable, while the 1.5m cable supplied with Asus PA27AC monitor works very flaky while the same cable works 100% on Latitude 7490, 2) USB devices attached to the monitor sometimes disappear, needing to detach/replug the cable, also something that only has happened on XPS 13) |
|
@superm1 as a side note, my usb issue wasn't solved by the fw update. I'm not sure if it's Dell TB16 dock issue, a TB controller issue, or a kernel issue. Is this something you'd want me to file somewhere here or elsewhere? (reloading kernel usb modules fixes it every time, there's no useful logs thought, a device just stop responding at random - sometimes mouse, sometimes keyboard, .. - until i replug them in or reload the module) |
|
After a month of use I have not seen regressions with 40.00. It may have improved may 2) unrelated issue since I don't now remember needing to do the detach/re-attach cycle for disappearing USB devices, although it was quite random also before, sometimes gone for a long time and then appearing many times in a shorter period. Meanwhile Mika seems to have posted a potential fix for the device gone problem in kernel. |
Even though I have previously updated my XPS 9370's firmware from 28.00 to 33.00, after #10 got fixed, there's no longer any firmware available at https://fwupd.org/lvfs/device/4eeb9d07-a96c-56d6-92d3-4a23ee7a6e4a
Furthermore, there would be 40.00 available at https://www.dell.com/support/home/fi/fi/fibsdt1/drivers/driversdetails?driverid=2670n&oscode=wt64a&productcode=xps-13-9370-laptop which might be something that would have really helped me since I've a few problems with my Thunderbolt monitor with XPS 9370 only.
The contents of the .exe file do not seem straight-forward enough to mimick the example from https://github.com/fwupd/fwupd/tree/master/contrib/firmware_packager either so I've been unable to find a solution so far.
The text was updated successfully, but these errors were encountered: