I use a Macpro with 64 bit EFI. As I replaced original Apple graphic card by a new one (non Apple) I have no more access at Boot Menu of the MacPro.
I'd like to install rEFInd on an external USB key I would let plugged all the time so I can get access at a boot menu again.
I formatted my USB key as Mac Filesystem and then run the install.sh script with parameter --ownhfs /dev/disk6s1 (disk6s1 being my usb key). Script executes without error and I can see in Finder it installed some files but my USB key doesn't appear in bootable volumes in System Preferences of Mac OSX :(
Any ideas what's wrong ?
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Boot Menu (Startup Manager http://support.apple.com/kb/ht1310 ) and rEFInd both require the graphics card to have a Mac compatible EFI. Otherwise, the EFI programs won't work or won't be visible. It doesn't matter where you install rEFInd. The only graphics cards that have a Mac compatible EFI are from Apple or the Radeon HD 7950 Mac Edition from Sapphire or the GTX 680 from EVGA. Otherwise, you need to flash the card with an EFI rom.
System Preferences doesn't display all bootable volumes. It only shows Mac OS X and Windows. If you want to boot something else, then you have to use the bless command with the --setBoot option which the install.sh script should have done for you. You can verify the results using the "bless --info" command. For HFS disks, you can check which file is blessed by using "bless --info /Volumes/YourHFSDiskName".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Joe van Tunen is correct about the firmware requirements for video cards. That said, I would also recommend trying to create an external medium using the generic boot filename (EFI/BOOT/bootx64.efi on most systems, which you can create with the --usedefault option to install.sh) rather than the Mac-specific method (created via --ownhfs). Mac firmware is notoriously inconsistent from one model to another, but most recent models support the more general EFI filename.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I use a Macpro with 64 bit EFI. As I replaced original Apple graphic card by a new one (non Apple) I have no more access at Boot Menu of the MacPro.
I'd like to install rEFInd on an external USB key I would let plugged all the time so I can get access at a boot menu again.
I formatted my USB key as Mac Filesystem and then run the install.sh script with parameter --ownhfs /dev/disk6s1 (disk6s1 being my usb key). Script executes without error and I can see in Finder it installed some files but my USB key doesn't appear in bootable volumes in System Preferences of Mac OSX :(
Any ideas what's wrong ?
Thanks
The Boot Menu (Startup Manager http://support.apple.com/kb/ht1310 ) and rEFInd both require the graphics card to have a Mac compatible EFI. Otherwise, the EFI programs won't work or won't be visible. It doesn't matter where you install rEFInd. The only graphics cards that have a Mac compatible EFI are from Apple or the Radeon HD 7950 Mac Edition from Sapphire or the GTX 680 from EVGA. Otherwise, you need to flash the card with an EFI rom.
System Preferences doesn't display all bootable volumes. It only shows Mac OS X and Windows. If you want to boot something else, then you have to use the bless command with the --setBoot option which the install.sh script should have done for you. You can verify the results using the "bless --info" command. For HFS disks, you can check which file is blessed by using "bless --info /Volumes/YourHFSDiskName".
Joe van Tunen is correct about the firmware requirements for video cards. That said, I would also recommend trying to create an external medium using the generic boot filename (
EFI/BOOT/bootx64.efion most systems, which you can create with the--usedefaultoption toinstall.sh) rather than the Mac-specific method (created via--ownhfs). Mac firmware is notoriously inconsistent from one model to another, but most recent models support the more general EFI filename.