Librem EC 1.14 Released

General Announcements
1

Changelog: https://source.puri.sm/firmware/releases/-/blob/master/changelog.md?ref_type=heads#librem-ec-v114-2025-11-21-feb850b

To update the Librem EC, follow the documented instructions: https://docs.puri.sm/Hardware/Librem_14/Maintenance/ec/upgrade.html

There are new features and bug fixes that are interesting such as keymap rebinding and a fix for batteries sometimes disappearing if they reached 100% charge.

6 Likes
2

Is there a way to receive email notifications of Librem-EC and PureBoot firmware releases?

Software App lists only OS updates, no firmware ones.

1 Like
3

From

the simple answer would seem to be “no” in terms of anything automatic.

However there is a more general Purism newsletter that you can subscribe to. (You would just be relying on the possibility that someone thinks it worthwhile to include an article or item in the newsletter.)

And there is the RSS feed of blog articles and development reports that you can subscribe to. (Ditto. And I think there are many who feel that the blog articles have become AI-generated and so unlikely to include the notification that you seek.)

In any case, those are the three mechanisms that I am aware of.

1 Like
4

There were no Purism newsletter or blog article about this EC release :frowning:.
There is a firmware category in this forum, but this post was not tagged for it…

I have no time to continuosly monitor this forum or changes in repository.

Since in PureOS there are no notifications about firmware updates, there should be a dedicated newsletter to this.

2 Likes
5

I’ve got replacement 3-cell battery. It was recognized by some old version of Librem EC. After this update the battery is not recognized by updated librem-ec-acpi on Qubes. The dmesg log says ACPI: battery: Slot [BAT0] (battery absent).

The battery is this one: Baterie kompatibilnĂ­ s Mechrevo CS-MRS100NB | Techtek
L14 keeps running when AC is disconnected.

Has anyone such issue? Any hints?

1 Like
6

Have Purism ever signed their firmware with some GPG keys to ensure that no tampering happened between their website and our installation? It doesn’t look like that. Here is how it should be done: Verifying signatures — Qubes OS Documentation

Sometimes they at least release sha256sum, which can’t really be verified reliably. But here even this is lacking. Can somebody independently confirm the sha256sum for this .iso?

sha256sum Librem_14_EC_Update.iso

db91dc2a2ef5b2f5ece6108f3237d78c5335703891a066aac96af76fdb83671f Librem_14_EC_Update.iso

7

Yes.

However that proves only that, with a very high degree of confidence, we downloaded the same file. (So, for example, it guards against undetected random errors in the file transfer to each of us.)

Note that the ‘correct’ way to verify a hash is to create a .txt file that comprises a single line, where that single line contains the hash, a space, an asterisk, the name of the file to be verified.

Let’s say that the file is called Librem_14_EC_Update.iso.sha256sum.txt

Then sha256sum -c Librem_14_EC_Update.iso.sha256sum.txt

That saves eyeballing the 256-bit hash to see that it is correct and, if preserved, would allow you to verify the integrity of your own copy of the file at any time in the future, at least against accidental change.

(If there is more than one line in the file then sha256sum -c will read each line in turn and verify the hash of a file.)

2 Likes