Hervé

I can't be 100% certain but I would expect HDMI audio to be managed through the integrated HD4600. This may require to use Rehabman's FakePCIID kexts. Your patched DSDT shows 2 x consecutive and different DSM methods in HDAU device. This is incorrect to me... Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x04) { "layout-id", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }) } } Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x04) { "layout-id", Buffer (0x04) { 0x0C, 0x00, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }) }

Check that the DSDT compiles without errors before you modify the code. Raw DSDT tables often have code that returns compilation errors from the onset. If it does compile properly, replace all references to B0D3 by HDAU, not just the device itself.

It's perfectly normal to get error messages for each kext you copy to /L/E or /S/L/E telling you that the files were improperly installed. That's because those kext files must have specific rights (=permissions) to be used. That's why you have to enter the chmod and chown commands; these repair permissions. The other touch and kextcache commands are for rebuilding the kext cache and prelinked kernel. In order to avoid the error regarding prelinked kernel, you can re-run the last 2 commands or replace: sudo kextcache -Boot -U / by sudo kextcache -system-prelinked-kernel You're obviously new to all this, so please don't hesitate to read up about hackintoshing on the many numerous sites so that you actually understand the various actions you undertake.

The tool is a Linux shell script (hence the ".sh" file extension), not an application per sé. You don't double click it, you execute the script from Terminal. You can open up Terminal, type "sudo ", then drag the ssdtPRGen.sh icon from wherever it is into the Terminal window. That should launch it. All details, direct from the creator, here: https://github.com/Piker-Alpha/ssdtPRGen.sh. 1st line under Help Information shows the command line syntax required to execute the script.

Please search the forum before posting, this model has been discussed in many threads before. In addition, we cannot guess what kexts (drivers) you used for keyboard and mouse, nor the model of wireless card you have in the E5420. As you probably know if you've done your little research, Intel wireless cards are not supported in OS X. You can look up our (non-exhaustive) list of supported/unsupported wireless cards in the R&D->Wifi forum subsection.

For HD4600 to be accelerated, you need to patch your DSDT to inject desktop id 0x0412 or inject it through Clover and use Rehabman's FakePCI kexts (FakePCIID + FakePCIID_Intel_HDMI_Audio + FakePCIID_Intel_HD_Graphics).

