Hervé

Do you actually have full graphics acceleration? Or doesn't Skylake graphics require layout-id injection?

You may also check that: 1) USB wake is disabled in BIOS 2) no wake on network access in your Power Savings Pref Pane But most importantly, ensure you have a driver package compatible with OS X El Capitan. Realtek's web site does not list much drivers beyond OS X Mountain Lion 10.8 for 802.11a/b/g/n single-chip devices, so check the dongle's manufacturer's web site. The best solution is to opt for a compatible mini-PCIe or 1/2 mini-PCIe card as suggested by Jake. DW1510 or DW1550 are indeed great hi-speed 802.11n cards. https://osxlatitude.com/index.php?/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/

ALC3246 indeed according to Dell's 3470 specs. Should be ven/dev ids 10ec:0256, i.e. ALC256 codec. For El Capitan, try the following Clover on-the-fly AppleHDA patches + attached kexts: Find: 6102EC10 Replace by: 00000000 Find: 6202EC10 Replace by: 00000000 Find: 8508EC10 Replace by: 00000000 Find: 8319D411 Replace by: 00000000 Find: 8419D411 Replace by: 5602EC10 AppleHDA_ALC256.kext.zip CodecCommander.kext.zip Patch your DSDT HDEF device to inject audio layout 3.

Pike R Alpha's generator script creates a CPU-specific SSDT file to obtain ful native CPU power management and Turbo boost. If you've not done that critical part yet, you've got no proper CPU power management. Hence my questions of August 27th. Furthermore, you may still be using NullCPUPM, in which case, you definitely have no CPU power management at all and that usually prevents Sleep. So, make sure you've: set your SMBIOS profile to MBA5,1 or MBP9,2 generated your CPU-specific SSDT removed NullCPUPowerManagement kext Proceed in that order as the SSDT generator script looks at SMBIOS profile...

You should stick to patching the Yosemite vanilla AppleHDA. I'd never use kexts of a version n+1 on a version n; it's usually the opposite... If using Clover, apply the on-the-fly patch alongside the complementary IDT audio kext which can be placed in /L/E (or /S/L/E) followed by usual permissions repair + cache rebuild. You may also inject it through the EFI/Clover/kexts/10.10 folder but that's obviously not cached and therefore slower. The Latitude E5430 is using same IDT 92HD93 codec as the E6x30 series. As such, you can use the following on-the-fly patch in Clover, alongside the attached IDT kext: Find: 8B19D411 Replace by: 00000000 Find: 8419D411 Replace by: DF761D11 There are 2 x occurences of each binary replacement if you ever wanted to do it manually in the actual vanilla AppleHDA kext binary file. AppleHDA_IDT_92HD93.kext.zip And, if required: Vanilla_AppleHDA_10.10.5.kext.zip The exact same on-the-fly/binary patch and IDT kext are re-usable with EC 10.11 and Sierra 10.12.

Where are you at? You simply copy the Extra folder to the root of your OS X partition...

You need to activate KernelPm in Clover CPU options. CPU power management is managed at kernel level for Haswell CPUs and this requires a patch on Hackintoshes.

With 14years of experience (knowing that hackintoshing began 10years ago when Apple switched to Intel), you should have no problem installing OS X on this Asus and identifying the obvious.

Please make the effort to read the threads I linked above.

Audio codec of E6x30 is IDT 92HD93 (Codec 76DF). It's shown in BIOS info if you want to check.

Try and reset BIOS to default settings, then set HDD mode to AHCI and BIOS mode to Legacy.

For info, the "regular" (if I may call it this way) AppleHDA for E6230 consists of: injection of layout 12 in DSDT loading of IDT codec definition kext (xml.zlib files) binary patching of AppleHDA kext to inject IDT codec id 76DF: find 8B19D411 and replace by 00000000 find 8419D411 and replace by DF761D11

You should asked Wern what his patch consists of... There are mixed reports about his patches.

The best method is based on the Terminal commands. Why? Because, sometimes (often?), cache rebuild fails and returns error messages. You cannot see those outside Terminal mode.

