From 0b2a86c0fa49104d06bbe78d62faf796abd7cc93 Mon Sep 17 00:00:00 2001 From: LJ <5854483+l-2-j@users.noreply.github.com> Date: Tue, 30 Sep 2025 16:47:50 +0300 Subject: [PATCH 1/2] Fix systemd-boot is EFI driver capable The docs are just fully wrong about systemd-boot not being able to use non-FAT partitions. --- src/content/docs/installation/boot_managers.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/installation/boot_managers.mdx b/src/content/docs/installation/boot_managers.mdx index 107857ef..475ac1f1 100644 --- a/src/content/docs/installation/boot_managers.mdx +++ b/src/content/docs/installation/boot_managers.mdx @@ -61,7 +61,7 @@ If you encounter such issues, consider using `systemd-boot`. /boot filesystem support - FAT12/16/32 only + FAT12/16/32 for /efi, with ext4/Btrfs via EFI drivers for /boot (efifs) FAT natively; ext4/Btrfs via EFI drivers (efifs) Broad filesystem support (ext*, Btrfs, XFS, etc.) FAT12/16/32, ISO9660 for /boot @@ -133,8 +133,8 @@ Part of the systemd family, systemd-boot was created to be as simple as possible #### Cons - No support for BIOS/MBR. - Very barebones: no theming or customization. -- Only able to read boot images on EFI-supported filesystems (FAT12/16/32). -- Cannot find boot images on partitions other than its own ESP. +- Requires manually setting up separate `esp` and `/boot` (XBOOTLDR) partitions with EFI drivers to support filesystems beyond the default supported ones (FAT12/16/32). +- Cannot find boot images on partitions other than its own ESP or the XBOOTLDR partition. - Config is not auto-generated unless configured to do so. - No native support for Btrfs snapshot rollbacks due to requirement to store kernel images on the boot partition rather than the root. - Snapshot booting is possible only with custom setups (not provided by CachyOS). From 5477e4de60dc08717282c644c0a72bce8fed2c9e Mon Sep 17 00:00:00 2001 From: LJ <5854483+l-2-j@users.noreply.github.com> Date: Sun, 5 Oct 2025 18:52:56 +0300 Subject: [PATCH 2/2] Clear up systemd-boot and rEFInd FS support further --- src/content/docs/installation/boot_managers.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/installation/boot_managers.mdx b/src/content/docs/installation/boot_managers.mdx index 475ac1f1..21045f45 100644 --- a/src/content/docs/installation/boot_managers.mdx +++ b/src/content/docs/installation/boot_managers.mdx @@ -61,8 +61,8 @@ If you encounter such issues, consider using `systemd-boot`. /boot filesystem support - FAT12/16/32 for /efi, with ext4/Btrfs via EFI drivers for /boot (efifs) - FAT natively; ext4/Btrfs via EFI drivers (efifs) + According to firmware's support (usually FAT12/16/32); More with EFI drivers + Firmware's,ext2,ext3,ext4,btrfs,ISO-9660,HFS+, and NTFS; More with EFI drivers Broad filesystem support (ext*, Btrfs, XFS, etc.) FAT12/16/32, ISO9660 for /boot @@ -133,7 +133,7 @@ Part of the systemd family, systemd-boot was created to be as simple as possible #### Cons - No support for BIOS/MBR. - Very barebones: no theming or customization. -- Requires manually setting up separate `esp` and `/boot` (XBOOTLDR) partitions with EFI drivers to support filesystems beyond the default supported ones (FAT12/16/32). +- If using a boot filesystem beyond the firmware's default ones (FAT12/16/32), then separate ESP and [XBOOTLDR](https://wiki.archlinux.org/title/Systemd-boot#Installation_using_XBOOTLDR) partitions & EFI drivers need to be manually added. - Cannot find boot images on partitions other than its own ESP or the XBOOTLDR partition. - Config is not auto-generated unless configured to do so. - No native support for Btrfs snapshot rollbacks due to requirement to store kernel images on the boot partition rather than the root.