Nice, that did the trick.
But unfortunately the reboot failed - LUKS prompt didn’t come up (“Nothing to read on input… cryptsetup: ERROR: srypt_root cryptsetup failed, bad password or options?” repeats on the screen)
did you switch to unl0kr
?
Nope.
Ah, forgot that message (got lost in this long thread). I’ll try to figure it out…
Any idea why it brakes?
Do you mean why it breaks osk-sdl
? No, I did not investigate this question.
Fresh image flash, apt update, apt updgrade, apt dist-upgrade, apt --fix-broken install, apt dist-upgrade, another apt update and dist-upgrade (just to be sure), edited /etc/crypttab, apt install unl0kr, rebuilt initrd.img, restarted… and LUKS prompt looks weird in white when it first comes up
[edit to add:one more missed step - finally, you need to dl systemd-resolved and systemd-container from the codeberg backports site with another comp (do that at some point in the process with your L5, or), use an SD card or USB stick to get them to L5 and install them (sudo dpkg -i [package name]) to get online again, and if you get no network during installation at some point, check that you have correct date and time]
[edit to add: as this is now the procedure to activate backports, the info should be updated (in addition of: advice to taking first disc image backup so user can revert away from backports for when official updates come)]
[edit to add: a pic of unl0kr - I kinda like the more convenient keyboard (more roomy layout) and the settings - light/dark, kb toggle, layouts for us/es/de/fr with special characters (how about new LUKS pw: äöĸœßð€ẞÐbəßœöä%ä?). Not sure if there are any issues with purism or phosh integrations other than looks - any idea?]
nice i will try tonight again thanks for figuring it out.
i think i got the same result. after successfully applied everything, the network is networking even though everything shows normal, wifi is connected and cell mobile looks fine, but no data.
Did you install the systemd-resolved
etc?
Did you update/set right time and date? [Wrong time/date will prevent networking]
cant after dist-upgrade already lost the connection, cant install anything.
My bad. I had not tested network after my install since installation from network worked. This is the last missing step. I can confirm that I needed to install systemd-resolved (and for good measure systemd-container, didn’t test if that was necessary). I used a USB-stick (formatted to ext4 as for some reason fat didn’t work at one point), that I connected after downloading the packages there via another computer. Navigate to it and use sudo dpkg -i [package name]
(or equivalent apt command). Sorry again, missed this from the procedure as I didn’t do any tests before setting it down. That time thing though, it was something I needed to do at one point of the install to get things going.
let me try it. but now the whole backports link connection failed after I did sudo apt update anyone has this problem?
I see. I also have another problem that happened through the backports recently. If the backports didn’t go through somehow(I have connection), then it will auto reboot and show a loading spinner and becomes a bootloop. This is a new problem that I have so far
I too came across that spinning wheel and repeated re-loads of it at one point before getting the process right. Not sure why or how. It wasn’t anything to do with connection with me (I think). The spinner seems to be phosh related - I get that for a few seconds now after LUKS goes through with the working system.
i got the automatic reboot to that point but I didnt use the luks, I used the plain build.
It looks like new phosh boot screen. So, the system must be fully functional at this step and it worth to look inside the logs. May be using dual boot from sd-card and chroot…
this backdrops works on the plain image, right? I will try to install the system container and resolver before dist-upgrade, maybe luckily if it doenst auto reboot, I can have the internet connection.