Framework Laptop 13 Intel Core Ultra Series 1 BIOS 3.04 Release

[Kieran_Levin]

Framework Laptop 13 Intel Core Ultra Series 1 BIOS 3.04 Release

Nov 14, 2024

Highlights

• Thunderbolt certified.
• Fixed ALS sensor communication failure.
• Added automatic battery life extension if the system is attached to AC for several days.
• Fixed two security vulnerabilities: CVE-2023-45236 and CVE-2023-22613

Please note: This BIOS update is a multi-part update, meaning you will need to update to 3.03, (for Windows) update retimer firmware, and then update to 3.04. This is due to an issue that was found which can cause intermittent USB-PD failures during the update process. To prevent upgrading directly to 3.04, the BIOS version is version checked, so it is only possible to update to 3.03->3.04 in sequence. Due to changes in the CSME data structures, it is not possible to downgrade the BIOS from 3.03/3.04 once updated.

You can check your current BIOS version following the steps here to determine if you are on the latest release.

Subscribing to release notifications

If you want to subscribe to new release notifications you can now opt in through this link to receive an email when we release a new BIOS or driver update for your Framework Laptop. Please click here to manage notifications.

Battery Extender functionality

With the high energy density on the 61Wh battery, leaving it at 100% state of charge for an extended period of time can shorten the lifetime of the battery. To prevent this, we have added a new feature that automatically limits the maximum state of charge if the system is left plugged into power for more than 5 days. The timer is reset after the system is disconnected from a power adapter for more than 30 minutes.

Battery Extender Duration	Battery State of Charge
0-5< Days	99% → 100%
5-7 Days	90% → 95%
>7+ Days	85% → 87%

This functionality also reduces cycling of the battery by allowing the battery to discharge by several percent before charging again. Note that in addition to this automatic setting, you can also manually set a lower charge limit on your battery in BIOS to further preserve battery longevity.

This feature can be disabled or enabled in the BIOS Advanced menu.

Battery Extender: This option is enabled by default. If disabled, the system will always keep the battery fully charged.

Battery Extender Trigger: This option sets the number of days that must pass before the battery state of charge is reduced automatically to extend the battery life.

Battery Extender Reset: This option sets the number of minutes that the system is running on battery before the extender is reset, causing the system to charge to 100% when attached to power again.

Downloads

Windows

Download Link	SHA256
Framework_Laptop_13_Intel_Core_Ultra_Series1_BIOS_3.03_3.04.zip	04b341b7ef1b419345b0919cb09497cfe5a45e267768af3a4d40d07574cf6200

1. Ensure your system is plugged into power and your battery is charged.
2. Extract the contents of the zip.
3. Run the following updates in sequence. After each file is run your system will automatically restart.
4. Step1_Framework_Laptop_13_Intel_Core_Ultra_Series1_BIOS_3.03.exe
5. Step2_Framework_Laptop_13_Intel_Core_Ultra_Series1_Retimer_port01_624.exe
6. Step3_Framework_Laptop_13_Intel_Core_Ultra_Series1_Retimer_port23_624.exe
7. Step4_Framework_Laptop_13_Intel_Core_Ultra_Series1_BIOS_3.04.exe

Linux/LVFS

LVFS Updates are currently propagating to the beta channel once the metadata is rebuilt. These will be available to download in the next few hours.

Updating via LVFS is available in the testing channel during the beta period.

We have set a version check on LVFS, so you can only update to 3.04 from 3.03. So you will need to update to 3.03 first, and then 3.04 after you are running 3.03.

You can enable updates from testing by running

fwupdmgr enable-remote lvfs-testing

Please note that you must update with a charger attached.

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.

Linux/Other/UEFI Shell update

Download Link	SHA256
Framework_Laptop_13_Intel_Core_Ultra_Series1_capsule_signed_allsku_3.03_3.04_EFI.zip	020502033e76f28d25ddb03c70926e69587ca515e1ec4b65f74e08fa1ef38c01

