Bug#544227: why does the same thing work with 2.6.26?

[Mark Hedges <hedges@scriptdolphin.com>]

> I know that it works with the shipped images:
>
> | $ cat /proc/cmdline
> | BOOT_IMAGE=/vmlinuz-2.6.31-rc5-686-bigmem root=/dev/mapper/crypt_root ro resume=/dev/mapper/crypt_swap
>
> And we can't support arbitrary broken things done with our
> packages.

Please help me understand what that means without jumping
to conclusions or being dismissive before you understand.
What did I do that was "arbitrarily broken"?

Please help me understand how to build 2.6.30 with make-kpkg
so that it mounts root correctly using dm-crypt.

I was able to build 2.6.26 kernels using make-kpkg, and the
resulting .deb worked fine when installed, without any other
configuration.

I cannot build a successful .deb from 2.6.30 using
make-kpkg, with any config, even the one from the stock
2.6.30-1-486 kernel.

Is it possible that the correct modules are not being
installed in the initrd image?  That happened once with some
earlier kernel, 2.6.22 I seem to recall.

Simply asked:  what do I need to add, to get make-kpkg to
build a .deb that will boot a dm-crypt image?

Why don't you try it before you close the bug, eh?

Mark