Framework Laptop 13 Ryzen 7040 BIOS 3.07 Release BETA

[Quin_Chou]

Highlights

Please note this #3~#6 are copied from 3.06, as 3.06 was not promoted to stable. Delta is 3.05->3.07.

1. Fixes for battery extender functionality introduced in 3.06.
2. Modified the charge limit functionality to allow a 5% float range on the battery.
3. Fixed 5 security vulnerabilities.
4. Fixed ALS sensor communication failures.
5. Fixed IRQ1 wake issues on Linux.
6. Fixed diagnostic compatibility issue with 2.8K displays.

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

After the beta release, we will monitor community feedback, and publish this release to our stable release channel after approximately one week if no major issues are reported.

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.

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.

Battery Charge Limit Functionality

This release modifies the battery charge limit functionality to add a 5% float range. This allows us to reduce the number of microcycles on the battery when the CPU turbos.
Previously to the change in 3.07, the battery would be held at the target state of charge, so if a large power draw happened for a short time, such as when the CPU turbos, the battery would drain slightly and then charge again.
Introduced in this version, the battery will not start to charge until the battery has dropped 5% below the charge limit.

As an example, if the user sets the battery charge limit to 80%, the battery will maintain a state of charge between 80% and 75%. And will not charge up to 80% until it has discharged to 75% while the system is on.

Downloads

Windows

Download Link	SHA256
Framework_Laptop_13_Ryzen7040_BIOS_3.07.exe	0a05910770e29ad167bd757c3987c3790f9d1c572335314326b4f9203352e690

Instructions for Windows Installer:

1. Run the .exe.
2. Click yes to reboot.
3. Wait for the firmware progress bar to complete, and then the system will reboot.
4. If you are updating a system in standalone mode, please pay careful attention to the standalone update process below.

Please note that you must update with a charger attached.

Linux/LVFS

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

You can enable updates from testing by running

fwupdmgr enable-remote lvfs-testing

Please note that you must update with a charger attached, then run:

fwupdmgr refresh --force

then

fwupdmgr get-updates

then

fwupdmgr update

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_Ryzen7040_BIOS_3.07_efi.zip	51f871d439cc920c2fdba70750184602019bad2f4b60521bd1e57746041e71ce

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. Follow the instructions to install the update.

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.

Please note that the power and display output must be connected to the same side during standalone updates. Failure to do this may result in no display output during the update process.

We recommend the following update flow for standalone updates:

Part 1

Ensure that standalone operation is enabled in the bios advanced setup menu.

Display connected to upper left port.
Power connected to the lower left port.
Run the updater from EFI/Windows updater.

After rebooting into the updater the update will commence:

The updater will update the BIOS and EC.

The Updater will update the PD controller that is not connected to the power source.

You will see one PD controller will fail the update with the X, and “update complete” is displayed, but the bios will restart.

Part 2

At this screen, the bios update will stop. You must disconnect the display and power source, and move them to the other side.
The display should be connected to the top right.
Power should be connected to the bottom right.

Press the power button, and the second PD update will complete.

After this, the system will reboot, and your bios update is complete.

Security Fixes

Please note this is copied from 3.06, as 3.06 was not promoted to stable. Delta is 3.05->3.07.

Module Name	Vulnerability	Score
UefiPxeBcDxe	CVE-2023-45234	8.8
Dhcp6Dxe	CVE-2023-45230	8.8
IP6Dxe	CVE-2023-45232	7.5
IP6Dxe	CVE-2023-45233	7.5
AMD PI	CVE-2023-31315	7.5

Enhancements

1. Modified the charge limit functionality to allow a 5% float range on the battery. If the battery charge limit is set to 80%, now the battery will float between 75%-80%, reducing wear.
2. Lower the screen minimum brightness on Linux. This updates the minimum brightness PWM value in the bios, to allow the screen to default to a lower minimum brightness. Please note that this is not enforced in windows as the AMD graphics driver overrides the minimum brightness setting in the bios.

Fixes

1. Fixes for battery extender functionality. This release fixes the battery extender functionality bug when enabled with battery charge limit set below 100%.

2. Bug: If the charge limit was below the extender limit, and the extender triggered, the battery would charge above the extender limit.

3. The charging LED would toggle between White/Orange when reaching the charge limit.

4. Fix ACPI thermal_zone3 reporting incorrect values occasionally.

5. Update driver certificate for org.uefi.Driver.RtkUndiDxe

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.07	Updated
EC	ec_307_55046	Updated
PD	0.0.1C	Same
AMD PI	1.1.0.3	Updated

Reporting Issues

To report issues we have created a public issue tracker on github. GitHub · Where software is built 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, 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 through the bios release process, and will review them for future updates as well.

If you have an issue regarding hardware, broken devices, returns, etc, this is not the place, please contact support.

Known Issues

• BIOS display output may not show up in standalone mode when booting the first time. To work around this issue we suggest booting into the OS and then restarting and pressing F2 to enter the setup menu.
• When updating in standalone mode, there may be no display output after updating one side’s PD firmware. Suggest connecting power and display on the same side when performing a BIOS update in standalone mode.
• Connecting with iPhones over type-c may be unstable.

[James3]

Please can you also update the description to explain how to rollback to a previous bios in case this one causes problems for some people?
Or clearly state that rollback is not possible.

[alderonmatt]

tried this on 2 devices, haven’t bricked either so far one on windows and one on Linux.

[Grandpa_engineer]

anyone else have the black screen issue when trying to install the graphics driver thats anything newer than 24.8.1? i remember the fw16 having this issue, the 13 has it too but no one mentioned it apparently its when it has more than 64gb of ram and i have 96

