Bug 612940

Summary:	padlock-sha.ko): No such device
Product:	[openSUSE] openSUSE 11.3	Reporter:	David Kerkhof <dutchkind>
Component:	Basesystem	Assignee:	Ludwig Nussel <lnussel>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P4 - Low	CC:	dutchkind, meissner, pmlists
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description David Kerkhof 2010-06-09 16:28:04 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; nl; rv:1.9.2.4) Gecko/20100527 SUSE/3.6.4-6.1 Firefox/3.6.4

During boot I get the following message:

modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.34-8-desktop/kernel/drivers/crypto/padlock-sha.ko): No such device

I have an encrypted tmp and swap, so probably has to do with it.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1 Marcus Meissner 2010-06-10 07:03:08 UTC

is there an error in "dmesg" ?

Comment 2 David Kerkhof 2010-06-10 15:13:08 UTC

I looked, found no hints to this error in dmesg

Comment 3 Stephan Kulow 2010-10-25 14:17:34 UTC

Marcus, what exactly were you looking for with your question?

Comment 4 Marcus Meissner 2010-10-26 09:10:12 UTC

dont remember anymore.

the module probably needs to be in the initrd if it is used to enable the crypto stuff?

Comment 5 Peter Münster 2010-10-26 20:19:23 UTC

Hello,
Any news about this issue?  It's still present in 11.3 with all updates.
Cheers, Peter

Comment 6 Stephan Kulow 2010-10-27 06:47:45 UTC

I have no idea where this is coming from, but I have no experience about encrypted partitions either.

Comment 7 Ludwig Nussel 2010-10-27 08:36:02 UTC

Something (I don't know whether it's the kernel or modprobe or whatever magic) loads all modules that implement sha algorithms. padlock-sha requires hardware that is not present and therefore prints this message. It's harmless though as the generic implementation is loaded as well.

*** This bug has been marked as a duplicate of bug 467014 ***