> Pressing ESC, I get out of the splash and can see that cryptsetup is trying to unlock
> /dev/sda2 but never prompts me for the passphrase. As a result, the laptop simply can't
> boot.
Oh, interesting. The code in cryptsetup to select whether to prompt via plymouth is here in /lib/cryptsetup/cryptdisks.functions:
if [ -x /bin/plymouth ] && plymouth --ping; then KEYSCRIPT="plymouth ask-for-password --prompt" keyscriptarg=$(echo -e "$keyscriptarg") else KEYSCRIPT="/lib/udev/watershed /lib/cryptsetup/askpass"
fi
Is /dev/sda2 a luks volume, or a non-luks volume? (There are separate code paths for each) Could you try adding some debug statements to this code, to find out what's preventing cryptsetup from talking to plymouth?
> Pressing ESC, I get out of the splash and can see that cryptsetup is trying to unlock
> /dev/sda2 but never prompts me for the passphrase. As a result, the laptop simply can't
> boot.
Oh, interesting. The code in cryptsetup to select whether to prompt via plymouth is here in /lib/cryptsetup /cryptdisks. functions:
if [ -x /bin/plymouth ] && plymouth --ping; then
KEYSCRIPT= "plymouth ask-for-password --prompt"
keyscriptarg =$(echo -e "$keyscriptarg")
else
KEYSCRIPT= "/lib/udev/ watershed /lib/cryptsetup /askpass"
fi
Is /dev/sda2 a luks volume, or a non-luks volume? (There are separate code paths for each) Could you try adding some debug statements to this code, to find out what's preventing cryptsetup from talking to plymouth?