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 <body>
  12   <h1>The rEFInd Boot Manager:<br />Installing rEFInd</h1>
  13
  14 <p class="subhead">by Roderick W. Smith, <a
  15 href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
  16
  17 <p>Originally written: 3/14/2012; last Web page update:
  18 11/7/2012, referencing rEFInd 0.4.7</p>
  19
  20
  21 <p>I'm a technical writer and consultant specializing in Linux technologies. 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>
  22
  23 <table border="1">
  24 <tr>
  25 <td>Donate $1.00</td>
  26 <td>Donate $2.50</td>
  27 <td>Donate $5.00</td>
  28 <td>Donate $10.00</td>
  29 <td>Donate another value</td>
  30 </tr>
  31 <tr>
  32 <td><form name="_xclick" action="https://www.paypal.com/cgi-bin/webscr" method="post">
  33 <input type="hidden" name="cmd" value="_xclick">
  34 <input type="hidden" name="business" value="rodsmith@rodsbooks.com">
  35 <input type="hidden" name="item_name" value="rEFInd Boot Manager">
  36 <input type="hidden" name="currency_code" value="USD">
  37 <input type="hidden" name="amount" value="1.00">
  38 <input type="image" src="http://www.paypal.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="Make payments with PayPal - it's fast, free and secure!">
  39 </form>
  40
  41 </td>
  42 <td><form name="_xclick" action="https://www.paypal.com/cgi-bin/webscr" method="post">
  43 <input type="hidden" name="cmd" value="_xclick">
  44 <input type="hidden" name="business" value="rodsmith@rodsbooks.com">
  45 <input type="hidden" name="item_name" value="rEFInd Boot Manager">
  46 <input type="hidden" name="currency_code" value="USD">
  47 <input type="hidden" name="amount" value="2.50">
  48 <input type="image" src="http://www.paypal.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="Make payments with PayPal - it's fast, free and secure!">
  49 </form>
  50
  51 </td>
  52 <td><form name="_xclick" action="https://www.paypal.com/cgi-bin/webscr" method="post">
  53 <input type="hidden" name="cmd" value="_xclick">
  54 <input type="hidden" name="business" value="rodsmith@rodsbooks.com">
  55 <input type="hidden" name="item_name" value="rEFInd Boot Manager">
  56 <input type="hidden" name="currency_code" value="USD">
  57 <input type="hidden" name="amount" value="5.00">
  58 <input type="image" src="http://www.paypal.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="Make payments with PayPal - it's fast, free and secure!">
  59 </form>
  60
  61 </td>
  62 <td><form name="_xclick" action="https://www.paypal.com/cgi-bin/webscr" method="post">
  63 <input type="hidden" name="cmd" value="_xclick">
  64 <input type="hidden" name="business" value="rodsmith@rodsbooks.com">
  65 <input type="hidden" name="item_name" value="rEFInd Boot Manager">
  66 <input type="hidden" name="currency_code" value="USD">
  67 <input type="hidden" name="amount" value="10.00">
  68 <input type="image" src="http://www.paypal.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="Make payments with PayPal - it's fast, free and secure!">
  69 </form>
  70
  71 </td>
  72 <td>
  73 <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
  74 <input type="hidden" name="cmd" value="_donations">
  75 <input type="hidden" name="business" value="rodsmith@rodsbooks.com">
  76 <input type="hidden" name="lc" value="US">
  77 <input type="hidden" name="no_note" value="0">
  78 <input type="hidden" name="currency_code" value="USD">
  79 <input type="hidden" name="item_name" value="rEFInd Boot Manager">
  80 <input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
  81 <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!">
  82 <img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
  83 </form>
  84 </td></tr>
  85 </table>
  86
  87 <hr />
  88
  89 <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>
  90
  91 <hr />
  92
  93 <p class="sidebar"><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 boot loader, 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>
  94
  95 <p>Once you've uncompressed a rEFInd binary zip file, you must install it to your computer's 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. For Linux and Mac OS X, you can use the installation script, <a href="#installsh"><tt>install.sh</tt>,</a> which provides easy one-command installation on most systems. Occasionally this script will fail, though, so I also provide explicit instructions for <a href="#linux">Linux</a> and <a href="#osx">Mac OS X.</a> Installation under <a href="#windows">Windows</a> also must be done manually. In some cases, you'll have to deviate from the default naming conventions, as described in <a href="#naming">a section on this topic.</a> If you're upgrading rEFInd, see the <a href="#upgrading">section on upgrading.</a> Finally, I describe how to install some <a href="#addons">additional components</a> you might find useful.</a> Note that this page describes installing the main rEFInd program; if you want to use the EFI filesystem drivers included with rEFInd, you should consult the <a href="drivers.html">page on using drivers with rEFInd.</a></p>
  96
  97 <a name="installsh">
  98 <h2>Installing rEFInd Using <tt>install.sh</tt> under Linux or Mac OS X</h2>
  99
 100 <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. Worse, it's conceivable that running <tt>install.sh</tt> from Linux will damage your firmware, requiring that it be re-flashed. 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>
 101
 102 <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 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, though, 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>
 103
 104 <h3>Quick <tt>install.sh</tt> Instructions</h3>
 105
 106 <p>Under Linux, the <tt>install.sh</tt> script installs rEFInd to your disk's ESP. Under Mac OS X, the script installs rEFInd to your current OS X boot partition by default; but you can install to your ESP instead by passing the script the <tt>--esp</tt> option.</p>
 107
 108 <p>Before running this script under Linux, you should ensure that your ESP is 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.) This precaution isn't necessary under OS X.</p>
 109
 110 <p>A sample run under Linux looks something like this:</p>
 111
 112 <pre class="listing">
 113 # <tt class="userinput">./install.sh</tt>
 114 Installing rEFInd on Linux....
 115 ESP was found at /boot/efi using vfat
 116 Copied rEFInd binary file refind_x64.efi
 117
 118 Copying sample configuration file as refind.conf; edit this file to configure
 119 rEFInd.
 120
 121
 122 Installation has completed successfully.</pre>
 123
 124 <p>The output under OS X is a bit different:</p>
 125
 126 <pre class="listing">
 127 $ <tt class="userinput">./install.sh</tt>
 128 Not running as root; attempting to elevate privileges via sudo....
 129 Password:
 130 Installing rEFInd on OS X....
 131 Installing rEFInd to the partition mounted at '/'
 132 Copied rEFInd binary file refind_ia32.efi
 133
 134 Copying sample configuration file as refind.conf; edit this file to configure
 135 rEFInd.
 136
 137
 138 WARNING: If you have an Advanced Format disk, *DO NOT* attempt to check the
 139 bless status with 'bless --info', since this is known to cause disk corruption
 140 on some systems!!
 141
 142
 143 Installation has completed successfully.</pre>
 144
 145 <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>
 146
 147 <a name="extra_installsh">
 148 <h3>Extra <tt>install.sh</tt> Instructions</h3>
 149 </a>
 150
 151 <p>Some details that can affect how the script runs include the following:</p>
 152
 153 <ul>
 154
 155 <li>If you run the script as an ordinary user, it attempts to acquire
 156     <tt>root</tt> privileges by using the <tt>sudo</tt> command. This works
 157     on Mac OS X and some Linux installations (such as under Ubuntu or if
 158     you've added yourself to the <tt>sudo</tt> users list), but on some
 159     Linux installations this will fail. On such systems, you should run
 160     <tt>install.sh</tt> as <tt>root</tt>.</li>
 161
 162 <li>Under OS X, you can run the script with a mouse by opening a Terminal
 163     session and then dragging-and-dropping the <tt>install.sh</tt> file to
 164     the Terminal window. You'll need to press the Return or Enter key to
 165     run the script.</li>
 166
 167 <li>Under OS X, passing the <tt>--esp</tt> option causes the script to
 168     install rEFInd to the ESP. The script finds the first ESP that's
 169     identified by the <tt>diskutil</tt> program and, if it's not already
 170     mounted, mounts it to install rEFInd. Thus, it's conceivable that
 171     <tt>install.sh</tt> will install rEFInd to the wrong partition if you
 172     have multiple disks or if a disk has multiple ESPs. If you believe this
 173     has happened, you may need to re-install manually.</li>
 174
 175 <li>If you're using OS X 10.7's Whole Disk Encryption (WDE) feature, you
 176     <i>must</i> install rEFInd to the ESP, so the <tt>--esp</tt> option to
 177     <tt>install.sh</tt> is required. I'm still a little bit foggy about
 178     what's required to boot the system once this is done; see <a
 179     href="https://sourceforge.net/p/refind/discussion/general/thread/5c7d0195/">this
 180     forum thread</a> for a discussion of the topic.</li>
 181
 182 <li>If you're replacing rEFIt with rEFInd on a Mac, there's a chance that
 183     <tt>install.sh</tt> will warn you about the presence of a program
 184     called <tt>/Library/StartupItems/rEFItBlesser</tt> and ask if you want
 185     to delete it. This program is designed to keep rEFIt set as the boot
 186     manager by automatically re-blessing it if the default boot manager
 187     changes. This is obviously undesirable if you install rEFInd as your
 188     primary boot manager, so it's generally best to remove this program. If
 189     you prefer to keep your options open, you can answer <tt
 190     class="userinput">N</tt> when <tt>install.sh</tt> asks if you want to
 191     delete rEFItBlesser, and instead manually copy it elsewhere. If you
 192     subsequently decide to go back to using rEFIt as your primary boot
 193     manager, you can restore rEFItBlesser to its place.</li>
 194
 195 <li>If you're using OS X and an Advanced Format disk, heed the warning that
 196     <tt>install.sh</tt> displays and <i><b>do not</b></i> use <tt>bless
 197     --info</tt> to check your installation status; this combination has
 198     been reported to cause disk corruption on some Macs!</li>
 199
 200 <li>If you intend to boot BIOS-based OSes on a UEFI-based PC, you
 201     <i>must</i> edit the <tt>refind.conf</tt> file's <tt>scanfor</tt> line
 202     to enable the relevant searches. This is <i>not</i> necessary on Macs,
 203     though; because of the popularity of dual boots with Windows on Macs,
 204     the BIOS/legacy scans are enabled by default on Macs.</li>
 205
 206 <li>Under both Linux and OS X, you can add the <tt>--drivers</tt> option to
 207     have <tt>install.sh</tt> install all the filesystem drivers along with
 208     the main rEFInd program. (The default is to <i>not</i> install any
 209     drivers.)</li>
 210
 211 <li>Under both Linux and OS X, you can add the <tt>--usedefault <tt
 212     class="variable">devicepath</tt></tt> option to install rEFInd to the
 213     specified device as <tt>EFI/BOOT/bootx64.efi</tt> and
 214     <tt>EFI/BOOT/bootia32.efi</tt>. The specified device must be a valid
 215     FAT partition. This option also tells the script to <i>not</i> make
 216     changes to the computer's NVRAM. The idea is that you can easily create
 217     a bootable USB flash drive with this option: Create a proper
 218     FAT-formatted ESP on a disk (say, <tt>/dev/sdd1</tt>) and then type <tt
 219     class="userinput">sh ./install --usedefault /dev/sdd1</tt> to turn the
 220     disk into an emergency disk. This option can also be used to install
 221     rEFInd to an ESP using the <a href="#naming">alternative naming
 222     options</a> described later. This latter usage will result in a
 223     bootable rEFInd only if no other OS has already created an NVRAM
 224     variable pointing to itself.</li>
 225
 226 </ul>
 227
 228 <p>In any event, 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>
 229
 230 <a name="linux">
 231 <h2>Installing rEFInd Manually Using Linux</h2>
 232 </a>
 233
 234 <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>
 235
 236 <pre class="listing">
 237 $ <b>df /boot/efi</b>
 238 Filesystem     1K-blocks  Used Available Use% Mounted on
 239 /dev/sda1         191284 16604    174681   9% /boot/efi
 240 </pre>
 241
 242 <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> package, 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>
 243
 244 <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>
 245
 246 <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>
 247
 248 <ol>
 249
 250 <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.</li>
 251
 252 <li>Type <tt><b>cd /boot/efi/EFI/refind</b></tt> to change into rEFInd's new directory on the ESP.</li>
 253
 254 <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. You can optionally rename the binary you keep as <tt>refind.efi</tt>, but this isn't required. (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>
 255
 256 <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. See the <a href="drivers.html">page on drivers</a> for more on this topic.</li>
 257
 258 <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>
 259
 260 <p class="sidebar"><b>Weird:</b> I've received one report about a Lenovo computer that works only if rEFInd is installed using the name (<tt>-L</tt> parameter) <tt>Windows Boot Manager</tt> and the existing Windows boot loader, if present, is renamed.</p>
 261
 262 <a name="efibootmgr">
 263 <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 need to install this program on some systems; it's a standard part of most distributions' repositories.</li>
 264 </a>
 265
 266 <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>
 267
 268 </ol>
 269
 270 <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>
 271
 272 <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>
 273
 274 <a name="osx">
 275 <h2>Installing rEFInd Manually Using Mac OS X</h2>
 276 </a>
 277
 278 <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>
 279
 280 <pre class="listing">
 281 $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
 282 </pre>
 283
 284 <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>
 285
 286 <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>
 287
 288 <p>The procedure for installing rEFInd on a Mac is similar to that for installing it under Linux, except that you can (and probably should) install it to OS X's system partition or some other HFS+ partition rather than to the ESP, and you must use the <tt>bless</tt> utility rather than <tt>efibootmgr</tt>. To be precise, you should follow these steps:</p>
 289
 290 <ol>
 291
 292 <li>Open a Terminal window in which you'll type the following
 293     commands.</li>
 294
 295 <li>If you want to install rEFInd on your ESP, you must first mount it. You
 296     can do this by typing <b><tt>mkdir /Volumes/esp</tt></b> followed by
 297     <b><tt>sudo mount -t msdos /dev/disk0s1 /Volumes/esp</tt></b>. Note
 298     that this step is usually optional, and it makes the procedure a bit
 299     more complex, so you might want to forego it. On the other hand,
 300     installing to the ESP is required if you're using the whole-disk
 301     encryption feature of OS X 10.7. Note that you may need to change
 302     <tt>/dev/disk0s1</tt> to something else if your ESP is at an unusual
 303     location. Use a tool such as my <a
 304     href="http://www.rodsbooks.com/gdisk/">GPT fdisk (<tt>gdisk</tt>)</a>
 305     to examine your partition table to find your ESP if necessary.</li>
 306
 307 <li>Type <b><tt>sudo mkdir -p /efi/refind</tt></b> to create a suitable
 308     directory for rEFInd. If you want to place rEFInd on the ESP or some
 309     other partition, you should adjust the pathname appropriately, as in
 310     <tt>/Volumes/esp/efi/refind</tt>. Alternatively, you can use the Finder
 311     to create the directory.</li>
 312
 313 <li>Copy the files in the <tt>refind</tt> subdirectory of the rEFInd binary
 314     package to the like-named directory you've just created. You can do
 315     this in the Finder or by typing <b><tt>sudo cp -r refind/*
 316     /efi/refind/</tt></b> in your Terminal window after changing into the
 317     rEFInd package's main directory.</li>
 318
 319 <li>Remove the file for the version of rEFInd you're not using, as in
 320     <b><tt>sudo rm /efi/refind/refind_ia32.efi</tt></b> on a Mac with a
 321     64-bit EFI or <b><tt>sudo rm /efi/refind/refind_x64.efi</tt></b> on a
 322     Mac with a 32-bit EFI.</li>
 323
 324 <li>Optionally, remove the drivers directory for the architecture you're
 325     not using&mdash;<tt>/efi/refind/drivers_ia32</tt> or
 326     <tt>/efi/refind/drivers_x64</tt>, as appropriate. You may also want to
 327     remove some or all of the drivers for the architecture you are using;
 328     if you don't need them, they'll slow down the start process. See the <a
 329     href="drivers.html">page on drivers</a> for more on this topic. Note
 330     that Apple's firmware includes its own HFS+ driver, so the HFS+ driver
 331     provided with rEFInd is useless on Macs.</li>
 332
 333 <li>If this is your first installation, type <b><tt>sudo mv
 334     /efi/refind/refind.conf-sample /efi/refind/refind.conf</tt></b>
 335     (adjusting the path as necessary) to rename the sample configuration
 336     file so that it will serve as a real configuration file. (Again, you
 337     can do this with the Finder, if you prefer.)</li>
 338
 339 <li>"Bless" rEFInd by typing one of the following two commands:
 340     <ul>
 341     <li>If you're installing rEFInd to an ordinary HFS+ volume, type <tt
 342         class="userinput">sudo bless --setBoot --folder /efi/refind --file
 343         /efi/refind/refind_x64.efi</tt>. (Adjust the path and filename as
 344         necessary if you're placing rEFInd somewhere else or using the
 345         32-bit version.)</li>
 346     <li>If you're installing rEFInd on the ESP, type <tt
 347         class="userinput">sudo bless --mount /Volumes/esp --setBoot --file
 348         /Volumes/esp/efi/refind/refind_x64.efi</tt>, adjusting the mount
 349         point and exact path to the file as appropriate for your
 350         installation.</li>
 351     </ul>
 352     As per the Warning earlier, <i>do not</i> use <tt>bless</tt>'s
 353     <tt>--info</tt> option to try to confirm the change to the boot status
 354     unless you're certain you do <i>not</i> have an Advanced Format hard
 355     disk.</li>
 356
 357 <li>If you don't want to reboot immediately after installing rEFInd, you
 358     may optionally unmount the ESP by typing <tt class="userinput">sudo
 359     umount /dev/disk0s1</tt> or <tt class="userinput">sudo umount
 360     /Volumes/esp</tt>. This step isn't strictly required, but if you want
 361     to keep the ESP out of your directory tree, it can be useful.</li>
 362
 363 </ol>
 364
 365 <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>
 366
 367 <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>
 368
 369 <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>
 370
 371 <a name="windows">
 372 <h2>Installing rEFInd Manually Using Windows</h2>
 373 </a>
 374
 375 <p>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>
 376
 377 <ol>
 378
 379 <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>
 380
 381 <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>
 382
 383 <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>
 384
 385 <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>
 386
 387 <li>Type <b><tt>cd S:</tt></b> to change to the ESP.</li>
 388
 389 <li>Type <b><tt>cd EFI\refind</tt></b> to change into the <tt>refind</tt> subdirectory</li>
 390
 391 <li>Type <b><tt>del refind_ia32.efi</tt></b> to delete the unused 32-bit version of rEFInd. (Windows only supports EFI boots on 64-bit EFI implementations and in 64-bit versions of Windows.)</li>
 392
 393 <li>Optionally type <tt class="userinput">rd /s drivers_ia32</tt> to delete the <tt>drivers_ia32</tt> directory and its contents. You may also want to selectively delete some of the drivers in the <tt>drivers_x64</tt> directory, depending on your needs. Unnecessary drivers may slow the rEFInd start process. See the <a href="drivers.html">page on drivers</a> for more on this topic.</li>
 394
 395 <li>Type <b><tt>rename refind.conf-sample refind.conf</tt></b> to rename rEFInd's configuration file.</li>
 396
 397 <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.</li>
 398
 399 <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>
 400
 401 </ol>
 402
 403 <p>At this point, when you reboot, rEFInd should appear as your new default boot program. One caveat: My only EFI Windows installation uses UEFI DUET, which "forgets" its boot options upon reboot. Thus, I'm unable to test the last two steps (which were provided by a helpful user) myself. If it doesn't work for you, you have several other options, such as:</p>
 404
 405 <ul>
 406
 407 <li>You can rename files on the ESP. as described in the next section, <a href="#naming">Alternative Naming Options.</a></li>
 408
 409 <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>.</li>
 410
 411 <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>
 412
 413 </ul>
 414
 415 <a name="naming">
 416 <h2>Alternative Naming Options</h2>
 417 </a>
 418
 419 <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. To do this, follow these steps:</p>
 420
 421 <ol>
 422
 423 <li>Access your ESP and install rEFInd to it, as described in earlier sections.</li>
 424
 425 <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>
 426
 427 <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>
 428
 429 <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>
 430
 431 <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>
 432
 433 </ol>
 434
 435 <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>
 436
 437 <p>If your computer seems to insist on booting an EFI boot loader called <tt>EFI/Microsoft/BOOT/bootmgfw.efi</tt>, be aware that it might not actually be looking for that filename, but for a boot manager with the EFI description <tt>Microsoft Boot Manager</tt>. Changing the description of the "real" <tt>EFI/Microsoft/BOOT/bootmgfw.efi</tt> using <tt>efibootmgr</tt> and then giving rEFInd that description, even when rEFInd is installed in a more conventional location, may work. I've received a report that at least one Lenovo model has this peculiar affliction.</p>
 438
 439 <a name="upgrading">
 440 <h2>Upgrading rEFInd</h2>
 441 </a>
 442
 443 <p>If you've installed an earlier version of rEFInd, you can upgrade a bit more easily than you can install directly:</p>
 444
 445 <ul>
 446
 447 <li>On a UEFI-based PC, under any OS, you should be able to replace your
 448     old rEFInd file with the new one. Make sure that the new rEFInd has the
 449     same name as the old one, and that it's for the correct CPU type. Since
 450     UEFI launches boot programs by filename, a simple file replacement will
 451     suffice to launch the new version. If the new version includes new
 452     icons, you may want to copy some or all of them.</li>
 453
 454 <li>On a Mac, you can copy over the old rEFInd binary file <i>from
 455     Linux</i> and it will usually work, provided you copy <i>directly</i>
 456     over the old file (rather than rename or delete the old file and then
 457     copy the new one in its place). The same caveats about icons as apply
 458     to UEFI-based PCs apply in this case. This method requires an extra
 459     step in Mac OS X, though....</li>
 460
 461 <li>In OS X, if you copy over the original file with the new one, you'll
 462     probably have to re-bless it to make it work.</li>
 463
 464 <li>Under Linux or OS X, you can re-run the <tt>install.sh</tt> script. In
 465     most cases this works fine, but you'll end up with a duplicate of the
 466     icons directory (<tt>icons-backup</tt>, which holds the original icons,
 467     whereas <tt>icons</tt> holds the icons from the new package). Normally
 468     this just wastes some disk space; but if you've customized your icons,
 469     you'll need to copy your altered icons back.</li>
 470
 471 </ul>
 472
 473 <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>
 474
 475 <a name="addons">
 476 <h2>Installing Additional Components</h2>
 477 </a>
 478
 479 <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 these other programs, you must download and install them separately from rEFInd:</p>
 480
 481 <ul>
 482
 483 <li><b><a
 484     href="http://tianocore.git.sourceforge.net/git/gitweb.cgi?p=tianocore/edk2;a=blob_plain;f=EdkShellBinPkg/FullShell/X64/Shell_Full.efi;hb=HEAD">shell.efi</a></b>&mdash;This
 485     file, placed in the ESP's <tt>efi/tools</tt> directory, adds the
 486     ability to launch a text-mode EFI shell from rEFInd. Note that the
 487     download link is to a 64-bit binary that must be renamed before rEFInd
 488     will recognize it. Additional shell download links appear on the <a
 489     href="https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#UEFI_Shell_download_links">Arch
 490     Linux wiki,</a> and on other sites; try a Web search if the shell you
 491     find doesn't work to your satisfaction.</li>
 492
 493 <li><b>gptsync.efi</b>&mdash;This program creates a <a
 494     href="http://www.rodsbooks.com/gdisk/hybrid.html">hybrid MBR</a> from
 495     your regular GPT disk. A hybrid MBR is a dangerous hack that enables
 496     Windows and OS X to coexist on a Macintosh disk. If you're using a
 497     UEFI-based PC, a hybrid MBR will be useless at best, so you shouldn't
 498     create one, and it's safest to not install <tt>gptsync.efi</tt>. If
 499     you're using a hybrid MBR to enable dual-booting Windows and OS X on a
 500     Mac, though, placing this program file in the ESP's or Mac boot
 501     partition's <tt>efi/tools</tt> directory will enable you to regenerate
 502     your hybrid MBR should some other tool convert the MBR to a standard
 503     protective MBR. You can obtain the file from the <a
 504     href="http://refit.sourceforge.net">original rEFIt package.</a></li>
 505
 506 <li><b>Drivers</b>&mdash;You can install drivers to extend the capabilities
 507     of the EFI. rEFInd ships with filesystem drivers for ext2fs and
 508     ReiserFS, which can enable you to boot a Linux kernel with EFI stub
 509     support from an ext2fs, ext3fs, or ReiserFS partition. (rEFInd also
 510     provides ISO-9660 and HFS+ drivers.) You can find additional drivers
 511     from other sources, although they're still on the scarce side. See the
 512     <a href="drivers.html">Using EFI Drivers</a> page for more on this
 513     topic.</li>
 514
 515 </ul>
 516
 517 <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>
 518
 519 <a name="sluggish">
 520 <h2>Fixing a Sluggish Macintosh Boot</h2>
 521 </a>
 522
 523 <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. I've been unable to replicate this problem myself, and its true cause remains mysterious to me. I have found <a href="http://ubuntuforums.org/showpost.php?p=12256273&postcount=200">a Web forum post</a> describing a possible fix. 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>
 524
 525 <ol>
 526
 527 <li>Boot into Linux.</li>
 528
 529 <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>
 530
 531 <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>
 532
 533 <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>
 534
 535 </ol>
 536
 537 <hr />
 538
 539 <p>copyright &copy; 2012 by Roderick W. Smith</p>
 540
 541 <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>
 542
 543 <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>
 544
 545 <p><a href="index.html">Go to the main rEFInd page</a></p>
 546
 547 <p><a href="using.html">Learn how to use rEFInd</a></p>
 548
 549   <p><a href="http://www.rodsbooks.com/">Return</a> to my main Web page.</p>
 550 </body>
 551 </html>