Unable to boot latest kernel

[chrisoprase]

Hi, I have a HDD install of 64 bit Kali 1.0.6 with GNOME as a WM. The / partition is on a luks device in a lvm partion, and the boot partition is on a usb hdd where grub is installed.
After updating to kernel 3.12, if I select the new kernel image, it detects the lvm partition, but then it doesn't prompt for the password to unlock the LUKS device. I just get a blinking cursor, I'm not even dropped to a shell.
Selecting the older kernel (3.7) works fine.

root@kali:~# cat /etc/fstab
#boot_stick:
UUID=a78d7534-6051-4bb8-87df-1b5b9a1d6ff6	/boot		ext4		noatime,defaults			0	2
# /dev/mapper/cryptroot:
UUID=ef2d5895-d2ad-4afd-bb35-25073fd9d05c	/		ext4		usrquota,errors=remount-ro,relatime	0	1
# /dev/mapper/lvmdebian_swap:
UUID=92d407ab-37bb-4f72-88d2-57e042b21f48	none		swap		sw					0	0

root@kali:~# cat /etc/crypttab
cryptroot	ID=dm-name-cryptroot				none		luks,retry=1

root@kali:~# ls -lash /dev/disk/by-uuid
0 lrwxrwxrwx 1 root root  5a3ec99c-86fe-473d-9056-c6bf802d0f47 -> ../../dm-1
0 lrwxrwxrwx 1 root root  92d407ab-37bb-4f72-88d2-57e042b21f48 -> ../../dm-0
0 lrwxrwxrwx 1 root root  a78d7534-6051-4bb8-87df-1b5b9a1d6ff6 -> ../../sdb2
0 lrwxrwxrwx 1 root root  ef2d5895-d2ad-4afd-bb35-25073fd9d05c -> ../../dm-2

root@kali:~# ls -lash /dev/disk/by-id
0 lrwxrwxrwx 1 root root  10 Jan 11 23:31 dm-name-cryptroot -> ../../dm-2
0 lrwxrwxrwx 1 root root  10 Jan 11 23:31 dm-name-lvmdebian-encryptedroot -> ../../dm-1
0 lrwxrwxrwx 1 root root  10 Jan 11 23:31 dm-name-lvmdebian-swap -> ../../dm-0
0 lrwxrwxrwx 1 root root  10 Jan 11 23:31 dm-uuid-CRYPT-LUKS1-5a3ec99c86fe473d9056c6bf802d0f47-cryptroot -> ../../dm-2
0 lrwxrwxrwx 1 root root  10 Jan 11 23:31 dm-uuid-LVM-Gm208cceHxf5QmvNCiuTDvCRyC9R102z68y0mll9MwJQD0ZmMjM5uOJrA9c1xE62 -> ../../dm-1
0 lrwxrwxrwx 1 root root  10 Jan 11 23:31 dm-uuid-LVM-Gm208cceHxf5QmvNCiuTDvCRyC9R102zjORdVh3a8fhg9zzbwr1zIvVf01SHIhDN -> ../../dm-0
0 lrwxrwxrwx 1 root root  10 Jan 11 23:31 usb-WD_My_Passport_0740_575834314136315830393334-0:0-part2 -> ../../sdb2

root@kali:~# cat /etc/default/grub
...
GRUB_CMDLINE_LINUX="resume=UUID=92d407ab-37bb-4f72-88d2-57e042b21f48 cryptdevice=/dev/mapper/lvmdebian-encryptedroot:cryptroot root=/dev/mapper/cryptroot ro"
...

root@kali:~# ls -lash /boot
146K -rw-r--r--  1 root root 146K config-3.12-kali1-amd64
134K -rw-r--r--  1 root root 134K config-3.7-trunk-amd64
7.0K drwxr-xr-x  3 root root 7.0K grub
 18M -rw-r--r--  1 root root  18M initrd.img-3.12-kali1-amd64
 16M -rw-r--r--  1 root root  16M initrd.img-3.7-trunk-amd64
 12K drwx------  2 root root  12K lost+found
173K -rw-r--r--  1 root root 173K memtest86+.bin
175K -rw-r--r--  1 root root 175K memtest86+_multiboot.bin
2.3M -rw-r--r--  1 root root 2.3M System.map-3.12-kali1-amd64
2.2M -rw-r--r--  1 root root 2.2M System.map-3.7-trunk-amd64
2.8M -rw-r--r--  1 root root 2.8M vmlinuz-3.12-kali1-amd64
2.3M -rw-r--r--  1 root root 2.3M vmlinuz-3.7-trunk-amd64

[amarok]

I had a similar problem, and you need to fix your crypttab:
First, the man page says it supports UUID, but doesn't mention ID
Second, the real problem is that you have the wrong source device on the second field: I suggest you replace ID=dm-name-cryptroot with /dev/mapper/lvmdebian-encryptedroot
then update-initramfs -u and boot from the new kernel on grub

Explanation: /dev/mapper/cryptroot is the luks device with your decrypted data, so cryptroot goes on the first field of crypttab; the second field is the source device, ie the container that has the encrypted data, which in this case is the lvm partition on /dev/mapper/lvmdebian-encryptedroot