pennm Posted March 26, 2021 Share Posted March 26, 2021 Hi all, I have a working Pinebook Pro Focal build with LUKS encryption enabled. The only issue I have is that when booting no progress or password prompt is displayed. As soon as I enter the password and hit enter I see the boot logo or console output depending on what is set in armbianEnv.txt. I will be continuing my research and learning about the boot process in general but wanted to check in here to see if people had any obvious pointers to share or whether maybe this is a known limitation that is going to be hard to resolve. Thanks, Matt 0 Quote Link to comment Share on other sites More sharing options...
tparys Posted March 27, 2021 Share Posted March 27, 2021 If you're doing a LUKS unlock via cryptsetup, it's done inside of the initramfs (or initrd). The text of that is sent to the Linux console. It's before SystemD starts and initializes all consoles listed as kernel arguments. So IIRC, it's only the last one specified that takes effect at that point in boot. So if you want it on the main display, you may have to append a "console=/dev/tty0" kernel argument in your boot options. Once SystemD takes over all specified consoles become active, but the kernel only will use the last one specified for that part of the boot process. Or maybe first one? Sometimes my brain's mashed potatoes. Experiment a bit? I've not looked through the current Armbian + LUKS instructions. 0 Quote Link to comment Share on other sites More sharing options...
pennm Posted March 27, 2021 Author Share Posted March 27, 2021 Yeah I have been using console=display in armbianEnv.txt which translates to console=/dev/tty1 which I believe is what is required. I've also been trying to replicate a working setup based on the Manjaro + LUKS discussion on the Pine64 forums here: https://forum.pine64.org/showthread.php?tid=9052 I updated the initrd image to include the kernel modules seen in the Manjaro installer patch from that thread but still no dice. I need to look more closely to see if there's anything else from there I'm missing as would naively expect the same approach to be reproducible here. 0 Quote Link to comment Share on other sites More sharing options...
pennm Posted July 2, 2022 Author Share Posted July 2, 2022 So I've not looked further at this in over a year but figured I'd bump this to see if any other Armbian PBP users have solved this yet. 0 Quote Link to comment Share on other sites More sharing options...
hexdump Posted July 2, 2022 Share Posted July 2, 2022 @pennm - not directly armbian, but maybe it is the same problem there too: https://github.com/hexdump0815/linux-mainline-and-mali-rockchip-rk33xx-kernel/commit/ece606e53780dec397cca7c1f10d70d57f1d0511 good luck and best wishes - hexdump 0 Quote Link to comment Share on other sites More sharing options...
spalf Posted December 9, 2023 Share Posted December 9, 2023 hi, make sure you have all the kernel modules in your initramfs as listed here: https://github.com/NixOS/nixos-hardware/blob/master/pine64/pinebook-pro/default.nix i had the same issue with my archilnux installation until i included all of them 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted December 9, 2023 Share Posted December 9, 2023 1 hour ago, spalf said: i had the same issue Probably it just works now. There were many fixes applied to this area in past year and half. https://github.com/armbian/build/commits/main/lib/functions/image/initrd.sh 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.