Clover UEFI Booting Windows using Mac OS Startup Disk PrefPane, possible?

See title, is this possible or did I make this feature up?

Some Background:
I am currently running Mac OS 10.8.5 on an SSD and Windows 7 (UEFI install) on a separate HDD using Clover as a boot loader (both systems run fine on their own). When I do not have the EmuVariableUEFI-64.efi driver installed, the Startup Disk PrefPane complains that the Windows drive is not 'blessed', but Clover is able to pick which OS to boot based upon which one was last used. When the driver is installed, selecting the Windows drive in the PrefPan doesn't give a bless error, but restarting results in automatically booting into Mac OS X (not the selected Windows drive). Additionally, with the driver installed Clover does not boot into Windows when it was last used.

My ultimate goal is to be able to boot into Mac OS X as default, yet be able to pick the Windows drive from the Startup Disk PrefPane as needed to avoid having to use a wired/USB keyboard during Clover drive selection.

Did you install RC scripts in Clover? Startup Disk works fine here to and from any drive or partition.

Yes, RC scripts are installed. Thank you for your feedback. I was afraid I was tilting at windmills for a minute. This is me:



And here is some of the boot.log output I think may be pertinent. I must have missed a step somewhere with the Loader?

1:463 0:000 GetEfiBootDeviceFromNvram:
1:463 0:000 efi-boot-device-data: MemoryMapped(0xB,0xFFE00000,0xFFEFFFFF)\FvFile(2B0585EB-D8B8-49A9-8B8C-E21B01AEF2B7)
1:463 0:000 BootCampHD: PciRoot(0x0)\Pci(0x1C,0x7)\Pci(0x0,0x0)\Sata(0x1,0x0,0x0)
1:463 0:000 Volume: 'PciRoot(0x0)\Pci(0x1C,0x7)\Pci(0x0,0x0)\Sata(0x1,0x0,0x0)'
1:463 0:000 LoaderPath: '<null string>'
1:463 0:000 volume: disk = PciRoot(0x0)\Pci(0x1C,0x7)\Pci(0x0,0x0)\Sata(0x1,0x0,0x0)
1:463 0:000 searching for that disk
1:463 0:000 not found
1:463 0:000 Searching for DefaultVolume 'Macintosh HD' ...
1:463 0:000 found entry 1. 'Boot Mac OS X from Macintosh HD', Volume 'Macintosh HD',

I installed OSX and Clover UEFI, included RCscripts and EmuVariableUefi-64. Verified nvram was being written and updated. Then installed Windows 8.1 EFI to a second drive. Set OSX as boot drive, it was as easy as that...

My log looks like this:

1:013 0:006 GetEfiBootDeviceFromNvram:
1:014 0:000 efi-boot-device-data: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A5B3BD62-8FF5-4D11-8661-8338028DED80,0x64028,0x1DB59340)
1:014 0:000 Volume: 'PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A5B3BD62-8FF5-4D11-8661-8338028DED80,0x64028,0x1DB59340)'
1:014 0:000 LoaderPath: '<null string>'
1:014 0:000 Guid = A5B3BD62-8FF5-4D11-8661-8338028DED80
1:014 0:000 volume: partition = PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A5B3BD62-8FF5-4D11-8661-8338028DED80,0x64028,0x1DB59340)
1:014 0:000 searching for that partition
1:014 0:000 found entry 0. 'Boot Mac OS X from Yosemite', Volume 'Yosemite'
1:014 0:000 Boot redirected to Entry 0. 'Boot Mac OS X from Yosemite'

Luck with this... I'm sure you'll get it working.

Although I installed RC script and EmuVariableUefi-64, there's only OSX disk in the 'Startup Disk'.
I'm running Mac OS on a fusion drive(SSD+HDD) and W7 on a separate HDD.

How can I make the hard disk(W7) appear on Startup Disk?

Hi,

