Bug 437272 - padlock: No such device
Summary: padlock: No such device
Keywords:
Status: CLOSED DUPLICATE of bug 438288
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cryptsetup-luks
Version: 5.2
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Milan Broz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-13 10:39 UTC by Matthew Booth
Modified: 2013-03-01 04:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-19 14:29:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matthew Booth 2008-03-13 10:39:24 UTC
Description of problem:
Immediately after entering my first LUKS password (but not the second), I get a
warning something like:

modprobe: WARNING: Unable to load padlock (/lib/modules/..../padlock.ko): No
such device

This is displayed on the console every time, but I can't find it in a log file
anywhere. It doesn't appear to actually relate to any breakage, but it looks
scary. I suggest one of the following:

* It should be made to insert properly
* It should not probed if the hardware is not present
* The error message should be suppressed

Version-Release number of selected component (if applicable):
initscripts-8.45.19.EL-1.i386
kernel 2.6.18-84.el5xen

How reproducible:
Always

Comment 1 Bill Nottingham 2008-03-13 15:20:28 UTC
This is either cryptsetup-luks or dm-crypt.

Comment 2 Milan Broz 2008-03-13 15:33:08 UTC
(In reply to comment #1)
> This is either cryptsetup-luks or dm-crypt.

Neither. It's product of autodetection of kernel crypto module (AES), it just
use generic module later if hw is not detected - anyway, error message should be
probably suppressed.


Comment 3 Milan Broz 2008-06-19 14:29:02 UTC
Kernel padlock.ko issue, see https://bugzilla.redhat.com/show_bug.cgi?id=438288#c4


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


Note You need to log in before you can comment on or make changes to this bug.