Framework Laptop 13 Ryzen 7040 BIOS 3.20 Release STABLE

Framework Laptop 13
, , , ,
21

I’m not on the latest BIOS yet, but I can confirm this behavior in my standalone 7840U. Installing the RTC battery available from the Framework marketplace resolves the issue.

1 Like
22

Thank you for that confirmation.

The thing is, it’s able to remember everything else through complete power loss. It remembers that I disabled TPM. It remembers my max battery charge level. And so on.

Why can’t it remember the simple Auto/Game setting for the UMA?

23

Have you reported it here:

1 Like
24

Someone with a bricked device should also report the issue on GitHub, otherwise this may not get the needed attention.

25

Just reported it.

3 Likes
26

Updated 7840U board from 3.17 → 3.20 via lvfs on f44 with no problems, just took awhile.

27

Updated 7840U board from 3.18 → 3.20 via lvfs and… it get stuck at two blue dots :sad_but_relieved_face:

I can now follow the BIOS update stuck thread…

1 Like
28

Did you have the RTC coin cell installed. If not, the iGPU UMA setting reset could be the result of memory training.

29

Ok I successfully fixed it myself thanks to the following community guide:

1 Like
30

This just happened to us when upgrading from BIOS 3.18 (one of the few, most remained on 3.17) to 3.20. We’ve already updated 10 machines without issue, but number 11 locked up during the BIOS update and now the laptop is bricked.

1 Like
31

What do we know about the bricking? Does it only occur while upgrading from 3.18?

My Laptop 13 at work is still on 3.17, and my private one is on 3.19, and I’m afraid to upgrade to 3.20.

1 Like
32

I upgraded from 3.16 to 3.20, no problem during the process. Either the bricking rate is higher from 3.18, or it’s irrelevant of version as most computers were 3.18 before flashing 3.20

1 Like
33

So I’m holding upgrading to this version given the issues some people have had bricking their laptops, which I think never occurred before. Do we know if this is happening only on laptops with Linux or it has nothing to do with the OS?

2 Likes
34

went straight from 3.19B ( because i was not going to have my laptop not connect to my KVM for my convinience) to 3.20, no issues whatso ever ( although i did not have any USB connected to the laptop when i initiated the upgrade.

35

Reading this thread, I think i’ll skip this version since I’m out of warranty :slightly_frowning_face:. Who knows what would happen if i decide to roll the dice.

3 Likes
36

Does anyone relate to this issue? Framework 13 AMD 7840U freeze on Linux kernel 7.0.0 and 7.0.1

I notice it happens occasionally, unexpectedly on my system these days :face_with_diagonal_mouth: kernel 7.0.11

37

This is an absolutely insane situation. Given all the random bricking, nobody should be upgrading to BIOS 3.20.

Framework should immediately withdraw BIOS 3.20 from circulation and revert to 3.18 as the latest stable release.

BIOS 3.20 should be treated as radioactive material.

On top of that, refusing to replace out-of-warranty bricked mainboards because of a faulty BIOS is very poor form. If you’re providing BIOS updates for your own hardware, you’re setting up a perfectly reasonable expectation that the BIOS upgrade is guaranteed to work on that hardware. Otherwise there is really no point in providing BIOS upgrades.

Reading the " BIOS update stuck " thread is essentially a horror story. Users should not resort to hardware hacking to fix a fault caused by Framework. No reputable company would allow this dumpster fire to continue.

CC Matt_Hartley

5 Likes
38

Does anyone relate to this issue? Framework 13 AMD 7840U freeze on Linux kernel 7.0.0 and 7.0.1

I had this problem on 7.0.0 and 7.0.1, but not since. Now on 7.1.6 and no problems.

39

I contacted support regarding bricked out of warranty mainboards caused by Framework’s bios, and received this response:

“If your device is out of warranty, we will still review the case, but coverage for replacement or repair cannot be guaranteed.”

This essentially means you’re on your own if a BIOS update fails.

@Quin_Chou Would it not be appropriated to clearly state in the first post that if you update your computer with this official STABLE BIOS and it bricks your device, Framework will not cover the repair?

Also, if I understand points 1 and 2 in the changelog correctly, I need 3.20 to upgrade my non-Pro laptop with Pro components. Does this mean my two year old laptop is now effectively EOL? How does this align with Framwork’s mission statement?

3 Likes
40

Updated through LVFS and no issues seen. Well I avtually already updated in the beta period

1 Like