€•J      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ&/translations/zh_CN/admin-guide/README”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/zh_TW/admin-guide/README”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/it_IT/admin-guide/README”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/ja_JP/admin-guide/README”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/ko_KR/admin-guide/README”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/pt_BR/admin-guide/README”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/sp_SP/admin-guide/README”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒtarget”“”)”}”(hŒ.. _readme:”h]”h}”(h]”h ]”h"]”h$]”h&]”Œrefid”Œreadme”uh1hµh´Khhh²hh³Œ@/var/lib/git/docbuild/linux/Documentation/admin-guide/README.rst”ubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ-Linux kernel release 6.x <http://kernel.org/>”h]”(hŒLinux kernel release 6.x <”…””}”(hhËh²hh³Nh´NubhŒ	reference”“”)”}”(hŒhttp://kernel.org/”h]”hŒhttp://kernel.org/”…””}”(hhÕh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”h×uh1hÓhhËubhŒ>”…””}”(hhËh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhhÆh²hh³hÃh´KubhŒ	paragraph”“”)”}”(hŒºThese are the release notes for Linux version 6.  Read them carefully,
as they tell you what this is all about, explain how to install the
kernel, and what to do if something goes wrong.”h]”hŒºThese are the release notes for Linux version 6.  Read them carefully,
as they tell you what this is all about, explain how to install the
kernel, and what to do if something goes wrong.”…””}”(hhðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´KhhÆh²hubhÅ)”}”(hhh]”(hÊ)”}”(hŒWhat is Linux?”h]”hŒWhat is Linux?”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhhþh²hh³hÃh´KubhŒblock_quote”“”)”}”(hXS  Linux is a clone of the operating system Unix, written from scratch by
Linus Torvalds with assistance from a loosely-knit team of hackers across
the Net. It aims towards POSIX and Single UNIX Specification compliance.

It has all the features you would expect in a modern fully-fledged Unix,
including true multitasking, virtual memory, shared libraries, demand
loading, shared copy-on-write executables, proper memory management,
and multistack networking including IPv4 and IPv6.

It is distributed under the GNU General Public License v2 - see the
accompanying COPYING file for more details.
”h]”(hï)”}”(hŒÙLinux is a clone of the operating system Unix, written from scratch by
Linus Torvalds with assistance from a loosely-knit team of hackers across
the Net. It aims towards POSIX and Single UNIX Specification compliance.”h]”hŒÙLinux is a clone of the operating system Unix, written from scratch by
Linus Torvalds with assistance from a loosely-knit team of hackers across
the Net. It aims towards POSIX and Single UNIX Specification compliance.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Khj  ubhï)”}”(hX  It has all the features you would expect in a modern fully-fledged Unix,
including true multitasking, virtual memory, shared libraries, demand
loading, shared copy-on-write executables, proper memory management,
and multistack networking including IPv4 and IPv6.”h]”hX  It has all the features you would expect in a modern fully-fledged Unix,
including true multitasking, virtual memory, shared libraries, demand
loading, shared copy-on-write executables, proper memory management,
and multistack networking including IPv4 and IPv6.”…””}”(hj#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Khj  ubhï)”}”(hŒoIt is distributed under the GNU General Public License v2 - see the
accompanying COPYING file for more details.”h]”hŒoIt is distributed under the GNU General Public License v2 - see the
accompanying COPYING file for more details.”…””}”(hj1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Khj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÃh´Khhþh²hubeh}”(h]”Œwhat-is-linux”ah ]”h"]”Œwhat is linux?”ah$]”h&]”uh1hÄhhÆh²hh³hÃh´KubhÅ)”}”(hhh]”(hÊ)”}”(hŒOn what hardware does it run?”h]”hŒOn what hardware does it run?”…””}”(hjP  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjM  h²hh³hÃh´Kubj  )”}”(hX   Although originally developed first for 32-bit x86-based PCs (386 or higher),
today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and
UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell,
IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64 Xtensa, and
ARC architectures.

Linux is easily portable to most general-purpose 32- or 64-bit architectures
as long as they have a paged memory management unit (PMMU) and a port of the
GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has
also been ported to a number of architectures without a PMMU, although
functionality is then obviously somewhat limited.
Linux has also been ported to itself. You can now run the kernel as a
userspace application - this is called UserMode Linux (UML).
”h]”(hï)”}”(hX=  Although originally developed first for 32-bit x86-based PCs (386 or higher),
today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and
UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell,
IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64 Xtensa, and
ARC architectures.”h]”hX=  Although originally developed first for 32-bit x86-based PCs (386 or higher),
today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and
UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell,
IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64 Xtensa, and
ARC architectures.”…””}”(hjb  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Khj^  ubhï)”}”(hXà  Linux is easily portable to most general-purpose 32- or 64-bit architectures
as long as they have a paged memory management unit (PMMU) and a port of the
GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has
also been ported to a number of architectures without a PMMU, although
functionality is then obviously somewhat limited.
Linux has also been ported to itself. You can now run the kernel as a
userspace application - this is called UserMode Linux (UML).”h]”hXà  Linux is easily portable to most general-purpose 32- or 64-bit architectures
as long as they have a paged memory management unit (PMMU) and a port of the
GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has
also been ported to a number of architectures without a PMMU, although
functionality is then obviously somewhat limited.
Linux has also been ported to itself. You can now run the kernel as a
userspace application - this is called UserMode Linux (UML).”…””}”(hjp  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´K"hj^  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÃh´KhjM  h²hubeh}”(h]”Œon-what-hardware-does-it-run”ah ]”h"]”Œon what hardware does it run?”ah$]”h&]”uh1hÄhhÆh²hh³hÃh´KubhÅ)”}”(hhh]”(hÊ)”}”(hŒDocumentation”h]”hŒDocumentation”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjŒ  h²hh³hÃh´K+ubj  )”}”(hXá  - There is a lot of documentation available both in electronic form on
  the Internet and in books, both Linux-specific and pertaining to
  general UNIX questions.  I'd recommend looking into the documentation
  subdirectories on any Linux FTP site for the LDP (Linux Documentation
  Project) books.  This README is not meant to be documentation on the
  system: there are much better sources available.

- There are various README files in the Documentation/ subdirectory:
  these typically contain kernel-specific installation notes for some
  drivers for example. Please read the
  :ref:`Documentation/process/changes.rst <changes>` file, as it
  contains information about the problems which may result from upgrading
  your kernel.
”h]”hŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hXˆ  There is a lot of documentation available both in electronic form on
the Internet and in books, both Linux-specific and pertaining to
general UNIX questions.  I'd recommend looking into the documentation
subdirectories on any Linux FTP site for the LDP (Linux Documentation
Project) books.  This README is not meant to be documentation on the
system: there are much better sources available.
”h]”hï)”}”(hX‡  There is a lot of documentation available both in electronic form on
the Internet and in books, both Linux-specific and pertaining to
general UNIX questions.  I'd recommend looking into the documentation
subdirectories on any Linux FTP site for the LDP (Linux Documentation
Project) books.  This README is not meant to be documentation on the
system: there are much better sources available.”h]”hX‰  There is a lot of documentation available both in electronic form on
the Internet and in books, both Linux-specific and pertaining to
general UNIX questions.  Iâ€™d recommend looking into the documentation
subdirectories on any Linux FTP site for the LDP (Linux Documentation
Project) books.  This README is not meant to be documentation on the
system: there are much better sources available.”…””}”(hj¬  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´K-hj¨  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj£  ubj§  )”}”(hX@  There are various README files in the Documentation/ subdirectory:
these typically contain kernel-specific installation notes for some
drivers for example. Please read the
:ref:`Documentation/process/changes.rst <changes>` file, as it
contains information about the problems which may result from upgrading
your kernel.
”h]”hï)”}”(hX?  There are various README files in the Documentation/ subdirectory:
these typically contain kernel-specific installation notes for some
drivers for example. Please read the
:ref:`Documentation/process/changes.rst <changes>` file, as it
contains information about the problems which may result from upgrading
your kernel.”h]”(hŒ¬There are various README files in the Documentation/ subdirectory:
these typically contain kernel-specific installation notes for some
drivers for example. Please read the
”…””}”(hjÄ  h²hh³Nh´Nubh)”}”(hŒ2:ref:`Documentation/process/changes.rst <changes>`”h]”hŒinline”“”)”}”(hjÎ  h]”hŒ!Documentation/process/changes.rst”…””}”(hjÒ  h²hh³Nh´Nubah}”(h]”h ]”(Œxref”Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jÐ  hjÌ  ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œadmin-guide/README”Œ	refdomain”jÝ  Œreftype”Œref”Œrefexplicit”ˆŒrefwarn”ˆŒ	reftarget”Œchanges”uh1hh³hÃh´K4hjÄ  ubhŒa file, as it
contains information about the problems which may result from upgrading
your kernel.”…””}”(hjÄ  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´K4hjÀ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj£  ubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1j¡  h³hÃh´K-hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÃh´K-hjŒ  h²hubeh}”(h]”Œdocumentation”ah ]”h"]”Œdocumentation”ah$]”h&]”uh1hÄhhÆh²hh³hÃh´K+ubhÅ)”}”(hhh]”(hÊ)”}”(hŒInstalling the kernel source”h]”hŒInstalling the kernel source”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhj  h²hh³hÃh´K<ubj  )”}”(hXð  - If you install the full sources, put the kernel tarball in a
  directory where you have permissions (e.g. your home directory) and
  unpack it::

    xz -cd linux-6.x.tar.xz | tar xvf -

  Replace "X" with the version number of the latest kernel.

  Do NOT use the /usr/src/linux area! This area has a (usually
  incomplete) set of kernel headers that are used by the library header
  files.  They should match the library, and not get messed up by
  whatever the kernel-du-jour happens to be.

- You can also upgrade between 6.x releases by patching.  Patches are
  distributed in the xz format.  To install by patching, get all the
  newer patch files, enter the top level directory of the kernel source
  (linux-6.x) and execute::

    xz -cd ../patch-6.x.xz | patch -p1

  Replace "x" for all versions bigger than the version "x" of your current
  source tree, **in_order**, and you should be ok.  You may want to remove
  the backup files (some-file-name~ or some-file-name.orig), and make sure
  that there are no failed patches (some-file-name# or some-file-name.rej).
  If there are, either you or I have made a mistake.

  Unlike patches for the 6.x kernels, patches for the 6.x.y kernels
  (also known as the -stable kernels) are not incremental but instead apply
  directly to the base 6.x kernel.  For example, if your base kernel is 6.0
  and you want to apply the 6.0.3 patch, you must not first apply the 6.0.1
  and 6.0.2 patches. Similarly, if you are running kernel version 6.0.2 and
  want to jump to 6.0.3, you must first reverse the 6.0.2 patch (that is,
  patch -R) **before** applying the 6.0.3 patch. You can read more on this in
  :ref:`Documentation/process/applying-patches.rst <applying_patches>`.

  Alternatively, the script patch-kernel can be used to automate this
  process.  It determines the current kernel version and applies any
  patches found::

    linux/scripts/patch-kernel linux

  The first argument in the command above is the location of the
  kernel source.  Patches are applied from the current directory, but
  an alternative directory can be specified as the second argument.

- Make sure you have no stale .o files and dependencies lying around::

    cd linux
    make mrproper

  You should now have the sources correctly installed.
”h]”j¢  )”}”(hhh]”(j§  )”}”(hXÞ  If you install the full sources, put the kernel tarball in a
directory where you have permissions (e.g. your home directory) and
unpack it::

  xz -cd linux-6.x.tar.xz | tar xvf -

Replace "X" with the version number of the latest kernel.

Do NOT use the /usr/src/linux area! This area has a (usually
incomplete) set of kernel headers that are used by the library header
files.  They should match the library, and not get messed up by
whatever the kernel-du-jour happens to be.
”h]”(hï)”}”(hŒŒIf you install the full sources, put the kernel tarball in a
directory where you have permissions (e.g. your home directory) and
unpack it::”h]”hŒ‹If you install the full sources, put the kernel tarball in a
directory where you have permissions (e.g. your home directory) and
unpack it:”…””}”(hj3  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´K>hj/  ubhŒliteral_block”“”)”}”(hŒ#xz -cd linux-6.x.tar.xz | tar xvf -”h]”hŒ#xz -cd linux-6.x.tar.xz | tar xvf -”…””}”hjC  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1jA  h³hÃh´KBhj/  ubhï)”}”(hŒ9Replace "X" with the version number of the latest kernel.”h]”hŒ=Replace â€œXâ€ with the version number of the latest kernel.”…””}”(hjS  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´KDhj/  ubhï)”}”(hŒíDo NOT use the /usr/src/linux area! This area has a (usually
incomplete) set of kernel headers that are used by the library header
files.  They should match the library, and not get messed up by
whatever the kernel-du-jour happens to be.”h]”hŒíDo NOT use the /usr/src/linux area! This area has a (usually
incomplete) set of kernel headers that are used by the library header
files.  They should match the library, and not get messed up by
whatever the kernel-du-jour happens to be.”…””}”(hja  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´KFhj/  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj,  ubj§  )”}”(hX-  You can also upgrade between 6.x releases by patching.  Patches are
distributed in the xz format.  To install by patching, get all the
newer patch files, enter the top level directory of the kernel source
(linux-6.x) and execute::

  xz -cd ../patch-6.x.xz | patch -p1

Replace "x" for all versions bigger than the version "x" of your current
source tree, **in_order**, and you should be ok.  You may want to remove
the backup files (some-file-name~ or some-file-name.orig), and make sure
that there are no failed patches (some-file-name# or some-file-name.rej).
If there are, either you or I have made a mistake.

Unlike patches for the 6.x kernels, patches for the 6.x.y kernels
(also known as the -stable kernels) are not incremental but instead apply
directly to the base 6.x kernel.  For example, if your base kernel is 6.0
and you want to apply the 6.0.3 patch, you must not first apply the 6.0.1
and 6.0.2 patches. Similarly, if you are running kernel version 6.0.2 and
want to jump to 6.0.3, you must first reverse the 6.0.2 patch (that is,
patch -R) **before** applying the 6.0.3 patch. You can read more on this in
:ref:`Documentation/process/applying-patches.rst <applying_patches>`.

Alternatively, the script patch-kernel can be used to automate this
process.  It determines the current kernel version and applies any
patches found::

  linux/scripts/patch-kernel linux

The first argument in the command above is the location of the
kernel source.  Patches are applied from the current directory, but
an alternative directory can be specified as the second argument.
”h]”(hï)”}”(hŒæYou can also upgrade between 6.x releases by patching.  Patches are
distributed in the xz format.  To install by patching, get all the
newer patch files, enter the top level directory of the kernel source
(linux-6.x) and execute::”h]”hŒåYou can also upgrade between 6.x releases by patching.  Patches are
distributed in the xz format.  To install by patching, get all the
newer patch files, enter the top level directory of the kernel source
(linux-6.x) and execute:”…””}”(hjy  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´KKhju  ubjB  )”}”(hŒ"xz -cd ../patch-6.x.xz | patch -p1”h]”hŒ"xz -cd ../patch-6.x.xz | patch -p1”…””}”hj‡  sbah}”(h]”h ]”h"]”h$]”h&]”jQ  jR  uh1jA  h³hÃh´KPhju  ubhï)”}”(hXW  Replace "x" for all versions bigger than the version "x" of your current
source tree, **in_order**, and you should be ok.  You may want to remove
the backup files (some-file-name~ or some-file-name.orig), and make sure
that there are no failed patches (some-file-name# or some-file-name.rej).
If there are, either you or I have made a mistake.”h]”(hŒ^Replace â€œxâ€ for all versions bigger than the version â€œxâ€ of your current
source tree, ”…””}”(hj•  h²hh³Nh´NubhŒstrong”“”)”}”(hŒ**in_order**”h]”hŒin_order”…””}”(hjŸ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj•  ubhŒõ, and you should be ok.  You may want to remove
the backup files (some-file-name~ or some-file-name.orig), and make sure
that there are no failed patches (some-file-name# or some-file-name.rej).
If there are, either you or I have made a mistake.”…””}”(hj•  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´KRhju  ubhï)”}”(hXC  Unlike patches for the 6.x kernels, patches for the 6.x.y kernels
(also known as the -stable kernels) are not incremental but instead apply
directly to the base 6.x kernel.  For example, if your base kernel is 6.0
and you want to apply the 6.0.3 patch, you must not first apply the 6.0.1
and 6.0.2 patches. Similarly, if you are running kernel version 6.0.2 and
want to jump to 6.0.3, you must first reverse the 6.0.2 patch (that is,
patch -R) **before** applying the 6.0.3 patch. You can read more on this in
:ref:`Documentation/process/applying-patches.rst <applying_patches>`.”h]”(hX¼  Unlike patches for the 6.x kernels, patches for the 6.x.y kernels
(also known as the -stable kernels) are not incremental but instead apply
directly to the base 6.x kernel.  For example, if your base kernel is 6.0
and you want to apply the 6.0.3 patch, you must not first apply the 6.0.1
and 6.0.2 patches. Similarly, if you are running kernel version 6.0.2 and
want to jump to 6.0.3, you must first reverse the 6.0.2 patch (that is,
patch -R) ”…””}”(hj·  h²hh³Nh´Nubjž  )”}”(hŒ
**before**”h]”hŒbefore”…””}”(hj¿  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj·  ubhŒ8 applying the 6.0.3 patch. You can read more on this in
”…””}”(hj·  h²hh³Nh´Nubh)”}”(hŒD:ref:`Documentation/process/applying-patches.rst <applying_patches>`”h]”jÑ  )”}”(hjÓ  h]”hŒ*Documentation/process/applying-patches.rst”…””}”(hjÕ  h²hh³Nh´Nubah}”(h]”h ]”(jÜ  Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jÐ  hjÑ  ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”jé  Œ	refdomain”jß  Œreftype”Œref”Œrefexplicit”ˆŒrefwarn”ˆjï  Œapplying_patches”uh1hh³hÃh´KXhj·  ubhŒ.”…””}”(hj·  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´KXhju  ubhï)”}”(hŒ–Alternatively, the script patch-kernel can be used to automate this
process.  It determines the current kernel version and applies any
patches found::”h]”hŒ•Alternatively, the script patch-kernel can be used to automate this
process.  It determines the current kernel version and applies any
patches found:”…””}”(hjû  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Kahju  ubjB  )”}”(hŒ linux/scripts/patch-kernel linux”h]”hŒ linux/scripts/patch-kernel linux”…””}”hj	  sbah}”(h]”h ]”h"]”h$]”h&]”jQ  jR  uh1jA  h³hÃh´Kehju  ubhï)”}”(hŒÄThe first argument in the command above is the location of the
kernel source.  Patches are applied from the current directory, but
an alternative directory can be specified as the second argument.”h]”hŒÄThe first argument in the command above is the location of the
kernel source.  Patches are applied from the current directory, but
an alternative directory can be specified as the second argument.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Kghju  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj,  ubj§  )”}”(hŒ—Make sure you have no stale .o files and dependencies lying around::

  cd linux
  make mrproper

You should now have the sources correctly installed.
”h]”(hï)”}”(hŒDMake sure you have no stale .o files and dependencies lying around::”h]”hŒCMake sure you have no stale .o files and dependencies lying around:”…””}”(hj/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Kkhj+  ubjB  )”}”(hŒcd linux
make mrproper”h]”hŒcd linux
make mrproper”…””}”hj=  sbah}”(h]”h ]”h"]”h$]”h&]”jQ  jR  uh1jA  h³hÃh´Kmhj+  ubhï)”}”(hŒ4You should now have the sources correctly installed.”h]”hŒ4You should now have the sources correctly installed.”…””}”(hjK  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Kphj+  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj,  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1j¡  h³hÃh´K>hj(  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÃh´K>hj  h²hubeh}”(h]”Œinstalling-the-kernel-source”ah ]”h"]”Œinstalling the kernel source”ah$]”h&]”uh1hÄhhÆh²hh³hÃh´K<ubhÅ)”}”(hhh]”(hÊ)”}”(hŒSoftware requirements”h]”hŒSoftware requirements”…””}”(hjv  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjs  h²hh³hÃh´Ksubj  )”}”(hXÙ  Compiling and running the 6.x kernels requires up-to-date
versions of various software packages.  Consult
:ref:`Documentation/process/changes.rst <changes>` for the minimum version numbers
required and how to get updates for these packages.  Beware that using
excessively old versions of these packages can cause indirect
errors that are very difficult to track down, so don't assume that
you can just update packages when obvious problems arise during
build or operation.
”h]”hï)”}”(hXØ  Compiling and running the 6.x kernels requires up-to-date
versions of various software packages.  Consult
:ref:`Documentation/process/changes.rst <changes>` for the minimum version numbers
required and how to get updates for these packages.  Beware that using
excessively old versions of these packages can cause indirect
errors that are very difficult to track down, so don't assume that
you can just update packages when obvious problems arise during
build or operation.”h]”(hŒjCompiling and running the 6.x kernels requires up-to-date
versions of various software packages.  Consult
”…””}”(hjˆ  h²hh³Nh´Nubh)”}”(hŒ2:ref:`Documentation/process/changes.rst <changes>`”h]”jÑ  )”}”(hj’  h]”hŒ!Documentation/process/changes.rst”…””}”(hj”  h²hh³Nh´Nubah}”(h]”h ]”(jÜ  Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jÐ  hj  ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”jé  Œ	refdomain”jž  Œreftype”Œref”Œrefexplicit”ˆŒrefwarn”ˆjï  Œchanges”uh1hh³hÃh´Kuhjˆ  ubhX>   for the minimum version numbers
required and how to get updates for these packages.  Beware that using
excessively old versions of these packages can cause indirect
errors that are very difficult to track down, so donâ€™t assume that
you can just update packages when obvious problems arise during
build or operation.”…””}”(hjˆ  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Kuhj„  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÃh´Kuhjs  h²hubeh}”(h]”Œsoftware-requirements”ah ]”h"]”Œsoftware requirements”ah$]”h&]”uh1hÄhhÆh²hh³hÃh´KsubhÅ)”}”(hhh]”(hÊ)”}”(hŒBuild directory for the kernel”h]”hŒBuild directory for the kernel”…””}”(hjË  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjÈ  h²hh³hÃh´Kubj  )”}”(hX  When compiling the kernel, all output files will per default be
stored together with the kernel source code.
Using the option ``make O=output/dir`` allows you to specify an alternate
place for the output files (including .config).
Example::

  kernel source code: /usr/src/linux-6.x
  build directory:    /home/name/build/kernel

