Framework Laptop 13 Ryzen 7040 BIOS 3.16 Release STABLE

[lbkNhubert]

Right, that’s why I noted that my comment does not explain why they didn’t use 3.0A. I’m just guessing, but my best guess is that there was a hex vs decimal discrepancy somewhere along the line, and they are unable or unwilling to use hexadecimal letters in the numbering scheme. Seems odd. Unless we get an official response from someone at Framework we may never know, just like we may never know how many licks it takes to get to the center of a tootsie pop.

[TheTRUEAsian]

What I did is first use the 2.05 driver bundle. Then use winget to install the framework tool. Afterwards, use CMD as admin to run the tool.

[jhoff80]

Looks like it’s at: framework-system/EXAMPLES.md at v0.4.5 · FrameworkComputer/framework-system · GitHub

[jhoff80]

Has anyone else seen random reboots a few seconds after coming out of sleep on this BIOS, or is it just me? I initially saw it when Logi Options+ was trying to upgrade, but I’ve uninstalled that and I’m still seeing it.

I’m going to downgrade to 3.09 and see if it goes away.

[Will_Nilges]

Uh oh, is this issue back? There are some troubleshooting steps in there you might try (Are you on Linux? I think some of them actually got mainlined but I can’t find the patch right now).

[Quin_Chou]

It is for hardware bitlock issue. You can refer to below links.

Cannot boot from partially locked self-encrypting drives

Unable to boot from write-locked OPAL SED SSD

This is a pretty specific case and something the development team likely would love some feedback and specifics to help them narrow down what is going on to prevent the reading of a partially locked drive. The best place to log this and submit information is here.

Issues enabling BitLocker hardware encryption (Windows Encrypted Hard Drive) on AMD 7840

Well, I had more the luck the second time, using the Samsung Secure Erase tool & enabling BitLocker via the command line I was able to get it to the point it was using hardware encryption. Unfortunately on the next boot it failed POST saying it couldn’t find the boot device. I believe that’s the same result others have seen attempting the same. I think we’re stuck until this is addressed by Framework with a BIOS update. [PXL_20231105_042224618] [PXL_20231105_042443110]

[jhoff80]

On Windows, not Linux. Unfortunately I don’t really have the time right now to troubleshoot to see if it’s the BIOS or some other conflict, so I’m already back on the release firmware and hoping it goes away again.

[iridris]

@Quin_Chou

Introduced the Framework EC device.

Very excited for this part!

[kirelagin]

Before update:

  Build version:  azalea_v3.4.113385-ec:c25dec,os:7b88e1,cmsis:4aa3ff 2025-04-14 01:55:38 marigold1@ip-172-26-3-226

├─AMD Ryzen 7 7840U w/ Radeon 780M Graphics:
│ │   Device ID:          4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ │   Current version:    0x0a704107
│ │   Vendor:             Advanced Micro Devices, Inc.
│ │   GUIDs:              2a1df9de-fe02-59c8-8af1-32c8bb011f94 ← CPUID\PRO_0&FAM_19&MOD_74
│ │                       5a4bca32-6547-584f-bb36-920d9adede25 ← CPUID\PRO_0&FAM_19&MOD_74&STP_1
│ │   Device Flags:       • Internal device
│ │ 
│ ├─AMD Radeon 780M:
│ │ │   Device ID:        83eba1fa14bdefee1f6b4bcf06069b298e1c338f
│ │ │   Summary:          AMD AMD_PHOENIX_GENERIC
│ │ │   Current version:  1
│ │ │   Vendor:           Advanced Micro Devices, Inc. [AMD/ATI] (PCI:0x1002)
│ │ │   GUID:             4a1501b7-b500-5255-9d9c-41d652a4d5bc ← AMD\113-PHXGEN
│ │ │   Device Flags:     • Internal device
│ │ │                     • Can tag for emulation
│ │ │ 
│ ├─Secure Processor:
│ │     Device ID:        c54ab0237d7a8db8c717b68e0be78e4374a2a079
│ │     Current version:  00.2d.00.7d
│ │     Bootloader Version: 00.2d.00.7d
│ │     Vendor:           Advanced Micro Devices, Inc. (PCI:0x1022)
│ │     GUID:             9eb6a793-7f97-5fb5-b49c-139d2ce3ee46 ← PCI\VEN_1022&DEV_15C7
│ │     Device Flags:     • Internal device
│ │                       • Can tag for emulation
│ │   
│ ├─System Management Unit (SMU):
│ │     Device ID:        db0330716216c629bb2c07256e5d018f499eb6ce
│ │     Summary:          Microcontroller used within CPU/APU program 0
│ │     Current version:  76.87.0
│ │     Vendor:           Advanced Micro Devices, Inc.
│ │     GUID:             3ac3159e-6eef-5f6b-bc8d-67686b238747 ← /sys/devices/platform/AMDI0009:00
│ │     Device Flags:     • Internal device
│ │                       • Can tag for emulation

After update:

  Build version:  azalea_v3.4.113388-ec:cf6b79,os:7b88e1,cmsis:4aa3ff 2025-07-16 02:38:38 marigold1@ip-172-26-3-226

