[pkg-cryptsetup-devel] Bug#541835: Bug#541835: cryptsetup: unclear kernel requirements

[Jonas Meurer]

On 16/08/2009 Celejar wrote:
> On Sun, 16 Aug 2009 23:10:58 +0200
> Jonas Meurer <jonas at freesources.org> wrote:
> > so you at least need aes, cbc and sha256 kernel modules.
> 
> ~$ cat /boot/proc-crypto 
> name         : aes
> driver       : aes-generic
> module       : aes_generic
> priority     : 100
> refcnt       : 1
> selftest     : passed
> type         : cipher
> blocksize    : 16
> min keysize  : 16
> max keysize  : 32
> 
> So it seems that cbc and sha256 are indeed not being properly loaded.
> But this was after I had manually modprobed cbc.ko and
> sha256_generic.ko (without error).  Any way to figure out why they
> aren't being properly loaded?

i don't know, but maybe the modprobe in initramfs is a striped down
version that doesn't print out errors if the modules don't exist.

how exactly did you try to load cbc and sha256? because you need to give
the module name as argument, not the filename (i.e. modprobe cbc, not
modprobe cbc.ko).

if everything is setup properly, the cryptroot initramfs script should
load required modules automaticly anyway, so i guess that your selfbuild
kernel simply doesn't have cbc and sha256 modules compiled.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20090816/095d6219/attachment.pgp>