[arch-general] new mkinitcpio / harmless error message at boot
After doing a pacman -Syu and installed the mkinitcpio 0.6 , I'm getting an error insmoding padlock-sha just after I enter the root device luks encryption passphrase. I'm assuming there is an easy solution to this. Any idea?
On 02/11/2010 02:52 PM, Hussam Al-Tayeb wrote:
After doing a pacman -Syu and installed the mkinitcpio 0.6 , I'm getting an error insmoding padlock-sha just after I enter the root device luks encryption passphrase. I'm assuming there is an easy solution to this. Any idea?
harmless. i've been seeing it for years. if it bothers you, blacklist the module in mikinitcpio.conf and rebuild. On 02/11/2010 03:01 PM, Hussam Al-Tayeb wrote:
Why does /lib/initcpio/hooks/encrypt say /sbin/cryptsetup but the actual installed file is /sbin/cryptsetup.static?
[kludge@an ~]$ locate cryptsetup | grep bin /sbin/cryptsetup.static /usr/sbin/cryptsetup [kludge@an ~]$ ls -al /usr/sbin/cryptsetup -rwxr-xr-x 1 root root 20404 Jan 24 07:53 /usr/sbin/cryptsetup [kludge@an ~]$ ls -al /sbin/cryptsetup.static -rwxr-xr-x 1 root root 1131736 Jan 24 07:53 /sbin/cryptsetup.static crypsetup.static is, well, static and links to no libraries. bigger, but stands alone, in case /lib gets fubar'd. better? -kludge
Am 11.02.2010 21:52, schrieb Hussam Al-Tayeb:
After doing a pacman -Syu and installed the mkinitcpio 0.6 , I'm getting an error insmoding padlock-sha just after I enter the root device luks encryption passphrase. I'm assuming there is an easy solution to this. Any idea?
I think I added the option CRYPTO_MODULES to restrict which modules are added to initramfs - this way you can omit padlock. But using this option also can completely screw up everything. I don't think you should worry about the padlock messages, they just appear because virtually nobody has a padlock encryption device.
participants (3)
-
Hussam Al-Tayeb
-
kludge
-
Thomas Bächler