Switiching to rEFInd from systemd-boot (w/ brtfs)

so i recently installed endeavourOS on a new machine. I selected encrypted brtfs and systemd-boot in the installation process. Now i want to switch from systemd-boot to rEFInd and i have some general questions since it is not working as expected.

Basically i read various pages and the forum regarding this ([How to install rEFInd?](https://discovery.endeavouros.com/grub-and-refind/how-to-install-refind/2021/03/, The rEFInd Boot Manager - rodsbooks), however the easy method did not seem to work for me out of the box and for the manual setup i lack some understanding of what is going on.

At the current state rEFInd only shows the systemd-boot option which was initially installed. Of course i want to directly boot into the latest achlinux kernel and maybe have another option for the lts-linux kernel, in the future i want to use the brtfs snapshot support by rEFInd and maybe want to try out enabling secure boot - but one step after another.

What i did:
installed refind and refind-brtfs
first i tried:
sudo refind-install
that did not worked - it looked like it run through without errors but i did not end up with my boot options, so i read more inside the manual and tried (for later possibility of secure boot and stating the ESP parition directly)
sudo refind-install --localkeys --encryptkeys --usedefault /dev/nvme0n1p1
that did not help though, afterwards i ran
sudo mkrlconf --force

sudo efibootmgr --create --disk /dev/nvme0n1p1 --loader /efi/EFI/refind/refind_x64.efi --label "rEFInd Boot Manager" --unicode

i also tried to add a manual entry inside the global refind.conf which had no effect and i commented out the extra_kernel_version_strings linux-lts,linux line

here is my refind.conf:

# refind.conf
# Configuration file for the rEFInd boot menu

# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout). Setting it to -1 causes
# an immediate boot to the default OS *UNLESS* a keypress is in the buffer
# when rEFInd launches, in which case that keypress is interpreted as a
# shortcut key. If no matching shortcut is found, rEFInd displays its
# menu with no timeout.
timeout 20

# Set the logging level. When set to 0, rEFInd does not log its actions.
# When set to 1 or above, rEFInd creates a file called refind.log in
# its home directory on the ESP and records information about what it's
# doing. Higher values record more information, up to a maximum of 4.
# This token should be left at the default of 0 except when debugging
# problems.
# Default value is 0
#log_level 1

# Normally, when the timeout period has passed, rEFInd boots the
# default_selection. If the following option is uncommented, though,
# rEFInd will instead attempt to shut down the computer.
# recent UEFI-based PCs are most likely to work with this feature.
# Default value is true

# Whether to store rEFInd's rEFInd-specific variables in NVRAM (1, true,
# or on) or in files in the "vars" subdirectory of rEFInd's directory on
# disk (0, false, or off). Using NVRAM works well with most computers;
# however, it increases wear on the motherboard's NVRAM, and if the EFI
# is buggy or the NVRAM is old and worn out, it may not work at all.
# Storing variables on disk is a viable alternative in such cases, or
# if you want to minimize wear and tear on the NVRAM; however, it won't
# work if rEFInd is stored on a filesystem that's read-only to the EFI
# (such as an HFS+ volume), and it increases the risk of filesystem
# damage. Note that this option affects ONLY rEFInd's own variables,
# such as the PreviousBoot, HiddenTags, HiddenTools, and HiddenLegacy
# variables. It does NOT affect Secure Boot or other non-rEFInd
# variables.
# Default is true
use_nvram false

# Screen saver timeout; the screen blanks after the specified number of
# seconds with no keyboard input. The screen returns after most keypresses
# (unfortunately, not including modifier keys such as Shift, Control, Alt,
# or Option). Setting a value of "-1" causes rEFInd to start up with its
# screen saver active. The default is 0, which disables the screen saver.
#screensaver 300

# Hide user interface elements for personal preference or to increase
# security:
#  banner      - the rEFInd title banner (built-in or loaded via "banner")
#  label       - boot option text label in the menu
#  singleuser  - remove the submenu options to boot macOS in single-user
#                or verbose modes; affects ONLY macOS
#  safemode    - remove the submenu option to boot macOS in "safe mode"
#  hwtest      - the submenu option to run Apple's hardware test
#  arrows      - scroll arrows on the OS selection tag line
#  hints       - brief command summary in the menu
#  editor      - the options editor (+, F2, or Insert on boot options menu)
#  badges      - device-type badges for boot options
#  all         - all of the above
# Default is none of these (all elements active)
#hideui singleuser
#hideui all

# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Icon files may be in any supported format -- ICNS (*.icns), BMP (*.bmp),
# PNG (*.png), or JPEG (*.jpg or *.jpeg); however, rEFInd's BMP and JPEG
# implementations do not support transparency, which is highly desirable
# in icons.
# Default is "icons".
#icons_dir myicons
#icons_dir icons/snowy

# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported, as well as PNG and JPEG
# images. (ICNS images can also be used, but ICNS has limitations that
# make it a poor choice for this purpose.) PNG and JPEG support is
# limited by the underlying libraries; some files, like progressive JPEGs,
# will not work.
#banner hostname.bmp
#banner mybanner.jpg
#banner icons/snowy/banner-snowy.png

# Specify how to handle banners that aren't exactly the same as the screen
# size:
#  noscale     - Crop if too big, show with border if too small
#  fillscreen  - Fill the screen
# Default is noscale
#banner_scale fillscreen

# Icon sizes. All icons are square, so just one value is specified. The
# big icons are used for OS selectors in the first row and the small
# icons are used for tools on the second row. Drive-type badges are 1/4
# the size of the big icons. Legal values are 32 and above. If the icon
# files do not hold icons of the proper size, the icons are scaled to
# the specified size. The default values are 48 and 128 for small and
# big icons, respectively.
#small_icon_size 96
#big_icon_size 256

# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons. If an image other
# than the optimal size is specified, it will be scaled in a way that may
# be ugly.
# Like the banner option above, these options take a filename of an
# uncompressed BMP, PNG, JPEG, or ICNS image file with a color depth of
# 24, 8, 4, or 1 bits. The PNG or ICNS format is required if you need
# transparency support (to let you "see through" to a full-screen banner).
#selection_big   selection-big.bmp
#selection_small selection-small.bmp

# Set the font to be used for all textual displays in graphics mode.
# For best results, the font must be a PNG file with alpha channel
# transparency. It must contain ASCII characters 32-126 (space through
# tilde), inclusive, plus a glyph to be displayed in place of characters
# outside of this range, for a total of 96 glyphs. Only monospaced fonts
# are supported. Fonts may be of any size, although large fonts can
# produce display irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#font myfont.png

# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.

# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#textmode 2

# Set the screen's video resolution. Pass this option one of the following:
#  * two integer values, corresponding to the X and Y resolutions
#  * one integer value, corresponding to a GOP (UEFI) video mode
#  * the string "max", which sets the maximum available resolution
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#resolution 1024 768
#resolution 1440 900
#resolution 3
#resolution max

# Enable touch screen support. If active, this feature enables use of
# touch screen controls (as on tablets). Note, however, that not all
# tablets' EFIs provide the necessary underlying support, so this
# feature may not work for you. If it does work, you should be able
# to launch an OS or tool by touching it. In a submenu, touching
# anywhere launches the currently-selection item; there is, at present,
# no way to select a specific submenu item. This feature is mutually
# exclusive with the enable_mouse feature. If both are uncommented,
# the one read most recently takes precedence.

# Enable mouse support. If active, this feature enables use of the
# computer's mouse. Note, however, that not all computers' EFIs
# provide the necessary underlying support, so this feature may not
# work for you. If it does work, you should be able to launch an
# OS or tool by clicking it with the mouse pointer. This feature
# is mutually exclusive with the enable_touch feature. If both
# are uncommented, the one read most recently takes precedence.

# Size of the mouse pointer, in pixels, per side.
# Default is 16
#mouse_size 16

# Speed of mouse tracking. Higher numbers equate to faster
# mouse movement. This option requires that enable_mouse be
# uncommented.
# Legal values are between 1 and 32. Default is 4.
#mouse_speed 4

# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except macOS. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
#   osx     - macOS
#   linux   - A Linux kernel with EFI stub loader
#   elilo   - The ELILO boot loader
#   grub    - The GRUB (Legacy or 2) boot loader
#   windows - Microsoft Windows
# Default value: osx
#use_graphics_for osx,linux

# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
#  shell            - the EFI shell (requires external program; see rEFInd
#                     documentation for details)
#  memtest          - the memtest86 program, in EFI/tools, EFI/memtest86,
#                     EFI/memtest, EFI/tools/memtest86, or EFI/tools/memtest
#  gptsync          - the (dangerous) gptsync.efi utility (requires external
#                     program; see rEFInd documentation for details)
#  gdisk            - the gdisk partitioning program
#  apple_recovery   - boots the Apple Recovery HD partition, if present
#  windows_recovery - boots an OEM Windows recovery tool, if present
#                     (see also the windows_recovery_files option)
#  mok_tool         - makes available the Machine Owner Key (MOK) maintenance
#                     tool, MokManager.efi, used on Secure Boot systems
#  csr_rotate       - adjusts Apple System Integrity Protection (SIP)
#                     policy. Requires "csr_values" to be set.
#  install          - an option to install rEFInd from the current location
#                     to another ESP
#  bootorder        - adjust the EFI's (NOT rEFInd's) boot order
#  about            - an "about this program" option
#  hidden_tags      - manage hidden tags
#  exit             - a tag to exit from rEFInd
#  shutdown         - shuts down the computer (a bug causes this to reboot
#                     many UEFI systems)
#  reboot           - a tag to reboot the computer
#  firmware         - a tag to reboot the computer into the firmware's
#                     user interface (ignored on older computers)
#  fwupdate         - a tag to update the firmware; launches the fwupx64.efi
#                     (or similar) program
#  netboot          - launch the ipxe.efi tool for network (PXE) booting
# Default is shell,memtest,gdisk,apple_recovery,windows_recovery,mok_tool,about,hidden_tags,shutdown,reboot,firmware,fwupdate
# To completely disable scanning for all tools, provide a showtools line
# with no options.
#showtools shell, bootorder, gdisk, memtest, mok_tool, apple_recovery, windows_recovery, about, hidden_tags, reboot, exit, firmware, fwupdate

# Tool binaries to be excluded from the tools line, even if the
# general class is specified in showtools. This enables trimming an
# overabundance of tools, as when you see multiple mok_tool entries
# after installing multiple Linux distributions.
# Just as with dont_scan_files, you can specify a filename alone, a
# full pathname, or a volume identifier (filesystem label, partition
# name, or partition GUID) and a full pathname.
# Default is an empty list (nothing is excluded)
#dont_scan_tools ESP2:/EFI/ubuntu/mmx64.efi,gptsync_x64.efi

# Boot loaders that can launch a Windows restore or emergency system.
# These tend to be OEM-specific.
# Default is LRS_ESP:/EFI/Microsoft/Boot/LrsBootmgr.efi
#windows_recovery_files LRS_ESP:/EFI/Microsoft/Boot/LrsBootmgr.efi

# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#scan_driver_dirs EFI/tools/drivers,drivers

# Which types of boot loaders to search, and in what order to display them:
#  internal      - internal EFI disk-based boot loaders
#  external      - external EFI disk-based boot loaders
#  optical       - EFI optical discs (CD, DVD, etc.)
#  netboot       - EFI network (PXE) boot options
#  hdbios        - BIOS disk-based boot loaders
#  biosexternal  - BIOS external boot loaders (USB, eSATA, etc.)
#  cd            - BIOS optical-disc boot loaders
#  manual        - use stanzas later in this configuration file
#  firmware      - boot EFI programs set in the firmware's NVRAM
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# The netboot option is experimental and relies on the ipxe.efi and
# ipxe_discover.efi program files.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#scanfor internal,external,optical,manual,firmware

# By default, rEFInd relies on the UEFI firmware to detect BIOS-mode boot
# devices. This sometimes doesn't detect all the available devices, though.
# For these cases, uefi_deep_legacy_scan results in a forced scan and
# modification of NVRAM variables on each boot. Adding "0", "off", or
# "false" resets to the default value. This token has no effect on Macs or
# when no BIOS-mode options are set via scanfor.
# Default is unset (or "uefi_deep_legacy_scan false")

# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#scan_delay 5

# When scanning volumes for EFI boot loaders, rEFInd always looks for
# macOS's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The "+" symbol denotes appending to the list of scanned
# directories rather than overwriting that list.
# The default is to scan the "boot" and "@/boot" directories in addition
# to various hard-coded directories.
#also_scan_dirs boot,ESP2:EFI/linux/kernels
#also_scan_dirs boot,@/boot
#also_scan_dirs +,@/kernels

# Partitions (or whole disks, for legacy-mode boots) to omit from scans.
# For EFI-mode scans, you normally specify a volume by its label, which you
# can obtain in an EFI shell by typing "vol", from Linux by typing
# "blkid /dev/{devicename}", or by examining the disk's label in various
# OSes' file browsers. It's also possible to identify a partition by its
# unique GUID (aka its "PARTUUID" in Linux parlance). (Note that this is
# NOT the partition TYPE CODE GUID.) This identifier can be obtained via
# "blkid" in Linux or "diskutil info {partition-id}" in macOS.
# For legacy-mode scans, you can specify any subset of the boot loader
# description shown when you highlight the option in rEFInd.
# The default is "LRS_ESP".
#dont_scan_volumes "Recovery HD"

# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory, the EFI/tools directory, the
# EFI/memtest directory, the EFI/memtest86 directory, or the
# com.apple.recovery.boot directory. Using the dont_scan_dirs option
# enables you to "blacklist" other directories; but be sure to use "+"
# as the first element if you want to continue blacklisting existing
# directories. You might use this token to keep EFI/boot/bootx64.efi out
# of the menu if that's a duplicate of another boot loader or to exclude
# a directory that holds drivers or non-bootloader utilities provided by
# a hardware manufacturer. If a directory is listed both here and in
# also_scan_dirs, dont_scan_dirs takes precedence. Note that this
# blacklist applies to ALL the filesystems that rEFInd scans, not just
# the ESP, unless you precede the directory name by a filesystem name or
# partition unique GUID, as in "myvol:EFI/somedir" to exclude EFI/somedir
# from the scan on the myvol volume but not on other volumes.
#dont_scan_dirs ESP:/EFI/boot,EFI/Dell,EFI/memtest86

# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, various Secure Boot and recovery
# tools are present in this list, but may appear as second-row
# items.
# The file may be specified as a bare name (e.g., "notme.efi"), as
# a complete pathname (e.g., "/EFI/somedir/notme.efi"), or as a
# complete pathname with volume (e.g., "SOMEDISK:/EFI/somedir/notme.efi"
# or 2C17D5ED-850D-4F76-BA31-47A561740082:/EFI/somedir/notme.efi").
# OS tags hidden via the Delete or '-' key in the rEFInd menu are
# added to this list, but stored in NVRAM.
# The default is shim.efi,shim-fedora.efi,shimx64.efi,PreLoader.efi,
# TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,
# HashTool-signed.efi,bootmgr.efi,fb{arch}.efi
# (where "{arch}" is the architecture code, like "x64").
# If you want to keep these defaults but add to them, be sure to
# specify "+" as the first item in the new list; if you don't, then
# items from the default list are likely to appear.
#dont_scan_files shim.efi,MokManager.efi

# EFI NVRAM Boot#### variables that should NOT be presented as loaders
# when "firmware" is an option to "scanfor". The comma-separated list
# presented here contains strings that are matched against the
# description field -- if a value here is a case-insensitive substring
# of the boot option description, then it will be excluded from the
# boot list. To specify a string that includes a space, enclose it
# in quotes. Specifying "shell" will counteract the automatic
# inclusion of built-in EFI shells.
#dont_scan_firmware HARDDISK,shell,"Removable Device"

# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When set to "1", "true", or "on", this
# option causes all files in scanned directories with names that begin with
# "vmlinuz", "bzImage", or "kernel" to be included as loaders, even if they
# lack ".efi" extensions. Passing this option a "0", "false", or "off" value
# causes kernels without ".efi" extensions to NOT be scanned.
# Default is "true" -- to scan for kernels without ".efi" extensions.
#scan_all_linux_kernels false

# Support loaders that have been compressed with gzip.
# On x86 and x86-64 platforms, Linux kernels are self-decompressing.
# On ARM64, Linux kernel files are typically compressed with gzip,
# including the EFI stub loader. This makes them unloadable in rEFInd
# unless rEFInd itself uncompresses them. This option enables rEFInd
# to do this. This feature is unnecessary on x86 and x86-64 systems.
# Default is "false" on x86 and x86-64; "true" on ARM64.
#support_gzipped_loaders true

# Combine all Linux kernels in a given directory into a single entry.
# When so set, the kernel with the most recent time stamp will be launched
# by default, and its filename will appear in the entry's description.
# To launch other kernels, the user must press F2 or Insert; alternate
# kernels then appear as options on the sub-menu.
# Default is "true" -- kernels are "folded" into a single menu entry.
#fold_linux_kernels false

# Comma-delimited list of strings to treat as if they were numbers for the
# purpose of kernel version number detection. These strings are matched on a
# first-found basis; that is, if you want to treat both "linux-lts" and
# "linux" as version strings, they MUST be specified as "linux-lts,linux",
# since if you specify it the other way, both vmlinuz-linux and
# vmlinuz-linux-lts will return with "linux" as the "version string," which
# is not what you'd want. Also, if the kernel or initrd file includes both a
# specified string and digits, the "version string" includes both. For
# instance, "vmlinuz-linux-4.8" would yield a version string of "linux-4.8".
# This option is intended for Arch and other distributions that don't include
# version numbers in their kernel filenames, but may provide other uniquely
# identifying strings for multiple kernels. If this feature causes problems
# (say, if your kernel filename includes "linux" but the initrd filename
# doesn't), be sure this is set to an empty string
# (extra_kernel_version_strings "") or comment out the option to disable it.
# Default is no extra version strings
extra_kernel_version_strings linux-lts,linux

# Write to systemd EFI variables (currently only LoaderDevicePartUUID) when
# launching Linux via an EFI stub loader, ELILO, or GRUB. This variable,
# when present, causes systemd to mount the ESP at /boot or /efi *IF* either
# directory is empty and nothing else is mounted there.
# Default is "false"
#write_systemd_vars true

# Symlinked loaders will be processed when this setting is set to true.
# These are ignored by default as they may result in undesirable outcomes.
# This token may, however, be useful on Linux setups that provide symbolic
# links in scanned locations that point to kernels in unscanned locations,
# such as some openSUSE installations.
#follow_symlinks true

# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#max_tags 0

# Set the default menu selection.  The available arguments match the
# keyboard accelerators available within rEFInd.  You may select the
# default loader using:
#  - A digit between 1 and 9, in which case the Nth loader in the menu
#    will be the default.
#  - A "+" symbol at the start of the string, which refers to the most
#    recently booted loader.
#  - Any substring that corresponds to a portion of the loader's title
#    (usually the OS's name, boot loader's path, or a volume or
#    filesystem title).
# You may also specify multiple selectors by separating them with commas
# and enclosing the list in quotes. (The "+" option is only meaningful in
# this context.)
# If you follow the selector(s) with two times, in 24-hour format, the
# default will apply only between those times. The times are in the
# motherboard's time standard, whether that's UTC or local time, so if
# you use UTC, you'll need to adjust this from local time manually.
# Times may span midnight as in "23:30 00:30", which applies to 11:30 PM
# to 12:30 AM. You may specify multiple default_selection lines, in which
# case the last one to match takes precedence. Thus, you can set a main
# option without a time followed by one or more that include times to
# set different defaults for different times of day.
# The default behavior is to boot the previously-booted OS.
#default_selection 1
#default_selection Microsoft
#default_selection "+,bzImage,vmlinuz"
#default_selection Maintenance 23:30 2:00
#default_selection "Maintenance,macOS" 1:00 2:30

# Enable VMX bit and lock the CPU MSR if unlocked.
# On some Intel Apple computers, the firmware does not lock the MSR 0x3A.
# The symptom on Windows is Hyper-V not working even if the CPU
# meets the minimum requirements (HW assisted virtualization and SLAT)
# http://www.thomas-krenn.com/en/wiki/Activating_the_Intel_VT_Virtualization_Feature
# for more on this subject.
# The default is false: Don't try to enable and lock the MSR.
#enable_and_lock_vmx false

# Tell a Mac's EFI that macOS is about to be launched, even when it's not.
# This option causes some Macs to initialize their hardware differently than
# when a third-party OS is launched normally. In some cases (particularly on
# Macs with multiple video cards), using this option can cause hardware to
# work that would not otherwise work. On the other hand, using this option
# when it is not necessary can cause hardware (such as keyboards and mice) to
# become inaccessible. Therefore, you should not enable this option if your
# non-Apple OSes work correctly; enable it only if you have problems with
# some hardware devices. When needed, a value of "10.9" usually works, but
# you can experiment with other values. This feature has no effect on
# non-Apple computers.
# The default is inactive (no macOS spoofing is done).
#spoof_osx_version 10.9

# Set the CSR values for Apple's System Integrity Protection (SIP) feature.
# Values are two-byte (four-character) hexadecimal numbers. These values
# define which specific security features are enabled. Below are the codes
# for what the values mean. Add them up (in hexadecimal!) to set new values.
# Apple's "csrutil enable" and "csrutil disable" commands set values of 10
# and 877, respectively. (Prior to OS 11, 77 was used rather than 877; 877
# is required for OS 11, and should work for OS X 10.x, too.)
#   CSR_ALLOW_UNTRUSTED_KEXTS            0x0001
#   CSR_ALLOW_UNRESTRICTED_FS            0x0002
#   CSR_ALLOW_TASK_FOR_PID               0x0004
#   CSR_ALLOW_KERNEL_DEBUGGER            0x0008
#   CSR_ALLOW_APPLE_INTERNAL             0x0010
#   CSR_ALLOW_ANY_RECOVERY_OS            0x0100
#   CSR_ALLOW_UNAPPROVED_KEXTS           0x0200
#csr_values 10,877

# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#include manual.conf

# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
#  volume    - identifies the filesystem from which subsequent files
#              are loaded. You can specify the volume by filesystem
#              label, by partition label, or by partition GUID number
#              (but NOT yet by filesystem UUID number).
#  loader    - identifies the boot loader file
#  initrd    - Specifies an initial RAM disk file
#  icon      - specifies a custom boot loader icon
#  ostype    - OS type code to determine boot options available by
#              pressing Insert. Valid values are "MacOS", "Linux",
#              "Windows", and "XOM". Case-sensitive.
#  graphics  - set to "on" to enable graphics-mode boot (useful
#              mainly for MacOS) or "off" for text-mode boot.
#              Default is auto-detected from loader filename.
#  options   - sets options to be passed to the boot loader; use
#              quotes if more than one option should be passed or
#              if any options use characters that might be changed
#              by rEFInd parsing procedures (=, /, #, or tab).
#  disabled  - use alone or set to "yes" to disable this entry.
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.

# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.

# A sample entry for a Linux 3.13 kernel with EFI boot stub support
# on a partition with a GUID of 904404F8-B481-440C-A1E3-11A5A954E601.
# This entry includes Linux-specific boot options and specification
# of an initial RAM disk. Note uses of Linux-style forward slashes.
# Also note that a leading slash is optional in file specifications.
menuentry Linux {
    icon EFI/refind/icons/os_linux.png
    volume 904404F8-B481-440C-A1E3-11A5A954E601
    loader bzImage-3.3.0-rc7
    initrd initrd-3.3.0.img
    options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"

# Below is a more complex Linux example, specifically for Arch Linux.
# This example MUST be modified for your specific installation; if nothing
# else, the PARTUUID code must be changed for your disk. Because Arch Linux
# does not include version numbers in its kernel and initrd filenames, you
# may need to use manual boot stanzas when using fallback initrds or
# multiple kernels with Arch. This example is modified from one in the Arch
# wiki page on rEFInd (https://wiki.archlinux.org/index.php/rEFInd).
menuentry "Arch Linux" {
    icon     /EFI/refind/icons/os_arch.png
    volume   "Arch Linux"
    loader   /boot/vmlinuz-linux
    initrd   /boot/initramfs-linux.img
    options  "root=PARTUUID=5028fa50-0079-4c40-b240-abfaf28693ea rw add_efi_memmap"
    submenuentry "Boot using fallback initramfs" {
        initrd /boot/initramfs-linux-fallback.img
    submenuentry "Boot to terminal" {
        add_options "systemd.unit=multi-user.target"

# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
    loader /EFI/ubuntu/grubx64.efi
    icon /EFI/refind/icons/os_linux.png

# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
    loader \EFI\elilo\elilo.efi

# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
    loader \EFI\Microsoft\Boot\bootmgfw.efi

# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
    icon \EFI\refind\icons\os_win.png
    loader \EFI\tools\shell.efi
    options "fs0:\EFI\tools\launch_windows.nsh"

# MacOS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My macOS" {
    icon \EFI\refind\icons\os_mac.png
    volume "macOS boot"
    loader \System\Library\CoreServices\boot.efi

# The firmware_bootnum token takes a HEXADECIMAL value as an option
# and sets that value using the EFI's BootNext variable and then
# reboots the computer. This then causes a one-time boot of the
# computer using this EFI boot option. It can be used for various
# purposes, but one that's likely to interest some rEFInd users is
# that some Macs with HiDPI displays produce lower-resolution
# desktops when booted through rEFInd than when booted via Apple's
# own boot manager. Booting using the firmware_bootnum option
# produces the better resolution. Note that no loader option is
# used in this type of configuration.
menuentry "macOS via BootNext" {
    icon /EFI/refind/icons/os_mac.png
    firmware_bootnum 80

menuentry "Endeavour OS" {
    icon     /efi/EFI/refind/icons/os_arch.png
    volume   C44C-437B
    loader   /efi/9dfe81e5b0ea4daa8226f5badb20bfdf/6.2.9-arch1-1/linux
    initrd   /efi/9dfe81e5b0ea4daa8226f5badb20bfdf/6.2.9-arch1-1/initrd
    options  "root=/dev/nvme0n1p2 rw add_efi_memmap"

and here is my refind_linux.conf

"Boot with standard options"  "nvme_load=YES nowatchdog rw rootflags=subvol=/@ rd.luks.uuid=65d254bc-67a4-4e0c-b520-9bc5825fd81c root=/dev/mapper/luks-65d254bc-67a4-4e0c-b520-9bc5825fd81c systemd.machine_id=9dfe81e5b0ea4daa8226f5badb20bfdf"
"Boot to single-user mode"    "nvme_load=YES nowatchdog rw rootflags=subvol=/@ rd.luks.uuid=65d254bc-67a4-4e0c-b520-9bc5825fd81c root=/dev/mapper/luks-65d254bc-67a4-4e0c-b520-9bc5825fd81c systemd.machine_id=9dfe81e5b0ea4daa8226f5badb20bfdf single"
"Boot with minimal options"   "ro root=/dev/mapper/luks-65d254bc-67a4-4e0c-b520-9bc5825fd81c"

Output of lsblk:

NAME                                          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
nvme0n1                                       259:0    0 953,9G  0 disk  
├─nvme0n1p1                                   259:1    0  1000M  0 part  /efi
└─nvme0n1p2                                   259:2    0 952,9G  0 part  
  └─luks-65d254bc-67a4-4e0c-b520-9bc5825fd81c 254:0    0 952,9G  0 crypt /var/log

my fstab:

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=C44C-437B                            /efi           vfat    defaults,noatime 0 2
/dev/mapper/luks-65d254bc-67a4-4e0c-b520-9bc5825fd81c /              btrfs   subvol=/@,defaults,noatime,compress=zstd 0 0
/dev/mapper/luks-65d254bc-67a4-4e0c-b520-9bc5825fd81c /home          btrfs   subvol=/@home,defaults,noatime,compress=zstd 0 0
/dev/mapper/luks-65d254bc-67a4-4e0c-b520-9bc5825fd81c /var/cache     btrfs   subvol=/@cache,defaults,noatime,compress=zstd 0 0
/dev/mapper/luks-65d254bc-67a4-4e0c-b520-9bc5825fd81c /var/log       btrfs   subvol=/@log,defaults,noatime,compress=zstd 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
UUID=7d6e5efd-bbf8-4fcf-94b6-64a9e90e7ba6	/swap	btrfs	subvol=@swap,nodatacow,noatime,nospace_cache	0	0
/swap/swapfile	none	swap	defaults	0	0

what is inside of /boot

-rw-r--r-- 1 root root 7066624 15. Feb 01:22 intel-ucode.img
-rw-r--r-- 1 root root     583  3. Apr 20:04 refind_linux.conf

what is inside of /efi

9dfe81e5b0ea4daa8226f5badb20bfdf  EFI  loader

6.1.22-1-lts  6.2.9-arch1-1

initrd  initrd-fallback  linux

initrd  initrd-fallback  linux

BOOT  Linux  refind  systemd  tools

BOOT.CSV  BOOTX64.EFI  drivers_x64  icons  keys  refind.conf  refind.conf-sample  vars


arrow_left.png       os_bionic.png      os_kubuntu.png    os_suse.png            tool_mok_tool.png
arrow_right.png      os_centos.png      os_legacy.png     os_systemd.png         tool_netboot.png
boot_linux.png       os_chakra.png      os_linuxmint.png  os_trusty.png          tool_part.png
boot_win.png         os_chrome.png      os_linux.png      os_ubuntu.png          tool_rescue.png
func_about.png       os_clover.png      os_lubuntu.png    os_uefi.png            tool_shell.png
func_bootorder.png   os_crunchbang.png  os_mac.png        os_unknown.png         tool_windows_rescue.png
func_csr_rotate.png  os_debian.png      os_mageia.png     os_void.png            transparent.png
func_exit.png        os_devuan.png      os_mandriva.png   os_win8.png            vol_efi.png
func_firmware.png    os_elementary.png  os_manjaro.png    os_win.png             vol_external.png
func_hidden.png      os_fedora.png      os_netbsd.png     os_xenial.png          vol_internal.png
func_install.png     os_freebsd.png     os_network.png    os_xubuntu.png         vol_net.png
func_reset.png       os_frugalware.png  os_opensuse.png   os_zesty.png           vol_optical.png
func_shutdown.png    os_gentoo.png      os_redhat.png     svg
mouse.png            os_gummiboot.png   os_refind.png     tool_apple_rescue.png
os_arch.png          os_haiku.png       os_refit.png      tool_fwupdate.png
os_artful.png        os_hwtest.png      os_slackware.png  tool_memtest.png

boot_win.svg         os_debian.svg      os_haiku.svg   os_redhat.svg  os_xenial.svg
func_csr_rotate.svg  os_devuan.svg      os_legacy.svg  os_refind.svg  tool_fwupdate.svg
mouse.svg            os_elementary.svg  os_mac.svg     os_refit.svg   tool_memtest.svg
os_clover.svg        os_gummiboot.svg   os_netbsd.svg  os_win.svg     tool_rescue.svg

refind_local.cer  refind_local.crt



BOOT.CSV  drivers_x64  icons  keys  refind.conf  refind_x64.efi  vars


arrow_left.png       os_bionic.png      os_kubuntu.png    os_suse.png            tool_mok_tool.png
arrow_right.png      os_centos.png      os_legacy.png     os_systemd.png         tool_netboot.png
boot_linux.png       os_chakra.png      os_linuxmint.png  os_trusty.png          tool_part.png
boot_win.png         os_chrome.png      os_linux.png      os_ubuntu.png          tool_rescue.png
func_about.png       os_clover.png      os_lubuntu.png    os_uefi.png            tool_shell.png
func_bootorder.png   os_crunchbang.png  os_mac.png        os_unknown.png         tool_windows_rescue.png
func_csr_rotate.png  os_debian.png      os_mageia.png     os_void.png            transparent.png
func_exit.png        os_devuan.png      os_mandriva.png   os_win8.png            vol_efi.png
func_firmware.png    os_elementary.png  os_manjaro.png    os_win.png             vol_external.png
func_hidden.png      os_fedora.png      os_netbsd.png     os_xenial.png          vol_internal.png
func_install.png     os_freebsd.png     os_network.png    os_xubuntu.png         vol_net.png
func_reset.png       os_frugalware.png  os_opensuse.png   os_zesty.png           vol_optical.png
func_shutdown.png    os_gentoo.png      os_redhat.png     svg
mouse.png            os_gummiboot.png   os_refind.png     tool_apple_rescue.png
os_arch.png          os_haiku.png       os_refit.png      tool_fwupdate.png
os_artful.png        os_hwtest.png      os_slackware.png  tool_memtest.png

boot_win.svg         os_debian.svg      os_haiku.svg   os_redhat.svg  os_xenial.svg
func_csr_rotate.svg  os_devuan.svg      os_legacy.svg  os_refind.svg  tool_fwupdate.svg
mouse.svg            os_elementary.svg  os_mac.svg     os_refit.svg   tool_memtest.svg
os_clover.svg        os_gummiboot.svg   os_netbsd.svg  os_win.svg     tool_rescue.svg

refind_local.cer  refind_local.crt




entries  entries.srel  loader.conf  random-seed


What do i need to change in order to directly start endeavourOS from rEFInd and not go through systemd-boot?
Do i need to change refind.conf or refind_linux.conf or both?
Why did refind-install not generated this but took systemd-boot as only option? Can i somehow show refind-install the right path to generate this automatically?
Why is my ESP at /efi/ and not /boot? Is this a matter of endeavourOS or systemd-boot?
Why do i not have these initramfs-linux.img files or vmlinuz-linux?
Is it easier to switch from grub to rEFInd than from systemd-boot to rEFInd? (i did not confige that much else)

You need to configure refind to find the kernels and boot images. Since we don’t support refind directly, I have never investigated how to do this and give you more specific guidance.

When you choose systemd-boot, we install in compliance with the Boot Loader Specification(BLS) which is a standard. It seems like refind doesn’t support this by default. As a result, it cant’ find your kernels.

It probably isn’t an issue with refind-install, it is probably configuration you need to do.

Why would it be at /boot and not /efi? :wink:

There is no correct place to put it. There are a number of places that are all valid. We chose /efi as it doesn’t interfere with anything else but you could also mount it at /boot. It will still work.

As above, we follow the BLS which puts the files at different locations. This avoids kernel collision when multi-booting.

It requires less configuration to make this switch, yes. Because we have never investigated how to switch from systemd-boot to refind directly, I can’t say if it is easier or harder.

1 Like

Not having tried to implement anything similar on btrfs, I am not sure where the problem arises. However, the first thing I would check is to locate the actual boot file(s), and add it to the also-scan-dirs entry in refind.conf

On my system, this is located in /boot/efi/EFI/refind - but you may need to be a bit proactive to find it on yours! A s ‘rule’ (read, my experience so far) - if there is anything in a legit bootable form in anyplace is ends up looking, it will display it and allow it to be used for a boot selection.

As a side note, not all 'alternative; file systems are provided with reading routines in rEFInd - for instance I needed to make a separate boot partition for some file systems to be usable with rEFInd - such as f2fs. I do not know the state of play regarding btrfs…

Hope some of this helps! I keep meaning to set up a build with EnOS’s system-d boot to ‘play’ with - but I haven’t done so as yet…

This is not quite right. The volume entry can be your PARTUUID, but not your filesystem UUID. You can use blkid to find it.

The path to the icon should be relative to the EFI partition, so in your case /EFI/BOOT/icons/os_arch.png.

The path to the loader and initrd entries should be relative to the volume, so drop the leading /efi.

If it helps, I wrote a guide on another forum that includes a step-by-step for setting up the manual boot stanza. Obviously ignore the rest of the topic; here I have linked to the part that describes setting up the boot stanza:

It will also break every time the kernel updates since the path will change.

1 Like

If the path to the kernel is changing when the kernel upgrades, then the path would need to be changed in the stanza as well. I know rEFInd will take a string as an argument for finding the kernel (or many kernels), but I am not sure if it will take a string for a directory.

If the goal is to switch to rEFInd from systemd-boot, it may be best to remove systemd-boot altogether–or at least disable the script that defines this path which changes dynamically, and just store the kernel and images in /boot. Or anywhere that does not routinely change.

Edit to add:

If you are asking because you are considering re-installing, another option to consider is installing with no bootloader. I have two EOS installations I have used this option with; it works out great. I really appreciate that EOS offers this in the installer–it is a very uncommon option to get.

I typically mount the ESP at /efi and the Btrfs partition at / in the installer, pick “no bootloader”, and then when the installation is up you just set up the stanza in refind.conf and you are done.

If you mess up the stanza, you’ll have to chroot in to fix it of course, so…be careful! :smile:

Refind boot from systemd.

Edit: rEFInd is a boot manager not a boot loader.

Nice one @ricklinux, although in your pictures I can see you are booting from rEFInd to systemd-boot (using systemd-boot as the bootloader). @exp mentioned they want to use rEFInd as the bootloader instead of systemd-boot.

Hmm, that’s not quite right. rEFInd can be a boot manager, and hand off to other bootloaders as you have set up. However it can also be a full-fledged bootloader in its own right. Having another bootloader is not needed with rEFInd.

Well that’s not how it’s explained from the author and developer of rEFInd. :man_shrugging:

Edit: https://www.rodsbooks.com/refind/

You are right, according to the author it is technically facilitating the kernel serving as its own EFI bootloader.

However, according to this same author’s very technical interpretation of what is or isn’t a bootloader, systemd-boot is not a bootloader either:

The systemd-boot boot manager is, as the name implies, part of the Linux systemd startup system. This boot manager was previously known as gummiboot, which is German for rubber boat. Under either name, it is, like rEFIt and rEFInd, a boot manager, not a boot loader; you can use systemd-boot to select which OS to boot or to launch a 3.3.0 or later kernel, but not to launch another OS’s kernel.

In the case of a setup where rEFInd is effectively serving as the bootloader, I typically refer to it as such even if that is not technically correct. I think all of us here are accustomed to doing to same in the case of systemd-boot–it’s just much less confusing.

Ive never tried using rEFInd without a bootloader.

It’s a little clunky to set up, but once you get the hang of it I think it’s really great–especially for multibooting setups.

Once you start writing the boot stanza, you can make custom “submenu” entries to use rEFInd to boot alternate kernels or fallback images, or even hand off to another bootloader.

This is one of those things that is mostly meaningless.

By the authors definition of a boot loader and a boot manager, all the major boot loaders we use including grub and systemd-boot would be “boot managers”

Okay …it’s a bootmanager / bootloader. :wink:


It would be nice to try rEFInd without systemd. I would have to install it on vm and probably need help to get it working.

Edit: Maybe i try sometime when i feel like getting a migraine. :rofl:

I would not think of grub as a manager :policeman: just because it works on hardware level :person_shrugging: .

Grub is a real tool :wink: . Others are still trying :stuck_out_tongue_closed_eyes: .

As for

Grub dev reports it as a boot loader. I trust him more than rEFInd’s dev.

For what it’s worth, the rEFInd author classifies Grub as a bootloader. Here is his list:

  • The Boot Loaders—A boot loader loads an OS kernel into memory and executes it. The following programs can all launch the Linux kernel in this way. A few can launch other OS kernels or perform boot manager tasks, too, as described shortly.
    • Using ELILO—This boot loader is modelled after the BIOS-mode LILO. ELILO was one of the (maybe the) first EFI boot loader for Linux, but it seems to have been abandoned in 2013.
    • Using SYSLINUX—This is a family of boot loaders for Linux, covering both BIOS-mode and EFI-mode booting from a variety of media. It’s similar to ELILO in overall scope and capabilities, but it seems to have seen no development since late 2014.
    • Using GRUB Legacy—Officially, the first version of GRUB (aka GRUB Legacy does not support EFI-mode booting; however, an EFI-enabled version was forked by Fedora and used by that distribution through Fedora 17, which was released in 2012. Fedora 18, released in 2013, switched to GRUB 2…
    • Using GRUB 2—This boot loader is the default for most Linux distributions; although many used one of the preceding boot loaders at one time, by 2014 most had switched to GRUB 2. GRUB 2 provides the most features of any Linux boot loader, particularly features related to technical matters such as network booting, support for LVM and encrypted filesystems, etc.
    • Using the Kernel’s EFI Stub Loader—The Linux kernel itself can be configured with a built-in EFI boot loader. Most Linux distributions enable this feature by default on their kernels. This unusual feature enables a simpler boot manager, as described next, to effectively function as a boot loader…
  • The Boot Managers—Boot managers hand off control to another boot program; they don’t boot an OS directly. (The EFI stub loader, though, blurs the lines.)
    • Using rEFIt—This boot manager originated in the Mac world (which switched to EFI earlier than the rest of the PC world), but was abandoned in 2010. It is a very graphical boot manager, using icons rather than text in its boot menu. It remains useful, although it has some serious limitations, particularly when booting Linux via the EFI stub loader. Chances are you’re better off using rEFInd…
    • Using rEFInd—This is my fork of rEFIt, with the goal of adding features to make it more useful on UEFI-based PCs and to boot Linux kernels via the EFI stub loader, while retaining and expanding rEFIt’s graphical nature and ease of use. rEFInd has features that make it a good choice for those who boot many OSes, and especially those who install multiple Linux distributions.
    • Using gummiboot/systemd-boot—This program is a bare-bones text-mode boot manager for EFI-based systems. It’s linked to the dominant systemd startup system, and its developers are promoting a boot standard that could be very helpful in multi-distribution installations; but systemd-boot has some design features that limit its utility and it hasn’t gained much traction against the dominant GRUB 2.
    • Using fallback.efi—This program (usually installed using an architecture-specific variant name, such as fbx64.efi) is a highly specialized program that I classify as a boot manager because its job is to pass control to another boot manager or boot loader; however, it presents no menu. Instead, it tries to re-create the firmware’s own built-in boot manager options, in case they’ve been wiped out. Linux distributions are increasingly relying on it to deal with flaky EFIs; but it can cause problems if you don’t understand what it’s doing.

As dalto pointed out though, for most users the nuance is somewhat pointless to be concerned with.

1 Like

All in all he still describes rEFInd as a boot manager? :man_shrugging: Since i have never used it to boot an OS directly without grub. I just believed it to be the case. Even thought it can be set up without systemd-boot i still think of it as a boot manager since it is booting from the image using UEFI. I don’t know … potato patoto! :thinking:

Edit: I’m not so sure i have enough knowledge to even set it up. Maybe? :man_shrugging:

Well, like he says the EFI stub loader “blurs the lines”.

I think if you spend as much time studying bootloaders as that guy, you probably develop your own special understanding of the mechanics of bootloaders. :face_with_monocle: :laughing:

You can get started easily enough by using a VM like you mentioned.

  1. Install EOS in the VM, choose the “no bootloader” option.
  2. Before reboot, install refind.
  3. Run sudo refind-install.
  4. Reboot!

In most cases, that’s all you need for setting up a bootable rEFInd entry. Creating a “proper” boot stanza is only needed if you want to achieve more specific configuration, or you have a non-standard setup you want to boot with.

IMHO, this is correct.
Another way to see this, is that a manager is looking for files, (or BIOS/EFI entries), that already exist, and triggers them.
A loader uses its own created files/config (like grub.cfg), or reading the MBR sector.
Now that I rethink this, EFI systems can only have managers, while MSDOS Legacy can only have loaders. Obviously, this is why rEFInd cannot boot in MSDOS/MBR systems :wink: :person_shrugging: .

1 Like