Note that if you use the EFI shell update with Windows, you should suspend Bitlocker if enabled before updating using the EFI updater.

Instructions for EFI shell update:

1. Extract contents of zip folder to a FAT32 formatted USB drive. Cleanly unmount the drive before physically removing it, otherwise the BIOS update may not function correctly.

2. Attach a charger to your device while updating.

3. Boot your system while pressing F12 and boot from the thumb drive.

4. Let startup.nsh run automatically.

5. This will update to 3.03. The system will reboot several times and apply 4 updates.

6. After applying the first update and rebooting restart and press F12 and boot from the thumb drive a second time.

7. Let startup.nsh run automatically.

8. This will update from 3.03 to 3.04.

Updating a Mainboard outside of a laptop

This release supports standalone updates without a battery attached. After rebooting, please follow the onscreen instructions to update your BIOS when in standalone mode, which will require moving the power source between both sides of the Mainboard to allow PD firmware to update correctly.

Security Fixes

Module Name	Vulnerability	Score	Note
TcpDxe	CVE-2023-45236	5.8	Networking is not enabled in the BIOS unless enabled by the user.
IhisiSmm	CVE-2023-22613	8.8

Enhancements

1. Upgrade Insyde Tag 05.54.27.0031 with Intel MeteorLakeSiliconPkg 4122.17.
2. Add Battery Extender Functionality.
3. Thunderbolt Certified.

Fixes

1. Fix ALS Communication issues, and ALS yellow bang in device manager when exiting modern standby.

Component Versions

This BIOS update is a bundle of updates to multiple embedded components in the system.

Not all of them use the same version number.

BIOS	3.03/3.04	Updated
EC	ec_304_74a8e9a	Updated
PD	0.0.0A	Updated
Intel CSME	18.0.5.2141	Updated

Reporting Issues

To report issues we have created a public issue tracker on github. Issues · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub

We hope that this is a better way to track issues with community involvement moving forward as we have found it difficult to both gather relevant information about issues people are reporting on the forums, and track the issues through their lifecycle in a transparent way.

If you do experience an issue with the update that is related to your system firmware, or updating, please post as complete a description as you can, including relevant system information, and external peripherals. Please note that we do not currently have a SLA for responding to issues on github, but we will be reviewing them throughout the BIOS release process, and will review them for future updates as well.

If you have an issue unrelated to the BIOS update, please contact Framework Support. Framework | Fix Consumer Electronics

Known Issues

1. If external ports are disabled in the BIOS, they can still function if the wifi/bluetooth device is disabled/enabled.

[Juan_Shihfu]

You forgot to add domain to your efi version link😄

https://framework_laptop_13_intel_core_ultra_series1_capsule_signed_allsku_3.03_3.04_efi.zip/

[Juan_Shihfu]

[lbkNhubert]

The link to the linux download in Kieran’s post is this:

https://framework_laptop_13_intel_core_ultra_series1_capsule_signed_allsku_3.03_3.04_efi.zip/

So it is missing the domain that appears to be in the link to the windows version.

[Kieran_Levin]

Thanks for catching the link, i updated the top post with the correct link.

[Sleeping_bird]

Installed fine via EFI, fwupdmgr didn’t show any available updates even with lvfs-testing enabled.

So far, so good.

[Mr.V]

Same for me; lvfs command ran successfully and i enabled the repository in Discovery of Fedora 41, but no update was offered so i proceeded to run the update from USB and that went trough fine.

[basert]

When will this BIOS version hit stable? I use my Framework as a professional machine so I dont really wanna use beta versions But the battery charge limit changes look really nice.

[Juan_Shihfu]

I’m using this since day1, and manually set the Battery Extender days from 5 to 1, it works great and no other issues found.

[Destroya]

This BIOS release is promoted to stable as of today!

[speed_up]

After update 3.03 → 3.04 mine does not recognise the trackpad anymore…
Some idea what to do on windows?

