Hervé

Just use the kexts provided in the published bootpack, stay away from EDP (unless you want trouble) and use the specific PS2Controller kext of the bootpack. That's all. The kexts go to /L/E and you repair permissions + rebuild cache with those Terminal commands you've listed above.

You can try as long as you use an AMD kernel. I can highly recommend those built and published by Bronya. You'll find them at InsanelyMac. Worked great for recent versions such as Mavericks or Yosemite. Don't know if it were provided for El Capitan, I've not followed the developments for months.

3rd Developper Beta (16A254g) released today. D630, Penryn C2D/nVidia Quadro NVS 135M -> Ok E6220, Sandy Bridge i5/HD3000 -> Ok (but using previous version of patched AppleHDA is now KO) E6230, Ivy Bridge i5/HD4000 -> Ok (but using previous version of patched AppleHDA is now KO) E6440, Haswell i5/HD4600 -> Ok (but using previous version of patched AppleHDA is now KO)

2 things you can do for headphones: 1) ensure you boot with headphones connected or 2) after plugging in your headphones, put laptop to sleep then wake it

You can also use the attached. All thanks to Rehabman. BrcmPatchRAM2.kext.zip

Which PS2 controller are you using? This one?

KP is probably due to the PS2Controller you're using although this usually did not happen until 10.11.4 and you're obviously installing 10.11.3. You shoud be able to safely use the version provided here. Just replace the kext. Indeed, Intel i5-3340M is a dual-core CPU, but each core is dual-thread capable, hence 4 logical CPUs...

I'm not sure this guide is still appropriate… It's quite outdated nowadays. Why don't you guys follow a more standard and traditional method instead, like for the older D630/D830? It's going to be the same principle and overall fine-tuning for your 1st gen Core CPUs as it were for Core2Duo. What will differ will be FakeSMC tuning, SMBIOS profile and those kexts specific to the E6410 hardware. 'should be something like this: 1) USB installer creation procedure: Mount InstallESD.dmg found in Install OS X Yosemite.app/Contents/SharedSupport Then, using Terminal, mount BaseSystem.dmg (hidden file) open /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg Use Disk Utility to restore the contents of BaseSystem.dmg on a USB key (or HDD partition) formatted Mac OS extended (journaled). Remove link for Packages in folder System/Installation of your USB key rm /Volumes/OS\ X\ Base\ System\ 1/System/Installation/Packages Copy folder Packages located in InstallESD.dmg to folder System/Installation of your USB key cp -R /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System\ 1/System/Installation Copy the 2 hidden files (BaseSystem.dmg & Basesystem.chunklist) of InstallESD.dmg to the root of your USB key cp /Volumes/OS\ X\ Install\ ESD/BaseSystem.* /Volumes/OS\ X\ Base\ System\ 1 To boot with Chameleon (you can safely use versions r2395, r2401 or r2468): Download the appropriate package off InsanelyMac's repo and install Chameleon on the USB installer partition called "OS X Base System" Create a folder "Kernels" under /System/Library of the USB installer and place a copy of the vanilla kernel there as "kernel"Yosemite 10.10.x kernel available here Create a folder "Extra" at root of your USB installer and copy the files of the E6410 boot pack there Copy the kexts from the pack to /System/Library/Extensions, repair permissions and rebuild kext cache sudo chmod -R 755 /Volumes/OS\ X\ Base\ System\ 1/System/Library/Extensions sudo chown -Rf 0:0 /Volumes/OS\ X\ Base\ System\ 1/System/Library/Extensions sudo touch /Volumes/OS\ X\ Base\ System\ 1/System/Library/Extensions sudo /Volumes/OS\ X\ Base\ System\ 1/usr/sbin/kextcache -Boot -U /Volumes/OS\ X\ Base\ System\ 1 -K /Volumes/OS\ X\ Base\ System\ 1/System/Library/Kernels/kernel ` 2) Yosemite installation procedure: Boot your USB installer and proceed with installation (if prompted for Bluetooth keyboard and mouse, just press [space]) Upon completion, reboot your freshly made Yosemite installation via your USB installer and complete 1st boot system configuration 3) Post-installation fine-tuning: Install Chameleon bootloader on Yosemite partition ​Copy the Extra folder of your USB installer to your Yosemite partition Copy the kexts of your Extra folder to /S/L/E From Terminal, repair kext permissions and rebuild cache sudo chmod -R 755 /S*/L*/E* sudo chown -R 0:0 /S*/L*/E* sudo touch /S*/L*/E* sudo kextcache -Boot -U / From Terminal, adjust Sleep mode sudo pmset hibernatemode 0 sudo rm -f /var/vm/sleepimage ` NB: You may prefer to opt for Enoch rather than Chameleon these days. Recent versions such as 2795 are perfect for all recent OS X versions from Mavericks to El Capitan. More recent versions from r2824 fully support Sierra too. Enoch is available at the usual Insanelymac repository. You may also want to install El Capitan rather than Yosemite. You can follow this D630 guide if you wish, which is just an updated version of the Yosemite procedure.

