Road to crimson

As discussed with @evangelos.tzaras let's have a meta issue (this only lists the things still todo, not all the things that have already been done):

• Switch image build to debos (pureos/infra/pureos-image-recipes!2)
• Continuously build recent unencrypted images using debos (replacine our vmdebootstrap ones for landing)
• complete gtk3 patches (Librem5/debs/gtk#38)
• Use u-boot via deb (from there on we can deprecate arm01)
• crimson artwork (#334)
• backport core libs
  • gtk 1.12
  • libadwaita 1.4
  • wlroots 0.17.0 (no issue yet)
• Sort out pulseaudio vs pipewire
• pipewire echo cancellation
• continuously build encrypted images too
• here we could release an alpha/beta variant (depending from what's still open from the issues below):

Issues tagged crimson:

• Librem5 space
• PureOS core
• PureOS packages

Other bits:

• Test upgrade path from Byzantium
• sync issues

changed the description

How do we use u-boot via deb if it has binary blobs in it ?

1. wget https://<url-to-artifact-of-latest-stable-tag>
2. dpkg -i uboot-imx_*.deb
3. run u-boot-install-librem5
4. dpkg --purge uboot-imx

Ok so not hosted in PureOS. Just installed from a deb.

That would work for image building. We'll still need the raw imx file for initial bootstraping of the device.

yes, but these can come out of the same ci pipeline.

changed the description

changed the description

added crimson label

changed the description

changed the description

changed the description

Some notes as this came up in private and public matrix conversations:

• I had backported the versions of phoc (0.33.0), phosh (0.34.0), phosh-osk-stub (0.34.0) and phosh-mobile-setting (0.34.0) that didn't require any library bumps. So if these are deemed o.k. (they're ~6 mo behind) then the additional library backports (gtk4 4.12, libadwaita 1.4, wlroots 0.17) can be skipped in the above list. Crimson would then be ~6 mo behind but that's still better than byzantium (~1y behind). Updating those libs is then still possible during the crimson cycle (with the potential of e.g. a wlroots update breaking other compositors (sway, wayfire¸…) which might upset users. The alternative would be to drop possibly affected reverse dependencies upfront.
• The pipewire switch could be skipped and postponed to dawn as could then be pw echo cancellation
• Matthias has addresses multiple sync issues in the meantime

The pipewire switch could be skipped and postponed to dawn as could then be pw echo cancellation

Since the use case of the Librem5 (at least for me) does involve a long uptime this debian bug could hit Librem5 users as well as me on my Librem14 running Crimson.

Since I don't see this issue pointing to any sub issues on PA vs Pipewire, I'll document my findings here in case another soul wants to try upgrading to crimson.

After updating sources.list to crimson and doing dist-upgrade, I had no modem audio. The journal was not super helpful, but there were some pipewire errors. So, the first thing I did was to switch back to PA.

systemctl --user mask pipewire pipewire-pulse pipewire.socket pipewire-pulse.socket wireplumber
systemctl --user enable pulseaudio

Still no audio with PA. Digging deeper, I found that crimson needs a newer alsa-ucm-conf.

There is a newer version in http://repo.pureos.net/pureos/pool/main/a/alsa-ucm-conf/ , 1.2.11, but I did not dig enough to find out what repo that is in because the deps are not clean. I just installed the master copy from https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2.

Now, modem audio is working again. This may well have worked without switching from pipewire.