Framework Laptop 16 Ryzen 7040 BIOS 3.05 Release BETA

Framework Laptop 16
1

2024-11-21

Highlights

  • Added automatic battery lifetime extender if the system is attached to AC for several days.
  • Fixed 1 security vulnerability.
  • Fixed 2 performance issues when connected with 3rd party adapters and dongles.
  • Fixed ALS HID communication failures.

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 85Wh 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.

1600Ă—900 188 KB

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_16_Amd_Ryzen7040_BIOS_3.05.exe e01fa8be02bc15e706352ee9d5948b74634ac41b18595394549db49af390be82

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.

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.

You can see the current releases status at

https://fwupd.org/lvfs/devices/work.frame.Laptop16.Ryzen7040.BIOS.firmware

Linux/Other/UEFI Shell update

Download Link SHA256
Framework_Laptop_16_Amd_Ryzen7040_BIOS_3.05_EFI.zip 7ca4e1e15704544f133606fc4fd210ea320595e71540df6e29fa5adef01258be

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.
  6. If you are updating a system in standalone mode, please pay careful attention to the standalone update process below.

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.

Security Fixes

Module Name Vulnerability Score
AMD PI CVE-2023-31315 7.5

Enhancements

  • Added battery lifetime extender functionality.
  • Update Insyde kernel to 05.54.23.0020 with AMD PhoenixPI-FP8-FP7_1.1.0.3.

Fixes

  • Change the boot option name to “GRUB Boot Loader” For EFI\Boot\grubx64.efi boot loader file.
  • Fix ALS HID device communication failures causing yellow bang in Windows device manager, or Linux kernel errors.
  • Fix issue with 240W power adapters to improve dGPU performance in best performance mode.
  • Fix issue where the CPU will be stuck at 500Mhz if the system is powered from an >100W charger through some brands of MFD hubs.

Important Note

  • After updating to this version you will not be able to downgrade to an earlier version.

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.06 Updated
EC ec_305_227507 Updated
PD 0.0.1E Same
AMD PI 1.1.0.3 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, 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

  1. Type-c connection may be unstable with some Apple phones.
  2. Cannot negotiate charging for certain portable EPR power banks.
  3. If a device is plugged into an expansion card slot during the update, all USB3/DP functionality will be lost until the device is removed and reinstalled, or the system is fully shut down and powered on again. (Power off, unplug the charger, wait 90 seconds, and then power on again to recover). This issue has an occasional failure rate.
7 Likes
3

I suppose we have to wait a little until the firmware has been propagated (fwupdmgr) does not yet show an update (with enable-remote lvfs-testing).

4

I’ve been having this issue using a Plugable TBT4-UD5, which is advertised as having 100W USB-C PD support, so the threshold for this problem might be >=100W, not >100W :slight_smile:

In any case, I’m quite looking forward to this fix, having the CPUs stuck at 500MHz is not sparking joy in my life, especially when a power-cycle is required to recover from it.

1 Like
5

@Jorg_Mertin
Same here, not firmware update appearing in fwupdmgr, even though the fwupd.org site shows it present.
I am in UK.

6

This is a bit alarming, seems to be against open-source spirit

7

I updated FW16 to 3.0.5 using the EFI.
I had to do a minor edit to Startup.nsh, but only because I did not put it in /EFI/Boot and put it in /EFI/boot2. So, simply find/replace Startup.nsh “Boot” → “boot2” made it work.
If Startup.nsh is wrong, it gives an error with something like “winux.bin” not found.

One word of warning. It does not have an “Are you sure you wish to upgrade from X to Y version ?” It just says press a key within 8 seconds to abort.
The update took about 3 minutes of spinning wheel to complete.

8

Probably not synced to our local servers yet.

9

Battery extender functionality is GG. Honestly this is a very good idea. Can’t wait for it to hit stable!

10

Installation with LVFS from Tumbleweed worked. I’m up and running again, but had to reboot the system and re-configure my external monitors. Maybe known issue #3.

11

Is your battery fully charged? You may need to discharge it a bit and then plug your system back in before fwupdmgr will install the update.

12

Synced now.

        Vendor: INSYDE Corp.
        Version: 03.05
        Release Date: 11/13/2024
        Address: 0xE0000
       product: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
       vendor: Advanced Micro Devices [AMD]
       physical id: 4
       bus info: cpu@0
       version: 25.116.1
13

The addition of the battery extension feature is awesome! Thanks for putting that together or coordinating it if it was the vendor. :slight_smile:

14

I tried installing the BIOS update and it got to about 40% on the screen with the spinning framework logo. Then the whole screen went black. After 15 minutes there had been no change. I force powered off the laptop with the power button. The laptop thankfully did boot again. I ran the BIOS update .exe again from Windows 11 and the second time the GUI update screen did get to 100% and said “Update completed”.

Issue reported on github too: BIOS 3.05 Beta Install Failure · Issue #7 · FrameworkComputer/SoftwareFirmwareIssueTracker

1 Like
15

I’m also experiencing known issue #3. I’ve unplugged all devices and reconnected them without success. I’ve also powered off the laptop and unplugged the devices for a few minutes still no luck restoring USB3 functionality.

16

When you powered off the laptop, did you also unplug all devices and also unplug the power brick from the usb-c and wait more than 40 seconds before plugging stuff in again?

17

Nice to see this line item. @Kieran_Levin - any more insight on the scope of these 2 issues. Thanks

18

Yes, I unplugged everything including the charger.

19

@Joseph_Schroedl

  1. Try going into the BIOS and reset it to factory defaults. One of the bios options is something like that.
  2. Try resetting the main board. Following the pressing of the chassis open switch many time etc. Accurate instructions are on other threads. Search for “chassis open”.
20

Turns out it was my USB-C dock that I had connected to the laptop during the BIOS update that was the issue. I had to remove power from my Anker 568 dock and unplug it to fully power cycle the dock before it would work again.