To configure and build the kernel, use::

  cd /usr/src/linux-6.x
  make O=/home/name/build/kernel menuconfig
  make O=/home/name/build/kernel
  sudo make O=/home/name/build/kernel modules_install install

Please note: If the ``O=output/dir`` option is used, then it must be
used for all invocations of make.
”h]”(hï)”}”(hŒðWhen compiling the kernel, all output files will per default be
stored together with the kernel source code.
Using the option ``make O=output/dir`` allows you to specify an alternate
place for the output files (including .config).
Example::”h]”(hŒ~When compiling the kernel, all output files will per default be
stored together with the kernel source code.
Using the option ”…””}”(hjÝ  h²hh³Nh´NubhŒliteral”“”)”}”(hŒ``make O=output/dir``”h]”hŒmake O=output/dir”…””}”(hjç  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hjÝ  ubhŒ\ allows you to specify an alternate
place for the output files (including .config).
Example:”…””}”(hjÝ  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´KhjÙ  ubjB  )”}”(hŒRkernel source code: /usr/src/linux-6.x
build directory:    /home/name/build/kernel”h]”hŒRkernel source code: /usr/src/linux-6.x
build directory:    /home/name/build/kernel”…””}”hjÿ  sbah}”(h]”h ]”h"]”h$]”h&]”jQ  jR  uh1jA  h³hÃh´K‡hjÙ  ubhï)”}”(hŒ(To configure and build the kernel, use::”h]”hŒ'To configure and build the kernel, use:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´KŠhjÙ  ubjB  )”}”(hŒšcd /usr/src/linux-6.x
make O=/home/name/build/kernel menuconfig
make O=/home/name/build/kernel
sudo make O=/home/name/build/kernel modules_install install”h]”hŒšcd /usr/src/linux-6.x
make O=/home/name/build/kernel menuconfig
make O=/home/name/build/kernel
sudo make O=/home/name/build/kernel modules_install install”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”jQ  jR  uh1jA  h³hÃh´KŒhjÙ  ubhï)”}”(hŒfPlease note: If the ``O=output/dir`` option is used, then it must be
used for all invocations of make.”h]”(hŒPlease note: If the ”…””}”(hj)  h²hh³Nh´Nubjæ  )”}”(hŒ``O=output/dir``”h]”hŒO=output/dir”…””}”(hj1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hj)  ubhŒB option is used, then it must be
used for all invocations of make.”…””}”(hj)  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´K‘hjÙ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÃh´KhjÈ  h²hubeh}”(h]”Œbuild-directory-for-the-kernel”ah ]”h"]”Œbuild directory for the kernel”ah$]”h&]”uh1hÄhhÆh²hh³hÃh´KubhÅ)”}”(hhh]”(hÊ)”}”(hŒConfiguring the kernel”h]”hŒConfiguring the kernel”…””}”(hjZ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjW  h²hh³hÃh´K•ubj  )”}”(hX>    Do not skip this step even if you are only upgrading one minor
  version.  New configuration options are added in each release, and
  odd problems will turn up if the configuration files are not set up
  as expected.  If you want to carry your existing configuration to a
  new version with minimal work, use ``make oldconfig``, which will
  only ask you for the answers to new questions.

