Systemd-boot and rEFInd?

I switched from Windows to EndeavourOS since a month or two now. Reading and exploring wikis here and on Arch slowly. Please correct me if I state some terminologies incorrectly.
I was using systemd-boot boot manager (the one that creates fallback initramfs?).

I installed rEFInd today, and it shows me two entries(auto-generated) named:
- Boot systemd-bootx64.efi from 499 MiB FAT volume
- UEFI OS
Both open the systemd-boot screen where I can pick which kernel to boot.
The behavior I expected was to see eos logo or eos entries “auto-detected” at least.

Why is this happening? Is it safe to just bootctl remove and let rEFInd work alone?

I read a post while writing this post here: Switiching to rEFInd from systemd-boot (w/ brtfs). I do not have encrypted volumes, but I do have btrfs. Since I don’t know what to do, I will just post this here.

Here is some information about my system:

Partition Table:
PS: Ignore the first leftover partition.

parted /dev/nvme0n1 print
Model: SAMSUNG MZVLQ512HALU-00000 (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size    File system     Name                  Flags
1      1049kB  106MB  105MB   fat32                                 msftdata
6      106MB   438GB  438GB   btrfs
7      438GB   502GB  64.3GB  btrfs           Basic data partition
9      502GB   503GB  524MB   fat32           EFI system partition  boot, esp
8      503GB   512GB  8594MB  linux-swap(v1)                        swap

inxi -FAX --no-host: https://0x0.st/HPC3.txt

My ESP partition contents:

tree --sort name --filelimit 70 /efi
/efi
├── c8a8e4fe23234c91a83edfedb4704bb5
│   ├── 6.2.13-arch1-1
│   │   ├── initrd
│   │   ├── initrd-fallback
│   │   └── linux
│   └── 6.3.1-x64v3-xanmod1
│       ├── initrd
│       ├── initrd-fallback
│       └── linux
├── EFI
│   ├── BOOT
│   │   └── BOOTX64.EFI
│   ├── Linux
│   ├── refind
│   │   ├── BOOT.CSV
│   │   ├── drivers_x64
│   │   │   └── btrfs_x64.efi
│   │   ├── icons  [77 entries exceeds filelimit, not opening dir]
│   │   ├── icons-backup  [76 entries exceeds filelimit, not opening dir]
│   │   ├── keys
│   │   ├── refind.conf
│   │   ├── refind_x64.efi
│   │   └── vars
│   │       └── PreviousBoot
│   ├── systemd
│   │   └── systemd-bootx64.efi
│   └── tools
└── loader
├── entries
│   ├── c8a8e4fe23234c91a83edfedb4704bb5-6.2.13-arch1-1.conf
│   ├── c8a8e4fe23234c91a83edfedb4704bb5-6.2.13-arch1-1-fallback.conf
│   ├── c8a8e4fe23234c91a83edfedb4704bb5-6.3.1-x64v3-xanmod1.conf
│   └── c8a8e4fe23234c91a83edfedb4704bb5-6.3.1-x64v3-xanmod1-fallback.conf
├── entries.srel
├── loader.conf
└── random-seed

17 directories, 20 files

efibootmgr:

efibootmgr -uv
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0002
Boot0000* rEFInd Boot Manager   HD(9,GPT,6ecea89a-8b48-0f4b-aff4-d5d0e657178c,0x3a7e9800,0xfa000)/File(\EFI\REFIND\REFIND_X64.EFI)
dp: 04 01 2a 00 09 00 00 00 00 98 7e 3a 00 00 00 00 00 a0 0f 00 00 00 00 00 9a a8 ce 6e 48 8b 4b 0f af f4d5 d0 e6 57 17 8c 02 02 / 04 04 3a 00 5c 00 45 00 46 00 49 00 5c 00 52 00 45 00 46 00 49 00 4e 00 44 00 5c 00 52 00 45 00 46 00 49 00 4e 00 44 00 5f 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0002* UEFI OS       HD(9,GPT,6ecea89a-8b48-0f4b-aff4-d5d0e657178c,0x3a7e9800,0xfa000)/File(\EFI\BOOT\BOOTX64.EFI)
dp: 04 01 2a 00 09 00 00 00 00 98 7e 3a 00 00 00 00 00 a0 0f 00 00 00 00 00 9a a8 ce 6e 48 8b 4b 0f af f4d5 d0 e6 57 17 8c 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
data: 00 00 42 4f

bootctl list: https://0x0.st/HPC0.txt

With systemd-boot, the kernels and boot images are in the ESP stored according to the Boot Loader Specification(BLS)

If you want to use refind as-is in that scenario, you would need to configure it to find the images stored in that format. Before you ask, no, I don’t know how to do that.

Alternatively, you could install using the “No bootloader” option and then install refind. That would likely be closer to what you would expect.