Skip to content
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

fwupd update not working #3168

Closed
robertek opened this issue Nov 11, 2024 · 3 comments
Closed

fwupd update not working #3168

robertek opened this issue Nov 11, 2024 · 3 comments

Comments

@robertek
Copy link
Contributor

Fwupdmgr is not able to update the firmware due to have efi runtime in /usr/libexec.

This is somehow a duplicate of #3072. But I would like to create this as a new bug, since it has a real consequence until fixed.

❯ fwupdmgr update     
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade Intel Management Engine from 192.81.1753 to 192.95.2489?             ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ Intel formal release MEFW for WHL platform Consumer and Corporate            ║
║                                                                              ║
║ 20NQS43F0N must remain plugged into a power source for the duration of the   ║
║ update to avoid damage.                                                      ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: 
Waiting…                 [***************************************]
failed to wait for prepare replug: /usr/lib/fwupd/efi/fwupdx64.efi and /usr/lib/fwupd/efi/fwupdx64.efi.signed cannot be found

When the /usr/libexec/fwupd/efi/fwupdx64.efi is copied to /usr/lib/fwupd/efi/fwupdx64.efi it starts working.

@nekopsykose
Copy link
Contributor

nekopsykose commented Nov 11, 2024

yea, probably fixed with 838330f

@robertek
Copy link
Contributor Author

Ahh, sorry haven't noticed the latest update. I have upgraded to revision r3 and can confirm it is fixed. Thanks.

@nekopsykose
Copy link
Contributor

it was a bugfix for this issue, didn't exist before you opened it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants