How To Compile A Kernel - The CentOS Way - Page 2
3 Building A Kernel The Traditional Way
This chapter describes a different approach that can be used on any Linux system. As there's nothing CentOS-specific in this, of course you will not end up with a kernel rpm package.
3.1 Download The Kernel Sources
We download our desired kernel to /usr/src. Go to www.kernel.org and select the kernel you want to install, e.g. linux-22.214.171.124.tar.bz2 (you can find all 2.6 kernels here: http://www.kernel.org/pub/linux/kernel/v2.6/). Then you can download it to /usr/src like this:
Then we unpack the kernel sources and create a symlink linux to the kernel sources directory:
tar xjf linux-126.96.36.199.tar.bz2
3.2 Modify /etc/modprobe.conf
Now we must comment out the mptscsi module in /etc/modprobe.conf because otherwise we will get a warning like this:
WARNING: No module mptscsi found for kernel 188.8.131.52, continuing anyway
when we build our new kernel.
3.3 Apply Patches To The Kernel Sources (Optional)
Sometimes you need drivers for hardware that isn't supported by the new kernel by default, or you need support for virtualization techniques or some other bleeding-edge technology that hasn't made it to the kernel yet. In all these cases you have to patch the kernel sources (provided there is a patch available...).
Now let's assume you have downloaded the needed patch (I call it patch.bz2 in this example) to /usr/src. This is how you apply it to your kernel sources (you must still be in the /usr/src/linux directory):
bzip2 -dc /usr/src/patch.bz2 | patch -p1 --dry-run
The first command is just a test, it does nothing to your sources. If it doesn't show errors, you can run the second command which actually applies the patch. Don't do it if the first command shows errors!
If your patches are compressed with gzip (.gz) instead of bzip2 (.bz2), then you patch your kernel as follows:
gunzip -c /usr/src/patch.gz | patch -p1 --dry-run
You can also apply kernel prepatches to your kernel sources. For example, if you need a feature that is available only in kernel 2.6.19-rc6, but the full sources haven't been released yet for this kernel. Instead, a patch-2.6.19-rc6.bz2 is available. You can apply that patch to the 2.6.18 kernel sources, but not to kernel 184.108.40.206 or 220.127.116.11 or 18.104.22.168, etc. This is explained on http://kernel.org/patchtypes/pre.html:
Prepatches are the equivalent to alpha releases for Linux; they live in the testing directories in the archives. They should be applied using the patch(1) utility to the source code of the previous full release with a 3-part version number (for example, the 2.6.12-rc4 prepatch should be applied to the 2.6.11 kernel sources, not, for example, 22.214.171.124.)
So if you want to compile a 2.6.19-rc6 kernel, you must download the 2.6.18 kernel sources (http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.18.tar.bz2) in step 3.1 instead of kernel 126.96.36.199!
This is how you apply the 2.6.19-rc6 patch to kernel 2.6.18:
3.4 Configure The Kernel
It's a good idea to use the configuration of your current working kernel as a basis for your new kernel. Therefore we copy the existing configuration to /usr/src/linux:
make clean && make mrproper
Then we run
which brings up the kernel configuration menu. Go to Load an Alternate Configuration File and choose .config (which contains the configuration of your current working kernel) as the configuration file:
Then browse through the kernel configuration menu and make your choices. When you are finished and select Exit, answer the following question (Do you wish to save your new kernel configuration?) with Yes:
3.5 Build And Install The Kernel
To build and install the kernel, execute these three commands:
Now be patient, the kernel compilation can take some hours, depending on your kernel configuration and your processor speed. The last command will also automatically create a ramdisk for you as well as configure /boot/grub/menu.lst.
Now edit /boot/grub/menu.lst. You should find a stanza for your new kernel at the top of the list, but to make sure that the new kernel gets booted instead of your old one, you must set the value of default to 0.
My menu.lst looks like this:
Now reboot the system:
shutdown -r now
If everything goes well, it should come up with the new kernel. You can check if it's really using your new kernel by running
This should display something like
If the system doesn't start, restart it, and when you see this:
press any key to enter the GRUB menu:
Select your old kernel and start the system. You can now try again to compile a working kernel. Don't forget to remove the stanza of the not-working kernel from /boot/grub/menu.lst.