Cryptsetup and the 3.18.27-1 Kernel

Discuss development on Bubba
MouettE
Site admin
Posts: 271
Joined: 06 Oct 2011, 19:45

Re: Cryptsetup and the 3.18.27-1 Kernel

Post by MouettE » 15 Dec 2018, 22:34

Hello,

Well the messages are expected because you are downgrading the kernel. It's not such a big deal though.

That being said I'm going to try to fix the new kernel. I'll keep you posted, in the meantime either mark the bubb3-kernel to hold or do not upgrade to avoid replacing your -88 working version with the new -135 version.

hooper35
Posts: 23
Joined: 13 Sep 2007, 04:43

Re: Cryptsetup and the 3.18.27-1 Kernel

Post by hooper35 » 16 Dec 2018, 15:26

Thanks.

MouettE
Site admin
Posts: 271
Joined: 06 Oct 2011, 19:45

Re: Cryptsetup and the 3.18.27-1 Kernel

Post by MouettE » 21 Dec 2018, 21:16

Hello,

I just ran a few tests on my b3 and the 4.9.135-1 kernel have no problem opening an encrypted volume with aes-xts-plain64 :

Code: Select all

root@b3:~# uname -a
Linux b3 4.9.135-1 #1 Fri Oct 26 22:08:33 EDT 2018 armv5tel GNU/Linux
root@b3:~# cryptsetup -v luksOpen /dev/sda2 test
Saisissez la phrase secrète pour /dev/sda2 :
Emplacement de clé 0 déverrouillé.
Opération réussie.
root@b3:~# cryptsetup -v status test
/dev/mapper/test is active.
  type:    LUKS1
  cipher:  aes-xts-plain64
  keysize: 256 bits
  device:  /dev/sda2
  offset:  4096 sectors
  size:    1044480 sectors
  mode:    read/write
Opération réussie.
Maybe you could check your syslog for more details, or run cryptsetup with --debug to try identify more precisely the cause of the error ?

Post Reply