I was trying some stuff, and upgraded PureOS Byzantium to PureOS Crimson by looking at the tutorial from Amber to Byzantium on the PureOS download front page and typing Crimson instead of Byzantium.
I did this on nonstandard hardware, not a Librem device from Purism.
Ever since the update, the lightdm installation I was using stopped launching. So I tried installing gdm3 again (I had removed it). Didn’t fix the issue. After boot, I am stuck on fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress.
But Ctrl+C does nothing. I am able to use CTRL+ALT+F2, or ssh, to open a console.
I tried changing apt sources back to byzantium and running sudo apt reinstall '~i' which the internet suggested might do a full reinstall. But, still stuck on the same issue.
Is clean installing Byzantium the only option or is this recoverable because I can still get to a console? The clean Byzantium install was working fine, but I only installed within the last week and didn’t setup backups yet.
(Byzantium was running fine but the reason for investigating Crimson is that I was trying to investigate my options for better nvidia card performance. llvmpipe was getting used for 3D which is software rendering, and I wondered if there is a way to get nouveau to do hardware rendering, maybe on a newer version)
Before doing that, since you do still have shell access, are there any files that you would like to rescue first?
Otherwise, I would suggest a clean reinstall from scratch of byzantium is the best approach. It is always possible that you can work out what went wrong and cobble a fix together but …
However before you do that, you might want to try a clean install from scratch of crimson. I say this because you don’t know whether the problem is a) crimson just won’t work out-of-the-box on your hardware or b) crimson is not yet ready to be installed by upgrade from byzantium.
I tried Crimson live boot from flash drive. It doesn’t get as far as the install that I tried to upgrade – instead sits at a flashing underscore. The Ctrl+Alt+F3 style recovery consoles were clickable and it would momentarily show a login prompt, but then remove it before I could humanly actually enter any credentials.
Seems I will be on Byzantium, then.
Edit: Took me a few to redownload a copy of Byzantium live ISO because I didn’t have one sitting around, but it’s night and day compared to the Crimson live iso. Happily opens a graphical desktop immediately upon booting.
The hardware mentioned in this thread had sat idle for some time. Earlier this week I booted it again, which I believe is the byzantium reinstall mentioned above. Then I did sudo apt update followed by sudo apt full-upgrade and thought nothing of it. I did not restart at the time, and I simply kept using the machine. Then I turned it off.
Several days later now, I turned it back on. But now, it’s giving the same “Press CTRL+C to cancel all filesystem checks in progress.” It’s been a while and I had forgotten, but this seems like the same issue that I was getting on crimson.
But if I use the CTRL+ALT+F2 recovery console, I can clearly see that the apt sources are still set on byzantium here. If this isn’t Crimson, or is the result of a newer version thing that’s now backported to Byzantium, does anybody know what this is? Should I be checking a system log to understand what kind of “filesystem checks” we think this is doing that prevent booting into lightdm or gdm?
Update: the above problem was my own dumb fault. The hardware here was actually running ImpureOS, rather than PureOS. Which is to say that I tainted an otherwise beautiful machine with nvidia drivers in order to get the full value of the hardware and the 3D performance that nouveau refused to offer.
The nvidia drivers broke the system after the upgrade, and I was able to fix it once I realized in journalctl that it said “No drm found” or something like that. Literally just used command line to update the nvidia drivers and it all came back.