Yes, it's confusing. Are you sure you are using UEFI boot? You should get boot.log at the root of OSX volume. Does it say:
Starting rEFIt rev 980 on American Megatrends EFI
Starting rEFIt rev 980 on CLOVER EFI
or something similar?
And the second thing - are you using some other nvram store/restore system from before? If I remember correctly, DHP/RevoGirl had some system for this previously.
And ... which board are you using?
I'm totally sure I'm using UEFI boot. In fact, that is the only boot method I've tried and the reason for choosing Clover as boot loader. I think CLover UEFI boot is the most aproach to apple stuff. The bad thing is that my system is a Dell optiplex 390 desktop. This board has given me many problems (ATA, graphics, etc.) but finally, after hard read and read, is running
So, I've been doing some researches and that's is what I found:
- boot.log shows following messages: (removed messages no import ants)
... 0:101 0:000 Starting rEFIt rev 980 on American Megatrends EFI ... 139 0:000 Clover revision: 980 running on OptiPlex 390 0:139 0:000 ... with board 0M5DCD 0:152 0:012 Using OEM config.plist at path: EFI\config.plist 0:152 0:000 Loading early settings 0:152 0:000 LoadDrivers() start 0:161 0:008 Starting HFSPlus.efi 0:173 0:012 Using load options 'HFSPlus.efi ' 0:173 0:000 - driver needs connecting 0:173 0:000 Starting FSInject-64.efi 0:186 0:012 Using load options 'FSInject-64.efi ' 0:186 0:000 Starting CsmVideoDxe-64.efi 0:198 0:012 Using load options 'CsmVideoDxe-64.efi ' 0:198 0:000 - driver needs connecting 0:198 0:000 Starting OsxAptioFixDrv-64.efi 0:207 0:008 Using load options 'OsxAptioFixDrv-64.efi ' 0:207 0:000 Starting OsxFatBinaryDrv-64.efi 0:219 0:012 Using load options 'OsxFatBinaryDrv-64.efi ' 0:219 0:000 2 drivers needs connecting ... 0:219 0:000 PlatformDriverOverrideProtocol not found. Installing ... Success 0:219 0:000 Edid: size=128 ... 3:380 0:000 FindStartupDiskVolume ... 3:380 0:000 GetEfiBootDeviceFromNvram: 3:383 0:002 efi-boot-device-data: Acpi(PNP0A03,0)/Pci(1F|2)/Ata(Primary,Master)/HD(Part2,Sig83BD7E68-885D-4C37-BE2A-D71A1D63886E) 3:383 0:000 Volume: 'Acpi(PNP0A03,0)/Pci(1F|2)/Ata(Primary,Master)/HD(Part2,Sig83BD7E68-885D-4C37-BE2A-D71A1D63886E)' 3:383 0:000 LoaderPath: '' 3:383 0:000 Guid = 83BD7E68-885D-4C37-BE2A-D71A1D63886E 3:383 0:000 FindStartupDiskVolume searching ... ...
Last part, makes me think that "efi-boot-device-data" exists in NVRAM. Then, why "nvram -p" does not show me it?
Other message I don't know if I have to care about is "PlatformDriverOverrideProtocol not found. Installing ... Success" and don't know if it is related to next finding.
- I've tried to get my system-id to check if the lasts bytes match with my en0 MAC address.
As you explains here, I've set InjectSystemID=Yes and no CustomUUID, so my system-id must be located into IODeviceTree:/efi/platform/system-id... but it does not:
Davids-iMac:~ David$ ioreg -p IODeviceTree +-o Root +-o / +-o chosen | +-o memory-map +-o efi | +-o kernel-compatibility | +-o runtime-services | +-o configuration-table | | +-o EB9D2D31-2D88-11D3-9A16-xxxxxxxxxxxx | | +-o 8868E871-E4F1-11D3-BC22-xxxxxxxxxxxx | | +-o 49152E77-1ADA-4764-B7A2-xxxxxxxxxxxx | | +-o 4C19049F-4137-4DD3-9C10-xxxxxxxxxxxx | | +-o 7739F24C-93D7-11D4-9A3A-xxxxxxxxxxxx | | +-o 05AD34BA-6F02-4214-952E-xxxxxxxxxxxx | +-o platform +-o cpus
(none of the UUID endings match my ethernet mac address and I don't know if my system-id must be one of them)
At this point, it seems like something goes wrong with my NVRAM variables/efi injection. What do you think?
If you need some more info/logs/tests from me, feel free to ask. Thank you!