Awesome to hear that this is coming. I absolutely hate Winblows, and having to boot back to that to update firmware, BIOS, etc is the only reason I have not obliterated that pile of rubbish OS from every hard drive in the house.
2 Likes
Any estimate on the schedule for LVFS support would be very helpful. I am reluctant to mess with the bootloader at present, but I have no idea how long that will delay the BIOS update for me.
This recent tweet commented “We’re in the last stages of testing LVFS/fwupd”.
https://twitter.com/FrameworkPuter/status/1479137228349575171
9 Likes
Two months since the last hint mentioning “last stages of testing.” Any update on the schedule for LVFS support?
7 Likes
Also super stoked for this!
1 Like
I think this thread is the oldest about LVFS (with fwupd). So, I would like to use it as LVFS main thread. Maybe nrp’s comment below on 3rd March is Framework’s latest status about LVFS.
We’re working on resolving the issue on EFI boot entries getting cleared before we deploy through LVFS.
I don’t understand what is blocker now. But my idea is that Framework would share the details, and use a power of communities to fix the issue. You may find the domain specialist in the communities. This is an open source way, right (if it is possible)?
Another related thread: BIOS 3.06 on LVFS testing, but error trying to update under Fedora 35
4 Likes
It would be very helpful to have an update on the LVFS progress. I don’t see anything since January 2022.
1 Like
See Framework Laptop BIOS and Driver Releases (11th Gen Intel® Core™)
You need to enable lvfs-testing. As 3.10 (for 11th gen!) is out of beta now, perhaps they should move it to regular.
Also: be careful that the update process (both through LVFS and through EFI shell) need space on the EFI partition on the internal disc. At 100Mb, that partition is very sparingly provisioned. The presence of any remnants of other boot setups can be enough to have the update process fail without indication of what went wrong (you just won’t have updated firmware).
It looks like most linux disk formatting tools that come with distributions like Fedora are extremely reluctant to meddle with existing EFI partitions and get easily confused when there are multiple, so it’s quite possible to be stuck with the original 100Mb one even if you thought you made a bigger one.
I think Framework would save their customers a lot of possible pain (and perception of broken firmware update procedures) if they just provisioned 1Gb for the EFI partition on their premade systems.
1 Like
I am reluctant to enable testing, so I am mostly interested in the expectation for the stable channel.
6 Likes
Any updates on this?
Implemented in the testing channel.
11th gen:
2 Likes
Great! Do you know when it will be stable?
No idea, sorry.
Does “testing” in “lvfs-testing” refer to testing versions of the BIOSes there, or to testing the lvfs distribution channel?
1 Like
I’m pretty sure that Framework is using the “testing channel” of LVFS due to the imperfect state of the distribution channel itself. I have seen a number of announcements of BIOS versions that appear to be stable and which may be acquired through the LVFS “testing channel.” I suffer the same general confusion as you, and would welcome an authoritative description of the situation.
Right now when searching by “Framework Laptop” on the fwupd.org, I can see only the Framework Laptop 13 AMD is not testing state.
https://fwupd.org/lvfs/devices/work.frame.Laptop.Ryzen7040.BIOS.firmware
State stable
1 Like
What @junaruga has said is correct. For Ryzen 7040 Series, the the current state is stable as outlined here and here.
1 Like
I don’t see any updates for the 13th gen intel core Framework 13 on LVFS.
Are there any updates for 13th gen that just haven’t yet been uploaded to LVFS? (I didn’t find a place for them when looking at the main corporate site.)
Is LVFS now considered a first class mechanism for delivering firmware updates?
It appears that Framework simply hasn’t released any BIOS update for 13th gen, yet:
FWIW, you can get there via: BIOS and Drivers Downloads
They can’t distribute all the Intel proprietary blobs through lvfs right now and that is because of LVFS