pinephone pro: installing to emmc with --fde: "cryptsetup: not found"

added device-pine64-pinephonepro help wanted labels

mentioned in merge request postmarketos.org!160 (merged)

By Oliver Smith on 2022-03-28T07:11:11

mentioned in merge request !2870 (closed)

By Oliver Smith on 2022-03-28T07:17:19

Maybe it's an issue when using Tow-Boot Jumpdrive-like functionality, but I didn't run into this issue when doing PC pmbootstrap -> SD -> eMMC path. I've made an SD card with pmbootrap with FDE, and then using this SD card I did the same steps to install PostmarketOS to PinePhone Pro with FDE - everything seems to work

By Mikhail Podshivalin on 2022-03-30T22:24:43

I did not encountered the issue. Installation with fde through tow-boot usb mass storage access was pretty smooth. System boot correctly.

I think I already encountered this kind of issue before. I failed to type the luks passphrase multiple time without understanding what was going on. Rebooting the device and I one shooted the passphrase. Is it possible this issue relate to the pinebook "Cant find boot partition" ? Maybe it only happen some times ? (I rebooted the devices 3 times in a row without encountering the issue)

edit: I now have the "incorrect passphrase" whith my sd cart inserted. Both issues seems unrelated

By Willow on 2022-03-31T14:50:06

I openned a dedicated ticket for this unrelated issue. The bug I had eventually now happen everytime #1485 (closed)

By Willow on 2022-03-31T14:50:06

I just tried FDE on an OG PP (with Tow-Boot and both UEFI and our previous (old) u-boot scripts), using !3068 (closed), and it worked just fine. Can anyone still reproduce this issue? Is it device-specific somehow (I can not think of a reason how it would)?

By Bart Ribbers on 2022-10-07T07:49:07

@ollieparanoid if you can't reproduce this anymore please close it. It's another checkbox for !3068 (closed).

By Bart Ribbers on 2022-10-07T07:49:06

Hello @PureTryOut,

I've tested today on my PPP with pmOS v22.06 that the FDE works correctly.

$ cat /sys/firmware/devicetree/base/model
Pine64 PinePhonePro
$ uname -a
Linux eagle 5.17.9 #4 SMP PREEMPT Mon Oct 24 02:22:19 UTC 2022 aarch64 Linux
$ sudo cryptsetup isLuks /dev/mmcblk0p2 && echo "Is LUKS device"
Is LUKS device
eagle:~$ lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
mmcblk0      179:0    0 115.2G  0 disk
├─mmcblk0p1  179:1    0   243M  0 part /boot
└─mmcblk0p2  179:2    0   115G  0 part
mmcblk0boot0 179:256  0     4M  1 disk
mmcblk0boot1 179:512  0     4M  1 disk

By Petr Hodina on 2023-01-15T13:36:43

However,

it fails to load the rootfs on v22.12 -> /init: line 362: cryptsetup: not found @PureTryOut

Here is the output from serial console:

U-Boot TPL 2021.10 (Oct 04 2021 - 15:09:26)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2021.10 (Oct 04 2021 - 15:09:26 +0000)
Trying to boot from SPI
NOTICE:  BL31: v2.6(release):
NOTICE:  BL31: Built : 00:00:00, Jan  1 1980


Tow-Boot 2021.10 (Oct 04 2021 - 15:09:26 +0000)005 [variant: spi]

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 PinePhonePro
DRAM:  3.9 GiB
PMIC:  RK8180 (on=0x40, off=0x04)
MMC:   mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25lq128e with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Pine64 PinePhonePro
Net:   No ethernet found.
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Please press [ESCAPE] or [CTRL+C] to enter the boot menu.
off
off
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Card did not respond to voltage select! : -110
Scanning disk mmc@fe310000.blk...
Disk mmc@fe310000.blk not ready
Card did not respond to voltage select! : -110
Scanning disk mmc@fe320000.blk...
Disk mmc@fe320000.blk not ready
Scanning disk mmc@fe330000.blk...
Found 3 disks
** Unable to read file ubootefi.var **
Failed to load EFI variables
BootOrder not defined
EFI boot manager: Cannot load any image
Found EFI removable media binary efi/boot/bootaa64.efi
716800 bytes read in 56 ms (12.2 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Booting /efi\boot\bootaa64.efi
Welcome to GRUB!


  Booting `postmarketOS'

EFI stub: Booting Linux Kernel...
EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services...
Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Linux version 6.1.3 (pmos@CZPRGL-B18SYD3) (aarch64-alpine-linux-musl-gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, GNU ld (GNU Binutils) 2.39) #3 SMP Sun Jan 15 00:02:58 UTC 2023
Machine model: Pine64 PinePhonePro
earlycon: uart8250 at MMIO32 0x00000000ff1a0000 (options '')
printk: bootconsole [uart8250] enabled
### postmarketOS initramfs ###
Configuring kernel firmware image search path
NOTE: Waiting 10 seconds for the framebuffer /dev/fb0.
If your device does not have a framebuffer, disable this with:
no_framebuffer=true in <https://postmarketos.org/deviceinfo>
Setting framebuffer mode to: U:720x1440p-0
Setup usb network
  /sys/class/android_usb does not exist, skipping android_usb
  Setting up an USB gadget through configfs
Starting unudhcpd
  Using interface usb0
  Starting the DHCP daemon
Trying to start server with parameters: Server IP addr: 172.16.42.1:67, client IP addr: 172.16.42.2, interface: usb0
Trying to bind to interface: usb0
Server started!
Mount boot partition (/dev/mmcblk2p1) to /boot (read-only)
Detected vfat filesystem
Extract /boot/initramfs-extra
cpio: lib/ld-musl-aarch64.so.1 not created: newer or same age file exists
cpio: lib/libc.musl-aarch64.so.1 not created: newer or same age file exists
cpio: lib/libdevmapper.so.1.02 not created: newer or same age file exists
11748 blocks
Received DHCP DISCOVER from client: f6:21:be:09:ba:50
Received DHCP REQUEST from client: f6:21:be:09:ba:50
/init: line 362: cryptsetup: not found
Mount root partition (/dev/mmcblk2p2) to /sysroot (read-only)
WARNING: Detected unsupported 'crypto_LUKS' filesystem (/dev/mmcblk2p2).
ERROR: unable to mount root partition!

By Petr Hodina on 2023-01-15T14:46:53

mentioned in issue #1906 (closed)

By Petr Hodina on 2023-01-15T15:16:39

I don't know if it's relevant, but I got this exact issue while trying to get FDE on samsung-grandpplte:

/init: line 380: cryptsetup: not found
Mount root partition (/dev/mapper/mmcblk0p26p2) to /sysroot (read-only)
WARNING: Detected unsupported 'crypto_LUKS' filesystem (/dev/mapper/mmcblk0p26p2).
ERROR: unable to mount root partition!

By Yassine Oudjana on 2023-02-02T18:44:03

I have the same issue (ERROR: unable to mount root partition!) while using -fde on 6.3.4-sdm845 postmarketos-qcom-sdm845 aarch64 Linux. Build from 29-05-2023 (edge). Without -fde just works like charm. So apparently still an issue..

By streaktools on 2023-06-18T08:56:34

Still seems to be broken on pinephone pro with latest plasma installer (20230809-1953) and fde enabled. Was able to get the SD card booting with full disk encryption after manually updating fstab but after unlocking luks I was met with a blank screen.

The DE seems to hang there, no interaction from KB or touch inputs.

I tried the same trick on the eMMC and was not able to get it to boot (still showing missing boot partition).
I might be missing something, but in case this helps someone else, this is how I attempted to fix the luks boot on eMMC:

# you will need qemu-user-static locally if not on an ARM system
#sudo apt-get install qemu-user-static
# mount pinephonepro in usb mode, then locally..
PINEPHONE_DEV=/dev/sdc
PINEPHONE_MNT=/media/anon/pmOS_root
PINEPHONE_MMC_BOOTPART=/dev/mmcblk2p1
sudo mount ${PINEPHONE_DEV}1 $PINEPHONE_MNT/boot
sudo mount --bind /dev $PINEPHONE_MNT/dev
sudo mount --bind /dev/pts $PINEPHONE_MNT/dev/pts
sudo mount --bind /proc $PINEPHONE_MNT/proc
sudo mount --bind /sys $PINEPHONE_MNT/sys
sudo cp /usr/bin/qemu-arm-static /media/anon/pmOS_root/bin/
sudo chroot $PINEPHONE_MNT /bin/sh
# then inside the chroot..
ROOT_UUID=$(grep -E -m 1 'UUID=.*? +/' /etc/fstab |cut -d ' ' -f 1 | cut -d '=' -f 2)
echo "root UUID=$ROOT_UUID none luks,discard" >/etc/crypttab
mkinitfs
sed -i "s%UUID=$ROOT_UUID%/dev/mapper/root%" /etc/fstab
sed -i -E 's%UUID=.*? (/boot.*)%/dev/mmcblk1p1 \1%' /etc/fstab
# back on local machine..
sudo umount $PINEPHONE_MNT/dev/pts
sudo umount $PINEPHONE_MNT/dev
sudo umount $PINEPHONE_MNT/proc
sudo umount $PINEPHONE_MNT/sys
sudo umount $PINEPHONE_MNT/boot
sudo umount $PINEPHONE_MNT
# reboot phone from emmc

If I had to put a guess out there, the issue seems to be that the installer is not setting up /etc/crypttab and the UUIDs it puts in /etc/fstab are incorrect.
Hope that helps debugging, i'm not spending any more time on this tonight. cheers!

By Tyler Moore on 2023-08-13T04:04:09

I tried this on my Pinephone Pro yesterday using pmbootstrap install --sdcard=/dev/sda --fde (which was the eMMC device) and it worked fine. It all worked out of the box and I didn't have to modify anything. I am using sxmo-de-sway if that matters.

By Kyle Ambroff-Kao on 2023-11-07T22:42:57

I decided to try again today but with phosh instead of sxmo-de-sway and I got similar behavior to what is described here.

So sxmo-de-sway: works, phosh: doesn't work.

I noticed that when running pmbootstrap install with phosh selected postmarketos-base-nofde is selected as the provider for postmarketos-fde-unlocker.

$ ./pmbootstrap.py install --sdcard=/tmp/test.img --fde
[21:15:32] *** (1/4) PREPARE NATIVE CHROOT ***
[sudo] password for kyle: 
Sorry, try again.
[sudo] password for kyle: 
[21:15:45] (native) install cryptsetup util-linux parted
[21:15:46] *** (2/4) CREATE DEVICE ROOTFS ("pine64-pinephonepro") ***
[21:15:46] Register qemu binfmt (aarch64)
[21:15:48] (rootfs_pine64-pinephonepro) install postmarketos-base device-pine64-pinephonepro postmarketos-ui-phosh device-pine64-pinephonepro-nonfree-firmware calls chatty evince firefox-esr font-noto font-noto-emoji gnome-calculator gnome-clocks gnome-console gnome-contacts gnome-software gnome-software-plugin-apk gnome-text-editor karlender lollypop loupe mobile-config-firefox phosh-mobile-settings portfolio postmarketos-artwork-wallpapers postmarketos-default-camera postmarketos-tweaks postmarketos-welcome postprocessd ttyescape htop emacs tmux gnupg postmarketos-base-nofde

When I did the same thing after running init and selecting sxmo-de-sway, unl0kr provided postmarketos-base-nofde.

$ ./pmbootstrap.py install --sdcard=/tmp/test.img --fde
[21:19:24] *** (1/4) PREPARE NATIVE CHROOT ***
[21:19:24] (native) install alpine-base
[21:19:26] (native) install cryptsetup util-linux parted
[21:19:26] *** (2/4) CREATE DEVICE ROOTFS ("pine64-pinephonepro") ***
[21:19:26] (native) install qemu-aarch64
[21:19:26] Register qemu binfmt (aarch64)
[21:19:26] (rootfs_pine64-pinephonepro) install alpine-base
[21:19:29] (rootfs_pine64-pinephonepro) install postmarketos-base device-pine64-pinephonepro postmarketos-ui-sxmo-de-sway device-pine64-pinephonepro-nonfree-firmware w3m sfeed adwaita-icon-theme clickclack firefox-esr font-noto font-noto-emoji imv mobile-config-firefox postmarketos-default-camera postprocessd ttyescape htop emacs tmux gnupg unl0kr

When I install phosh after ensuring that unl0kr is in the list of installed packages it works and I can boot with FDE on the pinephone pro just fine.

I think this explains why it worked for me when I installed with FDE a few weeks ago, maybe something about the dependencies of postmarketos-ui-sxmo-de-sway pulls in unl0kr transitively.

For some reason that I don't understand yet the wrong provider is chosen when --fde is used with postmarketos-ui-phosh.

Reading through pmbootstrap code here, it looks like when --fde is supplied to the install command, it searches for a provider of postmarketos-fde-unlocker. There are three, unl0kr, osk-sdl and postmarketos-base-nofde. pmb.parse.depends.package_provider() will ensure that one of those is already in the list of packages to install. If one of those are not in the list of packages to install, it will choose the highest priority provider, which is postmarketos-base-nofde with priority 1.

unl0kr works. I haven't tried osk-sdl.

I'm trying to figure out how this is all supposed to be wired up so I can detangle this. It seems like there is just a dependency missing somewhere. I don't see osk-sdl or unl0kr listed as dependencies in any of the device specific packages.

By Kyle Ambroff-Kao on 2023-12-03T07:59:43

pinephone pro: installing to emmc with --fde: "cryptsetup: not found"

Describe your issue

What's the expected behaviour?

What's the current behaviour?

How to reproduce your issue?

What device are you using?

On what postmarketOS version did you encounter the issue?

What's the build date of the image? (in yyyy-mm-dd format)

Child items 0

Activity