Framework Laptop 13 Ryzen 7040 BIOS 3.09 Release BETA

Framework Laptop 13
,
22

Are you able to clarify the expected relationship between the charge limit and the battery extender? Does having a charge limit override and effectively disable the battery extender?

23

So update seems stable?
I am eager to update but I know it’s still BETA😅

24

the charge limit is the maximum charge % the battery will be allowed to reach, not the minimum, so yes set it to 75%

1 Like
25

how do i get ectool on linux mint?

26

Fedora 42 - updated via LVFS-testing to 3.09
Enabled both charging limit and battery extender and set the limit to 80%
Everything looks good so far. Charging limit is respected and status shows as charging.

1 Like
27

you can download the last artifact for your OS or you can build from source.

1 Like
28

Full Changelog?

1 Like
29

Updated the BIOS to 3.09, and the charge limit functionality appears to be working as intended with the charge limit set to 80%. I have the “battery extender” feature disabled as it’d be redundant with this charge limit, so I haven’t tested if it works correctly with both features enabled.

2 Likes
30

I just updated to 3.09 and things look fine for now. I didn’t touch the battery settings, and BIOS kept my 80% charge limit. The battery extender was already disabled, to work around the bug in 3.08, and I didn’t test enabling it.

The update did change my default boot order, though. I had to do the update from Windows (fwupd wouldn’t work because my UEFI partition is too small), and after rebooting, Windows had moved to the top of the boot order list. This is the first time this happens (have upgraded BIOS from 3.03 to 3.05 to 3.08 before). No biggie, but it took me a while to figure out that I had to disable the “auto” boot order option to be able to go back to my previous default.

2 Likes
31

I am trying to update via LVFS (I enabled lvfs-testing as suggested in the instructions), but it is saying no available firmware updates. I have updated via LVFS in the past.

1 Like
32

@NapalmCricket You can also download the corresponding .cab file from LVFS and install with fwupdmgr local-install.

33

Tried a fwupdmgr refresh --force to make sure you have the latest repo metadata?

34

i tried it didn’t work said there are no updates and I don’t want to do it using the usb way

35

@sydney Where would I download the .cab file (I am not really all that familiar with LVFS).

36

Version 0.0.3.9, click the “Download Archive” button below, or:

https://fwupd.org/downloads/9a9b6b23623227b1a2b5906030de4a1c08990ef3b57a65df101dab6ea4169b47-Framework_Laptop_13_Amd_Ryzen7040_fwupd_3.09.cab

fwupdmgr local-install "location/to/cab/file"
37

Thanks for the link, though for some reason it doesn’t like it:

fwupdmgr local-install 9a9b6b23623227b1a2b5906030de4a1c08990ef3b57a65df101dab6ea4169b47-Framework_Laptop_13_Amd_Ryzen7040_fwupd_3.09.cab
Decompressing…           [                       \               ]
System Firmware [1e4fa9cea0b89e613370cf9657ffa0b6d3f37fec] is not updatable
38

Updated to 3.09 yesterday.
Limit at 65% and Extender enabled, it works fine!

39

Well, i don’t know what to tell you. I just updated this way..

Did you specify the correct location of the cab file? How did you download the cab file? What BIOS are you currently on?

40

I’ve found that the battery must be charging. It’s a weird thing, but it won’t start unless the charger is detected to be charging the battery, not just connected. So if the battery is full, or at your set charge limit, disconnect the charger and wait for the battery percentage to drop a bit. Then plug in the charger and do the LVFS update again, and it should find the update (assuming you have the testing branch enabled and have forced a refresh).

41

Agree. @Quin_Chou once stabilised change log should also include the delta between previous stable (3.05) and current so that those updating directly from previous stable know exactly what has changed.

4 Likes