#"Boot to terminal" "root=PARTUUID=XXXXXXXX rootfstype=XXXX ro systemd.unit=multi-user.target" #"Boot with defaults" "root=PARTUUID=XXXXXXXX rootfstype=XXXX ro" # This file should be present in the same directory as the EFISTUB kernel and initramfs files (I omitted a few things to make this look better, mostly in the Microscoft directory, but didn't want to omit anything otherwise just in case any of this is the problem.) Note that the Linux mount point for the ESP is not just irrelevant to the EFI it's something that the EFI doesn't even know! Thus, your "include" directive: The ESP is typically mounted at /boot or /boot/efi. Linux uses a unified directory tree in which all files are in one directory structure, starting from a root ("/") directory, including files in other partitions. This is true of the "include" directive, for instance. In some contexts, rEFInd also requires you to omit the directory, and assumes that the file reference is relative to rEFInd's installation directory. Most EFI programs, including rEFInd, enable you to omit the filesystem number when referring to files on the same partition.
![arch linux mac os theme arch linux mac os theme](https://linuxhint.com/wp-content/uploads/2020/06/1-14.png)
EFI boot loaders reside in subdirectories of the EFI System Partition's (ESP's) "EFI" directory, which is typically the first filesystem ("fs0:") - thus, rEFInd is likely to be in fs0:\EFI\refind.
![arch linux mac os theme arch linux mac os theme](https://i0.wp.com/manjaro.site/wp-content/uploads/2019/09/catalina.png)
I believe you're suffering from confusion over the difference between paths as seen in Linux and paths as seen in EFI.ĮFI uses a DOS/Windows-like view of the disk in which each partition is accessed via a filesystem number ("fs0:", "fs1:", and so on).