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
signature.asc
Description: This is a digitally signed message part.
