The rEFInd Boot Manager: Installing rEFInd The rEFInd Boot Manager: Installing rEFInd by Roderick W. Smith, Originally written: 3/14/2012; last Web page update:, referencing rEFInd 0.11.2 This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Donate $1.00 Donate $2.50 Donate $5.00 Donate $10.00 Donate $20.00 Donate another value This page is part of the documentation for the rEFInd boot manager. If a Web search has brought you here, you may want to start at the.
Don't be scared by the length of this page! Only portions of this page apply to any given user, and most people can install rEFInd from an RPM or Debian package in a matter of seconds or by using the refind-install script in minute or two. Once you've obtained a rEFInd binary file, as described on you must install it to your computer's EFI System Partition (ESP) (or conceivably to some other location).
The script has several options for handling differing setups and UEFI implementations, see refind-install(8). For many systems it should be sufficient to simply run: # refind-install. Scanfont 5 Keygen more. This will attempt to find and mount your ESP, copy rEFInd files to esp/EFI/refind/, and use efibootmgr to make rEFInd the default EFI boot. When you 'switch' to a.imgPTN file, the E2B partition disappears. So the _ISO folder and all other files are no longer present. The only reason to use imgPTN files.
The details of how you do this depend on your OS and your computer (UEFI-based PC vs. The upcoming sections provide details. See the Contents sidebar to the left for links to specific installation procedures.
For most Linux users, an RPM or Debian package is the best way to go. If your Linux system doesn't support these formats, though, or if you're running OS X, using the refind-install script can be a good way to go. If you're using Windows, you'll have to install manually. Important: A rEFInd zip file, when uncompressed, creates a directory called refind- version, where version is the version number. This directory includes a subdirectory called refind that holds the rEFInd binary along with another that holds documentation, as well as miscellaneous files in refind- version itself. When I refer to 'the refind directory' on this page, I mean the directory with that precise name, not the refind- version directory that is its parent.
Note: As of version 10.12 ('Sierra'), Apple has renamed its OS X OS to macOS. I continue to use 'OS X' to refer to any version of this OS. I've seen reports of rEFInd not working with macOS 10.12; however, my own experience is that it works fine—with the caveat that the upgrade produces a boot coup, as described on.
Hi, I'm running mint 14 with kernel 3.8.0 dual booting with bt5 kernel 3.2.6 I installed refind from the.deb package and it gave me this output: CAUTION: Your computer appears to support Secure Boot, but you haven't specified a valid shim.efi file source. If you've disabled Secure Boot and intend to leave it disabled, this is fine; but if Secure Boot is active, the resulting installation won't boot.
You can read more about this topic. I don't think secure boot is enabled since my laptop was shipped with windows 7. The Very Best Of Shocking Blue Download Movies. The problem is that there's no option to disable secure boot on this BIOS (Insyde H20) After I rebooted it was like nothing changed, GRUB show up as I never installed refind. Can you help me?
Code: wolf@blackbird ~ $ sudo efibootmgr -c -l ' EFI refind refind_x64.efi' -L rEFInd BootCurrent: 0000 BootOrder: 0001,0000 Boot0000* Windows Boot Manager Boot0001* rEFInd wolf@blackbird ~ $ sudo efibootmgr -v BootCurrent: 0000 BootOrder: 0001,0000 Boot0000* Windows Boot Manager HD(1,800,2f000,d2553afc-f274-4dc7-80e3-3bda881ba3d0)File( EFI Microsoft Boot bootmgfw.efi)RC Boot0001* rEFInd HD(1,800,2f000,d2553afc-f274-4dc7-80e3-3bda881ba3d0)File( EFI refind refind_x64.efi) wolf@blackbird ~ $ After reboot. Cyberwolf, It seems you've got a broken EFI that's dropping changes to its NVRAM. (Or looked at another way, there's a bug in efibootmgr that prevents it from working with your firmware.) There are several possible solutions to this problem: • Boot to an EFI version 2 shell and use its 'bcfg' command to add rEFInd to the boot list. This sometimes works when efibootmgr doesn't. This is a little complex, though.