Ok, it seems that the module auto-loading does occur. I booted both the current stock Lucid kernel 2.6.32-22-generic and the latest Lucid mainline kernel 2.6.34-020634-generic after commenting out the alias lines I previously added to /etc/modprobe.d/aliases.conf and the modules are still loaded and are listed by lsmod:
dmesg | egrep -i 'rng|aes|sha|padlock' [ 1.570984] alg: No test for stdrng (krng) [ 1.999550] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 4.334218] padlock: Using VIA PadLock ACE for AES algorithm. [ 4.345308] padlock: Fallback driver 'sha1' could not be loaded! [ 4.345325] alg: hash: Failed to load transform for sha1-padlock: -2 [ 4.349040] padlock: Fallback driver 'sha256' could not be loaded! [ 4.349056] alg: hash: Failed to load transform for sha256-padlock: -2 [ 4.349090] padlock: Using VIA PadLock ACE for SHA1/SHA256 algorithms. [ 4.355390] VIA RNG detected lsmod | egrep 'rng|padlock' via_rng 1323 0 padlock_sha 3363 0 padlock_aes 5079 0 aes_generic 26863 1 padlock_aes My bad :) Seems this bug can be closed. -- Crypto engine module loading and breakage https://bugs.launchpad.net/bugs/355384 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
