If the kernel is compiled with support for a certain feature/hardware (it will be marked with a * in menuconfig), then yes, the size of the kernel increases accordingly. If you just add support as a module (marked with a M), the kernel size is not increased. Some modules will be loaded at boot, so it isn't always necessary to edit /etc/rc.d/rc.modules. However, if you have a module that you need loaded and it does not load by default, then uncommenting it or adding a line for it in rc.modules will usually suffice.

Exellent post.

One note, please correct the spelling of :

make modules_install

the "e" in modules is missing

Done :-)

Is it possible to compile and install single module (which was completely missed before) without recompiling and reinstall all modules? Maybe it can be done by inserting parameter (module name or something) to "make modules" and "make modules_install"?

Make takes care of compiling only the changed files (modules). If the modules are already compiled, they are not compiled again.

I've followed the directions posted above; however, when rebooting, it still boots up 2.4.20 kernel.

It states, "loading Linux.old.....".

What have I overlooked?

I believe you may have something goofy with your lilo.conf...can you post its' contents here?

Here it is.

peter@Carbuncle:~$ less /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
append = "hdc=ide-scsi hdd=ide-scsi"
#compact # faster, but won't work on all systems.
#prompt
#timeout = 5
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz.old
root = /dev/hda1
label = Linux.old
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

You only have an entry for your old kernel in that lilo.conf - vmlinuz.old - you need to add an entry for your new kernel and run lilo to update.

Okay, I spoke too soon. I had thought that it was working but didn't look too closely and I went back to work.

Coming back to my machine, I see that it's still 2.4.20.

I grabbed a sysadmin who looked at it and he had me run lilo -v and it returned:

yadda yadda...

Boot image: /boot/vmlinuz
Added Carbuncle *

Boot image: /boot/vmlinuz.old -> vmlinuz-ide-2.4.20
Added Linux.old

/boot/boot.0300 exists - no backup copy made.
Writing boot sector.

Stumped.

My lilo.conf is as follows now:

yadda yadda ...

boot = /dev/hda
append = "hdc=ide-scsi hdd=ide-scsi"
#compact # faster, but won't work on all systems.
#prompt
#timeout = 5
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = Carbuncle
read-only
image = /boot/vmlinuz.old
root = /dev/hda1
label = Linux.old
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
~
/etc/lilo.conf lines 1-43/43 (END)

This is my first time I'm trying to recompile a kernel (cuz kde 3.1 takes about 10 seconds just to start up applications and I don't like other guis). I downloaded slackware online and burned it to cd, then did full install (with all applications etc.), but now when I'm trying to follow your guide and you mentioned going to /usr/src/linux/Makefile with text editor, but when I go to /usr/src the only folder there is rpm (and no files there either), after this I searched my disk for makefile and found about 40 of them (and I have no clue which one is the one I need), could someone help me? Thanks.

You need to download and untar a kernel.

thanks, I've recompiled my kernel, and now my KDE 3.1 opens everything up instantly (used to be up to 20 seconds before), I didn't know kernel would have this much effect on KDE. But there is another problem now. Linux no longer supports sound (and it even gives an error message about that when it boots up) and the internet no longer works. For the internet I think I know what the problem might be, I didn't think I would need to share files across computers so I disabled file sharing with other computers and from other computers, but since I use a router it probabaly thinks of my router as a computer too. So I think I can fix the internet (I hope), but I have no clue what to do about the sound, I think I only disabled one sound option that said I should type lspci -n to see if I was using it, and when I typed it it said that I wasnt using that thing, os I said N for it.

Great guide. thanks.

However, my guide does not include 'make menuconfig' 'make clean' and 'make' but 'make mproper' and 'make config' So I was wondering if anyone could tell me the difference?

make mproper is like an aggressive make clean
make config is make menuconfig but text based.

On Another Note:
If, like me, you can't be arsed to deal with modules. Just compile them directly into the kernel (e.g '*' and not 'M' in make menuconfigs selection boxes).
You loose the advantages of dynamically loading and unloading modules/drivers. But I have no need to do that :-)
And to get detailed information on an option in make menuconfig just press "SHIFT + ?" when the option is selected.

Aaron