From Fedora Project Wiki

(Add grubby so that make install works with an upstream kernel)
 
(21 intermediate revisions by 8 users not shown)
Line 12: Line 12:
 
Not all of these will apply to all methods but this provides a good dependency list of items to install
 
Not all of these will apply to all methods but this provides a good dependency list of items to install
  
<code> # sudo dnf install fedpkg fedora-packager rpmdevtools ncurses-devel pesign pesign-rh-test-certs</code>
+
<code> # sudo dnf install fedpkg fedora-packager rpmdevtools ncurses-devel pesign grubby</code>
  
 
Give the following command from the top directory of the kernel source tree once you have checked it out
 
Give the following command from the top directory of the kernel source tree once you have checked it out
Line 24: Line 24:
 
Also make sure you add the user doing the build to /etc/pesign/users and run the authorize user script:
 
Also make sure you add the user doing the build to /etc/pesign/users and run the authorize user script:
  
<code># sudo /usr/libexec/pesign/pesign-authorize-users</code>
+
<code># sudo /usr/libexec/pesign/pesign-authorize</code>
  
It should be noted that pesign pesign-rh-test-certs gets pulled in automatically for some, but not for everyone, it depends on how you installed pesign.  It is best to make sure that you have it installed.
+
It should be noted that pesign pesign-rh-test-certs gets pulled in automatically for some, but not for everyone, it depends on how you installed pesign.  It is best to make sure that you have it installed.  
 +
 
 +
{{admon/note|pesign|Also note that <code>pesign</code> is applicable only for UEFI platforms (x86, arm, aarch64), it's not used on eg. ppc64le or s390x.}}
  
 
{{admon/note|dnf versus yum|As of Fedora 22[https://docs.fedoraproject.org/en-US/Fedora/22/html/Release_Notes/] [[dnf]] has replaced [[yum]] as the default package manager. In the event you are building a kernel for an older system you will either have to install dnf or substitute <code>yum</code> for <code>dnf</code> and/or <code>yumdownloader</code> from the <code>yum-utils</code> package.}}
 
{{admon/note|dnf versus yum|As of Fedora 22[https://docs.fedoraproject.org/en-US/Fedora/22/html/Release_Notes/] [[dnf]] has replaced [[yum]] as the default package manager. In the event you are building a kernel for an older system you will either have to install dnf or substitute <code>yum</code> for <code>dnf</code> and/or <code>yumdownloader</code> from the <code>yum-utils</code> package.}}
Line 40: Line 42:
 
<code> $ fedpkg clone -a kernel </code>
 
<code> $ fedpkg clone -a kernel </code>
  
As of the time of this wiki writing (April 2015), the kernel was managed using git. Each fedora release is a separate branch. rawhide tracks master. To get the tree for a particular release, you can use git checkout from the top of your newly created source tree.
+
As of the time of this wiki writing, the kernel is managed using git. Each fedora release is a separate branch. rawhide tracks master. To get the tree for a particular release, you can use git checkout from the top of your newly created source tree.
 +
 
 +
e.g. for fedora 23,
 +
 
 +
<code> $ git checkout origin/f23 </code>
 +
 
 +
You can now make whatever changes / customizations you need before generating the rpms and installing them. You may want to consider uncommenting
 +
 
 +
<code> # define buildid .local </code>
 +
 
 +
to avoid conflicts, e.g.
  
e.g. for fedora 22,
+
<code> %define buildid .local </code>
  
<code> $ git checkout origin/f22 </code>
 
  
You can now make whatever changes / customizations you need before generating the rpms and installing them. When finished, generate the appropriate rpms with
+
When finished, generate the appropriate rpms with
  
 
<code> $ fedpkg local </code>
 
<code> $ fedpkg local </code>
Line 64: Line 75:
 
=== Enabling config options ===
 
=== Enabling config options ===
  
If there are configuration options that need to be adjusted for your build, you can add changes in the config-local file. This will override anything set in the rest of the defconfigs.
+
If there are configuration options that need to be adjusted for your build, you can add changes in the kernel-local file. These changes will get picked up when you build.
  
 
=== Updating ===
 
=== Updating ===
Line 79: Line 90:
 
Now you can run whatever other commands you want (e.g. make release)
 
Now you can run whatever other commands you want (e.g. make release)
  
== Building a Kernel from the source RPM ==
+
== Building a kernel from the exploded git trees ==
  
Make sure you have installed all dependencies
+
Fedora keeps a git tree containing Fedora patches applied on top of the vanilla sources.
  
=== Get the Source ===
+
<code> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/fedora.git </code>
{{Admon/warning |Do Not Build Packages as <code>root</code>. | Configuring and building packages as <code>root</code> is inherently dangerous and not required, even for the kernel.  The following instructions allow any normal user to configure and build kernels from the source packages.}}
 
  
# Prepare an RPM package-building environment in your (non-root) home directory by running the following command: <pre>rpmdev-setuptree</pre>This command creates a new directory <code>~/rpmbuild</code>, with several empty subdirectories including <code>SPECS</code>, <code>SOURCES</code>, <code>BUILD</code> and others. It also creates an initial <code>~/.rpmmacros</code> customization file for you.
+
<code> $ git checkout -b my_branch kernel-4.7.4-200.fc24</code>
# Download the <code>kernel-<version>.src.rpm</code> file. It is not necessary to enable the Fedora source repositories -- the <code>dnf download</code> command will do that for you automatically:<pre>dnf download --source kernel</pre>
 
  
{{Admon/note | pre-FC22: # Download the <code>kernel-<version>.src.rpm</code> file.  It is not necessary to enable the Fedora source repositories -- the <code>yumdownloader</code> command will do that for you automatically:<pre>yumdownloader --source kernel</pre>}}
+
You can now build the kernel following regular kernel instructions. This tree is useful for generating patches that can be applied to the kernel.spec.
  
 +
== Building a Kernel from the source RPM ==
  
# Install build dependencies for the kernel source with the <code>dnf builddep</code> command (root is required to install these packages):<pre>su -c 'dnf builddep kernel-<version>.src.rpm'</pre>
+
Instructions for this are on a [[Building_a_custom_kernel/Source_RPM | separate page]]. In general, you should use one of the other methods for building the kernel which are much easier.
# Install <code>kernel-<version>.src.rpm</code> with the following command:<pre>rpm -Uvh kernel-<version>.src.rpm</pre>This command writes the RPM contents into <code>${HOME}/rpmbuild/SOURCES</code> and <code>${HOME}/rpmbuild/SPECS</code>, where <code>${HOME}</code> is your home directory.  It is safe to ignore any messages similar to the following:
 
<pre>warning: user kojibuilder does not exist - using root
 
warning: group kojibuilder does not exist - using root
 
</pre>
 
 
 
{{Admon/warning | Space Required. The full kernel building process requires several gigabytes of extra space on the file system containing your home directory.}}
 
 
 
=== Prepare the Kernel Source Tree ===
 
This step expands all of the source code files for the kernel. This is required to view the code, edit the code, or to generate a patch. (Again, all of this should be done as a regular user, not as root.)
 
 
 
1. Prepare the kernel source tree using the following commands:
 
<pre>cd ~/rpmbuild/SPECS
 
rpmbuild -bp --target=$(uname -m) kernel.spec
 
</pre>
 
 
 
The unloaded and patched kernel source tree is now located in the <code>~/rpmbuild/BUILD/kernel-<version>/linux-<version>.<arch></code> directory.
 
 
 
=== Copy the Source Tree and Generate a Patch ===
 
This step is for applying a patch to the kernel source. If a patch is not needed, proceed to "Configure Kernel Options".
 
 
 
{{admon/note|Advanced Users|There are tools such as 'quilt' that allow you to avoid copying the source tree.  For advanced users, such tools are often a time saver over the steps below|}}
 
 
 
Copy the source tree to preserve the original tree while making changes to the
 
 
 
 
 
<pre>
 
export arch=x86_64 # replace x86_64 with your arch
 
export ver=3.7 # replace 3.1 with your kernel version
 
export subver=4-204
 
export fedver=fc16 # replace fc16 with your fedora version
 
cp -r ~/rpmbuild/BUILD/kernel-$ver.$subver.$fedver ~/rpmbuild/BUILD/kernel-$ver.$fedver.orig
 
cp -al ~/rpmbuild/BUILD/kernel-$ver.$subver.$fedver.orig ~/rpmbuild/BUILD/kernel-$ver.$fedver.new
 
</pre>
 
 
 
{{Admon/warning | The second <code>cp</code> command hardlinks the <code>.orig</code> and <code>.new</code> trees to make <code>diff</code> run faster.  Most text editors know how to break the hardlink correctly to avoid problems. Vim does not break hard links by default, so don't use 'cp -al' use 'cp -r', or look into the 'breakhardlink' setting.}}
 
 
 
Using vim on FC14, it treated the hard link as a hard link and thus the above technique failed.  It was necessary to repeat the original copy used for the .orig directory for the .new directory.  Note that this uses twice the space.
 
 
 
Make changes directly to the code in the <code>.new</code> source tree, or copy in a modified file. This file might come from a developer who has requested a test, from the upstream kernel sources, or from a different distribution.
 
 
 
After the <code>.new</code> source tree is modified, generate a patch. To generate the patch, run <code>diff</code> against the entire <code>.new</code> and <code>.orig</code> source trees with the following command:
 
 
 
<pre>
 
cd ~/rpmbuild/BUILD
 
diff -uNrp kernel-$ver.$subver.$fedver.orig kernel-$ver.$subver.$fedver.new > ../SOURCES/linux-$ver.$subver.$fedver-mynewpatch.patch
 
</pre>
 
 
 
Replace 'linux-$ver.$subver.$fedver-mynewpatch.patch' with the desired name for the new patch.
 
 
 
Lastly edit the patch file to remove the leading directory, this is required because the kernel spec file applies patches with '-p1' only.
 
 
 
For example the following:
 
<pre>
 
--- kernel-3.8.fc18.orig/linux-3.8.11-200.bz708406.fc18.x86_64/kernel/kexec.c        2013-02-18 18:58:34.000000000 -0500
 
+++ kernel-3.8.fc18.new/linux-3.8.11-200.bz708406.fc18.x86_64/kernel/kexec.c    1969-12-31 19:00:00.000000000 -0500
 
</pre>
 
 
 
Should be changed to:
 
<pre>
 
--- linux-3.8.11-200.bz708406.fc18.x86_64/kernel/kexec.c        2013-02-18 18:58:34.000000000 -0500
 
+++ linux-3.8.11-200.bz708406.fc18.x86_64/kernel/kexec.c    1969-12-31 19:00:00.000000000 -0500
 
</pre>
 
 
 
 
 
{{Admon/warning | For more information on patching refer to the man pages for <code>diff(1)</code> and <code>patch(1)</code>.}}
 
 
 
=== Configure Kernel Options ===
 
This step is for modifying the options the kernel is configured with. This step is optional. If no configuration changes are needed, proceed to "Prepare Build Files".
 
 
 
{{admon/important|Small changes|If you only want to make a small number of configuration changes, you should simply set the options as desired in the config-local file.  This will be sourced and override the remaining config-* files and avoids a lot of unnecessary work.  You can skip the steps below if you use config-local}}
 
 
 
# Change to the kernel source tree directory:<pre>cd ~/rpmbuild/BUILD/kernel-$ver.$fedver/linux-$ver.$subver.$fedver.$arch/</pre> If you only want to make minor changes to the default fedora kernel, skip to step 4., and use one of the two configuration tools to edit those minor changes into the default config file.
 
# Select the desired configuration file from <code>~/rpmbuild/BUILD/kernel-$ver.$fedver/linux-$ver.$subver.$fedver.$arch/configs</code>. Copy the desired config file to <code>~/rpmbuild/BUILD/kernel-$ver.$fedver/linux-$ver.$subver.$fedver.$arch/.config</code>: <pre>cp configs/<desired-config-file> .config</pre>
 
# Run the following command: <pre>make oldconfig</pre>
 
# Then run the following command, selecting and saving the desired kernel options from the text-based UI:<pre>make menuconfig</pre>
 
#* For a graphical UI, instead run: <pre>make xconfig</pre>
 
# Add a new line to the top of the config file that contains the hardware platform the kernel is built for (the output of <code>uname -i</code>). The line is preceded by a <code>#</code> sign. For example, an x86_64 machine would have the following line added to the top of the config file:<pre># x86_64</pre>
 
# Copy the config file to <code>~/rpmbuild/SOURCES/</code>: <pre>cp .config ~/rpmbuild/SOURCES/config-`uname -m`-generic</pre>
 
{{admon/important|32-bit x86 kernels|The 32-bit PAE kernel uses the config-i686-PAE configuration file.  If you are building a PAE kernel, you will need to copy your config file to <code>~/rpmbuild/SOURCES/</code>: <pre> cp .config ~/rpmbuild/SOURCES/config-i686-PAE</pre>  If you are building a non-PAE kernel, you will need to copy your config file to <pre> cp .config ~/rpmbuild/SOURCES/config-x86-32-generic</pre>.  Again, the use of config-local is encouraged unless you are making a large number of configuration changes.}}
 
 
 
=== Prepare Build Files ===
 
This step makes the necessary changes to the <code>kernel.spec</code> file. This step is required for building a custom kernel.
 
 
 
1. Change to the <code>~/rpmbuild/SPECS</code> directory:
 
 
 
<pre>cd ~/rpmbuild/SPECS
 
</pre>
 
 
 
2. Open the <code>kernel.spec</code> file for editing.<br>
 
3. Give the kernel a unique name. This is important to ensure the custom kernel is not confused with any released kernel. Add a unique string to the kernel name by changing the 'buildid' line. Optionally, change ".local" to your initials, a bug number, the date or any other unique string.
 
 
 
Change this line:
 
<pre>
 
#% define buildid .local
 
</pre>
 
 
 
To this (note the extra space is removed in addition to the pound sign):
 
<pre>
 
%define buildid .<custom_text>
 
</pre>
 
 
 
4. If you generated a patch, add the patch to the <code>kernel.spec</code> file, preferably at the end of all the existing patches and clearly commented.
 
 
 
<pre># cputime accounting is broken, revert to 2.6.22 version
 
Patch2220: linux-2.6-cputime-fix-accounting.patch
 
 
 
Patch9999: linux-2.6-samfw-test.patch
 
</pre>
 
 
 
The patch then needs to be applied in the patch application section of the spec file. Again, at the end of the existing patch applications and clearly commented.
 
 
 
<pre>
 
ApplyPatch linux-2.6-cputime-fix-accounting.patch
 
 
 
ApplyPatch linux-2.6-samfw-test.patch
 
 
 
 
 
</pre>
 
 
 
=== Build the New Kernel ===
 
This step actually generates the kernel RPM files. This step is required for building a custom kernel.
 
 
 
Use the <code>rpmbuild</code> utility to build the new kernel:
 
 
 
* Ensure /usr/sbin is in your path (to pull in /usr/sbin/modinfo):
 
<pre>export PATH=/usr/sbin:$PATH
 
</pre>
 
 
 
* To build all kernel flavors:
 
<pre>rpmbuild -bb --target=`uname -m` kernel.spec
 
</pre>
 
 
 
* To disable specific kernel flavors from the build (for a faster build):
 
 
 
<pre>rpmbuild -bb --without <option> --target=`uname -m` kernel.spec
 
</pre>
 
 
 
Valid values for "option" above include <code>xen</code>, <code>smp</code>, <code>up</code>, <code>pae</code>, <code>kdump</code>, <code>debug</code> and <code>debuginfo</code>. Specifying <code>--without debug</code> strips out some debugging code from the kernels, where specifying <code>--without debuginfo</code> disables the building of the <code>kernel-debuginfo</code> packages.
 
 
 
* To specify that only a specific kernel should be built:
 
 
 
<pre>rpmbuild -bb --with <option> --target=`uname -m` kernel.spec
 
</pre>
 
 
 
Valid values for "option" above include <code>xenonly</code>, <code>smponly</code>, and <code>baseonly</code>.
 
 
 
* For example, to build just the kernel and kernel-devel packages, the command would be:
 
 
 
<pre>rpmbuild -bb --with baseonly --without debuginfo --target=`uname -m` kernel.spec
 
</pre>
 
 
 
The build process takes a long time to complete. A lot of messages will be printed to the screen. These messages can be ignored, unless the build ends with an error. If the build completes successfully, the new kernel packages will be located in the <code>~/rpmbuild/RPMS</code> directory.
 
 
 
{{Admon/warning | TO DO | add a troubleshooting section}}
 
 
 
==== Following Generic Textbooks ====
 
 
 
Many of the tutorials, examples, and textbooks about Linux kernel development assume the kernel sources are installed under the <code>/usr/src/linux/</code> directory. If you make a symbolic link, as shown below, you should be able to use those learning materials with the Fedora packages. Install the appropriate kernel sources, as shown earlier, and then run the following command:
 
 
 
<pre>su -c 'ln -s /usr/src/kernels/<version>.<release>-<arch> /usr/src/linux'
 
</pre>
 
 
 
Enter the <code>root</code> password when prompted.
 
 
 
=== Install the New Kernel ===
 
This step actually installs the new kernel into the running system.
 
 
 
To install the new kernel, use the <code>rpm -ivh</code> command, '''not''' the <code>-U</code> or <code>--upgrade</code> options:
 
 
 
<pre>su -c "rpm -ivh $HOME/rpmbuild/RPMS/<arch>/kernel-<version>.<arch>.rpm"
 
</pre>
 
 
 
This command will install your kernel in /boot, create a new initramfs to bootstrap your kernel, and automatically add your new kernel to your grub bootloader "menu.lst".  At this point, you can reboot to give control to your new kernel.
 
  
 
== Building Only Kernel Modules (Out Of Tree Modules) ==
 
== Building Only Kernel Modules (Out Of Tree Modules) ==
Line 279: Line 116:
  
 
You can build against any kernel version, as long as you have <code>kernel</code> and <code>kernel-devel</code> packages installed for that version.  The rest of this section assumes we're building for the running kernel; if not, replace <code>`uname -r`</code> with the desired version number.
 
You can build against any kernel version, as long as you have <code>kernel</code> and <code>kernel-devel</code> packages installed for that version.  The rest of this section assumes we're building for the running kernel; if not, replace <code>`uname -r`</code> with the desired version number.
 
{{Admon/note | The kernel-doc package contains official Kbuild documentation - see files under Documentation/kbuild, in particular the modules.txt file. }}
 
  
 
As a simple example, to build the <code>foo.ko</code> module from <code>foo.c</code>, create the following <code>Makefile</code> in the directory containing the <code>foo.c</code> file:
 
As a simple example, to build the <code>foo.ko</code> module from <code>foo.c</code>, create the following <code>Makefile</code> in the directory containing the <code>foo.c</code> file:
Line 318: Line 153:
 
Clone a kernel tree from kernel.org  
 
Clone a kernel tree from kernel.org  
  
{{Admon/note | Tips for kernel.org sources|The README file in the top-level directory provides very good build instructions, including how to direct the build to a particular directory, the necessary make targets, and the order in which to issue them. Ssave time by reviewing the Documentation directory and its sub-directories containing  informative ".txt" files. View the top level Makefile for kernel version information.}}
+
{{Admon/note | Tips for developing with kernel.org sources|The README file in the top-level directory provides very good build instructions, including how to direct the build to a particular directory, the necessary make targets, and the order in which to issue them. Save time by reviewing the Documentation directory and its sub-directories containing  informative ".txt" files. View the top level Makefile for kernel version information.}}
  
 
<code> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git </code>
 
<code> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git </code>
Line 324: Line 159:
  
 
<code> $ cd linux </code>
 
<code> $ cd linux </code>
 +
 +
If you need the stable kernel releases, add the stable remote:
 +
 +
<code> $ git remote add -f stable git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git </code>
  
 
Double check what baseline is being used and check out a new one if necessary:
 
Double check what baseline is being used and check out a new one if necessary:
  
<code> $ git checkout v3.19 </code>
+
<code> $ git checkout v4.5.2</code>
  
 
=== Applying patches ===
 
=== Applying patches ===
Line 348: Line 187:
  
 
=== Configuring the kernel ===
 
=== Configuring the kernel ===
{{admon/note| As a potential option to the instructions below, consider using the make targets "mrproper" and "menuconfig" as specified in the top-level README file.  The "menuconfig" target is an alternative to "oldconfig" and pops up a GUI that allows you to set virtually all build options. Accepting the defaults is generally fine, although you can use the "General Setup->Local version" option to append a label to your build instead of tweaking "EXTRAVERSION" in the .config file.}}
+
{{admon/note| Potential options to the instructions below|Consider using the make targets "mrproper" and "menuconfig" as specified in the top-level README file.  The "menuconfig" target is an alternative to "oldconfig" and pops up a menu that allows you to easily set virtually all build options. Accepting the defaults is generally fine, although you can use the "General Setup->Local version" option to append a label to your build instead of tweaking "EXTRAVERSION" in the .config file.}}
  
 
Chances are that the kernel you are running is older than the one you are about to configure.  This means there will be new options.
 
Chances are that the kernel you are running is older than the one you are about to configure.  This means there will be new options.
Line 372: Line 211:
  
 
<code> # make modules_install </code>
 
<code> # make modules_install </code>
 +
 
<code> # make install </code>
 
<code> # make install </code>
  

Latest revision as of 14:49, 11 May 2020

This document provides instructions for advanced users who want to rebuild the kernel from some source. Note, however, that when building or running any such kernel, one should NOT expect support from the Fedora kernel team; you're pretty much on your own here if something doesn't work as you'd hoped or expected. But hey, you're an advanced user, so you can handle it, right? Anyway, advanced users build custom kernels for a variety of reasons:

  • To apply patches for testing that they either generated or obtained from another source
  • To reconfigure the existing kernel
  • To learn more about the kernel and kernel development


Dependencies for building kernels

Not all of these will apply to all methods but this provides a good dependency list of items to install

# sudo dnf install fedpkg fedora-packager rpmdevtools ncurses-devel pesign grubby

Give the following command from the top directory of the kernel source tree once you have checked it out

# sudo dnf builddep kernel.spec

if you plan to run 'make xconfig'

# sudo dnf install qt3-devel libXi-devel gcc-c++

Also make sure you add the user doing the build to /etc/pesign/users and run the authorize user script:

# sudo /usr/libexec/pesign/pesign-authorize

It should be noted that pesign pesign-rh-test-certs gets pulled in automatically for some, but not for everyone, it depends on how you installed pesign. It is best to make sure that you have it installed.

Note.png
pesign
Also note that pesign is applicable only for UEFI platforms (x86, arm, aarch64), it's not used on eg. ppc64le or s390x.
Note.png
dnf versus yum
As of Fedora 22[1] dnf has replaced yum as the default package manager. In the event you are building a kernel for an older system you will either have to install dnf or substitute yum for dnf and/or yumdownloader from the yum-utils package.

Building a Kernel from the Fedora source tree

Make sure you have installed all dependencies

$ fedpkg clone kernel

you will likely need to checkout the source anonymously unless you have an Fedora developer account

$ fedpkg clone -a kernel

As of the time of this wiki writing, the kernel is managed using git. Each fedora release is a separate branch. rawhide tracks master. To get the tree for a particular release, you can use git checkout from the top of your newly created source tree.

e.g. for fedora 23,

$ git checkout origin/f23

You can now make whatever changes / customizations you need before generating the rpms and installing them. You may want to consider uncommenting

# define buildid .local

to avoid conflicts, e.g.

%define buildid .local


When finished, generate the appropriate rpms with

$ fedpkg local

The rpms will be generated in a subdirectory $ARCH which can then be installed:

$ dnf install --nogpgcheck ./x86_64/kernel-$version.rpm

Building a non-debugging kernel

Branched kernels are built with debugging enabled by default in the early stages of the release to assist developers. To make a kernel with debugging information disabled, you can follow the above instructions to check out and do:

$ make release

$ fedpkg local

Enabling config options

If there are configuration options that need to be adjusted for your build, you can add changes in the kernel-local file. These changes will get picked up when you build.

Updating

  • $ cd kernel
  • kernel $ git status
    • your tree will be dirty in the configs and kernel.spec
  • kernel $ git stash
    • puts aside your changes so your tree will be clean
  • kernel $ git pull origin
    • update to the latest tree from fedpkg git

Now you can run whatever other commands you want (e.g. make release)

Building a kernel from the exploded git trees

Fedora keeps a git tree containing Fedora patches applied on top of the vanilla sources.

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/fedora.git

$ git checkout -b my_branch kernel-4.7.4-200.fc24

You can now build the kernel following regular kernel instructions. This tree is useful for generating patches that can be applied to the kernel.spec.

Building a Kernel from the source RPM

Instructions for this are on a separate page. In general, you should use one of the other methods for building the kernel which are much easier.

Building Only Kernel Modules (Out Of Tree Modules)

Warning.png
This section needs to be updated and fleshed out

This section is for users who are only interested in working on a kernel module, and who do not wish to build an entire custom kernel. It is not necessary to download and rebuild the entire kernel in order to build a module. To build a module for the currently running kernel, only the matching kernel-devel package is required. Run the following command to install the kernel-devel package using dnf.

su -c 'dnf install kernel-devel'
Note.png
You may need to install 'kernel-PAE-devel' if you are using the PAE kernel

You can build against any kernel version, as long as you have kernel and kernel-devel packages installed for that version. The rest of this section assumes we're building for the running kernel; if not, replace uname -r with the desired version number.

As a simple example, to build the foo.ko module from foo.c, create the following Makefile in the directory containing the foo.c file:

obj-m := foo.o

KDIR  := /lib/modules/$(shell uname -r)/build
PWD   := $(shell pwd)

default:
[TAB]$(MAKE) -C $(KDIR) M=$(PWD) modules

[TAB] Denotes a tab character which must come first for makefile lines containing commands.

Then, issue the make command to build the foo.ko module.

The above is a helpful local Makefile wrapper invoking kbuild; in general you can simply do things like

# make -C /lib/modules/`uname -r`/build M=`pwd` modules
# make -C /lib/modules/`uname -r`/build M=`pwd` clean
# make -C /lib/modules/`uname -r`/build M=`pwd` modules_install

etc to build those targets.

Building Vanilla upstream kernel

Sometimes a Fedora developer may ask you to try building and installing an upstream kernel (possibly with a patch added) for testing. If there are multiple iterations, it may be quicker for you to do this than for the developer to turn around several RPMs.

Existing Fedora Vanilla packages

There is an effort underway for packaging vanilla kernels. See if this meets your needs first

Getting the sources

Clone a kernel tree from kernel.org

Note.png
Tips for developing with kernel.org sources
The README file in the top-level directory provides very good build instructions, including how to direct the build to a particular directory, the necessary make targets, and the order in which to issue them. Save time by reviewing the Documentation directory and its sub-directories containing informative ".txt" files. View the top level Makefile for kernel version information.

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git This will clone the entire upstream tree. This may take a while depending on your connection speed. (While the tree is syncing, why not take the time to update some steps on this wiki that are inevitably out of date?)

$ cd linux

If you need the stable kernel releases, add the stable remote:

$ git remote add -f stable git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git

Double check what baseline is being used and check out a new one if necessary:

$ git checkout v4.5.2

Applying patches

The patch method

If you were asked to apply any patches by the developer, this is the stage at which we would do so. These would typically be applied using a command something like..

$ cat ~/testpatch.diff | patch -p1

If you have to try multiple different patches individually, you can unapply the previous one after testing by adding -R on the end of the above command.

The git method

Most developers these days generate patches using git and you can use git to help apply patches. You can do:

$ git am -3 <patch file>

This will create a git commit of a single patch in your tree.

Configuring the kernel

Note.png
Potential options to the instructions below
Consider using the make targets "mrproper" and "menuconfig" as specified in the top-level README file. The "menuconfig" target is an alternative to "oldconfig" and pops up a menu that allows you to easily set virtually all build options. Accepting the defaults is generally fine, although you can use the "General Setup->Local version" option to append a label to your build instead of tweaking "EXTRAVERSION" in the .config file.

Chances are that the kernel you are running is older than the one you are about to configure. This means there will be new options. There are several possibilities here.

  • If the developer has pointed you at a specific config file to use, save it in the linux directory with the filename .config
  • You can take your existing .config file by using the command cp /boot/config-uname -r* .config

When you run the next step, you'll be asked (potentially lots of) questions about all the new options. Just hitting return 'should' always pick the safe decision for each option. However, it's worth taking care and reading each option, as this isn't always the case, and they may introduce new features your distro isn't capable of running, which may result in a non-booting system.

  • FIXME how to grab a rawhide config

With the config in place, you are now ready to move on to the next step.

Building the kernel

$EDITOR Makefile Change the EXTRAVERSION line to add something on the end. For example, if it reads "EXTRAVERSION = -rc5" change it to "EXTRAVERSION = -rc5-dave" (what you choose is only relevant for the final part of this procedure)

$ make oldconfig

$ make bzImage

$ make modules

(become root)

# make modules_install

# make install

You have now built and installed a kernel. It will show up in the grub menu next time you reboot.

Rebuilding

If you have been asked to try several different things, the procedure once you have already built the tree once is mostly the same. A make clean is recommended between builds. This will leave the .config in place, so you can skip that step above and proceed straight to the make bzImage part of the steps above. Because we installed ccache in the first step, subsequent builds may go a lot faster as the compiler hits files that haven't changed since the last time it built them.

Cleaning up

Once you have tested the kernel, and you've booted back to one of your kernels installed from an RPM, you can clean up the files that the above procedure installed by becoming root, and calling these commands. (Be sure to get the kernel version correct!) Remember above, we changed EXTRAVERSION to add a 'tag' to the kernel ? All the files it installed will have this as part of the filename. So you should be able to use wildcards to delete them safely using commands similar to those below. (Just replace 'dave' with whatever tag you chose)

rm -f /boot/config-2.6.*dave* /boot/initrd-2.6.*dave* /boot/vmlinuz-*dave* /boot/System.map-*dave*
rm -rf /lib/modules/2.6*dave*

Finally, you will need to remove the kernel as an option to your bootloader. This will change from architecture to architecture. For x86, (as root), edit /boot/grub2/grub.cfg or /boot/efi/EFI/fedora/grub.cfg if you have EFI enabled and delete the four lines relating to your kernel (They should be easy to spot, they'll be the ones with your tag). They'll look something like this..

title Fedora Core (2.6.22-rc3-dave)
root (hd0,0)
kernel /vmlinuz-2.6.22-rc3-dave ro root=/dev/md0
initrd /initrd-2.6.22-rc3-dave.img