Comment 9 for bug 305934

I just want to add that I also experienced this with a recent backports kernel on Debian Lenny (). It seems like the padlock-sha modules loads the kernel generic sha module as fallback. I had the following aliases set:

alias aes padlock_aes
alias sha1 padlock_sha

Removing the sha1->padlock_sha alias made the module load fine at boot time and /proc/crypto looks nice without failing selftests. This seems to be a change from earlier kernel versions, where this alias was recommended to be set by some tutorials.