Hi Ben, Ben Hutchings wrote, on 23-01-10 15:57:
This shouldn't be a problem - all modules will be loaded and the best one for the hardware will be used. We should stop padlock-aes printing an error message in this case though.
I know this is not a serious bug causing malfunction, but I would really like the dependency to be fixed so I can get a nice clean boot for my customers.
Waiting for /dev to be fully populated...modprobe: WARNING: Error inserting padlock_aes (/lib/modules/2.6.30-2-686/kernel/drivers/crypto/padlock-aes.ko): No such device Waiting for /dev to be fully populated...modprobe: WARNING: Error inserting padlock_aes (/lib/modules/2.6.32-3-686/kernel/drivers/crypto/padlock-aes.ko): No such device
I am still getting the warning on both:
Linux version 2.6.30-2-686 (Debian 2.6.30-8squeeze1) (da...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Fri Dec 4 00:53:20 UTC 2009 Linux version 2.6.32-3-686 (Debian 2.6.32-9) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Thu Feb 25 06:14:20 UTC 2010
Could somebody make the small change and fix this issue? I hope to get this fixed for the upcoming release. Thank in advance, With kind regards, Jelle de Jong -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bfa6534.6040...@powercraft.nl
