I am using Hp Laptop 15 with Amd Ryzen 3 3300u and using fedora 42 (faced this in fedora 41). There is an firmware update and whenever I tap on update, the device restarts and the notification comes of update installed but when I open software manager, the update does not get installed and stays there as before. I tried fwupdmgr and gnome firmware update but nothing worked out for me
As a workaround, can you apply the firmware update by some other means (e.g. fwupdmgr)?
Not working
Another option might be to go directly to your manufacturer’s website and download the latest BIOS update from there. They might have a bootable image of some sort that you can use to install it, or an EFI executable, or maybe even something that would run directly under Linux. (More often I’ve seen programs that can be run under something like FreeDOS.)
I just tried the commands as detailed here and it worked on one of my computers:
[root@localhost ~]# fwupdmgr get-devices
Dell Inc. OptiPlex 5070
...
│
├─PC601 NVMe SK hynix 512GB:
...
│
└─UEFI dbx:
Device ID: 362301da643102b9f38477387e2193e57abaa590
Summary: UEFI revocation database
Current version: 20160809
Minimum Version: 20160809
Vendor: UEFI:Microsoft
Install Duration: 1 second
GUIDs: 4a6cd2cb-8741-5257-9d1f-89a275dacca7 ← UEFI\CRT_E28D59CA489BD2AD580F2EA5D62D6A29BB9C02AE5A818434A37DA7FC11DFF9E9&ARCH_X64
f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
Device Flags: • Internal device
• Updatable
• Needs a reboot after installation
• Device is usable for the duration of the update
• Only version upgrades are allowed
• Signed Payload
[root@localhost ~]# fwupdmgr enable-remote lvfs
╔══════════════════════════════════════════════════════════════════════════════╗
║ Enable new remote? ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ The LVFS is a free service that operates as an independent legal ║
║ entity and has no connection with Fedora Linux. Your ║
║ distributor may not have verified any of the firmware updates for ║
║ compatibility with your system or connected devices. All firmware ║
║ is provided only by the original equipment manufacturer. ║
║ ║
║ Enabling this functionality is done at your own risk, which means ║
║ you have to contact your original equipment manufacturer ║
║ regarding any problems caused by these updates. Only ║
║ problems with the update process itself should be filed at ║
║ https://bugzilla.redhat.com/. ║
╚══════════════════════════════════════════════════════════════════════════════╝
Agree and enable the remote? [Y|n]: y
Authenticating… [ - ]
Do you want to refresh this remote now? (Requires internet connection) [Y|n]: y
Downloading… [***************************************]
Successfully enabled and refreshed remote
[root@localhost ~]# fwupdmgr refresh
Metadata is up to date; use --force to refresh again.
[root@localhost ~]# fwupdmgr update
Devices with no available firmware updates:
• TPM
• UEFI Device Firmware
Devices with the latest available firmware version:
• PC601 NVMe SK hynix 512GB
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade UEFI dbx from 20160809 to 20241101? ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ This updates the list of forbidden signatures (the "dbx") to the latest ║
║ release from Microsoft. ║
║ ║
║ An insecure version of Howyar's SysReturn software was added, due to a ║
║ security vulnerability that allowed an attacker to bypass UEFI Secure Boot. ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: y
Waiting… [***************************************]
Successfully installed firmware
An update requires a reboot to complete. Restart now? [y|N]: n
[root@localhost ~]#
Where does the above procedure fail for you and what is the error message?
I just checked and there is an bios update which I somehow missed. It’s in .exe format so how do I flash it?
Does it say it will run under DOS? If so, you might be able to make a FreeDOS boot drive: The FreeDOS Project
I followed all your steps but the problem even after rebooting the system the system is still on that previous firmware version
Ah, so the update did work. It is just cached somehow and you cannot clear the cache. I’m not sure where all the update caches are for the different update utilities. I normally use dnf and its cache can be cleaned with sudo dnf clean all. You might try that.
Naa nothing was mentioned in the website about this
Cleaned now what sir?
See if the update utility still sees the update is needed. I’m not sure if your update utility would use the same cache as dnf what is the name of the GUI update software you are using?
I am updating it through the terminal
Oh. Then dnf clean all should have worked to clear the update cache.
But I didn’t think dnf detected firmware updates. I thought that was a gnome-software or discover thing.
I didn’t get that warning about “no reports require uploading”. It might just be a bug in your system’s firmware. That BIOS update you found might fix it, if you can figure out how to apply it.
I think I have to switch to windows apply the bios update and then switch back to fedora
Thank u very much sir for your assistance
Yes, if you have a dual-boot system, that should work.
Otherwise, there might be a workaround here: Lenovo T480s - ME Firmware upgrade loop · Issue #70 · fwupd/firmware-lenovo · GitHub
1 Like