Hervé

Then inject Intel graphics + layout id 01660003 in Clover and you'll have full graphics acceleration and max resolution on screen.

AR5B95 is compatible but not the best choice if you want AirDrop and Handoff. Opting for a more modern combo BT4.0+wireless card, especially with Sierra, such as those based on BCM4360 or BCM4352 chips would require less patching and be a much better choice (AR5B195 and similar are AR5B95+combo Bluetooth 3.0). One of the best possible choices is to go for an Apple card such as the BCM94360CD with a mini-PCIe adapter board. They work OOB and support all those features with 802.11ac gigabit wireless connectivity. https://osxlatitude.com/index.php?/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/ https://osxlatitude.com/index.php?/topic/1916-the-perfect-mini-pcie-wifi-and-bluetooth-combo-card-for-notebooks/ https://osxlatitude.com/index.php?/topic/7554-broadcom-bcm4360cd-80211-ac-wifi-and-bluetooth-combo-card/

Seems the patch is not applied. Post a zipped copy of your Clover config.plist file.

Unless you've configured the kexts patches through Clover, you'll have to repatch your Azul frambefuffer kext + AppleHDA kext after each update. The patches are readily available in various E6440, E6540 or E7440 and Haswell iGPU threads & guides posted on the forum.

Or Google for it...

DVD player needs full graphics acceleration to run, so no hope in your case. VGA and Monitor PrefPane are probably linked to absence of framebuffer. Don't expect any fixes here... For wireless, please read the FAQ section. As for Sleep not working when you close the lid, it can depend a several things: defective or disconnected sensor inside the laptop, absence of Sleep altogether (need CPU power management as a pre-requisite), need for DSDT/ACPI adjustments, etc. Check that Sleep works through Apple menu and/or Fn-F1 or Fn-Esc to begin with. You also need to be aware that even if you got Sleep to work, you may encounter graphics nastiness (garbled screen and subsequent need to reboot) on wake. That's what happens on old GMA-based systems that run 64bit versions of OS X without full graphics acceleration. Remember that this will never be a good Hackintosh...

Then I suspect you might have a dying HDD...

Then you're either using the wrong pack or the patched DSDT (or any other patched table) is incorrect. I suggest you post your extracted raw table to get it patched properly. In case you've not done so already, update your BIOS to latest version.

Try & grab the BCM5722D v2.3.6 off the D630 Mav/Yos/EC/Sie packs available here. But 1st of all, check your BIOS settings because it looks like Ethernet is disabled in BIOS...

I see reports of errors on your NTFS partition so you may want to watch out for HDD errors. Then, there is clearly a timeout with your Bluetooth device. Maybe you need to repatch a kext or re-apply a firmware patch. Difficult to say more until you advise on the hardware model....

Please refrain from multiple posting on the LAN matter (and, as a general rule, any other matter). You've posted about it 4 or 5 times in the last few hours and we're not going to reply to each post.

Guys, you can maybe try the BCM5722D v2.3.6 found in the D630 Sierra pack posted here. No guarantee it'll work, but worth a shot if nothing else works... The PCI devices would be better listed with Terminal command lspci -nn in order to display PCI ids alongside device description. This being said, BCM5761 GigEthernet card appears to bear id 14e4:1681 so it's easy to check if covered by suggested kext version. Here's the list of cards supported by the kext: <string>pci14e4,165a</string> <string>pci14e4,167a</string> <string>pci14e4,1672</string> <string>pci14e4,167b</string> <string>pci14e4,1673</string> <string>pci14e4,169b</string> <string>pci14e4,1693</string> <string>pci14e4,1712</string> <string>pci14e4,1713</string> <string>pci14e4,1691</string> <string>pci14e4,1698</string> <string>pci14e4,16b5</string> <string>pci14e4,16b1</string> <string>pci14e4,1692</string> <string>pci14e4,1600</string> <string>pci14e4,1681</string> <string>pci14e4,1680</string> Then, there is the matter of a BIOS ROM parameter of some sort that can interfere with Ethernet. It was mentioned some time ago in discussions with JakeLo. Need to dig that out. This ROM parameter can be enabled or disabled to check subsequent Ethernet behaviour... Edit: found it; it's Legacy Option ROMs option. On some Dell laptops, it needs to be disabled to bring Ethernet back to life.

What's the PCI id of the Ethernet card?

So you know what to look for now... Hint: E6410 published packs maybe.

You'll have to tell us what audio codec that E5410 has. There's a good chance it'll be listed in the BIOS settings. If not, look on Dell's web site. Failing that, try the usual alternative, i.e. VoodooHDA. Re: battery management, I guess you can try and grab the battery kext I posted in my D630 Mavericks pack or E6220/E6440 Mavericks/Yosemite guides.

I'm a little wary about a "method from youtube and not from this side"... Then BIOS is A03, i.e. ancient. I'd start by updating to the latest version.

Diificult to help without more info... Method used? Bootpack used? Screen resolution? If screen res is 1366x768, you can follow my E6220 guide and re-use the SSDT for i5-2520M. I'd advise to retrieve the E6420 DSDT from a different guide like JakeLo's Latitude/Inspiron/Precision general one.

Erm... where do you get that from? Really? Did you read the comments?

None normally expected. Follow the usual/regular advise: if you do update, take a full backup or image of your current installation in case things do go wrong afterwards.

Absolutely no idea. I gave you everything one would normally require.

Moving to Support section. Please try and post in the relevant sections in the future... Don't use distros, it's not reliable since you cannot know what's inside and how they're made. Only use vanilla installations. You can refer to my E6440 guides since both model share the same hardware specs. It does not matter that you have a different CPU (but don't ignore the related warning obviously).

Unless you really need Clover, I'd advise you run with Chameleon/Enoch and follow the guides I posted here.

At least, your cache did properly rebuild on the 2nd attempt.

If/when the kextcache command returns such an error "xxxxxxxx 77", repeat the touch + kextcache commands. You can ignore any other error but 77.

Don't get confused by the BIOS info or Dell's own documentation that stipulate ALC3226. In OS X, what counts is the reported Codec and it is 10EC:0292, i.e. ALC292.