On Mon, Jan 03, 2011 at 08:29:02PM +0000, Ben Hutchings wrote: > On Mon, 2011-01-03 at 10:12 -0700, dann frazier wrote: > > On Mon, Jan 03, 2011 at 05:05:32AM +0000, Ben Hutchings wrote: > > > On Sun, 2011-01-02 at 21:30 -0700, dann frazier wrote: > > > > On Sun, Jan 02, 2011 at 08:57:19PM +0000, Ben Hutchings wrote: > > > [...] > > > > > Please can you test whether aesni-intel loads and works in: > > > > > > > > > > 1. Package version 2.6.32-12 > > > > > <http://snapshot.debian.org/package/linux-2.6/2.6.32-12/>. This was > > > > > the > > > > > last version with aesni-intel included. > > > > > > > > > > 2. Package version 2.6.32-29, modified to reenable aesni-intel. See > > > > > the > > > > > instructions at > > > > > <http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>. > > > > > a. Follow section 4.2.1. > > > > > b. Change '# CONFIG_CRYPTO_AES_NI_INTEL is not set' to > > > > > 'CONFIG_CRYPTO_AES_NI_INTEL=m' in > > > > > debian/config/kernelarch-x86/config-arch-64. > > > > > c. Follow section 4.2.4. > > > > > > > > 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. > > > > > > I'm guessing you don't have an AES-encrypted hard drive though... > > > > I do: > > > > $ sudo cryptsetup status sda5_crypt > > /dev/mapper/sda5_crypt is active: > > cipher: aes-cbc-essiv:sha256 > > [...] > > > > Though I don't know how to verify that the hardware implementation is > > actually being used. > > I think that trying to remove the module is a valid test.
Finally found a convenient time to reboot; in both cases (-12 & -29 + the module) the module is unremovable on my system. -dann -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org