[lfs] branch trunk updated: kernel: add HIGHMEM4G for 32-bit

"Git Owner" ([email protected] via lfs-book Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.book
Message-ID <176846129827.27228.2476898137962646950@rivendell.linuxfromscratch.org>
This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch trunk
in repository lfs.

The following commit(s) were added to refs/heads/trunk by this push:
     new e3bd8b4a0 kernel: add HIGHMEM4G for 32-bit
e3bd8b4a0 is described below

commit e3bd8b4a059a985342c762ee3e333360c8e28078
Author: Xi Ruoyao <[email protected]>
AuthorDate: Thu Jan 15 14:54:15 2026 +0800

    kernel: add HIGHMEM4G for 32-bit
    
    Without this in 32-bit kernel you can only use ~800 MiB of RAM.  Sigh.
---
 chapter10/kernel.xml            | 7 +++++++
 chapter10/kernel/highmem.toml   | 1 +
 chapter10/kernel/highmem.xml    | 7 +++++++
 chapter10/kernel/kernel.version | 2 +-
 chapter10/kernel/systemd.xml    | 3 +--
 5 files changed, 17 insertions(+), 3 deletions(-)

diff --git a/chapter10/kernel.xml b/chapter10/kernel.xml
index 0c4739167..66e58f46b 100644
--- a/chapter10/kernel.xml
+++ b/chapter10/kernel.xml
@@ -151,6 +151,13 @@
       <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
         href="kernel/x2apic.xml"/>
 
+      <para>If you are building a 32-bit system,
+      adjust the configuration so the kernel will
+      be able to use up to 4GB physical RAM:</para>
+
+      <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
+        href="kernel/highmem.xml"/>
+
       <para>If the partition for the LFS system is in a NVME SSD (i. e. the
       device node for the partition is <filename>/dev/nvme*</filename>
       instead of <filename>/dev/sd*</filename>), enable NVME support or
diff --git a/chapter10/kernel/highmem.toml b/chapter10/kernel/highmem.toml
new file mode 100644
index 000000000..93e66af3b
--- /dev/null
+++ b/chapter10/kernel/highmem.toml
@@ -0,0 +1 @@
+HIGHMEM4G='*'
diff --git a/chapter10/kernel/highmem.xml b/chapter10/kernel/highmem.xml
new file mode 100644
index 000000000..03b228e59
--- /dev/null
+++ b/chapter10/kernel/highmem.xml
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
+<!-- Automatically generated by kernel-config.py
+     DO NOT EDIT! -->
+<screen role="nodump"><emphasis role='blue'>P</emphasis>rocessor type and features ---&gt;
+  [*] H<emphasis role='blue'>i</emphasis>gh Memory Support                                            [HIGHMEM4G]</screen>
diff --git a/chapter10/kernel/kernel.version b/chapter10/kernel/kernel.version
index 954ea4957..ab1d61511 100644
--- a/chapter10/kernel/kernel.version
+++ b/chapter10/kernel/kernel.version
@@ -1 +1 @@
-6.16.1
+6.18.2
diff --git a/chapter10/kernel/systemd.xml b/chapter10/kernel/systemd.xml
index 5a598b764..35d48dd16 100644
--- a/chapter10/kernel/systemd.xml
+++ b/chapter10/kernel/systemd.xml
@@ -38,8 +38,7 @@
                                                            ...  [DEVTMPFS_MOUNT]
     <emphasis role='blue'>F</emphasis>irmware loader ---&gt;
       &lt; /*&gt; <emphasis role='blue'>F</emphasis>irmware loading facility                                [FW_LOADER]
-      [ ]     <emphasis role='blue'>E</emphasis>nable the firmware sysfs fallback mechanism
-                                                    ...  [FW_LOADER_USER_HELPER]
+      [ ]   <emphasis role='blue'>E</emphasis>nable the firmware sysfs fallback mechanism [FW_LOADER_USER_HELPER]
   <emphasis role='blue'>F</emphasis>irmware Drivers ---&gt;
     [*] <emphasis role='blue'>E</emphasis>xport DMI identification via sysfs to userspace                 [DMIID]
     [*] M<emphasis role='blue'>a</emphasis>rk VGA/VBE/EFI FB as generic system framebuffer       [SYSFB_SIMPLEFB]

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.