From: srs5694 Date: Tue, 23 Feb 2016 14:02:57 +0000 (-0500) Subject: Added documentation on refind-mkdefault script (bootcoup.html and X-Git-Url: https://code.delx.au/refind/commitdiff_plain/af701e2da03597cc45fa171febf7933b1357564a Added documentation on refind-mkdefault script (bootcoup.html and related images). --- diff --git a/docs/refind/asus-bootmanager.jpg b/docs/refind/asus-bootmanager.jpg new file mode 100644 index 0000000..4e86672 Binary files /dev/null and b/docs/refind/asus-bootmanager.jpg differ diff --git a/docs/refind/asus-bootorder.jpg b/docs/refind/asus-bootorder.jpg new file mode 100644 index 0000000..d90f3e3 Binary files /dev/null and b/docs/refind/asus-bootorder.jpg differ diff --git a/docs/refind/bootcoup.html b/docs/refind/bootcoup.html new file mode 100644 index 0000000..d15742b --- /dev/null +++ b/docs/refind/bootcoup.html @@ -0,0 +1,468 @@ + + + + + + The rEFInd Boot Manager: Keeping rEFInd Booting + + + + + + +

The rEFInd Boot Manager:
Keeping rEFInd Booting

+ +

by Roderick W. Smith, rodsmith@rodsbooks.com

+ +

Originally written: 1/28/2016, referencing rEFInd 0.10.2

+ + +

This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!

+ + + + + + + + + + + + + + + + + + + + + + + + +
Donate $1.00Donate $2.50Donate $5.00Donate $10.00Donate $20.00Donate another value
+
+ + + + + + + + + +
+		 +
+ + + + + + + + + +
+		 +
+ + + + + + + + + +
+		 +
+ + + + + + + + + +
+		 +
+ + + + + + + + + +
+		 +
+ + + + + + + + +
+
+ +
+ +

This page is part of the documentation for the rEFInd boot manager. If a Web search has brought you here, you may want to start at the main page.

+ +
+ +
+ +

Once you've installed rEFInd, you may face a new challenge: Keeping it set as your default boot manager. Users of multi-boot computers have long faced similar challenges, because most OSes provide mechanisms to keep themselves booting, even at the cost of disrupting other OSes—or overriding your own choices. On this page, I refer to such unwanted changes as boot coups. Experienced multi-booters know the tools and techniques to avoid or recover from boot coups. If you're new to the EFI world, though, most of the techniques you may know for helping with BIOS-mode booting don't apply to EFI-mode booting.

+ +

This page describes tools and techniques you can use to keep rEFInd set as your default boot manager, or at least to recover it as the default boot option if something else takes over. This page is organized by OS, describing the tools and techniques you can use in each OS to recover from a boot coup—or in some cases, to prevent one from occurring. I begin and end with information on firmware-based tools, though. Chances are you should not read this page straight through; instead, peruse the Contents to the left and pick and OS and, perhaps, a recovery tool or technique you wish to pursue and read the relevant section. In most cases, the recovery technique is fairly quick and painless, once you understand how to do it.

+ +
+ +
+ +

Contents

+ + + +
+ + +

Evading the Guards: Performing a One-Time Boot to Your Desired OS

+ + +

Most EFIs provide their own build-in boot managers. These tools are primitive, and in some cases they can be difficult to reach, but they can be useful if you need to bypass a new system default in order to boot an OS that has the tools you need to control the boot process.

+ +

On Macs, holding the Option key (usually Alt with a PC keyboard) brings up the Mac's boot manager. Typically, the Esc key, Enter key, or a function key (usually F8 or above) does the job on UEFI-based PCs. Some computers provide a prompt for what key will do the job, but this isn't always true. Sometimes the keyboard is disabled in the early stages of the boot process by default—part of a strategy to speed up system boots. Disabling a "fast start" feature in the firmware may work around this problem.

+ +

Once you've found the built-in boot manager, you'll see its display, which is typically a text-mode listing of boot options. On UEFI-based PCs, the user interface is typically similar to the one used in years past on BIOS-based computers to select the boot device; it's simply been upgraded to include the descriptions held in NVRAM for specific boot loaders. (In fact, prompts are often outdated and misleading; as in the below example, they may refer to "boot devices," when in fact most of the options are EFI boot loader programs.) As an example, an ASUS P8 H77-I's boot manager looks like this:

+ +
A typical EFI boot manager display is very + rudimentary.

+ +

You typically select the option you want to boot by using the arrow keys, then hit the Enter key to boot it. If rEFInd is working but has been overridden as the default, you can select it; or if your preferred OS has its own option, you may be able to launch it directly.

+ +

Keep in mind, though, that some of the options on the built-in boot manager's menu may not work, or may work in unexpected ways. For instance, you might see options to boot hard disks in BIOS/CSM/legacy mode. These options might not work; and even if they do, they'll boot the computer in BIOS mode, so you won't be able to use the tools described on this page to correct your boot problems.

+ + +

Staging a Counter-Revolution: Re-Installing rEFInd

+ + +

The most general, and in some cases the easiest, solution to a boot coup is to re-install rEFInd. If you haven't updated rEFInd in a while, this approach has the advantage of providing an update to rEFInd (assuming you first download the latest version). The Installing rEFInd page describes how to install rEFInd from Linux, OS X, Windows, or an EFI shell. The refind-install script preserves your existing refind.conf configuration file, so an upgrade should not affect your customizations. (The rEFInd icons will be updated to the latest versions, but refind-install moves the original icons to a backup directory, so you can restore them if you've customized them or if they've changed and you don't like the new icons.)

