2024-11-21
Highlights
- Fixed 5 security vulnerabilities.
- Fixed ALS sensor communication failures.
- Fixed IRQ1 wake issues on Linux.
- Fixed diagnostic compatibility issue with 2.8K displays.
- Added automatic battery lifetime extender if the system is attached to AC for several days.
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.
Downloads
Windows
| Download Link | SHA256 |
|---|---|
| Framework_Laptop_13_Ryzen7040_BIOS_3.06.exe | 07c85f9fa2caf16d9bca46275164ff35ccb0cc1538d6c412bfe95f2c3dfa7684 |
Instructions for Windows Installer:
- Run the .exe.
- Click yes to reboot.
- Wait for the firmware progress bar to complete, and then the system will reboot.
- 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 LVFS: Laptop 13 AMD Ryzen 7040
Linux/Other/UEFI Shell update
| Download Link | SHA256 |
|---|---|
| Framework_Laptop_13_Ryzen7040_capsule_signed_allsku_3.06_EFI.zip | 308bfcf6e84521dfc5c6435538b2bbb08cebcc8df722509be8ad654eb239f609 |
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:
- 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.
- Attach a charger to your device while updating.
- Boot your system while pressing F12 and boot from the thumb drive.
- Let startup.nsh run automatically.
- Follow the instructions to install the update.
- 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.
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
| 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
- Added battery lifetime extender functionality
- Update Insyde kernel to 05.54.23.0020 with AMD PhoenixPI-FP8-FP7_1.1.0.3.
Fixes
- Fix issue with IRQ1 triggering on non keyboard wake sources. Causing Linux to wake unexpectedly.
- Fix EDID reporting with 2.8K panel. Which would erroneously report no panel connected blink codes.
- Adjusted _CRT temperature thresholds which would cause the thermal sensors to not be initialized by the kernel on some Linux Kernel versions.
- Modify power button behavior to prevent powering on the system when the Input Cover is first connected to the Mainboard.
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_306_f666c | 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. 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
- 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.
