Framework Laptop 12 Intel® Core™ 13th Gen BIOS 3.05 Release BETA -Held

A note for Bazzite (and presumably other Universal Blue images) users, and for @Quin_Chou:

TL;DR:

  • ujust update saw the new firmware but did not apply it. Manual update with fwupdmgr update worked.
  • It’s easy to miss the “Device requires AC power to be connected” error in ujust update.

The long version:

(note that I’m on a slightly modified version of bazzite-dx, but I doubt my changes or the -dx changes would affect this - maybe someone else with a “normal” Bazzite install can comment on whether they experience the same issues)

In my case at least, ujust update did not apply the update. It did show the available update in the “Firmware upgrades” section (same output as fwupdmgr get-updates), but did not apply it (even after a reboot). There was no error reported, and it said “Firmware upgrades: OK” in the summary at the end. That’s after enabling lvfs-testing of course (see first post), otherwise there’s just no update available as this is still in beta. I ran it again, same thing.

Running fwupdmgr update manually from the command line did successfully download and queue the update for installation at the next reboot, and the laptop is now on BIOS 3.05 (confirmed with ujust bios-info after rebooting).

Also: If you’re not on AC power (or presumably if the battery is at 100% and AC power is reported as “off” to fwupdmgr), there’s a message about that in the “Firmware upgrades” section but it scrolls by pretty fast as part of the whole ujust update process, and in the summary it still says “Firmware upgrades: OK”. So even if the update worked with ujust update, you could still easily miss the fact that it’s not being applied because of the AC status.

These 2 issues mean you can easily think you’re keeping your BIOS up to date along with everything else

(I’ll have a look at the ujust update “recipe”, but I’m no expert so expectations are low :slightly_smiling_face:)