+ +

One possible complication to this approach is if you're stuck booting in an unfamiliar OS. In such a case, you may be able to boot into your preferred OS on a one-time basis by using your computer's built-in boot manager. The trouble is that how you do this varies greatly from one computer to another. On a Mac, you should hold down the Option key as the startup chime sounds. On a UEFI-based PC, you can usually access a boot manager menu by hitting the Esc, Enter, or a function key (typically F8 or above) soon after powering on the computer. Some modern computers disable this functionality in the interest of speeding the boot process. You can often re-enable it by disabling the "fast start" option in the firmware—but entering the firmware presents an equal challenge. Microsoft provides a way to do this in Windows 8 and later; see this Lenovo page for documentation on how to use this feature. (The same procedure works on any brand of computer.)

+ + +

Recovering from a Coup Using Linux

+ + +

Linux's primary tool for adjusting the EFI boot order is efibootmgr. If you installed rEFInd from Linux, chances are you used this tool, even if you don't realize it. (The refind-install script calls efibootmgr, and this script is called automatically by the rEFInd RPM and Debian packages). The easiest way to do this is to use the refind-mkdefault script. A more complex but flexible approach is to use efibootmgr directly. I also describe some steps you can take to make it less likely that Linux will stage a boot coup to begin with, thus obviating the need to perform a repair.

+ + +

Using refind-mkdefault to Adjust Your Boot Priority

+ + +

Since version 0.10.3, rEFInd has shipped with a script called refind-mkdefault, which uses efibootmgr to identify rEFInd and set it as the default (first) boot option. Use of this script is quite simple: Launch it as root (or via sudo):

+ +
$ sudo refind-mkdefault
+rEFInd is not the first boot entry; adjusting....
+Setting a boot order of 0000,0002,0085,0003,0081
+ +

The exact output of the script depends on the current state of the system; it might also respond that rEFInd is already the default boot entry or that it could not identify a rEFInd entry, for instance. The boot order shown in this example is meaningless by itself; it's the boot order as identified by efibootmgr; for details, see the next section.

+ +

Instead of using refind-mkdefault manually, you might consider running it automatically at every boot or shutdown. You can, for instance, call it from /etc/rc.local or create a script in /etc/rc6.d that calls it to have it run when you shut down the computer. Details, however, vary from one distribution to another, so you should consult your distribution's documentation for details. If you use it in this way, rEFInd should correct a boot coup caused by an update to GRUB; however, this repair will happen only after a reboot if you call refind-mkdefault in a startup script. If you call it from a shutdown script, rEFInd should correct such a coup before it has a chance to cause problems.

+ +

If you've given the rEFInd entry an unusual name, you can pass the script the -L name or --label name option, as in:

+ +
$ sudo refind-mkdefault -L ubuntu
+ +

This example moves an entry that contains the string ubuntu (case-insensitive) to the top of the boot order. Thus, refind-mkdefault can set any boot program as the default, so long as it's already registered with the firmware. The script searches the entirety of output lines created by efibootmgr -v (as described shortly), and so it matches on descriptions, filenames, and even the obscure EFI codes that identify devices.

+ + +

Using efibootmgr to Adjust Your Boot Priority

+ + +

