(In reply to Takashi Iwai from comment #16) for case (3), @ desktop, with flags: -ssse3 -aes cat /proc/cpuinfo | egrep "model name|flags" | head -n2 model name : AMD Phenom(tm) II X4 945 Processor flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate npt lbrv svm_lock nrip_save > They are just built-in, so they are always there on that kernel flavor. Hence modprobe "fails". But > the functionality is already present on your system. Can you clarify where it 'is', then? lsmod | egrep -i "aes|sha|sse" | grep -v sharp aes_x86_64 17131 0 sha512_generic 12942 0 which requires /etc/modprobe.d/99-local-crypto.conf alias aes aes-x86_64 alias sha512 sha512_generic but modprobe sha1 modprobe: ERROR: could not find module by name='sha1_generic' modprobe: ERROR: could not insert 'sha1_generic': Function not implemented modprobe sha256 modprobe: ERROR: could not insert 'sha256_ssse3': No such device modprobe sha1_generic lsmod | egrep -i "aes|sha|sse" | grep -v sharp aes_x86_64 17131 0 sha512_generic 12942 0 modprobe sha256_generic lsmod | egrep -i "aes|sha|sse" | grep -v sharp aes_x86_64 17131 0 sha512_generic 12942 0 I.e., there's no sha1_* sha256_* module/capability