X-Git-Url: https://code.delx.au/refind/blobdiff_plain/fae4a8d3fada7d96cf0e50e13622a7ca72b17c0a..65eb839a6d8d68a439056473a0d3728dfd39d2c4:/docs/refind/installing.html diff --git a/docs/refind/installing.html b/docs/refind/installing.html index c68268f..0b28864 100644 --- a/docs/refind/installing.html +++ b/docs/refind/installing.html @@ -15,7 +15,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com

Originally written: 3/14/2012; last Web page update: -5/15/2012, referencing rEFInd 0.3.5

+5/20/2012, referencing rEFInd 0.4.0

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!

@@ -92,7 +92,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com

Important: A rEFInd zip file, when uncompressed, creates a directory called refind-version, where version is the version number. This directory includes a subdirectory called refind that holds the boot loader, along with another that holds documentation, as well as miscellaneous files in refind-version itself. When I refer to "the refind directory" on this page, I mean the directory with that precise name, not the refind-version directory that is its parent.

-

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, install.sh, which provides easy one-command installation on most systems. Occasionally this script will fail, though, so I also provide explicit instructions for Linux and Mac OS X. Installation under Windows also must be done manually. In some cases, you'll have to deviate from the default naming conventions, as described in a section on this topic. If you're upgrading rEFInd, see the section on upgrading. Finally, I describe how to install some additional components you might find useful.

+

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, install.sh, which provides easy one-command installation on most systems. Occasionally this script will fail, though, so I also provide explicit instructions for Linux and Mac OS X. Installation under Windows also must be done manually. In some cases, you'll have to deviate from the default naming conventions, as described in a section on this topic. If you're upgrading rEFInd, see the section on upgrading. Finally, I describe how to install some additional components you might find useful. 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 page on using drivers with rEFInd.

Installing rEFInd Using install.sh under Linux or Mac OS X

@@ -198,12 +198,14 @@ Filesystem 1K-blocks Used Available Use% Mounted on
    -
  1. Type cp -r refind /boot/efi/EFI/ from the refind-version directory in which the refind directory exists. This copies all the files that rEFInd needs to work.
    2. +
  2. Type cp -r refind /boot/efi/EFI/ from the refind-version directory in which the refind directory exists. This copies all the files that rEFInd needs to work. Note that this includes all of rEFInd's drivers.
  3. Type cd /boot/efi/EFI/refind to change into rEFInd's new directory on the ESP.
  4. Type rm refind_ia32.efi to remove the IA32 binary if you're using an x86-64 (64-bit) system; or type rm refind_x64.efi to remove the x86-64 binary if you're using an x86 (32-bit) system. You can optionally rename the binary you keep as refind.efi, 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 refind_x64.efi.
    5. +
  5. Optionally, type rm -r drivers_ia32 to remove the x86 drivers from an x86-64 system, or rm -r drivers_x64 to remove the x86-64 drivers from a 32-bit x86 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 page on drivers for more on this topic.
    6. +
  6. Rename the configuration file by typing mv refind.conf-sample refind.conf. Consult the Editing the rEFInd Configuration File page for information on how to adjust your options.
    7. @@ -268,6 +270,15 @@ $ ioreg -l -p IODeviceTree | grep firmware-abi 64-bit EFI or sudo rm /efi/refind/refind_x64.efi on a Mac with a 32-bit EFI. +
  7. Optionally, remove the drivers directory for the architecture you're + not using—/efi/refind/drivers_ia32 or + /efi/refind/drivers_x64, as appropriate. 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 page on drivers for more on this topic. Note + that Apple's firmware includes its own HFS+ driver, so the HFS+ driver + provided with rEFInd is useless on Macs.
    8. +
  8. If this is your first installation, type sudo mv /efi/refind/refind.conf-sample /efi/refind/refind.conf (adjusting the path as necessary) to rename the sample configuration @@ -322,6 +333,8 @@ $ ioreg -l -p IODeviceTree | grep firmware-abi
  9. Type del refind_ia32.efi 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.)
    10. +
  10. Optionally type rd /s drivers_ia32 to delete the drivers_ia32 directory and its contents. You may also want to selectively delete some of the drivers in the drivers_x64 directory, depending on your needs. Unnecessary drivers may slow the rEFInd start process. See the page on drivers for more on this topic.
    11. +
  11. Type rename refind.conf-sample refind.conf to rename rEFInd's configuration file.
  12. 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.
    13. @@ -428,10 +441,12 @@ $ ioreg -l -p IODeviceTree | grep firmware-abi href="http://refit.sourceforge.net">original rEFIt package.
  13. Drivers—You can install drivers to extend the capabilities - of the EFI. Most notably, filesystem drivers for ext2fs and ReiserFS - are available. These can enable you to boot a Linux kernel with EFI - stub support from an ext2fs, ext3fs, or ReiserFS partition. See the Using EFI Drivers page for more on this + of the EFI. rEFInd ships with filesystem drivers for ext2fs and + ReiserFS, which can enable you to boot a Linux kernel with EFI stub + support from an ext2fs, ext3fs, or ReiserFS partition. (rEFInd also + provides ISO-9660 and HFS+ drivers.) You can find additional drivers + from other sources, although they're still on the scarce side. See the + Using EFI Drivers page for more on this topic.