you can download the last artifact for your OS or you can build from source.
1 Like
Full Changelog?
1 Like
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
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
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
@NapalmCricket You can also download the corresponding .cab file from LVFS and install with fwupdmgr local-install.
Tried a fwupdmgr refresh --force to make sure you have the latest repo metadata?
i tried it didn’t work said there are no updates and I don’t want to do it using the usb way
@sydney Where would I download the .cab file (I am not really all that familiar with LVFS).
Version 0.0.3.9, click the “Download Archive” button below, or:
fwupdmgr local-install "location/to/cab/file"
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
Updated to 3.09 yesterday.
Limit at 65% and Extender enabled, it works fine!
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?
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).
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
Did you specify the correct location of the cab file? How did you download the cab file? What BIOS are you currently on?
I downloaded it directly via the link you provided above (with Firefox). I did specify the entire path to the cab file on the command line. I am on version 3.08 currently.
Did you try an absolute path? Is the cab file perhaps corrupted? I don’t know what else to tell you.. Perhaps an SELinux issue? checked the logs? Perhaps wait for the official release?
I tried redownloading it twice, and I did try an absolute path. SELinux not enabled on my laptop.
I updated from 3.0.7 to 3.0.9. That is the only difference i can see so far. Furthermore, there appears to be a unusual low success rate reported by LVFS for this version.
Most likely a typo as it’s tagged with bios instead.
1 Like