Hervé

Try and reseat the modules maybe.

Try and remove one of your SODIMM to check how it goes with only 4Go.

In all likelihood, that'll be a HWMonitor related issue. Your SysProfiler reports 2 cores... Make sure to use the HWMonitor that goes with FakeSMC + all the FakeSMC PlugIns. Kozlek provides full packages on his repositories. Eg: http://sourceforge.net/projects/hwsensors/files/* You do have both Cores enabled in Clover, right?

"somewhat successfuly" you said? 1st gen Intel HD is only partially supported on those models due to eDP display connector. Try and remove the Intel HD kexts and see if it boots to completion. There are plenty of threads and posts related to this model. Did you read them? You'll never be able to gain graphics acceleration on this model, so you'll only experience poor performance. The E6410 with 1st gen Intel HD graphics is not a suitable platform as a Hackintosh.

No, I don't think you understand. Check your loaded kexts in SysProfiler. You most probably do not have any AMD kexts loaded. I'm not actually sure your Radeon card is supported. Getting the card reported, as in "identified", in SysProfiler is different from being supported and gain graphics acceleration. In fact, the card being detected in SysProfiler does indicate that OS X is able to collect information from BIOS tables. However, OS X does not support dual graphics in most Hackintoshes (Optimus-like technology is not supported). You may have to rely only on the Intel HD chip.

You may manually edit the SMBIOS plist through a text editor like TextEdit or vi in Terminal (if you know vi of course). One of the easiest way is to use Chameleon Wizard app from which you can open up your existing SMBIOS plist file and generate random serial numbers.

Sounds like your bootloader operates in its default US QWERTY mode. "-" key will be 2nd one left of DELETE/BackSpace key, itself located above the ENTER key. If you're using Chameleon or Enoch, you may install the bootloader keyboard layout that fits your country, if it exists of course (not all models exist..). Some layouts are available from the installation package when you run it.

I suspect somethign wrong with the bootpack. Maybe it's a Clover pack, not a Chameleon one. If you're installing Mountain Lion of Mavericks with myHack, I suggest you follow this Mavericks guide. Obviously, don't use the patched SNB FrameBuffer kext from Mavericks with ML... NB: For Lion and ML, Im' pretty sure you'll need the older AppleACPIPlatform kext v1.3.6 (of SL 10.6.8) provided in the Chameleon bootpack. It's not required with Mavericks and later OS X versions.

If it's running Ok off the HD4600 when Switchable Graphics are enabled in BIOS, you may not have to disable the nVidia GPU by SSDT. Try it out, experiment and see by yourself. Best way to learn...

Seems Ok, so you just need to inject desktop HD4600 id (0x0412) in Clover since you're not injecting this in the DSDT.

You obviously don't have any graphics kexts loaded for that Radeon HD 6370. In fact, if you look inside the AMD6000Controller kext, you probably won't see any reference to id 68e4. Ex: AMD6000Controller kext of Mavericks 10.9.5 <key>CFBundleIdentifier</key> <string>com.apple.kext.AMD6000Controller</string> <key>IOClass</key> <string>AMD6000Controller</string> <key>IOMatchCategory</key> <string>IOFramebuffer</string> <key>IOName</key> <string>AMD6000Controller</string> <key>IOPCIMatch</key><string>0x67681002 0x67701002 0x67791002 0x67601002 0x67611002 0x67501002 0x67581002 0x67591002 0x67401002 0x67411002 0x67451002 0x67381002 0x67391002 0x67201002 0x67221002 0x67181002 0x67191002 0x68401002 0x68411002 0x67041002</string> You could try to start by patching that kext and see where that leads you.

?

