This is exactly what I was looking for to replace the systemd that comes
with Pop!_OS by default. I wanted a simple boot manager for my W10 + Pop
without the need of installing the "old" GRUB bootloader, but at the
same time giving me the opportunity to play with some different kernels
mainly due to Nvidia proprietary driver and asus-nb-ctl (power manager and
some other tweaks).
Long story short, after installing via ubuntu apt I'm getting a blank
screen with rEFInd logo. I got so interested that I started reading the
whole manual to try to solve my issue but to be honest I wasn't able to fix
it. Everything seems to be fine on my eyes (not well literate though).
That's the reason I'm kindly asking for your help.
Another possibility is that you're encountering a filesystem driver bug. Removing unnecessary filesystem drivers (from /boot/efi/EFI/refind/drivers_x64, normally) can fix this problem; or you may need to run a filesystem check or even switch to another filesystem, at least to hold your kernel and associated files. (A ~1GB /boot partition should be adequate for this.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
I came to use (or try to) rEFInd after reading an interesting article here (
https://teejeetech.in/2020/09/05/linux-multi-boot-with-refind/) describing
the features and how to install it.
This is exactly what I was looking for to replace the systemd that comes
with Pop!_OS by default. I wanted a simple boot manager for my W10 + Pop
without the need of installing the "old" GRUB bootloader, but at the
same time giving me the opportunity to play with some different kernels
mainly due to Nvidia proprietary driver and asus-nb-ctl (power manager and
some other tweaks).
Long story short, after installing via ubuntu apt I'm getting a blank
screen with rEFInd logo. I got so interested that I started reading the
whole manual to try to solve my issue but to be honest I wasn't able to fix
it. Everything seems to be fine on my eyes (not well literate though).
That's the reason I'm kindly asking for your help.
I ran the ls -R /boot/efi as you can find below.
/boot/efi: 8fd6b8a74dbc0bd12ad06a2d5ff5b8e6 EFI loader 'System Volume
Information'/boot/efi/8fd6b8a74dbc0bd12ad06a2d5ff5b8e6:/boot/efi/EFI:BOOT
Pop_OS-e903ea46-336e-4345-b83e-4e3e604ee3a5 systemdLinux refind
tools/boot/efi/EFI/BOOT:BOOTX64.EFI/boot/efi/EFI/Linux:/boot/efi/EFI/Pop_OS-e903ea46-336e-4345-b83e-4e3e604ee3a5:cmdline
initrd.img vmlinuz.efi/boot/efi/EFI/refind:BOOT.CSV icons keys
refind.conf-sampledrivers_x64 icons-backup refind.conf
refind_x64.efi/boot/efi/EFI/refind/drivers_x64:btrfs_x64.efi/boot/efi/EFI/refind/icons:arrow_left.png
os_fedora.png os_ubuntu.pngarrow_right.png os_freebsd.png
os_unknown.pngboot_linux.png os_frugalware.png os_void.pngboot_win.png
os_gentoo.png os_win8.pngfunc_about.png os_gummiboot.png
os_win.pngfunc_bootorder.png os_haiku.png
os_xenial.pngfunc_csr_rotate.png os_hwtest.png os_xubuntu.pngfunc_exit.png
os_kubuntu.png os_zesty.pngfunc_firmware.png os_legacy.png
READMEfunc_hidden.png os_linuxmint.png
tool_apple_rescue.pngfunc_install.png os_linux.png
tool_fwupdate.pngfunc_reset.png os_lubuntu.png
tool_memtest.pngfunc_shutdown.png os_mac.png tool_mok_tool.pngmouse.png
os_mageia.png tool_netboot.pngos_arch.png os_mandriva.png
tool_part.pngos_artful.png os_netbsd.png tool_rescue.pngos_bionic.png
os_network.png tool_shell.pngos_centos.png os_opensuse.png
tool_windows_rescue.pngos_chakra.png os_redhat.png
transparent.pngos_chrome.png os_refind.png
vol_external.pngos_clover.png os_refit.png
vol_internal.pngos_crunchbang.png os_slackware.png
vol_net.pngos_debian.png os_suse.png vol_optical.pngos_devuan.png
os_systemd.pngos_elementary.png
os_trusty.png/boot/efi/EFI/refind/icons-backup:arrow_left.png
os_fedora.png os_ubuntu.pngarrow_right.png os_freebsd.png
os_unknown.pngboot_linux.png os_frugalware.png os_void.pngboot_win.png
os_gentoo.png os_win8.pngfunc_about.png os_gummiboot.png
os_win.pngfunc_bootorder.png os_haiku.png
os_xenial.pngfunc_csr_rotate.png os_hwtest.png os_xubuntu.pngfunc_exit.png
os_kubuntu.png os_zesty.pngfunc_firmware.png os_legacy.png
READMEfunc_hidden.png os_linuxmint.png
tool_apple_rescue.pngfunc_install.png os_linux.png
tool_fwupdate.pngfunc_reset.png os_lubuntu.png
tool_memtest.pngfunc_shutdown.png os_mac.png tool_mok_tool.pngmouse.png
os_mageia.png tool_netboot.pngos_arch.png os_mandriva.png
tool_part.pngos_artful.png os_netbsd.png tool_rescue.pngos_bionic.png
os_network.png tool_shell.pngos_centos.png os_opensuse.png
tool_windows_rescue.pngos_chakra.png os_redhat.png
transparent.pngos_chrome.png os_refind.png
vol_external.pngos_clover.png os_refit.png
vol_internal.pngos_crunchbang.png os_slackware.png
vol_net.pngos_debian.png os_suse.png vol_optical.pngos_devuan.png
os_systemd.pngos_elementary.png
os_trusty.png/boot/efi/EFI/refind/keys:altlinux.cer
openSUSE-UEFI-CA-Certificate-4096.cercanonical-uefi-ca.cer
openSUSE-UEFI-CA-Certificate.cercentos.cer refind.cerfedora-ca.cer
refind_local.cermicrosoft-kekca-public.cer
refind_local.crtmicrosoft-pca-public.cer
SLES-UEFI-CA-Certificate.cermicrosoft-uefica-public.cer/boot/efi/EFI/systemd:systemd-bootx64.efi/boot/efi/EFI/tools:/boot/efi/loader:entries
loader.conf
random-seed/boot/efi/loader/entries:Pop_OS-current.conf'/boot/efi/System
Volume Information':
I very much appreciate you taking the time to review my issue.
Thank you in advance and best wishes
You may be running into a known memory management bug that's fixed in a pre-release version described here:
https://sourceforge.net/p/refind/discussion/general/thread/09ef58e5a3/
Another possibility is that you're encountering a filesystem driver bug. Removing unnecessary filesystem drivers (from
/boot/efi/EFI/refind/drivers_x64, normally) can fix this problem; or you may need to run a filesystem check or even switch to another filesystem, at least to hold your kernel and associated files. (A ~1GB/bootpartition should be adequate for this.)