Mailinglist Archive: opensuse-bugs (6901 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=467014

https://bugzilla.novell.com/show_bug.cgi?id=467014#c17


Beat Meier <mbe_ml@xxxxxxxxxxxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mbe_ml@xxxxxxxxxxxxxxxxxx.a
                   |                            |r

--- Comment #17 from Beat Meier <mbe_ml@xxxxxxxxxxxxxxxxxxxxx> 2011-03-06 
20:31:47 UTC ---
Jeff

I have the same problem. You can reproduce it when you have an luks encrypted
partition (created with defaults from cryptsetup-1.1.2-3.3.x86_64 i.e.
cbc-essiv:sha256) and an entry in /etc/crypttab which will be loaded at
startup.
The messages in dmesg are:

[    7.608301] padlock: VIA PadLock not detected.
[   27.271036] padlock: VIA PadLock Hash Engine not detected.

For example my entry for /etc/crypttab is:
  SecData1 /dev/sdb11 none luks,tries=2,timeout=10

If you mount this partition with the right password there will be the
message...
The same message apears if you try to load the module with
  modprobe padlock-sha
-> FATAL: Error inserting padlock_sha
(/lib/modules/2.6.34.7-0.7-desktop/kernel/drivers/crypto/padlock-sha.ko): No
such device

I load the following additional modules to use cryptsetup in 
/etc/sysconfig/kernel
  dm_crypt aes
to create my initrd

It seems to be a problem in a dependency which tries to load padlock-sha.ko
even not used ...

If you need more information send me an email, will be glad to help

Greetings

Beat

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.