On 08/02/2008 Joachim Breitner wrote: > > The errors are obviously not produced by cryptsetup itself, but rather > > by some initramfs magic. that's the reason why they only appear at boot > > process, and not at invoking cryptdisks/cryptsetup manually. > > I’m not sure about his. I am pretty sure the error messages came _after_ > I entered the password the first time, but _before_ cryptsetup exits, > which I noticed when I entered the password wrong the first time, and > the second prompt came after the error messages. > > I’ll make sure this observation is correct at the next boot. > > Also, fgrepping the contents of my initramdisk for padlock, I only get: > ./lib/modules/2.6.24-1-686/kernel/drivers/crypto/padlock-aes.ko. > ./lib/modules/2.6.24-1-686/kernel/drivers/crypto/padlock-sha.ko. > ./sbin/cryptsetup. > ./usr/lib/libcrypto.so.0.9.8. > > so no script is manually loading these. Hey Joachim, Still some script adds the modules to you initramdisk, but i'm not sure whether this is initramfs-tools (update-initramfs) or some thirdparty script. Maybe you could add some debugging code to /usr/share/initramfs-tools/scripts/local-top/cryptroot and/or /usr/share/initramfs-tools/hooks/cryptroot? David, could you give further advice? greetings, jonas
Attachment:
signature.asc
Description: Digital signature