[TheTRUEAsian]

Try rerunning the driver bundle.

[speed_up]

Did this - no change.
Solved: Had to re-activate camera in bios and restart once.
After this i could deactivate it again; everything fine now!

[Zachary_Weiss]

Just installed the efi shell update (I’m on fedora 41) and my external monitor isn’t recognized anymore. Any idea what might cause that?

Edit: nevermind, the issue seems to have resolved itself by unplugging the HDMI expansion card and plugging it back in, as suggested here.

[RodC]

Dual Booters Beware.

I’m running a Windows 11/Fedora dual boot config. My first attempt at BIOS updating failed. There was not enough room in the EFI disc partition to unpack/complete the process. Turns out my EFI partition was only 100Mb in size. A result of the Win11 install.

So I booted a live USB Fedora environment, and used gparted to resize/move various partitions to be able to grow the EFI partition. Well I could enlarge the EFI partition just fine, but gparted could not expand the file system contained in it. I spent about 45min. trying to find a solution, no joy. I finally copied the EFI partition contents to a temporary location, and with gparted deleted the EFI partition, recreated it (careful here, there a flags to be set) and copied the contents back into the new (larger) EFI partition.

Afterwards the system booted W11 just fine. But Fedora would not boot. . I spent another 30-45 minutes trying to figure out how to fix the Fedora booting issue. No luck, finally I just reinstalled Fedora.

Everything is now back up and running just fine, and my EFI partition is 1G in size (future proofed). An interesting, informative experience.

–
Rod

[Nick_Clarke]

After updating first to 3.03 and then subsequently to 3.04 automatically via the firmware updater tool in Ubuntu 24.04, my system would not successfully boot, and the init LED codes suggested that DDR OK failed. I have 2x16GB ram installed, which was working without issue before this update. I pulled one of my Crucial (CT32G56C46S5) 16 GB RAM sticks and it successfully booted again. It does not appear to be an issue with the the individual stick or the channel. I booted successfully using each stick alone, but could not get it to boot using both sticks, regardless of which channel they were placed in.

My thought was to lower the speed of the ram in the BIOS and try both sticks, but afaik, that is not possible? Any other thoughts? I do find it odd that this memory worked previously, but failed after the bios update.

I’ll open up an issue in the github issue tracker.

[Omid_Khalili]

I had a similar issue. After upgrading to v.3.03 with the firmware updater on Ubuntu 24.04, the laptop wouldn’t post with Crucial 2x16G CT2K16G56C46S5 (32GB).

Here is what fixed it for me:

• Removed SODIMM 2. It still couldn’t boot. Physically disconnected the battery and reconnected it. The laptop booted with only 16GB memory on SODIMM 1.
• Upgraded to v.3.04 with Ubuntu firmware updater, and the laptop booted again with 16GB memory.
• Turned off the machine and installed the second memory. Disconnected and reconnected the battery, but the laptop couldn’t post again.
• I took out memory#2 again, and this time, when the laptop was posted, I went into the BIOS and disabled “Quick Boot” and “Quiet Boot”. Then, I chose the “Disconnect Battery” option in the BIOS and pressed F10 to save without an AC connection.
• With the laptop powered down, I installed the second memory again and connected the AC. I turned ON the laptop and waited for the post. Laptop posted this time showing it testing the memory, when it finished it booted to Ubuntu with 32GB memory installed.
• Rebooted again and enabled “Quick Boot” and “Quiet Boot”.

[Nick_Clarke]

Thanks for the guide @Omid_Khalili . This worked for me. I only had 1 DIMM in channel 0, so I rebooted to disabled quick and quiet boot, enabled the “disconnect battery” option while only on battery power and saved. I then plugged in my AC power to reboot the system. It posted and did a quick memory test (15 sec or so) and showed all 32 GB reporting as passing. It then booted normally. I restarted to re-enable quick and quiet boot and disable “disconnect battery” option. Things appear to be working fine.