Update causes problem with rEFInd bootloader

[hci]

Hi,
after updating my (dual-boot win +) xfce-system from Stable Update 2024-12-16 to Stable Update 2025-02-16 rEFInd bootloader does not replace grub as before. I already de- and reinstalled refind and manjaro-refind-installer with no success. Any advice would be appreciated. Thanks

[doctorx]

sounds like it got replaced in efi. You may want to double check your bios settings and install efibootmgr and make sure there is still and entry for it. Also, i am not sure, but try running mkinitcpio -P and see if that helps.

[soundofthunder]

@hci

rEFInd bootloader does not replace grub as before

It’s possible that an update of Windows or of Manjaro’s Grub has reset the default boot entry in BIOS.

Reinstalling rEFInd, and then booting to your BIOS to make sure rEFInd UEFI Bootloader is selected as first in boot order, should correct that.

---

To avoid this happening again, consider installing rEFInd to the fallback location (i.e: $ESP/EFI/BOOT) – All files currently in $ESP/EFI/refind would then reside under $ESP/EFI/BOOT instead.

Generally, another OS will not write it’s EFI boot files to the fallback location when it differs from the main boot file (example when $ESP/EFI/Manjaro/grubx64.efi differs from $ESP/EFI/boot/refind_x64.efi) and when rEFInd is then set as the default bootloader, it tends to stay that way.

(I’ve been doing exactly this for many years.)

The following is taken from my related article [Multiboot] Windows and Linux on Separate Disks:

BOOT PRIORITY ‘HIJACKING’

Some Linux distributions (such as Debian) cause the boot priority to be reset after every update.If you are multibooting another Linux flavour along with Manjaro/Windows, it may be beneficial to move rEFInd to the default/fallback location $esp/EFI/BOOT to ensure it isn’t affected.

The ArchWiki outlines a procedure for this under rEFInd - 3.2 Manual installation ; although, it seems to lack any clear direction.

This author found it much simpler to first copy/rename the rEFInd EFI executable to the default/fallback location;

sudo cp /usr/share/refind/refind_x64.efi /boot/efi/EFI/BOOT/bootx64.efi

→ and then immediately boot from a Manjaro Live Installer DVD/USB and manually move the content of {$esp}/EFI/refind/ to {$esp}/EFI/BOOT/; and finally, delete the original (now empty) {$esp}/EFI/refind directory.

More in-depth information can be found on Rod Smith’s site The rEFInd Boot Manager and specifically Keeping rEFInd Booting.

---

@hci

I already de- and reinstalled refind and manjaro-refind-installer with no success.

Note that despite it’s name manjaro-refind-installer actually has little to do with installing rEFInd. However, you can use this package to easily select the kernel rEFInd should boot.

Beyond that, it’s usefulness is questionable.

---

Do this for a typical rEFInd installation from Manjaro:

1. Install the rEFind package from the official Manjaro repo:

sudo pacman -S refind

2(a). Install rEFInd to the usual location (/ESP/refind):

sudo refind-install

…or…

2(b). Install rEFInd to the fallback location (/EFI/BOOT):

sudo refind-install --usedefault /dev/sdXY

• Change /dev/sdXY to your $ESP partition.
• Installation with refind-install script (Arch Wiki)

---

I hope this helps.

Regards.

---

(Note:- it’s also possible you have another issue entirely.)