Kernel & kpkg Questions

[MADHATter7]

I was ready to to install the kernel 2.2.18 I compiled from the kernel-source-2.2.18.deb package AGAIN last night and thought I should get a little clarification first:

Based on all of the man pages, kernel docs, /usr/docs and info I have read, this is what I believe the procedure is:

unpack the source code
make clean
make config or make menuconfig or make xconfig
select your configuration
then make modules (??)
then make-dpkg --revision=customXX kernel_image
then dpkg -i kernel-image-2.2.18-XX.deb

The modules part is what I need assistance with. I know the kpkg installs the modules and such, but does the make-kpkg also make the modules ??

And WHAT exactly is proper form as far as modules go ? (General Opinions) I mean, I understand that the more options you compile as a module, the smaller (& faster) the kernel is. Basically, what do you do ?

For instance, my old kernel (2.2.12 - from Slink) used apx. 5-6% idle w/ XFree, gkrellm, Netscape and an Eterm running. I compiled 2.2.18 already (but compiled w/ everything I needed in the kernel - no modules) and it runs apx. 15-20% under the same conditions. However, the 2.2.18 will smoke the 2.2.12 as far as speed goes, even with all options in the kernel ! Is this normal ? And why ?

Just wanted to be sure I am performing this step properly ....

Thanks in advance for any/all assistance

------------------
MADHATter7

EMAIL : madhatterus@netscape.net
ICQ : 101324593
AIM : MADHATTERus
Yahoo : madhatt_t00l

[teeitup]

I've had very unpredictable results using kpkg. Sometimes it's the greatest and other times it doesn't work at all.

I have gone back to the standard procedure of compiling and installing kernels and modules.

Just my 2 cents. I would like to here others experiences with kpkg.



------------------
Don't take life to seriously, You'll never get out alive!
-Bugs Bunny-

[MADHATter7]

Well, I will post my own answer, since I hate doing a search on the forums only to find an exact match for what I am looking for and follow the thread to the end for it to not post the final resolution to the original question(s).

At any rate, make-kpkg DOES make the modules as well, which are then install by the follow-up dpkg -i command.

BTW, teeitup, this is the second 2.2.18 kernel I have compiled and installed with the kernel-package and it works sweet. I removed all *bloat* from the kernel and put it in module form.

It improved overall speed a little, but not too much....

Happy compiling !

------------------
MADHATter7

EMAIL : madhatterus@netscape.net
ICQ : 101324593
AIM : MADHATTERus
Yahoo : madhatt_t00l

[Craig McPherson]

I've compiled about every kernel from 2.0.32 to 2.4.0 with make-kpkg, and I haven't had any trouble with it -- just remember to increment your revision number if you compile the same kernel version multiple times. I think it's so awesome, how it updates the /vmlinuz and /vmlinuz.old symlinks automatically and everything.

And, yes, it does do modules and everything, though you already know that now...

[Strike]

My first kernel package was 2.4.0 and it worked flawlessy for me. I didn't even put a revision flag on and it automatically appended the "Custom" stuff on the end. 'Twas rather smooth. I have no regrets from going over to the Debian side of things so far, none at all.

[X_Entity]

Debian/Rulez.

only thing I ever had a problem with was if they release a new kernel image it has once tried to upgrade my kernel in my normal evening apt-get upgrade. This shoudln't happen if you set the custom version high enough.
Kpkg takes all the work out of compiling a kernel and just makes life easier.

Debian/Rulez