cryptsetup fails after linux-imx6-cubox-dt 3.14.14 upgrade

[Daimusou]

On 3.14.24-1 now, and I still have this problem.

[pepedog]

There is no kernel that can do it all.
3.0 can't do Bluetooth
3.14 can't do caam, although mk01 says it can and linux4kix says it can't
3.17/18rc can't do gpu stuff

[patrykk]

You could try my kernel base on 3.17.7 with staff ported for udoo:
https://github.com/patrykk/linux-udoo

best regards,

[pg99]

Newest standard kernel (3.14.26-1) also doesn't work. If I manage to find the time, I'll try to install your 3.17.7 kernel and see if that works. Thanks for the post! I'll let you know how that goes. (PS. Some Cubox people are trying to focus on the 3.14 kernel to finally get one kernel 'that does it all': http://www.solid-run.com/community/topic1525.html. I am still silently hoping that at some point this will be successfull).

[crystaltraveler]

Came across this thread with the same issue on my novena board. I found out what's wrong.

The AESBS crypto driver is buggy for XTS on ARM (https://github.com/torvalds/linux/blob/ ... sbs-glue.c). To use aes-xts-* ciphers you'll have to build a new kernel with

$this->bbcode_second_pass_code('', 'CONFIG_CRYPTO_AES_ARM_BS=m
CONFIG_CRYPTO_XTS=m')

Then after installing your new kernel, before running cryptsetup, run:

$this->bbcode_second_pass_code('', 'rmmod aes-arm-bs
modprobe xts')

as root. Hope this helps!

[pepedog]

Sadly this doesn't work on the CuBox

[themylogin]

crystaltraveler, your solution works like a charm! Thanks a lot!

pepedog, it worked for me on hummingboard, it should work for you on cubox. Try it again re-checking all steps.