On Fri, 2010-01-22 at 21:06 +0100, Jelle de Jong wrote: > Package: linux-image-2.6.30-2-686 > Version: 2.6.30-8squeeze1 > Severity: normal > > > Waiting for /dev to be fully populated...modprobe: WARNING: Error > inserting padlock_aes > (/lib/modules/2.6.30-2-686/kernel/drivers/crypto/padlock-aes.ko): No > such device > > # uname -a > Linux alix07 2.6.30-2-686 #1 SMP Fri Dec 4 00:53:20 UTC 2009 i586 > GNU/Linux > > # modprobe --show-depends aes > insmod /lib/modules/2.6.30-2-686/kernel/crypto/aes_generic.ko > insmod /lib/modules/2.6.30-2-686/kernel/drivers/crypto/padlock-aes.ko > insmod /lib/modules/2.6.30-2-686/kernel/crypto/aes_generic.ko > insmod /lib/modules/2.6.30-2-686/kernel/arch/x86/crypto/aes-i586.ko > insmod /lib/modules/2.6.30-2-686/kernel/crypto/aes_generic.ko This shouldn't be a problem - all modules will be loaded and the best one for the hardware will be used. We should stop padlock-aes printing an error message in this case though. Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo.
Attachment:
signature.asc
Description: This is a digitally signed message part