- Joined
- Jan 19, 2013
- Messages
- 16
- Motherboard
- Gigabyte > Need full model name > See Forum Rules!
- CPU
- i7 > Need full CPU model number > See Forum Rules!
- Graphics
- ATI > Need full model name > See Forum Rules!
- Mac
- Classic Mac
- Mobile Phone
RehabMan suggested:
Apparently this helped paulkol. But not clear which of the suggestions were the key enabler(s) ?
I tweaked my EFI as well now per above as best possible and will see tomorrow night if I get past my stuck i7-7700K ++++++++ boot.
Try with:
OsxAptioFixDrv-64.efi instead of OsxAptioFix2Drv-64.efi.
KernelCpu should be false
CsrActiveConfig should be 0x67
GenericUSBXHCI.kext has no applicability to your hardware.
You are double injecting due to dup kexts in 10.12 and Other. Place all kexts in Other. Remove 10.12.
Only place essential kexts in kexts/Other (eg. no need for more than one Ethernet kext)
Disable all KextsToPatch (you don't need NVMe, audio, etc to boot the installer... you can re-enable NVMe or use HackrNVMe spoofed later)
fyi: Skylake AppleAPIC patch is a mistake (current macOS/OS X does not need it... it causes problems, not solves them)
config.plist/SMBIOS/Trust should be true (you have false)
If you're specifying memory details with SMBIOS/Memory, make sure they are accurate.
Eliminate unneeded *.efi from drivers64UEFI (leave only DataHubDxe-64.efi, EmuVariableUefi-64.efi, FSInject-64.efi, OsxAptioFixDrv-64.efi, VboxHfs-64.efi)
You could try HFSPlus.efi instead of VboxHfs-64.efi.
Check BIOS settings!
Try also with cpus=1
Apparently this helped paulkol. But not clear which of the suggestions were the key enabler(s) ?
I tweaked my EFI as well now per above as best possible and will see tomorrow night if I get past my stuck i7-7700K ++++++++ boot.