Bug 1996403
Summary: | fwupdtool cannot updated firmware on Lenovo x390 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | fedoraproject.org |
Component: | fwupd | Assignee: | Richard Hughes <rhughes> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 34 | CC: | cody6730, rhughes |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-12-20 14:18:28 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
fedoraproject.org
2021-08-22 16:49:07 UTC
I am having this same problem. Occasionally, upon rebooting, the GRUB menu will be displayed, but the system will boot without applying the update. Manually selecting "Linux firmware updater" yields the same result. Additional clarification: I am not running this on an x390. I am using a ThinkPad X1 Extreme 2nd Edition. After disabling secure boot, the system updates normally. Could this be a bug in shim? https://github.com/rhboot/shim/pull/379 I can confirm that disabling Secure Boot and trying the update afterwards worked (Thanks to cody6730 for finding that out). However, I am not quite sure what the exact sequence was, because I had two different "reboot experiences". The first one showed a rotating progress indicator (The | / - \ sequence within the red background of the Lenovo logo and the rebooted without any further upgrade. Another "fwupdtool update" then proceeded with the actual update and finished it successfully - the system is not up-to-date according to "fwupdtool get-updates". Note to future readers: Enabling Secure Boot afterwards again is definitely a good idea. Important correction to my last comment: It should read "the system is now(!) up-to-date"the I'll close this as I think we're good with the latest set of updates. |