Hi!

 

I'm trying to use the image Cubietruck_Debian_3.8_jessie_4.0.4.raw with my CubieTruck, but run into problems when trying to use an external LUKS-disk which is encrypted using aes-xts-plain64.

 

'cryptsetup luksOpen' informs the following:

device-mapper: reload ioctl on  failed: No such file or directory
Failed to setup dm-crypt key mapping for device /dev/disk/by-uuid/<xxxx>.
Check that kernel supports aes-xts-plain64 cipher (check syslog for more info).

'cat /proc/crypto | grep name' lists only this, which seems kinda minimal:

name         : stdrng
name         : stdrng
name         : crc32c
name         : deflate
name         : ecb(arc4)
name         : arc4
name         : aes
name         : des3_ede
name         : des
name         : sha224
name         : sha256
name         : sha1
name         : md5
name         : md4

Directory /lib/modules/4.0.4-cubietruck/kernel/crypto/ has these files:

af_alg.ko  algif_rng.ko  async_tx  ccm.ko  crypto_null.ko  ctr.ko  fcrypt.ko  gcm.ko  gf128mul.ko  ghash-generic.ko  pcbc.ko  seqiv.ko

So, it seems that some crypto modules for the kernel are missing, but I don't know which ones are needed ('aes-xts' or similar, at least, maybe?).

 

Any ideas on what to do? Do I need to compile the kernel to include the modules? Does the older 3.4.x(?) kernel have these included?

 

Thanks.

New kernel config:

https://github.com/igorpecovnik/lib/blob/next/config/linux-sunxi-next.config

 

CONFIG_DM_CRYPT=m

 

This is enabled as module.

 

I also don't know what exactly is needed without research and can only add blindly some new modules in this area but it will take some time before I rebuild a kernel. In such cases is better and faster if you try to build a kernel by your own. That's why I made a script

 

When compiling remember to save the .config because it's overwritten on each run. 

 

Old kernel config:

https://github.com/igorpecovnik/lib/blob/next/config/linux-sunxi.config

 

Don't know. Simply try it and than we have at least something to compare to.