Description of problem:
I've been attempting to install F12 x86_64 on a new T410 laptop.
I've enabled disk encryption in the Anaconda UI, with a default partitioning scheme. This is a new laptop, with no previous OS installed.
Manual installation appears to succeed, provided I pass "nomodeset vnc" at installation boot line.
However, on attempting to boot, I get various error messages.
Unable to get a direct screenshot, so manually typing the following:
alg: No test for __aes-aesni (__driver-aes-aesni)
alg: No test for __ecb-aes-aesni (__driver-ecb-aes-aesni)
alg: No test for __cbc-aes-aesni (__driver-cbc-aes-aesni)
alg: No test for __ecb-aes-aesni (cryptd(__driver-ecb-aes-aesni))
padlock: VIA PadLock not detected.
alg: skcipher: Failed to load transform for xts-aes-aesni: -2
device-mapper: table: 253:0: crypt: Error allocating crypto tfm
device-mapper: ioctl: error adding target to table
device-mapper: reload ioctl failed: Invalid argument
Failed to setup dm-crypt key mapping for device /dev/sda2
Check that kernel supports aes-xts-plain-cipher (check syslog for more info).
Failed to read from key storage
Ray Strode told me this is an issue with hardware crypto support: the hardware apparently has hardware crypt support, but a buggy module means that the crypto doesn't work, and thus the encrypted OS can't be booted.
The workaround of adding:
to the kernel boot line fixed it for me. (Documenting it here in Bugzilla)
Version-Release number of selected component (if applicable):
Created attachment 398629 [details]
Photo of the boot failure
The problem is still present with the latest F12 kernel update; on this hardware I still need to use "rdblacklist=aesni-intel" to boot successfully (with encrypted partitions as per defaults), or the boot fails with (apparently) the same errors as in comment #0.
This is with:
Can you get to a shell after boot fails and see what is in /proc/crypto?
So this error occurs regardless of install or not? (IE: blacklisted on install, then unblacklist and it will fail)
I'm looking into it now, it's a very strange error in a mess of code... If it happens outside of the installer it will be easier for me to test it.
kernel-188.8.131.52-79.fc13 has been submitted as an update for Fedora 13.
kernel-184.108.40.206-79.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
I had my wireless AP set to use AES for encryption, and after upgrading to kernel-220.127.116.11-79.fc13 I have no longer been able to connect to my wireless network. Now that I see this change I can probably just change the encryption settings on my AP (once I get home later today), but this might have broken things for other users who aren't able to control the cipher used by access points they use.
No. That's a different bug and unrelated to this. You still have AES support, this just removes the ability to use the Core i7 AES instructions to accelerate it.
Was this also happening on F-13? The bug was reported against F-12 and that is still not fixed, but a patch went into F-13...
Could this be happening because we have CONFIG_CRYPTO_FIPS=y set in our .config? That will disable any crypto drivers that fail testing, and we are seeing messages that no tests exist for that driver.
This patch added NULL tests for those algorithms (?):
Added patch from comment #10 to 18.104.22.168-144
Reported fixed via IRC. Also added a fix from F-13 in 22.214.171.124-145 for the async crypto testing error messages.
kernel-126.96.36.199-150.fc12 has been submitted as an update for Fedora 12.
kernel-188.8.131.52-150.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/kernel-184.108.40.206-150.fc12
kernel-220.127.116.11-150.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.