# Update Question Linux/BIOS **URL:** \ **Category:** Framework Laptop 12\ **Tags:** bios\ **Created:** [October 25, 2025, 4:12pm UTC](https://community.frame.work/t/update-question-linux-bios/77143 "2025-10-25T16:12:14Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Isaac\_Tait](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/isaac_tait/32/40338_2.png) [@Isaac\_Tait](https://community.frame.work/u/Isaac_Tait)\ **Post date:** [October 25, 2025, 4:12pm UTC](https://community.frame.work/t/update-question-linux-bios/77143/1 "2025-10-25T16:12:14Z")
I got an email stating that a software update was available for my laptop. I followed the [process](https://knowledgebase.frame.work/en_us/how-to-check-the-bios-version-on-windows-linux-bios-ryupu8HT3) to check BIOS: `Vendor: INSYDE Corp. Version: 03.04 Release Date: 06/23/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` I meet the criteria for the update (13th gen Intel Core currently on BIOS 3.04). So, I followed the [update process](https://knowledgebase.frame.work/framework-laptop-12-bios-and-driver-releases-13th-gen-intel-core-HyrqeX2ex?utm_campaign=2025-10-15-fl12-software-update%20(01K7ME7WFD2XZNBYP7MYJW6WBB)&utm_medium=email&utm_source=Framework%20Laptop%20software%20update%20email%20subscriptions%20list&_kx=NPhaMN-7nG_2zRYgyvpa-yyYXcZJbQCj9cAB2-nqD3lyMNDnjzfzscJepHpfayCT.LNYsui) but it’s not installing… I have Linux Mint so I’m following the Linux/LVSF procedures. Here’s what it’s returning: ```auto fwupdmgr refresh --force ``` Updating lvfs Downloading… [\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*] Successfully downloaded new metadata: 2 local devices supported * * * fwupdmgr get-updates Devices with no available firmware updates: • WD BLACK SN770M 1TB • Laptop 12 Webcam Module • UEFI dbx Devices with the latest available firmware version: • Intel Management Engine • System Firmware No updates available * * * ```auto fwupdmgr update ``` Devices with no available firmware updates: • WD BLACK SN770M 1TB Devices with the latest available firmware version: • Intel Management Engine • Laptop 12 Webcam Module • System Firmware • UEFI dbx ---
**Author:** ![bobh](https://avatars.discourse-cdn.com/v4/letter/b/df705f/32.png) [@bobh](https://community.frame.work/u/bobh)\ **Post date:** [October 25, 2025, 4:15pm UTC](https://community.frame.work/t/update-question-linux-bios/77143/2 "2025-10-25T16:15:36Z")
Did you reboot? ---
**Author:** ![Isaac\_Tait](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/isaac_tait/32/40338_2.png) [@Isaac\_Tait](https://community.frame.work/u/Isaac_Tait)\ **Post date:** [October 25, 2025, 4:52pm UTC](https://community.frame.work/t/update-question-linux-bios/77143/3 "2025-10-25T16:52:46Z")
Yes. I’ve tried the process twice rebooting after each time and it still says BIOS 3.04 ---
**Author:** ![madvillain](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@madvillain](https://community.frame.work/u/madvillain)\ **Post date:** [October 25, 2025, 8:07pm UTC](https://community.frame.work/t/update-question-linux-bios/77143/4 "2025-10-25T20:07:56Z")
I tried updating to the 3.06 firmware a week ago on Fedora Workstation through the terminal and like you the update didn’t seem to be available and would not download. I ended up manually downloading the EFI shell update (scroll down to “Linux/Other/UEFI Shell update”), put it on a FAT32 formatted USB drive, and I was able to boot into it and install the new firmware without issue. ---
**Author:** ![Isaac\_Tait](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/isaac_tait/32/40338_2.png) [@Isaac\_Tait](https://community.frame.work/u/Isaac_Tait)\ **Post date:** [October 25, 2025, 8:30pm UTC](https://community.frame.work/t/update-question-linux-bios/77143/5 "2025-10-25T20:30:11Z")
I tried the EFI shell update route. However, when I restart the computer and hold the F12 button the screen turns on and off once or twice then the normal login screen appears… ---
**Author:** ![madvillain](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@madvillain](https://community.frame.work/u/madvillain)\ **Post date:** [October 25, 2025, 8:33pm UTC](https://community.frame.work/t/update-question-linux-bios/77143/6 "2025-10-25T20:33:36Z")
Try hitting the F12 key repeatedly instead of holding it. ---
**Author:** ![2disbetter](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/2disbetter/32/1176_2.png) [@2disbetter](https://community.frame.work/u/2disbetter)\ **Post date:** [October 25, 2025, 9:16pm UTC](https://community.frame.work/t/update-question-linux-bios/77143/7 "2025-10-25T21:16:10Z")
I am running Omarchy and just used fwupdmgr to upgrade the BIOS on my FW 12. There was a previous update that went first. This required an update. After rebooting I ran fwupdmgr update again and it applied the bios update on the reboot. I also had fwupdmgr work on my FW 13 with a 12th gen mainboard. Just wanted to report that it was working for me. ---
**Author:** ![Simon\_Bolscher](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@Simon\_Bolscher](https://community.frame.work/u/Simon_Bolscher)\ **Post date:** [October 25, 2025, 9:17pm UTC](https://community.frame.work/t/update-question-linux-bios/77143/8 "2025-10-25T21:17:20Z")
You’re not doing anything wrong. I had the same problem. The 3.5 and 3.6 are not publicly released in LVFS from what I can see here (still in testing state): [LVFS: Laptop 12 Intel 13th Gen Core](https://fwupd.org/lvfs/devices/work.frame.Laptop12.RPL.BIOS.firmware) > Version 0.0.3.6 — may not be suitable for production systems (state: testing) > > 2025-10-16 16:22:09 > Version 0.0.3.5 — may not be suitable for production systems (state: testing) > > 2025-09-19 08:11:39 > Version 0.0.3.4 (state: stable) > > 2025-08-12 06:05:23 Seems like Framework might need to mark a checkbox to enable 3.5 & 3.6 in LVFS. Not sure if this is intentional or if they just forgot that. You can try the following command: ```bash fwupdmgr enable-remote lvfs-testing ``` And then try the update procedure again (refresh, get-updates, update). You might want to disable lvfs-testing after that via ```bash fwupdmgr disable-remote lvfs-testing ``` ---
**Author:** ![2disbetter](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/2disbetter/32/1176_2.png) [@2disbetter](https://community.frame.work/u/2disbetter)\ **Post date:** [October 25, 2025, 10:54pm UTC](https://community.frame.work/t/update-question-linux-bios/77143/9 "2025-10-25T22:54:43Z")
> [@Simon\_Bolscher](#): > > You can try the following command: > > ```auto > fwupdmgr enable-remote lvfs-testing > > ``` I think this is the command I used as well, because when I update the repos for fwupdmgr it includes lvfs-testing. ---
**Author:** ![Patrick\_Chamberlain](https://avatars.discourse-cdn.com/v4/letter/p/3be4f8/32.png) [@Patrick\_Chamberlain](https://community.frame.work/u/Patrick_Chamberlain)\ **Post date:** [October 26, 2025, 7:48am UTC](https://community.frame.work/t/update-question-linux-bios/77143/11 "2025-10-26T07:48:43Z")
I wasn’t aware of this until I saw this thread. I’m happy to wait for a stable release - am I missing anything by not updating from 3.4? ---
**Author:** ![2disbetter](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/2disbetter/32/1176_2.png) [@2disbetter](https://community.frame.work/u/2disbetter)\ **Post date:** [October 26, 2025, 8:10am UTC](https://community.frame.work/t/update-question-linux-bios/77143/12 "2025-10-26T08:10:36Z")
It should be noted that Framework calls the 3.06 version stable. On Windows you are to install it. That it doesn’t appear to be staged properly in Linux is an oversight, perhaps, but I have 3.06 on my FW 12 and all is well. ---
**Author:** ![madvillain](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@madvillain](https://community.frame.work/u/madvillain)\ **Post date:** [October 26, 2025, 8:30am UTC](https://community.frame.work/t/update-question-linux-bios/77143/13 "2025-10-26T08:30:15Z")
3.06 is considered stable even though it doesn’t seem to be currently available on Linux through LVFS unless you enable updates from testing. It’s mostly security fixes, but also adds battery charge limit status functionality. Previously on 3.04, when I charge the FW12’s battery to the 80% limit that I set it to in the bios, the charge icon indicator in Fedora would remain green as if it is still charging even though it isn’t. With bios 3.06, the charge indicator now turns white to signify that it has stopped charging. ---
**Author:** ![Isaac\_Tait](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/isaac_tait/32/40338_2.png) [@Isaac\_Tait](https://community.frame.work/u/Isaac_Tait)\ **Post date:** [October 28, 2025, 12:10am UTC](https://community.frame.work/t/update-question-linux-bios/77143/14 "2025-10-28T00:10:22Z")
Looking at the LVFS site it says 3.6 is Reported Success: 94% (low confidence). How is 94% low confidence? 3.5 is 100% but also low confidence where as 3.4 is 98% and high confidence. It doesn’t make any sense. ---
**Author:** ![Simon\_Bolscher](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@Simon\_Bolscher](https://community.frame.work/u/Simon_Bolscher)\ **Post date:** [October 28, 2025, 7:10am UTC](https://community.frame.work/t/update-question-linux-bios/77143/15 "2025-10-28T07:10:42Z")
Confidence is about the number of reported updates from systems. Low confidence just means that only a small number of users finished the update through LVFS. As a result, the 94% success rate probably doesn’t represent the real success rate (might be higher or lower when more update reports are coming in).