CentOS - Mar 2011 - modprobe :: not finding existing .ko

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

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?
or more abstract:
have anyone succeed to use padlock (via) hardware with openssl (or other 
software) in centos?

Thanks,
Adrian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3110 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://lists.centos.org/pipermail/centos/attachments/20110318/bd3d8bc6/attachment-0001.p7s>

centos-bounces at centos.org 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
> 
> 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?
> or more abstract:
> have anyone succeed to use padlock (via) hardware with openssl (or
> other software) in centos?
> 
> Thanks,
> Adrian
Thought: Link your padlock-aes.ko to also exist as padlock_aes.ko
Does modprobe now find the files?

Are there aliases in modprobe.conf that (in effect) map - to _ in module
names?

Insert spiffy .sig here:
Life is complex: it has both real and imaginary parts.

//me
*******************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom
they are addressed. If you have received this email in error please
notify the system manager. This footnote also confirms that this
email message has been swept for the presence of computer viruses.
www.Hubbell.com - Hubbell Incorporated**

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?

On Fri, Mar 18, 2011 at 9:03 AM, Adrian Sevcenco
<Adrian.Sevcenco at cern.ch> 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
>
> but if i try :
> root at sevcenco: ~ # modprobe -v padlock-aes.ko
> FATAL: Module padlock_aes.ko not found.
When using the modprobe command, you need to omit the ".ko" part.

Akemi

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
> 
> 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?
> or more abstract:
> have anyone succeed to use padlock (via) hardware with openssl (or other 
> software) in centos?
Have you run 'modprobe -a' since installing the modules?

James Pearson

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
>
> but if i try :
> root at sevcenco: ~ # modprobe -v padlock-aes.ko
> FATAL: Module padlock_aes.ko not found.
<snip>
Here's a question: what kernel are you running? The most current CentOS
5.5 is 2.6.18-194.32.1.el5, while you're pointing to 2.6.38-0, unless I
misunderstand how the elrepo modules are installed.

         mark