I have a similar issue as the OP where when selecting the boot disk in the startup disk pane or Paragon NTFS for Mac preference pane (if the NTFS driver is set as active, this preference pane shows windows disks, if deactivated, they show in startup disk preference pane. (@tazjhc: could this be your problem? - you have an NTFS driver installed? - I've read elsewhere that others, not just Paragon's, do similar things)

While the below is copied from post 3 above (sorry all, writing on my iPad as rig is off), i get very similar info:

1:463 0:000 GetEfiBootDeviceFromNvram:
1:463 0:000 efi-boot-device-data: MemoryMapped(0xB,0xFFE00000,0xFFEFFFFF)\FvFile(2B0585EB-D8B8-49A9-8B8C-E21B01AEF2B7)
1:463 0:000 BootCampHD: PciRoot(0x0)\Pci(0x1C,0x7)\Pci(0x0,0x0)\Sata(0x1,0x0,0x0)
1:463 0:000 Volume: 'PciRoot(0x0)\Pci(0x1C,0x7)\Pci(0x0,0x0)\Sata(0x1,0x0,0x0)'
1:463 0:000 LoaderPath: '<null string>'
1:463 0:000 volume: disk = PciRoot(0x0)\Pci(0x1C,0x7)\Pci(0x0,0x0)\Sata(0x1,0x0,0x0)
1:463 0:000 searching for that disk
1:463 0:000 not found
1:463 0:000 Searching for DefaultVolume 'Macintosh HD' ...
1:463 0:000 found entry 1. 'Boot Mac OS X from Macintosh HD', Volume 'Macintosh HD',

Although I have highlighted a different section that I believe to be the problem.

@Foxtrot: How did you install Clover? With my P8P67 Deluxe rig, I had to install Boot0af to the MBR (True UEFI doesn't work) and the Bootloader was BIOS IO for access to drive as supposed to SATA access to drives, otherwise when booting to windows via Clover I lost access to drives on the Marvell SATA ports until I uninstalled and reinstalled the driver and that didn't persist through reboot, so it was every time(bit of a pain!).

Clover is build is 2758. Windows is 7 Ultimate 64 Bit installed UEFI. OS X is Mavericks 10.9.4

I've tried with and without the following Clover drivers installed:

EmuVariableUEFI.efi
NTFS.efi

My thought is we need to map drive PciRoot(0x0)\Pci(0x1C,0x7)\Pci(0x0,0x0)\Sata(0x1,0x0,0x0) to the bootloader path for windows EFI, but not sure how to do that in Clover at this time.

Parallel

Hello Parallel,

I'm wondering if PciRoot(0x0)\Pci(0x1C,0x7)\Pci(0x0,0x0)\Sata(0x1,0 x0,0x0) is simply generic for 'I have no idea where that drive is' when you set it in the pref pane.

As of this writing, I have completely re-installed Mac OS (Mavericks) using clover, in addition to installing Windows 8 on a separate drive (operating in UEFI only mode on mobo). The same behavior as described previously still persists.

Clover build is 2747 here.

I'm unclear on one point of your post; is Windows 7 on a separate hard drive?

EDIT: This may be what we're dealing with...
http://www.projectosx.com/forum/index.php?s=&showtopic=2562&view=findpost&p=21735

The major obstacles which may cause this thing not fully working are:
- when Win option is selected in Startup Disk, then OSX passes only pointer (device path) to the disk where Win is, and not to the partition - it's possible that Clover is not able to detect correct partition in some cases
- some differences between device paths generated from OSX and from UEFI/CloverEFI

Click to expand...

Hi Foxtrot,

To confirm, yes, Windows is on a separate disk. I will say as well that when booting windows, the next boot is into OS X unless I manually change it too which seems to agree with the post you linked to.

I am wondering if my issue stems from having a couple of windows boot managers (I installed windows once on a spare disk in UEFI mode to see if I could, but when I went to install it on the correct disk afterwards (despite having deleted original install I might add!) I kept getting errors until I unplugged all other disks in my system so I literally only had the one I wanted to use connected.

After having plugged the other drives back in, it still works, but I have two listings for windows boot manager in BIOS/UEFI setup!!!

I'm off to check all my EFI partitions to see if I can find a duplicate......

Something interesting that may be relevant:

I let the windows install disk partition the disk, generating the EFI, MSR and primary partitions for the GPT disk.

The EFI partition on the windows 7 disk is 100MB.

If you use OS X's disk utility to "verify" the disk it complains the EFI partition is too small - which matches with the fact that any GPT disks created by OS X have an EFI Partition of 200MB

Could this be the reason that the partition isn't correctly identified when using the startup pane?

@Foxtrot, if you're not too far along with your re-installation, could you manually partition your windows 7 disk with a 200MB EFI partition?

OR

Could someone with the startup disk pane working (which appears to be windows 8 users) check the size of the relevant EFI and report back?

EDIT: Just re-read Foxtrot's last post. I read the re-install and saw windows and assumed things. I see now that he installed windows 8 this time and has the same problem still. Although, EFI partition size????