[solved] aesni_intel module not loaded since switch to kmod

Question

Since installing kmod-4-1 as replacement for module-init-tools the AES-NI instruction optimized crypto modules (aesni_intel) don't get loaded automatically anymore.
CPU is a SandyBridge Core-i5 2500K; aes-x86_64 isn't loaded anymore either. The CPU definitely supports AES-NI.
Is this a problem or am I supposed to write those modules down by hand in rc.conf MODULES section?
Kind regards
lynix
Last edited by lynix (2012-02-01 20:57:25)

Answer 1

Nevermind. I found the bug -- I'll make sure this is fixed for kmod5.
tech note for those interested:
A module alias can resolve to many modules -- in this case, the alias 'aes' resolves to "aes_generic", "padlock_aes", "aesni_intel", and "aes_x86_64". modprobe, including the library equivalent, should insist on trying to insert all of these. kmod does, but it makes the mistake of quitting if one of them errors out. To wit:
with module-init-tools:
# modprobe -v aes
insmod /lib/modules/3.2.2-1-ARCH/kernel/crypto/aes_generic.ko.gz
insmod /lib/modules/3.2.2-1-ARCH/kernel/drivers/crypto/padlock-aes.ko.gz
WARNING: Error inserting padlock_aes (/lib/modules/3.2.2-1-ARCH/kernel/drivers/crypto/padlock-aes.ko.gz): No such device
insmod /lib/modules/3.2.2-1-ARCH/kernel/crypto/cryptd.ko.gz
insmod /lib/modules/3.2.2-1-ARCH/kernel/arch/x86/crypto/aes-x86_64.ko.gz
insmod /lib/modules/3.2.2-1-ARCH/kernel/arch/x86/crypto/aesni-intel.ko.gz
WARNING: Error inserting aesni_intel (/lib/modules/3.2.2-1-ARCH/kernel/arch/x86/crypto/aesni-intel.ko.gz): No such device
with kmod:
# modprobe -v aes
insmod /lib/modules/3.2.2-1-ARCH/kernel/crypto/aes_generic.ko.gz
insmod /lib/modules/3.2.2-1-ARCH/kernel/drivers/crypto/padlock-aes.ko.gz
ERROR: could not insert 'padlock_aes': No such device
Last edited by falconindy (2012-02-01 20:54:47)