I see my BIOS version is 3.03 on Fedora Linux on my Framework Laptop 12, batch 1, gray color.
$ sudo dmidecode -s bios-version
03.03
I noticed the Laptop 12’s current latest stable BIOS version is 3.04, according to the following page. Anyone, did you upgrade the BIOS from 3.03 to 3.04? Do I need to upgrade from 3.03 to 3.04?
Honestly, it’s always a good idea having a current firmware running.
I will upgrade the BIOS later when I have time. Thank you for your advice!
I did and it resolved the issue that I was having with the fan not detected at boot. Framework seems to have made good progress on the firmware front, hopefully they keep it up.
Thank you for your info!
How did you confirm the fan was not detected, then the fan was detected after upgrading the BIOS to 3.04?
After updating the BIOS visa LVFS on Fedora Linux, I still see the bios version is 3.03, not 3.04.
The command log is below as a reference. I didn’t see the updater pages such as mentioned on this page to update BIOS and EC after rebooting.
$ which fwupdmgr
/bin/fwupdmgr
$ rpm -qf /bin/fwupdmgr
fwupd-2.0.12-1.fc42.x86_64
$ fwupdmgr refresh --force
Updating lvfs
Downloading… [***************************************]
Successfully downloaded new metadata: Updates have been published for 4 of 11 local devices
$ fwupdmgr get-updates
Devices with no available firmware updates:
• KEK CA
• Laptop 12 Webcam Module
• SBAT
• WD BLACK SN770M 2TB
• Windows UEFI CA
• frame.work-LaptopDB
• frame.work-LaptopKEK
Devices with the latest available firmware version:
• Intel Management Engine
• System Firmware
• UEFI CA
Framework Laptop 12 (13th Gen Intel Core)
│
└─UEFI dbx:
│ Device ID: 362301da643102b9f38477387e2193e57abaa590
│ Summary: UEFI revocation database
│ Current version: 20230501
│ Minimum Version: 20230501
│ Vendor: UEFI:Microsoft
│ Install Duration: 1 second
│ GUIDs: f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
│ d07ff664-b0e1-5f4e-a723-d7fbcbfcb94f ← UEFI\CRT_3CD3F0309EDAE228767A976DD40D9F4AFFC4FBD5218F2E8CC3C9DD97E8AC6F9D&ARCH_X64
│ f6821e29-aadb-5553-afc5-52d527622fb7 ← UEFI\CRT_A54022CD89A063636FC7B3AFEE52106C2CEEC133C56A07E040DFABC90313B758&ARCH_X64
│ Device Flags: • Internal device
│ • Updatable
│ • Supported on remote server
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Only version upgrades are allowed
│ • Full disk encryption secrets may be invalidated when updating
│ • Signed Payload
│ • Can tag for emulation
│
├─Secure Boot dbx Configuration Update:
│ New version: 20250507
│ Remote ID: lvfs
│ Release ID: 115586
│ Summary: UEFI Secure Boot Forbidden Signature Database
│ Variant: x64
│ License: Proprietary
│ Size: 24.0 kB
│ Created: 2025-01-17
│ Urgency: High
│ Tested: 2025-06-11
│ Distribution: fedora 42 (workstation)
│ Old version: 20241101
│ Version[fwupd]: 2.0.11
│ Vendor: Linux Foundation
│ Duration: 1 second
│ Release Flags: • Trusted metadata
│ • Is upgrade
│ • Tested by trusted vendor
│ Description:
│ This updates the list of forbidden signatures (the "dbx") to the latest release from Microsoft.
│
│ Some insecure versions of BiosFlashShell and Dtbios by DT Research Inc were added, due to a security vulnerability that allowed an attacker to bypass UEFI Secure Boot.
│ Issues: 806555
│ CVE-2025-3052
│ Checksum: 3ebe1c9be68b6c559ed2831a0bfd891c84e6d6db9af7c61156230d79f6466648
│
└─Secure Boot dbx Configuration Update:
New version: 20241101
Remote ID: lvfs
Release ID: 105821
Summary: UEFI Secure Boot Forbidden Signature Database
Variant: x64
License: Proprietary
Size: 15.1 kB
Created: 2025-01-17
Urgency: High
Vendor: Linux Foundation
Duration: 1 second
Release Flags: • Trusted metadata
• Is upgrade
Description:
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.
Issues: 529659
CVE-2024-7344
Checksum: 093e6913dfecefbdaa9374a2e1caee7bf7e74c7eda847624e456e344884ba5f6
$ fwupdmgr update
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade UEFI dbx from 20230501 to 20250507? ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ This updates the list of forbidden signatures (the "dbx") to the latest ║
║ release from Microsoft. ║
║ ║
║ Some insecure versions of BiosFlashShell and Dtbios by DT Research Inc were ║
║ added, due to a security vulnerability that allowed an attacker to bypass ║
║ UEFI Secure Boot. ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]:
══════════════════════════════════════════════════════════════════════════════╗
║ Full Disk Encryption Detected ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ Some of the platform secrets may be invalidated when updating this ║
║ firmware. Please ensure you have the volume recovery key before continuing. ║
║ ║
║ See https://github.com/fwupd/fwupd/wiki/Full-Disk-Encryption-Detected for ║
║ more details. ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]:
Waiting… [***************************************]
Successfully installed firmware
Devices with the latest available firmware version:
• Intel Management Engine
• System Firmware
• UEFI CA
Devices with no available firmware updates:
• KEK CA
• Laptop 12 Webcam Module
• SBAT
• WD BLACK SN770M 2TB
• Windows UEFI CA
• frame.work-LaptopDB
• frame.work-LaptopKEK
An update requires a reboot to complete. Restart now? [y|N]:
My current BIOS version is below after updating the BIOS by the above commands. I picked up the command from this page. I am not sure if there are changes from the status before the updating BIOS.
$ sudo dmidecode | grep -A3 'Vendor:\|Product:' && sudo lshw -C cpu | grep -A3 'product:\|vendor:'
Vendor: INSYDE Corp.
Version: 03.03
Release Date: 06/05/2025
Address: 0xE0000
product: 13th Gen Intel(R) Core(TM) i5-1334U
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: 6.186.3
Prior to the bios update I had a screen at boot time directing me either to hit the power button to continue to boot or to hold it for five seconds to shut down. Continuing the boot had the fan not running unless I used fw-fanctrl. After the bios update the screen at boot is no longer present, and the fan runs properly without needing to use fw-fanctrl.
I am booting from an expansion card that I can switch between my 12, 13, and 16 machines. Right now the 12 is getting the most use. I can take notes on it with handwriting to text using Gboard in waydroid, and it is doing fine for general purpose. It is not as fast as the 16 or the 13 that I upgraded to the 7640 board, but it is better than the 11th Gen that I had in the 13 until the recent upgrade.
So far I am enjoying it a lot, as I have been able to use it as I had hoped.
I believe the update had to do with a race condition on power delivery side that would not allow boot if you unplugged while powering on, etc. Good update to have. I too feel that Framework is really getting their firmware team speed really up there. Much love Framework!
Just FYI, I updated on Windows 11 last night and had zero issues. The update process went smooth and all works as expected after the update.
I am running Bluefin Aurora based on Fedora 42, and while I can run the fwupdmgr commands fine, it does not show that there is an update available. I am currently running BIOS 3.0.3 and am not super familiar with updating firmware on any Linux, is this an expected issue? I’m fine updating via EFI if it comes to that, I am just trying to understand the process better for the future.
All right. Thank you for sharing the info. I am not sure if I saw the screen at boot time directing me to do that. But after the bio update with the above steps, I see my fan is running without the fw-fanctrl.
So, what is your BIOS version? Could you see the BIOS version 3.04 after the BIOS update on Windows 11?
I am seeing another case, the BIOS update on the Framework Laptop 12 via LVFS didn’t do anything.
Hi @IceNine451, in your case, where the fwupdmgr didn’t show that there is an update available, did you run the fwupdmgr with full charging status? If you ran the command with full charging, it could cause the LVFS not to be triggered. The charging state and the fully charged state are different in my understanding.
LVFS may not update if the battery is 100% charged. LVFS uses the battery status to determine if it is safe to apply updates. However if our battery is at 100% and the charger is off, we set the battery charging status to false. In this case you can discharge your battery a few percent, then plug in AC again and run fwupdmgr update.
i also don’t see the 3.04 update in LVFS yet. i ran fwupd update once after i installed it which updated something but now that i checked my EFI version it is not 3.04. i’m on NixOS if that is relevant somehow.
to check for updates i used (80% battery and charging)
$ fwupdmgr refresh --force
$ fwupdmgr get-updates
Devices with the latest available firmware version:
• UEFI dbx
• Intel Management Engine
• System Firmware
• UEFI CA
No updates available
and to check the current version i ran
$ sudo ectool version
RO version: sunflower-3.0.3-d8d6368
RW version: sunflower-3.0.3-d8d6368
Firmware copy: RO
Build info: sunflower-3.0.3-d8d6368 2025-06-04 07:37:47 marigold1@ip-172-26-3-226
Tool version: 0.0.1-isolate Jan 1 1980 none
the EFI setup utility says “InsydeH20 Version” is “LFR20.03.03” which i’m not sure if that’s the same version or a coincidence in similar numbers
Did at least someone manage to update the BIOS by use of fwupdmgr?
This is an inquiry to get further information.
Maybe there is something wrong server-side with LVFS?
This is pure speculation on my part.
Yup, BIOS and EC are version 3.04 after the update.
Answering my own question here.
It seems version 3.03 is the most recent version on LVFS (at the time of writing*)…
*Before some smartass shows up on Monday posting “your link points to version 3.04 you dum-dum!”.
Good catch! Thanks for investigating it!
I took the screenshot on the above-linked page as evidence to assist you!
I am seeing the 3.04:
But I updated the BIOS using WIndows. Just easier.
but i don’t have windows here 