Adjusting your boot order in Linux is a two-step process: First you must identify the existing boot entries. With that done, you specify a new boot order. You can identify boot entries by typing efibootmgr alone (as root or via sudo). This may be adequate; however, a more complete display, including the name of the boot loader executable, can be obtained by adding -v:

+ +
+$ sudo efibootmgr
+BootCurrent: 0000
+Timeout: 0 seconds
+BootOrder: 0002,0000,0085,0003,0081
+Boot0000* rEFInd Boot Manager
+Boot0002* Windows Boot Manager
+Boot0003* Windows Boot Manager
+Boot0081* Mac OS X
+Boot0085* ubuntu
+
+ +

In this example, the use of -v was not necessary, because the labels were clear and accurate; you can see that the BootOrder line identifies a boot order of Boot0002 (Windows) followed by Boot0000 (rEFInd), then various others. If you're in doubt, you can examine the complete output with efibootmgr -v:

+ +
sudo efibootmgr -v
+BootCurrent: 0000
+Timeout: 0 seconds
+BootOrder: 0002,0000,0085,0003,0081
+Boot0000* rEFInd Boot Manager	HD(1,800,113000,2491a00e-2a89-4dc4-af21-34c436c8f88a)File(\EFI\refind\shimx64.efi)
+Boot0002* Windows Boot Manager	HD(2,113800,113000,8b0b6d94-06af-4894-b9de-13ca354714a5)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
+Boot0003* Windows Boot Manager	HD(1,800,113000,2491a00e-2a89-4dc4-af21-34c436c8f88a)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
+Boot0081* Mac OS X	Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)-.o. .-.e.e. .-.f. .e.f.i.-.a.p.p.l.e.-.p.a.y.l.o.a.d.0.-.d.a.t.a...
+Boot0085* ubuntu	HD(1,800,113000,2491a00e-2a89-4dc4-af21-34c436c8f88a)File(EFI\Ubuntu\grubx64.efi)
+ +

Much of this output looks like gibberish, and is useful only for very advanced diagnostics. Note, however, the part of each line that specifies a filename, in parentheses after File—this information can help disambiguate a misleading or redundant name.

+ +

To adjust the boot order, you must identify the rEFInd entry and then use the -o option to efibootmgr to adjust the order:

+ +
$ sudo efibootmgr -o 0000,0085,0002,0003,0081
+BootCurrent: 0000
+Timeout: 0 seconds
+BootOrder: 0000,0085,0002,0003,0081
+Boot0000* rEFInd Boot Manager
+Boot0002* Windows Boot Manager
+Boot0003* Windows Boot Manager
+Boot0081* Mac OS X
+Boot0085* ubuntu
+ +

In this example, I moved rEFInd to the top of the list, followed by ubuntu (GRUB), Windows, and OS X. You can adjust the order in any way you want. You can also omit items you don't want to include—but be aware that if you omit Windows entirely from the boot list, it's likely to add itself back (at the top of the list) the next time you boot it.

+ + +

Preventing a Linux Coup by Disabling GRUB Updates

+ + +

Once Linux is installed, the usual cause of a Linux boot coup is an update of GRUB. Such updates are relatively rare, but they can happen at any time when the distribution maintainer pushes out a version of GRUB with a bug fix. Therefore, one way to prevent a Linux boot coup is to disable such updates. Unfortunately, the details of how to do this vary from one distribution to another. Furthermore, disabling such updates has its drawbacks.

+ +

One problem with disabling GRUB updates is that you'll be cut off from the benefits they bring—GRUB updates are normally distributed because they contain important bug fixes. These updates might even be security-related. Of course, if you're booting via rEFInd without involving GRUB, you may not care about such updates. This possibility suggests the first way to disable GRUB updates: Remove GRUB entirely.

+ +

To remove GRUB, you must employ your package management system. For instance, on an RPM-based system, you might type:

+ +
# rpm -e grub2 grub2-efi grub2-tools
+ +

On a system that uses Debian packages, a similar command is:

+ +
# dpkg -P grub-efi-amd64 grub-efi-amd64-signed grub-common grub-efi-amd64-bin \
+  grub-common grub2-common shim-signed
+ +

