So I’ve held off on upgrading the firmware for a few days. Just to make sure I was not going to be the first who notices a problem 
But now that I’m ready, the option is gone on pop_os?
❯ sudo fwupdmgr update
[sudo] password for mark:
No updatable devices
When I tried this last week, I got a whole bit of text explaining the upgrade with a yes / no
I even did it multiple times, to reread the text. But today “No updatable devices” ?
Was the firmware pulled or something?
Did you enable lvfs-testing repo?
Yep:
❯ fwupdmgr enable-remote lvfs-testing
╔══════════════════════════════════════════════════════════════════════════════╗
║ Enable new remote? ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ The LVFS is a free service that operates as an independent legal entity and ║
║ has no connection with Pop!_OS. 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. ║
║ ║
║ This remote contains firmware which is not embargoed, but is still being ║
║ tested by the hardware vendor. You should ensure you have a way to manually ║
║ downgrade the firmware if the firmware update fails. ║
║ ║
║ 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://github.com/pop-os/pop/issues. ║
╚══════════════════════════════════════════════════════════════════════════════╝
Agree and enable the remote? [Y|n]: y
Authenticating… [ \ ]
Do you want to refresh this remote now? (Requires internet connection) [Y|n]: y
Downloading… [***************************************]
Downloading… [***************************************]
Downloading… [***************************************]
Successfully enabled and refreshed remote
❯ sudo fwupdmgr update
[sudo] password for mark:
No updatable devices
Isn’t it super weird?
What is your Framework generation, 11 gen or 12 gen? What is the version of the current BIOS (the result of the sudo dmidecode -s bios-version)?
It’s the 11th gen
❯ sudo dmidecode -s bios-version
[sudo] password for mark:
03.10
And p.: Today the option has returned:
❯ sudo fwupdmgr update
Devices with no available firmware updates:
• UEFI Device Firmware
• UEFI Device Firmware
• WDS100T1X0E-00AFY0
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade System Firmware from 0.0.3.16 to 0.0.3.17? ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ Due to an incompatibility between our BIOS and recent versions of fwupdmgr ║
║ please set DisableCapsuleUpdateOnDisk=true in /etc/fwupd/uefi_capsule.conf ║
║ before applying this update. ║
║ ║
║ Updating the BIOS firmware will erase NVRAM boot variables. Press F3 during ║
║ boot to manually select a desired boot entry after the update has completed ║
║ if you run into this issue. ║
║ ║
║ Changes in this release ║
║ ║
║ • Add setup menu option in advanced tab to enable standalone operation ║
║ mode. This will modify onboard LED behavior to skip presence checks for ║
║ chassis open, display, battery and C cover. ║
║ • Change low battery power LED behavior from red to white. ║
║ ║
║ Fixes in this release ║
║ ║
║ • Improve battery life when HDMI/DP expansion cards are attached but no ║
║ display is connected. ║
║ • Add support for Capsule on Disk for future updates to improve LVFS ║
║ compatibility. ║
║ • Fix pressing F12 key during boot will system hang when BIOS quiet boot ║
║ is disabled. ║
║ • Correct BIOS setup item TPM availability missing word. ║
║ ║
║ Laptop must remain plugged into a power source for the duration of the ║
║ update to avoid damage. ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]:
Without me doing anything. So it must have been either pop_os or lvfs I guess… Updating now.
After enabling lvfs-testing, a manual refresh operation would have pulled the new BIOS option right away. In your case, it auto-refreshed at some point later.
That was not this case though. The lfvs-testing was already on and I had already received this same note in the terminal before.