Lines Matching full:kernels
13 The text aims at people running kernels from mainstream Linux distributions on
16 who are already familiar with building their own kernels: they help avoid
51 * **Preparations**: set up everything to build your own kernels::
55 # * Ensure Secure Boot permits booting self-compiled Linux kernels.
110 make -s kernelrelease | tee -a ~/kernels-built
114 tail -n 1 ~/kernels-built
188 remove some kernels you built earlier. You most likely want to keep those
190 likely no longer need kernels tested during the actual bisection
204 free to remove all kernels built during the actual bisection (Segment 3 c);
205 the kernels you built earlier and later you might want to keep around for
225 This guide describes how to set up your own Linux kernels for investigating bugs
239 :ref:`Preparations: set up everything to build your own kernels <introprep_bissbs>`.
243 :ref:`Segment 2: check if the kernels you build work fine <introworkingcheck_bissbs>`.
274 Preparations: set up everything to build your own kernels
281 :ref:`Build kernels on a different machine <buildhost_bis>` below.
466 something to keep in mind: if something is misbehaving with the kernels built
477 * Ensure all the kernels you will build are clearly identifiable using a special
588 much your kernels actually require will be determined later during this guide.
591 parallel to the your Linux distribution's kernels::
607 down: if you will build more kernels as described in segment 2 and 3, you will
629 make -s kernelrelease | tee -a ~/kernels-built
638 tail -n 1 ~/kernels-built
682 make -s kernelrelease | tee -a ~/kernels-built
688 tail -n 1 ~/kernels-built
708 Segment 2: check if the kernels you build work fine
736 make -s kernelrelease | tee -a ~/kernels-built
742 tail -n 1 ~/kernels-built
756 to begin the bisection. This will make you build quite a few kernels -- usually
787 make -s kernelrelease | tee -a ~/kernels-built
812 tail -n 1 ~/kernels-built
910 make -s kernelrelease | tee -a ~/kernels-built
924 the kernels you installed: the boot menu otherwise will become confusing or
929 * To remove one of the kernels you installed, look up its 'kernelrelease'
930 identifier. This guide stores them in '~/kernels-built', but the following
935 You in most situations want to remove the oldest kernels built during the
967 top of the latest codebase? Then you want to keep those two kernels around
972 reasons? Then you want to keep as many kernels as possible around for a few
975 * In other cases it likely is a good idea to keep the following kernels around
1051 make -s kernelrelease | tee -a ~/kernels-built
1083 Preparations for building your own kernels
1120 kernels that utilize such modules. That's because such kernels are not
1136 they reject booting self-compiled kernels by default.
1138 You ideally deal with this by making your platform trust your self-built kernels
1343 a range (say 6.1..6.2), as they are internally based on earlier kernels
1414 In case you want to build kernels for another machine, locate its kernel build
1430 can easily happen that your self-built kernels will lack modules for tasks you
1452 But if you plan to build and use self-built kernels regularly, you might want to
1460 That parameter also allows you to build trimmed kernels for another machine in
1472 Tag the kernels about to be build argument
1475 *Ensure all the kernels you will build are clearly identifiable using a
1478 This allows you to differentiate your distribution's kernels from those created
1481 not lose track of you kernels, as their version numbers will look slightly
1780 The kernels built during a bisection consume quite a bit of space in /boot/ and
1782 fill up volumes during a bisection -- and due to that even kernels which used to
1803 ignore or react scantly to reports from tainted kernels -- unless of course the
1807 Documentation/admin-guide/tainted-kernels.rst; doing so is also in your own
1858 *Check if the kernels you build work fine.*
1866 and you might be building and testing ten or more kernels for nothing before
1871 Many readers of this guide normally run kernels that are patched, use add-on
1872 modules, or both. Those kernels thus are not considered 'vanilla' -- therefore
1877 stable/longterm kernels of different series (e.g. 6.0.13..6.1.5): it will
1891 In case the feature that broke with newer kernels does not work with your first
1995 instead of testing ten or more kernels you might only have to build a few to
2028 of the kernels you installed.* [:ref:`... <introclosure_bissbs>`]
2039 *To remove one of the kernels you installed, look up its 'kernelrelease'
2042 The kernels you install during this process are easy to remove later, as its
2045 thus bypass your distribution's packaging system): all parts of your kernels are
2050 identifier; hence, to remove all modules for one of the kernels you built,
2072 for kernels manually: you might accidentally remove files of a 6.0.13 kernel
2086 When you are really short of storage space removing the kernels as described in
2126 Build kernels on a different machine
2129 To compile kernels on another system, slightly alter the step-by-step guide's
2133 the kernels later.