2012/10/1 Michael Prokop
<mika@debian.org>
* Samuel Hym [Mon Oct 01, 2012 at 06:41:10PM +0200]:
> My disk is dm_crypted. After upgrading from 0.107 to 0.108, my system
> could not
> boot anymore with the newly generated ramfs: entering the passphrase did not
> unlock the disk, yielding the same error message as a wrong passphrase.
> Downgrading to 0.107 solved the problem.
[...]
What version of cryptsetup are you using?
I'm using package version 2:1.4.3-2 but this might just be irrelevant since:
Is there any visible difference between running
"update-initramfs -u -v" for 0.107 and 0.108?
Yes!
With 0.107, I have a line:
Adding binary /bin/loadkeys
not with 0.108.
What about differences between the generated initramfs (check e.g.
with "lsinitramfs /boot/initrd.img-$(uname -r)")?
Similarly, the diff is:
--- /dev/fd/63 2012-10-02 17:26:29.136907406 +0200
+++ /dev/fd/62 2012-10-02 17:26:29.116907309 +0200
@@ -1,4 +1,4 @@
-/root/initrd.img-3.2.0-3-amd64-0.107
+initrd.img-3.2.0-3-amd64
.
scripts
scripts/functions
@@ -955,7 +955,6 @@
bin/reboot
bin/mkdir
bin/nuke
-bin/loadkeys
bin/gunzip
bin/umount
bin/false
@@ -990,7 +989,6 @@
etc/ld.so.conf
etc/lvm
etc/lvm/lvm.conf
-etc/boottime.kmap.gz
etc/modprobe.d
etc/modprobe.d/blacklist-cups-usblp.conf
etc/modprobe.d/alsa-base.conf
Does setting KEYMAP=y in /etc/initramfs-tools/initramfs.conf help?
No change. It was set to n, but there does not seem to make any difference, strangely enough.
Regards
Sam