Here is the patched DSDT required to get the built-in LCD working on the D520: Patched_D520_DSDT.aml.zip Patches applied to the extracted raw DSDT table: 1) Fixed incorrect _HID statement for AMW0 device (not linked to LCD issue, but erroneous code that needs fixing to be able to recompile the table) incorrect code: Device (AMW0) { Mutex (WMIX, 0x01) Name (_HID, "*pnp0c14") /* incorrect statement */ Name (_UID, 0x00) fixed code: Device (AMW0) { Mutex (WMIX, 0x01) Name (_HID, "PNP0C14") /* correct statement */ Name (_UID, Zero) 2) Injected some basic GMA950 characteristics into VID device @0x00020000 (=IGPU) with a DSM method original code: Device (VID) { Name (_ADR, 0x00020000) Method (_DOS, 1, NotSerialized) { Store (Arg0, MIS4) SMI (0x9E, MIS4) } patched code: Device (VID) { Name (_ADR, 0x00020000) Method (_DSM, 4, NotSerialized) /* DSM method to inject device characteristics */ { Store (Package (0x06) { "device_type", Buffer (0x08) { "display" }, "model", Buffer (0x0D) { "Intel GMA950" }, "AAPL,slot-name", Buffer (0x09) { "Internal" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } /* end of DSM method */ Method (_DOS, 1, NotSerialized) { Store (Arg0, MIS4) SMI (0x9E, MIS4) } 3) Added a DTGP method to complete the above injection (placed between OSID and SOST methods) added code: Method (DTGP, 5, NotSerialized) { If (LEqual (Arg0, Buffer (0x10) { /* 0000 */ 0xC6, 0xB7, 0xB5, 0xA0, 0x18, 0x13, 0x1C, 0x44, /* 0008 */ 0xB0, 0xC9, 0xFE, 0x69, 0x5E, 0xAF, 0x94, 0x9B })) { If (LEqual (Arg1, One)) { If (LEqual (Arg2, Zero)) { Store (Buffer (One) { 0x03 }, Arg4) Return (One) } If (LEqual (Arg2, One)) { Return (One) } } } Store (Buffer (One) { 0x00 }, Arg4) Return (Zero) } 4) Injected built-in display characteristics with a PNLF device (placed between LID and PBTN devices) added code: Device (PNLF) { Name (_HID, EisaId ("APP0002")) Name (_CID, "backlight") Name (_UID, 0x0A) Name (_STA, 0x0B) }

Nothing wrong with those specs for Hackintoshing purposes.

Erm... with a bit of effort... DSDT for HiRes E6420 model available here: https://osxlatitude.com/index.php?/topic/7091-dell-latitude-e6420-with-i5-2410m-hd3000-and-1600x900-lcd-mavericks/ And SSDT files for i5-2520M is also available here for instance: https://osxlatitude.com/index.php?/topic/6503-dell-latitude-e6320-with-i5-2520m-hd3000-and-1366x768-lcd-mavericks/ https://osxlatitude.com/index.php?/topic/7914-dell-latitude-e6220-with-intel-i5-2520m-hd3000-and-1366x768-lcd-mavericksyosemite/ You've been on this forum long enough to be aware that there is no known issue generating CPU-specific SSDT tables using Piker Alpha's renowned tool. It's available at the end of a Google search on "Piker SSDT generator"... https://www.google.fr/#q=Piker+SSDT+generator

Sounds like the bootloader did not install properly... Try and reinstall it.

No, but you'll need to set DualLink to Yes (or 1). Can be done through DSDT patch or configured as a bootloader (Chameleon/Enoch/Clover) parameter.

From a chipset/CPU point of view, this PC will support all modern Mac OS X / OS X versions from Snow Leopard 10.6 to the latest El Capitan 10.11. As stipulated by JakeLo in the previous post, full compatibility will depend entirely on the discrete/add-on graphics card fitted to this machine. The integrated Intel GMA X4500 bears no support whatsoever in OS X. I've seen that some of those old RM One were fitted with nVidia G210; that's supported Ok. Failing that, there are plenty of cheap entry level cards that should fit in there and that are compatible with OS X. Eg: the cheap and chearful nVidia GT610. You can search the forum (and the Net), plenty of posts on that matter.

Battery information should work with Rehabman's ACPIBatteryManager v1.60.4 but may require DSDT patching. Often the case with EC... Shutdown/restart is also a typical issue sorted by DSDT patching. Rehabman's has a whole set of DSDT patches on his repository. Look it up. For the RT5370-based wireless dongle, check the Ralink/Mediatek web site. They list drivers per chip and per OS. You'll soon see if it is supported under OS X or not. Mavericks or Yosemite drivers, if they exist, should work without issues under EL Capitan. From memory, I believe it is. Check our non-exhaustive list of supported/unsupported wireless cards here.

You download EC from AppStore using a system running OS X (SL 10.6.8 being the minimum version). OS X has been free of charge since Mavericks... You'll need to be logged in AppStore using a valid Apple id; whether it's yours or your friend's is irrelevant. You'll obtain the downloaded app in the Applications folder under the name "Install OS X El Capitan". This app file can just be copied/transferred to any media, whether a disk, a USB key or even a SD card for instance. It really is just plain bog standard common sense and explained... on Apple's web site! http://www.apple.com/osx/how-to-upgrade/

Dozens of post explaining how to cancel hibernation on the forum...

Use Rehabman's ACPIBatteryManager v1.60.4.

Alternatively, you may opt for Enoch. r2795 boot El Capitan without issues.

You should not use the -x flag; that calls on the safe mode which normally prevents graphics kexts to load. You'll never obtain graphics acceleration/support in safe mode. If you manage to boot your system on occasion, why don't you create a proper vanilla USB installer instead of using that distro which clearly appears to cause issues (as they often do)?

My mistake I forgot to mention that you need to specify the correct Azul frame buffer too. In the case of a laptop, the correct AzulFB to use is usually 0x0a260006, i.e. #12. If you boot with Chameleon/Enoch, you may experiment with boot loader option IntelAzulFB=xx where xx is in the range 0 to 15. With Clover, you specify the FB with parameter ig-platform-id in hexadecimal string.

You said you were using Chameleon... Which version exactly. For El Capitan, you should use the Enoch branch because mainstream Chameleon still does not support 10.11 as far as I know. Enoch r2795 works perfectly on all my Hacks.

You use either or but not both. You should not use P and C States generation on an Ivy bridge CPU (and there was a typo for C States in your post or boot plist). Those only apply to Core2Duo and Arrandale Intel CPUs. 3rd generation Ivy bridge CPUs require 1) patched AICPUPM kext, 2) DropSSDT=Yes in the boot plist, 3) CPU-specific SSDT table generation for SpeedStep + Turbo boost.

You may experiment with alternative boot option IntelCapriFB=xx and manually try various values (in decimal, range 0 to 11 or 1 to 12, I 'can't remember) until you find the one that fits your system. Each decimal value corresponds to a particular FrameBuffer. IntelCafriFB and ig-platform-id are interchangeable parameters but the former is expressed in decimal, the latter in hexadecimal string.

If you disable nVidia discrete GPU, I guess you fallback on the integrated Intel HD GPU. i7-4710MQ is Haswell CPU with HD4600 integrated graphics, so you will gain graphics acceleration by: forcing your HD4600 id from mobile 0416 to desktop 0412 (DSDT patch or Clover overwriting for instance) use Rehabman's Fake PCI id kexts (use FakePCIID + FakePCI_Intel_HD_Graphics + FakePCI_Intel_HDMI_audio kexts)

Sounds like you're missing your LAN card, presumably due to lack of driver (kext). Are you using a LAN/Ethernet kext at all? E6230 uses same LAN card as E6220, i.e. same AppleIntelE1000e kext. Check that it's enabled in BIOS. LAN/Ethernet must be en0 with wireless anything else like en1, en2, ... for FaceTime/AppStore/etc. to work. At worst, you can use a fake Ethernet driver.

That's probably because you don't have your Ethernet/LAN card configured as 1st interface en0. You can manually remove all interfaces from the network PrefPane + all plist files from the /Library/Preferences/SystemConfiguration folder, then reboot or add the Ethernet manually again. You can search this on the forum, it's often been discussed before.