Hervé

UseKernelCache is always set to Yes on all my Chameleon/Enoch builds. HDMI output should work OOB O2 Micro SD card reader works OOB with the published patch for the appropriate DSDT device (identify the device with IORegistryExplorer, then patch the device to declare compatibility with Apple's own device 14e4:16bc). All details are available in the R&D->Card readers section. For keyboard layouts, please consult the existing topics on that matter in the R&D->Keyboard section.

Not sure the BrcmXXX kexts actually operate from /L/E. I've always had to install them in /S/L/E, very much like the patched AppleHDA kexts. All FakePCIIDxxx kexts are Ok in /L/E on the other hand.

Here's an older guide for Mavericks on the HD3000 model. For Yosemite, you can follow the principles of this E6220 guide, knowing that you can reuse the kexts used for Mavericks. Same installation process for El Capitan an Sierra but changes will be required: 1) need to switch to Dr Hurt's PS2 controller kext. Provided in the E6220 El Capitan/Sierra guide 2) need to modify DSDT to rename EHCx USB2 controllers to EH0x and use a USB injector to retain all USB ports working Jake has a Clover-based El Capitan/Sierra generic guide that includes packs for the E6420.

There are existing threads about OS X on this workstation model in this forum Desktops section. Have a read through.

It's embedded in the last few pages of Dr Hurt's thread.

/E/E is only used with Enoch to inject kexts at startup if you boot with option KernelBooter_kexts=Yes. It's not used with Clover but it operates the same way as kexts placed in EFI/Clover/kexts/xxxx. For kexts to be cached (which is what anyone would want), they should be placed in /L/E (that's the place meant for 3rd party kexts) or, alternatively, /S/L/E but that latter is better kept vanilla/untouched (except for patched AppleHDA).

You must have changed something somewhere. I assume you're using Clover so check that you're still faking the correct desktop HD4600 iGPU.

You can ignore that, that's Ok. If you get an error with a number 77, you must however repeat the cache rebuilding.

Clover on-the-fly patches only apply to cached kexts. I don't use Clover so I could be wrong but I believe that AppleHDA will not load (and therefore cache) if the IDT dummy kext is injected through Clover's EFI/Clover/kexts/xxxx folder. To me, the dummy kext must be placed in /L/E (or /S/L/E) to be cached. Once the kext is moved there, you should repair the folder's permissions and rebuild your cache. I don't think you'll manage to get audio if you only place the dummy IDT kext in Clover's kext folder.

Maybe you can post a zipped copy of your EFI Clover folder and advise whether you've added any kexts to /S/L/E or /L/E. Did you get any error when you rebuilt cache?

Post your DSDT; you may need to rename XHC1 to XHC but also to add "Darwin" to the OSI tests in order to set OSYS parameter to values as per Vista, Win7 or later.

If you search the forum, you'll find many threads and posts about this known issue and the BIOS downgrade you need to do.

No double posting please... I suggest you boot your USB installer and, once at the main screen, open Terminal to copy your original PS2 kexts from your USB installer to your HDD partition. If you're using Clover, mount the EFI partition and copy the kexts in the EFI/Cover/kexts/10.xx or EFI/Clover/kexts/Other folder.

Audio should work without issues with the IDT dummy kext found in my E6220 El Capitan pack + the published AppleHDA Clover on-the-fly patches. Details of this IDT 92HD90 (codec 76E7) patch are available in numerous threads/posts.

The best thing to do until one has generated his/her own CPU-specific SSDT is to run with NullCPUPM. The time-out related delay with AppleACPICPU may be linked to patched AICPUPM without proper SSDT. I guess arcaman6 will know once he has generated and used his SSDT.

You said you didn't care about battery life... In principle, if Apple followed their past trend, yes it's highly likely that they used IGPU naming convention on the MacBookPro13,1/13,2/13,3. The only way to verify is to obtain an extracted DSDT or IOReg off one of those Skylake MBP. I would certainly run Sierra for such an SMBIOS, that's what those MBP models were released with so I'm not entirely surprised El Capitan would not boot such a profile. If you look at the MacBookPro13,x range, you will see that: MBP13,1: low voltage Skylake i5/i7 CPU + Intel HD 540 graphics (0.30-1.00/1.05GHz) MBP13,2: low voltage Skylake i5/i7 CPUs + Intel HD 550 graphics (0.30-1.05/1.10GHz) MBP13,3: regular Skylake i7 CPUs + Intel HD 530 graphics only (0.35-1.05GHz) or dual Intel HD 530/AMD Radeon Pro 450/455 Re: CPU power management, did you use Pike's Master or Beta branch? You need to use the Beta version for Skylake CPUs. It does cater for i7-6820HQ and MBP13,x as shown in the Skylake.cfg and Models.cfg database files:

https://osxlatitude.com/index.php?/topic/7914-dell-latitude-e6220-with-i5-2520m-hd3000-and-1366x768-lcd-mavericksyosemiteel-capitansierra/ https://osxlatitude.com/index.php?/topic/9383-dell-e6220-i7-2620m-clover-detailed-guide/ and somehow (but would benefit from adjustments for Sierra at this point of time) https://osxlatitude.com/index.php?/topic/8506-dell-latitude-inspiron-precision-clover-guide/

Please use the existing and proven guides that provide all that you need for this model.

You may also opt for the Apple BCM94360CD with mini-PcIe adapter. Works perfectly, OOB and up to 1.3Gbps. It requires 4 x antenna connexions but tha's not an issue with the E6x00 Series.

Il you lookup Pike R Alpha's repository, you 'll see instructions regarding options/parameters you can pass to the script in order to get your SSDT generated. The script uses a given database of CPU settings and obviously not every single model is included. But you can do it yourself. The instructions to do so are also provided. You can Google for "Pike R Alpha ssdt generator".

You cannot be in high performance mode without speedstep, on the contrary. I believe you'll find your system to be laggy without it. Best way for you to get a feel is try and experiment it by yourself I guess.

Strange request... Without proper CPU power management in place, you CPU should operate at LFM (800MHz or 1.2GHz, I don't know) and HFM (2.7GHz), i.e. switch between them two with no intermediate speeds and no Turbo boost. You'd experience reduced performance because of this, a much slower system and probably reduced battery usage; it's not the recommended way to run your Hackintosh. But if that's what you want, simply remove your generated SSDT from your EFI/Clover/ACPI/Patched folder.

Please try and post in the correct sections. You keyboard and Touchpad will work wih Dr Hurt's recent ALPS TouchPad controller kext. Versions R4, R5 or R6. They're available in his dedicated thread of the R&D->Kernel Extensions subsection.

Is it a DW1502 or DW1702? What do tools such as DPCIManager or lspci -nn Terminal command show? A card based on Atheros AR9285 (168c,2b) works under OS X with the DSDT patch that declares it compatible with AR9380 168c,30 for instance. The card is 2.4GHz only so it won't detect 5GHz networks by the way...

Don't waste your time on this model. It uses an eDP connector for the LCD screen and that's not supported on 1st gen Intel HD graphics. As such, the best you can get is partial graphics acceleration which leads to poor system performance.