Ouh… lots to cover! Bootloader and kexts: Are you using Enoch or Clover? With Enoch, add-on kexts should go to /L/E/, followed by permissions repair + cache rebuild. That's the preferred folder for best ideal performance and efficiency. Kexts placed in /E/E will be injected at boot time if and only if Enoch boot option KernelBooter_kexts=Yes is used. Clover works in a simile way where it injects kexts placed in EFI/Clover/kexts/10.x or EFI/Clover/kexts/Other I don't know where the kexts you pictured above are placed (I assume /L/E or /E/E) but a few things appear incorrect. Patched (or vanilla) AppleHDA usually only loads from /S/L/E. You list an ApplePS2Controller alongside VoodooPS2Controller + VoodooPS2Mouse. You can only have one or the other, Apple or Voodoo, not both... USB ports: USB ports injection is done through the following summarized methodology: selecting the appropriate SMBIOS profile (should be MacBookpro5,1 for the E6500) renaming of all EHC1/EHC2 references in DSDT table to EH01/EH02 identification of all USB ports in IOReg by plugging a USB key in each individual port and taking a note of it editing the Info.plist file of provided USBInjector kext, where USB ports are defined according to IOReg findings under Mac model EH01/EH02 controllers (Mac mode being set to MacBookPro5,1 here) This has been explained at great length on Rehabman's repo and at InsanelyMac, it's a simple matter of applying what experts on the matter have written some time ago. mergesoft never bothered to reply or return to the thread so we don't know where he/she got after our suggestions and kexts supply… For your info, I recently worked on a Latitude E6400 that I set in close config to my D630: tuned FakeSMC (SMC+AGPM), MBP5,1 profile, USBinjector of D630. All worked perfectly. No reason why the same would not work on E6500... CPU performance: Poor performance with a Core2Duo CPU on Intel 45 Express chipset may result from: Dynamic Acceleration (IDA) being set in BIOS on a laptop fitted with a Merom CPU. It should only be set with a Penryn CPU. Which do you have? incorrect use or tune of FakeSMC kext/SMBIOS profile, resulting in lack of native CPU power management unnecessary use of NullCPUPowerManagement next Absence of P States + C States generation (selectable at boot loader level) This has been explained at great length in exiting articles and threads on this web site/forum. Audio: The Latitude E6500 is fitted with IDT 92HD71B codec. That's what you need to seek in terms of AppleHDA patch. The patched AppleHDA kext must go to /S/L/E and the codec-specific IDT next can go to /S/L/E or /L/E. Failing that, try VoodooHDA (you may need to experience several versions from say v2.7.1 to 2.8.9). Remember to repair permissions and rebuild cache after all kexts handling. Display outputs: With regards to display ports, you may have not noticed it but the DSDT I patched was mergesoft's initial table of E6400 origin. Griftopia's DSDT appears to be of Dell Precision (Mx400?) mobile workstation origin. I had not paid any attention to the GPU part of mergesoft's DSDT. If you compare the 2 files and examine the dGPU definitions under device AGP @00010000, you'll notice 2 things: E6400's table uses name IGPU for both iGPU and dGPU; this is not ideal at all but is not causing trouble and I can easily upload a revised DSDT that will rename the dGPU to GFX0. E6400's table uses different NVCAP settings than the Precision Mxx00's. This is the key to obtain both VGA and DP ports working as NVCAP defines the nVidia GPU output display ports arrangements. You basically need to look up for the correct NVCAP settings that fit to your E6500 system (LCD/LVDS + DP + VGA ?). Refer to the info provided here. If you can' find anything that works, try and remove the NVCAP part of your patched DSDT, reboot and see what's provided in IOReg. Hopefully, IOReg may show the correct values to inject (or not). E6400 NVCAP: "NVCAP", Buffer (0x18) { /* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, /* 0008 */ 0x0E, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A, /* 0010 */ 0x00, 0x00, 0x00, 0x00 }, Mxx00 NVCAP: "NVCAP", Buffer (0x14) { /* 0000 */ 0x05, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, /* 0008 */ 0x2A, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0E, /* 0010 */ 0x00, 0x00, 0x00, 0x00 }, ` I'll try and dig out the copy of the E6400 pack I recently helped finalize, hopefully, this can sort you out with your E6500. Note that my work did not include anything related to VGA and DP outputs.

https://en.wikipedia.org/wiki/Extended_Display_Identification_Data http://www.extron.com/company/article.aspx?id=uedid http://www.osx86.net/forums/topic/20664-guide-edid-injection/ https://sourceforge.net/p/cloverefiboot (chameleon, stolen and rebranded)/discussion/1726372/thread/f895ad29/ http://www.hackurmac.com/2014/03/guide-add-your-custom-retina-hidpi.html and so on...

