Ubuntu Wiki

This page will describe how to easily build the kernel.

The majority of users that are interested in building their own kernel are doing so because they have installed Ubuntu on their system and they wish to make a small change to the kernel for that system. In many cases the user just wants to make a kernel configuration change.

The purpose of this page is to give that user a minimum amount of information for them to meet the goal of making a simple change to the kernel, building it and installing their kernel. It is not intended to be the definitive guide to doing Ubuntu kernel development.

Obtaining the source for an Ubuntu release

There are a number of different ways of getting the kernel sources. The two main ways will be documented here.

If you have installed a version of Ubuntu and you want to make changes to the kernel that is installed on your system, use the apt-get method (described below) to obtain the sources.

However, if you wish to get the most up to date sources for the Ubuntu release you are running and make changes to that, use the git method (described below) to obtain the sources.

apt-get

The source code which generated a specific binary package may be obtained using the apt-get source <package> command. For example to obtain the source for the currently running kernel you can use the command:

• apt-get source linux-image-$(uname -r)

git

All of the Ubuntu Kernel source is maintained under git. The source for each release is maintained in its own git repository on kernel.ubuntu.com. To obtain a local copy you can simply git clone the repository for the release you are interested in as shown below.

• git clone git://kernel.ubuntu.com/ubuntu/ubuntu-<release>.git

For example to obtain the maverick tree:

• git clone git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git

Build Environment

If you've not built a kernel on your system before, there are some packages needed before you can successfully build. You can get these installed with:

• sudo apt-get build-dep linux-image-$(uname -r)

Modifying the configuration

This step can be skipped if no configuration changes are wanted. The build process will use a configuration that is put together from various sub-config files. The simplest way to modify anything here is to run:

• chmod a+x debian/scripts/misc/*
  fakeroot debian/rules clean
  fakeroot debian/rules editconfigs

This take the current configuration for each architecture/flavour supported and call menuconfig for that. The chmod is needed because the way the source package is created looses the executable bits on the scripts.

Building the kernel

Building the kernel is quite easy. Change your working directory to the root of the kernel source tree and then type the following commands:

• fakeroot debian/rules clean
  fakeroot debian/rules binary-headers binary-generic

If the build is successful, a set of three .deb binary package files will be produced in the directory above the build root directory. For example after building a kernel with version "2.6.38-7.37" on an amd64 system, these three .deb packages would be produced:

• cd ..
  ls *.deb
      linux-headers-2.6.38-7_2.6.38-7.37_all.deb
      linux-headers-2.6.38-7-generic_2.6.38-7.37_amd64.deb
      linux-image-2.6.38-7-generic_2.6.38-7.37_amd64.deb

Testing the new kernel

Install the three-package set (on your build system, or on a different target system) with dpkg -i and then reboot:

• sudo dpkg -i linux*2.6.38-7.37*.deb
  sudo reboot

Cross compiling for ARM

Check out ti-omap4 branch, then run the following commands:

For armel

• apt-get install gcc-arm-linux-gnueabi
  export $(dpkg-architecture -aarmel)
  export CROSS_COMPILE=arm-linux-gnueabi-
  fakeroot debian/rules binary-omap4

For armhf

• apt-get install gcc-arm-linux-gnueabihf
  export $(dpkg-architecture -aarmhf)
  export CROSS_COMPILE=arm-linux-gnueabihf-
  fakeroot debian/rules binary-omap4

See also

The above instructions provide a very simple recipe for obtaining the sources and then building them. If you are going to be doing more kernel development than simple configuration changes you may want to look at:

Git the source