Build Your Own Kernel
Build Your Own Kernel
Contents
1. Build Environment
2. Obtaining the source for an
Ubuntu release
1. apt
2. git
3. Modifying the configuration
4. Building the kernel
5. Testing the new kernel
6. Debug Symbols
7. See also
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.
Build Environment
If you have not built a kernel on your system before, there are some packages needed before
you can successfully build. You can get these installed with:
Unfortunately, the above does not install all of the necessary dependencies. The current Disco
Dingo release requires the following additional packages.
The above command requires your system to have the correct deb-src lines in
/etc/apt/sources.list. For example, on Disco Dingo you should have:
deb-src http://archive.ubuntu.com/ubuntu disco main
deb-src http://archive.ubuntu.com/ubuntu disco-updates main
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 method 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.
apt
The source code which generated a specific binary package may be obtained using the
apt source <package> command. For example to obtain the source for the currently
running kernel you can use the command:
git
The build process uses a configuration that is put together from various sub-config files. The
simplest way to modify anything here is to run the commands below. This takes the current
configuration for each architecture/flavour supported and calls menuconfig to edit its config
file. The chmod is needed only if you obtain the source by apt rather than git, because the
way the source package is created, it loses the executable bits on the scripts.:
In order to make your kernel "newer" than the stock Ubuntu kernel from which you are
based, you should add a local version modifier. Add something like "+test1" to the end of the
first version number in the debian.master/changelog file, before building. This will help
identify your kernel when running as it also appears in uname -a. Note that when a new
Ubuntu kernel is released that will be newer than your kernel (which needs regenerating), so
care is needed when upgrading. NOTE: do not attempt to use CONFIG_LOCALVERSION
as this _will_ break the build.
If the build is successful, several .deb binary package files will be produced in the directory
above the build root directory. For example after building a kernel with version "4.8.0-17.19"
on an amd64 system, these three (or more) .deb packages will be produced:
cd ..
ls *.deb
linux-headers-4.8.0-17_4.8.0-17.19_all.deb
linux-headers-4.8.0-17-generic_4.8.0-17.19_amd64.deb
linux-image-4.8.0-17-generic_4.8.0-17.19_amd64.deb
On later releases, you will also find a linux-extra- package which you should also install if
present.
Debug Symbols
Sometimes it is useful to have debug symbols built as well. Two additional steps are needed.
First pkg-config-dbgsym needs to be installed. Second when executing the binary-* targets
you need to add 'skipdbg=false'.