We’ve just released a fast-spin BIOS 3.06 STABLE for the Framework 16 AI 300 because of the Bluetooth bug in 3.05
Highlights
- Fixed an issue where Bluetooth audio output was non-functional.
- Resolved intermittent system hangs or black screens occurring during the entry or resume phases of Hybrid Shutdown.
- Fixed a Yellow Bang affecting the AMD Audio Co-Processor and HD Audio Controller when resuming from Hybrid Shutdown.
- Updated the help string for the BIOS option “Select a UEFI file as trusted for execution”.
- Fixed an issue where the Battery Extender status was reported incorrectly following a reboot, hibernation, or shutdown after the timer had expired.
Note:
- With BIOS 3.06, you can downgrade to a previous version.
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.
Downloads
Windows
| Download Link | SHA256 |
|---|---|
| https://downloads.frame.work/bios/Framework_Laptop_16_Amd_RyzenAI300_BIOS_3.06.exe | f93467573844caeb3d9254500dbd728b52cc6b7d7ec71be72ca492d7ecbc95cb |
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
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 |
|---|---|
| https://downloads.frame.work/bios/Framework_Laptop_16_Amd_RyzenAI300_BIOS_3.06_EFI.zip | 5859f19c49361147d53c32d592675c02b89e1f6424e9727722f29f5950d74d71 |
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.
Security Fixes
N/A
Enhancements
- Updated the help string for the BIOS option “Select a UEFI file as trusted for execution”.
Fixes
- Fixed an issue where Bluetooth audio output was non-functional.
- Resolved intermittent system hangs or black screens occurring during the entry or resume phases of Hybrid Shutdown.
- Fixed a Yellow Bang affecting the AMD Audio Co-Processor and HD Audio Controller when resuming from Hybrid Shutdown.
- Fixed an issue where the Battery Extender status was reported incorrectly following a reboot, hibernation, or shutdown after the timer had expired.
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.
| Firmware | Version | Updated? |
|---|---|---|
| BIOS | 3.06 | Updated |
| EC | ec_306_eb68558 | Updated |
| PD | 0.0.22 | None |
| NVIDIA® GeForce RTX™ 5070 PD | 0.0.22 | None |
| AMD PI | StrixKrackanPI-FP8 1.1.0.2d | None |
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
- Intermittent CPU frequency lock at 600MHz following S3/Modern Standby resume