Forget the VoodooPS2Controller then. Keep the ApplePS2Controller you currently use. What you can do though is add your country Logitech layout if it's available in Ukulele package. Use the older version v2.2.8 rather than newer version v3.0.4. Simply copy the 2 files for your country layout in /Library/Keyboard Layouts and reboot. Keyboard mapping is an old matter and has been mentioned before on the forum: https://osxlatitude.com/index.php?/topic/2616-non-mac-keyboard-maps/

As mentioned earlier, due to obvious dependancies issues, this kext can only be injected from /E/E with Enoch and/or, I guess, Clover's EFI/kexts folder. It cannot loaded (nor cached) from /S/L/E or /L/E.

Which boot loader are you using, Clover or Chameleon/Enoch?

No, the DSDT normally remains untouched throughout for graphics. It can need updating on occasions; for instance the USB device for El Capitan.

Did you patch your DSDT for HD3000 layout and screen res at all? What LCD screen resolution do you have? Anything beyond 1440x900 usually requires to set DualLink to true.

Re: keyboard layout, you may want to consider the ISO layout of your VoodooPS2Controller if that's what you use: https://osxlatitude.com/index.php?/topic/8641-proper-keyboard-layout-recognition-with-voodoops2controller-eg-latitude-e-series/ In Lion 10.7.5, you have to run AppleACPIPlatform kext v1.3.5 or v1.3.6 from SL, otherwise your laptop would KP. Check your hibernation mode, your power savings settings in the PrefPane and verify that you do have native CPU SpeedStepping in place (correct tuned FakeSMC kext + correct SMBIOS profile). https://osxlatitude.com/index.php?/topic/2673-performance-tuning-with-fakesmc/ If you have all that but still experience issues with sleep causing immediate wake, then the issue is DSDT related and I'd suggest you post your current DSDT.

Probably an Optimus-related issue. Did you tune your laptop for HD3000 graphics? Do you get graphics acceleration at all?

Mobo baking is indeed not a permanent fix and one will require to re-bake again; can be sooner, can be later. It really does depend on the quality of reballing and long term usage but it does fix the GPU issue. I've had to re-bake my D630 about 3 times in the last 4 or 5 years. 10 good minutes at 200C, then stop the oven, open its door and leave the mobo cool off. Make sure to have native CPU+GPU SpeedStepping in good working order + fan free of any dust clog + non-dry thermal paste onto CPU+GPU. If you heavily use your laptop, pay a little annual visit to the mobo inside the casing.

Normally, it should be the same set of files as for EC, except the temporary MBP7,1 SMBIOS only for installation (return to MBP5,1 afterwards). Well, it was for my D630...

Cards working under Sierra in an identical manner as under El Capitan (no controller listed in SysProfiler). They just require the Generic USB3.0 XHCI kext. Here the GMYLE adapter:

If you read the thread I linked above, it says not to install/run EDP as it is not necessary. Unfortunately, you seem to confirm that EDP remains screwed up for our original D Series these days. Just run myHack and if it does not prompt you to install the Extra folder, re-run myHack and choose "Install Extra" in the myHack menu, pointing to the downloaded pack from my D6x0 thread. that's all you need to do. Same goes for Chameleon, myHack may not install Chameleon automatically. So don't hesitate to download version r2468 and install it manually.

myHack is based on Chameleon. Stick to that for a Lion installation. It'll be much easier than Clover.

Please install Lion with myHack tool + the D620 GMA950 HiRes Lion pack available here. Forget Leppy's old SL guide, it's deprecated nowadays. Guidance for myHack installation is available in the EDP menu at the top of your screen.

2nd Developper Beta released today (version 16A239j): D630, Penryn C2D/nVidia Quadro NVS 135M -> Ok E6220, Sandy Bridge i5/HD3000 -> Ok E6230, Ivy Bridge i5/HD4000 -> Ok E6440, Haswell i5/HD4600 -> Ok Cache rebuild systematically reports an error but appears Ok (computers reboot fine and quick afterwards): KernelCache ID: 20FECA3505CEEE55E16D0FD8236A6E14 symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>

Look up for the patch for the well-known final stage boot glitch. Basically you need to binary patch the IOGraphicsFamily kext.

The order of the permissions repair commands (sudo chmod/sudo chown) does not matter as long as they're done ahead of the sudo touch commands (their own order does not matter either) and the final sudo kextcache command.

Where did you install your add-on kexts? /S/L/E or /L/E? Maybe Kext Wizard does not work well in EC 10.11.5. Personally, I've not used tools like this for years. I'd invite you to follow the manual method described in the guide you followed, starting with permissions repair: sudo chmod -Rf 755 /S*/L*/E* sudo chown -Rf 0:0 /S*/L*/E* sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo touch -f /S*/L*/E* sudo touch -f /L*/E* sudo kextcache -Boot -U / This method pretty much garantees good cache rebuild. if you encounter errors (it can happen and that's why I prefer the manual method to tools like Kext Wizard), retype the last 3 x commands. Booting without cache is "just" a lot slower than with it; that's about it.