- Alternative configuration commands are::

    "make config"      Plain text interface.

    "make menuconfig"  Text based color menus, radiolists & dialogs.

    "make nconfig"     Enhanced text based color menus.

    "make xconfig"     Qt based configuration tool.

    "make gconfig"     GTK based configuration tool.

    "make oldconfig"   Default all questions based on the contents of
                       your existing ./.config file and asking about
                       new config symbols.

    "make olddefconfig"
                       Like above, but sets new symbols to their default
                       values without prompting.

    "make defconfig"   Create a ./.config file by using the default
                       symbol values from either arch/$ARCH/configs/defconfig
                       or arch/$ARCH/configs/${PLATFORM}_defconfig,
                       depending on the architecture.

    "make ${PLATFORM}_defconfig"
                       Create a ./.config file by using the default
                       symbol values from
                       arch/$ARCH/configs/${PLATFORM}_defconfig.
                       Use "make help" to get a list of all available
                       platforms of your architecture.

    "make allyesconfig"
                       Create a ./.config file by setting symbol
                       values to 'y' as much as possible.

    "make allmodconfig"
                       Create a ./.config file by setting symbol
                       values to 'm' as much as possible.

    "make allnoconfig" Create a ./.config file by setting symbol
                       values to 'n' as much as possible.

    "make randconfig"  Create a ./.config file by setting symbol
                       values to random values.

    "make localmodconfig" Create a config based on current config and
                          loaded modules (lsmod). Disables any module
                          option that is not needed for the loaded modules.

                          To create a localmodconfig for another machine,
                          store the lsmod of that machine into a file
                          and pass it in as a LSMOD parameter.

                          Also, you can preserve modules in certain folders
                          or kconfig files by specifying their paths in
                          parameter LMC_KEEP.

                  target$ lsmod > /tmp/mylsmod
                  target$ scp /tmp/mylsmod host:/tmp

                  host$ make LSMOD=/tmp/mylsmod \
                          LMC_KEEP="drivers/usb:drivers/gpu:fs" \
                          localmodconfig

                          The above also works when cross compiling.

    "make localyesconfig" Similar to localmodconfig, except it will convert
                          all module options to built in (=y) options. You can
                          also preserve modules by LMC_KEEP.

    "make kvm_guest.config"   Enable additional options for kvm guest kernel
                              support.

    "make xen.config"   Enable additional options for xen dom0 guest kernel
                        support.

    "make tinyconfig"  Configure the tiniest possible kernel.

  You can find more information on using the Linux kernel config tools
  in Documentation/kbuild/kconfig.rst.

- NOTES on ``make config``:

   - Having unnecessary drivers will make the kernel bigger, and can
     under some circumstances lead to problems: probing for a
     nonexistent controller card may confuse your other controllers.

   - A kernel with math-emulation compiled in will still use the
     coprocessor if one is present: the math emulation will just
     never get used in that case.  The kernel will be slightly larger,
     but will work on different machines regardless of whether they
     have a math coprocessor or not.

   - The "kernel hacking" configuration details usually result in a
     bigger or slower kernel (or both), and can even make the kernel
     less stable by configuring some routines to actively try to
     break bad code to find kernel problems (kmalloc()).  Thus you
     should probably answer 'n' to the questions for "development",
     "experimental", or "debugging" features.
”h]”(j  )”}”(hX{  Do not skip this step even if you are only upgrading one minor
version.  New configuration options are added in each release, and
odd problems will turn up if the configuration files are not set up
as expected.  If you want to carry your existing configuration to a
new version with minimal work, use ``make oldconfig``, which will
only ask you for the answers to new questions.
”h]”hï)”}”(hXz  Do not skip this step even if you are only upgrading one minor
version.  New configuration options are added in each release, and
odd problems will turn up if the configuration files are not set up
as expected.  If you want to carry your existing configuration to a
new version with minimal work, use ``make oldconfig``, which will
only ask you for the answers to new questions.”h]”(hX-  Do not skip this step even if you are only upgrading one minor
version.  New configuration options are added in each release, and
odd problems will turn up if the configuration files are not set up
as expected.  If you want to carry your existing configuration to a
new version with minimal work, use ”…””}”(hjp  h²hh³Nh´Nubjæ  )”}”(hŒ``make oldconfig``”h]”hŒmake oldconfig”…””}”(hjx  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hjp  ubhŒ;, which will
only ask you for the answers to new questions.”…””}”(hjp  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´K—hjl  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÃh´K—hjh  ubj¢  )”}”(hhh]”(j§  )”}”(hX«  Alternative configuration commands are::

  "make config"      Plain text interface.

  "make menuconfig"  Text based color menus, radiolists & dialogs.

  "make nconfig"     Enhanced text based color menus.

  "make xconfig"     Qt based configuration tool.

  "make gconfig"     GTK based configuration tool.

  "make oldconfig"   Default all questions based on the contents of
                     your existing ./.config file and asking about
                     new config symbols.

  "make olddefconfig"
                     Like above, but sets new symbols to their default
                     values without prompting.

  "make defconfig"   Create a ./.config file by using the default
                     symbol values from either arch/$ARCH/configs/defconfig
                     or arch/$ARCH/configs/${PLATFORM}_defconfig,
                     depending on the architecture.

  "make ${PLATFORM}_defconfig"
                     Create a ./.config file by using the default
                     symbol values from
                     arch/$ARCH/configs/${PLATFORM}_defconfig.
                     Use "make help" to get a list of all available
                     platforms of your architecture.

  "make allyesconfig"
                     Create a ./.config file by setting symbol
                     values to 'y' as much as possible.

  "make allmodconfig"
                     Create a ./.config file by setting symbol
                     values to 'm' as much as possible.

  "make allnoconfig" Create a ./.config file by setting symbol
                     values to 'n' as much as possible.

  "make randconfig"  Create a ./.config file by setting symbol
                     values to random values.

  "make localmodconfig" Create a config based on current config and
                        loaded modules (lsmod). Disables any module
                        option that is not needed for the loaded modules.

                        To create a localmodconfig for another machine,
                        store the lsmod of that machine into a file
                        and pass it in as a LSMOD parameter.

                        Also, you can preserve modules in certain folders
                        or kconfig files by specifying their paths in
                        parameter LMC_KEEP.

                target$ lsmod > /tmp/mylsmod
                target$ scp /tmp/mylsmod host:/tmp

                host$ make LSMOD=/tmp/mylsmod \
                        LMC_KEEP="drivers/usb:drivers/gpu:fs" \
                        localmodconfig

                        The above also works when cross compiling.

  "make localyesconfig" Similar to localmodconfig, except it will convert
                        all module options to built in (=y) options. You can
                        also preserve modules by LMC_KEEP.

  "make kvm_guest.config"   Enable additional options for kvm guest kernel
                            support.

  "make xen.config"   Enable additional options for xen dom0 guest kernel
                      support.

  "make tinyconfig"  Configure the tiniest possible kernel.

You can find more information on using the Linux kernel config tools
in Documentation/kbuild/kconfig.rst.
”h]”(hï)”}”(hŒ(Alternative configuration commands are::”h]”hŒ'Alternative configuration commands are:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Kžhj™  ubjB  )”}”(hX©  "make config"      Plain text interface.

"make menuconfig"  Text based color menus, radiolists & dialogs.

"make nconfig"     Enhanced text based color menus.

"make xconfig"     Qt based configuration tool.

"make gconfig"     GTK based configuration tool.

"make oldconfig"   Default all questions based on the contents of
                   your existing ./.config file and asking about
                   new config symbols.

"make olddefconfig"
                   Like above, but sets new symbols to their default
                   values without prompting.

"make defconfig"   Create a ./.config file by using the default
                   symbol values from either arch/$ARCH/configs/defconfig
                   or arch/$ARCH/configs/${PLATFORM}_defconfig,
                   depending on the architecture.

"make ${PLATFORM}_defconfig"
                   Create a ./.config file by using the default
                   symbol values from
                   arch/$ARCH/configs/${PLATFORM}_defconfig.
                   Use "make help" to get a list of all available
                   platforms of your architecture.

"make allyesconfig"
                   Create a ./.config file by setting symbol
                   values to 'y' as much as possible.

"make allmodconfig"
                   Create a ./.config file by setting symbol
                   values to 'm' as much as possible.

"make allnoconfig" Create a ./.config file by setting symbol
                   values to 'n' as much as possible.

"make randconfig"  Create a ./.config file by setting symbol
                   values to random values.

"make localmodconfig" Create a config based on current config and
                      loaded modules (lsmod). Disables any module
                      option that is not needed for the loaded modules.

                      To create a localmodconfig for another machine,
                      store the lsmod of that machine into a file
                      and pass it in as a LSMOD parameter.

                      Also, you can preserve modules in certain folders
                      or kconfig files by specifying their paths in
                      parameter LMC_KEEP.

              target$ lsmod > /tmp/mylsmod
              target$ scp /tmp/mylsmod host:/tmp

              host$ make LSMOD=/tmp/mylsmod \
                      LMC_KEEP="drivers/usb:drivers/gpu:fs" \
                      localmodconfig

                      The above also works when cross compiling.

"make localyesconfig" Similar to localmodconfig, except it will convert
                      all module options to built in (=y) options. You can
                      also preserve modules by LMC_KEEP.

"make kvm_guest.config"   Enable additional options for kvm guest kernel
                          support.

"make xen.config"   Enable additional options for xen dom0 guest kernel
                    support.

"make tinyconfig"  Configure the tiniest possible kernel.”h]”hX©  "make config"      Plain text interface.

