Re: Creating kernel packages with make-kpkg

Hallo, > I was told, just recently in debian-devel, that only the kernel needs > to be patched (and only the top-level Makefile). Apparently, the > patch applies cleanly to 2.2.17, not sure about 2.4.x Looks like that's right. The kernel modules are now installed in /lib/modules/2.2.17-adder

Creating kernel package with IPSEC support

Hi, Finally I figured out that my last problem (Modules are not working and make menuconfig shows me an empty kernel menu) has something todo with the Freeswan-Patch. If I don't use it, all is working fine, but if I apply it to the kernel I have the mentioned problems. I have tried two ways to

Re: Creating kernel packages with make-kpkg

Hallo, > You shouldn't be using the --flavour option unless you > have patched the kernel using the patch supplied in > /usr/doc/kernel-package/Flavours.gz Ah, haven't known that. Thanks. > Klaus> the modules? And are these module packages compatible with > Klaus> all kernel 2.2.17

Creating kernel packages with make-kpkg

Hi, I have created some kernel packages with make-kpkg and now I want to build the alsa- and pcmcia-modules for these kernels. For example I have two different kernel packages: kernel-image-2.2.17-mamba - This is a standard kernel with no additional patches kernel-image-2.2.17-adder

Problems creating new kernel packages with make-kpkg

Hi, I have some strange problems using make-kpkg. I'm trying to create debian packages for a heavily patched 2.2.17 kernel. I choosed "uni" as flavour and currently I am at revision "12". I create the packages with the command make-kpkg --bzImage --flavour uni --revision 12 buildpackage The