That´s true. I think most of the troubles here are related to the BIOS eventhough everyone is using the same version from the first thread.
In the attachement you can find my "Minimal EFI folders" to boot into the Install USB and into already installed system.
In BIOS used the settings from the first post and disabled OPROM (legacy boot) in order to boot the installer. Now, weirdly enough it works even when OPROM enabled.
However things seems a bit random in here. Some folks can´t boot with adapter connected and I can only boot with it. Sometimes I even had to connect USB mouse in order to boot from USB.
Now even after all the patching my EFI boot seems still rather unstable. I can still boot only with the adapter connected and I have like 50% chance to boot anyway. Sometimes Clover loads the theme and sometimes it doesn´t which is not correlated with ability to boot properly at all. As I said: random
Thanks - I needed that too.. If I define Clover.efi as the only way to boot in BIOS it sometimes reverses back (why??) and I have to boot with F12 into UEFI Clover partition again and then get my 50% chance with adapter connected or 0% without
Yeah - I needed to this too. It´s incorrect in the first post.
Sometimes even the smallest details matter. For example, which USB port you're using, and what kind of USB stick (USB3 vs. USB2). This is why someone who gets it to work should document the procedures down to the smallest detail.
As for BIOS settings, post #1 doesn't even mention if BIOS settings should be set to default before applying the changes mentioned. So, at this point saying "used the settings from the first post" is undefined. No way to know whether the changes mentioned in post #1 are a delta from the way the laptop ships (which may change over time), from defaults, or from the way it just happened to be set for the individual that wrote post #1. This is why setting BIOS to a known state (default), then making the minimal changes required, and documenting them... is important.
And good stability should not be expected unless you have completely patched ACPI, implemented power management, etc. And even still... Skylake is new and there are no Macs that use Skylake graphics... so even then it may not be stable.
And "can't boot" always needs clarification. Can't boot Clover? Can't boot OS X? Verbose result? KP? BIOS won't POST?
Working together and communicating with details will help individual results benefit the group.
Comments on EFI(Boot into installer).zip:
- FakePCIID_Broadcom_WiFi.kext does nothing by itself (so including it by itself serves no purpose).
- FakeSMC.kext is old
- it is likely some sort of PS2 kext would be needed unless you plan on using a USB keyboard/mouse
- OsxAptioFixDrv-64.efi may be more (or less) reliable than OsxAptioFix2Drv-64.efi
- EmuVariableUefi-64.efi is not needed for installation
- just FYI: config.plist looks exactly like the guide config.plist except 0x191b0000.
- UHD models would need config.plist/Devices/FakeID/IntelGFX=0x012345678
Comments on EFI(Boot after installed)
- FakeSMC.kext is old
- RealtekRTL8111.kext is missing (would be required if you want internet access before kexts are installed)
- if FakePCIID_BroadCom_WiFi.kext was there, you could use WiFi too (since FakePCIID.kext is there)
Otherwise they are identical.
And of course neither has any ACPI work, so you should not expect the system to be stable. Just as an example, typically mobile Skylake AppleLPC is not supported and requires ACPI patching (or other ways) to make it load. It is an important one...
