Comment 3 for bug 140906

Sorry, I forgot a very important question all this brings up ...

Given that I now have a kernel that boots (and leaving aside that fact that hopefully my hardware
will be fixed soon, so that all of this is mute), how do I go about and build a working boot medium (netboot) for
the install? For reasons leading too far I made fresh installs of feisty (rather than upgrades) for a number
of machines until I encountered this combination of (so far unnoticed) hardware problem and
kernel bug. I install via netboot, and it seems to me that lots of modules (i.e., stuff that normally is in
the initrd) is in udebs which are loaded on demand (usually while the installer says "checking hardware" or
something like this. It's at this point that the system hangs. I have a local mirror, so adding a new udeb there
is not the problem (although there might be checksum issues?). But how do I go about building these udebs?
Hints (pointers to documentation appreciated!!!)

As I say, my question may not be urgent in this case, since hopefully a few days from now I'll have fully
workign hardware, but the problem could arise in the future ("not yet supported hardware etc")