Full disk encryption with calamares: beware of last testing upgrade!

Full disk encryption with calamares: beware of last testing upgrade! - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: Mobian on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=139)
+---- Thread: Full disk encryption with calamares: beware of last testing upgrade! (/showthread.php?tid=19702)

Full disk encryption with calamares: beware of last testing upgrade! - mdk - 02-20-2025

I just upgraded my pinephone to the last testing via apt as always, and now the full disk encryption (calamares) passephrase prompt is looping with a "bad option" error. So I can no longer boot.

I have not investigated yet, just wanted to alert you.

I bet I can save myself by mounting the eMMC over USB, hopefully last time I had a similar issue I wrote about it: https://mdk.fr/blog/black-screen-at-boot-on-my-pinephone.html

Update:I tried another apt full-upgrade and a dpkg-reconfigure linux-image-6.6-sunxi64 over USB mass storage / chroot, no luck, but it seems a tad different, it now reads:

panel-sitronix-st7703 : ... midi_dsi_attach failed (-517) Is host ready?
pinephone-keyboard: Failed to read device ID: -6

Update: I noticed in my upgrade that phosh-osk-stub had an upgrade, so I downgraded it with `dpkg -i /var/cache/apt/archives/phosh-osk-stub_0.44.0-1_arm64.deb`, but no luck, still no keyboard at boot to decrypt my root fs Sad

RE: Full disk encryption with calamares: beware of last testing upgrade! - dragonhospital - 02-21-2025

Ask devs in #mobian matrix room. Share their fix.

Quote:Starting kernel ...

[ xx.xxxxxx] lima 1c40000.gpu: error -ENODEV: _opp_set_regulators: no regulator (mali) found
[ xx.xxxxxx] pinephone-keyboard 3-0015: Failed to read device ID: -6
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized
MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized

BusyBox v1.37.0 (Debian 1:1.37.0-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

RE: Full disk encryption with calamares: beware of last testing upgrade! - d4s - 02-21-2025

(Yesterday, 02:07 AM)dragonhospital Wrote: Ask devs in #mobian matrix room. Share their fix.

Quote:Starting kernel ...

MESA-LOADER: failed to open dri: /usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/gbm, suffix _gbm)
ERROR: Could not create window/display: EGL not initialized

Hi, I have the same issue -- the core problem is in the absence of the library "dri_gbm.so", which is not copied during initramfs generation, I see the error below:

Code:
ln: failed to create symbolic link '/var/tmp/mkinitramfs_87Ugk3//usr/lib/aarch64-linux-gnu/dri/libdril_dri.so': File exists

I did a check of the initramfs contents, by copying it to the host and added `/usr/lib/aarch64-linux-gnu/gbm/dri_gbm.so` manually -- that requires unpack and pack of existing initramfs. After that, Pinephone booted well.

Looks like the issue is in initramfs generation scripts, so with `osk-sdl` the initramfs would be regenerated in wrong way.

In Matrix channel, there were a suggestion to switch to more recent OSK `unl0kr` and that helped in my case.

Safe steps:

change `/etc/crypttab` file, to point to proper keyscript `keyscript=/usr/share/initramfs-tools/scripts/unl0kr-keyscript`

install `unl0kr`, automatically regenerated initramfs will contain both OSKs

remove `osk-sdl` and initramfs will be regenerated again, but will contain only `unl0kr`

Good thing what initramfs is 3 times (!!!) less than with osk-sdl with all deps:

Code:
$ ls -lh /boot/initrd.img-6.12-sunxi64*

-rw-r--r-- 1 root root 29M Feb 14 18:53 /boot/initrd.img-6.12-sunxi64

-rw-r--r-- 1 root root 99M Feb 14 16:45 /boot/initrd.img-6.12-sunxi64.bak

Bad news -- the `unl0kr` doesn't support the Pinephone keyboard.

RE: Full disk encryption with calamares: beware of last testing upgrade! - dragonhospital - 02-21-2025

d4s how is initramfs unpacked&packed?

Your instructions is for everyone that has not booted. Trixie users do not reboot!

First back up /etc/crypttab

Second change osk-sdl-keyscript in /etc/crypttab to unl0kr-keyscript

Third sudo apt install --reinstall unl0kr

chroot steps if already rebooted and broke.

First download 2023 mobian img from mobian.org

Second write mobian img to spare SD card

Third put SD card in pinephone and boot while holding down volume button

Fourth when fresh mobian loaded use password 1234 and connect to internet

Fifth open terminal console and sudo su

Sixth apt install cryptsetup-bin

Seventh lsblk to find boot and encrypted fs of onboard mmc

Eight cryptsetup luksOpen /dev/mmblkXpY root X and Y are numbers from lsblk

Ninth mount /dev/mapper/root /mnt

Tenth mount /dev/dev/mmblkApB /mnt/boot A and B are numbers from lsblk

Eleventh for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done

Twelfth sudo chroot /mnt

Thirteenth back up /etc/crypttab and change osk-sdl-keyscript in /etc/crypttab to unl0kr-keyscript

Fourteenth sudo apt install --reinstall unl0kr

exit and reboot

unl0kr crashes w/USB keyboard. Bug. Use onscreen keyboard to unlock and boot.
Camera now broken too, can't load firmware. Bug.