there a way to update kernel throught RPM and but it's just wrong at my opinion... RH/Mandrake RPMed kernel is a big bloated generic kernel with tons of modules and stuff you won't need. Nothing worth a very small optimized kernel compiled from source.
About your update :
-Don't use "make mrproper". This clean out the kernel configuration, unless you want to start over, you usually don't need this.
-make oldconfig tries to make a default base config based on your actual kernel configuration.
- at this point, you probably want to take a look at the config to add/change some options. type "make menuconfig" (or make xconfig if you are in X). You will get a menu with tons of options. Don't panic, even the uber geek down here don't know every single options. Just go with your general feeling, it's generally safe to add too much thing, just make sure you aren't missing anything. If you are in doubt, look at the "help" dialog. With some practice you will compile very small, efficient kernels.
- You should not type make bzImage right now. Since you are compiling a 2.6 kernel (it's way easier than 2.4) just type "make all". It will build the kernel and then run make bzImage by itself. Easy.
- Once it is done (make sure there is no mistake) you have to copy the kernel image you just build in your /boot and to edit your boot loader (/boot/grub.conf or /etc/lilo.conf) to point to this new file. The kernel image is in /usr/src/linux-XXX/arch/i386/boot/bzImage. Rename it the way you want and make sure to ajust the boot loader.
Depending your boot loader configuration, you might want to copy /usr/src/linux-XXX/System.map too.
- Now, you have to type "make modules_install" to install all new modules you compiled. Once this is done you can risk a reboot.
- Ps 1 : Make sure to keep an entry in the boot loader that point to the "old" kernel, the one that was working already. You will probably need few try to get your kernel working, so you better keep a way to boot the old working one. In worst case, you can use your installation CD to boot into your system, if you broke something.
- Ps 2 : Time... Compiling a kernel take some time but I am really surprised it took you that long. It takes around 4 hours on my P166, so it should take you really less time. On my 1Ghz, it takes around 25 mins, so it,s not that bad. Note the first time you compile it will take much more time (because then it wont recompile part that don't need too).
- Ps 3: Compiling kernel from source can be hard, hazardous, annoying, long BUT it's one of the best thing you can do to learn about linux and how it manages hardwares. Plus most hardwares problems (like "My XXXX device is not working") can be solved by recompiling the kernel (instead of relying on default one). You might not see it right now but it's really something usefull that you need to learn