Why don't you switch to Enoch bootloader? By far, it's a lot simpler to use than Clover and does not require a driving license or a PhD like Clover so often does. Enoch r2795 works perfectly with EC (and earlier versions). I can pretty much guarantee that it'll boot your EC partition on the 1st attempt. You just need: 1) a folder called Extra at the root of your OS X installation 2) a subfolder called Extensions in /Extra, where you place your add-on/injected kexts 3) to create your boot plist + SMBIOS plist in /Extra with a tool such as Chameleon Wizard 4) to create a Enoch-specific kernel plist in /Extra 5) to add EC-specific SIP-disabling CsrActiveConfig parameter in your boot plist and set it to 3 (or any other appropriate/desired value but 3 is fine) Your SMBIOS plist should be set to MacBookPro9,2 or MacBookAir5,2 (generate your own serial number using the 2 x Random buttons): Your boot plist should be set to something like this: To add the SIP-disabling parameter, edit your boot plist with TextEdit and add the following lines: <key>CsrActiveConfig</key> <string>3</string> ` For the kernel plist, you may use the file attached below. If you want to cache/prelink your kexts (to speedup boot time), copy them from /Extra/Extensions to /Library/Extensions, repair permissions and rebuild the cache, then set KernelBooter_kexts to No in the kernel plist using TextEdit. kernel.plist.zip If you use a patched AppleHDA kext, you can keep it in /L/E as long as you remove the original vanilla one from /S/L/E.

Obviously, since I wrote earlier that it was the same patch in EC than Yos. Otherwise, there would not be much sense mentioning it, would there?

For wifi, please lookup our non-exhaustive inventory of supported/unsupported cards and dongles as listed in the R&D->hardware section. Please use the forum Search facility.

Reboot with -f -v and tell us where it stops. I take it you used the generic boot pack, right?

If HDMI output does not work, then you probably did not apply the patch properly. I tested it myself directly on the Azul FB kext and I can guarantee that it works. Can't say about DP since my E6440 does not have any such port. I'd have to check for audio, it's been a while since I put my laptop on a TV screen for testing but if memory serves me right, I don't recall getting HDMI audio working... Maybe it also depends on the AppleHDA patch.

Use the forum Search facility and follow the guides! https://osxlatitude.com/index.php?/topic/2945-guide-for-enabling-vga-and-hdmi-in-intel-hd4000-gpu/

You can consult the existing guides for that model (especially JakeLo's guides) and the numerous threads for this model to find what you need for those missing finctionalities such as audio and battery management.

Most if not all of the pack provided here should do for EC.

Azul FB needs patching for HDMI output... Same patch in EC as in Yos. https://osxlatitude.com/index.php?/topic/7387-dell-latitude-e6440-with-i5-4300m-hd4600-and-1600x900-lcd-mavericksyosemite/page-2&do=findComment&comment=48816

Please look at our list of supported/unsupported wireless cards in R&D->Wifi forum sub-section. Lenovo systems often suffer from whitelist BIOS which limits the choice of mini-PCIe/half mini-PCIe cards, so check out the Lenovo web site 1st. No such issue with USB dongles.

http://www.osxlatitude.com/edp/documentation/

I've updated the guide to avoid any confusion since there clearly was some with El Capitan. Please follow the revised instructions to the letter: For [...] Yosemite and El Capitan, proceed as follows: Remove the 3 WWAN modems listed in Network Preferences Make a backup of vanilla CellPhoneHelper kext found in /S/L/E Make a copy of CellPhoneHelper.kext from /S/L/E to your desktop Open up the Desktop kext and browse through to the Contents folder to patch the Info plist as detailed below Once your plist has been updated, move the patched kext from your Desktop to /S/L/E and replace the original kext Repair permissions, rebuild cache and reboot The patch basically consists of a pasted copy of the Sony Ericsson W350 entry, modified with the Ericsson FF5521gw, HP hs2340 or Dell DW5550 PCI device ids (entered in decimal values) and the Sony Ericsson reference for Device Vendor. It seems you took the shortcut of copying/pasting the code I had previously published as an example in the thread. That applied to Mav/Yos and will not work in EC... I've modified the guide to avoid this. Basically, you need to start from the W350 entry provided in CellPhoneHelper v1.4.0 of EC. You should notice the code differs a little between the EC version of the kext and earlier OS X versions; that's why the patch you made was not working.

Well, it seems you'll apparently find what you need with a simple Google search on "BCM5761 kext"...