Bug#429928: cryptsetup: can't boot with kernel 2.6.21
On Fri, Jun 22, 2007 at 08:58:30PM +0200, Jonas Meurer wrote: severity 429928 minor thanks On 22/06/2007 Dmitry Borodaenko wrote: Maybe some of these modules where compiled into the 2.6.18 kernel while the 2.6.21 kernel has compiled them as modules. You are right, cbc and blkcipher were missing. After adding these to /etc/yaird/Default.cfg, the kernel now boots, although it still complains about missing gzip binary (doesn't do any harm, any idea why it needs it?). Guess this bug can now be upgraded to normal or even minor, but it would still be nice to update documentation about this issue, README.initramfs seems like the right place. Or should this bug be reassigned to yaird to make sure that it automatically detects this situation? Hey Dmitry, I just downgraded the severity to minor, but I guess that you're right with the assumption that yaird should automatically add these modules when they're needed for an encrypted root fs. I'm not sure how initramfs-tools behaves though, so I'll wait for a comment from David who knows much more about ramdisk stuff. David, can we expect that yaird handles this case automatically? Then I would reassign the bug to yaird. Otherwise we should at least document it somewhere, as Dmitry suggested. The initramfs scripts adds the correct block cipher modules, I guess that yaird's crypto logic needs similar fixes, so yes - it seems reasonable to reassign the bug to yaird. -- David Härdeman
Bug#429928: [Pkg-cryptsetup-devel] Bug#429928: cryptsetup: can't boot with kernel 2.6.21
(just noticed my previous email didn't get to the bug, see below: On 6/22/07, Dmitry Borodaenko [EMAIL PROTECTED] wrote: On 6/21/07, Jonas Meurer [EMAIL PROTECTED] wrote: This most likely means that the required crypto kernel modules were not loaded by the initramfs. For aes-cbc-essiv:sha256, you need the kernel modules dm-mod, dm-crypt, aes, cbc, sha256 and blkcipher. If you use initramfs-tools, add all these to /etc/initramfs-tools/modules and regenerate the initramfs afterwards. Maybe some of these modules where compiled into the 2.6.18 kernel while the 2.6.21 kernel has compiled them as modules. You are right, cbc and blkcipher were missing. After adding these to /etc/yaird/Default.cfg, the kernel now boots, although it still complains about missing gzip binary (doesn't do any harm, any idea why it needs it?). Guess this bug can now be upgraded to normal or even minor, but it would still be nice to update documentation about this issue, README.initramfs seems like the right place. Or should this bug be reassigned to yaird to make sure that it automatically detects this situation? Minor addition: found what caused the gzip error, it's this like in yaird's init script: gunzip /etc/console/boottime.kmap.gz Obviously it has nothing to do with cryptsetup. -- Dmitry Borodaenko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#429928: cryptsetup: can't boot with kernel 2.6.21
severity 429928 minor thanks On 22/06/2007 Dmitry Borodaenko wrote: Maybe some of these modules where compiled into the 2.6.18 kernel while the 2.6.21 kernel has compiled them as modules. You are right, cbc and blkcipher were missing. After adding these to /etc/yaird/Default.cfg, the kernel now boots, although it still complains about missing gzip binary (doesn't do any harm, any idea why it needs it?). Guess this bug can now be upgraded to normal or even minor, but it would still be nice to update documentation about this issue, README.initramfs seems like the right place. Or should this bug be reassigned to yaird to make sure that it automatically detects this situation? Hey Dmitry, I just downgraded the severity to minor, but I guess that you're right with the assumption that yaird should automatically add these modules when they're needed for an encrypted root fs. I'm not sure how initramfs-tools behaves though, so I'll wait for a comment from David who knows much more about ramdisk stuff. David, can we expect that yaird handles this case automatically? Then I would reassign the bug to yaird. Otherwise we should at least document it somewhere, as Dmitry suggested. ... jonas -- In post-historical society, the rulers have ceased to rule, but the slaves remain slaves. - Perry Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#429928: cryptsetup: can't boot with kernel 2.6.21
Package: cryptsetup Version: 2:1.0.4+svn29-1 Severity: important When booting latest Linux kernel 2.6.21 from unstable (linux-image-2.6.21-1-686 2.6.21-4), device mapper reports Error allocating crypto tfm (see screen photo at boot time[0]) and returns to the step of asking for password. [0] http://people.debian.org/~angdraug/cryptsetup-error.jpg Kernel 2.6.18 (linux-image-2.6.18-4-686 2.6.18.dfsg.1-12) boots without errors. [EMAIL PROTECTED]:~$ cat /etc/crypttab # target device source device key file options root/dev/sda5 nonecipher=aes-cbc-essiv:sha256 #swap /dev/sda6 /dev/urandomswap -- Dmitry Borodaenko -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (50, 'testing'), (50, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) Locale: LANG=be_BY.UTF-8, LC_CTYPE=be_BY.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cryptsetup depends on: ii dmsetup 2:1.02.18-1 The Linux Kernel Device Mapper use ii libc62.5-11 GNU C Library: Shared libraries ii libdevma 2:1.02.18-1 The Linux Kernel Device Mapper use ii libgcryp 1.2.4-2 LGPL Crypto library - runtime libr ii libpopt0 1.10-3 lib for parsing cmdline parameters ii libuuid1 1.39+1.40-WIP-2007.04.07+dfsg-2 universally unique id library cryptsetup recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#429928: [Pkg-cryptsetup-devel] Bug#429928: cryptsetup: can't boot with kernel 2.6.21
On 21/06/2007 Dmitry Borodaenko wrote: Package: cryptsetup Version: 2:1.0.4+svn29-1 Severity: important When booting latest Linux kernel 2.6.21 from unstable (linux-image-2.6.21-1-686 2.6.21-4), device mapper reports Error allocating crypto tfm (see screen photo at boot time[0]) and returns to the step of asking for password. [EMAIL PROTECTED]:~$ cat /etc/crypttab # target device source device key file options root/dev/sda5 nonecipher=aes-cbc-essiv:sha256 #swap /dev/sda6 /dev/urandomswap This most likely means that the required crypto kernel modules were not loaded by the initramfs. For aes-cbc-essiv:sha256, you need the kernel modules dm-mod, dm-crypt, aes, cbc, sha256 and blkcipher. If you use initramfs-tools, add all these to /etc/initramfs-tools/modules and regenerate the initramfs afterwards. Maybe some of these modules where compiled into the 2.6.18 kernel while the 2.6.21 kernel has compiled them as modules. ... jonas -- In post-historical society, the rulers have ceased to rule, but the slaves remain slaves. - Perry Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
