Hervé

You can look at my research on the matter in the R&D->Graphics section. It was done for my Haswell laptop but the principles remain the same. You need to identify your DP port through an IOReg browser (IORegistryExplorer, IOJones), then experiment with binary modifications of your relevant layout-id section in the BDW framebuffer.

For the HDMI audio patch, all that's required is to modify the HDMI output connector-type from its default value of 00 04 00 00 to 00 08 00 00. This patch is applicable to all systems whatever the frameBuffer (SNB, Capri, Azul, BDW, etc.) and for all versions of OS X. So, you need to identify the HDMI port line in your particular layout-id of the Broadwell framebuffer (kext BDW FB) and then apply the binary patch; this can be done "on-the-fly" through Clover or through direct binmod of the FB binary file itself.

HDMI audio is handled through AppleHDA (patched for your own codec) + Intel framebuffer (patched BDW FB in your case).

By 2016, everyone who's done a minimum research should know that no Intel wireless card is supported under OS X. It's even mentioned in the FAQ section: https://osxlatitude.com/index.php?/topic/8696-is-my-wireless-card-compatible-with-os-x/ Please use the forum Search facility before posting.

A change to the SMBIOS profile may help, like a little jiggle of the production week n° or year to generate a different serial n°. Assuming the SMBIOS chosen model is right...

The only 10.11.3 you could download would be the Combo update. And that would only install on an earlier 10.11-10.11.2 build. Apple only provides the latest version for installation package download. Oh and, no, 10.11.3 would not work better than 10.11.4+ on that system. Maybe you should make a new installation...

Does it boot if you limit your CPU to 1 core (eg: option cpus=1 in Chameleon/Enoch)?

Means the cache was not rebuilt. Re-type the last 2 commands or use the following alternative command for kextcache: sudo kextcache system-prelinked-kernel

Updated with 10.11.6 files.

Is your Ethernet interface set to en0? That's mandatory.

Looking ok. But if you keep getting "wrong password", then you're not entering the right one...

FaceTime, like AppStore, should only require Ethernet to be up & running as en0. The other stuff is for iMessage.

Yes, you need to copy the EFI folder to the EFI partition. You can mount it with Clover Configurator.

Reset your BIOS to factory settings, then set AHCI on and disable Optimus.

Please read the guide before asking questions answered there...

Correct.

