Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
A quick test shows no bootscreen. I did…

1) clone primary SSD to backup HDD (tested bootable)

2) install cover (all default setting, GPU is HD7950)

3) select HDD to boot, restart

4) hear the chime, but black screen only. HOWEVER, all USB 3.0 drives work (card reader / HDD enclosure LED shows that all SD cards / HDDs are mounted). That's just few seconds after the chime, so, 100% not load to OS desktop yet. Something properly initialise the USB 3.0 card (KT4004).

5) no loading sound from HDD, the computer seems waiting for something (may be cover is actually there but I just can't see), so, I press Enter (assume it's pointing to the default HDD).

6) continue to boot, and then confirmed that's boot from the backup HDD.


So, the good news is.

A) it won't kill anything

B) USB 3.0 may be bootable!!!


But I need more time to figure out if I can make cover properly initialise the GPU.


Try putting the relevant graphic kexts into the relevant folder in Clover for your version of macOS.
 
I don't know how this procedure would work with AMD/ATI. My guess is that, Clover should be able to initialize the video card. Secondly, since we don't have to do anything special to activate the AMD/ATI drivers, it should just work. Again, this is all speculation on my part...

Yes, if you don't change any settings, I think that Clover won't do anything and will just act as a boot loader that you can use to select whatever operating systems you have on your system. Example:
View attachment 673430
Source: Random Clover boot screenshot I got from Google (The appearance of this is completely customizable and will most likely look different for you)
looks good
 
A quick test shows no bootscreen. I did…

1) clone primary SSD to backup HDD (tested bootable)

2) install cover (all default setting, GPU is HD7950)

3) select HDD to boot, restart

4) hear the chime, but black screen only. HOWEVER, all USB 3.0 drives work (card reader / HDD enclosure LED shows that all SD cards / HDDs are mounted). That's just few seconds after the chime, so, 100% not load to OS desktop yet. Something properly initialise the USB 3.0 card (KT4004).

5) no loading sound from HDD, the computer seems waiting for something (may be cover is actually there but I just can't see), so, I press Enter (assume it's pointing to the default HDD).

6) continue to boot, and then confirmed that's boot from the backup HDD.


So, the good news is.

A) it won't kill anything

B) USB 3.0 may be bootable!!!


But I need more time to figure out if I can make cover properly initialise the GPU.

Hmm. Yes, it does sound like Clover is loaded but it's not initializing the video card. Did you choose Legacy when installing clover?

