code.delx.au - refind/blob - docs/refind/installing.html

   1 <?xml version="1.0" encoding="utf-8" standalone="no"?>
   2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
   3   "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
   4
   5 <html xmlns="http://www.w3.org/1999/xhtml">
   6 <head>
   7   <title>The rEFInd Boot Manager: Installing rEFInd</title>
   8   <link href="../Styles/styles.css" rel="stylesheet" type="text/css" />
   9 </head>
  10
  11 <meta name="viewport" content="width=device-width, initial-scale=1">
  12
  13 <body>
  14   <h1>The rEFInd Boot Manager:<br />Installing rEFInd</h1>
  15
  16 <p class="subhead">by Roderick W. Smith, <a
  17 href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
  18
  19 <p>Originally written: 3/14/2012; last Web page update:
  20 3/1/2015, referencing rEFInd 0.8.7</p>
  21
  22
  23 <p>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. Thanks!</p>
  24
  25 <table border="1">
  26 <tr>
  27 <td>Donate $1.00</td>
  28 <td>Donate $2.50</td>
  29 <td>Donate $5.00</td>
  30 <td>Donate $10.00</td>
  31 <td>Donate $20.00</td>
  32 <td>Donate another value</td>
  33 </tr>
  34 <tr>
  35
  36 <td>
  37 <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
  38 <input type="hidden" name="cmd" value="_donations">
  39 <input type="hidden" name="business" value="rodsmith@rodsbooks.com">
  40 <input type="hidden" name="lc" value="US">
  41 <input type="hidden" name="no_note" value="0">
  42 <input type="hidden" name="currency_code" value="USD">
  43 <input type="hidden" name="amount" value="1.00">
  44 <input type="hidden" name="item_name" value="rEFInd Boot Manager">
  45 <input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
  46 <input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
  47 <img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
  48 </form>
  49 </td>
  50
  51 <td>
  52 <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
  53 <input type="hidden" name="cmd" value="_donations">
  54 <input type="hidden" name="business" value="rodsmith@rodsbooks.com">
  55 <input type="hidden" name="lc" value="US">
  56 <input type="hidden" name="no_note" value="0">
  57 <input type="hidden" name="currency_code" value="USD">
  58 <input type="hidden" name="amount" value="2.50">
  59 <input type="hidden" name="item_name" value="rEFInd Boot Manager">
  60 <input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
  61 <input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
  62 <img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
  63 </form>
  64 </td>
  65
  66
  67 <td>
  68 <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
  69 <input type="hidden" name="cmd" value="_donations">
  70 <input type="hidden" name="business" value="rodsmith@rodsbooks.com">
  71 <input type="hidden" name="lc" value="US">
  72 <input type="hidden" name="no_note" value="0">
  73 <input type="hidden" name="currency_code" value="USD">
  74 <input type="hidden" name="amount" value="5.00">
  75 <input type="hidden" name="item_name" value="rEFInd Boot Manager">
  76 <input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
  77 <input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
  78 <img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
  79 </form>
  80 </td>
  81
  82 <td>
  83 <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
  84 <input type="hidden" name="cmd" value="_donations">
  85 <input type="hidden" name="business" value="rodsmith@rodsbooks.com">
  86 <input type="hidden" name="lc" value="US">
  87 <input type="hidden" name="no_note" value="0">
  88 <input type="hidden" name="currency_code" value="USD">
  89 <input type="hidden" name="amount" value="10.00">
  90 <input type="hidden" name="item_name" value="rEFInd Boot Manager">
  91 <input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
  92 <input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
  93 <img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
  94 </form>
  95 </td>
  96
  97 <td>
  98 <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
  99 <input type="hidden" name="cmd" value="_donations">
 100 <input type="hidden" name="business" value="rodsmith@rodsbooks.com">
 101 <input type="hidden" name="lc" value="US">
 102 <input type="hidden" name="no_note" value="0">
 103 <input type="hidden" name="currency_code" value="USD">
 104 <input type="hidden" name="amount" value="20.00">
 105 <input type="hidden" name="item_name" value="rEFInd Boot Manager">
 106 <input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
 107 <input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
 108 <img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
 109 </form>
 110 </td>
 111
 112 <td>
 113 <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
 114 <input type="hidden" name="cmd" value="_donations">
 115 <input type="hidden" name="business" value="rodsmith@rodsbooks.com">
 116 <input type="hidden" name="lc" value="US">
 117 <input type="hidden" name="no_note" value="0">
 118 <input type="hidden" name="currency_code" value="USD">
 119 <input type="hidden" name="item_name" value="rEFInd Boot Manager">
 120 <input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
 121 <input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
 122 <img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
 123 </form>
 124 </td></tr>
 125 </table>
 126
 127 <hr />
 128
 129 <p>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 <a href="index.html">main page.</a></p>
 130
 131 <hr />
 132
 133 <div style="float:right; width:55%">
 134
 135 <p><b>Don't be scared by the length of this page!</b> 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 <tt>install.sh</tt> script in minute or two.</p>
 136
 137 <p>Once you've obtained a rEFInd binary file, you must install it to your computer's EFI System Partition (ESP) (or conceivably to some other location). The details of how you do this depend on your OS and your computer (UEFI-based PC vs. Macintosh). 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 <tt>install.sh</tt> script can be a good way to go. If you're using Windows, you'll have to install manually.</p>
 138
 139 <p class="sidebar" style="width:95%"><b>Important:</b> A rEFInd zip file, when uncompressed, creates a directory called <tt>refind-<i>version</i></tt>, where <tt><i>version</i></tt> is the version number. This directory includes a subdirectory called <tt>refind</tt> that holds the rEFInd binary along with another that holds documentation, as well as miscellaneous files in <tt>refind-<i>version</i></tt> itself. When I refer to "the <tt>refind</tt> directory" on this page, I mean the directory with that precise name, not the <tt>refind-<i>version</i></tt> directory that is its parent.</p>
 140
 141 </div>
 142
 143 <div class="navbar">
 144
 145 <h4 class="tight">Contents</h4>
 146
 147 <ul class="tight">
 148
 149 <li class="tight"><a href="#packagefile">Installing rEFInd using an RPM or Debian package file</a></li>
 150
 151 <li class="tight"><a href="#installsh">Installing rEFInd Using <tt>install.sh</tt> under Linux or Mac OS X</a>
 152
 153    <ul class="tight">
 154
 155    <li class="tight"><a href="#quickstart">Quick <tt>install.sh</tt> Instructions</a></li>
 156
 157    <li class="tight"><a href="#extra_installsh">Extra <tt>install.sh</tt> Instructions</a></li>
 158
 159    </ul></li>
 160
 161 <li class="tight"><a href="#manual">Installing rEFInd Manually</a>
 162
 163    <ul>
 164
 165    <li class="tight"><a href="#linux">Installing rEFInd Manually Using Linux</a></li>
 166
 167    <li class="tight"><a href="#osx">Installing rEFInd Manually Using Mac OS X</a></li>
 168
 169    <li class="tight"><a href="#windows">Installing rEFInd Manually Using Windows</a></li>
 170
 171    <li class="tight"><a href="#efishell">Installing rEFInd Manually Using an EFI Shell</a></ul></li>
 172
 173 <li class="tight"><a href="#naming">Alternative Naming Options</a>
 174
 175    <ul>
 176
 177    <li class="tight"><a href="#mvrefind">Using <tt>mvrefind.sh</tt></li>
 178
 179    <li class="tight"><a href="#manual_renaming">Renaming Files Manually</li>
 180
 181    </ul></li>
 182
 183 <li class="tight"><a href="#upgrading">Upgrading rEFInd</a></li>
 184
 185 <li class="tight"><a href="#addons">Installing Additional Components</a></li>
 186
 187 <li class="tight"><a href="#sluggish">Fixing a  Macintosh Boot</a>
 188
 189    <ul>
 190
 191    <li class="tight"><a href="#shortform">Using the <tt>--shortform</tt> Option</a></li>
 192
 193    <li class="tight"><a href="#fallback">Using the Fallback Filename</a></li>
 194
 195    <li class="tight"><a href="#moving">Moving rEFInd to an HFS+ Volume</a></li>
 196
 197    <li class="tight"><a href="#clearing">Clearing the NVRAM Entries</a></li>
 198
 199    <li class="tight"><a href="#wakeprobs">Fixing Wake Problems</a></li>
 200
 201    <li class="tight"><a href="#nolinux">Fixing a Failure to Find Linux</a></li>
 202
 203    </ul></li>
 204
 205 <li class="tight"><a href="#winprob">Fixing Windows Boot Problems</a></li>
 206
 207 <li class="tight"><a href="#uninstalling">Uninstalling rEFInd</a>
 208
 209    <ul>
 210
 211    <li class="tight"><a href="#uinst_linux">Uninstalling rEFInd from Linux</a></li>
 212
 213    <li class="tight"><a href="#uinst_osx">Uninstalling rEFInd from OS X</a></li>
 214
 215    <li class="tight"><a href="#uinst_windows">Uninstalling rEFInd from Windows</a></li>
 216
 217    <li class="tight"><a href="#post_uninst">Post-Uninstallation Activity (UEFI-Based PCs)</a></li>
 218
 219 </ul></ul></li>
 220
 221 </div>
 222
 223 <a name="packagefile">
 224 <h2>Installing rEFInd Using an RPM or Debian Package File</h2>
 225 </a>
 226
 227 <p>I provide RPM and Debian package files for rEFInd; and starting with version 0.8.1, I'm maintaining an Ubuntu PPA for rEFInd. If you have a working RPM-based or Debian-based Linux installation that boots in EFI mode, using one of these files is likely to be the easiest way to install rEFInd: You need only download the file and issue an appropriate installation command. In some cases, double-clicking the package in your file manager will install it. If that doesn't work, a command like the following will install the RPM on an RPM-based system:</p>
 228
 229 <pre class="listing"># <tt class="userinput">rpm -Uvh refind-0.8.7-1.x86_64.rpm</tt></pre>
 230
 231 <p>On a Debian-based system, the equivalent command is:</p>
 232
 233 <pre class="listing"># <tt class="userinput">dpkg -i refind_0.8.7-1_amd64.deb</tt></pre>
 234
 235 <p>Either command produces output similar to that described for <a href="#installsh">using the <tt>install.sh</tt> script,</a> so you can check it for error messages and other signs of trouble. The package file installs rEFInd and registers it with the EFI to be the default boot loader. The script that runs as part of the installation process tries to determine if you're using Secure Boot, and if so it will try to configure rEFInd to launch using shim; however, this won't work correctly on all systems. Ubuntu 12.10 users who are booting with Secure Boot active should be wary, since the resulting installation will probably try to use Ubuntu's version of shim, which won't work correctly with rEFInd. The shim program provided with more recent versions of Ubuntu should work correctly.</p>
 236
 237 <a name="ppa">
 238 <p>If you're using Ubuntu, you should be able to install the PPA as follows:</p></a>
 239
 240 <pre class="listing">$ <tt class="userinput">sudo apt-add-repository ppa:rodsmith/refind</tt>
 241 $ <tt class="userinput">sudo apt-get update</tt>
 242 $ <tt class="userinput">sudo apt-get install refind</tt></pre></pre>
 243
 244 <p>The PPA version will update automatically with your other software, which you might or might not want to have happen. It's also built with GNU-EFI rather than with TianoCore. This last detail <i>should</i> have no practical effects, but it might be important if you've got a buggy EFI or if there's some undiscovered rEFInd bug that interacts with the build environment.</p>
 245
 246 <p>Since version 0.6.3, the installation script makes an attempt to install rEFInd in a bootable way even if you run the script from a BIOS-mode boot, and therefore the RPM and Debian packages do the same. I cannot guarantee that this will work, though, and even if it does, some of the tricks that <tt>install.sh</tt> uses might not persist for long. You might therefore want to use <tt><a href="#mvrefind">mvrefind.sh</a></tt> to move your rEFInd installation to another name after you boot Linux for the first time from rEFInd.</p>
 247
 248 <p>Since version 0.6.2-2, my package files have installed the rEFInd binaries to <tt>/usr/share/refind-<tt class="variable">version</tt></tt>, the documentation to <tt>/usr/share/doc/refind-<tt class="variable">version</tt></tt>, and a few miscellaneous files elsewhere. (The PPA package omits the version number from the file paths.) Upon installation, the package runs the <tt>install.sh</tt> script to copy the files to the ESP. This enables you to re-install rEFInd after the fact by running <tt>install.sh</tt>, should some other tool or OS wipe the ESP or should the installation go awry. In such cases you can <a href="#installsh">use <tt>install.sh</tt></a> or <a href="#manual">install manually.</a></p>
 249
 250 <a name="installsh">
 251 <h2>Installing rEFInd Using <tt>install.sh</tt> under Linux or Mac OS X</h2>
 252
 253 <p class="sidebar"><b>Warning:</b> If you're using a Macintosh, you should run <tt>install.sh</tt> from Mac OS X rather than from Linux. If run from Linux, rEFInd is unlikely to be fully installed. The reason is that Apple uses non-standard methods to enable a boot loader, and the Linux functions in <tt>install.sh</tt> assume standard EFI installation methods.</p>
 254
 255 <p>If you're using Linux or Mac OS X, the easiest way to install rEFInd is to use the <tt>install.sh</tt> script. This script automatically copies rEFInd's files to your ESP or other target location and makes changes to your firmware's NVRAM settings so that rEFInd will start the next time you boot. If you've booted to OS X or in non-Secure-Boot EFI mode to Linux on a UEFI-based PC, <tt>install.sh</tt> will probably do the right thing, so you can get by with the quick instructions. If your setup is unusual, if your computer uses Secure Boot, or if you want to create a USB flash drive with rEFInd on it, you should read the <a href="#extra_installsh">extra instructions</a> for this utility.</p>
 256
 257 <a name="quickstart">
 258 <h3>Quick <tt>install.sh</tt> Instructions</h3>
 259 </quickstart>
 260
 261 <p>By default, the <tt>install.sh</tt> script installs rEFInd to your disk's ESP. Under Mac OS X, you can instead install rEFInd to your current OS X boot partition by passing the script the <tt>--notesp</tt> option, or to a non-boot HFS+ partition by using the <tt>--ownhfs <tt class="variable">devicefile</tt></tt> option. Under either OS, you can install to something other than the currently-running OS by using the <tt>--root <tt class="variable">/mountpoint</tt></tt> option. (See <a href="#table1">Table 1</a> for details.)</p>
 262
 263 <p>Under Linux, <tt>install.sh</tt> will be most reliable if your ESP is already mounted at <tt>/boot</tt> or <tt>/boot/efi</tt>, as described in more detail in the <a href="#linux">Installing rEFInd Manually Using Linux</a> section. (If you installed Linux in EFI mode, chances are your ESP is properly mounted.) If your ESP is not so mounted, <tt>install.sh</tt> will attempt to locate and mount an ESP, but this action is not guaranteed to work correctly. If you run <tt>install.sh</tt> from a BIOS/legacy-mode boot, particularly on a computer that also runs Windows, you should be aware that the tricks the script uses to install itself from BIOS mode are rather delicate. You can convert to a more conventional configuration using the <a href="#mvrefind"><tt>mvrefind.sh</tt> script</a> after you've booted in EFI mode.</p>
 264
 265 <p>Prior to version 0.8.4, <tt>install.sh</tt> installed rEFInd to the OS X root partition by default. I changed this because the default configuration for OS X 10.10 ("Yosemite") makes this placement unusable. Instead, <tt>install.sh</tt> now installs to the ESP under OS X, just as it does under Linux. <i>If you're upgrading a working install of rEFInd to the OS X root partition, it's best to pass the <tt>--notesp</tt> option to <tt>install.sh</tt>.</i> This option is described in more detail shortly.</p>
 266
 267 <p>A sample run under Linux looks something like this:</p>
 268
 269 <pre class="listing">
 270 # <tt class="userinput">./install.sh</tt>
 271 Installing rEFInd on Linux....
 272 ESP was found at /boot/efi using vfat
 273 Installing driver for ext4 (ext4_x64.efi)
 274 Copied rEFInd binary files
 275
 276 Copying sample configuration file as refind.conf; edit this file to configure
 277 rEFInd.
 278
 279
 280 Installation has completed successfully.</pre>
 281
 282 <p>The output under OS X is a bit different:</p>
 283
 284 <pre class="listing">
 285 $ <tt class="userinput">./install.sh</tt>
 286 Not running as root; attempting to elevate privileges via sudo....
 287 Password:
 288 Installing rEFInd on OS X....
 289 Installing rEFInd to the partition mounted at /Volumes/ESP
 290 Found suspected Linux partition(s); installing ext4fs driver.
 291 Installing driver for ext4 (ext4_ia32.efi)
 292 Copied rEFInd binary files
 293
 294 Copying sample configuration file as refind.conf; edit this file to configure
 295 rEFInd.
 296
 297
 298 WARNING: If you have an Advanced Format disk, *DO NOT* attempt to check the
 299 bless status with 'bless --info', since this is known to cause disk corruption
 300 on some systems!!
 301
 302
 303 Installation has completed successfully.
 304
 305 Unmounting install dir</pre>
 306
 307 <p>In either case, the details of the output differ depending on your existing configuration and how you ran the program. Unless you see an obvious warning or error, you shouldn't be concerned about minor deviations from these examples. If you run into such a situation, or if you want to install in an unusual way, read on....</p>
 308
 309 <p>Note that the change to an ESP location for rEFInd with version 0.8.4 means that, if you upgrade rEFInd from an earlier version, you may notice a rEFInd boot option in the rEFInd menu. This option will boot the old version of rEFInd (or the new one, if something went wrong and the old version continues to boot). You can rid yourself of the unwanted boot menu by deleting the old files or by using <tt>dont_scan_dirs</tt> or <tt>dont_scan_files</tt> in <tt>refind.conf</tt>. Before you do this, you should use rEFInd to identify the unwanted files&mdash;the filename and volume identifier appear under the icons when you highlight the option. You can then locate and delete them from within OS X. Before you delete the old files, though, you may want to copy over any changes you've made to the rEFInd configuration, icons, and other support files.</p>
 310
 311 <a name="extra_installsh">
 312 <h3>Extra <tt>install.sh</tt> Instructions</h3>
 313 </a>
 314
 315 <p>Some details that can affect how the script runs include the following:</p>
 316
 317 <ul>
 318
 319 <li>If you run the script as an ordinary user, it attempts to acquire
 320     <tt>root</tt> privileges by using the <tt>sudo</tt> command. This works
 321     on Mac OS X and some Linux installations (such as under Ubuntu or if
 322     you've added yourself to the <tt>sudo</tt> users list), but on some
 323     Linux installations this will fail. On such systems, you should run
 324     <tt>install.sh</tt> as <tt>root</tt>.</li>
 325
 326 <li>Under OS X, you can run the script with a mouse by opening a Terminal
 327     session and then dragging-and-dropping the <tt>install.sh</tt> file to
 328     the Terminal window. You'll need to press the Return or Enter key to
 329     run the script.</li>
 330
 331 <li>If you're using OS X 10.7's Whole Disk Encryption (WDE) feature, or the
 332     loogical volumes feature in OS X 10.10, you <i>must</i> install rEFInd
 333     to the ESP or to a separate HFS+ partition. The default in rEFInd 0.8.4
 334     and later is to install to the ESP. If you prefer to use a separate
 335     HFS+ volume, the <tt>--ownhfs <tt
 336     class="variable">device-file</tt></tt> option to <tt>install.sh</tt> is
 337     required.</li>
 338
 339 <li>If you're <i>not</i> using WDE or logical volumes, you can install
 340     rEFInd to the OS X root (<tt>/</tt>) partition by using the
 341     <tt>--notesp</tt> option to <tt>install.sh</tt>. Using this option is
 342     recommended when upgrading from a working rEFInd installation in this
 343     location.</li>
 344
 345 <li>If you're replacing rEFIt with rEFInd on a Mac, there's a chance that
 346     <tt>install.sh</tt> will warn you about the presence of a program
 347     called <tt>/Library/StartupItems/rEFItBlesser</tt> and ask if you want
 348     to delete it. This program is designed to keep rEFIt set as the boot
 349     manager by automatically re-blessing it if the default boot manager
 350     changes. This is obviously undesirable if you install rEFInd as your
 351     primary boot manager, so it's generally best to remove this program. If
 352     you prefer to keep your options open, you can answer <tt
 353     class="userinput">N</tt> when <tt>install.sh</tt> asks if you want to
 354     delete rEFItBlesser, and instead manually copy it elsewhere. If you
 355     subsequently decide to go back to using rEFIt as your primary boot
 356     manager, you can restore rEFItBlesser to its place.</li>
 357
 358 <li>If you're using OS X and an Advanced Format disk, heed the warning that
 359     <tt>install.sh</tt> displays and <i><b>do not</b></i> use <tt>bless
 360     --info</tt> to check your installation status; this combination has
 361     been reported to cause disk corruption on some Macs!</li>
 362
 363 <li>If you intend to boot BIOS-based OSes on a UEFI-based PC, you
 364     <i>must</i> edit the <tt>refind.conf</tt> file's <tt>scanfor</tt> line
 365     to enable the relevant searches. This is <i>not</i> necessary on Macs,
 366     though; because of the popularity of dual boots with Windows on Macs,
 367     the BIOS/legacy scans are enabled by default on Macs.</li>
 368
 369 <li>On Linux, <tt>install.sh</tt> checks the filesystem type of the
 370     <tt>/boot</tt> directory and, if a matching filesystem driver is
 371     available, installs it. Note that the "<tt>/boot</tt> directory" may be
 372     on a separate partition or it may be part of your root (<tt>/</tt>)
 373     filesystem, in which case the driver for your root filesystem is
 374     installed. This feature is unlikely to work properly from an emergency
 375     system, although it might if you have a separate <tt>/boot</tt>
 376     partition and if you mount that partition at <tt>/boot</tt> in your
 377     emergency system, and the ESP at <tt>/boot/efi</tt>.</li>
 378
 379 <li>On OS X, <tt>install.sh</tt> checks your partition tables for signs of
 380     a Linux installation. If such a sign is found, the script installs the
 381     EFI filesystem driver for the Linux ext4 filesystem. This will enable
 382     rEFInd to read your Linux kernel <i>if</i> it's on an ext2, ext3, or
 383     ext4 filesystem. Note that some configurations will require a
 384     <tt>/boot/refind_linux.conf</tt> file, which can be reliably generated
 385     only under Linux. (The <tt>mkrlconf.sh</tt> script that comes with
 386     rEFInd will do this job once you've booted Linux.) In the meantime, you
 387     can launch GRUB from rEFInd or press F2 or Insert twice after
 388     highlighting the Linux option in rEFInd. This will enable you to enter
 389     a <tt>root=/dev/<tt class="variable">whatever</tt></tt> specification,
 390     where <tt>/dev/<tt class="variable">whatever</tt></tt> is the device
 391     identifier of your Linux root (<tt>/</tt>) filesystem.
 392
 393 <li>If you run <tt>install.sh</tt> on Linux and if
 394     <tt>/boot/refind_linux.conf</tt> doesn't already exist,
 395     <tt>install.sh</tt> creates this file and populates it with a few
 396     sample entries. If <tt>/boot</tt> is on a FAT partition (or HFS+ on a
 397     Mac), or if it's on an ext2fs, ext3fs, ext4fs, ReiserFS, or HFS+
 398     partition and you install an appropriate driver, the
 399     result is that rEFInd will detect your kernel and will probably boot it
 400     correctly. Some systems will require manual tweaking to
 401     <tt>refind_linux.conf</tt>, though&mdash;for instance, to add
 402     <tt>dolvm</tt> to the boot options on Gentoo systems that use LVM.</li>
 403
 404 </ul>
 405
 406 <p>In addition to these quirks, you should be aware of some options that <tt>install.sh</tt> supports to enable you to customize your installation in various ways. The syntax for <tt>install.sh</tt> is as follows:</p>
 407
 408 <pre class="listing">
 409 install.sh [--notesp | --usedefault <tt class="variable">device-file</tt> | --root <tt class="variable">mount-point</tt> | \
 410             --ownhfs <tt class="variable">device-file</tt> ] \
 411            [--nodrivers | --alldrivers] [--shim <tt class="variable">shim-filename</tt>] [--localkeys] [--yes]
 412 </pre>
 413
 414 <p>The details of the options are summarized in <a href="#table1">Table 1.</a> Broadly speaking, they come in four classes: installation location options (<tt>--notesp</tt>, <tt>--usedefault</tt>, and <tt>--root</tt>), driver options (<tt>--nodrivers</tt> and <tt>--alldrivers</tt>), Secure Boot options (<tt>--shim</tt> and <tt>--localkeys</tt>), and a user input option (<tt>--yes</tt>). Using some of these options in unusual conditions can generate warnings and prompts to confirm your actions. In particular, using <tt>--shim</tt> or <tt>--localkeys</tt> when you're <i>not</i> booted in Secure Boot mode, or failing to use <tt>--shim</tt> when you <i>are</i> booted in Secure Boot mode, will generate a query and a request to confirm your installation. Consult the <a href="secureboot.html">Managing Secure Boot</a> page for more on this topic.</p>
 415
 416 <table border="1" cellpadding="1" cellspacing="2" summary="Table 1: Options to <tt>install.sh</tt>"><a name="table1"><caption><b>Table 1: Options to <tt>install.sh</tt></b></caption></a>
 417 <tr>
 418    <th>Option</th>
 419    <th>Explanation</th>
 420 </tr>
 421 <tr>
 422    <td><tt>--notesp</tt></td>
 423    <td>This option, which is valid only under OS X, tells <tt>install.sh</tt> to install rEFInd to the OS X root partition rather than to the ESP. This behavior was the default in rEFInd 0.8.3 and earlier, so you may want to use it when upgrading installations of that version, unless you used <tt>--esp</tt> (which is now the default behavior, although the <tt>--esp</tt> option no longer exists) or <tt>--ownhfs</tt>. You may also want to use <tt>--notesp</tt> on new installations if you're sure you're <i>not</i> using whole-disk encryption or logical volumes.</td>
 424 </tr>
 425 <tr>
 426    <td><tt>--usedefault <tt class="variable">device-file</tt></tt></td>
 427    <td>You can install rEFInd to a disk using the default/fallback filename of <tt>EFI/BOOT/bootx64.efi</tt> (and <tt>EFI/BOOT/bootia32.efi</tt>, if the 32-bit build is available) using this option. The <tt class="variable">device-file</tt> should be an <i>unmounted</i> ESP, or at least a FAT partition, as in <tt>--usedefault /dev/sdc1</tt>. Your computer's NVRAM entries will <i>not</i> be modified when installing in this way. The intent is that you can create a bootable USB flash drive or install rEFInd on a computer that tends to "forget" its NVRAM settings with this option. This option is mutually exclusive with <tt>--notesp</tt> and <tt>--root</tt>.</td>
 428 </tr>
 429 <tr>
 430    <td><tt>--ownhfs <tt class="variable">device-file</tt></tt></td>
 431    <td>This option should be used <i>only</i> under OS X. It's used to install rEFInd to an HFS+ volume <i>other than</i> a standard Mac boot volume. The result should be that rEFInd will show up in the Mac's own boot manager. More importantly, suspend-to-RAM operations may work correctly. Note that this option requires an HFS+ volume that is <i>not</i> currently an OS X boot volume. This can be a data volume or a dedicated rEFInd partition. The ESP might also work, if it's converted to use HFS+.</td>
 432 </tr>
 433 <tr>
 434    <td><tt>--root <tt class="variable">/mount-point</tt></tt></td>
 435    <td>This option is intended to help install rEFInd from a "live CD" or other emergency system. To use it, you should mount your regular installation at <tt class="variable">/mount-point</tt>, including your <tt>/boot</tt> directory (if it's separate) at <tt class="variable">/mount-point</tt><tt>/boot</tt> and (on Linux) your ESP at that location or at <tt class="variable">/mount-point</tt><tt>/boot/efi</tt>. The <tt>install.sh</tt> script then installs rEFInd to the appropriate location&mdash;on Linux, <tt class="variable">/mount-point</tt><tt>/boot/EFI/refind</tt> or <tt class="variable">/mount-point</tt><tt>/boot/efi/EFI/refind</tt>, depending on where you've mounted your ESP. Under OS X, this option is only useful in conjunction with <tt>--notesp</tt>, in which case rEFInd will install to <tt class="variable">/mount-point</tt><tt>/EFI/refind</tt>. The script also adds an entry to your NVRAM for rEFInd at this location. You cannot use this option with <tt>--usedefault</tt>. Note that this option is <i>not</i> needed when doing a dual-boot Linux/OS X installation; just install normally in OS X.</td>
 436 </tr>
 437 <tr>
 438    <td><tt>--nodrivers</tt></td>
 439    <td>Ordinarily <tt>install.sh</tt> attempts to install the driver required to read <tt>/boot</tt> on Linux. This attempt works only if you're using ext2fs, ext3fs, ext4fs, or ReiserFS on the relevant partition. If you want to forego this driver installation, pass the <tt>--nodrivers</tt> option. This option is the implicit when you use <tt>--usedefault</tt>.</td>
 440 </tr>
 441 <tr>
 442    <td><tt>--alldrivers</tt></td>
 443    <td>When you specify this option, <tt>install.sh</tt> copies <i>all</i> the driver files for your architecture. You may want to remove unused driver files after you use this option, especially if your computer uses Secure Boot. Note that some computers hang or fail to work with any drivers if you use this option, so use it with caution.</td>
 444 </tr>
 445 <tr>
 446    <td><tt>--shim <tt class="variable">shim-filename</tt></tt> or <tt>--preloader <tt class="variable">preloader-filename</tt></tt></td>
 447    <td>If you pass this option to <tt>install.sh</tt>, the script will copy the specified shim program file to the target directory, copy the <tt>MokManager.efi</tt> file from the shim program file's directory to the target directory, copy the 64-bit version of rEFInd as <tt>grubx64.efi</tt>, and register shim with the firmware. (If you also specify <tt>--usedefault</tt>, the NVRAM registration is skipped.) When the target file is identified as PreLoader, much the same thing happens, but <tt>install.sh</tt> copies <tt>HashTool.efi</tt> instead of <tt>MokManager.efi</tt> and copies rEFInd as <tt>loader.efi</tt> rather than as <tt>grubx64.efi</tt>. The intent is to simplify rEFInd installation on a computer that uses Secure Boot; when so set up, rEFInd will boot in Secure Boot mode, with one caveat: The first time you boot, MokManager/HashTool will launch, and you must use it to locate and install a public key or register rEFInd as a trusted application. The rEFInd public key file will be located in the rEFInd directory's <tt>keys</tt> subdirectory under the name <tt>refind.cer</tt>. Note that I'm not providing a shim binary myself, but you can download one from <a href="http://www.codon.org.uk/~mjg59/shim-signed/">here.</a> Some distributions also provide their own shim programs, so can point to them&mdash;for instance, in <tt>/boot/efi/EFI/fedora/shim.efi</tt>.</td>
 448 </tr>
 449 <tr>
 450    <td><tt>--localkeys</tt></td>
 451    <td>This option tells <tt>install.sh</tt> to generate a new Machine Owner Key (MOK), store it in <tt>/etc/refind.d/keys</tt> as <tt>refind_local.*</tt>, and re-sign all the 64-bit rEFInd binaries with this key before installing them. This is the preferable way to install rEFInd in Secure Boot mode, since it means your binaries will be signed locally rather than with my own key, which is used to sign many other users' binaries; however, this method requires that both the <tt>openssl</tt> and <tt>sbsign</tt> binaries be installed. The former is readily available in most distributions' repositories, but the latter is not, so this option is not the default.</td>
 452 </tr>
 453 <tr>
 454    <td><tt>--yes</tt></td>
 455    <td>This option causes the script to assume a <tt>Y</tt> input to every yes/no prompt that can be generated under certain conditions, such as if you specify <tt>--shim</tt> but <tt>install.sh</tt> detects no evidence of a Secure Boot installation. This option is intended mainly for use by scripts such as those that might be used as part of an installation via an RPM or Debian package.</td>
 456 </tr>
 457 </table>
 458
 459 <p>After you run <tt>install.sh</tt>, you should peruse the script's output to ensure that everything looks OK. <tt>install.sh</tt> displays error messages when it encounters errors, such as if the ESP is mounted read-only or if you run out of disk space. You may need to correct such problems manually and re-run the script. In some cases you may need to fall back on manual installation, which gives you better control over details such as which partition to use for installation.</p>
 460
 461 <a name="manual">
 462 <h2>Installing rEFInd Manually</h2>
 463 </a>
 464
 465 <p>Sometimes the <tt>install.sh</tt> script just won't do the job, or you may need to install using an OS that it doesn't support, such as Windows. In these cases, you'll have to install rEFInd the old-fashioned way, using file-copying commands and utilities to add the program to your EFI's boot loader list. I describe how to do this with <a href="#linux">Linux</a>, <a href="#osx">OS X</a>, <a href="#windows">Windows</a>, and <a href="#efishell">the EFI shell.</a></p>
 466
 467 <a name="linux">
 468 <h3>Installing rEFInd Manually Using Linux</h3>
 469 </a>
 470
 471 <p>On a UEFI-based PC, you'll normally install rEFInd to the ESP, which is usually mounted at <tt>/boot/efi</tt>. You can verify that this is the case by using the <tt>df</tt> command:</p>
 472
 473 <pre class="listing">
 474 $ <b>df /boot/efi</b>
 475 Filesystem     1K-blocks  Used Available Use% Mounted on
 476 /dev/sda1         191284 16604    174681   9% /boot/efi
 477 </pre>
 478
 479 <p class="sidebar"><b>Warning:</b> If you're running Linux on a Mac, I recommend you install rEFInd under OS X. The Mac's boot process deviates a bit from EFI standards, so you'll probably have to use a tool called <tt>bless</tt> under Mac OS to do the job. Alternatively, there's a new Linux program, <tt>hfs-bless</tt>, part of the <a href="http://www.codon.org.uk/~mjg59/mactel-boot/"><tt>mactel-boot</tt></a> RPM package or as part of the <a href="https://launchpad.net/~detly/+archive/ubuntu/mactel-utils">mactel-utils PPA for Ubuntu</a>, that's supposed to work with <tt>efibootmgr</tt> to make a Mac HFS partition bootable. I've not yet tried it, though. There are also reports that the <tt>efibootmgr</tt> tool used under Linux can corrupt some Macs' firmware. Although I've seen some vague suggestions that this problem has been fixed under 3.<i>x</i> kernels, I haven't tested this claim.</p>
 480
 481 <p>This example shows that <tt>/dev/sda1</tt> is mounted at <tt>/boot/efi</tt>, which is a typical configuration. (The ESP can be on another disk or partition, but <tt>/dev/sda1</tt> is the most common place for an ESP.) If your output shows <tt>/boot</tt> or <tt>/</tt> under the <tt>Mounted on</tt> column, then your ESP isn't mounted. (An exception is if you're mounting the ESP at <tt>/boot</tt>. This is an unusual configuration. If you're using it, you can proceed, making suitable adjustments to subsequent commands.) If you get a <tt>df: `/boot/efi': No such file or directory</tt> error message, then the <tt>/boot/efi</tt> directory doesn't even exist. In such cases, you may need to jump through some extra hoops, as described on my <a href="http://www.rodsbooks.com/efi-bootloaders/installation.html">EFI Boot Loader Installation</a> page.</p>
 482
 483 <p>Assuming the ESP is mounted at <tt>/boot/efi</tt>, you can install the rEFInd files as follows (you must be <tt>root</tt> to issue these commands, or precede each of them with <tt><b>sudo</b></tt>):</p>
 484
 485 <ol>
 486
 487 <li>Type <tt><b>cp -r refind /boot/efi/EFI/</b></tt> from the <tt>refind-<i>version</i></tt> directory in which the <tt>refind</tt> directory exists. This copies all the files that rEFInd needs to work. Note that this includes <i>all</i> of rEFInd's drivers. This command also copies the rEFInd binaries as signed by me; if you prefer to re-sign the binaries yourself, you'll have to do so before or during the copy operation, as described on the <a href="secureboot.html">Managing Secure Boot</a> page.</li>
 488
 489 <li>Type <tt><b>cd /boot/efi/EFI/refind</b></tt> to change into rEFInd's new directory on the ESP.</li>
 490
 491 <li>Type <tt><b>rm refind_ia32.efi</b></tt> to remove the IA32 binary if you're using an <i>x</i>86-64 (64-bit) system; or type <tt><b>rm refind_x64.efi</b></tt> to remove the <i>x</i>86-64 binary if you're using an <i>x</i>86 (32-bit) system. (Note that you must keep the version that's the correct bit width for your EFI; if you've installed a 32-bit Linux on a 64-bit PC with a 64-bit EFI, you'd keep <tt>refind_x64.efi</tt>.</li>
 492
 493 <li>Optionally, type <tt class="userinput">rm -r drivers_ia32</tt> to remove the <i>x</i>86 drivers from an <i>x</i>86-64 system, or <tt class="userinput">rm -r drivers_x64</tt> to remove the <i>x</i>86-64 drivers from a 32-bit <i>x</i>86 system. You may also want to remove some or all of the drivers for the architecture you are using. If you don't need them, they'll slow down the start process, and worse, loading unnecessary drivers can cause some systems to hang or interfere with the drivers you do need. See the <a href="drivers.html">page on drivers</a> for more on this topic.</li>
 494
 495 <li>Rename the configuration file by typing <tt><b>mv refind.conf-sample refind.conf</b></tt>. Consult the <a href="configfile.html">Editing the rEFInd Configuration File</a> page for information on how to adjust your options.</li>
 496
 497 <p class="sidebar"><b>Weird:</b> A <a href="http://mjg59.dreamwidth.org/20187.html">bug exists</a> in some Lenovo computers (and perhaps in some others, too) that causes the firmware's boot manager to refuse to boot any boot loader that doesn't have the name <tt>Windows Boot Manager</tt> or <tt>Red Hat Enterprise Linux</tt>. If you have such a system, you must pass one of those names (in quotes) rather than <tt>rEFInd</tt> to <tt>efibootmgr</tt> via its <tt>-L</tt> option. This bug was reported to Lenovo in mid-November 2012, and by late 2013, at least some Lenovos were mercifully free of this bug.</p>
 498
 499 <a name="efibootmgr">
 500 <li>On a UEFI-based system, type <tt><b>efibootmgr -c -l \\EFI\\refind\\refind_x64.efi -L rEFInd</b></tt> to add rEFInd to your EFI's list of available boot loaders, which it stores in NVRAM. Adjust the path to the binary as required if you install somewhere else. You may also need to include additional options if your ESP isn't on <tt>/dev/sda1</tt> or if your configuration is otherwise unusual; consult the <tt>efibootmgr</tt> man page for details. You may need to install this program on some systems; it's a standard part of most distributions' repositories. Also, if you're installing in Secure Boot mode, you must normally register <tt>shim.efi</tt> rather than the rEFInd binary, and rename <tt>refind_x64.efi</tt> to <tt>grubx64.efi</tt>.</li>
 501 </a>
 502
 503 <li>If other boot loaders are already installed, you can use <tt>efibootmgr</tt> to adjust their boot order. For instance, <b><tt>efibootmgr -o 3,7,2</tt></b> sets the firmware to try boot loader #3 first, followed by #7, followed by #2. (The program should have displayed a list of boot loaders when you added yours in the preceding step.) Place rEFInd's number first to set it as the default boot program.</li>
 504
 505 </ol>
 506
 507 <p>Note the use of doubled-up backslashes (<tt>\\</tt>) rather than forward slashes (<tt>/</tt>) in the directory separators when using <tt>efibootmgr</tt>. This command will work on most systems that are already booted into EFI mode; however, it won't work if you're booted in BIOS mode. You may also need to add options if your ESP is in some unusual location or if your system is unusual in some way. Consult the <tt>efibootmgr</tt> man page if you need help.</p>
 508
 509 <p>On some systems, <tt>efibootmgr</tt> won't do what you expect. On such systems, you may have better luck renaming the rEFInd files, as described in the <a href="#naming">Alternative Naming Options</a> section.</p>
 510
 511 <a name="osx">
 512 <h3>Installing rEFInd Manually Using Mac OS X</h3>
 513 </a>
 514
 515 <p>Before installing rEFInd on a Mac, you must determine whether it uses a 32-bit or 64-bit EFI implementation. Most Intel-based Macs have 64-bit EFIs, so you should use the <tt>refind_x64.efi</tt> file with them; but very early Intel-based Macs have 32-bit EFIs (and sometimes 32-bit CPUs), which require the <tt>refind_ia32.efi</tt> file. You can determine whether your Mac needs the <i>x</i>86-64 or IA32 build by typing the following command in a Mac Terminal window:</p>
 516
 517 <pre class="listing">
 518 $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
 519 </pre>
 520
 521 <p>The result should include either <tt>EFI32</tt> or <tt>EFI64</tt>, indicating that you should use the <tt>refind_ia32.efi</tt> or <tt>refind_x64.efi</tt> binary, respectively.</p>
 522
 523 <p>You should also be aware of your OS X version and installation options. If you used whole-disk encryption (WDE) or a logical volume for installation, you <i>cannot</i> install to the OS X root partition; you <i>must</i> install to the ESP or to a separate HFS+ partition. WDE became an option with OS X 10.7 and logical volumes are the default in OS X 10.10. If in doubt, proceed with an installation to the ESP or to a separate HFS+ partition.</p>
 524
 525 <p class="sidebar"><b>Warning:</b> Numerous rEFIt bug reports indicate disk corruption problems on disks over about 500 GiB. <a href="https://sourceforge.net/tracker/?func=detail&aid=3218104&group_id=161917&atid=821764">This</a> report on the problem, and particularly the post by mic-marchen, suggests that the problem is related to a bug in OS X's <tt>bless</tt> utility, and particularly its <tt>--info</tt> option, that causes it to corrupt data on disks with 4 KiB sectors. These <i>Advanced Format</i> disks are becoming increasingly common, particularly at larger disk sizes. Therefore, I <i>strongly</i> recommend that you <i>not</i> type <tt class="userinput">sudo bless --info</tt> to check the status of your installation if you have such a disk, or even if you suspect you might have such a disk. (I've seen Advanced Format disks as small as 320 GB.)</p>
 526
 527 <p>The procedure for installing rEFInd on a Mac is similar to that for installing it under Linux, except that you must use the <tt>bless</tt> utility rather than <tt>efibootmgr</tt> to register the program with the firmware. Also, you'll probably have to mount your ESP manually, since that's not done by default under OS X. To be precise, you should follow these steps:</p>
 528
 529 <ol>
 530
 531 <li>Open a Terminal window in which you'll type the following
 532     commands.</li>
 533
 534 <li>If you want to install rEFInd on your ESP, you must first mount it. You
 535     can do this by typing <b><tt>mkdir /Volumes/esp</tt></b> followed by
 536     <b><tt>sudo mount -t msdos /dev/disk0s1 /Volumes/esp</tt></b>. Note
 537     that you may need to change <tt>/dev/disk0s1</tt> to something else if
 538     your ESP is at an unusual location. Type <tt class="userinput">diskutil
 539     list</tt> or use a tool such as my <a
 540     href="http://www.rodsbooks.com/gdisk/">GPT fdisk (<tt>gdisk</tt>)</a>
 541     to examine your partition table to find your ESP if necessary.</li>
 542
 543 <li>Type <b><tt>sudo mkdir -p /Volumes/esp/efi/refind</tt></b> to create a
 544     suitable directory for rEFInd. If you want to place rEFInd on the OS X
 545     root partition, you should adjust the pathname appropriately, as in
 546     <tt>/efi/refind</tt>. Alternatively, you can use the Finder to create
 547     the directory.</li>
 548
 549 <li>Copy the files in the <tt>refind</tt> subdirectory of the rEFInd binary
 550     package to the like-named directory you've just created. You can do
 551     this in the Finder or by typing <b><tt>sudo cp -r refind/*
 552     /Volumes/esp/efi/refind/</tt></b> in your Terminal window after
 553     changing into the rEFInd package's main directory.</li>
 554
 555 <li>Remove the file for the version of rEFInd you're not using, as in
 556     <b><tt>sudo rm Volumes/esp/efi/refind/refind_ia32.efi</tt></b> on a Mac
 557     with a 64-bit EFI or <b><tt>sudo rm
 558     /Volumes/esp/efi/refind/refind_x64.efi</tt></b> on a Mac with a 32-bit
 559     EFI.</li>
 560
 561 <li>Optionally, remove the drivers directory for the architecture you're
 562     not using&mdash;<tt>/Volumes/esp/efi/refind/drivers_ia32</tt> or
 563     <tt>/Volumes/esp/efi/refind/drivers_x64</tt>, as appropriate. You may
 564     also want to remove some or all of the drivers for the architecture you
 565     are using; if you don't need them, they'll slow down the start process.
 566     See the <a href="drivers.html">page on drivers</a> for more on this
 567     topic. Note that Apple's firmware includes its own HFS+ driver, so the
 568     HFS+ driver provided with rEFInd is useless on Macs.</li>
 569
 570 <li>If this is your first installation, type <b><tt>sudo mv
 571     /Volumes/esp/efi/refind/refind.conf-sample
 572     /Volumes/esp/efi/refind/refind.conf</tt></b> (adjusting the path as
 573     necessary) to rename the sample configuration file so that it will
 574     serve as a real configuration file. (Again, you can do this with the
 575     Finder, if you prefer.)</li>
 576
 577 <li>"Bless" rEFInd by typing one of the following two commands:
 578     <ul>
 579     <li>If you're installing rEFInd on the ESP, type <tt
 580         class="userinput">sudo bless --mount /Volumes/esp --setBoot --file
 581         /Volumes/esp/efi/refind/refind_x64.efi --shortform</tt>, adjusting
 582         the mount point and exact path to the file as appropriate for your
 583         installation.</li>
 584     <li>If you're installing rEFInd to an ordinary HFS+ volume, type <tt
 585         class="userinput">sudo bless --setBoot --folder /efi/refind --file
 586         /efi/refind/refind_x64.efi</tt>. (Adjust the path and filename as
 587         necessary if you're placing rEFInd somewhere else or using the
 588         32-bit version.)</li>
 589     </ul>
 590     As per the Warning earlier, <i>do not</i> use <tt>bless</tt>'s
 591     <tt>--info</tt> option to try to confirm the change to the boot status
 592     unless you're certain you do <i>not</i> have an Advanced Format hard
 593     disk.</li>
 594
 595 <li>If you don't want to reboot immediately after installing rEFInd, you
 596     may optionally unmount the ESP by typing <tt class="userinput">sudo
 597     umount /dev/disk0s1</tt> or <tt class="userinput">sudo umount
 598     /Volumes/esp</tt>. This step isn't strictly required, but if you want
 599     to keep the ESP out of your directory tree, it can be useful.</li>
 600
 601 </ol>
 602
 603 <p>When you reboot, your Mac should bring up the rEFInd menu, and should continue to do so thereafter. If you make changes that break this association, you can re-run the <tt>bless</tt> command (if necessary, restoring the rEFInd files first). This might be necessary after installing system updates from Apple or if you upgrade rEFInd to a newer version.</p>
 604
 605 <p>If you're replacing rEFIt, you may discover that rEFInd works on the first boot, but the system reverts back to rEFIt or a direct boot to OS X on the second boot. To fix this problem, you can remove the rEFItBlesser program, which is located at <tt>/Library/StartupItems/rEFItBlesser</tt>. This program attempts to keep rEFIt set as the default boot loader, but it also has the purpose of protecting the computer from launching the wrong OS after waking from sleep. If you want that protection, my suggestion is to install rEFIt and rEFItBlesser and then replace the <tt>refit.efi</tt> file with <tt>refind_x64.efi</tt> or <tt>refind_ia32.efi</tt> (renaming it to <tt>refit.efi</tt>). Used in this way, rEFInd will still look for its own configuration file, <tt>refind.conf</tt>, so you'll need to move it but <i>not</i> rename it. If you don't move the icons from the rEFInd package, your icons will continue to look like rEFIt icons, and you'll be missing the new icons for specific Linux distributions that rEFInd provides. One final caveat: It's conceivable that rEFItBlesser is what's causing filesystem corruption for some users, so if you've been having this problem with rEFIt, it might be worth disabling this program and not using it with rEFInd.</p>
 606
 607 <p>If you want to remove rEFInd from your system, you can delete its files. The Mac will revert to booting using whatever standard boot loader it can find. Alternatively, you can use <tt>bless</tt> to bless another EFI boot loader. The GUI Startup Disk utility in System Preferences provides a simplified interface that enables you to select which OS X installation to boot, but it doesn't look for non-Apple boot loaders, so you can't use it to enable rEFInd.</p>
 608
 609 <a name="windows">
 610 <h3>Installing rEFInd Manually Using Windows</h3>
 611 </a>
 612
 613 <p class="sidebar"><b>Warning:</b> Windows 8 implements a fast shutdown feature that helps speed up shutdown and startup operations on a single-boot computer. Unfortunately, this feature can cause filesystem corruption if it's used on a multi-boot computer. You can disable the feature by launching an Administrator Command Prompt window and typing <tt class="userinput">powercfg /h off</tt> in it.</p>
 614
 615 <p>I know relatively little about Windows EFI management tools; however, I do know that at least two relevant tools exist: the standard <tt>bcdedit</tt> and the third-party <i>EasyUEFI.</i></p>
 616
 617 <p>The <a href="http://www.easyuefi.com/index-us.html">EasyUEFI tool</a> is a free (as in beer) GUI tool for managing EFI boot programs. I've only tried it once, and it seemed fairly intuitive and easy to use, but I don't have detailed instructions on how to use it. If you want to use EasyUEFI, you'll have to use it in place of <tt>bcdedit</tt> at the end of the following procedure.</p>
 618
 619 <p>Attempt this method of installation only on a UEFI-based PC; this method will not work on Windows that's installed on a Mac in BIOS/CSM/legacy mode. To install rEFInd under Windows, you must first find a way to access the ESP, which Windows normally hides from view. One way to accomplish this goal, and to proceed forward once the ESP is accessible, is as follows:</p>
 620
 621 <ol>
 622
 623 <li>Locate Command Prompt in the Start menu, right-click it, and select Run as Administrator. This action opens a Command Prompt window with administrative privileges.</li>
 624
 625 <li>Type <b><tt>mountvol S: /S</tt></b> in the Administrator Command Prompt window. This makes the ESP accessible as drive <tt>S:</tt> from that window. (You can use a drive identifier other than <tt>S:</tt> if you like.)</li>
 626
 627 <li>Change into the main rEFInd package directory, so that the <tt>refind</tt> subdirectory is visible when you type <b><tt>dir</tt></b>.</li>
 628
 629 <li>Type <b><tt>xcopy /E refind S:\EFI\refind\</tt></b> to copy the <tt>refind</tt> directory tree to the ESP's <tt>EFI</tt> directory. If you omit the trailing backslash from this command, <tt>xcopy</tt> will ask if you want to create the <tt>refind</tt> directory. Tell it to do so.</li>
 630
 631 <li>Type <b><tt>S:</tt></b> to change to the ESP.</li>
 632
 633 <li>Type <b><tt>cd EFI\refind</tt></b> to change into the <tt>refind</tt> subdirectory</li>
 634
 635 <li>You may want to selectively delete some of the drivers in the <tt>drivers_x64</tt> or <tt>drivers_ia32</tt> directory, depending on your architecture and needs. Unnecessary drivers will slow the rEFInd start process, and can even cause the drivers you need to not work or cause a system crash. See the <a href="drivers.html">page on drivers</a> for more on this topic.</li>
 636
 637 <li>Type <b><tt>rename refind.conf-sample refind.conf</tt></b> to rename rEFInd's configuration file.</li>
 638
 639 <p class="sidebar"><b>Note:</b> I've heard from a couple of Windows 10 users that the <tt>bcdedit</tt> commands described here don't work. I don't yet know if this is a coincidence or if Microsoft has changed <tt>bcdedit</tt> in such a way that these instructions no longer apply. If you run into this problem, either try using EasyUEFI or use another installation method, such as the <a href="#linux">Linux method</a> from a Linux emergency boot disc.</p>
 640
 641 <li>Type <b><tt>bcdedit /set {bootmgr} path \EFI\refind\refind_x64.efi</tt></b> to set rEFInd as the default EFI boot program. Note that <tt>{bootmgr}</tt> is entered as such; that's not a notation for a variable. Also, change <tt>refind_x64.efi</tt> to <tt>refind_ia32.efi</tt> on systems with 32-bit EFIs. Such computers are rare, and most of them are tablets. Check your Windows bit depth to determine which binary you should use.</li>
 642
 643 <li>If you like, type <b><tt>bcdedit /set {bootmgr} description "<i>rEFInd description</i>"</tt></b> to set a description (change <tt><i>rEFInd description</i></tt> as you see fit).</li>
 644
 645 </ol>
 646
 647 <p>At this point, when you reboot, rEFInd should appear as your new default boot program. If it doesn't work for you, you have several other options, such as:</p>
 648
 649 <ul>
 650
 651 <li>You can rename files on the ESP. as described later, in <a href="#naming">Alternative Naming Options.</a></li>
 652
 653 <li>You can boot from an optical disc into an emergency OS to do the job. Ubuntu, for instance, provides an EFI-bootable installer with a "try before installation" mode. You'll need to type <b><tt>sudo apt-get install efibootmgr</tt></b> to install <tt>efibootmgr</tt>, but you can then use that program as described <a href="#efibootmgr">earlier</a>. (If you're using Ubuntu, you'll need to precede the command with <b><tt>sudo</tt></b>. If you use an Ubuntu image, you can install rEFInd <a href="#ppa">via its PPA,</a> which is an easy way to do the job. (In fact, the rEFInd PPA depends on the <tt>efibootmgr</tt> package, so you shouldn't need to manually install it.) The PPA approach may even be easier than installing from Windows using its tools, at least if you're familiar with Linux and have an Ubuntu desktop image handy.</li>
 654
 655 <li>You may be able to use rEFInd's bootable CD image to use rEFInd to boot an OS that's been installed but rendered inoperable because of changes to your boot order. You can then use <tt>efibootmgr</tt>, <tt>bless</tt>, or some other tool to restore rEFInd as the default boot loader.</li>
 656
 657 </ul>
 658
 659 <a name="efishell">
 660 <h3>Installing rEFInd Manually Using an EFI Shell</h3>
 661 </a>
 662
 663 <p class="sidebar"><b>Warning:</b> Do not attempt to use the procedure described in this section on a Macintosh. Macs have a strange EFI implementation that does not use the EFI variables that this procedure manipulates. Therefore, chances are this procedure simply won't work. It's conceivable that this procedure will actually cause problems, but I'm not curious enough to try it and risk damaging my Mac!</p>
 664
 665 <p>If you can't currently boot any OS (say, because a firmware update has wiped your NVRAM entries), you may find it convenient to install rEFInd using an EFI version 2 shell. Unfortunately, the <tt>bcfg</tt> command described here is not available in the EFI version 1 shell, and the version 2 shell is unusable on many firmware implementations prior to 2.3.1. Thus, this procedure won't work for all systems.</p>
 666
 667 <p>In addition to emergency situations, using <tt>bcfg</tt> can be desirable if <tt>efibootmgr</tt> or other OS-hosted tools don't do the job. This happens under VirtualBox, for instance. An alternative in such cases can be to use <a href="#naming">alternative names for rEFInd.</a></p>
 668
 669 <p>To begin, you must have a way to launch your shell. Unfortunately, this can pose a dilemma, since without rEFInd or some other boot manager, many EFI implementations lack the means to launch a shell. Some will do so, though, if the shell is stored as <tt>shellx64.efi</tt> (for <i>x</i>86-64) or <tt>shellia32.efi</tt> (for <i>x</i>86) in the root directory of the ESP. Thus, you can try copying your shell file there. You can obtain EFI 2 shells here:</p>
 670
 671 <ul>
 672
 673 <li><a href="https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/ShellBinPkg/UefiShell/X64/Shell.efi"><i>x</i>86-64 (64-bit) shell 2</a></li>
 674
 675 <li><a href="https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/ShellBinPkg/UefiShell/Ia32/Shell.efi"><i>x</i>86 (32-bit) shell 2</a></li>
 676
 677 <li><a href="http://dl.dropbox.com/u/17629062/Shell2.zip">Alternate <i>x</i>86-64 (64-bit) shell 2 for older EFIs</a></li>
 678
 679 </ul>
 680
 681 <p>Note that the IA32 shell included in rEFInd's CD-R image version is a version 1 shell, so you can't use it for this purpose. You can, however, copy rEFInd's files from the CD-R. You can even launch the version 1 shell included with rEFInd and then use that to launch a version 2 shell. The <i>x</i>86-64 shell on the CD-R is the alternate shell, which should work on any <i>x</i>86-64 computer. Once you've booted the shell, you can proceed as follows:</p>
 682
 683 <ol>
 684
 685 <li>If you haven't installed rEFInd previously, unpack its zip file to a
 686     FAT partition. This can be the ESP itself or another partition, such as
 687     a USB flash drive. If you're simply repairing a lost NVRAM entry, you
 688     needn't move your existing rEFInd files.</li>
 689
 690 <li>Identify your filesystems, which are labelled with the form <tt>fs<tt
 691     style="variable">n</tt>:</tt>, as in <tt>fs0:</tt> for the first
 692     filesystem, <tt>fs1:</tt> for the second, and so on. Type the
 693     filesystem number followed by the Enter key to begin using it. You can
 694     then type <tt class="userinput">ls</tt> or <tt
 695     class="userinput">dir</tt> to see the contents of the filesystem.
 696     Chances are your ESP will be <tt>fs0:</tt>, but it could be something
 697     else. (The following steps assume your ESP is <tt>fs0:</tt>; you'll
 698     need to adjust them if it's not.) If rEFInd's source files are on
 699     another device, you must identify it, too.</li>
 700
 701 <p class="sidebar"><b>Note:</b> Skip ahead to step #12 if you're merely re-activating an already-installed rEFInd binary. If an entry exists but it's no longer the primary one, you can skip ahead to step #14.</p>
 702
 703 <li>If necessary, create a directory for rEFInd by typing <tt
 704     class="userinput">mkdir fs0:\EFI\refind</tt>. (If the <tt>fs0:\EFI</tt>
 705     directory doesn't already exist, you must create it first,
 706     though.)</li>
 707
 708 <li>Change to the directory in which rEFInd's files exist.</li>
 709
 710 <li>Type <tt class="userinput">cp refind_x64.efi fs0:\EFI\refind</tt> to
 711     copy the rEFInd binary file. (Adjust the name if you're using a 32-bit
 712     computer.)</li>
 713
 714 <li>Type <tt class="userinput">cp refind.conf-sample
 715     fs0:\EFI\refind\refind.conf</tt> to copy and rename the sample rEFInd
 716     configuration file.</li>
 717
 718 <li>Type <tt class="userinput">cp -r icons fs0:\EFI\refind\</tt> to copy
 719     rEFInd's icons.</li>
 720
 721 <li>Optionally, type <tt class="userinput">cp -r drivers_x64
 722     fs0:\EFI\refind\</tt> to copy rEFInd's 64-bit drivers. (You could
 723     instead copy the 32-bit drivers or limit yourself to just the drivers
 724     you need, of course.)</li>
 725
 726 <li>Type <tt class="userinput">fs0:</tt>, if necessary, to change to the
 727     ESP.</li>
 728
 729 <li>Type <tt class="userinput">cd \EFI\refind</tt> to change to rEFInd's
 730     installation directory.</li>
 731
 732 <li>If you want to edit rEFInd's options, type <tt class="userinput">edit
 733     refind.conf</tt> and use the shell's built-in text editor to do so.
 734     Press F2 followed by the Enter key to save your changes and F3 to
 735     exit.</li>
 736
 737 <li>Type <tt class="userinput">bcfg boot dump -b</tt> to see a list of
 738     existing NVRAM entries. Pay attention to their numbers (labelled
 739     <tt>Option:</tt> and <tt>Variable:</tt>, with the latter number
 740     preceded by the string <tt>Boot</tt>, as in <tt>Boot0007</tt>). You'll
 741     want to create a boot entry for rEFInd using a number that's not in
 742     use.</li>
 743
 744 <li>Type <tt class="userinput">bcfg boot add 3
 745     fs0:\EFI\refind\refind_x64.efi "rEFInd"</tt>, adjusting the number
 746     (<tt>3</tt> in this example), filesystem (<tt>fs0:</tt>), and filename
 747     (<tt>\EFI\refind\refind_x64.efi</tt>) as necessary for your system. If
 748     you're used to Linux, be sure to use backslashes (<tt>\</tt>), not
 749     Linux-style forward slashes (<tt>/</tt>), as directory separators. Note
 750     that some shells may ignore the number you entered and use another one,
 751     so watch for this possibility.</li>
 752
 753 <li>Type <tt class="userinput">bcfg boot mv <i>3</i> 0</tt>, substituting
 754     the option number for the entry you created for <tt
 755     class="variable">3</tt>. This moves rEFInd to the top of the boot
 756     order.</li>
 757
 758 <li>Type <tt class="userinput">reset</tt> to reboot the computer.</li>
 759
 760 </ol>
 761
 762 <p>With any luck, rEFInd will start up at this point. If not, you can check your settings using a shell or an emergency system for your OS of choice. In an EFI shell, you might type <tt class="userinput">bcfg boot dump -b</tt> to view your boot loader entries and verify that rEFInd appears at the top of the list. Be sure to check the pathname for typos. If you continue to have problems, you might look into giving rEFInd a <a href="#naming">fallback filename</a> that your firmware will recognize.</p>
 763
 764 <a name="naming">
 765 <h2>Alternative Naming Options</h2>
 766 </a>
 767
 768 <p>Some EFI implementations do a poor job of honoring the boot options set via Linux's <tt>efibootmgr</tt> or other tools. You may also lack access to such utilities, such as if you must install rEFInd in Windows. In such cases, you may need to change the boot loader's name so that the EFI will see it as the default boot loader. rEFInd should then boot when your NVRAM lacks information on specific boot loaders to use. Broadly speaking, there are two alternative names that are most useful:</p>
 769
 770 <ul>
 771
 772 <li><tt class="userinput">EFI/BOOT/boot<i>arch</i>.efi</tt>&mdash;This name
 773     is the official EFI fallback filename. It's most commonly used on
 774     bootable removable disks, but it can be used on hard disks. It's
 775     typically used only if no NVRAM entry points to a valid boot
 776     loader.</li>
 777
 778 <li><tt class="userinput">EFI/Microsoft/Boot/bootmgfw.efi</tt>&mdash;This
 779     filename has no official special standing in the EFI specification, but
 780     as a practical matter, many EFI implementations use it as a fallback
 781     boot loader in addition to or instead of
 782     <tt>EFI/BOOT/boot<i>arch</i>.efi</tt>. In fact, some give it such a
 783     high precedence that you can't boot anything that's not given this
 784     name!
 785
 786 </ul>
 787
 788 <p>If you need to use one of these names, or something more exotic, you can do so in either of two ways: You can <a href="#mvrefind">use the <tt>mvrefind.sh</tt> script</a> to move your installation in one step, or you can <a href="#manual_renaming">move and rename your files manually.</a></p>
 789
 790 <a name="mvrefind">
 791 <h3>Using <tt>mvrefind.sh</tt></h3>
 792 </a>
 793
 794 <p>The easiest way to move a rEFInd installation, at least in Linux, is to use the <tt>mvrefind.sh</tt> script. If you installed from one of my RPM or Debian packages, this script should be installed in <tt>/usr/sbin</tt>, so you can use it like a regular Linux command; otherwise you'll need to install it to your path yourself or type its complete path. Either way, it works much like the Linux <tt>mv</tt> command, but you pass it the directory in which a rEFInd installation appears and a target location:</p>
 795
 796 <pre class="listing">
 797 # <tt class="userinput">mvrefind.sh /boot/efi/EFI/BOOT /boot/efi/EFI/refind</tt>
 798 </pre>
 799
 800 <p>This example moves rEFInd from <tt>/boot/efi/EFI/BOOT</tt> to <tt>/boot/efi/EFI/refind</tt>. It differs from <tt>mv</tt> in several ways:
 801
 802 <ul>
 803
 804 <li>The script renames rEFInd in a way that's sensitive to its source and
 805     destination directories&mdash;for instance, <tt>mvrefind.sh</tt> knows
 806     that rEFInd (or shim, for Secure Boot installations) must be called
 807     <tt>bootx64.efi</tt> on a 64-bit installation in
 808     <tt>/boot/efi/EFI/BOOT</tt>, so it looks for rEFInd under that name
 809     when copying from this directory, or it renames rEFInd to that name
 810     when copying to it.</li>
 811
 812 <li>The script creates a new NVRAM entry for rEFInd when it copies to any
 813     location but <tt>EFI/BOOT</tt> or <tt>EFI/Microsoft/Boot</tt>. It
 814     refuses to copy to such locations if it's not run from an EFI-mode
 815     boot.</li>
 816
 817 <li>The script knows enough to back up existing boot loaders stored in
 818     <tt>EFI/BOOT</tt> or <tt>EFI/Microsoft/Boot</tt> when copying to these
 819     locations. For the former location, the script backs up
 820     <tt>EFI/BOOT</tt> as <tt>EFI/BOOT-rEFIndBackup</tt>; for the latter, it
 821     moves <tt>EFI/Microsoft/Boot/bootmgfw.efi</tt> to
 822     <tt>EFI/Microsoft/bootmgfw.efi</tt>.</li>
 823
 824 </ul>
 825
 826 <p>The <tt>mvrefind.sh</tt> script is likely to be useful in resolving boot problems&mdash;if your system won't boot, you can try copying the installation to <tt>/boot/efi/EFI/BOOT</tt>, <tt>/boot/efi/EFI/Microsoft/Boot</tt>, and <tt>/boot/efi/EFI/refind</tt> in turn, testing the boot process after each attempt. (These filenames all assume your ESP is mounted at <tt>/boot/efi</tt>.) You could also copy a BIOS-mode install from <tt>/boot/efi/EFI/BOOT</tt> or <tt>/boot/efi/EFI/Microsoft/Boot</tt> to <tt>/boot/efi/EFI/refind</tt> to make it more robust against Windows repairs (assuming your firmware isn't broken).</p>
 827
 828 <a name="manual_renaming">
 829 <h3>Renaming Files Manually</h3>
 830 </a>
 831
 832 <p>You can move and rename rEFInd manually from any OS by following these steps:</p>
 833
 834 <ol>
 835
 836 <li>Access your ESP, as described in earlier sections.</li>
 837
 838 <li>Look for an existing directory called <tt>EFI/BOOT</tt> or <tt>EFI/Microsoft/Boot</tt>. If neither of these directories exist, skip the next step. (Note that FAT is case-insensitive, so the name may vary in case.)</li>
 839
 840 <li>Rename the existing directory or boot loader file to something else. For <tt>EFI/BOOT</tt>, try renaming it to <tt>EFI/Oldboot</tt>. For <tt>EFI/Microsoft/Boot</tt>, move or rename the <tt>bootmgfw.efi</tt> file it contains. For instance, you can move it to <tt>EFI/Microsoft</tt>. This will keep the boot loader accessible to rEFInd's menu, while preventing the firmware from launching it automatically.</li>
 841
 842 <li>Rename/move your <tt>EFI/refind</tt> directory to <tt>EFI/BOOT</tt>. If you're working from <tt>EFI/Microsoft/Boot</tt>, you should move the contents of your rEFInd directory to <tt>EFI/Microsoft/Boot</tt>.</li>
 843
 844 <li>Rename <tt>EFI/BOOT/refind_x64.efi</tt> to the name of the boot loader it's replacing&mdash;it should become <tt>EFI/BOOT/bootx64.efi</tt> or <tt>EFI/Microsoft/Boot/bootmgfw.efi</tt>.</li>
 845
 846 </ol>
 847
 848 <p>When you reboot, rEFInd should come up. With any luck, it will detect your old boot loader as an option, if one was installed before.</p>
 849
 850 <a name="upgrading">
 851 <h2>Upgrading rEFInd</h2>
 852 </a>
 853
 854 <p>If you've installed an earlier version of rEFInd, you can upgrade a bit more easily than you can install directly:</p>
 855
 856 <ul>
 857
 858 <li>On a UEFI-based PC, under any OS, you should be able to replace your
 859     old rEFInd file with the new one. Make sure that the new rEFInd has the
 860     same name as the old one, and that it's for the correct CPU type. Since
 861     UEFI launches boot programs by filename, a simple file replacement will
 862     suffice to launch the new version. If the new version includes new
 863     icons, you may want to copy some or all of them.</li>
 864
 865 <li>On a Mac, you can copy over the old rEFInd binary file <i>from
 866     Linux</i> and it will usually work, provided you copy <i>directly</i>
 867     over the old file (rather than rename or delete the old file and then
 868     copy the new one in its place). The same caveats about icons as apply
 869     to UEFI-based PCs apply in this case. This method requires an extra
 870     step in Mac OS X, though....</li>
 871
 872 <li>In OS X, if you copy over the original file with the new one, you'll
 873     probably have to re-bless it to make it work.</li>
 874
 875 <li>Under Linux or OS X, you can re-run the <tt>install.sh</tt> script. In
 876     most cases this works fine, but you'll end up with a duplicate of the
 877     icons directory (<tt>icons-backup</tt>, which holds the original icons,
 878     whereas <tt>icons</tt> holds the icons from the new package). Normally
 879     this just wastes some disk space; but if you've customized your icons,
 880     you'll need to copy your altered icons back. Under Linux, versions
 881     0.6.2 and later of <tt>install.sh</tt> search for rEFInd in several
 882     locations on the ESP, and will upgrade whatever is found. The same is
 883     true with versions 0.8.5 and later under OS X when installing to the
 884     ESP. If you install to a location other than the ESP under OS X, be
 885     sure to include the same option to <tt>install.sh</tt>
 886     (<tt>--notesp</tt> or <tt>--ownhfs</tt>) to replace the original rather
 887     than create a new installation to the ESP.</li>
 888
 889 <li>Under an RPM- or Debian-based Linux distribution, you can use your
 890     package system to install a newer version of the RPM or Debian package
 891     that I provide. This will upgrade the files in your Linux filesystem
 892     and re-run the <tt>install.sh</tt> script, so as with the previous
 893     options, you'll waste a little disk space on duplicated icons, but the
 894     process should otherwise work quite well.</li>
 895
 896 <li>If you installed using my Ubuntu PPA or a package provided by an OS
 897     distribution (such as the packages that ship with Arch and ALT Linux),
 898     performing a system update will probably update rEFInd, too. Depending
 899     on how the package was created, though, this update might or might not
 900     install the update to the ESP; you might need to manually re-run the
 901     installation script. Consult your distribution's documentation for
 902     details. My Ubuntu PPA will automatically run <tt>install.sh</tt> after
 903     the package is installed.</li>
 904
 905 </ul>
 906
 907 <p>In all cases, if the new version includes new or altered configuration file options, you may need to manually update your configuration file. Alternatively, if you've used the default configuration file, you can replace your working <tt>refind.conf</tt> with <tt>refind.conf-sample</tt> from the rEFInd zip file. (When using <tt>install.sh</tt>, this file will be copied to rEFInd's installation directory under its original name, so you can rename it within that directory to replace the old file.)</p>
 908
 909 <p>If you're upgrading to rEFInd from rEFIt, you can simply run the <tt>install.sh</tt> script as described earlier or perform a manual installation. Once installed, rEFInd will take over boot manager duties. You'll still be able to launch rEFIt from rEFInd; a rEFIt icon will appear in rEFInd's menu. You can eliminate this option by removing the rEFIt files, which normally reside in <tt>/EFI/refit</tt>.</p>
 910
 911 <a name="addons">
 912 <h2>Installing Additional Components</h2>
 913 </a>
 914
 915 <p>rEFInd includes the ability to launch any EFI program; however, rEFInd detects only certain programs. These include boot loaders in traditional locations and a handful of other programs. To launch most of these other programs, you must download and install them separately from rEFInd:</p>
 916
 917 <ul>
 918
 919 <li><b><a
 920     href="http://tianocore.git.sourceforge.net/git/gitweb.cgi?p=tianocore/edk2;a=blob_plain;f=EdkShellBinPkg/FullShell/X64/Shell_Full.efi;hb=HEAD"><tt>shell.efi</tt></a></b>&mdash;This
 921     file, placed in the ESP's <tt>EFI/tools</tt> directory, adds the
 922     ability to launch a text-mode EFI shell from rEFInd. Note that the
 923     download link is to a 64-bit binary that must be renamed before rEFInd
 924     will recognize it. Additional shell download links appear on the <a
 925     href="https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#UEFI_Shell_download_links">Arch
 926     Linux wiki,</a> and on other sites; try a Web search if the shell you
 927     find doesn't work to your satisfaction.</li>
 928
 929 <li><b><a
 930     href="http://www.memtest86.com/download.htm">Memtest86</a></b>&mdash;This
 931     is a popular tool for performing basic hardware tests, and especially
 932     memory tests. rEFInd recognizes this program when it is stored in the
 933     <tt>EFI/tools</tt>, <tt>EFI/tools/memtest</tt>,
 934     <tt>EFI/tools/memtest86</tt>, <tt>EFI/memtest</tt>, or
 935     <tt>EFI/memtest86</tt> directory, with a program filename of
 936     <tt>memtest86.efi</tt>, <tt>memtest86_x64.efi</tt>,
 937     <tt>memtest86x64.efi</tt>, or <tt>bootx64.efi</tt>. (Change
 938     <tt>x64</tt> to <tt>ia32</tt> on IA-32 systems.) Be sure to download
 939     the EFI version of the program. If you get the USB flash drive version,
 940     you should mount the flash drive's ESP (partition 2) and copy the
 941     <tt>EFI/BOOT</tt> directory to your own ESP's
 942     <tt>EFI/tools/memtest</tt> or other Memtest86 directory name, as just
 943     specified. rEFInd should then recognize it, provided the
 944     <tt>showtools</tt> line includes the <tt>memtest</tt> or
 945     <tt>memtest86</tt> token.</li>
 946
 947 <li><b><tt>gptsync.efi</tt> or <tt>gptsync_<tt
 948     class="variable">arch</tt>.efi</tt></b>&mdash;This program creates a <a
 949     href="http://www.rodsbooks.com/gdisk/hybrid.html">hybrid MBR</a> from
 950     your regular GPT disk. A hybrid MBR is a dangerous hack that enables
 951     Windows and OS X to coexist on a Macintosh disk. If you're using a
 952     UEFI-based PC, a hybrid MBR is likely to be useless at best, so you
 953     shouldn't create one, and it's safest to not install
 954     <tt>gptsync.efi</tt>. If you're using a hybrid MBR to enable
 955     dual-booting Windows and OS X on a Mac, though, placing this program
 956     file in the ESP's or Mac boot partition's <tt>EFI/tools</tt> directory
 957     will enable you to regenerate your hybrid MBR should some other tool
 958     convert the MBR to a standard protective MBR. You can obtain the file
 959     from the <a href="http://refit.sourceforge.net">original rEFIt
 960     package,</a> or beginning with rEFInd 0.6.9, an updated version is
 961     included in the rEFInd package. The rEFInd version of <tt>gptsync_<tt
 962     class="variable">arch</tt>.efi</tt> uses a more sophisticated algorithm
 963     for determining what GPT partitions to duplicate in the MBR and it
 964     includes additional safeguards to minimize the risk of damage should
 965     you run the program on a disk that might have been damaged. The
 966     original rEFIt version of the program usually goes by the filename
 967     <tt>gptsync.efi</tt>, whereas the updated rEFInd version ships with an
 968     architecture code, as in <tt>gptsync_x64.efi</tt> or
 969     <tt>gptsync_ia32.efi</tt>. The rEFInd <tt>install.sh</tt> script
 970     installs <tt>gptsync_<tt class="variable">arch</tt>.efi</tt> when run
 971     under OS X, but not when run on Linux. In addition to installing the
 972     program, you must edit <tt>refind.conf</tt>, uncomment the
 973     <tt>showtools</tt> line, and add <tt>gptsync</tt> to its list of
 974     options.</li>
 975
 976 <li><b>Drivers</b>&mdash;You can install drivers to extend the capabilities
 977     of the EFI. rEFInd ships with filesystem drivers for ext2fs, ext4fs, and
 978     ReiserFS, which can enable you to boot a Linux kernel with EFI stub
 979     support from an ext2fs, ext3fs, ext4fs, or ReiserFS partition. (rEFInd also
 980     provides ISO-9660 and HFS+ drivers.) You can find additional drivers
 981     from other sources, although they're still on the scarce side. See the
 982     <a href="drivers.html">Using EFI Drivers</a> page for more on this
 983     topic.</li>
 984
 985 <li><b>Secure Boot files</b>&mdash;If you're running on a system that
 986     supports Secure Boot, chances are you'll need extra support files, such
 987     as <tt>shim.efi</tt> and <tt>MokManager.efi</tt>. I describe these in
 988     detail on the <a href="secureboot.html">Managing Secure Boot</a>
 989     page.</li>
 990
 991 <li><b><a href="http://ipxe.org/">iPXE</a></b>&mdash;This tool provides the
 992     ability to boot a computer from a network server. Consult the
 993     <tt>BUILDING.txt</tt> file in the rEFInd source code package for
 994     information on building and installing these tools. You must also
 995     activate rEFInd's support by adding the <tt>netboot</tt> option to the
 996     <tt>scanfor</tt> and/or <tt>showtools</tt> lines in
 997     <tt>refind.conf</tt>. <i>Network-boot/iPXE support is currently
 998     experimental;</i> I recommend that only developers or those who are
 999     willing to use "bleeding-edge" software try it. Once activated, rEFInd
1000     will present a new menu item for booting from the network server.
1001     rEFInd itself will normally be installed locally. (You can deliver
1002     rEFInd as a network-boot image, but that image will be able to boot
1003     only OSes on the local disk.)</li>
1004
1005 </ul>
1006
1007 <p>I've seen links to other versions of these tools from time to time on the Web, so if you try one of these programs and it crashes or behaves strangely, try performing a Web search; you may turn up something that works better for you than the one to which I've linked.</p>
1008
1009 <a name="sluggish">
1010 <h2>Fixing Macintosh Boot Problems</h2>
1011 </a>
1012
1013 <p>I've received a few reports of a sluggish boot process (a delay of about 30 seconds before starting rEFInd) on some Macs after installing rEFInd, as well as some other Mac-specific peculiarities. I've been unable to replicate thess problems myself, and their true causes remains mysterious to me. I have found several possible solutions, though: <a href="#shortform">Using the <tt>--shortform</tt> option,</a> <a href="#fallback">using the fallback filename,</a> <a href="#moving">moving rEFInd to an HFS+ volume,</a> <a href="#clearing">clearing NVRAM entries,</a> <a href="#wakeprobs">fixing wake problems,</a> and <a href="#nolinux">fixing a failure to find Linux.</a></p>
1014
1015 <a name="shortform">
1016 <h3>Using the <tt>--shortform</tt> Option</h3>
1017 </a>
1018
1019 <p>Prior to version 0.8.5, these instructions and the <tt>install.sh</tt> script omitted the <tt>--shortform</tt> option from the <tt>bless</tt> command when installing rEFInd to the ESP. An rEFInd user, however, discovered that using the option eliminated the 30-second delay, so it is now the default with 0.8.5's <tt>install.sh</tt>, and is specified in the instructions. If you installed rEFInd 0.8.4 or earlier, you may want to re-install or re-<tt>bless</tt> rEFInd using this option.</p>
1020
1021 <p>There is one caveat, though: The <tt>man</tt> page for <tt>bless</tt> notes that <tt>--shortform</tt> notes that its use can come "at the expense of boot time performance." Thus, it's not clear to me that this option might not actually <i>create</i> problems on some computers. (It's eliminated the boot delay on my 2014 MacBook Air and has no detrimental effect on an old 32-bit Mac Mini that's never had a boot delay problem, though.) Thus, if you have problems with rEFInd 0.8.5 or later, you might try running <tt>bless</tt>, as described in <a href="#osx">Installing rEFInd Manually Using OS X's</a> step 8, but <i>omit</i> the <tt>--shortform</tt> option.</p>
1022
1023 <a name="fallback">
1024 <h3>Using the Fallback Filename</h3>
1025 </a>
1026
1027 <p>I've received a few reports that installing rEFInd to the ESP using the fallback filename (<tt>EFI/BOOT/bootx64.efi</tt> on most systems, or <tt>EFI/BOOT/bootia32.efi</tt> on very old Macs) can work around a sluggish boot problem. In fact, version 0.8.4's <tt>install.sh</tt> script copied the rEFInd binary to this name when run under OS X. (Version 0.8.5 switches to using <tt>--shortform</tt> with the more conventional <tt>EFI/refind/refind_x64.efi</tt> or <tt>EFI/refind/refind_ia32.efi</tt> name, as just noted.) If you installed to a name other than <tt>EFI/BOOT/BOOT<tt class="variable">{ARCH}</tt></tt>, either manually or by using the 0.8.5 or later <tt>install.sh</tt>, renaming (and re-<tt>bless</tt>ing) the installation is worth trying.</p>
1028
1029 <a name="moving">
1030 <h3>Moving rEFInd to an HFS+ Volume</h3>
1031 </a>
1032
1033 <p>Most of the reports of sluggish Macintosh boots I've seen note that the user installed rEFInd to the ESP rather than to the OS X root partition. Some users have reported that re-installing rEFInd to the OS X root partition clears up the problem. This is obviously a straightforward solution to the problem, if it works. (This location is not an option when using WDE or OS X logical volumes.) Note that rEFInd can launch boot loaders that are stored on any partition that the EFI can read no matter where it's installed; therefore, you'll still be able to launch boot loaders stored on the ESP (or elsewhere) if you install it in this way.</p>
1034
1035 <p>A variant of this solution is to create a small (~100MiB) HFS+ volume to be used exclusively by rEFInd. You can then install rEFInd to that volume with the <tt>--ownhfs</tt> option to <tt>install.sh</tt>, as in <tt class="userinput">./install.sh --ownhfs /dev/disk0s6</tt> if the volume is <tt>/dev/disk0s6</tt>. This approach has the advantage that it can be managed via OS X's own Startup Disk tool in System Preferences.</p>
1036
1037 <p>The biggest drawback to storing rEFInd on an HFS+ volume is that you won't be able to edit the rEFInd configuration file or move rEFInd-related binaries from an EFI shell if you install it in this way, since Apple's HFS+ driver for EFI is read-only. (The same is true of rEFInd's HFS+ driver, so it won't help you overcome this limitation.) You may also be limited in making changes to your rEFInd configuration from Linux or other OSes, too, since Linux's HFS+ drivers disable write support by default on volumes with an active journal. You can force write access by using the <tt>force</tt> option to <tt>mount</tt>; however, this procedure is noted as being risky in the Linux HFS+ documentation, so I don't recommend doing this on a regular basis on the OS X boot volume. This isn't as risky if you use a dedicated HFS+ rEFInd partition, though. You could even mount it as the Linux <tt>/boot</tt> partition, in which case it would also hold the Linux kernel and related files.</p>
1038
1039 <p>A variant of this solution is suggested in <a href="http://www.sparxeng.com/blog/software/fixing-slow-boot-on-a-triple-boot-mountain-lion-mac">this blog post,</a> which recommends placing rEFInd on an HFS+ volume on the first SATA channel. (In the blogger's case, that channel used to hold an optical drive, but that drive was replaced by a hard disk.)</p>
1040
1041 <a name="clearing">
1042 <h3>Clearing the NVRAM Entries</h3>
1043 </a>
1044
1045 <p>Another possible solution is documented in <a href="http://ubuntuforums.org/showpost.php?p=12256273&postcount=200">a Web forum post.</a> Be aware, though, that this procedure involves using the <tt>efibootmgr</tt> utility on Macs, which has been known to damage the firmware on some Macs. Other reports indicate that this problem has been fixed with 3.3.0 and later kernels. Thus, I present this information cautiously and with a strong "use at your own risk" warning. If you care to proceed, I recommend you update your Linux kernel to the latest possible version and then proceed as follows:</p>
1046
1047 <ol>
1048
1049 <li>Boot into Linux.</li>
1050
1051 <li>Type <tt class="userinput">efibootmgr</tt> as <tt>root</tt> to obtain a list of your boot loader entries. Each entry includes a boot number, as in <tt>Boot0003</tt> or <tt>Boot0027</tt>.</li>
1052
1053 <li>Remove all of the boot loader entries <i>except</i> rEFInd's by using <tt>efibootmgr</tt>'s <tt>-b <tt class="variable">bootnum</tt></tt> option to specify the boot entry and <tt>-B</tt> to delete it. For instance, typing <tt class="userinput">efibootmgr -b 0027 -B</tt> as <tt>root</tt> deletes boot entry <tt>Boot0027</tt>. Issue a separate <tt>efibootmgr</tt> command for each boot entry.</li>
1054
1055 <li>Re-install rEFInd using the install script. It's unclear from the original post if this meant installing from Linux or from OS X.</li>
1056
1057 </ol>
1058
1059 <a name="wakeprobs">
1060 <h3>Fixing Wake Problems</h3>
1061 </a>
1062
1063 <p>Some people have reported that installing rEFInd causes problems with resuming from a suspended OS X session. I know of two workarounds to such problems:</p>
1064
1065 <ul>
1066
1067 <li>Install rEFInd to an HFS+ volume using the <tt>--ownhfs</tt> option to <tt>install.sh</tt>. Unfortunately, this solution requires either creating a small HFS+ volume for rEFInd or using an already-existing non-bootable HFS+ volume (if you've got one for data storage, for example).</li>
1068
1069 <li>Type <tt class="userinput">sudo pmset -a autopoweroff 0</tt> in a Terminal window. This solution is likely to work if sleep operations work normally up to a point, but fail after about three hours.</li>
1070
1071 </ul>
1072
1073 <p>I've recently acquired a 2014 MacBook Air, but I haven't yet had the chance to try to reproduce this problem and find a workaround. It's on my to-do list, though.</p>
1074
1075 <a name="nolinux">
1076 <h3>Fixing a Failure to Find Linux</h3>
1077 </a>
1078
1079 <p>Some users report that rEFInd doesn't detect Linux, or won't boot it when it is found. Broadly speaking, there are two common causes of this problem:</p>
1080
1081 <ul>
1082
1083 <li><b>A malfunctioning BIOS/legacy boot</b>&mdash;If you installed Linux in BIOS/legacy mode, as most online documentation suggests, it could be that your <a href="http://www.rodsbooks.com/gdisk/hybrid.html">hybrid MBR</a> is missing or damaged. The usual symptom of this problem is that rEFInd shows a generic Linux penguin icon and that selecting it produces a message to the effect that a bootable OS could not be found. As hybrid MBRs are ugly and dangerous, I recommend avoiding them if possible, so my preferred solution to this problem is to set up EFI filesystem drivers and boot that way; however, fixing the hybrid MBR may be an easier solution. This is especially true if you installed a 32-bit version of Linux on a 64-bit Mac (or a 64-bit version on a rare Mac with a 64-bit CPU but a 32-bit EFI).</li>
1084
1085 <li><b>EFI filesystem driver problems</b>&mdash;Ideally, rEFInd should be able to load and run your Linux kernel directly, but this approach normally requires you to have a working EFI driver for the filesystem that holds your Linux kernel. This won't always be the case; and even if it is installed, there can be interference from other drivers, so you may need to <i>remove</i> the drivers that you don't use. If drivers are the root of your problem, you won't see any Linux options, or you'll see the one penguin icon (as above) with no others that point to your Linux kernel(s).</li>
1086
1087 </ul>
1088
1089 <p>If you suspect that your hybrid MBR is damaged, you can try re-creating it with my <a href="http://www.rodsbooks.com/gdisk/">GPT fdisk (<tt>gdisk</tt>)</a> program. The GPT fdisk <a href="http://www.rodsbooks.com/gdisk/hybrid.html">hybrid MBR documentation</a> covers this procedure in detail. You can run <tt>gdisk</tt> from either OS X or Linux, although you may need to install it, particularly in OS X.</p>
1090
1091 <p>If you suspect driver problems, you'll need to mount your ESP (as described in the <a href="#osx">manual OS X installation instructions</a>), locate the rEFInd <tt>drivers_x64</tt> directory, and adjust its contents. Make sure you have a driver for the filesystem that holds your Linux kernel. If you don't know what filesystem this is, it's probably ext4fs. rEFInd ships with several filesystem drivers, including one for ext4fs. You should also remove unnecessary filesystem drivers. I've seen several reports of one driver interfering with others' operation. The biggest culprit seems to be the HFS+ driver when used on Macs.</p>
1092
1093 <p></p>
1094
1095 <a name="winprob">
1096 <h2>Fixing Windows Boot Problems</h2>
1097 </a>
1098
1099 <p>Most Windows boot problems are best addressed on Windows-specific sites, so I recommend you make the rounds of Windows forums to solve such problems. There is one that deserves mention here, though: If you accidentally erase the Windows boot loader file, <tt>EFI/Microsoft/Boot/bootmgfw.efi</tt>, you won't be able to boot Windows. The simplest solution is to restore this file from a backup you prepared ahead of time. If you don't have such a backup, though, you can restore it as follows:</p>
1100
1101 <ol>
1102
1103 <li>Boot from an emergency Windows recovery disk. If you don't have one, you can prepare one from a working Windows system as described <a href="http://windows.microsoft.com/en-us/windows7/create-a-system-repair-disc">here.</a></li>
1104
1105 <li>Type <tt class="userinput">diskpart</tt> to enter the Windows disk-partitioning tool.</li>
1106
1107 <li>In <tt>diskpart</tt>, type <tt class="userinput">sel disk 0</tt> followed by <tt>list vol</tt>. You should see a set of partitions. This step is intended to help you identify your ESP, which will probably be the only FAT32 partition on the disk. (If you have multiple disks, you may need to try again with <tt class="userinput">sel disk 1</tt> or higher.) Note the volume number of your ESP.</li>
1108
1109 <li>Type <tt class="userinput">sel vol 1</tt>, changing <tt>1</tt> to whatever the ESP's volume number is.</li>
1110
1111 <li>Type <tt class="userinput">assign letter=S:</tt> to assign the ESP a Windows disk identifier of <tt>S:</tt>. (You can use another letter if you prefer.)</li>
1112
1113 <li>Type <tt class="userinput">exit</tt> to exit from <tt>diskutil</tt>.</li>
1114
1115 <li>Type <tt class="userinput">cd /d s:\EFI\Microsoft\Boot\</tt> to change into the Windows boot loader directory. (If this directory doesn't exist, you may need to create it first with <tt>mkdir</tt>. If rEFInd or some other boot loader occupies this directory, back it up first.</li>
1116
1117 <li>Type <tt class="userinput">bootrec /fixboot</tt>.</li>
1118
1119 <li>Type <tt class="userinput">bcdboot c:\Windows /s s: /f ALL</tt>. Note that this command should set the Windows boot loader as the default. Omit <tt>/f ALL</tt> if you don't want to adjust the EFI's default boot program.</li>
1120
1121 <li>Reboot and hope it works! If the computer boots straight to Windows and you want to use rEFInd, use <tt>bcdedit</tt> in Windows, as described in step 9 of the <a href="#windows">Installing rEFInd Manually Using Windows</a> section of this page.</li>
1122
1123 </ol>
1124
1125 <p>For more information, see <a href="http://superuser.com/questions/460762/how-can-i-repair-the-windows-8-efi-bootloader">this SuperUser question and answer.</a></p>
1126
1127 <a name="uninstalling">
1128 <h2>Uninstalling rEFInd</h2>
1129 </a>
1130
1131 <p>If you decide you don't want to keep rEFInd, you can uninstall it. Doing so is a matter of removing the rEFInd files from your ESP (or from your OS X boot partition, if you installed the program there). The exact details of how to do this vary from one OS to another, though; and in some cases there are alternatives to completely uninstalling rEFInd that are easier to implement.</p>
1132
1133 <a name="uinst_linux">
1134 <h3>Uninstalling rEFInd from Linux</h3>
1135 </a>
1136
1137 <p>In Linux, a command like the following, typed as <tt>root</tt>, should remove rEFInd:</p>
1138
1139 <pre class="listing">
1140 # <tt class="userinput">rm -r /boot/efi/EFI/refind</tt>
1141 </pre>
1142
1143 <p>You must type this command as <tt>root</tt> (or use <tt>sudo</tt> in some environments, such as under Ubuntu). This example assumes that your ESP is mounted at <tt>/boot/efi</tt> and that rEFInd is installed in <tt>EFI/refind</tt> on that partition. If you've mounted your ESP elsewhere, or installed rEFInd elsewhere, you should adjust the command appropriately.</p>
1144
1145 <p>If you installed via an RPM or Debian package in Linux, using your package manager will remove the package files, but not the files that the installer places on your ESP. Thus, you must uninstall those files manually, as just described. To complete the job, you'll also have to remove <tt>/boot/refind_linux.conf</tt>, and perhaps the <tt>/etc/refind.d</tt> directory.</p>
1146
1147 <a name="uinst_osx">
1148 <h3>Uninstalling rEFInd from OS X</h3>
1149 </a>
1150
1151 <p>The easiest way to restore the standard OS X boot loader on a Mac is not to uninstall rEFInd; it's to bypass it. This can be accomplished with the Startup Disk item in the System Preferences panel:</p>
1152
1153     <br /><center><img src="startup-disk.png" align="center" width="668"
1154     height="355" alt="The OS X Startup Disk tool enables you to reset a Mac
1155     to use the standard OS X boot loader." border=2> </center><br />
1156
1157 <p>Select your startup disk (<i>Macintosh HD OS X, 10.10.1</i> in this example) and then click Restart. The computer should reboot into OS X, bypassing rEFInd.</p>
1158
1159 <p>I recommend stopping here, because the procedure for completely removing rEFInd from a Mac depends on your installation method and tends to be challenging for many Mac users, who are unfamiliar with the necessary command-line tools. Basically, you must reverse the steps described earlier, in <a href="#osx">Installing rEFInd Manually Using Mac OS X:</a></p>
1160
1161 <ol>
1162
1163 <li>You must first determine where rEFInd is installed. This can be any of
1164     several locations:
1165
1166     <ul>
1167
1168     <li>If you installed rEFInd 0.8.3 or earlier with the default options,
1169         or if you used the <tt>--notesp</tt> option with rEFInd 0.8.4 or
1170         later, it will be <tt>/EFI/refind</tt> on your main partition</li>
1171
1172     <li>If you installed rEFInd 0.8.4 or later with the default options, or
1173         if you used the <tt>--esp</tt> option with rEFInd 0.8.3 or earlier,
1174         it will be in <tt>EFI/refind</tt> or <tt>EFI/BOOT</tt> on the
1175         ESP.</li>
1176
1177     <li>If you used the <tt>--ownhfs</tt> option to <tt>install.sh</tt>,
1178         rEFInd will be in the <tt>System/Library/CoreServices</tt>
1179         directory on the volume you specified.</li>
1180
1181     <li>If you installed rEFInd manually, it will be wherever you put
1182         it.</li>
1183
1184     <li>In all cases, there could be duplicate (inactive) rEFInd files in
1185         unexpected places. This is particularly true if you tried
1186         installing rEFInd multiple times, each with different options to
1187         <tt>install.sh</tt>. Thus, if you delete rEFInd and it still comes
1188         up, you may have deleted the wrong files. (Note that dragging files
1189         to the Trash may have no effect, though&mdash;at least, not until
1190         you empty the Trash.)</li>
1191
1192     </ul>
1193
1194 <li>If necessary, mount the ESP or rEFInd-specific HFS+ volume, as
1195     described in <a href="#osx">Installing rEFInd Manually Using Mac OS
1196     X.</a></li>
1197
1198 <li>Verify that rEFInd is installed in the directory noted in step #1. If a
1199     <tt>refind.conf</tt> file is present, rEFInd is almost certainly
1200     installed in that directory. If not, it's not rEFInd there and you
1201     should <i>not</i> proceed. <b><i>Be extra cautious about deleting the
1202     <tt>System/Library/CoreServices</tt> directory,</i></b> since that's
1203     the default location of the OS X boot loader! <i>Never</i> delete this
1204     directory from your OS X root (<tt>/</tt>) partition, only from the
1205     partition you specified to <tt>install.sh</tt> using the
1206     <tt>--ownhfs</tt> option.</li>
1207
1208 <li>Once you've identified the rEFInd directory, delete it, or at least the
1209     rEFInd boot file. This file may be called <tt>refind_x64.efi</tt>,
1210     <tt>bootx64.efi</tt>, <tt>boot.efi</tt>, or conceivably something else.
1211     You may need to use <tt>sudo rm</tt> at the command line to accomplish
1212     this task, as in <tt class="userinput">sudo rm -r
1213     /Volumes/esp/EFI/refind</tt>.</li>
1214
1215 </ol>
1216
1217 <a name="uinst_windows">
1218 <h3>Uninstalling rEFInd from Windows</h3>
1219 </a>
1220
1221 <p>From Windows, you must reverse the directions for <a href="#windows">installing in Windows</a>&mdash;type <tt class="userinput">mountvol S: /S</tt> to mount your ESP as <tt>S:</tt>, then navigate to the <tt>S:\EFI</tt> directory and delete the <tt>refind</tt> subdirectory.</p>
1222
1223 <a name="post_uninst">
1224 <h3>Post-Uninstallation Activity (UEFI-Based PCs)</h3>
1225 </a>
1226
1227 <p>On a UEFI-based PC, when the computer boots and cannot find the rEFInd files, it should move on to the next boot loader in its list. In my experience, some EFI firmware implementations remove boot loaders they can't find from their NVRAM lists, so nothing else will be required, provided you have another working boot loader in your firmware's list. If your firmware doesn't automatically clean up its NVRAM entries, rEFInd's entry will do little harm; however, you can delete it with the <tt>efibootmgr</tt> utility in Linux:</p>
1228
1229 <pre class="listing">
1230 # <tt class="userinput">efibootmgr --verbose</tt>
1231 Timeout: 10 seconds
1232 BootOrder: 0000,0007
1233 Boot0000* rEFInd        HD(2,1b8,64000,f1b7598e-baa8-16ea-4ef6-3ff3b606ac1e)File(\EFI\refind\refind_x64.efi)
1234 Boot0007* CD/DVD Drive  BIOS(3,0,00)PATA: HP DVD Writer 1040r     .
1235 # <tt class="userinput">efibootmgr --delete-bootnum --bootnum 0000</tt>
1236 Timeout: 10 seconds
1237 BootOrder: 0007
1238 Boot0007* CD/DVD Drive</pre>
1239
1240 <p class="sidebar"><b>Warning:</b> As noted earlier, <tt>efibootmgr</tt> has been linked to firmware corruption on some Macs, at least with pre-3.3.0 Linux kernels. Therefore, I don't recommend using <tt>efibootmgr</tt> on Macs.</p>
1241
1242 <p>This example shows use of <tt>efibootmgr</tt>'s <tt>--verbose</tt> (<tt>-v</tt>) option to display boot programs so as to identify which one is rEFInd, followed by <tt>--delete-bootnum</tt> (<tt>-B</tt>) to delete a boot program and <tt>--bootnum</tt> (<tt>-b</tt>) to identify which one to delete. Of course, in this example there's not much else left, so you'd presumably want to install another boot program at this point! If you already have another one installed, you may want to check the <tt>BootOrder</tt> line to determine which one will take precedence when you reboot. If you don't like what it shows, you can adjust it with the <tt>--bootorder</tt> (<tt>-o</tt>) option; consult <tt>efibootmgr</tt>'s <tt>man</tt> page for details.</p>
1243
1244 <p>If you're not using Linux, you may be able to find a utility that serves
1245 a similar function. Under Windows, the <tt>bcdedit</tt> command, described
1246 in the <a href="#windows">section on installing rEFInd under Windows,</a>
1247 may work, although I've not attempted this.</p>
1248
1249 <hr />
1250
1251 <p>copyright &copy; 2012&ndash;2015 by Roderick W. Smith</p>
1252
1253 <p>This document is licensed under the terms of the <a href="FDL-1.3.txt">GNU Free Documentation License (FDL), version 1.3.</a></p>
1254
1255 <p>If you have problems with or comments about this Web page, please e-mail me at <a href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com.</a> Thanks.</p>
1256
1257 <p><a href="index.html">Go to the main rEFInd page</a></p>
1258
1259 <p><a href="yosemite.html">Comments on rEFInd and OS X 10.10 (Yosemite)</a></p>
1260
1261   <p><a href="http://www.rodsbooks.com/">Return</a> to my main Web page.</p>
1262 </body>
1263 </html>