You are not logged in.
Pages: 1
Topic closed
Hi
Im using luks encrypted root and storage, so right after booting (pressing in my password) it says something about not finding the module padlock-sha? Why? I mean, since it boots fine and unlocks the volumes.
Offline
Same here, with encrypted swap only.
1000
Offline
Same here, seems to be something with the new kernel
Offline
Thats wired, thanks for the link tough. But it doesnt solve the problem, this is my laptop i use @ work. I cant risk it dying. Everything does work, for now, and thats the important part.
Offline
I get the same warning, with everything encrypted except boot. There don't seem to be any consequences though.
Offline
If you're able to read & understand German, the solution is here: http://wiki.archlinux.de/?title=Festpla … lermeldung, but I give you a short summary (be REALLY careful and HAVE a FALLBACK image to boot):
First find out what modules your crypto system needs by comparing the output of
cd /lib/modules/$(uname -r)
source /lib/initcpio/functions
m="$(all_modules "/crypto/") "
echo $m
and
lsmod
Then edit your /etc/mkinitcpio.conf (as root) and add a line containing all your needed modules, e.g. my line looks like
CRYPTO_MODULES="xts aes_i586 aes_generic"
This way you tell the hook "encrypt" not to load unneccessary modules, BUT if you forget one needed module, the unlocking of your crypted device won't work. So just imagine what happens if you can't unlock your crypted root on boot, then: Use your fallback image!
The last step is to update your image by issuing (as root)
mkinitcpio -g /boot/kernel26.img
Now it's possible that udev tries to load the padlock modules, so just blacklist them by creating a file (call it e.g. padlock) in the directory /etc/modprobe.d/ and add the following contents:
blacklist padlock-aes
blacklist padlock-sha
Hope this helps.
Offline
An easier solution is to add this to your /etc/modprobe.conf
blacklist padlock_aes
blacklist padlock_sha
That's what I've done on my laptop after I migrated my /home partition to be encrypted this afternoon. All working OK
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
You do want the padlock modules if your laptop has a VIA CPU.
Offline
You do want the padlock modules if your laptop has a VIA CPU.
In which case the errors shouldn't be appearing, no?
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
apaige: Sure, but with a VIA cpu you also don't get those error messages as those modules will load just fine. ;-)
1000
Offline
An easier solution is to add this to your /etc/modprobe.conf
blacklist padlock_aes blacklist padlock_sha
That's what I've done on my laptop after I migrated my /home partition to be encrypted this afternoon. All working OK
No, for me *only* blacklisting the modules did not help since the encrypt hook tries to load all modules with its own routine and blacklisting is not respected. So only the combination of blacklisting *and* telling the encrypt-hook what modules you need solved the problem for me.
Offline
In my case the change of modules list in mkinitcpio.conf alone helped, with no change in modprobe.conf. And it's true that you have to be very careful and remember to add all the used modules in CRYPTO_MODULES line. I forgot to add one, and ended with maintance from USB drive.
Thanks!
Offline
rabinhood: please don't necro-bump http://wiki.archlinux.org/index.php/For … Bumping.27
Closing
Offline
Pages: 1
Topic closed