hey john, On 15/02/2010 John Martin wrote: > Also attached are: > > 1. The /boot/initrd.img-2.6.32-trunk-amd64 created when upgrading > update-inetd [4.35 -> 4.36] earlier today.
seems like you forgot to attach the initramfs image. i strongly believe that the problem is a misconfiguration on your side. otherwise other users of encrypted rootfs would have run into the same issue. please check any custom changes you made to /etc/initramfs-tools and /etc/modprobe.d. also, you could apply the attached patch to /usr/share/initramfs-tools/scripts/local-top/cryptroot and regenerate the initramfs afterwards in order to get some debugging output in the boot process. greetings, jonas
--- /usr/share/initramfs-tools/scripts/local-top/cryptroot +++ /usr/share/initramfs-tools/scripts/local-top/cryptroot @@ -291,6 +291,17 @@ fi + message "some debugging output just before cryptsetup is invoked:" + /bin/sleep 2 + lsmodout="$(lsmod)" + message "the output of lsmod:" + message "$lsmodout" + /bin/sleep 2 + message "are the usb keyboard modules loaded?" + /bin/sleep 2 + read -p "input any characters to test the keyboard: " testkbd + /bin/sleep 2 + message "if you see this message, your keyboard works" if ! crypttarget="$crypttarget" cryptsource="$cryptsource" \ $cryptkeyscript "$cryptkey" | $cryptcreate --key-file=- ; then message "cryptsetup: cryptsetup failed, bad password or options?"
signature.asc
Description: Digital signature