"make menuconfig"  Text based color menus, radiolists & dialogs.

"make nconfig"     Enhanced text based color menus.

"make xconfig"     Qt based configuration tool.

"make gconfig"     GTK based configuration tool.

"make oldconfig"   Default all questions based on the contents of
                   your existing ./.config file and asking about
                   new config symbols.

"make olddefconfig"
                   Like above, but sets new symbols to their default
                   values without prompting.

"make defconfig"   Create a ./.config file by using the default
                   symbol values from either arch/$ARCH/configs/defconfig
                   or arch/$ARCH/configs/${PLATFORM}_defconfig,
                   depending on the architecture.

"make ${PLATFORM}_defconfig"
                   Create a ./.config file by using the default
                   symbol values from
                   arch/$ARCH/configs/${PLATFORM}_defconfig.
                   Use "make help" to get a list of all available
                   platforms of your architecture.

"make allyesconfig"
                   Create a ./.config file by setting symbol
                   values to 'y' as much as possible.

"make allmodconfig"
                   Create a ./.config file by setting symbol
                   values to 'm' as much as possible.

"make allnoconfig" Create a ./.config file by setting symbol
                   values to 'n' as much as possible.

"make randconfig"  Create a ./.config file by setting symbol
                   values to random values.

"make localmodconfig" Create a config based on current config and
                      loaded modules (lsmod). Disables any module
                      option that is not needed for the loaded modules.

                      To create a localmodconfig for another machine,
                      store the lsmod of that machine into a file
                      and pass it in as a LSMOD parameter.

                      Also, you can preserve modules in certain folders
                      or kconfig files by specifying their paths in
                      parameter LMC_KEEP.

              target$ lsmod > /tmp/mylsmod
              target$ scp /tmp/mylsmod host:/tmp

              host$ make LSMOD=/tmp/mylsmod \
                      LMC_KEEP="drivers/usb:drivers/gpu:fs" \
                      localmodconfig

                      The above also works when cross compiling.

"make localyesconfig" Similar to localmodconfig, except it will convert
                      all module options to built in (=y) options. You can
                      also preserve modules by LMC_KEEP.

"make kvm_guest.config"   Enable additional options for kvm guest kernel
                          support.

"make xen.config"   Enable additional options for xen dom0 guest kernel
                    support.

