Bug#293508: initrd-tools refuses to make an initrd when lvm support is compiled, in the kernel

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

maximilian attems <debian@sternwelten.at> writes:

> On Fri, 04 Feb 2005, Benedict Verheyen wrote:
>
>> I'm trying to switch from a 2.4.24 kernel to a 2.6.10 kernel and
>> in the process go from lvm1 to lvm2. My root is also on lvm.
>> When i compile a kernel with lvm2 in it, so no dm-mod to be found,
>> mkinitrd refuses to build an initrd saying "Kernel does not support LVM".
>> 
>> If i set lvm2 as module, then it makes an initrd.
>> 
>> root@arthur# mkinitrd -o initrd.img-2.6.10.03feb2005-skas3-v7 -r
>> /dev/main/lv_root 2.6.10.03feb2005-skas3-v7
>> /usr/sbin/mkinitrd: /dev/mapper/main-lv_root: Kernel does not support LVM
>> 
>> root@arthur# grep "DM" /boot/config-2.6.10.03feb2005-skas3-v7
>> ...
>> CONFIG_BLK_DEV_DM=y
>> ...
>> 
>
> well initrd makes only sense for modularized kernels,
> why are you at all building an initrd?
> i'm very enclined to close that bug.

One might need it for dm_crypt or other not automagical stuff.

MfG
        Goswin