Roderick W. Smith

If your kernel is the Linux/kde-linux_202501310256+3.efi file on your ESP, then setting the following line in refind.conf should get it detected: also_scan_dirs +,Linux Be sure that there's no later also_scan_dirs line in refind.conf. If this doesn't work, then you might try installing and launching an EFI shell. You can then poke around in the shell to see if that file really is a kernel with an EFI stub loader; you should be able to launch it by typing its name, and if it doesn't launch, you may...

That's not really possible. rEFInd runs under EFI, which has a completely different naming convention from Linux. That is, /dev/sda1 is a Linux partition name that is not retrievable from EFI. In theory, I could poach the Linux kernel's naming code for use in rEFInd, in the hopes of getting the same results; but even that would not be guaranteed to work because of differences in drivers -- a disk might show up in Linux but not the EFI, which would throw off the naming convention. Even the partition...

I don't think the problem is an encrypted /boot partition, since rEFInd does work when loaded from an external USB flash drive. What filesystem is used for the rEFInd install (the ESP)? On a Mac, that must be FAT or HFS+, and it must not be encrypted. Kali should have set it up correctly, but it's worth double-checking. Also, what partition table is used on the disk, GPT or MBR? If it's MBR, then the Mac's firmware will default to BIOS/CSM/legacy mode and won't load any EFI-mode boot program. Macs,...

rEFInd relies on the EFI to set the screen resolution, and the EFI in turn relies on whatever video drivers it can find (typically in the motherboard or video card). These resolutions are limited in number, and aren't guaranteed to match your monitor's optimal resolution (although that's usually one of the ones that's available); you can't just set an arbitrary resolution. If you're using a UEFI-based PC, the failure message when you try to use an unsupported video mode should show a list of supported...

This is almost certainly a filesystem issue -- either damage to the filesystem caused by the resize or restore operation or a bug in the filesystem driver. I recommend running disk checks (with fsck) on the filesystems you modified. If that doesn't help, then as a diagnostic measure, try removing the rEFInd filesystem drivers (from the ESP's EFI/refind/drivers_x64 directory). If that helps, then you can try restoring only the one that you need to read the kernel. If the problem recurs, then it's...

Fixed incorrect terminology about the Windows fast startup feature in documentation

The volume line must come before the loader line in manual boot stanzas. Chances are that's the problem; your configuration put them in the wrong order.

I'm afraid that's not supported at the moment; it would require significant changes to rEFInd's screen-display code.