# Framework Laptop 16 Ryzen AI300 BIOS 3.06 Release STABLE

**URL:** <https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393>\
**Category:** Framework Laptop 16\
**Tags:** bios-announcement, bios, framework-laptop-16-amd-ai-300, graphics-module-nvidia-5070\
**Created:** [May 6, 2026, 5:48am UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393 "2026-05-06T05:48:34Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Quin\_Chou](https://avatars.discourse-cdn.com/v4/letter/q/cdc98d/32.png) [@Quin\_Chou](https://community.frame.work/u/Quin_Chou)\
**Post date:** [May 6, 2026, 5:48am UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393/1 "2026-05-06T05:48:34Z")

</div>

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

1. Fixed an issue where Bluetooth audio output was non-functional.
2. Resolved intermittent system hangs or black screens occurring during the entry or resume phases of Hybrid Shutdown.
3. Fixed a Yellow Bang affecting the AMD Audio Co-Processor and HD Audio Controller when resuming from Hybrid Shutdown.
4. Updated the help string for the BIOS option “Select a UEFI file as trusted for execution”.
5. 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](https://knowledgebase.frame.work/en_us/how-to-check-the-bios-version-on-windows-linux-bios-ryupu8HT3) 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](https://manage.kmail-lists.com/subscriptions/subscribe?a=LNYsui&g=VskBpF) 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](https://downloads.frame.work/bios/Framework_Laptop_16_Amd_RyzenAI300_BIOS_3.06.exe) | f93467573844caeb3d9254500dbd728b52cc6b7d7ec71be72ca492d7ecbc95cb |

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

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](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:

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.

## Security Fixes

N/A

## Enhancements

1. Updated the help string for the BIOS option “Select a UEFI file as trusted for execution”.

## Fixes

1. Fixed an issue where Bluetooth audio output was non-functional.
2. Resolved intermittent system hangs or black screens occurring during the entry or resume phases of Hybrid Shutdown.
3. Fixed a Yellow Bang affecting the AMD Audio Co-Processor and HD Audio Controller when resuming from Hybrid Shutdown.
4. 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](https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker/issues) 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. Intermittent CPU frequency lock at 600MHz following S3/Modern Standby resume

---

<div class="post-metadata">

**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\
**Post date:** [May 6, 2026, 7:24am UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393/2 "2026-05-06T07:24:00Z")

</div>

In the release notes, please can you include details of a url to EC source code, and which git branch to select so one can rebuild it and which compiler it is built with. I.e. not just the:  
EC ec\_306\_eb68558 Updated

I am currently having problems compiling the EC source code. I probably have a compiler bug that is somehow corrupting some specific i2c transactions, but not all, so knowing the above details would help me.

Please include this with each release note in future, for all the different mainboards.

---

<div class="post-metadata">

