-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thunderbolt 4 Dock upgrade fails with "SPI state is busy [0x08]" after 15 mins #431
Comments
From a suggestion at [1], I was able to workaround this by updating 10.11 -> 10.13 -> 10.16. It'd be nice if fwupd could consider this constraint on updates, or at least present a release note to the user. |
I've asked Lenovo to add the requirement of >=10.13 on the 10.16 firmware -- which will force fwupd to do it in two steps. |
I'm experiencing this exact problem when trying to update my dock on a t14 gen 5 with amd from 10.16 to 10.18. |
I have the same issue even if I'm trying to upgrade "failed to wait for erase: failed after 30 retries: SPI state is busy [0x08]" I'm on a Lenovo Thinkpad Z16 |
We're unable to update from 10.16 to 10.18 with fwupd 1.9.24 on Ubuntu 24.04 on a Thinkpad P14s with this exact error. |
Unable to update from 10.16 to 10.18 with fwupd-1.9.27 on Fedora 41 on a ThinkPad P16v with this same error. |
I currently have the exact same problem with an E16 Gen2 (Intel, 21MA) and my ("new" , refurbished) 40B0 TB4 dock currently running 10.17 firmware version. Same issue when using my E16 Gen1 (AMD, 21JT). Occurs even with the newest version of fwupd (2.03) Kernel in use is 6.11.0-13-generic |
Same error trying to upgrade 10.15 -> 10.16 on a P16s, fwupd 1.9.27 and kernel 6.12.7. |
I have also seen the error twice: fwupd: 1.9.27 |
I'm trying to update a ThinkPad Thunderbolt 4 Dock using a Z16 Gen1 running fwupd 1.19.14 from Debian trixie.
It tries for 15 mins, but eventually times out. This happened twice in row, with me powering off the dock and laptop in between.
The text was updated successfully, but these errors were encountered: