lfs/chapter10/kernel/sysv.toml

WERROR=' '
PSI='*'
PSI_DEFAULT_DISABLED=' '
IKHEADERS=' '
CGROUPS='*'
MEMCG='*'
EXPERT=' '
RELOCATABLE='*'
RANDOMIZE_BASE='*'
STACKPROTECTOR='*'
STACKPROTECTOR_STRONG='*'
UEVENT_HELPER=' '
DEVTMPFS='*'
DEVTMPFS_MOUNT='*'
SYSFB_SIMPLEFB='*'
DRM='*'
DRM_PANIC='*'
DRM_PANIC_SCREEN='kmsg'
DRM_FBDEV_EMULATION='*'
DRM_SIMPLEDRM='*'
FRAMEBUFFER_CONSOLE='*'

revision='sysv'
kernel: Use new kernel configuration rendering method Import kernel-config infrastructure from BLFS and use it for kernel configuration. Note that kernel-config.py is slightly different from BLFS: we need role="nodump" for <screen> here. 2023-07-31 17:08:56 +01:00			`WERROR=' '`
			`PSI='*'`
			`PSI_DEFAULT_DISABLED=' '`
			`IKHEADERS=' '`
			`CGROUPS='*'`
			`MEMCG='*'`
			`EXPERT=' '`
			`RELOCATABLE='*'`
			`RANDOMIZE_BASE='*'`
			`STACKPROTECTOR='*'`
			`STACKPROTECTOR_STRONG='*'`
			`UEVENT_HELPER=' '`
			`DEVTMPFS='*'`
			`DEVTMPFS_MOUNT='*'`
drm-panic: kernel: Enable SimpleDRM Currently on a LFS system booted via legacy BIOS (intead of UEFI), the users can make two different configurations: 1. The DRM driver for the GPU is built as a module. Then before the module is loaded (i.e. the root fs is properly mounted) the kernel messages are displayed via the VGA console. 2. The DRM driver for the GPU is built into the kernel image. Then the kernel messages are displayed via the DRM-emulated framebuffer console since a very early stage (before the root fs is properly mounted). When the system is booted via UEFI, we use SimpleDRM on the EFI framebuffer for displaying kernel messages, thus it's always the case 2. Both are not good for diagnostic in case the root fs cannot be mounted properly (it's very frequent on lfs-support): - With 1 the VGA console can only fit 80x24 characters, so the relevent information is often flushed away. - With 2 the panic message is often displayed improperly when a DRM driver is running. The "DRM panic" feature introduced since Linux 6.11 (but it'll only become usable for LFS since Linux 6.12) can fix the case 2, while case 1 just cannot be fixed. So start to make LFS booted via legacy BIOS to use method 2 now, then we can enable DRM panic and fix this long-standing issue. 2024-10-30 11:38:59 +00:00			`SYSFB_SIMPLEFB='*'`
			`DRM='*'`
drm-panic: kernel: Enable DRM_PANIC Since the previous commit, we've ensured the kernel displaying via DRM even in the early stage. Now enable DRM_PANIC so the kernel will correctly show the last lines of the kernel messages in case a panic happens. Tested with an incorrect root= line in 3 configurations: - A QEMU VM booted via BIOS - A real machine booted via BIOS - A real machine booted via UEFI And in all configurations the panic message is correctly dumped. In 1024x768 we can get 48 lines (twice of 24 lines in VGA console). 2024-12-01 09:30:51 +00:00			`DRM_PANIC='*'`
			`DRM_PANIC_SCREEN='kmsg'`
drm-panic: kernel: Enable SimpleDRM Currently on a LFS system booted via legacy BIOS (intead of UEFI), the users can make two different configurations: 1. The DRM driver for the GPU is built as a module. Then before the module is loaded (i.e. the root fs is properly mounted) the kernel messages are displayed via the VGA console. 2. The DRM driver for the GPU is built into the kernel image. Then the kernel messages are displayed via the DRM-emulated framebuffer console since a very early stage (before the root fs is properly mounted). When the system is booted via UEFI, we use SimpleDRM on the EFI framebuffer for displaying kernel messages, thus it's always the case 2. Both are not good for diagnostic in case the root fs cannot be mounted properly (it's very frequent on lfs-support): - With 1 the VGA console can only fit 80x24 characters, so the relevent information is often flushed away. - With 2 the panic message is often displayed improperly when a DRM driver is running. The "DRM panic" feature introduced since Linux 6.11 (but it'll only become usable for LFS since Linux 6.12) can fix the case 2, while case 1 just cannot be fixed. So start to make LFS booted via legacy BIOS to use method 2 now, then we can enable DRM panic and fix this long-standing issue. 2024-10-30 11:38:59 +00:00			`DRM_FBDEV_EMULATION='*'`
			`DRM_SIMPLEDRM='*'`
			`FRAMEBUFFER_CONSOLE='*'`
kernel: Use new kernel configuration rendering method Import kernel-config infrastructure from BLFS and use it for kernel configuration. Note that kernel-config.py is slightly different from BLFS: we need role="nodump" for <screen> here. 2023-07-31 17:08:56 +01:00
			`revision='sysv'`