Adrian Sevcenco wrote: > Hi! I try to load an module that it is found in curent > /lib/modules/`uname -r` tree ... > root at sevcenco: ~ # ls -l /lib/modules/`uname > -r`/kernel/drivers/crypto/padlock-* > -rwxr--r-- 1 root root 14296 Mar 16 19:37 > /lib/modules/2.6.38-0.el5.elrepo/kernel/drivers/crypto/padlock-aes.ko > -rwxr--r-- 1 root root 10808 Mar 16 19:37 > /lib/modules/2.6.38-0.el5.elrepo/kernel/drivers/crypto/padlock-sha.ko I notice you're using the elrepo-provided ml kernel, not the centos one. > but if i try : > root at sevcenco: ~ # modprobe -v padlock-aes.ko > FATAL: Module padlock_aes.ko not found. > > notice the change from - to _ > Any idea about this? I don't think that's relevant. man modprobe says: note that for convenience, there is no difference between _ and - in module names. Do you get anything in dmesg after the failure? > or more abstract: > have anyone succeed to use padlock (via) hardware with openssl (or other > software) in centos?