Hervé

How about booting in verbose mode and posting a (reasonably-sized) picture of the crash/KP?

Search the forum for "boot0" or "4K" sector issue. There are several threads/posts and they provide the procedure you need to follow to fix the issue. It's a little well-knwon bug of Chameleon.

Why don't you use the existing packs provided in the guides for this model?

Consider that this requires 3 major phases: 1) copying of all necessary OS X installation package files 2) installation of the Clover bootloader 3) the fine-tuning for your target Hackintosh (Clover fine-tuning, copying of hardware-related kexts/drivers, patched ACPI/BIOS tables, etc.) Phase 1) is largely documented in the numerous guides available on this forum. You can look them up in the "Guides" section Phase 2) is pretty much straight forward, you simply install the Clover app Phase 3) is the more tricky one that requires a bit of research

Indeed, it's mentioned in the various guides on the forum.

The usual IDT patch simply applies https://osxlatitude.com/index.php?/topic/7914-dell-latitude-e6220-with-i5-2520m-hd3000-and-1366x768-lcd-mavericksyosemiteel-capitan/ You can simply apply the Vietnam tool patch to get audio going. It's listed for the E6x20.

Following up on the Yosemite/El Capitan/Recovery logos, I made up new Sierra logos/icons for the Chameleon/Enoch bootloader so that Sierra partitions can too enjoy their own icons. Fits nicely along all the other icons. Attached .png files are to be placed in the /Extra/Themes/Default folder. Sierra_themes_logos.zip

Apple presented its new version of Mac computers OS yesterday: macOS 10.12, called Sierra. DB1 version (16A201w) was made available to developers after the WWDC. Note that Sierra requires SSE4.1-capable CPUs so Penryn C2D CPUs -in which the instruction set was introduced- are the oldest that will do (eg: mobile T8xxx, T9xxx) but not older Merom models just won't (eg: mobile T7xxx). CPU upgrade may therefore be required for older C"D systems. Enoch boot loader was updated for Sierra by Micky1979 thereafter. I attempted installation on my E6230 using the classic manual procedure. Apart from VoodooPS2Controller-related KP (same sort of issue as previously encountered from El Capitan 10.11.4, different kext required), all went well and smooth. From this onset, most people can therefore expect an easy-enough future installation on their Hackintosh(es). Let's see how this develops over the next few months until official launch of Sierra in the autumn. It's the 1st DB version so it naturally has bugs and may not support all hardware components. Bluetooth support appears problematic for instance. As stated at WWDC, Sierra only supports Mac models from late 2009, not before. As such, expect messages such as "macOS Sierra cannot be installed on this computer" if you use the SMBIOS of an unsupported/older Mac model. For instance, Sierra will not install on a D630 nVidia when using the usual MBP5,1 SMBIOS; that's late 2008... Sierra will however install with a supported SMBIOS such as MBP7,1 and the required associated adjustments (eg: USB injector kext mods). Upon macOS installation, there's no initial graphics acceleration but the original MBP5,1 SMBIOS can be safely re-instated and everything then works as before. macOS Sierra brings some behaviour change at the moment. For instance, some kexts such as VoodooHDA + AppleHDADisabler no longer load from /L/E, only from /S/L/E. They won't even inject at startup from /E/E with boot option KernelBooter_kexts=Yes. Also met success on the SandyBridge/HD3000 E6220 but I have to report that graphics can appear a little buggy at times (screen artefacts/blurred text/etc.). And same on Haswell/HD4600 E6440, though booting the USB installer was difficult and I had to change ports several times until it booted.

Ha, now you mention Optimus and a discrete GPU ! It could very well be that your DP port is wired to the nVidia GPU. This being said, if you would be kind enough to detail your FB binmod, we may progress. You did mention setting your connector type to 00 04 00 00, but which port did you use?

Try and rebuild your cache to start with.

A newer version v1.3.6 of that kext has been available for a few months...

As listed at the very bottom of your forum page... http://www.osxlatitude.com/tuning-performance-with-fakesmc-smbios-plist/

What kind of SSD do you have? I experienced this behaviour with an Intel SSD model once Trim was enabled. Ok without.

Well, I initially also used the MBA6,2 for my Haswell-based E6440, then changed that to MBP11,1 as that gave me one extra intermediate CPU multiplier. Try and tune your FakeSMC kext too, that may modify iGPU behaviour. You never know and no harm to try...

OS X is generally more graphics demanding than Win7, so it's perfectly normal to me that battery life is shorter under OS X than it is with Windows. Depending on SMBIOS profile and FakeSMC tuning, you may optimise CPU speed stepping and possibly gain a little battery life. I take it you're using a CPU-specific SSDT to handle good CPU power management. You may also want to turn off accessories such as Bluetooth if you're not using them.

If your (mini) DP port is not working, you have no other solution than find out the correct FB adjustments to get it working. Once you've found out the correct settings, it'll be "rock solid" across the board. The HD4000 thread provides all the necessary info to get you going. You will not get a generic/standard solution that fits all machines if that's what you're after. You'll have to experiment; that's Hackintoshing I'm afraid... To give you an idea, you may find inspiration in this thread (look at posts #5 to #8). It's for SB HD3000 outputs, but the principles remain exactly the same for HD4000 outputs.

You may check the dedicated thread on HDMI/VGA output on HD4000 in the R&D section. It details the various binary patches to consider.

Are you sure you've got full graphics acceleration? One sure way to know, if you have a CD/DVD drive is to launch DVDPlayer app then check the Supported Features in Help menu. All should be supported. For AppStore, make sure you've installed the Ethernet kext and that your LAN card is detected as en0; if en1, remove all interfaces from your Network PrefPane, then all plist files from /Library/Preferences/SystemConfiguration and reboot.

When you get this error 77, redo the last commands (touch + kextcache). Failing that, opt for: sudo kextcache system-prelinked-kernel

Hmm, it's as if your graphics are not initialising. Check that you have the DSDT in its expected place and that it contains the appropriate SNB layout-id. Make sure to boot with: Enoch flags & parameters KernelBooter_kexts=Yes -f -v Extra folder copied to your USB installer Patched AICPUPM kext in place (/S/L/E) or NullCPUPM kext in /E/E

Boot in verbose mode (-v flag) to try and grab where the boot process hangs. But if you have same hardware + same BIOS version + same BIOS settings, I'm failing to think of anything specific.

Afaik, you only patch the Capri FB in order to gain specific video output(s) such as HDMI and/or VGA for instance. I think this was mentionned in previous posts. HD4000, like HD3000 before it, has no built-in dedicated VRAM; as such, for memory, these iGPU use computer's RAM.

Check that your HDD mode is set to AHCI in the BIOS settings. OS X does not usually support modes such as RAID. One other thing you may try when you obtain the "waiting for root device" is unplug then replug your USB installer key.

You need the patched AppleHDA kext in /S/L/E + the codec specific AppleHDAxxxx kext in /L/E. If you have Clover, you can simply add the on-the-fly AppleHDA patch to your config plist.

I could not say whether your friend's statement re: VGA control is true or not, but VGA output off IvyBridge iGPU is not usually supported OOB under OS X and requires FrameBuffer patching. Since you run on your integratedHD4000, I would expect you need the VGA patch applied to your Capri FrameBuffer. You'll find details of the patch here. Identify your active HD4000 layout-id (0x0166xxxx), then experiment with the described VGA patching possibilities until you hopefully find the value that works. Keep a backup of the vanilla Capri FB of course!