veilor-org/veilor-os
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

v0.5.18: add crypt + systemd-cryptsetup + ask-password agent to initramfs

Browse source 
v0.5.17 boot stuck at dracut-initqueue waiting for LUKS device that
never unlocks. Plymouth removal also dropped the dracut machinery
that prompts user for LUKS passphrase. Pure-text systemd-tty-ask-
password-agent works in real root but isn't bundled into initramfs.

Fix: dracut.conf.d/99-veilor-no-plymouth.conf:
  add_dracutmodules+=" crypt systemd-cryptsetup "
  install_items+=" /usr/bin/systemd-tty-ask-password-agent "

Result: dracut bundles systemd-cryptsetup + ask-password binary into
initramfs. cryptsetup-generator creates unit at boot, ask-password-
agent prompts on tty1 in text mode "Please enter passphrase for...:".
sendkey-friendly + works on real hardware.
This commit is contained in:
veilor-org 2026-05-03 17:35:31 +01:00
parent 60321c4908
commit 04595f77e9
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
overlay/usr/local/bin/veilor-installer
View file

@ -555,6 +555,12 @@ bash $REPO/scripts/kde-theme-apply.sh
mkdir -p /etc/dracut.conf.d
cat > /etc/dracut.conf.d/99-veilor-no-plymouth.conf << 'EOF'
omit_dracutmodules+=" plymouth "
# Ensure systemd-cryptsetup module + systemd-ask-password agent are
# included so LUKS prompt appears on tty1 (text mode) when plymouth
# is omitted. Without these, dracut loops on devexists waiting for
# an unlock that never happens.
add_dracutmodules+=" crypt systemd-cryptsetup "
install_items+=" /usr/bin/systemd-tty-ask-password-agent "
EOF
# Regenerate initramfs for the installed kernel(s).
for kver in /lib/modules/*/; do