It should not unless you use Gnome-software for the updates. Just using terminal and dnf won’t do fwupd updates.
I just tried setting the --fast-limit as an example, and that worked fine. So ryzenadj doesn’t seem entire broken.
1 Like
Our priority is to release a fix to the stable version before the end of March. Subsequently, we plan to implement a security fix, and work on this is underway.
8 Likes
So you just pushed back the release of the new BIOS version a few days after it was released and gave us absolutely no info on it, just edited the post title and that was it?
5 Likes
That’s a global update, not Framework specific.
1 Like
They held it because of an issue where the battery charge limit set in the BIOS isn’t honored and the battery will charge to 100%. They mentioned this here and in the threads for the BIOS for other machines, which were discovered to have the same issue.
1 Like
It’s just hit Linux LVFS (non-testing) too… is that the broken version as first posted or a fixed one ?!?
1 Like
I’m sure it’s the same version with broken charge limit that is now listed in this thread as held even though it’s available on the official support page.
3 Likes
It’s a mess. The issue was identified BEFORE it was pushed out as stable, but Framework still pushed it out. They then sent a mail out to say there is a new stable release, and the support page still shows it as the latest stable. BUT it is marked as held (rightly) on the first post of this thread. Again, this battery charge limit might not be super critical, but this shows that Framework have no rigour or discipline around quality control and release process of their software.
14 Likes
So, let’s recap this mess:
- 3.06 beta was released on November 21
- 3.06 beta had issues with the battery extender
- On December 5 the team announced the 3.06 beta was being held and would not be promoted to stable
- On December 6 the team announced that the target for 3.07 beta was the end of December
- On March 5, 3.07 beta was released
- On March 13, 3.07 was promoted to stable, and an email was sent
- On March 14, 3.07 was released on LVFS (where afaik it’s still available)
- On March 15, the team acknowledged issues with the battery charge limit in 3.07, and announced that a fix will be released before the end of March
- On March 20, the title of this announcement was changed, adding the word “Held”
But hey, they made a desktop for gaming and AI, so the investors must be happy now!
15 Likes
And soldered RAM 
1 Like
should be: ‘would not be promoted to stable’, i.e., would not become a proper - non-beta - release.
2 Likes
I think there may be another regression in 3.07 where charging from low-power PD sources is no longer working or not working as well. In 3.05 I was able to charge slowly from 18w and 20w PD devices even when using the computer for light tasks, but in 3.07 the charge is not happening or is imperceptibly slow. I can sometimes see the charging widget in the task bar intermittently switching from charging to not charging.
E: on further use I am not sure this is a regression-- I think the charging isn’t happening or intermittent when the power draw exceeds the low power charger, like when decoding a YouTube video or playing a game. I’m not sure if this is how it behaved in 3.05. When doing ultra light tasks the laptop is charging (slowly) as before.
3 Likes
How is that related to anything bios?
It expresses anger about what many of us here take to be Framework’s priorities.
EDIT: The priorities at issue comprise the valuing of new products over doing the right thing by current customers. The latter in turn includes: producing BIOSes in a timely manner; not pretending that BIOSes are in working order when they are not; and not producing BIOSes that contain serious bugs (or at least not doing so in combination with lateness and lack of transparency).
9 Likes
I didn’t realize that a Bazzite system update also extended to BIOS updates… I wish it had been more clear about that given others concerns about this. I’m surprised it hasn’t been pulled from LVFS considering it’s broken.
My charge limit is broken, like everyone else, but what’s even worse is that my precarious arrangement with my ThinkPad Thunderbolt Dock is now completely broken. Previously, I could get it to connect properly only in the exact following scenario:
- USB-C expansion card in the lower right slot
- The cable orientation mattered; in one orientation it alternated between connected and disconnected every half a second, in the other direction it connected correctly.
Now it does not connect at all anymore, I cannot get display output no matter what I do.
3 Likes
Honestly, that’s pretty weird in general considering that the lower right slot (while it does supoprt video out) doesn’t actually support USB4/Thunderbolt.
Indeed. I’ve never gotten the dock to work over Thunderbolt, forcing a downgrade to DP-Alt mode only was the only way to get it working before this BIOS update.
I agree with this. I’ve been a Framework Customer since my 11th gen Intel (12/2021 Batch 6), and have done significant investments / upgrades in my Framework equipment, 1. to address my needs 2. to help the company. But the BIOS issue and quality control have been an issue. Prioritizing new product launches makes sense from the perspective of maximizing profits, but the goal of the company is also to make modular, re-usable products/components, and not produce waste. I have to admit some of these products do seem wasteful and it seems that a bunch of the components are not even compatible across the product line (maybe just the expansion cards?). I opened a new support request due to my relatively new (November 2024) AMD Ryzen 7040 board having a dead port on the bottom left. Back when I was on my 11th gen Intel, I was on that board for about 2 years, and always had issues on and off with the ports, I thought it was because my OS didn’t support the ports (FreeBSD), but it turned out that it was actually the Mainboard being faulty. It got to the point where essentially 3/4 ports were dead or had major issues. So I’m a bit irrirated to be experiencing similar issues with one of the ports on a Mainboard that’s three generations ahead (11th Gen Intel → AMD Ryzen 7040 - if you count 12th gen, 13th gen, and then AMD (as oppose to Intel Ultra Core) as a generation jump), 3-4 years later. I’m a big framework supporter and will continue supporting the company since the values and ideals the company is striving for are important for me, and I do believe in supporting the company. I understand there are growing pains for sure. But I believe it’s ok to express my frustration and concerns.
For now I’ll stay on 3.05.
4 Likes
Which Linux distro are you using?
Kali with a Windows 11 duo boot
Which release version?
Rolling release, last date updated 24/03/2025.
Which kernel are you using?
6.12.13-amd64
Which BIOS version are you using?
3.05
Which Framework Laptop 13 model are you using?
AMD Ryzen 7040 Series
I’m trying to install the BIOS update but when I run the last command (fwupdmgr update) I’m told /boot/efi does not have sufficient space:
