https://bugzilla.novell.com/show_bug.cgi?id=396209 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=396209#c5 Matthias Koenig <mkoenig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mkoenig@novell.com |kernel-maintainers@forge.provo.novell.com --- Comment #5 from Matthias Koenig <mkoenig@novell.com> 2008-06-12 08:39:29 MDT --- Well, the init scripts don't insert this module -- it's the kernel. The error mesage is triggered by the cryptsetup luksOpen call. But this does not call modprobe. It just sets up dm-crypt with the AES cipher. It seems dm-crypt requests this cipher from the kernel crypto API, so any module with an aes alias is loaded by the kernel, so it also tries to load padlock-aes which spits out this error. I don't think, we can do here anything in userspace, we just request AES -- how this is done by the kernel and which implementation it chooses is beyond our reach. -- 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.