| 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
|---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
|---|
| 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
|---|
| 5 | %general-entities;
|
|---|
| 6 | ]>
|
|---|
| 7 |
|
|---|
| 8 | <sect1 id="ch-bootable-kernel" role="wrap">
|
|---|
| 9 | <?dbhtml filename="kernel.html"?>
|
|---|
| 10 |
|
|---|
| 11 | <sect1info condition="script">
|
|---|
| 12 | <productname>kernel</productname>
|
|---|
| 13 | <productnumber>&linux-version;</productnumber>
|
|---|
| 14 | <address>&linux-url;</address>
|
|---|
| 15 | </sect1info>
|
|---|
| 16 |
|
|---|
| 17 | <title>Linux-&linux-version;</title>
|
|---|
| 18 |
|
|---|
| 19 | <indexterm zone="ch-bootable-kernel">
|
|---|
| 20 | <primary sortas="a-Linux">Linux</primary>
|
|---|
| 21 | </indexterm>
|
|---|
| 22 |
|
|---|
| 23 | <sect2 role="package">
|
|---|
| 24 | <title/>
|
|---|
| 25 |
|
|---|
| 26 | <para>The Linux package contains the Linux kernel.</para>
|
|---|
| 27 |
|
|---|
| 28 | <segmentedlist>
|
|---|
| 29 | <segtitle>&buildtime;</segtitle>
|
|---|
| 30 | <segtitle>&diskspace;</segtitle>
|
|---|
| 31 |
|
|---|
| 32 | <seglistitem>
|
|---|
| 33 | <seg>&linux-knl-sbu;</seg>
|
|---|
| 34 | <seg>&linux-knl-du;</seg>
|
|---|
| 35 | </seglistitem>
|
|---|
| 36 | </segmentedlist>
|
|---|
| 37 |
|
|---|
| 38 | </sect2>
|
|---|
| 39 |
|
|---|
| 40 | <sect2 role="installation">
|
|---|
| 41 | <title>Installation of the kernel</title>
|
|---|
| 42 |
|
|---|
| 43 | <para>Building the kernel involves a few steps—configuration,
|
|---|
| 44 | compilation, and installation. Read the <filename>README</filename> file
|
|---|
| 45 | in the kernel source tree for alternative methods to the way this book
|
|---|
| 46 | configures the kernel.</para>
|
|---|
| 47 |
|
|---|
| 48 | <important>
|
|---|
| 49 | <para>
|
|---|
| 50 | Building the linux kernel for the first time is one of the most
|
|---|
| 51 | challenging tasks in LFS. Getting it right depends on the specific
|
|---|
| 52 | hardware for the target system and your specific needs. There are
|
|---|
| 53 | almost 12,000 configuration items that are available for the kernel
|
|---|
| 54 | although only about a third of them are needed for most computers. The
|
|---|
| 55 | LFS editors recommend that users not familiar with this process follow
|
|---|
| 56 | the procedures below fairly closely. The objective is to get an
|
|---|
| 57 | initial system to a point where you can log in at the command line when
|
|---|
| 58 | you reboot later in <xref linkend="ch-finish-reboot"/>. At this point
|
|---|
| 59 | optimization and customization is not a goal.
|
|---|
| 60 | </para>
|
|---|
| 61 |
|
|---|
| 62 |
|
|---|
| 63 | <para>
|
|---|
| 64 | For general information on kernel configuration see <ulink
|
|---|
| 65 | url="&hints-root;kernel-configuration.txt"/>. Additional information
|
|---|
| 66 | about configuring and building the kernel can be found at <ulink
|
|---|
| 67 | url="&anduin-sources;/kernel-nutshell/"/>.
|
|---|
| 68 | These references are a bit
|
|---|
| 69 | dated, but still give a reasonable overview of the process.
|
|---|
| 70 | </para>
|
|---|
| 71 |
|
|---|
| 72 | <para>
|
|---|
| 73 | If all else fails, you can ask for help on the <ulink
|
|---|
| 74 | url="https://www.linuxfromscratch.org/mail.html">lfs-support</ulink>
|
|---|
| 75 | mailing list. Note that subscribing is required in order for the list
|
|---|
| 76 | to avoid spam.
|
|---|
| 77 | </para>
|
|---|
| 78 | </important>
|
|---|
| 79 |
|
|---|
| 80 | <para>Prepare for compilation by running the following command:</para>
|
|---|
| 81 |
|
|---|
| 82 | <screen><userinput remap="pre">make mrproper</userinput></screen>
|
|---|
| 83 |
|
|---|
| 84 | <para>This ensures that the kernel tree is absolutely clean. The
|
|---|
| 85 | kernel team recommends that this command be issued prior to each
|
|---|
| 86 | kernel compilation. Do not rely on the source tree being clean after
|
|---|
| 87 | un-tarring.</para>
|
|---|
| 88 |
|
|---|
| 89 | <para>There are several ways to configure the kernel options. Usually,
|
|---|
| 90 | This is done through a menu-driven interface, for example:</para>
|
|---|
| 91 |
|
|---|
| 92 | <screen role="nodump"><userinput>make menuconfig</userinput></screen>
|
|---|
| 93 |
|
|---|
| 94 | <variablelist>
|
|---|
| 95 | <title>The meaning of optional make environment variables:</title>
|
|---|
| 96 |
|
|---|
| 97 | <varlistentry>
|
|---|
| 98 | <term><parameter>LANG=<host_LANG_value> LC_ALL=</parameter></term>
|
|---|
| 99 | <listitem>
|
|---|
| 100 | <para>This establishes the locale setting to the one used on the
|
|---|
| 101 | host. This may be needed for a proper menuconfig ncurses interface
|
|---|
| 102 | line drawing on a UTF-8 linux text console.</para>
|
|---|
| 103 |
|
|---|
| 104 | <para>If used, be sure to replace
|
|---|
| 105 | <replaceable><host_LANG_value></replaceable> by the value of
|
|---|
| 106 | the <envar>$LANG</envar> variable from your host. You can
|
|---|
| 107 | alternatively use instead the host's value of <envar>$LC_ALL</envar>
|
|---|
| 108 | or <envar>$LC_CTYPE</envar>.</para>
|
|---|
| 109 | </listitem>
|
|---|
| 110 | </varlistentry>
|
|---|
| 111 |
|
|---|
| 112 | <varlistentry>
|
|---|
| 113 | <term><command>make menuconfig</command></term>
|
|---|
| 114 | <listitem>
|
|---|
| 115 | <para>This launches an ncurses menu-driven interface. For other
|
|---|
| 116 | (graphical) interfaces, type <command>make help</command>.</para>
|
|---|
| 117 | </listitem>
|
|---|
| 118 | </varlistentry>
|
|---|
| 119 | </variablelist>
|
|---|
| 120 |
|
|---|
| 121 | <!-- Support for compiling a keymap into the kernel is deliberately removed -->
|
|---|
| 122 |
|
|---|
| 123 |
|
|---|
| 124 | <note>
|
|---|
| 125 | <para>A good starting place for setting up the kernel configuration is to
|
|---|
| 126 | run <command>make defconfig</command>. This will set the base
|
|---|
| 127 | configuration to a good state that takes your current system architecture
|
|---|
| 128 | into account.</para>
|
|---|
| 129 |
|
|---|
| 130 | <para>Be sure to enable/disable/set the following features or the system might
|
|---|
| 131 | not work correctly or boot at all:</para>
|
|---|
| 132 |
|
|---|
| 133 | <!-- To editors: for updating kernel configuration, edit
|
|---|
| 134 | kernel/*.toml and regenerate kernel/*.xml with
|
|---|
| 135 | "make -C kernel KERNEL_TREE=</usr/src/linux-&linux-version> -->
|
|---|
| 136 |
|
|---|
| 137 | <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
|
|---|
| 138 | href="kernel/sysv.xml"/>
|
|---|
| 139 |
|
|---|
| 140 | <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
|
|---|
| 141 | href="kernel/systemd.xml"/>
|
|---|
| 142 |
|
|---|
| 143 | <para>If the partition for the LFS system is in a NVME SSD (i. e. the
|
|---|
| 144 | device node for the partition is <filename>/dev/nvme*</filename>
|
|---|
| 145 | instead of <filename>/dev/sd*</filename>), enable NVME support or
|
|---|
| 146 | the LFS system won't boot:</para>
|
|---|
| 147 |
|
|---|
| 148 | <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
|
|---|
| 149 | href="kernel/nvme.xml"/>
|
|---|
| 150 | </note>
|
|---|
| 151 |
|
|---|
| 152 | <note revision="systemd">
|
|---|
| 153 | <para>While "The IPv6 Protocol" is not strictly
|
|---|
| 154 | required, it is highly recommended by the systemd developers.</para>
|
|---|
| 155 | </note>
|
|---|
| 156 |
|
|---|
| 157 | <para>There are several other options that may be desired
|
|---|
| 158 | depending on the requirements for the system. For a list of options needed
|
|---|
| 159 | for BLFS packages, see the <ulink
|
|---|
| 160 | url="&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index">BLFS
|
|---|
| 161 | Index of Kernel Settings</ulink>.</para>
|
|---|
| 162 |
|
|---|
| 163 | <note>
|
|---|
| 164 | <para>If your host hardware is using UEFI and you wish to boot the
|
|---|
| 165 | LFS system with it, you should adjust some kernel configuration
|
|---|
| 166 | following <ulink url="&blfs-book;postlfs/grub-setup.html#uefi-kernel">
|
|---|
| 167 | the BLFS page</ulink> <emphasis role='bold'>even if you'll use the
|
|---|
| 168 | UEFI bootloader from the host distro</emphasis>.</para>
|
|---|
| 169 | </note>
|
|---|
| 170 |
|
|---|
| 171 | <variablelist>
|
|---|
| 172 | <title>The rationale for the above configuration items:</title>
|
|---|
| 173 |
|
|---|
| 174 | <varlistentry>
|
|---|
| 175 | <term><parameter>Randomize the address of the kernel image (KASLR)</parameter></term>
|
|---|
| 176 | <listitem>
|
|---|
| 177 | <para>Enable ASLR for kernel image, to mitigate some attacks based
|
|---|
| 178 | on fixed addresses of sensitive data or code in the kernel.</para>
|
|---|
| 179 | </listitem>
|
|---|
| 180 | </varlistentry>
|
|---|
| 181 |
|
|---|
| 182 | <varlistentry>
|
|---|
| 183 | <term>
|
|---|
| 184 | <parameter>
|
|---|
| 185 | Compile the kernel with warnings as errors
|
|---|
| 186 | </parameter>
|
|---|
| 187 | </term>
|
|---|
| 188 | <listitem>
|
|---|
| 189 | <para>This may cause building failure if the compiler and/or
|
|---|
| 190 | configuration are different from those of the kernel
|
|---|
| 191 | developers.</para>
|
|---|
| 192 | </listitem>
|
|---|
| 193 | </varlistentry>
|
|---|
| 194 |
|
|---|
| 195 | <varlistentry>
|
|---|
| 196 | <term>
|
|---|
| 197 | <parameter>
|
|---|
| 198 | Enable kernel headers through /sys/kernel/kheaders.tar.xz
|
|---|
| 199 | </parameter>
|
|---|
| 200 | </term>
|
|---|
| 201 | <listitem>
|
|---|
| 202 | <para>This will require <command>cpio</command> building the kernel.
|
|---|
| 203 | <command>cpio</command> is not installed by LFS.</para>
|
|---|
| 204 | </listitem>
|
|---|
| 205 | </varlistentry>
|
|---|
| 206 |
|
|---|
| 207 | <varlistentry>
|
|---|
| 208 | <term>
|
|---|
| 209 | <parameter>
|
|---|
| 210 | Configure standard kernel features (expert users)
|
|---|
| 211 | </parameter>
|
|---|
| 212 | </term>
|
|---|
| 213 | <listitem>
|
|---|
| 214 | <para>This will make some options show up in the configuration
|
|---|
| 215 | interface but changing those options may be dangerous. Do not use
|
|---|
| 216 | this unless you know what you are doing.</para>
|
|---|
| 217 | </listitem>
|
|---|
| 218 | </varlistentry>
|
|---|
| 219 |
|
|---|
| 220 | <varlistentry>
|
|---|
| 221 | <term><parameter>Strong Stack Protector</parameter></term>
|
|---|
| 222 | <listitem>
|
|---|
| 223 | <para>Enable SSP for the kernel. We've enabled it for the entire
|
|---|
| 224 | userspace with <parameter>--enable-default-ssp</parameter>
|
|---|
| 225 | configuring GCC, but the kernel does not use GCC default setting
|
|---|
| 226 | for SSP. We enable it explicitly here.</para>
|
|---|
| 227 | </listitem>
|
|---|
| 228 | </varlistentry>
|
|---|
| 229 |
|
|---|
| 230 | <varlistentry>
|
|---|
| 231 | <term><parameter>Support for uevent helper</parameter></term>
|
|---|
| 232 | <listitem>
|
|---|
| 233 | <para>Having this option set may interfere with device
|
|---|
| 234 | management when using Udev.</para>
|
|---|
| 235 | </listitem>
|
|---|
| 236 | </varlistentry>
|
|---|
| 237 |
|
|---|
| 238 | <varlistentry>
|
|---|
| 239 | <term><parameter>Maintain a devtmpfs</parameter></term>
|
|---|
| 240 | <listitem>
|
|---|
| 241 | <para>This will create automated device nodes which are populated by the
|
|---|
| 242 | kernel, even without Udev running. Udev then runs on top of this,
|
|---|
| 243 | managing permissions and adding symlinks. This configuration
|
|---|
| 244 | item is required for all users of Udev.</para>
|
|---|
| 245 | </listitem>
|
|---|
| 246 | </varlistentry>
|
|---|
| 247 |
|
|---|
| 248 | <varlistentry>
|
|---|
| 249 | <term><parameter>Automount devtmpfs at /dev</parameter></term>
|
|---|
| 250 | <listitem>
|
|---|
| 251 | <para>This will mount the kernel view of the devices on /dev
|
|---|
| 252 | upon switching to root filesystem just before starting
|
|---|
| 253 | init.</para>
|
|---|
| 254 | </listitem>
|
|---|
| 255 | </varlistentry>
|
|---|
| 256 |
|
|---|
| 257 | <varlistentry>
|
|---|
| 258 | <term><parameter>Enable the generic EFI decompressor</parameter></term>
|
|---|
| 259 | <listitem>
|
|---|
| 260 | <para>Create the bootable image as an EFI application that carries
|
|---|
| 261 | the actual kernel image in compressed form. It can make the
|
|---|
| 262 | bootable image 50% smaller.</para>
|
|---|
| 263 | </listitem>
|
|---|
| 264 | </varlistentry>
|
|---|
| 265 |
|
|---|
| 266 | <varlistentry>
|
|---|
| 267 | <term><parameter>Framebuffer Console support</parameter></term>
|
|---|
| 268 | <listitem>
|
|---|
| 269 | <para>This is needed to display the Linux console on a frame
|
|---|
| 270 | buffer device. To allow the kernel to print debug messages at an
|
|---|
| 271 | early boot stage, it shouldn't be built as a kernel module
|
|---|
| 272 | unless an initramfs will be used. And, if
|
|---|
| 273 | <option>CONFIG_DRM</option> (Direct Rendering Manager) is enabled,
|
|---|
| 274 | it's likely <option>CONFIG_DRM_FBDEV_EMULATION</option> (Enable
|
|---|
| 275 | legacy fbdev support for your modesetting driver) should be
|
|---|
| 276 | enabled as well.</para>
|
|---|
| 277 | </listitem>
|
|---|
| 278 | </varlistentry>
|
|---|
| 279 |
|
|---|
| 280 | </variablelist>
|
|---|
| 281 |
|
|---|
| 282 | <para>Alternatively, <command>make oldconfig</command> may be more
|
|---|
| 283 | appropriate in some situations. See the <filename>README</filename>
|
|---|
| 284 | file for more information.</para>
|
|---|
| 285 |
|
|---|
| 286 | <para>If desired, skip kernel configuration by copying the kernel
|
|---|
| 287 | config file, <filename>.config</filename>, from the host system
|
|---|
| 288 | (assuming it is available) to the unpacked <filename
|
|---|
| 289 | class="directory">linux-&linux-version;</filename> directory. However,
|
|---|
| 290 | we do not recommend this option. It is often better to explore all the
|
|---|
| 291 | configuration menus and create the kernel configuration from
|
|---|
| 292 | scratch.</para>
|
|---|
| 293 |
|
|---|
| 294 | <para>Compile the kernel image and modules:</para>
|
|---|
| 295 |
|
|---|
| 296 | <screen><userinput remap="make">make</userinput></screen>
|
|---|
| 297 |
|
|---|
| 298 | <para>If using kernel modules, module configuration in <filename
|
|---|
| 299 | class="directory">/etc/modprobe.d</filename> may be required.
|
|---|
| 300 | Information pertaining to modules and kernel configuration is
|
|---|
| 301 | located in <xref linkend="ch-config-udev"/> and in the kernel
|
|---|
| 302 | documentation in the <filename
|
|---|
| 303 | class="directory">linux-&linux-version;/Documentation</filename> directory.
|
|---|
| 304 | Also, <filename>modprobe.d(5)</filename> may be of interest.</para>
|
|---|
| 305 |
|
|---|
| 306 | <para>Unless module support has been disabled in the kernel configuration,
|
|---|
| 307 | install the modules with:</para>
|
|---|
| 308 |
|
|---|
| 309 | <screen><userinput remap="install">make modules_install</userinput></screen>
|
|---|
| 310 |
|
|---|
| 311 | <para>After kernel compilation is complete, additional steps are
|
|---|
| 312 | required to complete the installation. Some files need to be copied to
|
|---|
| 313 | the <filename class="directory">/boot</filename> directory.</para>
|
|---|
| 314 |
|
|---|
| 315 | <caution>
|
|---|
| 316 | <para>If you've decided to use a separate &boot-dir; partition for the
|
|---|
| 317 | LFS system (maybe sharing a &boot-dir; partition with the host
|
|---|
| 318 | distro) , the files copied below should go there. The easiest way to
|
|---|
| 319 | do that is to create the entry for &boot-dir; in &fstab; first (read
|
|---|
| 320 | the previous section for details), then issue the following command
|
|---|
| 321 | as the &root; user in the
|
|---|
| 322 | <emphasis>chroot environment</emphasis>:</para>
|
|---|
| 323 |
|
|---|
| 324 | <screen role="nodump"><userinput>mount /boot</userinput></screen>
|
|---|
| 325 |
|
|---|
| 326 | <para>The path to the device node is omitted in the command because
|
|---|
| 327 | <command>mount</command> can read it from &fstab;.</para>
|
|---|
| 328 | </caution>
|
|---|
| 329 |
|
|---|
| 330 | <para>The path to the kernel image may vary depending on the platform being
|
|---|
| 331 | used. The filename below can be changed to suit your taste, but the stem of
|
|---|
| 332 | the filename should be <emphasis>vmlinuz</emphasis> to be compatible with
|
|---|
| 333 | the automatic setup of the boot process described in the next section. The
|
|---|
| 334 | following command assumes a LoongArch platform with an EFI boot loader
|
|---|
| 335 | (for example, GRUB built in &ch-final;):</para>
|
|---|
| 336 |
|
|---|
| 337 | <screen><userinput remap="install">cp -iv arch/loongarch/boot/vmlinuz.efi /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>
|
|---|
| 338 |
|
|---|
| 339 | <para><filename>System.map</filename> is a symbol file for the kernel.
|
|---|
| 340 | It maps the function entry points of every function in the kernel API,
|
|---|
| 341 | as well as the addresses of the kernel data structures for the running
|
|---|
| 342 | kernel. It is used as a resource when investigating kernel problems.
|
|---|
| 343 | Issue the following command to install the map file:</para>
|
|---|
| 344 |
|
|---|
| 345 | <screen><userinput remap="install">cp -iv System.map /boot/System.map-&linux-version;</userinput></screen>
|
|---|
| 346 |
|
|---|
| 347 | <para>The kernel configuration file <filename>.config</filename>
|
|---|
| 348 | produced by the <command>make menuconfig</command> step
|
|---|
| 349 | above contains all the configuration selections for the kernel
|
|---|
| 350 | that was just compiled. It is a good idea to keep this file for future
|
|---|
| 351 | reference:</para>
|
|---|
| 352 |
|
|---|
| 353 | <screen><userinput remap="install">cp -iv .config /boot/config-&linux-version;</userinput></screen>
|
|---|
| 354 |
|
|---|
| 355 | <para>Install the documentation for the Linux kernel:</para>
|
|---|
| 356 |
|
|---|
| 357 | <screen><userinput remap="install">cp -r Documentation -T /usr/share/doc/linux-&linux-version;</userinput></screen>
|
|---|
| 358 |
|
|---|
| 359 | <para>It is important to note that the files in the kernel source
|
|---|
| 360 | directory are not owned by <emphasis>root</emphasis>. Whenever a
|
|---|
| 361 | package is unpacked as user <emphasis>root</emphasis> (like we did
|
|---|
| 362 | inside chroot), the files have the user and group IDs of whatever
|
|---|
| 363 | they were on the packager's computer. This is usually not a problem
|
|---|
| 364 | for any other package to be installed because the source tree is
|
|---|
| 365 | removed after the installation. However, the Linux source tree is
|
|---|
| 366 | often retained for a long time. Because of this, there is a chance
|
|---|
| 367 | that whatever user ID the packager used will be assigned to somebody
|
|---|
| 368 | on the machine. That person would then have write access to the kernel
|
|---|
| 369 | source.</para>
|
|---|
| 370 |
|
|---|
| 371 | <note>
|
|---|
| 372 | <para>In many cases, the configuration of the kernel will need to be
|
|---|
| 373 | updated for packages that will be installed later in BLFS. Unlike
|
|---|
| 374 | other packages, it is not necessary to remove the kernel source tree
|
|---|
| 375 | after the newly built kernel is installed.</para>
|
|---|
| 376 |
|
|---|
| 377 | <para>If the kernel source tree is going to be retained, run
|
|---|
| 378 | <command>chown -R 0:0</command> on the <filename
|
|---|
| 379 | class="directory">linux-&linux-version;</filename> directory to ensure
|
|---|
| 380 | all files are owned by user <emphasis>root</emphasis>.</para>
|
|---|
| 381 | </note>
|
|---|
| 382 |
|
|---|
| 383 | <warning>
|
|---|
| 384 | <para>Some kernel documentation recommends creating a symlink from
|
|---|
| 385 | <filename class="symlink">/usr/src/linux</filename> pointing to the kernel
|
|---|
| 386 | source directory. This is specific to kernels prior to the 2.6 series and
|
|---|
| 387 | <emphasis>must not</emphasis> be created on an LFS system as it can cause
|
|---|
| 388 | problems for packages you may wish to build once your base LFS system is
|
|---|
| 389 | complete.</para>
|
|---|
| 390 | </warning>
|
|---|
| 391 |
|
|---|
| 392 | <warning>
|
|---|
| 393 | <para>The headers in the system's <filename
|
|---|
| 394 | class="directory">include</filename> directory (<filename
|
|---|
| 395 | class="directory">/usr/include</filename>) should
|
|---|
| 396 | <emphasis>always</emphasis> be the ones against which Glibc was compiled,
|
|---|
| 397 | that is, the sanitised headers installed in <xref
|
|---|
| 398 | linkend="ch-tools-linux-headers"/>. Therefore, they should
|
|---|
| 399 | <emphasis>never</emphasis> be replaced by either the raw kernel headers
|
|---|
| 400 | or any other kernel sanitized headers.</para>
|
|---|
| 401 | </warning>
|
|---|
| 402 |
|
|---|
| 403 | </sect2>
|
|---|
| 404 |
|
|---|
| 405 | <sect2 id="conf-modprobe" role="configuration">
|
|---|
| 406 | <title>Configuring Linux Module Load Order</title>
|
|---|
| 407 |
|
|---|
| 408 | <indexterm zone="conf-modprobe">
|
|---|
| 409 | <primary sortas="e-/etc/modprobe.d/usb.conf">/etc/modprobe.d/usb.conf</primary>
|
|---|
| 410 | </indexterm>
|
|---|
| 411 |
|
|---|
| 412 | <para>Most of the time Linux modules are loaded automatically, but
|
|---|
| 413 | sometimes it needs some specific direction. The program that loads
|
|---|
| 414 | modules, <command>modprobe</command> or <command>insmod</command>, uses
|
|---|
| 415 | <filename>/etc/modprobe.d/usb.conf</filename> for this purpose. This file
|
|---|
| 416 | needs to be created so that if the USB drivers (ehci_hcd, ohci_hcd and
|
|---|
| 417 | uhci_hcd) have been built as modules, they will be loaded in the correct
|
|---|
| 418 | order; ehci_hcd needs to be loaded prior to ohci_hcd and uhci_hcd in order
|
|---|
| 419 | to avoid a warning being output at boot time.</para>
|
|---|
| 420 |
|
|---|
| 421 | <para>Create a new file <filename>/etc/modprobe.d/usb.conf</filename> by running
|
|---|
| 422 | the following:</para>
|
|---|
| 423 |
|
|---|
| 424 | <screen><userinput>install -v -m755 -d /etc/modprobe.d
|
|---|
| 425 | cat > /etc/modprobe.d/usb.conf << "EOF"
|
|---|
| 426 | <literal># Begin /etc/modprobe.d/usb.conf
|
|---|
| 427 |
|
|---|
| 428 | install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i ohci_hcd ; true
|
|---|
| 429 | install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i uhci_hcd ; true
|
|---|
| 430 |
|
|---|
| 431 | # End /etc/modprobe.d/usb.conf</literal>
|
|---|
| 432 | EOF</userinput></screen>
|
|---|
| 433 |
|
|---|
| 434 | </sect2>
|
|---|
| 435 |
|
|---|
| 436 | <sect2 id="contents-kernel" role="content">
|
|---|
| 437 | <title>Contents of Linux</title>
|
|---|
| 438 |
|
|---|
| 439 | <segmentedlist>
|
|---|
| 440 | <segtitle>Installed files</segtitle>
|
|---|
| 441 | <segtitle>Installed directories</segtitle>
|
|---|
| 442 |
|
|---|
| 443 | <seglistitem>
|
|---|
| 444 | <seg>config-&linux-version;,
|
|---|
| 445 | vmlinuz-&linux-version;-lfs-&version;,
|
|---|
| 446 | and System.map-&linux-version;</seg>
|
|---|
| 447 | <seg>/lib/modules, /usr/share/doc/linux-&linux-version;</seg>
|
|---|
| 448 | </seglistitem>
|
|---|
| 449 | </segmentedlist>
|
|---|
| 450 |
|
|---|
| 451 | <variablelist>
|
|---|
| 452 | <bridgehead renderas="sect3">Short Descriptions</bridgehead>
|
|---|
| 453 | <?dbfo list-presentation="list"?>
|
|---|
| 454 | <?dbhtml list-presentation="table"?>
|
|---|
| 455 |
|
|---|
| 456 | <varlistentry id="config">
|
|---|
| 457 | <term><filename>config-&linux-version;</filename></term>
|
|---|
| 458 | <listitem>
|
|---|
| 459 | <para>Contains all the configuration selections for the kernel</para>
|
|---|
| 460 | <indexterm zone="ch-bootable-kernel config">
|
|---|
| 461 | <primary sortas="e-/boot/config">/boot/config-&linux-version;</primary>
|
|---|
| 462 | </indexterm>
|
|---|
| 463 | </listitem>
|
|---|
| 464 | </varlistentry>
|
|---|
| 465 |
|
|---|
| 466 | <varlistentry id="lfskernel">
|
|---|
| 467 | <term><filename>vmlinuz-&linux-version;-lfs-&version;</filename></term>
|
|---|
| 468 | <listitem>
|
|---|
| 469 | <para>The engine of the Linux system. When turning on the computer,
|
|---|
| 470 | the kernel is the first part of the operating system that gets loaded.
|
|---|
| 471 | It detects and initializes all components of the computer's hardware,
|
|---|
| 472 | then makes these components available as a tree of files to the
|
|---|
| 473 | software and turns a single CPU into a multitasking machine capable
|
|---|
| 474 | of running scores of programs seemingly at the same time</para>
|
|---|
| 475 | <indexterm zone="ch-bootable-kernel lfskernel">
|
|---|
| 476 | <primary sortas="b-lfskernel">lfskernel-&linux-version;</primary>
|
|---|
| 477 | </indexterm>
|
|---|
| 478 | </listitem>
|
|---|
| 479 | </varlistentry>
|
|---|
| 480 |
|
|---|
| 481 | <varlistentry id="System.map">
|
|---|
| 482 | <term><filename>System.map-&linux-version;</filename></term>
|
|---|
| 483 | <listitem>
|
|---|
| 484 | <para>A list of addresses and symbols; it maps the entry points and
|
|---|
| 485 | addresses of all the functions and data structures in the
|
|---|
| 486 | kernel</para>
|
|---|
| 487 | <indexterm zone="ch-bootable-kernel System.map">
|
|---|
| 488 | <primary sortas="e-/boot/System.map">/boot/System.map-&linux-version;</primary>
|
|---|
| 489 | </indexterm>
|
|---|
| 490 | </listitem>
|
|---|
| 491 | </varlistentry>
|
|---|
| 492 |
|
|---|
| 493 | </variablelist>
|
|---|
| 494 |
|
|---|
| 495 | </sect2>
|
|---|
| 496 |
|
|---|
| 497 | </sect1>
|
|---|
