ahh, so no from the landing.
1 Like
squeekboard 1.43 is here!
3 Likes
Will try this tonight after flash the crimson. I am going to give a try from pmos, ha. Do I need to run the same commands for the sound issue and the phosh issue after I update?(Kdb, and those three sound configure commands)
2 Likes
Nice to see that you are interested!
No, you should not use any recipe from Byzantium thread, please follow to another readme related to Crimson backports.
The sound issue is discussed here. I did not try this solution as I’m waiting for official updates and do not use Crimson as a daily driver yet, just a second OS.
2 Likes
sms/mms is working for me, but no sound on the call, more the mic is working even after I tried the fix on that link. Might try crimson later ha.
1 Like
gnome-settings-daemon 47.2 is here!
Now I’m able to connect my google account to sync contacts and calendar. 
2 Likes
phosh 0.45.0 is out
3 Likes
I think you should reconsider your storage option away from Codeberg, or at least request permission for these resources; If permission was granted, I think updating the README to clarify this would be prudent… Codeberg isn’t designed to be used as a file store and has a cost to their infrastructure. At the time of writing this, the librem5-crimson-backports repo is consuming around 2.9 GiB, more than they normally allow per project (which is 750 MiB for Git storage and 1.5 GiB for packages, LFS, and attachments). With the recent DoS attacks, I really don’t think it would be moral to burden the Codeberg team with this.
6 Likes
Phosh 0.45 is here!
2 Likes
Phosh 0.46 is here!
4 Likes
Thanks. You re a HERO!
galilley-Level
sent from ibm-power9
2 Likes
Chromium 126 (legacy)
This is the last version that woks well on Librem5 (etnaviv). The newer ones do not show elements of a lot of websites correctly. To install it remove the installed new version first and select this version from the repo:
$ sudo apt install chromium=126.0.6478.182-2~legacy chromium-common=126.0.6478.182-2~legacy chromium-l10n=126.0.6478.182-2~legacy chromium-shell=126.0.6478.182-2~legacy chromium-driver=126.0.6478.182-2~legacy
Next hold it to prevent further updates:
$ echo "chromium hold" | sudo dpkg --set-selections
1 Like
Clapper 0.8.0
taking into account the previous commit with patched mesa, it should work fine with workaround discussed here.
1 Like
Recently I’ve upgraded a lot of packages to achieve the Byzantium backports to update it further. This set of packages includes the support of L5 cameras by libcamera. So, this thread is also valid for Crimson backports too!
Just one specific thing - the kernel also should be rebuilt.
In fact I’ve added a few parameters. @dos, is it possible to include this options by default?
CONFIG_DMABUF_HEAPS=y
CONFIG_DMABUF_HEAPS_CMA=y
In advance I’ve also enabled this parameters:
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
CONFIG_WLAN_VENDOR_REALTEK=y
CONFIG_RTL_CARDS=m
CONFIG_RTL8192CE=m
CONFIG_RTLWIFI=m
CONFIG_RTLWIFI_PCI=m
CONFIG_RTL8192C_COMMON=m
1 Like
Just be careful with non Libre controllers enablements for GA on Gnu PureOS
GeneralAvailability.
1 Like
I falling in Love with Debian with the new desing+features on Apt v3.0.
I Really Really want APT v3.0 on Gnu Pureos Dawn by default even via backport.
APT v3.0 is so nice.
3 Likes
Just add apt v3 into repo, welcome for testing!
4 Likes
Thank you. 
3 Likes
I’m trying to use Crimson unofficial backports now on a latest Crimson image.
For info, I got:
Err:1 https://codeberg.org/galilley/librem5-crimson-backports/raw/branch/master/debs ./ libmbim-proxy 1.32.0-1
429 Too Many Requests [IP: <redacted> 443]
And many more similar errors. I will try to continue downloading via a VPN. To be continued…
1 Like
Via Mullvad VPN I managed to finish the download. After running the apt dist-upgrade command I did a reboot.
The Librem 5 does not fully boot any more, and gives this errors on a black screen and stops continuing to boot (note that I typed the errors below manually, so there can be spelling errors:)
I see around 12 times:
Nothing to read on input.
Next three times:
cryptsetup: ERROR: luks-xxxxxxxxxxxxxx: cryptsetup failed, bad password or options?
Then:
cryptsetup: ERROR: luks-xxxxxxxxxxxxxxx: maimum number of tries exceded
The whole sequence of luks errors roughly repeats four times.
Indeed, I did use the LUKS Crimson image variant.
1 Like