Hervé

Your E5520 is probably not too far off the E6x20 Series, so you can use the same installation method as listed in the various guides we have on this forum for those models. You'll have to generate your own CPU-specific SSDT for CPU power management if you can't find an existing one.

Then I would say your bootloader did not install properly. Re-install using default settings.

The kernel file goes under the name "kernel" in a folder called "Kernels", itself located in /System/Library. The "Kernels" folder does not exist by default and needs to be manually created for the Enoch / Chameleon based method.

Not really, the issues really seems to be related to the eDP/Intel HD graphics matter. This being said, we don't really know the method you used to create your USB installer, nor the list of add-on kexts you used. As an absolute minimum, you'd probably get away with a minimum set made of PS2 controllers + FakeSMC. And of course, as advised by Jake, remove the IntelHD graphics kexts so that they're not even loaded as the system boots up.

That cache and relinked kernel rebuilt ran Ok.

You can follow my ElCapitan guide for the D630 nVidia, using the D830 bootpack (or not). The only difference is that Yosemite does not require the CsrActiveConfig parameter (no SIP issue in Yos like in EC), just the kext-dev-mode parameter that you set to 1.

Just fitted one of those in the PCIe x8 (operates at x4 max) slot. Great cheap PCIe add-on card for this older SATA-I/PCIe 1.0 workstation. PCIe x4 may be a must for maximum/SATA-III performance. Made some quick performance comparisons with the BlackMagic app in Mav 10.9.5 and Yos 10.10.5: SSD off the integrated ICH5 SATA-I (150MB/s) non-AHCI controller (no Trim) Read: 132MB/s Write: 127MB/s SSD off the PCIe x1 (v1.0, i.e. 250MB/s) Marvell SATA-III (600MB/s) AHCI controller (Trim enabled) Read: 215MB/s Write: 145MB/s Looking forward to try out a PCIe x4 controller now.

These have been mentioned on other forums before but I got an opportunity to buy one of those PCIe SATA controllers for a few Euros. The card was advertised as based on Marvell 88SE9128 chipset but the model I received turned out as a 88SE9123. It certainly does not seem to make a difference and I reckon that most if not all Marvell 88SE9xxx-based SATA controllers would work exactly as this one does. The card comes as a basic and very compact PCIe x1 card with 2 x SATA-III 6Gb/s ports. Variants with 4 x ports or more exist too (there are various manufacturers offering SATA controllers based on those Marvell chipsets on PCIe x1/x2/x4 cards: Syba, Startech, IOCrest, etc.). It works OOB in Snow Leopard, Lion, Mountain Lion, Mavericks and Yosemite. By default, it's listed as "Unknown AHCI controller" under SL and as "Generic AHCI controller" in more recent OS X versions such as Mavericks or Yosemite, which can easily be fixed through a little patch of AppleAHCIPort kext. Just insert the card in a PCIe slot (x1, x4, x8 or even x16) and attach the disk(s). Perfect for older desktop PCs that do not have a SATA-II/SATA-III/AHCI capable controller and wish to enjoy SATA HDDs or SSDs at PCIe x1 speed (250MB/s for v1.0, 500MB/s for v2.0) and, for SSDs, enable Trim. WS670_SL:~ admin$ lspci -nn pcilib: 0000:05:00.0 64-bit device address ignored. [...] 04:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9123 PCIe SATA 6.0 Gb/s controller [1b4b:9123] (rev 11) 04:00.1 IDE interface [0101]: Marvell Technology Group Ltd. 88SE91A4 SATA 6Gb/s Controller [1b4b:91a4] (rev 11) {...] WS670_SL:~ admin$ ` The PCIe bus obviously drives the overall controller performance. As such, the true speed obtained on drives (and especially SSD) depends entirely on the PCIe version. As a reminder, theoretical unidirectional speeds per PCIe lane (in MB/s) are as follows: version\slot x1 x2 x4 x8 x16 PCIe 1.0 | 250 500 1000 2000 4000 PCIe 2.0 | 500 1000 2000 4000 8000 PCIe 3.0 | ~1000 ~2000 ~4000 ~8000 ~16000 (round-up values, real rates are about 1.5% lower) ` Performancewise, I obtained the following Blackmagic results on my old Precision 670 (PCIe v1.0, i.e. 250MB/s lane) with my Toshiba SATA-III SSD (Trim enabled) : Read: 215MB/s Write: 145MB/s 'not a huge improvement compared to results obtained with the SSD off the integrated SATA-1 (150MB/s) controller, but at least Trim is available.

Rest assured that trying to install a webcam driver on a computer that does not have such hardware is as effective in terms of destroying power as toilet paper in terms of protection againt nuclear explosion!

