Hi, > > the module was actually completely broken in 2.6.32 if > > CONFIG_CRYPTO_FIPS=y (which it is in Debian packages). However, it > > also looks like this was fixed in 2.6.32.19, which is incorporated in > > the source for the current package.
> fyi, 2.6.32-12 & 2.6.32-29 w/ CONFIG_CRYPTO_AES_NI_INTEL=m both boot > successfully w/ the aesni_intel module on my Lenovo T410. Reading the bug log I'm tempted to conclude that this problem has been dealt with, at least since 2.6.32.19. The module has also since long been enabled in unstable. Would it therefore be feasible to re-enable it in an upcoming Squeeze point update? thanks, Thijs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