Hmm, I've made additional tests and, since my dGPU appears turned off at boot time, I tried to turn it on through SSDT or DSDT edits. I've not managed to reach success yet. However, this reminded me that, many moons ago, I had noticed that HWMonitor never displayed any info about GPU at startup, only after wake. Basically, I would get this: At startup and until sleep After wake Now, if you look at the DSDT code for the _WAK method, you'll notice the following section: If (LOr (LEqual (Arg0, 0x03), LEqual (Arg0, 0x04))) { If (CondRefOf (\_SB.PCI0.PEG0.PEGP.EPON)) { \_SB.PCI0.PEG0.PEGP.EPON () } If (CondRefOf (\_SB.PCI0.RP05.PEGP.EPON)) { \_SB.PCI0.RP05.PEGP.EPON () } } ` To me this code is partially erroneous in the sense that there is no PEGP device under RP05 in any ACPI table, however the discrete GPU is definitely handled by PEGP under PEG0. Check what you get in HWMonitor at startup. If no GPU info appears, I believe your dGPU is off. If it appears, we'll have to find the right code to turn it off. If, like me, your dGPU appears turned on only after wake, apply the following DSDT patch: edit the SSDT table where method EPON is defined and create a new EPOF method (it did not exist in my SSDT-xx table). EPON method only sets ONOF parameter to 1 (true) so you can simply copy/paste the EPON code in a new EPOF method where you set ONOF parameter to 0 (false). in the above DSDT _WAK code, you can then replace the call to EPON by a call to EPOF instead. In the relevant SSDT table, you may notice that the ONOF parameter is used in SGON and SGOF methods that turn the dGPU on or off. although it would appear like the obvious thing to do, removing the above _WAK code is simply ineffective. In a nutshell: in your relevant SSDT-xx table, add this after EPON method: Method (EPOF, 0, Serialized) { Store (Zero, ONOF) Return (Zero) } in your DSDT, change the _WAK code to: If (LOr (LEqual (Arg0, 0x03), LEqual (Arg0, 0x04))) { If (CondRefOf (\_SB.PCI0.PEG0.PEGP.EPOF)) // Replace EPON by EPOF { \_SB.PCI0.PEG0.PEGP.EPOF () // Call to EPOF to turn off dGPU } // Comment out or remove those useless 4 lines below // ------------------------------------------------- // If (CondRefOf (\_SB.PCI0.RP05.PEGP.EPON)) // { // \_SB.PCI0.RP05.PEGP.EPON () // } } // <----- Don't remove or comment out that closing bracket! ` I think that should sort you out if dGPU is indeed turned off at startup and only activated after wake. Meantime, I'll keep trying to find the right code to really turn on or off the dGPU at system startup.

Where is your ApplePS2Controller kext? If in /L/E, make sure you repaired the permissions of that folder and rebuilt the cache. I've no issue with the kexts of the pack I published and my D630 runs 10.11.6 without any mods to kexts. If you get an error message at the end of cache rebuild process, just repeat the last 2 commands (touch + kextcache).

This Mavericks guide has the full pack for the E6430 with nVidia NVS 5200M. It also mentions disabling/re-enabling Optimus in BIOS. Additional info here too. The El Capitan installation process is detailed here.

Follow Jake's guide, it's more up to date than Pokenguyen's which was initially for Mavericks..

Audio will only work once you've patched the AppleHDA kext. Is it ALC3226 (ALC292) like on the E6x40? If so, I can give you patched kexts or, if you use Clover, apply the patch command you'll find in the packs posted by Jake in his El Capitan Clover guide for the Latitude / Inspiron laptops. Use Clover Configurator tool to examine Jake's posted config.plist for Clover. FaceTime/iMessage/AppStore require the Ethernet card to be activated and configured as 1st network interface en0. Check that out in Network PrefPane or through Terminal app with ifconfig command. I reckon the LAN card is the same in the E7x40 series as in the E6x40 but, again, Jake's guide offers packs will all the necessary drivers. Sleep should work OOB once you've got CPU power management fully working and eventual DSDT patches.

Your pictures shows a KP on AICPUPM so you need to use NullCPUPowerManagement kext until you activate the AsusAICPUPM patch in Clover config or patch the vanilla AICPUPM kext. If you want to use the nVidia GPU, you 1st need to enable Optimus in BIOS. Then I reckon you'd have to remove the Intel Capri kexts so that OS X makes no attempt to load drivers for the integrated HD4000 graphics. All should be indicated in Jake's guide.

Arf, I forgot one stupid thing! Assuming you already have a file SSDT.aml (for CPU power management settings), the revised SSDT table needs to be renamed SSDT-1.aml for it to be loaded by the bootloader. At least, that's how it works with Chameleon/Enoch: tables are read in the order SSDT / SSDT-1 / SSDT-2 / SSDT-3, etc. I've verified this in verbose mode. If keeping original SSDT-n.aml name (like SSDT-8.aml or SSDT-9.aml): E6440:~ admin$ bdmesg Enoch (2839) ... ... ... [ ACPI PATCHER ] Table /Extra/DSDT.aml read and stored at: 2f57000 ... Table /Extra/SSDT.aml read and stored at: 2f69000 ACPI Table not found: SSDT-1.aml ... DSDT: Old @c8fd31b0,50304943, New @2f57000,50304943 ... TABLE APIC, TABLE FPDT, TABLE LPIT, TABLE SSDT, OEM SSDT tables was dropped TABLE SSDT, OEM SSDT tables was dropped TABLE SSDT, OEM SSDT tables was dropped TABLE SSDT, OEM SSDT tables was dropped TABLE HPET, TABLE SSDT, OEM SSDT tables was dropped TABLE MCFG, TABLE SSDT, OEM SSDT tables was dropped TABLE ASF!, TABLE SSDT, OEM SSDT tables was dropped RSDT: Added 1 SSDT table(s) RSDT: Original checksum 180, New checksum 62 at 2f6c000 ... Added 1 SSDT table(s) into XSDT ... ACPI version 2 patching finished If renaming the revised table to SSDT-1.aml: E6440:~ admin$ bdmesg Enoch (2839) ... ... ... [ ACPI PATCHER ] Table /Extra/DSDT.aml read and stored at: 2f57000 ... Table /Extra/SSDT.aml read and stored at: 2f69000 Table /Extra/SSDT-1.aml read and stored at: 2f6a000 ACPI Table not found: SSDT-2.aml ... DSDT: Old @c8fd31b0,33373330, New @2f57000,33373330 ... TABLE APIC, TABLE FPDT, TABLE LPIT, TABLE SSDT, OEM SSDT tables was dropped TABLE SSDT, OEM SSDT tables was dropped TABLE SSDT, OEM SSDT tables was dropped TABLE SSDT, OEM SSDT tables was dropped TABLE HPET, TABLE SSDT, OEM SSDT tables was dropped TABLE MCFG, TABLE SSDT, OEM SSDT tables was dropped TABLE ASF!, TABLE SSDT, OEM SSDT tables was dropped RSDT: Added 2 SSDT table(s) RSDT: Original checksum 180, New checksum 130 at 2f6e000 ... Added 2 SSDT table(s) into XSDT ... ACPI version 2 patching finished

You can swap OPT and CMD keys through your keyboard PrefPane. It's as simple as that. For Sierra, it's a general issue affecting all systems, not just the E6430 or Dell laptops. It's obviously the result of changes by Apple but Sierra still is in Beta version... There are plenty of posts on keyboard mappings and tuning, please refer to them.

Support capability for OS X simply depends on the specs but I gather that the new V5 version is not based on the same hardware generation as the V2 which was Haswell-based. But I really much doubt that the OP really obtained "dual graphics with acceleration" as he'd be the 1st in the world to have achieved it. He got either or. For OS X installation, refer to existing guides, they all follow the same process, only drivers linked to specific hardware will differ; and ACPI (BIOS) tables of course! Post the hardware specs and you'll get a better answer. As for the battery duration under OS X, well... how long is a piece of string?