rEFInd goes beyond rEFIt in that rEFInd better handles systems with many boot loaders, gives better control over the boot loader search process, and allows users to define their boot loader entries. Like rEFIt, rEFInd can auto-detect your installed EFI boot loaders, and it presents a pretty GUI menu of boot options. you can use it boot into a temporary GRUB2 menu, using command like configfile (gpt0,X)/boot/grub/grub.cfg (where X is your Linux partion or your /boot partition) will get you your old GRUB2 menu, then it should work as usual. Downloading rEFInd 0.13.2 rEFInd is a fork of the rEFIt boot manager. Hold down Option during startup, your USB drive will show as EFI boot. You could create a standalone GRUB2 EFI image, then put it at /EFI/boot/boot圆4.efi of your USB drive partition (FAT32 format). If you want to boot into Yosemite, you have to hold down Option during startup, and choose your Yosemite partition.Īnother workaround is using a USB drive to boot a third party bootloader.įor example, check out this page. On my Macbook Air, it took 40 seconds until the rEFInd menu showed up and Yosemite partition wasn't recognized and listed in the menu, only my linux bootloader(grub2efi) and recovery partition were detected. Sudo bless -mount /Volumes/EFI -setBoot -file /Volumes/EFI/EFI/refind/refind_圆4.efi
Refind boot manager yosemite install#
I assume you have already installed rEFInd by running the install.sh script using default arguments (rEFInd should be install at /EFI/refind). Normally, the mount point should be /Volumes/EFIĢ. Open Disk Utility, select EFI partition and mount it. So, I tried install rEFInd manually into the EFI partition, and it worked.ġ. I think the reason of rEFInd is no longer working under Yosemite is because the root partition of the system does not reside in a physical partition any more, thus rEFInd will not be able to be recognized at the boot stage. I figured out a workaround for using rEFInd in Yosemite, but please note that it is probably not the best solution. Some users report that they need to enter one or two dummy entries, as in dont_scan_volumes foo,bar, to get it to work. This prevents the problems you are encountering. Like rEFIt, rEFInd can auto-detect your installed EFI boot loaders and it presents a pretty GUI menu of boot options. Personally, I installed rEFInd on my computer to its own partition. rEFInd is a fork of the rEFIt boot manager. The answer, given below, applies to Yosemite (OS X 10.10) and possibly earlier versions of OS X. Uncomment this line and remove the "Recovery HD" item from the line. My answer, to an unrelated question, outlines this new preferred method to start the rEFInd Boot Manager and Linux operating systems. In your favorite editor, locate the dont_scan_volumes line, which is commented out with a # symbol at the start of the line by default. Edit your new nf file, which should be located as described in the previous step.You should copy the file to either /Volumes/esp/EFI/refind/ (if you used -esp and mounted the ESP at /Volumes/esp) or to /Volumes/Mountpoint/System/Library/CoreServices/ (if you used a dedicated HFS+ volume note that Mountpoint will be the name of the volume). If you backed up your nf file, you can now copy it over your new nf file.If not, locate it and mount it with Disk Utility or mount. If you used the -ownhfs device-file installation option, the target partition should already be mounted, normally somewhere under /Volumes.If you installed rEFInd to your ESP, typing mkdir /Volumes/esp followed by sudo mount -t msdos /dev/disk0s1 /Volumes/esp will probably work, although in some cases your ESP won't be /dev/disk0s1, so you may need to change this detail.The details depend on how you installed it: The latter is preferable, but requires either a dedicated partition for rEFInd or an HFS+ data partition that is currently not bootable.Įnsure that the partition to which you've installed rEFInd is mounted. Re-install rEFInd, as described in the Installing rEFInd page but be sure to use the -esp or -ownhfs device-file option.Remove the /EFI/refind directory tree it's useless now, and its presence may cause confusion.If you've made changes to /EFI/refind/nf, back it up.If your rEFInd installation is currently starting but is not showing an OS X option, skip to step #7 but if rEFInd isn't starting, follow steps #2–7. Holding Option (or Alt) while powering up will normally give you Apple's own boot manager, which should enable you to boot to OS X. Boot to OS X, using whatever means is available to you.The official guidelines can be found on the rEFInd web site. # from /etc/grub.I'm going to reanswer my own question here because there is now an official solution from rEFInd, and thus I believe this is the right way to go about this. # It is automatically generated by grub-mkconfig using templates I have error message: error file'/mach_kernel' not found.
Refind boot manager yosemite mac os x#
now I have problem with booting Mac OS X Yosemite. I change boot order on my macbook in accordance with this link.