The details of what packages you must remove vary from one distribution to another, though. (The preceding examples are from Fedora and Ubuntu installations.) If you're unsure what packages to remove, you may need to use a your package management tools to track down all GRUB-related packages. GUI tools, such as Yumex for Fedora and Synaptic for Debian-based systems, can be very helpful in this task. Unfortunately, you must sometimes remove packages that you might not want to remove—for instance, the preceding example removes shim-signed from Ubuntu because shim-signed contains a dependency on GRUB, but rEFInd can use Shim for its Secure Boot support. Fortunately, if rEFInd is already booting via Shim, removing the shim-signed package will not remove the shimx64.efi binary from rEFInd's directory, so the system will continue to boot.

+ +

Note also that removing the GRUB packages will not remove the files installed to the EFI System Partition (ESP), so rEFInd will continue to show a GRUB option, normally with an icon for your distribution, in its main menu. If you want to remove that menu entry, you can delete the relevant files, normally from /boot/efi/EFI/distribution_name.

+ +

An added bonus to removing the GRUB packages is that you will no longer have to wait while GRUB's scripts scan your system every time your kernel updates. (Such scans can take well over a minute on a system with lots of installed OSes, and annoy me greatly.) Of course, these scans keep the GRUB menu up-to-date, so if they stop, GRUB will eventually stop working, even if you leave its binaries installed on your ESP.

+ +

One limitation to removing GRUB packages is that your distribution may try to re-install GRUB. As a workaround for Ubuntu systems, I use this dummy package, which claims to be "GRUB 3"—a version high enough that no GRUB 2 update should ever try to displace it. My "GRUB 3" dummy package contains nothing but a few empty directories.

+ +

A less radical approach to preventing boot coups related to GRUB updates is to use your packaging system to lock the current version in place. You can do this with Debian-based installations with the apt-mark hold command, as in:

+ +
# apt-mark hold grub-efi-amd64 grub-efi-amd64-signed grub-common grub-efi-amd64-bin \
+  grub-common grub2-common
+ +

You can achieve a similar result in Fedora by installing the yum-plugin-versionlock package, ensuring that enabled = 1 is set in /etc/yum/pluginconf.d/versionlock.conf, and editing /etc/yum/pluginconf.d/versionlock.list to include the names and versions of packages you want to lock at a particular version.

+ + +

Recovering from a Coup Using OS X

+ + +

A boot coup that leaves a computer booting straight to OS X was most likely caused by an update to OS X—either a software update that installed a fresh copy of the OS X boot loader or a complete re-installation of the OS. In either event, the solution is conceptually similar to the Linux solution, but the tools you use to correct the problem differ. In OS X, you would either use Startup Disk to set rEFInd as the default or use bless to do the same.

+ + +

Using Startup Disk to Adjust Your Boot Priority

+ + +

The Startup Disk utility appears in the System Preferences tool. Unfortunately, it will likely be useless if you installed rEFInd using refind-install and its default options, since this tool is designed to switch between OS X installations; it's not smart enough to detect a rEFInd installation and re-activate it.

+ +

If, however, you installed rEFInd by using the --ownhfs option to refind-install, your rEFInd installation volume should show up as an option in the Startup Disk utility. You should be able to click on it and then click Restart. Note that the name of the rEFInd volume may not be rEFInd, as it is in this screen shot; the name will match whatever volume holds rEFInd on your computer.

+ +
Startup Disk may enable you to reset rEFInd to being + the default boot program.

+ + +

Using bless to Adjust Your Boot Priority

+ + +

The more general solution to resetting rEFInd as the default boot manager from OS X is to follow a subset of the manual OS X installation instructions. Unfortunately, some details depend on where it is installed—on the ESP, on the main OS X root (/) partition, or on a separate HFS+ volume. If rEFInd is installed on its own HFS+ partition, using Startup Disk, as described in the previous section, is likely to be the easier solution. For the other two options, you should first figure out where rEFInd is installed and then follow this procedure:

