Not all of the components can be updated using LVFS which is why it isn’t offered with this update on Linux.
Not quite true, I updated an ancient 6th gen Intel machine just 10mins ago using LVFS and there was a screen that notified me during the BIOS update that the Intel ME was being updated. There may be an issue with using LVFS to update Intel ME capsules but I suspect the issue lies with Framework more than LVFS.
From @Kieran_Levin
so
Its not LVFS. Its that our BIOS does not support self-updating the ME firmware.
For the system to update itself, it needs to have the updater for that specific firmware built into the BIOS that is already on it. 11-13th gen have only ever used external updaters for ME (whether that’s the Windows, Linux or EFI version of it).
It seems FW will update ME via its own capsule, if they provide that ability. A separate capsule for most firmwares. Just like each ReTimer has its own capsule, plus the main BIOS. On Core Ultra, ME is the 4th capsule.
Other manufacturers rather pack all firmwares into a single capsule and let the BIOS manage all of the separate parts internal to it, because that makes it easier to control all parts of the update at once. But that really does not change, that the updater needs to be already present in the BIOS to do that.
We do not know if they only provided half of integrated updater-functionality at first. And only got to doing it in later generations or some other reason (although I think that is probable, given how extremely resource constrained the updates have been). Also seems to be a toolflow problem for FW, as they claimed this ability was present since 13th gen device. But then, for the single official update they launched, they still did not use it and shipped the ME update with the external updaters.
LVFS involvement is that it only supports a limited amount of update protocols. Updating ME directly is not one of them, because every manufacturer does that as part of the BIOS and via capsule if they use LVFS at all (because capsules are OS agnostic and the most sensible way for any core firwmare). Also, BIOS version and ME firmware are tied together, which is why manufacturers want to update this together as part of the main BIOS update.
Confirming that 3.08d update was successfully installed on a Framework 13 - 12th gen. Followed the instructions to run the update, then run the re-timer.
USB disk used - FAT32 partitioned Integral with the contents of the 3.08d zip. Laptop is with 2 TB SSD, 16GB RAM, Linux Mint, no Windows partition. Hope that helps.
(Have had the 65W battery for almost 9 months now, decided to get it over with one way or another today… )
Successfully upgraded from the stock 3.04.
Needed to follow suggestions from a reddit post after I encountered an error of CapsuleApp: cannot find a valid sile system on boot devices.
The fix was to remove the -OD
option from the CapsuleApp.efi
line in efi/boot/startup.nsh
.
Everything seems fine after the upgrade. OS is Arch Linux.
@Kieran_Levin @Matt_Hartley Is the EFI updater ever coming out of beta with a stable version released at some point in the future? Or has it been abandoned altogether?
Please do not post no-content replies.
Framework stated that they will improve on the BIOS update front and will release more (security) updates in the future. I can’t find that statement. Has anyone an idea where to find it?
The claim was made here:
Specifically:
…
That was posted about a year ago.
While I understand the desire to have it on Linux, I don’t understand the unwillingness to use a Windows update it that is what is available.
I don’t have windows.
I already used the unstable EFI updater though, I’m good. I’m just hoping for framework to get their linux support all figured out so that I can buy a newer mainboard without feeling like I’m throwing money into an unsuported product again.
Got it, thanks for the reply. I usually am in Linux but have windows available for when I need it - edit to add, for some apps I use that only run on windows or that I am unwilling to try to run in wine, such as one to adjust various settings in my vehicles. I agree that it will be great to have this all available without needing to use Windows. Have a great evening.
I am totally fine with the EFI updater. I do NOT want to use Windows, since we use the TPM2 to protect the integrity of the system and to encrypt data. If Windows somehow changes the state of the TPM2, I get into a lot of trouble.
That’s not unreasonable. If the only way to apply a required update were via windows, I would go ahead and do so. I would be surprised if it fiddled with the tpm, but you are smart to be careful. It definitely loves to mess with the efi setup.
They have made these kinds of claims several times and for several years. Then they comfortably delete the old trail of post (such as the original post for 3.06 Bios Update for Linux). Its beyond any excuse and unethical behavior of Framework.
They even delete the post criticizing them and threaten to ban from the community.
Damn, went to check if there was any BIOS updates and landed here. I’m a big supporter of Framework but a beta BIOS for over a year on a product designed the last isn’t a good sign. I’ve skipped though the last 100 posts or so and I’m not sure if I even want to attempt updating with linux installed. I have a couple m.2 drives laying around, should I just boot up a fresh windows installation and update that way? Uhg.
Bios itself isnt beta anymore. but the efi installer might be? the windows one does work.
Id wish the update process wasnt as complex as they have to make it (thanks original parts manufactures. looks at intel why do I trust intel again?)
Unless you have the new battery, I don’t see the point in updating the BIOS and potentially bricking your machine. A machine with security holes is better than spending 2 months dealing with support for a dead machine.
Things that aren’t fixed with 3.08 (or 3.06 or as delivered)
- 400mhz throttling despite cool temps
- blowing out more battery in sleep that booted
- waking up from sleep while closed (and cooking itself)
- hot fingerprint reader
When are we getting the information that 12th gen is EOL? Classic bait and switch.
This depends on your use-case. If you do not do security critical stuff, ok, but a lot of people use there machine for e.g. signing builds, online banking, …