- Timestamp:
- 03/10/2023 11:30:10 PM (19 months ago)
- Branches:
- multilib, xry111/multilib
- Children:
- 31e6ccb2
- Parents:
- 2858f02 (diff), 0bf56aad (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter10/kernel.xml
r2858f02 rdb84777 90 90 91 91 <para>For general information on kernel configuration see <ulink 92 url="&hints-root;kernel-configuration.txt"/>. BLFS has some information 93 regarding particular kernel configuration requirements of packages outside 94 of LFS at <ulink 95 url="&blfs-book;longindex.html#kernel-config-index"/>. Additional 92 url="&hints-root;kernel-configuration.txt"/>. Additional 96 93 information about configuring and building the kernel can be found at 97 <ulink url="http://www.kroah.com/lkn/"/> 98 99 < caution>94 <ulink url="http://www.kroah.com/lkn/"/>.</para> 95 96 <note> 100 97 <para>A good starting place for setting up the kernel configuration is to 101 run <command>make localmodconfig</command>. If the host kernel version 102 is not too different from the version of the kernel you are building, 103 this will set the base configuration to a good state similar to what 104 the host uses. Another possibility is to use <command>make 105 localyesconfig</command>, which does the same except everything is built 106 into the kernel.</para> 107 108 <para>Do not disable any option enabled by <command>make 109 localmodconfig</command> unless the following notes explicitly make it 110 disabled or you really know what you are doing.</para> 111 </caution> 112 113 <note> 114 <para>Another possibility is to run <command>make defconfig</command>, 115 which creates a more generic configuration for your architecture. You 116 may then have to disable drivers for hardware you do not have if 117 you want to reduce the kernel size.</para> 118 </note> 119 120 <note> 98 run <command>make defconfig</command>. This will set the base 99 configuration to a good state that takes your current system architecture 100 into account.</para> 101 121 102 <para>Be sure to enable/disable/set the following features or the system might 122 103 not work correctly or boot at all:</para> … … 196 177 [*] IOMMU Hardware Support ---> [CONFIG_IOMMU_SUPPORT] 197 178 [*] Support for Interrupt Remapping [CONFIG_IRQ_REMAP]</screen> 179 180 <para>If you are building a 32-bit system running on a hardware 181 with RAM more than 4GB, adjust the configuration so the kernel will 182 be able to use up to 64GB physical RAM:</para> 183 184 <screen role="nodump">Processor type and features ---> 185 High Memory Support ---> 186 (X) 64GB [CONFIG_HIGHMEM64G]</screen> 187 188 <para>If the partition for the LFS system is in a NVME SSD (i. e. the 189 device node for the parition is <filename>/dev/nvme*</filename> 190 instead of <filename>/dev/sd*</filename>), enable NVME support or 191 the LFS system won't boot:</para> 192 193 <screen role="nodump">Device Drivers ---> 194 NVME Support ---> 195 <*> NVM Express block device [CONFIG_BLK_DEV_NVME]</screen> 198 196 </note> 199 197 … … 203 201 </note> 204 202 205 <para revision="sysv">There are several other options that may be desired203 <para>There are several other options that may be desired 206 204 depending on the requirements for the system. For a list of options needed 207 205 for BLFS packages, see the <ulink 208 206 url="&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index">BLFS 209 Index of Kernel Settings</ulink> 210 (&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index).</para> 207 Index of Kernel Settings</ulink>.</para> 211 208 212 209 <note> … … 214 211 LFS system with it, you should adjust some kernel configuration 215 212 following <ulink url="&blfs-book;postlfs/grub-setup.html#uefi-kernel"> 216 the BLFS page</ulink>.</para> 213 the BLFS page</ulink> <emphasis role='bold'>even if you'll use the 214 UEFI bootloader from the host distro</emphasis>.</para> 217 215 </note> 218 216 … … 355 353 processors in x2APIC mode. x2APIC may be enabled by firmware on 356 354 64-bit x86 systems, and a kernel without this option enabled will 357 panic on boot if x2APIC is enabled by firmware. This option 355 panic on boot if x2APIC is enabled by firmware. This option has 358 356 has no effect, but also does no harm if x2APIC is disabled by the 359 357 firmware.</para>
Note:
See TracChangeset
for help on using the changeset viewer.