Unfortunately, I have no experience with AMD/ATI video cards with any recent version of macOS... :(

Maybe you can try setting the default boot volume with Clover Configurator and then press the Return key when you believe the Clover boot loader has loaded to see if booting macOS will get you video.
Screen Shot 2016-11-22 at 4.11.29 PM.png
 
Hmm. Yes, it does sound like Clover is loaded but it's not initializing the video card. Did you choose Legacy when installing clover?

Unfortunately, I have no experience with AMD/ATI video cards with any recent version of macOS... :(

Maybe you can try setting the default boot volume with Clover Configurator and then press the Return key when you believe the Clover boot loader has loaded to see if booting macOS will get you video.
View attachment 674161

No 100%, but this is what I did. That 2 ticks are default config, no other ticks. And the 1st item "UEFI booting only" remain uncheck, so, I think it means legacy also supported.
Screen Shot 2016-11-23 at 13.18.44.jpg

When I try to use cover configurator, I get this warning. Should I duplicate the plist file, mod it, and than fix the permission by myself? (This warning appear regardless if I mount the EFI partition or not)
Screen Shot 2016-11-23 at 13.23.35.jpg

[doublepost=1479878973][/doublepost]
Try putting the relevant graphic kexts into the relevant folder in Clover for your version of macOS.

Thanks for your suggestion, can you tell me more details on how to do it? Cover is more complicated than I expected.
 
I think "Install Clover in the ESP" may need to be set.

For the config.plist, I've never encountered that, i would duplicate because I don't know the correct permissions to set it to.
 
A simple UEFI install of Clover with no additional configuration should work. AMD cards don't need any special configuration, just leave Inject / Ati to False, no additional boot flags.

I'm not sure if you can select Clover as default boot volume from the system pref pane or if it has to be blessed from the Terminal. Can't test that locally because my MacPro has a broken NVRAM. :confused:
 
  • Like
Reactions: pastrychef
h9826790, any update on using Clover?

I stopped the study after only a few try, because it require more knowledge than I expect. I may resume that study, but there are many other things for me has higher priority at this moment.

Anyway, no definite conclusion yet, however, from my tests. It seems clover can make my USB 3.0 card work before macOS kick in. So, the hope is still there.
 
  • Like
Reactions: ActionableMango
I found this thread by chance and thought it looked interesting so thought I'd give this a try. Mac Pro 5.1 GTX980 pc nvidia card hence no boot screen, have plenty of drives to clone and experiment with however…

I fell at the first hurdle, couldn't even get the installer to work as I get an error message: Package is incompatible with this version of OS X.

From the google research I've done it looks like it is to do with the rootless/SIP protection introduced in this version of the OS. From what I understand, either an updated installer is required, or to disable SIP before doing the install which involves booting into recovery mode and punching in some terminal commands. All well and good, but I don't get a boot screen, so bit of a catch-22.

I've opened a ticket on their site so will see what comes of it. Just thought I'd put it out there…
 
  • Like
Reactions: m4v3r1ck
From what I understand, either an updated installer is required, or to disable SIP before doing the install which involves booting into recovery mode and punching in some terminal commands. All well and good, but I don't get a boot screen, so bit of a catch-22.

I thought I've read that recovery mode works with unflashed cards. I think h9826790 has done this.
 
I thought I've read that recovery mode works with unflashed cards. I think h9826790 has done this.

Correct, but that should be only applicable to the card that has native Apple driver. Since 980 require web driver to work, and there is no web driver avail in the recovery partition. So, I will say that's a no go for Maxwell card. Even worse, from memory, at least one member reported that even a flashed Maxwell card can't access the recovery partition in Sierra now, but I cannot test this by myself.
 
hmmm, OS X does have some default drivers for this card albeit not as well optimised as the NVidia drivers- there's a control panel in preferences which lets you switch between the 2.

I suppose the only way is to test it out, will let you know what happens…
 
There are no "default drivers" in OS X for this GPU, you won't see anything without the WebDrivers with an unflashed Maxwell card.

It might be possible to copy the WebDriver .kexts into the Recovery partition, never tried to do this though.
 
  • Like
Reactions: h9826790
You may be right. I tried to reboot in recovery mode but just got a black screen and upon restart an error message and log hinting at a kernel panic (I think), I've include it below just for reference in case you guys understand it.

You'd have to talk me thought the copying of kext files (from/to) though Florian, i can give it a go on my spare drive so no harm done if it cracks out.

---------------------------------------------

Anonymous UUID: E2427E43-F897-7A83-3077-C7963C3825EE

Fri Mar 3 14:14:01 2017

*** Panic Report ***
panic(cpu 8 caller 0xffffff801fe16df2): Kernel trap at 0xffffff7fa2648a1d, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000020, CR3: 0x000000001a318018, CR4: 0x00000000000226e0
RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0x0000000000000000, RDX: 0x0000000000000000
RSP: 0xffffff82e56a3b90, RBP: 0xffffff82e56a3ba0, RSI: 0x000000000000000e, RDI: 0x0000000000000000
R8: 0x0000000000000026, R9: 0xffffff804b5f441b, R10: 0x000000000000000c, R11: 0x0000000000000018
R12: 0xffffff804cb66000, R13: 0xffffff804cb66000, R14: 0xffffff804cb72800, R15: 0xffffff804cae7000
RFL: 0x0000000000010246, RIP: 0xffffff7fa2648a1d, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000020, Error code: 0x0000000000000000, Fault CPU: 0x8

Backtrace (CPU 8), Frame : Return Address
0xffffff82e56a3840 : 0xffffff801fd2ad21
0xffffff82e56a38c0 : 0xffffff801fe16df2
0xffffff82e56a3a80 : 0xffffff801fe33ca3
0xffffff82e56a3aa0 : 0xffffff7fa2648a1d
0xffffff82e56a3ba0 : 0xffffff7fa25edccc
0xffffff82e56a3be0 : 0xffffff7fa235a728
0xffffff82e56a3c70 : 0xffffff7fa235244e
0xffffff82e56a3cb0 : 0xffffff7fa25ee980
0xffffff82e56a3d00 : 0xffffff80202b6631
0xffffff82e56a3d50 : 0xffffff80202fde35
0xffffff82e56a3dc0 : 0xffffff801fde17de
0xffffff82e56a3e10 : 0xffffff801fd2ef8c
0xffffff82e56a3e40 : 0xffffff801fd139f3
0xffffff82e56a3e90 : 0xffffff801fd2429d
0xffffff82e56a3f10 : 0xffffff801fe0231a
0xffffff82e56a3fb0 : 0xffffff801fe344c6
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(2.4.1)[8922721D-5517-3883-BD3A-57422D0244A0]@0xffffff7fa2348000->0xffffff7fa2381fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[BDA92C3B-AD86-33E5-A7F1-1603465350A7]@0xffffff7fa044f000
com.apple.nvidia.driver.NVDAResman(10.0.4)[95736EED-9154-3CBF-B639-6038E7128035]@0xffffff7fa25eb000->0xffffff7fa286bfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[BDA92C3B-AD86-33E5-A7F1-1603465350A7]@0xffffff7fa044f000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[7372D580-6DDE-3457-B043-49B8447FC9D2]@0xffffff7fa23d5000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[8922721D-5517-3883-BD3A-57422D0244A0]@0xffffff7fa2348000
dependency: com.apple.AppleGraphicsDeviceControl(3.10.25)[DFDCFB7E-74E4-397E-AA6F-6ECFC41D5649]@0xffffff7fa25e6000

BSD process name corresponding to current thread: WindowServer
Boot args: nvda_drv=1 rp=file:///com.apple.recovery.boot/BaseSystem.dmg

Mac OS version:
14F27

Kernel version:
Darwin Kernel Version 14.5.0: Wed Jul 29 02:26:53 PDT 2015; root:xnu-2782.40.9~1/RELEASE_X86_64
Kernel UUID: 58F06365-45C7-3CA7-B80D-173AFD1A03C4
Kernel slide: 0x000000001fa00000
Kernel text base: 0xffffff801fc00000
__HIB text base: 0xffffff801fb00000
System model name: MacPro5,1 (Mac-F221BEC8)

System uptime in nanoseconds: 34986094500
last loaded kext at 33392623686: com.apple.iokit.IOUserEthernet 1.0.1 (addr 0xffffff7fa28e7000, size 36864)
loaded kexts:
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.iokit.IOBluetoothSerialManager 4.3.6f3
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleMCCSControl 1.2.12
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleTyMCEDriver 1.0.2d2
com.apple.driver.AGPM 110.19.6
com.apple.driver.AppleMikeyDriver 272.18.1
com.apple.driver.AppleHDAHardwareConfigDriver 272.18.1
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleHDA 272.18.1
com.apple.driver.AppleHV 1
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.6f3
com.apple.driver.AppleLPC 1.7.3
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.nvidia.NVDAStartup 10.0.4
com.apple.driver.AppleFIVRDriver 4.1.0
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.nke.webcontentfilter 5
com.apple.driver.DiskImages.SparseDiskImage 398
com.apple.driver.DiskImages.ReadWriteDiskImage 398
com.apple.driver.DiskImages.UDIFDiskImage 398
com.apple.driver.DiskImages.HTTPBackingStore 398
com.apple.driver.DiskImages.FileBackingStore 398
com.apple.driver.DiskImages.RAMBackingStore 398
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.7.1
com.apple.iokit.IOAHCIPassThrough 1.0.3
com.apple.driver.AppleUSBDisplays 372.1
com.apple.iokit.SCSITaskUserClient 3.7.5
com.apple.BootCache 36
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.driver.AppleUSBHub 705.4.2
com.apple.driver.AppleFWOHCI 5.5.2
com.apple.driver.AppleUSBXHCI 710.4.11
com.apple.driver.Intel82574L 2.6.8b1
com.apple.driver.AirPort.Brcm4331 800.20.24
com.apple.driver.AppleUSBEHCI 705.4.14
com.apple.driver.AppleUSBUHCI 656.4.1
com.apple.driver.AppleAHCIPort 3.1.2
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleACPIButtons 3.1
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 3.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.driver.AppleIntelCPUPowerManagementDriver 218.0.0
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.nke.applicationfirewall 161
com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
com.apple.kext.MojoKDP 2.0.1
com.apple.iokit.IOSurface 97.4
com.apple.iokit.IOSerialFamily 11
com.apple.nvidia.driver.NVDAResman 10.0.4
com.apple.AppleGraphicsDeviceControl 3.10.25
com.apple.driver.AppleSMBusController 1.0.13d1
com.apple.driver.DspFuncLib 272.18.1
com.apple.kext.OSvKernDSPLib 1.15
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.6f3
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.driver.AppleHDAController 272.18.1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOHDAFamily 272.18.1
com.apple.iokit.IOAudioFamily 203.3
com.apple.vecLib.kext 1.2.0
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleSMC 3.1.9
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.9.1d7
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.iokit.IOUSBUserClient 705.4.0
com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.5
com.apple.iokit.IOUSBMassStorageClass 3.7.2
com.apple.driver.DiskImages.KernelBacked 398
com.apple.driver.AppleUSBHIDKeyboard 176.2
com.apple.driver.AppleHIDKeyboard 176.2
com.apple.iokit.IOUSBHIDDriver 705.4.0
com.apple.iokit.IOUSBHIDDriverPM 710.4.7
com.apple.driver.AppleUSBMergeNub 705.4.0
com.apple.driver.AppleUSBComposite 705.4.9
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.5
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.6.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.5
com.apple.iokit.IOFireWireFamily 4.5.8
com.apple.iokit.IO80211Family 730.60
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOUSBFamily 720.4.4
com.apple.iokit.IOAHCIFamily 2.7.5
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.DiskImages 398
com.apple.iokit.IOStorageFamily 2.0
com.apple.iokit.IOBluetoothFamily 4.3.6f3
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.AppleACPIPlatform 3.1
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.Libm 1
com.apple.kec.corecrypto 1.0
Model: MacPro5,1, BootROM MP51.007F.B03, 6 processors, 6-Core Intel Xeon, 3.33 GHz, 24 GB, SMC 1.39f11
Graphics: NVIDIA GeForce GTX 980, NVIDIA GeForce GTX 980, PCIe, 4095 MB
Memory Module: DIMM 1, 8 GB, DDR3 ECC, 1333 MHz, 0x802C, 0x31384B53463147373250445A2D3147344531
Memory Module: DIMM 2, 8 GB, DDR3 ECC, 1333 MHz, 0x802C, 0x31384B53463147373250445A2D3147344531
Memory Module: DIMM 3, 8 GB, DDR3 ECC, 1333 MHz, 0x802C, 0x31384B53463147373250445A2D3147365031
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.24)
Bluetooth: Version 4.4.6f1 17910, 3 services, 19 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
Serial ATA Device: HL-DT-ST DVD-RW GH61N
Serial ATA Device: Samsung SSD 840 PRO Series, 512.11 GB
Serial ATA Device: Hitachi HDS723020BLA642, 2 TB
Serial ATA Device: ST31000524AS, 1 TB
USB Device: USB Bus
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: PTZ-631W
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: iPhone
USB Device: Apple Cinema HD Display
USB Device: USB 2.0 Bus
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: USB 3.0 Bus
USB Device: Multi-Reader
FireWire Device: built-in_hub, Up to 800 Mb/sec
Thunderbolt Bus:
---------------------------------------------
 
Finally have more time to test the "cover theory".

I managed to boot to cover (automatically). However, can't get the boot screen (without Mac EFI).

Also, when I boot to cover, I go to Options -> graphic injector, swtich on InjectATI, load video BIOS, etc. And then use "return" go back to the main menu.

However, once I restart the computer, those options back to the OFF position.

Anyone know what's wrong?

Also, select Bootcamp partition from cover will cause the the computer hang straight away. Shows black screen with a little white square in the centre (the square is same size as the Apple boot logo).

Choosing Windows as boot drive from system preference, or option boot to Windows, can boot to Windows (totally bypass cover).
 
Last edited:
I don't think you need to activate any of the options. On a real Mac, it should only need to serve as a GUI for you to select the OS of your choice. Once you've selected, the operating systems should load as normal.
 
I don't think you need to activate any of the options. On a real Mac, it should only need to serve as a GUI for you to select the OS of your choice. Once you've selected, the operating systems should load as normal.

With the stock options.

Cover only shows up when boot from the Mac EFI ROM (R9 280).

With PC VBIOS, only black screen. But I can sure cover is there, just nothing to display. Auto count down 5s to last boot drive works. Also, if I try to blindly navigate (disable the auto count down). I can shut down the Mac by short press power buttons.
 
With the stock options.

Cover only shows up when boot from the Mac EFI ROM (R9 280).

With PC VBIOS, only black screen. But I can sure cover is there, just nothing to display. Auto count down 5s to last boot drive works. Also, if I try to blindly navigate (disable the auto count down). I can shut down the Mac by short press power buttons.

Are you sure you installed Clover in Legacy Mode?

In Legacy Mode, you Mac should boot via the Bios Compatibility Layer or CSM. The CSM should load the vbios from you PC card, and you should get video on the Clover Boot screen.
 
Are you sure you installed Clover in Legacy Mode?

In Legacy Mode, you Mac should boot via the Bios Compatibility Layer or CSM. The CSM should load the vbios from you PC card, and you should get video on the Clover Boot screen.

I have absolutely no idea about this. Will need more time to study about that. Anyway, million thanks for your input. That's a very clear direction for me to go. Will report further once I can confirm that my installation is in Legacy mode.
 
I have absolutely no idea about this. Will need more time to study about that. Anyway, million thanks for your input. That's a very clear direction for me to go. Will report further once I can confirm that my installation is in Legacy mode.

Is the Disk you are installing Clover to a Hybrid GPT disk, i.e. did you install Windows via BootCamp on it?

I think, but can't confirm, that to install Clover in Legacy Mode you need to install boot0af or boot0ss, but I'm unclear as to installing to the ESP.

For me, on my Hackintoch, I have a Bios Motherboard, I use a MBR formatted USB stick with one HFS+ partition. I must choose Install boot0af to MBR and CloverEFI 64-bits BiosBlockIO.

The BiosBlockIO is only necessary for some Motherboards, likely not for the Mac Pro. I have chameleon installed my HD for booting 10.6.8 and 10.9.x. I had trouble with installing Clover to my HD, I never figured out the right combo.

I have a pure GPT disk, as I need more than 4 partitions.

Code:
/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS MacOS Sierra            338.5 GB   disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
   4:       Microsoft Basic Data                         90.8 GB    disk1s4
   5:         Microsoft Reserved                         133.2 MB   disk1s5
   6:                  Apple_HFS ELCAP                   15.7 GB    disk1s6
   7:                 Apple_Boot Recovery HD             650.0 MB   disk1s7
   8:                        EFI NO NAME                 104.9 MB   disk1s8
   9:                  Apple_HFS 10.6.8                  43.0 GB    disk1s9
  10:                        EFI NO NAME                 104.9 MB   disk1s10
  11:                 Apple_Boot Recovery HD             650.0 MB   disk1s11
  12:                  Apple_HFS Install OS X Yosemit... 9.2 GB     disk1s12
  13:                 Apple_Boot Recovery HD             650.0 MB   disk1s13
  14:                  Apple_HFS Mav                     389.6 GB   disk1s14
  15:           Linux Filesystem                         62.3 GB    disk1s15
  16:                 Linux Swap                         1.1 GB     disk1s16
  17:       Microsoft Basic Data Fat32                   37.6 GB    disk1s17
  18:                  Apple_HFS Snow Install            9.0 GB     disk1s18

I have multiple copies of OS X, and some OS X installers, Linux in EFI mode, and Windows 8.1 installed in EFI mode.

It's unclear to me, if you have Windows installed in BootCamp on a Hybrid GPT disk, if writing boot0af to the MBR with break your Windows install, Clover maybe able to boot it, or you may have to re-install Windows in EFI Mode, via Clover. It requires creating a USB install disk for Windows and copying a special boot file to it, the default boot file won't work.
 
Last edited:
Is the Disk you are installing Clover to a Hybrid GPT disk, i.e. did you install Windows via BootCamp on it?

I think, but can't confirm, that to install Clover in Legacy Mode you need to install boot0af or boot0ss, but I'm unclear as to installing to the ESP.

For me, on my Hackintoch, I have a Bios Motherboard, I use a MBR formatted USB stick with one HFS+ partition. I must choose Install boot0af to MBR and CloverEFI 64-bits BiosBlockIO.

The BiosBlockIO is only necessary for some Motherboards, likely not for the Mac Pro. I have chameleon installed my HD for booting 10.6.8 and 10.9.x. I had trouble with installing Clover to my HD, I never figured out the right combo.

I have a pure GPT disk, as I need more than 4 partitions.

Cover is installed on a HDD that with single HFS+ partition (not counting the EFI partition), MacOS 10.12.4 clone from my primary boot drive every morning (by CCC). No recovery partition on that particular HDD.

Never install Windows on this HDD. I tested it with the Windows SSD (SATA, connected in upper optical bay) connected or disconnected, same result.

The HDD should be pure GPT.

It the very first time I know something call boot0af and boot0ss. So, may be that's the problem.
 
boot0af:

Code:
Used for BIOS booting on BIOS motherboards.
boot0af (boot0 Active First) bootloader tries to boot the active partition defined in MBR. If there is no active partition, it will try to boot the first EFI/FAT32/HFS partition (defined in the MBR and then the GPT) with a valid PBR signature.
This choice will set the selected HFS/FAT32 partition status byte to active in the MBR.

boot0ss:

Code:
Used for BIOS booting on BIOS motherboards.
boot0ss (boot0 Signature Scanning) bootloader tries to boot the first EFI/FAT32/HFS partition (defined in the MBR and then the GPT) with a valid PBR signature. If no partition is found it will try to boot the active partition defined in MBR.
This bootloader is a good choice when you have Windows installed on the same disk because Windows wants to have its partition active.
This choice will NOT set the partition status byte to active in the MBR.

I would think you need the boot0af, but it's unclear to me if you pure GPT/GUID disk has any sort of Master Boot Record to write it too.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.