If your laptop is fitted with HD3000 iGPU only and no discrete GPU, try the attached patched table. To test it, keep your existing patched table in place, copy this new patched table to your EFI/Clover/ACPI/patched folder (i.e. next to the existing DSDT) and call this new "DSDT2.aml" table manually at Clover boot time through the menu. DSDT2.aml.zip Modifications done: Renamed integrated GPU device "VID" @00020000 to "IGPU" Injected Capri layout 0x01660003 into device IGPU through _DSM method Removed all _PRW methods declared under Scope (_SB.PCI0.EHC1), Scope (_SB.PCI0.EHC2) and Scope (_SB.PCI0.XHC) Injected new _PRW methods directly under Device (EHC1), Device (EHC2) and Device (XHC) Set _PRW methods of devices GLAN, EHC1, EHC2 and XHC to return (0x0D, Zero) Injected current (power) settings into devices EHC1, EHC2 and XHC through _DSM methods You may also post your existing patched DSDT table for comparison. Can you also advise on your current CPU power management settings, i.e. did you: set your SMBIOS to MacBookPro9,2 or MacBookAir5,2? apply AsusAICPUPM patch in Clover config or patch AICPUPM kext in /S/L/E? generate your CPU-specific power management SSDT with Pike R Alpha's SSDT generator?

Means you probably need to collect your built-in LCD EDID info from, say, Windows and then inject this back into OS X. You can look it up on the Web, there are lots of posts and threads about it. Can't give you a link at the moment, sorry, but I'm sure you'll find something quickly.

Maybe you have parameter cpus=1 (or equivalent) in your bootloader config.

Fixing USB ports in ElCapitan is fairly easy: you rename USB2.0 devices from EHC1/EHC2 to EH01/EH02 in tour DSDT (rename all instances individually) you reboot with your patched DSDT then run IORegistryexplorer (or equivalent like IOJones or otherwise) to identify your USB ports. To do that scroll down in your IOREg explorer window to the EH01/EH02 devices, then plug a USB key in all your USB ports. Each time you plug the key in a port, take a note of the port id/address/number where the key appears after IOReg refresh you create a USBinjector kext in which you declare USB port details under a Mac model that matches the SMBIOS you use Here's an example for my D630, SMBIOS MBP5,1. You need to do the equivalent using SMBIOS MBP8,1 which you should be using for your E5420. Use PlistEditPro to view and/or edit the Info.plist of the kext. USB_Injector.kext.zip All of this is explained in various Hackintosh forums on the web, it's a simple matter of searching a little, experimenting and implemeting.

I don't know what you have in your Clover folder but it should theoretically work with minimal straightforward/obvious adjustments (for instance, I would not place injected kexts in folder 10.11 but Others).

Strange... Sierra was installed and runs the exact same way as El Capitan and with same pack on all my Hacks...

You may also refer to Jake's Latitude/inspiron Clover guide. Remember to use the forum Search facility and read existing guides.

You'll find what you need in the old general D430 thread. I listed details of my SL installation in post #140. It's old stuff and you'd need to forget about the old EDP part but you'll get very good pointers. https://osxlatitude.com/index.php?/topic/147-dell-latitude-d430-thread/ I also recommend you refer to this. https://osxlatitude.com/index.php?/topic/2036-bios-settings-d430/ https://osxlatitude.com/index.php?/topic/8815-full-packs-for-d430-snow-leopard-lion-mlpf-mountain-lion/ If you have no access to a Mac or a Hack, I can recommend Nawcom's ModCD (bootable CD; look it up on the web, should be available at osx86.net) and retail SL DVD (10.6/10.6.3/10.6.8) or its image restored to USB key (more difficult to do/obtain if you don't have access to a Mac/Hack). Obviously, you'll need the external CD/DVD drive. You can still buy SL from Apple. I know that a large majority of Hackintoshers would never consider spending $20 on this, but it's the ultimate base from which you can create Lion/ML/Mav/Yos/EC/Sierra USB installer. I posted full details of a Nawcom's ModCD method again in this D420 thread and it's fully applicable to the D430. I recommend you also read other D430 threads posted in this very D4xx section. Otherwise, there are ways to create a USB installer from Windows or from within a Virtual Machine but I've never used any of those. You can still search the web for that. Failing all that, there are methods I won't mention but, as usual, Google is your friend... One last thing, but an important one in case you had missed it: you cannot run Mac OS beyond Lion 10.7.5 (or hacked MLPF ML) on that machine due to Intel GMA950 graphics. You can certainly install ML, Mavericks, Yosemite and El Capitan but you'd have no support for the GMA950, i.e. no graphics acceleration and the system would run like a dog with bad graphics.

Did you use the bootpacks from guides posted on this forum? They contain the correct PS2 Controller with TrackPad support. Grab it from here if you want (obviously in the Yosemite pack). SD card reader should work with the DSDT patch also mentioned in the same guide Wifi depends only on the card model you have. If Intel, replace it with any compatible cards that fits in your E6420, whether mini-PCIe or half mini-PCIe. Look-up the non-exhaustive list posted on our forum. Finally, Intel i5-2540M is fitted with HD3000 iGPU, not HD2000...