On Sun, 16 Aug 2009 23:44:44 +0200 Jonas Meurer <[email protected]> wrote:
> On 16/08/2009 Celejar wrote: > > On Sun, 16 Aug 2009 23:10:58 +0200 > > Jonas Meurer <[email protected]> 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. Right you are; I experimented, and modprobe doesn't complain no matter what I tell it to load - it just fails silently. > 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). Yup, I was doing this wrong. But after modprobing correctly, the best I could get was this: ~$ cat /boot/proc-crypto-iii name : sha256 driver : sha256-generic module : sha256_generic priority : 0 refcnt : 1 selftest : passed type : shash blocksize : 64 digestsize : 32 descsize : 168 name : sha224 driver : sha224-generic module : sha256_generic priority : 0 refcnt : 1 selftest : passed type : shash blocksize : 64 digestsize : 28 descsize : 168 name : aes driver : aes-asm module : aes_i586 priority : 200 refcnt : 1 selftest : passed type : cipher blocksize : 16 min keysize : 16 max keysize : 32 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 cbc will not load, no matter what I try. Any idea what the problem could be? > 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. But they *are* - I see them under lib/modules/xxxx/kernel/crytpo: aes_generic.ko cbc.ko crypto_algapi.ko crypto_blkcipher.ko crypto_hash.ko sha256_generic.ko So something is seriously messed up with my kernel / initramfs config - sha256 needs to be manually loaded, and cbc refuses to load at all. Any idea where to go from here? Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
