Anyone running the Crimson branch on the Librem 5? If so, what are your current findings? I will be testing on my other Librem 5 soon-ish
There seems to be a lot of interest in Crimson recently.
What are the most important new or updated features or fixes that Crimson brings to the L5, over Byzantium?
2 Likes
I’m interested in potential features regarding the camera that might be in Crimson. Wanting to hear other people’s takes before I jump in. Still jumping in, but wanting to see other people’s findings thus far.
No, I will update to Crimson when it is stable, similar to the situation with Qubes OS 4.2.0: I need production-ready experience.
4 Likes
This evening I will switch me second L5 to Crimson from Byzantium
4 Likes
Good luck. Please share your experience.
4 Likes
This. Only having one Librem 5, I want it to be stable. If they cost one-third of what they do (random figure) then I might buy a spare that could be used for this kind of crash-and-burn experience. 
1 Like
Just a friendly reminder to backup any important files before experimenting with a new unstable PureOS image.
2 Likes
This. Just this. Everyone. Please.
3 Likes
I am interested in doing the same on my second L5. Please share your steps to get there and your experience! Thank you
1 Like
If I didn’t get nerd7473 wrong he’s using his second device. So I guess there is no important file that needs to be saved.
However, wouldn’t it be better to flash it to crimson instead of updating? At least for people who want a “production-ready” experience with stable crimson builds later. Or am I wrong?
My opinion, yes. It is simpler and cleaner.
By cleaner, I mean, for example, that everyone installing crimson from scratch has an initially identical system.
As a data point, when a new LTS version of Ubuntu is released, they don’t even offer the upgrade from the previous LTS version until the first point release update to the new LTS version comes out. So the only way to run the LTS version immediately is to install from scratch (unless you really want to be on the bleeding edge and force the update before it is offered and are prepared to deal with whatever mess ensues).
2 Likes
The steps are mostly the same as reflashing the Librem 5.
The major difference is downloading the landing image (plain variant only as of this time) instead of the Byzantium image.
https://arm01.puri.sm/job/Images/job/Image%20Builds%20landing/
After you download it, extract the file and put it in the root directory of librem5-flash-image. Also get the DAS U-Boot image (u-boot-librem5.imx) and place it in the same directory.
https://arm01.puri.sm/job/u-boot_builds/job/uboot_librem5_mainline_build/
Then open the Terminal in the directory, and run this command:
$ ./scripts/librem5-flash-image --skip-downloadThis only works on the Evergreen model; do not follow these steps if you are on any other Librem 5 revision.
4 Likes
OK, that’s another reason to limit this to a crash-and-burn phone, not a real-use phone.
1 Like
Well, since December 27th, 2018, whenever anyone followed the instructions to reflash the Librem 5, the plain variant was used as the default. It was only recently changed to LUKS in June 23rd, 2023, which my actions may have been a catalyst for: I mentioned about it to Purism support just before I decided to make a forum account on June 26th, 2023.
2 Likes
Absoultely, that’s why I’m testing on my other L5
If you are gonna make the jump perhaps you should image your current byzantium set up via Jumpdrive and gnome disk as described here:
I was experimenting with image restoration and was successful at reflashing an image backup from my L5 that was saved on my L13 laptop.