X-Git-Url: https://code.delx.au/refind/blobdiff_plain/1c723f224b1bc771a4192a2679831c7a6d21c264..bfe73b5fa6321273b7cf86b02a3c2d114a167bc9:/docs/refind/drivers.html diff --git a/docs/refind/drivers.html b/docs/refind/drivers.html index 9b99a00..a497a71 100644 --- a/docs/refind/drivers.html +++ b/docs/refind/drivers.html @@ -283,7 +283,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com

All of these drivers rely on filesystem wrapper code written by rEFIt's author, Christoph Phisterer.

-

Note: rEFInd's install.sh script, when run from Linux, installs the driver required to read the /boot directory. Under OS X, the install.sh script installs the ext4fs driver if the script detects a Linux partition—but you might need to change this driver if you use another filesystem. The script installs all the available drivers if you pass it the --alldrivers option. (I do not recommend using this feature except for creating general-purpose USB flash drives with rEFInd, since having too many drivers can cause various problems.) See the Installing rEFInd page for details.

+

Note: rEFInd's refind-install script, when run from Linux, installs the driver required to read the /boot directory. Under OS X, the refind-install script installs the ext4fs driver if the script detects a Linux partition—but you might need to change this driver if you use another filesystem. The script installs all the available drivers if you pass it the --alldrivers option. (I do not recommend using this feature except for creating general-purpose USB flash drives with rEFInd, since having too many drivers can cause various problems.) See the Installing rEFInd page for details.

If you want to use one or more of these drivers, you can install them from the rEFInd binary package from the refind/drivers_arch directory, where arch is a CPU architecture code—x64 or ia32. The files are named after the filesystems they handle, such as ext4_x64.efi for the 64-bit ext4fs driver. You should copy the files for the filesystems you want to use to the drivers or drivers_arch subdirectory of the main rEFInd installation directory. (You may need to create this subdirectory.) Be careful to install drivers only for your own architecture. Attempting to load drivers for the wrong CPU type will cause a small delay at best, or may cause the computer to crash at worst. I've placed rEFInd's drivers in directories that are named to minimize this risk, but you should exercise care when copying driver files.