[Pkg-cryptsetup-devel] Bug#466573: Bug#466573: cryptsetup: 2.6.25-rc2 does not boot due to "Error allocating crypto tfm"

[Didier Raboud]

Le jeudi, 21 février 2008 00.08:15 David Härdeman, vous avez écrit :
> Didier, as a test, could you try booting with the "break" parameter,
> that should at least drop you into a shell even if cryptsetup refused
> to.
>
> Then you can do a "modprobe crypto_blkcipher", followed by "exit" which
> will continue the boot process. If that sorts it out, we at least know
> which module isn't being loaded properly.

Hi, 

I tried the boot with "break". I could get a prompt _before_ the LUKS 
passphrase. At this state, `cat /proc/modules` is empty. I can modprobe 
crypto_blkcipher, but it doesn't help for later LUKS passphrase.

But maybe something new : as I erased my "quiet vga=792" to put break, I 
noticed one more interessant line (hand-copied, sorry for eventual 
inaccuracy):

> device doesn't appear to be in the dev hash table.

Regards, 

Didier



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20080221/dc45db2e/attachment.pgp