├─AMD Ryzen 7 7840U w/ Radeon 780M Graphics:
│ │   Device ID:          4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ │   Current version:    0x0a70410a
│ │   Vendor:             Advanced Micro Devices, Inc.
│ │   GUIDs:              2a1df9de-fe02-59c8-8af1-32c8bb011f94 ← CPUID\PRO_0&FAM_19&MOD_74
│ │                       5a4bca32-6547-584f-bb36-920d9adede25 ← CPUID\PRO_0&FAM_19&MOD_74&STP_1
│ │   Device Flags:       • Internal device
│ │ 
│ ├─AMD Radeon 780M:
│ │ │   Device ID:        83eba1fa14bdefee1f6b4bcf06069b298e1c338f
│ │ │   Summary:          AMD AMD_PHOENIX_GENERIC
│ │ │   Current version:  1
│ │ │   Vendor:           Advanced Micro Devices, Inc. [AMD/ATI] (PCI:0x1002)
│ │ │   GUID:             4a1501b7-b500-5255-9d9c-41d652a4d5bc ← AMD\113-PHXGEN
│ │ │   Device Flags:     • Internal device
│ │ │                     • Can tag for emulation
│ │ │ 
│ ├─Secure Processor:
│ │     Device ID:        c54ab0237d7a8db8c717b68e0be78e4374a2a079
│ │     Current version:  00.2d.00.86
│ │     Bootloader Version: 00.2d.00.86
│ │     Vendor:           Advanced Micro Devices, Inc. (PCI:0x1022)
│ │     GUID:             9eb6a793-7f97-5fb5-b49c-139d2ce3ee46 ← PCI\VEN_1022&DEV_15C7
│ │     Device Flags:     • Internal device
│ │                       • Can tag for emulation
│ │   
│ ├─System Management Unit (SMU):
│ │     Device ID:        db0330716216c629bb2c07256e5d018f499eb6ce
│ │     Summary:          Microcontroller used within CPU/APU program 0
│ │     Current version:  76.96.0
│ │     Vendor:           Advanced Micro Devices, Inc.
│ │     GUID:             3ac3159e-6eef-5f6b-bc8d-67686b238747 ← /sys/devices/platform/AMDI0009:00
│ │     Device Flags:     • Internal device
│ │                       • Can tag for emulation

[sydney]

Thanks a bunch, friend. And have a nice day!

[knewman]

Easy update on Bluefin via fwupdmgr, no issues encountered so far - appreciate the work on this!

[Matthew_Shapiro]

also installed and runs fine in Manjaro Linux (latest kernel, unstable branch_

[Russ_S]

Fedora 42
Laptop 13 (AMD Ryzen 7040Series)
Kernel 6.15.9-201.fc42.x86_64
KDE Plasma 6.4.4

I updated BIOS to 3.16. No issues at all.

[jhoff80]

@jhoff80

Has anyone else seen random reboots a few seconds after coming out of sleep on this BIOS, or is it just me? I initially saw it when Logi Options+ was trying to upgrade, but I’ve uninstalled that and I’m still seeing it.

I’m going to downgrade to 3.09 and see if it goes away.

Still getting reboots on 3.09 so I don’t think it’s related to 3.16 at least.

[Yarko_Tymciurak]

Just installed – and after sleep/terminal lock, 2nd monitor doesn’t restore, not seen in “settings”

–

Operating System: Ubuntu 24.04.3 LTS
Kernel: Linux 6.12.42-061242-generic
Architecture: x86-64
Hardware Vendor: Framework
Hardware Model: Laptop 13 AMD Ryzen 7040Series
Firmware Version: 03.16
Firmware Date: Fri 2025-07-25
Firmware Age: 3w 1d

–

Running mainline kernel > 6.10

Will reboot in a minute, see what happens…

Reboots OK, both monitors showing; allowed to time-out lock again, and is 0K. A first time sleep event w/ new BIOS?

[Quin_Chou]

To address the hexadecimal vs. decimal conflict between ERST and the Linux version, we jumped from version 09 to 16. This explains why the BIOS is 3.16, not 3.10.

[SuperTux88]

They skipped 10-15 decimal (hex 0A-0F), and this is now 16 (hex 10) … so if you write this versions as hex, it would go from 3.09 to 3.10. So it kinda makes sense?

[dimitris]

Just another “all seems good” report here, running Fedora 42 Workstation.

fwupdmgr get-updates was offering both the BIOS and the dbx database update. To get around the efivars filesystem being full issue I updated only the BIOS with

fwupdmgr update <GUID for BIOS update shown in get-updates output>

After the update the machine booted up normally. Then the graphics got in a funky state but it seemed related to my Thunderbolt dock and/or external display. After a hard reboot, the machine was fine. I then performed the efivars workaround from the github issue above (reset Secure Boot config to factory defaults) and things seem normal, including:

$ df -h /sys/firmware/efi/efivars/
Filesystem      Size  Used Avail Use% Mounted on
efivarfs        148K   49K   95K  34% /sys/firmware/efi/efivars

The (new BIOS) Secure Boot factory defaults include the updated dbx so fwupdmgr get-updates shows everything up to date now.

[JL_Framework]

Indeed. Waiting for BIOS updates - to fix problems - is . . one thing. For there to be confusion about which BIOS is which . . seems desperate.

Framework’s recommended way of determining BIOS version reports ‘Version: 03.09’ on my Linux system; but fwupdmgr offers me no update to that version.

[Bram_De_Smet]

Same for me. No updates using fwupdmgr