-<a name="notes">
-<h2>Notes on Specific Drivers</h2>
-</a>
-
-<p class="sidebar"><b>Warning:</b> When compiled with GNU-EFI, rEFInd's drivers hang when run on my 32-bit Mac Mini. The TianoCore-compiled versions are fine, and the GNU-EFI-built binaries are fine on a 32-bit VirtualBox. The 64-bit GNU-EFI-built versions are fine on a MacBook Pro. Thus, the problem is very limited in scope. The problem can be quite serious if you run into it, though, since you must bypass rEFInd to boot the computer. In debugging the problem, I found that a key funtion was being entered mid-function, which suggests either an EFI bug or a problem with the compiler or related tools. In any event, the solution is simple: Use driver binaries built with TianoCore if you have a 32-bit Mac.</p>
-
-<p>I've tested several of the drivers described on this page on a handful
-of systems. The Pfisterer ext2fs driver (from any source) works on both
-ext2fs and ext3fs, but not on ext4fs—but Agner's derivative ext4fs
-driver handles ext4fs, so that's not a problem. The ReiserFS driver is
-obviously useful only on ReiserFS partitions. (Reiser4 is not supported, as
-far as I know.) The Btrfs driver is the newest of the Linux filesystem
-drivers included with rEFInd, and so I've tested it the least, but it's
-worked for me on several test systems. Given that ext2fs, ext3fs, and
-ReiserFS are getting a bit on in age by Linux standards, you might do well
-to use them on a separate Linux <tt>/boot</tt> partition; however, if
-you're willing to use ext3fs, ext4fs, Btrfs, or ReiserFS on your root
-(<tt>/</tt>) filesystem, you can use the EFI drivers to read your kernel
-from it. Note that this assumes you use conventional partitions; to the
-best of my knowledge, there's no EFI driver for Linux's Logical Volume
-Manager (LVM) or Redundant Array of Independent Disks (RAID)
-configurations, so the EFI can't access filesystems stored in these
-ways.</p>
-
-<p>As noted earlier, rEFInd's drivers prior to version 0.7.0, as well as related drivers from rEFIt, Clover, and VirtualBox, suffer from speed problems. These problems are mostly minor, adding a second or two to boot times; but on some computers, the speed problems can be dramatic, boosting kernel-load times up to as much as three minutes (under VirtualBox). If you run into excessive boot times with such a driver, try switching to the latest rEFInd driver instead. You might also try Pete Batard's efifs drivers.</p>
-
-<p>Although ext2fs, ext3fs, ext4fs, and ReiserFS are all case-sensitive, these drivers treat them in a case-insensitive way. Symbolic links work; however, rEFInd 0.6.11 and later ignore symbolic links, since many distributions use them in a way that creates redundant or non-functional entries in the rEFInd menu. You should be able to use hard links if you want to use a single kernel file in multiple ways (say for two distributions).</p>
-