**Author:** ![MagicDude4Eva](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/magicdude4eva/32/44562_2.png) [@MagicDude4Eva](https://community.frame.work/u/MagicDude4Eva)\
**Post date:** [May 6, 2026, 9:00am UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393/3 "2026-05-06T09:00:35Z")

</div>

Is there a delay? I am on a Framework 16 AI with BIOS 3.05 - doing a get-updates:

```bash
(fwupdmgr:20914): FuMain-DEBUG: 10:57:24.337: current version is 01000334: 01000334=same
(fwupdmgr:20914): FuMain-DEBUG: 10:57:24.339: current version is 0.31: 0.29=older, 0.31=same
(fwupdmgr:20914): FuMain-DEBUG: 10:57:24.341: current version is 0.31: 0.29=older, 0.31=same
(fwupdmgr:20914): FuMain-DEBUG: 10:57:24.344: current version is 0.0.3.5: 0.0.3.2=older, 0.0.3.5=same, 0.0.3.4=older, 0.0.3.3=older
(fwupdmgr:20914): FuMain-DEBUG: 10:57:24.346: current version is 2023: 2023=same
(fwupdmgr:20914): FuMain-DEBUG: 10:57:24.348: No releases found
Devices with no available firmware updates:
 • Database Key
 • Key Exchange Key
 • KEK CA
 • Laptop Webcam Module (2nd Gen)
 • Option ROM UEFI CA
 • PIXA3854:00 093A:0274
 • WD BLACK SN770M 2TB
 • WD BLACK SN850X 2000GB
 • Windows UEFI CA
 • frame.work-LaptopDB
 • frame.work-LaptopKEK
Devices with the latest available firmware version:
 • Fingerprint Sensor
 • Laptop 16 Keyboard Module - ISO
 • Laptop 16 Numpad Module
 • System Firmware
 • UEFI CA
 • UEFI dbx
No updates available

```

and doing update:

```auto
(fwupdmgr:21329): FuMain-DEBUG: 10:59:46.910: current version is 01000334: 01000334=same
(fwupdmgr:21329): FuMain-DEBUG: 10:59:46.911: current version is 0.31: 0.29=older, 0.31=same
(fwupdmgr:21329): FuMain-DEBUG: 10:59:46.913: current version is 0.31: 0.29=older, 0.31=same
(fwupdmgr:21329): FuMain-DEBUG: 10:59:46.914: current version is 0.0.3.5: 0.0.3.2=older, 0.0.3.5=same, 0.0.3.4=older, 0.0.3.3=older
(fwupdmgr:21329): FuMain-DEBUG: 10:59:46.915: current version is 2023: 2023=same
(fwupdmgr:21329): FuMain-DEBUG: 10:59:46.917: No releases found
Devices with the latest available firmware version:
 • Fingerprint Sensor
 • Laptop 16 Keyboard Module - ISO
 • Laptop 16 Numpad Module
 • System Firmware
 • UEFI CA
 • UEFI dbx
Devices with no available firmware updates:
 • Database Key
 • Key Exchange Key
 • KEK CA
 • Laptop Webcam Module (2nd Gen)
 • Option ROM UEFI CA
 • PIXA3854:00 093A:0274
 • WD BLACK SN770M 2TB
 • WD BLACK SN850X 2000GB
 • Windows UEFI CA
 • frame.work-LaptopDB
 • frame.work-LaptopKEK

```

---

<div class="post-metadata">

**Author:** ![Rik\_Blok](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/rik_blok/32/37627_2.png) [@Rik\_Blok](https://community.frame.work/u/Rik_Blok)\
**Post date:** [May 7, 2026, 7:24am UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393/4 "2026-05-07T07:24:21Z")

</div>

Thanks for the beta! Upgraded this morning and it’s been working well for me so far. Bluetooth audio is working for me.

---

<div class="post-metadata">

**Author:** ![fullness](https://avatars.discourse-cdn.com/v4/letter/f/8c91f0/32.png) [@fullness](https://community.frame.work/u/fullness)\
**Post date:** [May 8, 2026, 9:38pm UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393/5 "2026-05-08T21:38:26Z")

</div>

Great - i dont usually download beta vers but this is an immediate download for me, as i am super inconvenienced by the bluetooth bug!

---

<div class="post-metadata">

**Author:** ![JakeSully](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/jakesully/32/45327_2.png) [@JakeSully](https://community.frame.work/u/JakeSully)\
**Post date:** [May 11, 2026, 10:16pm UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393/6 "2026-05-11T22:16:06Z")

</div>

I just updated to this beta and it seems this one actually fixed the slow boot issue on my FW 16.

i had around 30-35 seconds black screen before bios logo.

Now with this bios update i’m getting around 6-7 seconds maximum black screen before bios logo appears on the screen 🙂

I timed the reboot and then i shut down the laptop fully and powered it on and got same around 6-7 seconds on both. No more 30-35 seconds wait.

Finally it is fixed and laptop reboots + boots up faster now!

Update: it seems when I have a windows SSD installed, I get 6-7 seconds black screen before bios logo shows.

But once I change SSD back to my linux one it returns with 33-35 seconds black screen before bios logo.

So something is up with linux side causing it to hang longer than it does on windows now.

---

<div class="post-metadata">

**Author:** ![BPM](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/bpm/32/16864_2.png) [@BPM](https://community.frame.work/u/BPM)\
**Post date:** [May 11, 2026, 11:54pm UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393/7 "2026-05-11T23:54:23Z")

</div>

I see that it’s now marked as Stable. I take it no changes from the Beta?

---

<div class="post-metadata">

**Author:** ![AlfInAussieland](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/alfinaussieland/32/44280_2.png) [@AlfInAussieland](https://community.frame.work/u/AlfInAussieland)\
**Post date:** [May 12, 2026, 1:39am UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393/8 "2026-05-12T01:39:45Z")

</div>

I get the audio pop noise randomly using Linux Fedora 44 KDE. I am going to upgrade it a bit later and see how we go.

---

<div class="post-metadata">

**Author:** ![AlfInAussieland](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/alfinaussieland/32/44280_2.png) [@AlfInAussieland](https://community.frame.work/u/AlfInAussieland)\
**Post date:** [May 13, 2026, 1:12pm UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393/9 "2026-05-13T13:12:28Z")

</div>

Just an update. A day after the BIOS update, I shut down the Laptop completely as I was still getting that Audio Popping Noise.

I can report that the problem still exists. What I don’t know is if this a Fedora43/44 KDE Plasma problem.

---

<div class="post-metadata">

**Author:** ![sefalk](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@sefalk](https://community.frame.work/u/sefalk)\
**Post date:** [May 15, 2026, 9:40am UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393/10 "2026-05-15T09:40:41Z")

</div>

After this update my FW16 constantly gets a black screen on startup, so not even backlight. The only way to get out of this is to power cycle.

Before this update, this happened rarely, mostly after standby resume I figured out.

---

<div class="post-metadata">

**Author:** ![Artemis\_Meursault\_Ge](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/artemis_meursault_ge/32/48287_2.png) [@Artemis\_Meursault\_Ge](https://community.frame.work/u/Artemis_Meursault_Ge)\
**Post date:** [May 23, 2026, 1:14pm UTC](https://community.frame.work/t/framework-laptop-16-ryzen-ai300-bios-3-06-release-stable/82393/11 "2026-05-23T13:14:22Z")

</div>

Where can we see the code you actually used?

I’ve checkout out and build the EC bin and the commit mentioned in your release doesn’t appear to exist. Am I looking in the wrong place?

```auto
EmbeddedController ❯ sudo $(which framework_tool) --ec-bin ~/logs/flash.ec
File
  Size: 524288 B
  Size: 512 KB
EC
  Type: RO
  Version: tulip-3.0.6-eb68558
  RollbackVer: 0
  Platform: tulip
  Version: 3.0.6
  Commit: eb68558
  Size: 258048 B
  Size: 252 KB
EC
  Type: RW
  Version: tulip-3.0.6-eb68558
  RollbackVer: 0
  Platform: tulip
  Version: 3.0.6
  Commit: eb68558
  Size: 258048 B
  Size: 252 KB

```

```auto
EmbeddedController ❯ sudo $(which framework_tool) --ec-bin ./src/platform/ec/build/zephyr/tulip/output/ec.bin
File
  Size: 524288 B
  Size: 512 KB
EC
  Type: RO
  Version: tulip-3.0.6-3050f2d
  RollbackVer: 0
  Platform: tulip
  Version: 3.0.6
  Commit: 3050f2d
  Size: 258048 B
  Size: 252 KB
EC
  Type: RW
  Version: tulip-3.0.6-3050f2d
  RollbackVer: 0
  Platform: tulip
  Version: 3.0.6
  Commit: 3050f2d
  Size: 258048 B
  Size: 252 KB

```

I appreciate the hash’s may differ because of commit IDs, but I dug into the binaries a little with a hex editor and disassembler and they have more substantiate differences.
