Framework Laptop 13 Ryzen 7040 BIOS 3.16 Release STABLE

Framework Laptop 13
,
21

Presumably something to do with hexadecimal vs decimal.

3.10 in hex = 3.16 in decimal.

That doesn’t explain why they didn’t use 3.0A for example, which would be 3.10 in decimal.

22

That doesn’t really explain it to me. If the internal numbering is hex then internally it would be 3.0A next which doesn’t in any way translate to 3.16.
Maybe they kept adding things and building new versions to test internally but extra things to add kept appearing before internal testing had finished.

23

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.

1 Like
24

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.

1 Like
25

I found something called FrameworkComputer.framework_tool but which downloads as framework_tool.exe.

The requirement for elevation seems largely fake.

The ectool.exe I had found before does some of the same things without elevation.

It’s right that this kind of meddling with the hardware must be restricted to things with elevated privileges, but simply making the command demand elevated privileges isn’t really the way to do it!

Surely the driver should be built so that only software with elevated privileges has access? If I’m correct, it’s barely providing any protection the way it is.

1 Like
26

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

1 Like
27

Thanks. Sorry, I re-edited my message after you replied but before I saw your reply.
It was mainly because I realized it DOES have built in help.

28

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.

29

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).

30

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

1 Like
31

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.

32

Very excited for this part!

2 Likes
33

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
1 Like
34

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

35

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

36

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

37

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.

1 Like
38

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

39

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?

1 Like
40

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.

3 Likes