According to the Framework Laptop 16 BIOS and Driver Releases page for my machine, I’ll need at least fwupd 2.0.16 (the project repo lists 2.1.1 as the latest). I assume this is why fwupdmgr get-updates is telling me I don’t have any updates available, leaving me stuck on BIOS 3.07. Running sudo apt upgrade fwupd (following an apt update) tells me I’m on the latest version, 1.9.34-0ubuntu1~24.04.1.
I get real uneasy when it comes to anything BIOS-related, so I figured I’d check in here before I started throwing commands at walls — am I missing something obvious? It looks like there’s a Snap available for fwupd at 2.1.1; is that the way to go?
Regardless, I figured it might be worth raising as a potential addition to the BIOS update page(s), since running through the processes outlined there shows that I’m fully up-to-date, for all intents and purposes.
Which Linux distro are you using?
Ubuntu
Which release version?
24.04.4 LTS
Which kernel are you using?
6.17.0-14-generic
Which BIOS version are you using?
3.07
Which Framework Laptop 16 model are you using? (AMD Ryzen™ 7040 Series)
Ryzen™ 7 7840HS
Have you tried running fwupdmgr refresh to update the local metadata?
With and without --force and sudo, yeah:
Updating lvfs
Downloading… [********************************* ]
Successfully downloaded new metadata: 1 local device supported
But:
Devices with no available firmware updates:
• System Firmware
• WD BLACK SN850X 1000GB
• Laptop Webcam Module (2nd Gen)
• UEFI dbx
• USB2.1 Hub
Devices with the latest available firmware version:
• Fingerprint Sensor
No updates available
That’s very strange. It’s normal for it to take a bit to show up depending on what mirrors you connect to and such… but the update’s been out a while and should be available everywhere by now. Sorry, I don’t know much more that’ll be of help other than suggesting you try a manual update somehow by downloading the file directly (assuming that’s an option).
Alright. Freshly-thrown spaghetti is currently sliding down the wall, and the good news is that I’m now on 4.03. To do so, I removed fwupd (sudo apt remove fwupd) and installed the Snap version, which showed up at 2.11. Ran the steps as documented and ran into the following hitch (edited for formatting only):
$ sudo fwupdmgr update
---
Upgrade UEFI dbx from 20230501 to 20250902?
This updates the list of forbidden signatures (the "dbx") to the latest
release from Microsoft.
Some insecure versions of the IGEL bootloader were added, due to a security
vulnerability that allowed an attacker to bypass UEFI Secure Boot.
---
Perform operation? [Y|n]: y
Writing…
failed to write-firmware: failed to notify snapd of prepare: snapd request failed with status 400
Which… is fine, probably, I assume. Rebooted, BIOS installed without a hitch, and was presented with the “update the keyboard and numpad” firmware screen. Continued on to boot as usual (keyboard/numpad are working), opened up the Firmware Updater GUI, and “no devices found.”
So, assuming my tinkering means I now “own” firmware updates in a new and exciting way, I did the following:
$ sudo fwupdmgr refresh --force
Updating lvfs
Downloading… [ \ ]
Successfully downloaded new metadata:
• 11 devices are updatable
• 4 devices are supported in the enabled remotes (an update has been published)
$ fwupdmgr get-updates
Devices with no available firmware updates:
• WD BLACK SN850X 1000GB
• KEK CA
• Laptop Webcam Module (2nd Gen)
• Option ROM UEFI CA
• SBAT
• USB2.1 Hub
• Windows Production PCA
• frame.work-LaptopAMDDB
• frame.work-LaptopAMDKEK
Devices with the latest available firmware version:
• System Firmware
• Fingerprint Sensor
• UEFI CA
────────────────────────────────────────────────
Devices that were not updated correctly:
• UEFI dbx (20230501 → 20250902)
No sign of keyboard/numpad firmware anywhere. Running sudo fwupdmgr update just makes another attempt at Upgrade UEFI dbx from 20230501 to 20250902 (which fails).
With the caveat that everything is currently working, give or take an annoying early-boot error screen, should I roll everything back to non-Snap, apt-installed fwupd? Woof.
Alright. sudo apt install fwupd has returned me to 1.9.34. Not ideal, but did mean the Firmware Updater GUI would work again, though seemingly out-of-date — no sign of keyboard/numpad in there. I assume I’ll want to go back to the Snap version next time I feel like doing this particular dance.
Because it seems like I did this update out-of-order (no keyboard/numpad update was offered via fwupdmgr at any point), I followed the manual keyboard/numpad firmware installation steps, and I’m now booting up error-free and on 4.03. That UEFI dbx update never did install.
Hopefully this thread is of value to someone in the future.
I’m hopeful some of these repos will update along with the next LTS release expected to be finalized near the end of this month… possibly wishful thinking though.
