rEFInd Boot Manager seems abandoned. Maybe remove it from CachyOS?

[HardCode4All]

I am currently in a pretty awkward situation where I cannot boot into the latest kernel (and I’m scared to upgrade the LTS kernel, too).

The kernel panic message looks like there could be a problem with rEFInd, but we are not really sure.

While poking around, I just realized that rEFInd seems to be completely abandoned. The last update is nearly two years ago!

Question to the Cachy team ( @ptr1337 ): maybe CachyOS should drop support for the rEFInd Boot Manager? Looks like a dead horse to me.

[YoYo-a11]

I chose rEFind for the initial installation a year ago. My multiboot (2xW10, CachyOS) system was automatically detected without any intervention from me, and it has worked flawlessly ever since. I didn’t have to study any how-to guides. I’m not against education ; I mean it just works.

If rEFind is discontinued, please remember to provide detailed instructions for migrating from rEFind to other boot managers.

[cscs]

Seems its not dead yet..

Latest NEWS.txt;

0.14.3 (?/??/2026):

• Fixed bug in refind-mkdefault that would cause it to crash if the
  BootOrder variable contained a pointer to a non-exitent Boot#### entry.

• Added icon for ArcaOS (icons/os_aos.png).

• Make writes of LoaderDevicePartUUID EFI variable non-persistent, to
  minimize wear-and-tear on NVRAM.

• Somewhere between versions 2.45 and 2.45.50.20251209 of objcopy, the
  –target option to objcopy changed subtly, which broke the GNU-EFI build
  process. I’ve worked around this by using --output-target instead.

And commit history;

rEFInd / Code Commit Log

[HardCode4All]

Ah okay I see. So let’s pretend I never asked that Will close the thread, although I am still stuck on my Kernel Panic scenario for whatever reason that may be

@YoYo-a11

If rEFind is discontinued, please remember to provide detailed instructions for migrating from rEFind to other boot managers.

There are already some in this forum somewhere, I believe.