Hervé

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.

The issue of the LCD connector cable may also come into account if screen resolution differ between the old and the new screen. For instance, on our old D630, the WXGA (1280x800) LCD cable differs from the WXGA+ (1440x900) one's.

The invalid signature message is normal with any patched kext. For the rest, I'd advise you to remove the IOAHCIBlockStorage patch, especially as Apple provides a dedicated command trimforce enable to support non-Apple SDD.

10.12.4 vanilla Azul FB kext is v10.24.45. If you open the binary kext file found in Contents\MacOS subfolder with, say, HexFiend, you'll find the mobile layout 0x0a260006 at offset 1380464: 0600260A 01030303 00000002 00003001 00006000 00000060 D90A0000 D90A0000 00000000 00000000 00000800 02000000 30000000 01050900 00040000 87000000 // line to patch 02040900 00040000 87000000 FF000000 01000000 40000000 0F000000 01010000 04000000 00000000 0E000000 00000000 ` To get HMDI output, you would normally patch that layout as follows: 0600260A 01030303 ........ ........ // ** unmodified ........ ........ ........ ........ // ** unmodified ........ ........ ........ ........ // ** unmodified ........ 01051200 00080000 ........ // patched line ........ ........ ........ ........ // ** unmodified ........ ........ ........ ........ // ** unmodified ........ ........ 0E000000 00000000 // ** unmodified and that's it (you leave all the ........ sequences unchanged). I attach 10.12.4's vanilla Azul FB kext v10.24.45, patched kext v10.24.45 and patched kext with version upped to v910.24.45. 'beats me if you still cannot get HDMI to work... 10.12.4_vanilla_AzulFB_v10.24.45.zip 10.12.4_patched_AzulFB_v10.24.45.zip 10.12.4_patched_AzulFB_v910.24.45.zip 2 options: you use patched version v10.24.45 to replace the vanilla version in /S/L/E. you use patched version v910.24.45 in /L/E, leaving the vanilla kext untouched in /S/L/E. With 1st option, repair permissions in /S/L/E with Terminal commands: sudo chmod -Rf 755 /S*/L*/E* sudo chown -Rf 0:0 /S*/L*/E* sudo touch -f /S*/L*/E* With 2nd option, repair permissions in /L/E with Terminal commands: sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo touch -f /L*/E* Thereafter and whatever the option you've gone for, rebuild your cache with Terminal command: sudo kextcache -Boot -U / If the kextcache command returns an error message "xxxxxxx 77", re-type the touch + kextcache commands.

https://osxlatitude.com/index.php?/topic/8723-enabling-dvidphdmi-with-intel-haswell4th-gen-hd4200440046005000-and-iris-51005200-gpu/

Erm... don't think so...

All Latitude Exx20 appear to have trouble with EFI boot. As such, stick to Legacy mode and hence my recommendation to turn to Chameleon/Enoch...

Feedback section is not for support. Moving to the correct section.

Closing this thread to avoid misplaced support discussions in this section.

Bottom is line is: do you need Clover? If you don't, you may want to consider switching to Chameleon/Enoch and run OS X trouble free, even Sierra 10.12.4.