Submit firmware to "Linux Vendor Firmware Service" (LVFS) for easy updating

Maybe some Linux users do not yet know the Linux Vendor Firmware Service. However, it’s a great combined effort (as per this whitepaper also on the site) to be able to update flashable devices in your devices, without having to boot Windows/Mac OS or so.

Well… in any case, what maters is that you get firmware updates on many Linux distros. Here e.g. with GNOME (thus it could also look like this in PureOS):


More information for end users are here. (screenshots also taken from there)

To get to the technical details, this whole thing depends on Purism. And, good news, actually they are already included in the vendor list on the site!
Bad news: They have not yet submitted any firmware updates there (last red column) and their statement there says:

Testing is in progress, hopefully done soon! 2017-08-15

So this statement is heavily outdated and you did not follow it by facts. So it would be great to hear the current state of this topic, and whether/when (hopefully the latter) you will upload firmware there.

Even major other vendors like Dell are better at this and regularly upload firmware there. So I would have expected that a Linux-specific vendor as you is at the top of that, too. :smiley:


Ugh, also saw an old thread that has received no reply about this topic:

So, really, Purism should comment on that…


If you have a look into the wiki, they’re still testing HEADS and don’t have coreboot in a state they wish to.
So maybe there’s a lot of work to be done, before considering an automated process like this?


Don’t even know if the BIOS is the only thing they want to update. But in any case there should be an update method. I mean even if there is work to do, people would otherwise need to flash updates manually, and that is inconvenient.
Also the update can be for “moving to HEADS” or so… don’t know the details and how/whether it is possible, but many other vendors are successful and fwupd includes great things like verifying applied updates after they are flashed and so on.

1 Like

I’v no doubt that this level of integration is complex to achieve. However, it would still be nice to get some visibility on what are they plans, roadmap etc…

Just so that we would have a clue about what we can/can’t expect regarding this.

1 Like

Hi everyone! This is definitely something that is active inside Purism. From what I understand we’ve already sent our updates upstream to LVFS and they have received our info. I’m looking into this internally and will post with more info as soon as we have it.


As far as I read on the site, it is fairly easy, as the whole system already supports a lot of things for flashing, verifying etc.

1 Like

I don’t want to assume bad faith here, but we’ve been hearing this “$something soon” quite a bit from Purism in the past years… First it was a:

Testing is in progress, hopefully done soon! 2017-08-15

on the vendor status page, and now it’s “we sent our updates to LVFS”… If the latter would have happened, we would see something similar to this page, with actual releases and updates…

Can we get another update on this? What’s keeping Purism from shipping coreboot updates the (now) standard way?


You’re right to send a reminder, thanks.

We’ve been in touch with upstream numerous times but there remain some details to work out. Frankly other work has come before this since it’s higher priority, but this work is delayed and not abandoned.


I’ll be a bit more specific about upstream’s requirements; they want flashrom to be usable from a tool called fwupd (firmware update). flashrom is only one of the packages that Purism contributes too, we modify things like coreboot and heads as well, so there’s lots of development going on and refactoring to using things like libflashrom has been a lower prio. Hopefully I’ll put it on the front burner once a couple issues that I need to resolve are complete.


If you have not bought yet, you cannot get anything but Evergreen, unless you find a recipient of Chestnut or Dogwood who is willing to sell it to you. Everything up to Evergreen is already claimed.

The newer models will have more refined hardware, with physical tweaks to CPU placement and thermal management. Firmware can’t change that.

1 Like

Will we ever get UEFI support? Like a tianocore package, that supports heads?

Have you thought about Christmas gifts for your users worried about running random shell scripts to update their coreboot images? :wink:

(In other words: any progress?)


Not so random.

I removed the “random” word, but I think the point remains.

1 Like

Indeed, a proper system integration is always better than any shell script. :smiley:

1 Like

Getting back to the LVFS topic some years later now… :sweat_smile:

In the meantime here is a thread about the same topic for the Librem 5:

In general, I don’t see much progress on this topic, however.
It would make updating firmware so much more convenient and even Dell XPS laptops support it, so you should really invest time in this IMHO! :smiley:

On the LVFS website it still says for Purism:

Testing is in progress, hopefully done soon! 2017-08-15

:heavy_check_mark: Has test account on the LVFS

Well… that’s not a lot of progress, is not it?

Especially since this was your last statement on this:

So, is there any update? This has obviously been requested for quite some time now…
And it would certainly make a great video, be it for the Librem 5 or any other device.

Note they now seem to have a nice dashboard for vendors and even consulting services are offered – should you need these.


I’ve been in touch with Hughsie a couple of times (maintainer of LVFS) but it’s never come together. I’ll make another effort beginning next week.


@jeremiah are there any progresses to report regarding LVFS support for coreboot firmware upgrades?

1 Like

There has been comments here:

Anyway, in my testing at least for the Librem Mini, nothing is available yet:

sudo fwupdmgr refresh
[sudo] password for admrugk: 
Updating lvfs
Downloading…             [*************************************  ]
Successfully downloaded new metadata: 0 local devices supported