"make tinyconfig"  Configure the tiniest possible kernel.”…””}”hj«  sbah}”(h]”h ]”h"]”h$]”h&]”jQ  jR  uh1jA  h³hÃh´K hj™  ubhï)”}”(hŒiYou can find more information on using the Linux kernel config tools
in Documentation/kbuild/kconfig.rst.”h]”hŒiYou can find more information on using the Linux kernel config tools
in Documentation/kbuild/kconfig.rst.”…””}”(hj¹  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Kíhj™  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj–  ubj§  )”}”(hXz  NOTES on ``make config``:

 - Having unnecessary drivers will make the kernel bigger, and can
   under some circumstances lead to problems: probing for a
   nonexistent controller card may confuse your other controllers.

 - A kernel with math-emulation compiled in will still use the
   coprocessor if one is present: the math emulation will just
   never get used in that case.  The kernel will be slightly larger,
   but will work on different machines regardless of whether they
   have a math coprocessor or not.

 - The "kernel hacking" configuration details usually result in a
   bigger or slower kernel (or both), and can even make the kernel
   less stable by configuring some routines to actively try to
   break bad code to find kernel problems (kmalloc()).  Thus you
   should probably answer 'n' to the questions for "development",
   "experimental", or "debugging" features.
”h]”(hï)”}”(hŒNOTES on ``make config``:”h]”(hŒ	NOTES on ”…””}”(hjÑ  h²hh³Nh´Nubjæ  )”}”(hŒ``make config``”h]”hŒmake config”…””}”(hjÙ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hjÑ  ubhŒ:”…””}”(hjÑ  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´KðhjÍ  ubj  )”}”(hXQ  - Having unnecessary drivers will make the kernel bigger, and can
  under some circumstances lead to problems: probing for a
  nonexistent controller card may confuse your other controllers.

- A kernel with math-emulation compiled in will still use the
  coprocessor if one is present: the math emulation will just
  never get used in that case.  The kernel will be slightly larger,
  but will work on different machines regardless of whether they
  have a math coprocessor or not.

- The "kernel hacking" configuration details usually result in a
  bigger or slower kernel (or both), and can even make the kernel
  less stable by configuring some routines to actively try to
  break bad code to find kernel problems (kmalloc()).  Thus you
  should probably answer 'n' to the questions for "development",
  "experimental", or "debugging" features.
”h]”j¢  )”}”(hhh]”(j§  )”}”(hŒ¹Having unnecessary drivers will make the kernel bigger, and can
under some circumstances lead to problems: probing for a
nonexistent controller card may confuse your other controllers.
”h]”hï)”}”(hŒ¸Having unnecessary drivers will make the kernel bigger, and can
under some circumstances lead to problems: probing for a
nonexistent controller card may confuse your other controllers.”h]”hŒ¸Having unnecessary drivers will make the kernel bigger, and can
under some circumstances lead to problems: probing for a
nonexistent controller card may confuse your other controllers.”…””}”(hjü  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Kòhjø  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hjõ  ubj§  )”}”(hX  A kernel with math-emulation compiled in will still use the
coprocessor if one is present: the math emulation will just
never get used in that case.  The kernel will be slightly larger,
but will work on different machines regardless of whether they
have a math coprocessor or not.
”h]”hï)”}”(hX  A kernel with math-emulation compiled in will still use the
coprocessor if one is present: the math emulation will just
never get used in that case.  The kernel will be slightly larger,
but will work on different machines regardless of whether they
have a math coprocessor or not.”h]”hX  A kernel with math-emulation compiled in will still use the
coprocessor if one is present: the math emulation will just
never get used in that case.  The kernel will be slightly larger,
but will work on different machines regardless of whether they
have a math coprocessor or not.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Köhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hjõ  ubj§  )”}”(hXa  The "kernel hacking" configuration details usually result in a
bigger or slower kernel (or both), and can even make the kernel
less stable by configuring some routines to actively try to
break bad code to find kernel problems (kmalloc()).  Thus you
should probably answer 'n' to the questions for "development",
"experimental", or "debugging" features.
”h]”hï)”}”(hX`  The "kernel hacking" configuration details usually result in a
bigger or slower kernel (or both), and can even make the kernel
less stable by configuring some routines to actively try to
break bad code to find kernel problems (kmalloc()).  Thus you
should probably answer 'n' to the questions for "development",
"experimental", or "debugging" features.”h]”hXt  The â€œkernel hackingâ€ configuration details usually result in a
bigger or slower kernel (or both), and can even make the kernel
less stable by configuring some routines to actively try to
break bad code to find kernel problems (kmalloc()).  Thus you
should probably answer â€˜nâ€™ to the questions for â€œdevelopmentâ€,
â€œexperimentalâ€, or â€œdebuggingâ€ features.”…””}”(hj,  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Kühj(  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hjõ  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1j¡  h³hÃh´Kòhjñ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÃh´KòhjÍ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj–  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1j¡  h³hÃh´Kžhjh  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÃh´K—hjW  h²hubeh}”(h]”Œconfiguring-the-kernel”ah ]”h"]”Œconfiguring the kernel”ah$]”h&]”uh1hÄhhÆh²hh³hÃh´K•ubhÅ)”}”(hhh]”(hÊ)”}”(hŒCompiling the kernel”h]”hŒCompiling the kernel”…””}”(hji  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjf  h²hh³hÃh´Mubj  )”}”(hXr  - Make sure you have at least gcc 8.1 available.
  For more information, refer to :ref:`Documentation/process/changes.rst <changes>`.

- Do a ``make`` to create a compressed kernel image. It is also possible to do
  ``make install`` if you have lilo installed or if your distribution has an
  install script recognised by the kernel's installer. Most popular
  distributions will have a recognized install script. You may want to
  check your distribution's setup first.

  To do the actual install, you have to be root, but none of the normal
  build should require that. Don't take the name of root in vain.

- If you configured any of the parts of the kernel as ``modules``, you
  will also have to do ``make modules_install``.

- Verbose kernel compile/build output:

  Normally, the kernel build system runs in a fairly quiet mode (but not
  totally silent).  However, sometimes you or other kernel developers need
  to see compile, link, or other commands exactly as they are executed.
  For this, use "verbose" build mode.  This is done by passing
  ``V=1`` to the ``make`` command, e.g.::

    make V=1 all

  To have the build system also tell the reason for the rebuild of each
  target, use ``V=2``.  The default is ``V=0``.

- Keep a backup kernel handy in case something goes wrong.  This is
  especially true for the development releases, since each new release
  contains new code which has not been debugged.  Make sure you keep a
  backup of the modules corresponding to that kernel, as well.  If you
  are installing a new kernel with the same version number as your
  working kernel, make a backup of your modules directory before you
  do a ``make modules_install``.

  Alternatively, before compiling, use the kernel config option
  "LOCALVERSION" to append a unique suffix to the regular kernel version.
  LOCALVERSION can be set in the "General Setup" menu.

- In order to boot your new kernel, you'll need to copy the kernel
  image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
  to the place where your regular bootable kernel is found.

- Booting a kernel directly from a storage device without the assistance
  of a bootloader such as LILO or GRUB, is no longer supported in BIOS
  (non-EFI systems). On UEFI/EFI systems, however, you can use EFISTUB
  which allows the motherboard to boot directly to the kernel.
  On modern workstations and desktops, it's generally recommended to use a
  bootloader as difficulties can arise with multiple kernels and secure boot.
  For more details on EFISTUB,
  see "Documentation/admin-guide/efi-stub.rst".

- It's important to note that as of 2016 LILO (LInux LOader) is no longer in
  active development, though as it was extremely popular, it often comes up
  in documentation. Popular alternatives include GRUB2, rEFInd, Syslinux,
  systemd-boot, or EFISTUB. For various reasons, it's not recommended to use
  software that's no longer in active development.

- Chances are your distribution includes an install script and running
  ``make install`` will be all that's needed. Should that not be the case
  you'll have to identify your bootloader and reference its documentation or
  configure your EFI.
”h]”j¢  )”}”(hhh]”(j§  )”}”(hŒ‚Make sure you have at least gcc 8.1 available.
For more information, refer to :ref:`Documentation/process/changes.rst <changes>`.
”h]”hï)”}”(hŒMake sure you have at least gcc 8.1 available.
For more information, refer to :ref:`Documentation/process/changes.rst <changes>`.”h]”(hŒNMake sure you have at least gcc 8.1 available.
For more information, refer to ”…””}”(hj‚  h²hh³Nh´Nubh)”}”(hŒ2:ref:`Documentation/process/changes.rst <changes>`”h]”jÑ  )”}”(hjŒ  h]”hŒ!Documentation/process/changes.rst”…””}”(hjŽ  h²hh³Nh´Nubah}”(h]”h ]”(jÜ  Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jÐ  hjŠ  ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”jé  Œ	refdomain”j˜  Œreftype”Œref”Œrefexplicit”ˆŒrefwarn”ˆjï  Œchanges”uh1hh³hÃh´Mhj‚  ubhŒ.”…””}”(hj‚  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Mhj~  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj{  ubj§  )”}”(hXÍ  Do a ``make`` to create a compressed kernel image. It is also possible to do
``make install`` if you have lilo installed or if your distribution has an
install script recognised by the kernel's installer. Most popular
distributions will have a recognized install script. You may want to
check your distribution's setup first.

To do the actual install, you have to be root, but none of the normal
build should require that. Don't take the name of root in vain.
”h]”(hï)”}”(hXE  Do a ``make`` to create a compressed kernel image. It is also possible to do
``make install`` if you have lilo installed or if your distribution has an
install script recognised by the kernel's installer. Most popular
distributions will have a recognized install script. You may want to
check your distribution's setup first.”h]”(hŒDo a ”…””}”(hj¾  h²hh³Nh´Nubjæ  )”}”(hŒ``make``”h]”hŒmake”…””}”(hjÆ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hj¾  ubhŒ@ to create a compressed kernel image. It is also possible to do
”…””}”(hj¾  h²hh³Nh´Nubjæ  )”}”(hŒ``make install``”h]”hŒmake install”…””}”(hjØ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hj¾  ubhŒì if you have lilo installed or if your distribution has an
install script recognised by the kernelâ€™s installer. Most popular
distributions will have a recognized install script. You may want to
check your distributionâ€™s setup first.”…””}”(hj¾  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´M	hjº  ubhï)”}”(hŒ…To do the actual install, you have to be root, but none of the normal
build should require that. Don't take the name of root in vain.”h]”hŒ‡To do the actual install, you have to be root, but none of the normal
build should require that. Donâ€™t take the name of root in vain.”…””}”(hjð  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Mhjº  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj{  ubj§  )”}”(hŒtIf you configured any of the parts of the kernel as ``modules``, you
will also have to do ``make modules_install``.
”h]”hï)”}”(hŒsIf you configured any of the parts of the kernel as ``modules``, you
will also have to do ``make modules_install``.”h]”(hŒ4If you configured any of the parts of the kernel as ”…””}”(hj  h²hh³Nh´Nubjæ  )”}”(hŒ``modules``”h]”hŒmodules”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hj  ubhŒ, you
will also have to do ”…””}”(hj  h²hh³Nh´Nubjæ  )”}”(hŒ``make modules_install``”h]”hŒmake modules_install”…””}”(hj"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hj  ubhŒ.”…””}”(hj  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Mhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj{  ubj§  )”}”(hXæ  Verbose kernel compile/build output:

Normally, the kernel build system runs in a fairly quiet mode (but not
totally silent).  However, sometimes you or other kernel developers need
to see compile, link, or other commands exactly as they are executed.
For this, use "verbose" build mode.  This is done by passing
``V=1`` to the ``make`` command, e.g.::

  make V=1 all

To have the build system also tell the reason for the rebuild of each
target, use ``V=2``.  The default is ``V=0``.
”h]”(hï)”}”(hŒ$Verbose kernel compile/build output:”h]”hŒ$Verbose kernel compile/build output:”…””}”(hjD  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Mhj@  ubhï)”}”(hX:  Normally, the kernel build system runs in a fairly quiet mode (but not
totally silent).  However, sometimes you or other kernel developers need
to see compile, link, or other commands exactly as they are executed.
For this, use "verbose" build mode.  This is done by passing
``V=1`` to the ``make`` command, e.g.::”h]”(hX  Normally, the kernel build system runs in a fairly quiet mode (but not
totally silent).  However, sometimes you or other kernel developers need
to see compile, link, or other commands exactly as they are executed.
For this, use â€œverboseâ€ build mode.  This is done by passing
”…””}”(hjR  h²hh³Nh´Nubjæ  )”}”(hŒ``V=1``”h]”hŒV=1”…””}”(hjZ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hjR  ubhŒ to the ”…””}”(hjR  h²hh³Nh´Nubjæ  )”}”(hŒ``make``”h]”hŒmake”…””}”(hjl  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hjR  ubhŒ command, e.g.:”…””}”(hjR  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Mhj@  ubjB  )”}”(hŒmake V=1 all”h]”hŒmake V=1 all”…””}”hj„  sbah}”(h]”h ]”h"]”h$]”h&]”jQ  jR  uh1jA  h³hÃh´Mhj@  ubhï)”}”(hŒsTo have the build system also tell the reason for the rebuild of each
target, use ``V=2``.  The default is ``V=0``.”h]”(hŒRTo have the build system also tell the reason for the rebuild of each
target, use ”…””}”(hj’  h²hh³Nh´Nubjæ  )”}”(hŒ``V=2``”h]”hŒV=2”…””}”(hjš  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hj’  ubhŒ.  The default is ”…””}”(hj’  h²hh³Nh´Nubjæ  )”}”(hŒ``V=0``”h]”hŒV=0”…””}”(hj¬  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hj’  ubhŒ.”…””}”(hj’  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Mhj@  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj{  ubj§  )”}”(hXp  Keep a backup kernel handy in case something goes wrong.  This is
especially true for the development releases, since each new release
contains new code which has not been debugged.  Make sure you keep a
backup of the modules corresponding to that kernel, as well.  If you
are installing a new kernel with the same version number as your
working kernel, make a backup of your modules directory before you
do a ``make modules_install``.

Alternatively, before compiling, use the kernel config option
"LOCALVERSION" to append a unique suffix to the regular kernel version.
LOCALVERSION can be set in the "General Setup" menu.
”h]”(hï)”}”(hX³  Keep a backup kernel handy in case something goes wrong.  This is
especially true for the development releases, since each new release
contains new code which has not been debugged.  Make sure you keep a
backup of the modules corresponding to that kernel, as well.  If you
are installing a new kernel with the same version number as your
working kernel, make a backup of your modules directory before you
do a ``make modules_install``.”h]”(hXš  Keep a backup kernel handy in case something goes wrong.  This is
especially true for the development releases, since each new release
contains new code which has not been debugged.  Make sure you keep a
backup of the modules corresponding to that kernel, as well.  If you
are installing a new kernel with the same version number as your
working kernel, make a backup of your modules directory before you
do a ”…””}”(hjÎ  h²hh³Nh´Nubjæ  )”}”(hŒ``make modules_install``”h]”hŒmake modules_install”…””}”(hjÖ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hjÎ  ubhŒ.”…””}”(hjÎ  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´M"hjÊ  ubhï)”}”(hŒºAlternatively, before compiling, use the kernel config option
"LOCALVERSION" to append a unique suffix to the regular kernel version.
LOCALVERSION can be set in the "General Setup" menu.”h]”hŒÂAlternatively, before compiling, use the kernel config option
â€œLOCALVERSIONâ€ to append a unique suffix to the regular kernel version.
LOCALVERSION can be set in the â€œGeneral Setupâ€ menu.”…””}”(hjî  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´M*hjÊ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj{  ubj§  )”}”(hŒºIn order to boot your new kernel, you'll need to copy the kernel
image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
to the place where your regular bootable kernel is found.
”h]”hï)”}”(hŒ¹In order to boot your new kernel, you'll need to copy the kernel
image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
to the place where your regular bootable kernel is found.”h]”hŒ»In order to boot your new kernel, youâ€™ll need to copy the kernel
image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
to the place where your regular bootable kernel is found.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´M.hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj{  ubj§  )”}”(hXî  Booting a kernel directly from a storage device without the assistance
of a bootloader such as LILO or GRUB, is no longer supported in BIOS
(non-EFI systems). On UEFI/EFI systems, however, you can use EFISTUB
which allows the motherboard to boot directly to the kernel.
On modern workstations and desktops, it's generally recommended to use a
bootloader as difficulties can arise with multiple kernels and secure boot.
For more details on EFISTUB,
see "Documentation/admin-guide/efi-stub.rst".
”h]”hï)”}”(hXí  Booting a kernel directly from a storage device without the assistance
of a bootloader such as LILO or GRUB, is no longer supported in BIOS
(non-EFI systems). On UEFI/EFI systems, however, you can use EFISTUB
which allows the motherboard to boot directly to the kernel.
On modern workstations and desktops, it's generally recommended to use a
bootloader as difficulties can arise with multiple kernels and secure boot.
For more details on EFISTUB,
see "Documentation/admin-guide/efi-stub.rst".”h]”hXó  Booting a kernel directly from a storage device without the assistance
of a bootloader such as LILO or GRUB, is no longer supported in BIOS
(non-EFI systems). On UEFI/EFI systems, however, you can use EFISTUB
which allows the motherboard to boot directly to the kernel.
On modern workstations and desktops, itâ€™s generally recommended to use a
bootloader as difficulties can arise with multiple kernels and secure boot.
For more details on EFISTUB,
see â€œDocumentation/admin-guide/efi-stub.rstâ€.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´M2hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj{  ubj§  )”}”(hXY  It's important to note that as of 2016 LILO (LInux LOader) is no longer in
active development, though as it was extremely popular, it often comes up
in documentation. Popular alternatives include GRUB2, rEFInd, Syslinux,
systemd-boot, or EFISTUB. For various reasons, it's not recommended to use
software that's no longer in active development.
”h]”hï)”}”(hXX  It's important to note that as of 2016 LILO (LInux LOader) is no longer in
active development, though as it was extremely popular, it often comes up
in documentation. Popular alternatives include GRUB2, rEFInd, Syslinux,
systemd-boot, or EFISTUB. For various reasons, it's not recommended to use
software that's no longer in active development.”h]”hX^  Itâ€™s important to note that as of 2016 LILO (LInux LOader) is no longer in
active development, though as it was extremely popular, it often comes up
in documentation. Popular alternatives include GRUB2, rEFInd, Syslinux,
systemd-boot, or EFISTUB. For various reasons, itâ€™s not recommended to use
software thatâ€™s no longer in active development.”…””•_(      }”(hj6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´M;hj2  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj{  ubj§  )”}”(hŒìChances are your distribution includes an install script and running
``make install`` will be all that's needed. Should that not be the case
you'll have to identify your bootloader and reference its documentation or
configure your EFI.
”h]”hï)”}”(hŒëChances are your distribution includes an install script and running
``make install`` will be all that's needed. Should that not be the case
you'll have to identify your bootloader and reference its documentation or
configure your EFI.”h]”(hŒEChances are your distribution includes an install script and running
”…””}”(hjN  h²hh³Nh´Nubjæ  )”}”(hŒ``make install``”h]”hŒmake install”…””}”(hjV  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jå  hjN  ubhŒš will be all thatâ€™s needed. Should that not be the case
youâ€™ll have to identify your bootloader and reference its documentation or
configure your EFI.”…””}”(hjN  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´MAhjJ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj{  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1j¡  h³hÃh´Mhjw  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÃh´Mhjf  h²hubeh}”(h]”Œcompiling-the-kernel”ah ]”h"]”Œcompiling the kernel”ah$]”h&]”uh1hÄhhÆh²hh³hÃh´MubhÅ)”}”(hhh]”(hÊ)”}”(hŒLegacy LILO Instructions”h]”hŒLegacy LILO Instructions”…””}”(hj‹  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjˆ  h²hh³hÃh´MGubj  )”}”(hXÌ  - If you use LILO the kernel images are specified in the file /etc/lilo.conf.
  The kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
  /boot/bzImage. To use the new kernel, save a copy of the old image and copy
  the new image over the old one. Then, you MUST RERUN LILO to update the
  loading map! If you don't, you won't be able to boot the new kernel image.

- Reinstalling LILO is usually a matter of running /sbin/lilo. You may wish
  to edit /etc/lilo.conf to specify an entry for your old kernel image
  (say, /vmlinux.old) in case the new one does not work. See the LILO docs
  for more information.

- After reinstalling LILO, you should be all set. Shutdown the system,
  reboot, and enjoy!

- If you ever need to change the default root device, video mode, etc. in the
  kernel image, use your bootloader's boot options where appropriate. No need
  to recompile the kernel to change these parameters.

- Reboot with the new kernel and enjoy.

”h]”j¢  )”}”(hhh]”(j§  )”}”(hXq  If you use LILO the kernel images are specified in the file /etc/lilo.conf.
The kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
/boot/bzImage. To use the new kernel, save a copy of the old image and copy
the new image over the old one. Then, you MUST RERUN LILO to update the
loading map! If you don't, you won't be able to boot the new kernel image.
”h]”hï)”}”(hXp  If you use LILO the kernel images are specified in the file /etc/lilo.conf.
The kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
/boot/bzImage. To use the new kernel, save a copy of the old image and copy
the new image over the old one. Then, you MUST RERUN LILO to update the
loading map! If you don't, you won't be able to boot the new kernel image.”h]”hXt  If you use LILO the kernel images are specified in the file /etc/lilo.conf.
The kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
/boot/bzImage. To use the new kernel, save a copy of the old image and copy
the new image over the old one. Then, you MUST RERUN LILO to update the
loading map! If you donâ€™t, you wonâ€™t be able to boot the new kernel image.”…””}”(hj¤  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´MJhj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj  ubj§  )”}”(hŒîReinstalling LILO is usually a matter of running /sbin/lilo. You may wish
to edit /etc/lilo.conf to specify an entry for your old kernel image
(say, /vmlinux.old) in case the new one does not work. See the LILO docs
for more information.
”h]”hï)”}”(hŒíReinstalling LILO is usually a matter of running /sbin/lilo. You may wish
to edit /etc/lilo.conf to specify an entry for your old kernel image
(say, /vmlinux.old) in case the new one does not work. See the LILO docs
for more information.”h]”hŒíReinstalling LILO is usually a matter of running /sbin/lilo. You may wish
to edit /etc/lilo.conf to specify an entry for your old kernel image
(say, /vmlinux.old) in case the new one does not work. See the LILO docs
for more information.”…””}”(hj¼  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´MPhj¸  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj  ubj§  )”}”(hŒXAfter reinstalling LILO, you should be all set. Shutdown the system,
reboot, and enjoy!
”h]”hï)”}”(hŒWAfter reinstalling LILO, you should be all set. Shutdown the system,
reboot, and enjoy!”h]”hŒWAfter reinstalling LILO, you should be all set. Shutdown the system,
reboot, and enjoy!”…””}”(hjÔ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´MUhjÐ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj  ubj§  )”}”(hŒÌIf you ever need to change the default root device, video mode, etc. in the
kernel image, use your bootloader's boot options where appropriate. No need
to recompile the kernel to change these parameters.
”h]”hï)”}”(hŒËIf you ever need to change the default root device, video mode, etc. in the
kernel image, use your bootloader's boot options where appropriate. No need
to recompile the kernel to change these parameters.”h]”hŒÍIf you ever need to change the default root device, video mode, etc. in the
kernel image, use your bootloaderâ€™s boot options where appropriate. No need
to recompile the kernel to change these parameters.”…””}”(hjì  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´MXhjè  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj  ubj§  )”}”(hŒ'Reboot with the new kernel and enjoy.

”h]”hï)”}”(hŒ%Reboot with the new kernel and enjoy.”h]”hŒ%Reboot with the new kernel and enjoy.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´M\hj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1j¡  h³hÃh´MJhj™  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÃh´MJhjˆ  h²hubeh}”(h]”Œlegacy-lilo-instructions”ah ]”h"]”Œlegacy lilo instructions”ah$]”h&]”uh1hÄhhÆh²hh³hÃh´MGubhÅ)”}”(hhh]”(hÊ)”}”(hŒIf something goes wrong”h]”hŒIf something goes wrong”…””}”(hj/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhj,  h²hh³hÃh´M`ubhï)”}”(hŒŒIf you have problems that seem to be due to kernel bugs, please follow the
instructions at 'Documentation/admin-guide/reporting-issues.rst'.”h]”hŒIf you have problems that seem to be due to kernel bugs, please follow the
instructions at â€˜Documentation/admin-guide/reporting-issues.rstâ€™.”…””}”(hj=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Mbhj,  h²hubhï)”}”(hŒôHints on understanding kernel bug reports are in
'Documentation/admin-guide/bug-hunting.rst'. More on debugging the kernel
with gdb is in 'Documentation/process/debugging/gdb-kernel-debugging.rst' and
'Documentation/process/debugging/kgdb.rst'.”h]”hX   Hints on understanding kernel bug reports are in
â€˜Documentation/admin-guide/bug-hunting.rstâ€™. More on debugging the kernel
with gdb is in â€˜Documentation/process/debugging/gdb-kernel-debugging.rstâ€™ and
â€˜Documentation/process/debugging/kgdb.rstâ€™.”…””}”(hjK  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÃh´Mehj,  h²hubeh}”(h]”Œif-something-goes-wrong”ah ]”h"]”Œif something goes wrong”ah$]”h&]”uh1hÄhhÆh²hh³hÃh´M`ubeh}”(h]”(Œ(linux-kernel-release-6-x-http-kernel-org”hÂeh ]”h"]”(Œ-linux kernel release 6.x <http://kernel.org/>”Œreadme”eh$]”h&]”uh1hÄhhh²hh³hÃh´KŒexpect_referenced_by_name”}”jg  h·sŒexpect_referenced_by_id”}”hÂh·subeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÃuh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hÉNŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j‘  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÃŒ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”hÂ]”h·asŒnameids”}”(jg  hÂjf  jc  jJ  jG  j‰  j†  j  j  jp  jm  jÅ  jÂ  jT  jQ  jc  j`  j…  j‚  j)  j&  j^  j[  uŒ	nametypes”}”(jg  ˆjf  ‰jJ  ‰j‰  ‰j  ‰jp  ‰jÅ  ‰jT  ‰jc  ‰j…  ‰j)  ‰j^  ‰uh}”(hÂhÆjc  hÆjG  hþj†  jM  j  jŒ  jm  j  jÂ  js  jQ  jÈ  j`  jW  j‚  jf  j&  jˆ  j[  j,  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”hŒsystem_message”“”)”}”(hhh]”hï)”}”(hhh]”hŒ,Hyperlink target "readme" is not referenced.”…””}”hjû  sbah}”(h]”h ]”h"]”h$]”h&]”uh1hîhjø  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œsource”hÃŒline”Kuh1jö  ubaŒtransformer”NŒinclude_log”]”Œ
decoration”Nh²hub.