Fwupd fails for keyboard/numpad 0.31 update

Framework Laptop 16
,
1

When I run fwupdmgr update and try to update my keyboard firmware to 0.31, it fails. I believe the keyboard (and numpad) fails to reattach in program mode, so it never gets flashed. You can see the results here. It requires restarting the computer for the keyboard to reconnect.

The FW16 keyboard firmware support article recommends LVFS for updating the keyboard and numpad firmware. And the BIOS firmware support article recommends having the battery at 100% charge. (Actually, it recommends NOT having 100% charge, but I’m assuming that’s a typo: “LVFS may not update if the battery is 100% charged.”) I’ve done it several times with and without 100% battery, ending in fiasco.

References:

  1. Framework 16 Keyboard/Numpad Firmware Update Article
  2. Results of running sudo fwupdmgr refresh --force
  3. Results of running sudo fwupdmgr get-updates
  4. Results of running sudo fwupdmgr update for the keyboard
  5. Results of running sudo fwupdmgr update for the numpad

Photo Dec 07 2025, 1 33 57 PM
Photo Dec 07 2025, 1 33 57 PM1920×1440 348 KB

1 Like
2

BIOS version, OS, fwupdmgr version?

See github.com/FrameworkComputer/qmk_firmware/releases for minimum required BIOS version, minimum fwupdmgr version, and options to update manually (uf2 section).

All of your privatebin links say “Could not get document data: Document does not exist, has expired or has been deleted”.

3

I have the same issue. I was able to get the BIOS update to run by saying ‘no’ to the keyboard updates, however the keyboard updates still fail to restart the devices.

image
image894×662 80.7 KB

My fwupd is on 2.0.19-1. My BIOS is clearly updated because I now get the same warning on bootup as in your screenshot.

I can restart the keyboard by sliding the touchpad out and back, which is quicker then rebooting and having to skip past the annoying message that my keyboard firmware is out of date, but manually doing that while fwupdmgr is waiting for the restart does not improve the situation.

4

Did the manual process from the Github page and that seems to have worked.

5

I’ve spent a lot of time recently building custom firmware for my RGB keyboard. If you hold down both the left and right alt keys while putting in the track pad module (keyboard doesn’t receive power until the touchpad is in place), the keyboard will pop up as an external flash drive (it’s in bootloader mode). You can then drag the appropriate firmware *.uf2 file onto that drive, and it will automatically install the update and reboot the keyboard. You just gotta make sure you download the right uf2 file from Frameworks site.

Perhaps that’ll help someone here.

3 Likes
Keyboard firmware update doesn't work?
6

This helped me tremendously, thank you! For anyone else curious, from https://community.frame.work/t/number-pad-stopped-working/70247/4?u=michael_riettini

  • Hold down keys for 2 and 6 while installing the module. [for the numpad]
  • Hold down the key at (0,0) in the matrix “(usually the top left key or Escape)” while installing the module. I believe this is the Esc key on the number pad. [for the macropad]
2 Likes
7

I have same experience as OP. Is there anyway to determine what the existing keyboard/numpad firmware version is before going through the manual update recipe?

8

Not that I know of off the top of my head, but I imagine tools like fwupdmgr might be able to do that somehow.

9

Hi @Matt_Wilkie, this might help:

1 Like
10

perfect, thanks @Rob-i-di-bob . That also allowed me to confirm the manual update worked without having to do a power cycle.

1 Like
11

I used numpad 1 and 6 per the github release notes, Releases · FrameworkComputer/qmk_firmware · GitHub , but otherwise the same. Note the caution of doing only one keyboard at a time.