Maybe those tools have any issue with ElCapitan or you're not using the correct value to disable SIP. With a CsrActiveConfig boot parameter set to 3, I can personally copy/replace kexts in /S/L/E and/or in /L/E, then repair permissions and rebuild cache using the usual well-known Terminal commands.

I would advise you to return to the vanilla kexts and experiment wit basic kext patching, starting by adding your HD6370 device id to the AMD6000Controller kext.

You're gonna have to be a little more specific... How do you add kexts and what kexts are they? Did you disable SIP to take your kexts into account?

When using Rehabman's most recent or latest ACPIBatteryManager kext (v1.60.x for instance), battery icon keeps flapping between battery level and no battery, this being accompanied by a very annoying flapping of screen brightness. I've looked into the DSDT to try and fix this and noticed 2 x different battery devices: BAT0 and BAT1. Device (BAT0) { Name (_HID, EisaId ("PNP0C0A")) Name (_UID, One) Name (_PCL, Package (0x01) { _SB }) Method (_STA, 0, NotSerialized) { Store (ECG5 (), Local0) And (Local0, 0x02, Local0) If (Local0) { Return (0x1F) } Return (0x0F) } Method (_BIF, 0, NotSerialized) { Name (BIF0, Package (0x0D) {}) ECG9 (One, BIF0) Return (BIF0) } Method (_BST, 0, NotSerialized) { Name (BST0, Package (0x04) {}) ECG6 (One, BST0) Return (BST0) } } Device (BAT1) { Name (_HID, EisaId ("PNP0C0A")) Name (_UID, 0x02) Name (_PCL, Package (0x01) { _SB }) Method (_STA, 0, NotSerialized) { Store (EEAC (0x05, Zero), Local0) If (LLess (Local0, 0x02)) { Return (Zero) } Store (ECG5 (), Local0) And (Local0, 0x08, Local0) If (Local0) { Return (0x1F) } Return (0x0F) } ` After some research on the issue and reading several real MacBook's DSDT code, I experimented a little on this and obtained what I believe to be a good and suitable solution by: removing the DSDT section related to Device (BAT1) replacing all remaining DSDT references to BAT1 by BAT0 renumbering Device (BAT0) _UID identifier from 1 to 0 Since applying those changes, battery icon and screen brightness have stopped flapping. I invite all E6440 owners to try out this patched DSDT and report accordingly. New_E6440_DSDT_Battery_Fix.zip

What do you mean with "No files (kext) uploaded" or "files (kext) uploaded"? Can you please clarify? As I see it in the verbose screenshots, the AMD6000Controller never seems to load. Did you check in SysProfiler->Software->Extensions as suggested? You have some work to do on that and it may require that you further define that Radeon HD6370 definition in DSDT but it seems to be Ok at the moment. This being said, I'd research the correct ATI Config profile to use to be sure ("ATY,Eulemur" at present). If you followed this thread (which is all about AMD kext patching as I had previously suggested), make sure to repair permissions and rebuild cache after you play with kexts in /S/L/E...

There's an option in the Energy Saver PrefPane to dim LCD when running on battery.

I think the big uncertainty is the support for your Haswell Intel HD (GT1) graphics. Can't say I've seen many installations on this kind of platforms. Nevertheless, this particular Intel HD remains part of the Haswell family of IGPUs, in the same respect as HD 4200/4400/4600 (GT2), iris 5000/5100/5200 (GT3/GT3e), so there's a chance... https://en.wikipedia.org/wiki/Intel_HD_and_Iris_Graphics#Haswell You'll have to play around with the Azul frambeuffer for sure. RampageDev's guide for Haswell HD 4x00/Iris can probably help you. http://www.rampagedev.com/?page_id=200&page=7 The best way to know is to try... If that dual-core Pentium and its integrated graphics turn out problematic, you may choose to opt for a CPU upgrade towards a Haswell i3/i5/i7 with integrated HD4x00 or Iris graphics.

No, take them out, clean up connectors and plug them back.

Consult the (non-exhaustive) lists of supported/unsupported wireless cards and dongles published in our R&D->Hardware->Wifi forum subsection. If your hardware is not listed, do try and identify the chip your card or dongle is based on. Note that: Cards and dongles manufacturers may provide OS X drivers, please consult their web site before asking. Chip manufacturers may provide OS X drivers (eg: Ralink, Realtek), please consult their web site before asking. Use Google to research for potential support or drivers under OS X. If you remain without suitable answer, please post a compatibility query in the dedicated forum subsection. Please note that, for years, Intel wireless cards were not supported at all. However, recent development was done and some Intel cards are now fully supported. See here for details: https://openintelwireless.github.io https://github.com/OpenIntelWireless Thanks. OSXL Crew

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.