[inffy]

I think that is still waiting for the fix from AMD. I remember reading that it should be available during March.

[Brian_Gregory]

SEEMS BROKEN.
I upgraded, and I appear to have lost the ability to set my own lower battery charge limit. The laptop is just ignoring my 70% charge limit. I have tried both with battery extender disabled and with it enabled.

[Richard3]

@Brian_Gregory

SEEMS BROKEN.
I upgraded, and I appear to have lost the ability to set my own lower battery charge limit. The laptop is just ignoring my 70% charge limit. I have tried both with battery extender disabled and with it enabled.
THIS IS UNACCEPTABLE.

My 80% limit isn’t holding either.

edit: It seems to be working again now. Like @Brian_Gregory , a few changes back and forth in the BIOS eventually fixed it.

[shawnyeager]

After first boot, post-update, USB C video output is borked. After a second reboot, all seems well.

[Will_Nilges]

Will this BIOS update fix the issue that some of us have been having where the machine will hard reset after coming out of sleep?

Spontaneous and ungraceful restarts upon closing the lid

Which Linux distro are you using? Arch Linux Which release version? (if rolling release without a release version, skip this question) (If rolling release, last date updated?) February Which kernel are you using? 6.13.3-zen1-1-zen Which BIOS version are you using? 0.0.3.5 Which Framework Laptop 13 model are you using? (AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™) AMD Ryzen™ 7040 Series Hey folks, this weeke…

[Brian_Gregory]

@Brian_Gregory

I appear to have lost the ability to set my own lower battery charge limit.

Okay, I re-entered every setting in the BIOS related to battery charging and battery extender and changed my battery charge limit several times, rebooting in between, but put it back to 70%, and things are now behaving differently, but oddly. It seems to have stopped charging the battery, but also it seems to have stopped accepting any AC power, like maybe it’s trying to bring the battery back down to 70%? But that’s not what used to happen, it used to just stop charging but continue to work off the AC power.

Added later: As the battery came down nearer to 70% the laptop started drawing power from AC, so maybe it’s working more or less acceptably right now, but only after a lot of fiddling about with BIOS settings and rebooting in between.

[Michael_Marley]

I installed this and haven’t had any issue besides the usual USB-C video output breakage that needs a full power cycle with the external power removed and re-applied to resume normal operation. That happens with every firmware update though.

[inffy]

Updated, everything seems to be fine. Enabled battery extender and also set back the charge limit to 60% ( extender was already disabled but I also disabled the charge limit setting in bios before the update)

[Tim_Bosse]

I didn’t need to reboot, a simple disconnect/reconnect of the display was sufficient.

[kenneb]

The new behavior is described in the first post of this thread:

Battery Charge Limit Functionality

This release modifies the battery charge limit functionality to add a 5% float range. This allows us to reduce the number of microcycles on the battery when the CPU turbos.
Previously to the change in 3.07, the battery would be held at the target state of charge, so if a large power draw happened for a short time, such as when the CPU turbos, the battery would drain slightly and then charge again.
Introduced in this version, the battery will not start to charge until the battery has dropped 5% below the charge limit.

As an example, if the user sets the battery charge limit to 80%, the battery will maintain a state of charge between 80% and 75%. And will not charge up to 80% until it has discharged to 75% while the system is on.

[Brian_Gregory]

That doesn’t say anything about it using battery power to bring the battery charge level down, even when AC is connected. That’s something I don’t think I’ve seen any device do before, though I can see that it’s probably a good idea in many situations, once you know it does it.

My laptop was connected to AC but only using battery power when the battery was well over my set charge limit. At some point as the battery discharged it starting using AC power, when I noticed the charge level was 71%, and it has stayed at 71%. My charge limit is set to 70%.

And immediately after the BIOS upgrade things were behaving very differently before I fiddled with all the settings and rebooted several times, which was how it ended up getting charged so far over 70% in the first place.

[gammy]

I noticed the same behaviour as you’ve described so far: system ignoring my 70% limit until I toggled it off/on with reboots in between, and the system then discharging with AC connected, KDE’s battery widget claiming “charging but with insufficient power” yet staying in performance (AC) mode as my settings dictate. In other words, apart from the incorrect message from the battery widget, things seem alright after toggling the setting off and on with reboots in between.

I wonder how many of us that noticed oddities were on the 3.06 beta previously. That case (going from beta to beta) could perhaps have been missed in Framework’s testing.

[sydney]

Actually, at this point i would like to see someone from Framework having a word/explanation about the whole Firmware support issue the company clearly appears to be having. As it currently stands, i have (unfortunately) lost almost all confidence in the companys ability to resolve these issues in a reasonable timeframe/manner.

IMHO, you should first properly support devices you have actually already sold (of course?!?), instead of constantly focussing on new products to launch. If i want that, i can buy a MacBook today, which will come in cheaper and more important, much more reliable than Framework current offerings.

The state the product lineup is currently in and the contact with Framework’s support team has indeed been quite a sobering experience, to say the very least. Framework computers are not cheap products.

[alderonmatt]

Feeling the same way, all the products feel like beta level products, i can’t even remember the last time i had a firmware issue with a razer or asus laptop but on framework i have ran into my 30th firmware bug or problem. (On release bios versions, im okay if the beta version is buggy)

[Matthew_Shapiro]

BIOS 3.07 works fine here so far.

[Amaranth]

^this. I’d like to test out the beta release but I’m hesitant to do so if there’s no way to roll back to the stable BIOS version if I run into problems.