This method will make a .deb of your kernel source, and, if you have non-standard modules, make a synchronized dependent .deb of those too. It’s a better way to manage kernel images; /boot will hold the kernel, the System.map, and a log of the active config file for the build. 

Note that you don’t have to compile your kernel the “Debian/Ubuntu way”; but we find that using the packaging system to manage your kernel is actually safer and easier. In fact, you can get your kernel sources right from Linus instead of linux-source , yet still use the kernel-package compilation method. 

Note that you’ll find complete documentation on using kernel-package under /usr/share/doc/kernel-package . This section just contains a brief tutorial. 

Hereafter, we’ll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory$^{5}$. We’ll also assume that your kernel version is 5.4. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using tar xf /usr/src/linux-source-5.4.tar.xz and change to the directory linux-source-5.4 that will have been created. 

Now, you can configure your kernel. Run make xconfig if X11 is installed, configured and being run; run make menuconfig otherwise (you’ll need libncurses5-dev installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select “Kernel module loader” in “Loadable module support” (it is not selected by default). If not included, your Ubuntu installation will experience problems. 

Clean the source tree and reset the kernel-package parameters. To do that, do make-kpkg clean . 

Now, compile the kernel: fakeroot make-kpkg --initrd --revision=1.0.custom kernel_image . The version number of “1.0” can be changed at will; this is just a version number that you will use to track your kernel builds. Likewise, you can put any word you like in place of “custom” (e.g., a host name). Kernel compilation may take quite a while, depending on the power of your machine. 

Once the compilation is complete, you can install your custom kernel like any package. As root, do dpkg -i ../linux-image-5.4- subarchitecture _1.0.custom_arm64.deb . 

The subarchitecture part is an optional sub-architecture, depending on what kernel options you set. dpkg -i will install the kernel, along with some other nice supporting files. For instance, the System.map will be properly installed (helpful for debugging kernel problems), and /boot/config-5.4 will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you’ll need to install that package as well. 

It is time to reboot the system: read carefully any warning that the above step may have produced, then shutdown -r now . 

For more information on Debian/Ubuntu kernels and kernel compilation, see the Debian Linux Kernel Handbook (http://kernel-handbook.alioth.debian.org/). For more information on kernel-package , read the fine documentation in /usr/share/doc/kernel-package . 

