[Pkg-cryptsetup-devel] Bug#429928: Bug#429928: cryptsetup: can't boot with kernel 2.6.21

[Dmitry Borodaenko]

(just noticed my previous email didn't get to the bug, see below:

On 6/22/07, Dmitry Borodaenko <angdraug at gmail.com> wrote:
> On 6/21/07, Jonas Meurer <jonas at freesources.org> 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