Changes in chapter10/kernel.xml [58962f7:f976691]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter10/kernel.xml
r58962f7 rf976691 142 142 [*] Strong Stack Protector [CONFIG_STACKPROTECTOR_STRONG] 143 143 Device Drivers ---> 144 Firmware Drivers --->145 EFI (Extensible Firmware Interface) Support --->146 [*] Enable the generic EFI decompressor [CONFIG_EFI_ZBOOT]147 144 Graphics support ---> 148 145 Frame buffer Devices ---> … … 167 164 [*] Control Group support [CONFIG_CGROUPS] ---> 168 165 [*] Memory controller [CONFIG_MEMCG] 169 [ ] Enable deprecated sysfs features to support old userspace tools [CONFIG_SYSFS_DEPRECATED]170 166 [ ] Configure standard kernel features (expert users) [CONFIG_EXPERT] 171 167 General architecture-dependent options ---> … … 186 182 Firmware Drivers ---> 187 183 [*] Export DMI identification via sysfs to userspace [CONFIG_DMIID] 188 EFI (Extensible Firmware Interface) Support --->189 [*] Enable the generic EFI decompressor [CONFIG_EFI_ZBOOT]190 184 Graphics support ---> 191 185 Frame buffer Devices ---> … … 198 192 [*] Tmpfs POSIX Access Control Lists [CONFIG_TMPFS_POSIX_ACL]</screen> 199 193 194 <para>Enable some additional features if you are building a 64-bit 195 system. If you are using menuconfig, enable them in the order of 196 <parameter>CONFIG_PCI_MSI</parameter> first, then 197 <parameter>CONFIG_IRQ_REMAP</parameter>, at last 198 <parameter>CONFIG_X86_X2APIC</parameter> because an option only 199 shows up after its dependencies are selected.</para> 200 201 <screen role="nodump">Processor type and features ---> 202 [*] Support x2apic [CONFIG_X86_X2APIC] 203 Device Drivers ---> 204 [*] PCI Support ---> [CONFIG_PCI] 205 [*] Message Signaled Interrupts (MSI and MSI-X) [CONFIG_PCI_MSI] 206 [*] IOMMU Hardware Support ---> [CONFIG_IOMMU_SUPPORT] 207 [*] Support for Interrupt Remapping [CONFIG_IRQ_REMAP]</screen> 208 209 <para>If you are building a 32-bit system running on a hardware 210 with RAM more than 4GB, adjust the configuration so the kernel will 211 be able to use up to 64GB physical RAM:</para> 212 213 <screen role="nodump">Processor type and features ---> 214 High Memory Support ---> 215 (X) 64GB [CONFIG_HIGHMEM64G]</screen> 216 200 217 <para>If the partition for the LFS system is in a NVME SSD (i. e. the 201 218 device node for the partition is <filename>/dev/nvme*</filename> … … 310 327 upon switching to root filesystem just before starting 311 328 init.</para> 312 </listitem>313 </varlistentry>314 315 <varlistentry>316 <term><parameter>Enable the generic EFI decompressor</parameter></term>317 <listitem>318 <para>Create the bootable image as an EFI application that carries319 the actual kernel image in compressed form. It can make the320 bootable image 50% smaller.</para>321 329 </listitem> 322 330 </varlistentry> … … 336 344 </varlistentry> 337 345 346 <varlistentry> 347 <term><parameter>Support x2apic</parameter></term> 348 <listitem> 349 <para>Support running the interrupt controller of 64-bit x86 350 processors in x2APIC mode. x2APIC may be enabled by firmware on 351 64-bit x86 systems, and a kernel without this option enabled will 352 panic on boot if x2APIC is enabled by firmware. This option has 353 has no effect, but also does no harm if x2APIC is disabled by the 354 firmware.</para> 355 </listitem> 356 </varlistentry> 357 338 358 </variablelist> 339 359 … … 390 410 the filename should be <emphasis>vmlinuz</emphasis> to be compatible with 391 411 the automatic setup of the boot process described in the next section. The 392 following command assumes a LoongArch platform with an EFI boot loader 393 (for example, GRUB built in &ch-final;):</para> 394 395 <screen><userinput remap="install">cp -iv arch/loongarch/boot/vmlinuz.efi /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen> 412 following command assumes an x86 architecture:</para> 413 414 <screen><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen> 396 415 397 416 <para><filename>System.map</filename> is a symbol file for the kernel.
Note:
See TracChangeset
for help on using the changeset viewer.