I had the same problem after the latest ubuntu upgrade. I fixed it by adding an initscript which removes the mapper device before crypdisks. It still asks a password, so it can't be used with remote reboots.
Not directly related to this bug, but I suggest also that the linurc script could print some debug messages if the kernel command line contains a debug or verbose switch: case "$(cat /proc/cmdline)" in *verbose*|*debug*) verbose=true;; esac test "$verbose" && echo "Running initrd linuxrc..." I have spent some time figuring out that why the password was asked and where... Regarding the software suspend problem we could try to swapoff the crypt device before suspend and abort the suspend if there is not enough ram to run without swap. Not sure if this is possible. -- Massimo Dal Zotto <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
