Hi, Hussam Al-Tayeb wrote:
Same issue here. If possible, can one of the developers please take a look at this?
My name change analysis was wrong.It seems that cryptsetup is triggering the loading of padlock-aes.ko and padlock-sha.ko even on hardware that doesn't work with them.
I ignored them in /etc/modprobe.conf with: install padlock_aes /bin/true install padlock_sha /bin/true Regards, Neil Darlow
