Framework Laptop 13 Ryzen AI300 BIOS 3.05 Release STABLE

Framework Laptop 13
,
1

Highlights

  1. Updated to UCSI 2.0 support.
  2. Update PD1 and PD2 firmware to v0.21.
  3. Added Framework’s dbx key.
  4. Corrected the help string description for the iGPU memory configuration.
  5. Fixed an issue where hardware encryption on OPAL drives could result in a missing boot drive after subsequent reboots.
  6. Fixed the issue preventing the Wooting 80HE Keyboard from working within the BIOS interface.

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
Framework_Laptop13_RyzenAI300_BIOS_3.05.exe EAA07A15EEFC410D2F58A7ACCBFED83F4ED559366DBED386A88CC4BD87D8D84E

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
Framework_Laptop13_RyzenAI300_BIOS_3.05_EFI.zip B8A61C554D31FFA7DE15F49B06D2C58E36107C00A9B7750C807922C4FF11C82D

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

N/A

Enhancements

  1. Updated to UCSI 2.0 support.
  2. Update PD1 and PD2 firmware to v0.21.
  3. Added Framework’s dbx key.

Fixes

  1. Corrected the help string description for the iGPU memory configuration.
  2. Fixed an issue where hardware encryption on OPAL drives could result in a missing boot drive after subsequent reboots.
  3. Fixed the issue preventing the Wooting 80HE Keyboard from working within the BIOS interface.

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.05 Updated
EC ec_305_9010bdf Updated
PD 0.0.21 Updated
AMD PI 1.1.0.0c Same

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

  • Setting TPM to hidden may cause systems with WD PC SN740 SSDs to get stuck in automatic repair during boot.
6 Likes
2

Thanks!
:white_check_mark: I just completed the update, everything went smoothly, no issues during the process, and the computer is starting up normally.

1 Like
3

Same as above. Everything went well during the update and appears to be working fine in normal usage.

4

Installed the bios update yesterday, now running a fresh install of Fedora 43 on hardware encrypted OPAL nvme (Samsung 990Pro).

So far, so good, LUKS with --hw-opal-only no longer renders the device invisible in boot menu.

5

FW13 here with AMD AI 350. Drive is a Samsung 990 EVO Plus 2TB. Gentoo linux, kernel 6.17.8

I have been using hardware encryption with this drive, unlocking it during boot. This has worked provided I added the kernel command line option “iommu=pt”. Without this option, the drive is not working correctly after resume from suspend.

With beta BIOS 3.05 I still have the same problem- it has NOT fixed that issue for me.

6

Hi,

How would “iommu=pt” have any affect on suspend/resume?
That setting affects a virtualisaion feature.

7

It also affects access to some cpu/gpu registers and stuff like usb4 pcie tunneling not just virtualization.

8

That would most likely be due to a bug in the linux kernel. Maybe not restoring iommu state enough before disk unlock.
I don’t use hardware disk encryption. After resume, does it ask for the disk password again? Is it a gui field for the password, or a terminal console screen?

9

Unfortunately after update, my Framework 13 no longer boots. See also: Boot problem after upgrade to BIOS 03.05

10

When I boot, the bios asks for the disk password. It resumes from s2idle suspend to the gnome login screen, not the bios unlock screen. This is the normal way hardware-encrypted drives work.

There are several posts on this forum about the issue with hardware encryption and suspend…that is where I found the iommu workaround.

I highly doubt this is a linux kernel issue, since for years I have used other laptops with hardware drive encryption and suspend under linux. It’s a basic function that should be expected to work on laptops.

12

The update went fine on my machine. The only quirk I now noticed is that the HSI level dropped from 3 to 1 due to a condition now not being met for HSI-2.

I started a thread with details/pics here: