-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include luks support in jumpdrive #79
Comments
You don't need ARM64 to mount the luks partition on the host. If your host has the luks tools it should just work |
I can mount, but chroot needs qemu. |
I have collected my notes for using qemu to chroot into the librem 5 here https://people.debian.org/~praveen/librem5-rescue.txt |
Though using chroot via qemu is not sufficient to update the kernel on Librem 5 (this could be a bug in how crypttab is setup in pureos too)
|
After updating /etc/crypttab on the laptop, the error changes to
This could probably be fixed in initramfs-tools or setting the value of platform where the tool is expecting. |
This may be related https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951198 |
On mobian, the kernel packages don't use flash kernel, so it can be updated using the chroot, though it is not yet relevant as mobian don't support luks yet. The steps for using qemu is documented at https://wiki.mobian.org/doku.php?id=tweaks#access-chroot-using-qemu-and-jumpdrive |
Also discussing the possibility of following mobian approach of kernel updates in pureos https://source.puri.sm/Librem5/OS-issues/-/issues/306 |
Librem 5 support luks encrypted partitions but currently jumpdrive does not include support for mounting such partitions. Please include it. telneting to jumpdrive should be enough to use luks commands to mount the encrypted partitions.
Current work around is using the disk directly from host system but it needs qemu to mount the arm64 chroot.
The text was updated successfully, but these errors were encountered: