Librem 15v4 and non-free Purism repo for microcode

I have a Librem 15v4 currently running PureOS 10 that is up to date:

$ uname -a
Linux librenomad 5.10.0-33-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03) x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: PureOS
Description: PureOS 10 (Byzantium)
Release: 10
Codename: byzantium
$

I know it’s a long time, but since 2024-05-09 when doing an apt update I get this message:

Err:8 https://deb.puri.sm/pureos green InRelease
Could not handshake: Error in the pull function. [IP: 138.201.183.165 443]

Looking in the apt sources files:

$ cat /etc/apt/sources.list.d/purism.list
# non-free Purism repo for microcode
deb https://deb.puri.sm/pureos/ green non-free contrib
$

Question #1: Is there a new repo for the microcode?
Question #2: If not, should I just delete purism.list ?

Thanks to anyone who knows the answer!

2 Likes

I was never aware of a non-free offering from Purism. My Librem 14 (different model than yours) doesn’t have any files under /etc/apt/sources.list.d/, and I don’t immediately see anything that looks like a non-free offering under repo.pureos.net, so I’d say just delete purism.list

1 Like

Thank you! The Librem 14 is a few years newer than the Librem 15, which came with this back in early 2019. It’s got a different Intel CPU than the 14, so I’m looking for official guidance from a Purism guru on this. :sunglasses:

BTW, I have several other files within source.list.d that point to repos of other software packages, including Mozilla Firefox, Proton VPN, and Signal Desktop. That’s needed if you want software that way, which I do.

I’m well aware of Purism Support, which I’ve used since 2018, but lately they’ve not been responsive, which is why I’m asking here.

1 Like

You may have better luck emailing support@puri.sm then, as these forums are mostly community-driven (though Purism staff do occasionally interact)

1 Like

I also have a Librem 14 and a Librem 5 USA, so plenty of Purism hardware. :sunglasses: A friend has a Librem Mini, one of the very first ones, and he likes it a lot.

1 Like

Then Purism Support is the only option.

No matter how knowledgeable, a rando in a forum is not official.

If it were my computer, I would make sure that I had a working Live Boot USB and I would make sure that I had a good dd backup … and I would just go for it :wink: i.e. comment it out - adding an extra comment about when and why I was making a change.

Assuming that “microcode” means “CPU microcode” then microcode updates are fairly infrequent anyway. If you ever hear of Intel releasing (yet another patch for dodgy microarchitectural side-channel attacks, er) something, you can always turn your attention back to finding whether and how Purism is packaging the microcode.

1 Like

These come with coreboot on Librem laptops: Firmware: coreboot 4.18-Purism-1, PureBoot Release 24

3 Likes

2 posts were split to a new topic: Getting an up-to-date Debian

Excellent! Exactly the info I was looking for. Thanks!

1 Like

Thanks, I should have left out the word “official”, but I got that anyway because the coreboot/PureBoot URL is official, and as soon as I saw the details I had what I needed. :sunglasses:

1 Like

You might run into this issue then:

1 Like

Thanks, I don’t have a Librem mini V2, but a friend has a mini V1.

1 Like

The issue I mention there is related to the update script and how it attempts to build a third-party tool from source if the tool isn’t found, so it theoretically could happen on any device, but it only manifests along certain branches of the script. So it’s totally possible to still have the script work for you. I just wanted to point out the possible issue in case you did run into it

1 Like

Thanks, I’ll check it out. It’s time to see what any Purism guys working on coreboot & PureBoot are doing.

1 Like