When trying to create an encrypted file system, the cryptsetup command is failing. Comparing the list of kernel modules loaded in the installer, with those in a Mageia 2 install, where it's working, I suspect diskdrake now has to modprobe aesni_intel, and the installer has to be modified to include the aesni-intel.ko.xz kernel module. I'll attach the report.bug file.
Created attachment 2746 [details] report.bug after cryptsetup fails
Whiteboard: (none) => 3alpha1
CC: (none) => ennael1
CC: (none) => thierry.vignaud
Status: NEW => ASSIGNEDAssignee: bugsquad => thierry.vignaud
Fixed in git
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
Though you have an AMD cpu and it shouldn't been needed on your machine. And aes-generic would work anyway. In your case, the cryptsetup command took too long and was killed by timeout
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Also next time compress the file before uploading
(In reply to comment #3) > Though you have an AMD cpu and it shouldn't been needed on your machine. > And aes-generic would work anyway. > In your case, the cryptsetup command took too long and was killed by timeout That doesn't make sense on this hardware. # time cryptsetup --cipher=aes-xts-benbi --key-size=512 luksFormat --batch-mode /dev/sda10 /tmp/.dmcrypt_key real 0m3.263s user 0m3.210s sys 0m0.031s /dev/sda10 is a 26.32 GB partition on an ssd drive. Creating the encrypted file system worked with the latest dual-cd, although rebooting into the installed system failed. Bug 7382 reported. I'll retest the i586 dvd before closing this bug.
Closing this bug, as an install done using the latest i586 dvd successfully created an encrypted root filesystem, and booted into it.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED