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.
1 Like
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.
3 Likes
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.