amicose wrote:Both Grub and Refind bring up the bkpbootmgfw.efi (or however it's called), which does boot straight into Windows. Selecting Mint however still boots into Grub- how can I get it to boot directly into Mint?
You need to make rEFInd boot the Linux kernel directly. This requires three things:
- rEFInd must be able to "see" the kernel. This means that either /boot must be on a filesystem that the EFI can read or you must copy the kernel (and its associated initrd file) to a partition that the EFI can read. I know this is vague, but without knowing how your system is partitioned and what filesystems you use, I can't be much more specific.
- The "scan_all_linux_kernels" option must be uncommented in refind.conf. This is the default with recent versions of rEFInd, so it shouldn't be necessary to take this action unless you've changed refind.conf or are using an old version of rEFInd (or a newer version installed over an older one).
- You need to feed the correct options to the kernel. This is most easily done by creating a file called refind_linux.conf in the same directory that holds the kernels (normally /boot; but if you copy them elsewhere to satisfy the first condition, refind_linux.conf should be in that location). This file should be created automatically by install.sh, but if it's missing, you can run mkrlconf.sh, as in "sudo mkrlconf.sh", to do this; or you can create refind_linux.conf manually, as described here.
Ordinarily, the rEFInd install.sh script sets all of these things up correctly; however, if there's a bug or if your configuration is strange, it might not work. ("Strange" could be, for instance, if you use an LVM or RAID setup and don't have a separate /boot partition or if you use something other than ext2/3/4fs or ReiserFS on /boot [or root (/) if you don't have a separate /boot partition]).
The most likely problem is with the first point. rEFInd includes drivers for ext2/3/4fs and ReiserFS, but if they weren't installed with rEFInd, the EFI won't be able to read your /boot directory or partition. Thus, you may need to check for the presence of the relevant file and, if it's absent, install it. See the rEFInd drivers documentation
for more details.
One other point: In some cases you might not see all the entries on the screen simultaneously. This happens if you have more boot loaders than there is available space on the screen to show them. In these cases you should see a green arrow to the right (or possibly the left) of the display. When you use the arrow keys to move past the edge of the display, it will scroll, showing you whatever entries are hidden. It's conceivable that rEFInd is finding your kernels but you're just not seeing them for this reason. Chances are your Mint kernels will show up with generic Linux "Tux" penguin icons.
And will I need to reinstall Refind or will it automatically scan for all valid efi files?
rEFInd makes a fresh scan every time it boots, so you won't need to re-install it.
Also it would be good to change the resolution of the Refind screen (it's in 800x600 or near enough, whch doesn't even display all the text) - where do I find the refind.conf file?
It's in the directory where the rEFInd binary lives -- normally /boot/efi/EFI/refind; but you might have moved it elsewhere, such as /boot/efi/EFI/BOOT or even /boot/efi/EFI/Microsoft/Boot.
OK, I found the /boot/efi/EFI/Microsoft/Boot directory. But - I still don't know how to move/rename files in Linux for which I don't have permissions!
Use "sudo", as in "sudo mv foo.txt bar.txt".