+ +
    + +
  1. Open a Terminal window in which you'll type the following + commands.
    2. + +
  2. If rEFInd is installed on your ESP, you must first mount it. The + easy way to do this is to use the mountesp script that comes + with rEFInd. When you run it, the script should tell you where the ESP + was mounted. You can do the job manually by typing mkdir + /Volumes/ESP followed by sudo mount -t msdos + /dev/disk0s1 /Volumes/ESP. Note that you may need to change + /dev/disk0s1 to something else if your ESP is at an unusual + location. Type diskutil list or use a tool + such as my GPT fdisk + (gdisk) to examine your partition table to find your ESP + if necessary.
    3. + +
  3. "Bless" rEFInd by typing one of the following two commands: +
      +
    • If rEFInd is installed on the ESP, type sudo bless --mount /Volumes/ESP --setBoot --file + /Volumes/ESP/efi/refind/refind_x64.efi --shortform, adjusting + the mount point and exact path to the file as appropriate for your + installation.
      • +
    • If rEFInd is installed on an ordinary HFS+ volume, type sudo bless --setBoot --folder /efi/refind --file + /efi/refind/refind_x64.efi. (Adjust the path and filename as + necessary if you're placing rEFInd somewhere else or using the + 32-bit version.)
      • +
    4. + +
+ +

One major caveat is that the bless command will fail if System Integrity Protection (SIP) is active. This feature is part of OS X 10.11 (El Capitan) and later, and you will have dealt with it during rEFInd installation if it's active. See this page of the rEFInd documentation for more on this subject. You can use any of the procedures outlined there with reference to installing rEFInd for dealing with a boot coup, as well.

+ +

As with most of the fixes described on this page, this method of recovering from a boot coup will not protect you from future boot coups. Fortunately, OS X updates that create boot coups are fairly rare, but you'll have to resign yourself to the fact that the problem may recur in the future.

+ + +

Recovering from a Coup Using Windows

+ + +

A couple of tools exist to help you manage the boot order in Windows. The easiest of these to use is the third-party EasyUEFI. Microsoft's bcdedit, though, has the advantage of working around a problem in which Windows keeps setting its own boot manager as the default. (This problem is rare, but crops up from time to time.)

+ + +

Using EasyUEFI to Adjust Your Boot Priority

+ + +

The third-party EasyUEFI program is a user-friendly GUI tool for managing EFI boot entries. If a Windows update resets Windows as the default boot program, you can use EasyUEFI to restore rEFInd as the default. Doing so is pretty straightforward:

+ +
    + +
  1. Download and install EasyUEFI.
    2. + +
  2. Launch EasyUEFI. The resulting display will look something like this:
    3. + +
    The Windows EasyUEFI tool enables adjusting the EFI + boot entries in a GUI environment.

    + +
  3. Click the rEFInd entry.
    4. + +
  4. Click the green up-arrow button (at the top of the column of icons between the Boot order and Detailed information panes) as many times as needed to bring rEFInd to the top of the list.
    5. + +
  5. Exit from EasyUEFI. Alternatively, you can select the Power -> Reboot menu entry to reboot and test the change immediately.
    6. + +
+ +

Note that EasyUEFI's menu shows the names of the boot entries. In some cases, rEFInd may be registered under another name. This is particularly likely if you used OS X's bless or Windows' bcdedit tools to register rEFInd with the firmware. You may be able to locate the rEFInd binary by examining the File path entry in the Detailed information pane, after selecting a "candidate" entry.

+ +

Like most of the remedies described on this page, this one makes an immediate change to the boot order but does not guarantee that the problem will not recur. In most cases, rEFInd will remain the primary boot program until it's changed again by another OS update, but all bets are off when that happens.

+ + +

Using bcdedit to Adjust Your Boot Priority

+ + +

You can use a truncated version of the Windows installation instructions to restore rEFInd as the default boot manager:

+ +
    + +
  1. 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.
    2. + +
  2. Type bcdedit /set {bootmgr} path \EFI\refind\refind_x64.efi to set rEFInd as the default EFI boot program. Note that {bootmgr} is entered as such; that's not a notation for a variable. Also, change refind_x64.efi to refind_ia32.efi 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. If you use Shim or PreLoader to boot with Secure Boot active, you should change the name of the binary appropriately.
    3. + +
  3. If you like, type bcdedit /set {bootmgr} description "rEFInd description" to set a description (change rEFInd description as you see fit).
    4. + +
+ +

This procedure, unlike the EasyUEFI one, creates a new boot menu item. It requires that you know the exact path to the rEFInd binary. (If you don't know this detail, you can mount your ESP, as described in the Windows installation instructions, and try to find it.) Overall, it's likely to be easier to use EasyUEFI; however, this procedure has one potential advantage: I've seen reports of cases in which Windows changes the default boot program on every boot. This procedure sometimes puts an end to such shenanigans. Thus, it can serve as a preventive measure against at least some future boot coups. I can't promise that it will work in all such cases, though. In particular, some EFIs, especially older ones, are buggy and ignore or forget their entries. Using bcdedit will not help protect against this problem.

+ + +

Using Your Firmware to Repair a Boot Coup

+ + +

Some, but not all, EFIs provide the means to adjust the boot order themselves. The details of how this works vary greatly from one implementation to another, so I can provide only fairly broad guidance on this point. As an example, consider how to adjust the boot order with the ASUS P8 H77-I motherboard:

+ +
    + +
  1. Turn on the computer.
    2. + +
  2. As the computer begins its Power-On Self-Test (POST), there will be a brief window in which you can hit the F2 or Del key to enter the firmware setup utility. Do so.
    3. + +
  3. In the "EZ-Mode" menu shown below, the boot order is shown graphically near the bottom of the screen. As you move the mouse over the entries, you'll see an expansion of each one. In the screen shot below, the second item is highlighted, and you can see it's rEFInd.
    4. + +
    Some EFIs provide a way to adjust the boot order.

    + +
  4. Click and drag the rEFInd entry to move it to the front of the list.
    5. + +
  5. Hit F10 to save your changes. A dialog box will ask for confirmation; click Save Changes & Reset.
    6. + +
+ +

This procedure is only an example for one EFI. In fact, some EFIs, including the one in the ASUS P8 H77-I, feature multiple user interface modes. The ASUS has an "Advanced" mode, for instance, in which the procedure would be slightly different. They key point, though, is to locate whatever menu displays the boot order and use that menu to adjust it. Such a menu may be shown on the main screen, as in the case of the ASUS' "EZ-Mode," or on a menu you must select—often called "Boot" or something similar. Some EFIs, particularly for low-end fully-assembled desktop and laptop computers, lack this functionality altogether.

+ +

As with most other fixes described on this page, this one won't protect you from future boot coups. Most boot coups are caused by actions of an OS, so prevention must be handled on an OS-by-OS basis.

+ +
+ +

copyright © 2016 by Roderick W. Smith

+ +

This document is licensed under the terms of the GNU Free Documentation License (FDL), version 1.3.

+ +

If you have problems with or comments about this Web page, please e-mail me at rodsmith@rodsbooks.com. Thanks.

+ +

Go to the main rEFInd page

+ +

Comments on rEFInd and OS X 10.10 (Yosemite)

+ +

Return to my main Web page.

+ + diff --git a/docs/refind/easyuefi.png b/docs/refind/easyuefi.png new file mode 100644 index 0000000..e5dfe4c Binary files /dev/null and b/docs/refind/easyuefi.png differ diff --git a/docs/refind/index.html b/docs/refind/index.html index 7236e95..402ec25 100644 --- a/docs/refind/index.html +++ b/docs/refind/index.html @@ -156,6 +156,8 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com

  • Installing rEFInd—Instructions for installing rEFInd, using Linux, OS X, and Windows
    • +
  • Keeping rEFInd Booting—Instructions for keeping rEFInd in charge of the boot process or recovering when another OS takes control
    • +
  • rEFInd and OS X 10.10 (Yosemite)—Apple's latest OS X makes some changes that require your attention (this subpage is rendered obsolete by rEFInd 0.8.4 and later
  • rEFInd and System Integrity Protection—How to install rEFInd on Macs running OS X 10.11 (El Capitan) diff --git a/docs/refind/installing.html b/docs/refind/installing.html index d77de10..d749e68 100644 --- a/docs/refind/installing.html +++ b/docs/refind/installing.html @@ -993,11 +993,11 @@ $ ioreg -l -p IODeviceTree | grep firmware-abi

    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:

    -
    The OS X Startup Disk tool enables you to reset a Mac + <br /><center><img src=

    -

    Select your startup disk (Macintosh HD OS X, 10.10.1 in this example) and then click Restart. The computer should reboot into OS X, bypassing rEFInd.

    +

    Select your startup disk (Macintosh HD OS X, 10.11.3 in this example) and then click Restart. The computer should reboot into OS X, bypassing rEFInd.

    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 Installing rEFInd Manually Using Mac OS X:

    @@ -1098,7 +1098,7 @@ may work, although I've not attempted this.

    Go to the main rEFInd page

    -

    Comments on rEFInd and OS X 10.10 (Yosemite)

    +

    Preventing and Repairing Boot Coups

    Return to my main Web page.

    diff --git a/docs/refind/startup-disk.png b/docs/refind/startup-disk.png index 19ac11f..b71a414 100644 Binary files a/docs/refind/startup-disk.png and b/docs/refind/startup-disk.png differ