Hervé

There are examples of what to do here. This was all based on Chameleon installation, not Clover which may overwrite some of those settings...

Sounds like a cache issue. Try to boot Chameleon with -f flag.

Check the various USB devices in the DSDT, they may also have to be renamed into UHC devices. Changing EHCI to EHC1 may not be sufficient. Following such advise from Polyzargone at IM, I'm about to verify this on the D630. Meantime, try this new one where all USBx devices are converted to UHCx devices: E6400_DSDT.aml.zip

You should post your files for the benefits of others.

Afaik, you can only run off the HD4600, the discrete AMD GPU is not supported (yet?).

Jake has posted several posts about the method to fake desktop HD4600 GPU (id 0x0412) with kexts. I'm sorry I don't have links at hand but you'll find them in the guide section or through the Search engine. You can also consult my E6440 Mavericks/Yosemite guide which fully details the methods I followed to patch the Azul frame buffer kext to support the mobile HD4600 GPU (id 0x0416). The exact same principles will apply to your HD4400. PS: afaik, Chameleon boot parameter "IntelAzulFB=xxx" is ineffective with Yosemite. With my E6440, it worked perfectly with Mavericks, never with Yosemite. I had to patch the DSDT.

That's quite normal, but can you confirm you reached the Yosemite desktop? You now need to finalise tuning to obtain graphics acceleration. You could do that either by faking HD4600 Desktop or by patching the graphics kext.

Again, all the necessary kexts and files are in the D630 pack I posted... You don't need EDP, which happens not to work at this time.

You probably have the wrong DSDT with unsuitable graphics settings for your particular LCD. What's its resolution?

No reason why it would not work. You can use my E6440 guide and adapt if necessary. I've linked to it on post #52. It'll depend on your own system's specs but it should be very similar to the E6440.

You need to set up the clover config.plist correctly for your own model, depending on specs. Could mean unselecting all DSDT fixes, selecting (or not selecting) kernel and/or AICPUPM patch, etc. I still haven't managed to boot the Clover USB installer on my C2D-based D630 either...

Open up the DSDT.aml file with a tool such as DSDTEditor, then do a search for "EHCI" and replace by "EHC1" (there could be a couple of instances). Compile the edited code and save as DSDT.aml. Place the newly compiled DSDT file in the Clover folder and reboot.

Are you building a myHack installation with our OSXL bootpack? Or is it some other method or a distro?

Maybe you're not using the correct bootpack for the Lion installer. You can use those I posted for the D630 X3100.

Sure, there are many guides on this forum for the E6x30 series. Use the "Search" facility.

BIOS settings all supplied at the top of the D8xx section...

No kext needed to support SATA drives.

Apple's Security Update 2015-004 will again break MPLF. In addition to the same files as mentioned above, it also installs IOSurface kext v86.0.5 in /S/L/E. A rollback to attached version v80.0.2 is necessary to fix the MLPF installation. IOSurface.kext.zip

Well, you obviously need to undertake the same graphics tuning you did for Yosemite... Mobile HD4200/HD4400/HD4600 are not natively supported by OS X to date.

Unselect all fixes under DSDT fix mask.

I've done a complete fresh installation using a Clover-based 10.11 USB installer this time. Process is same as for Yosemite, using the following well-known/well-documented method: Double click on InstallESD.dmg found in Install OS X 10.11 Developer Beta.app/Contents/SharedSupport to mount the dmg image Then 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 Install Clover v3224 to the USB installer. Keep default settings, just change bootloader option to install in MBR Place the attached DSDT + SSDT in EFI/CLOVER/ACPI/patched Place the attached kexts in EFI/CLOVER/kexts/other Use the attached config.plist file or adjust the options as follows at the Clover Boot Manager main menu once booted off the USB key: in DSDT fix mask, unselect Fix Display + Fix USB + Fix sound in Binaries patching, select AppleIntelCPUPM At the Clover boot Manager main menu, select the 1st listed partition ("Boot Mac OS X from OS X Base System"), press space and select boot without caches. The OS X installer will then load If/when prompted for USB keyboard and/or mouse, just press [ENTER] twice Proceed with OS X 10.11 installation as usual DSDT.aml.zip i5-2520M_ssdt.aml.zip kexts.zip config.plist.zip I've not managed to boot the installer of 0S X 10.11 with Chameleon yet, but here are copies of the kernel (to be placed in /S/L/Kernels as per Yosemite) and of the patched AICPUPM kext (to be placed in /S/L/E). As always, the i5-2520M SSDT must only be used on E6220 models fitted with that specific CPU. Other CPU models will require their own specific tuned-up SSDT which can easily be created by the usual SSDT Generator tool.

Try an use a recent version of Clover.

Device (EHCI) must be changed to Device (EHC1) in the DSDT or external USB ports will be dead. I much prefer the system with working USB ports!

myHack v3.xx never supported Yosemite so I think it would have been difficult to create a myHack Yosemite installer. If you did, tell us how because you'll make lots of people happy. More seriously, I've recently posted full packs for the D630 nVidia, so don't hesitate to use that as a workaround to the current EDP issues.

Manufacturer's online support->model documentation is usually the best (ignored/forgotten) place to find system's specs. A basic Google search on "XYZ specs" usually leads good results too... For the more techies, the output of lspci -nn Terminal command or of DPCIManager tool will give good pointers.