Hervé

If you run El Capitan with Clover, you can upgrade pretty much directly. If you run with Enoch, opt for Sierra (no support for easy High Sierra installation yet) and perform a fresh install over your existing El Capitan installation. You'll retain all existing files and/or applications.

It's a dial-up modem so you obviously need to configure the dial-up access as shown in post #1 (i.e. enter the number to dial and/or the relevant APN). This info depends on your service provider (Orange, SFR, etc.) and you'll find details through a Google search. You'll also find an example here. If you patch the CellPhoneHelper kext to run the card as a WWAN, you'll only need the APN.

Gents, this is a Sierra-related thread. If you wish to discuss High Sierra -and since it differs quite a lot from previous versions with regards to installation-, please create a new thread. This for the benefits of other folks who would be interested in discussing High Sierra on this laptop.

Clover makes no use of Chameleon/Enoch /Extra folder. The kexts for High Sierra are the same as for Sierra or earlier versions.

Unless you're absolutely adamant on using Clover, you may want to consider the Enoch method... https://osxlatitude.com/index.php?/topic/7387-dell-latitude-e6440-with-i5-4300m-hd4600-and-1600x900-lcd-mavericksyosemiteel-capitansierra/page-3&do=findComment&comment=67673 Remember to double check your BIOS settings https://osxlatitude.com/index.php?/topic/9247-e6440-bios-settings/

There are various ways, it really depends on the model. You can look at the card itself and check for any indication on the label or you can scrounge the Web for indications. if you cannot identify the chip, you may try to patch the kext using various module entries of the Info.plist file as the starting base. You'd then be on a trial and error mode. The Ericsson F3507G module has been discussed at great length in a separate thread. Can't remember if the card got to run as a WWAN module as just as a dial-up modem. It was reported fully working under El Capitan so you could expect it still works under Sierra and High Sierra. I've not played with 3G modules for some time now, they've become sort of obsolete with the ever widening ability to use one's smartphone as a wireless hotspot/access point.

Guys, please, ok you're new but there's an FAQ section! https://osxlatitude.com/index.php?/topic/8696-is-my-wireless-card-compatible-with-os-x/

https://osxlatitude.com/index.php?/topic/8696-is-my-wireless-card-compatible-with-os-x/ Couple of points: the wireless LED never lits on a Hackintosh mixed results with AR5B125; you should probably consider a different card

Regarding rebuilding of cache, all is explained in the FAQ section: https://osxlatitude.com/index.php?/topic/9961-how-do-i-repair-permissions-and-rebuild-the-cache-yosemite-and-later/

If that totally eluded you, note that it's the chip that matters...

Please consult the FAQ section. https://osxlatitude.com/index.php?/topic/8696-is-my-wireless-card-compatible-with-os-x/

From memory, Skylake support was only introduced in 10.11.4.

Well, now that you've entirely gotten rid of the faking kext and properly installed BCM5722D kext, try and play to the Legacy Option ROMs BIOS option again. And update BIOS to version A12 too, paying special attention to Intel vPro and non-vPro versions...

It means it's the loaded kext (driver) for your LAN card! And that happens because you inject the kext faking Broadcom BCM57765 from Clover's EFI folder. You need to understand how kext injection and kext installation (caching) works... When JakeLo tells you to get rid of that kext, you're meant to remove it. Entirely. In addition, note that you should never: 1) install a kext in multiple locations such as /S/L/E AND /L/E 2) inject a kext from Clover AND install it at the same time in /S/L/E and/or /L/E Trying to install and/or inject a kext in multiple locations will only cause trouble. So don't do it.

That's incorrect, the E6440 actually has 3 x slots for add-on mini-PCIe cards, one of them is full-size (and combo PCIe/BT/mSata). That slot sits on top of a 2nd half-size one and I'd agree that the connector is not easily visible when you remove the cover (because the full size slot is at 90° of the 2nd half-size one). Nevertheless, it's there... I personally use the slot for an mSata SSD... You should consult the E6440 maintenance manual available on Dell's web site.

SMBIOS profile can also affect HDMI output. Which profile did you configure?

No double post on the forum please... High Sierra's vanilla Capri FB shows the following layouts: 03006601 01020402 00000004 00000001 00000060 10070000 10070000 00000000 00000000 00000000 00000000 00000000 05030000 02000000 30000000 02050000 00040000 07040000 03040000 00040000 81000000 04060000 00040000 81000000 00000000 00020011 00000000 [...] 04006601 01030101 00000002 00000001 00000060 10070000 10070000 00000000 60B90400 00000000 00000000 00000000 05030000 02000000 30020000 00000000 01000000 40000000 00000000 01000000 40000000 00000000 01000000 40000000 00000000 00000000 00000000 i.e. the same as in El Capitan and Sierra for layout 01660003 and roughly the same for layout 01660004 (3rd line differs slightly). You're using the HiRes layout 01660004, so refer to the info I posted in post #32 of the Capri VGA/DP/DVI/HDMI guide. As explicitly stated in the post, that vanilla layout only supports LVDS output by default, so follow the guide.

https://osxlatitude.com/index.php?/topic/7914-dell-latitude-e6220-with-i5-2520m-hd3000-and-1366x768-lcd-mavericksyosemiteel-capitansierra/

Yes, you should be able to do it all through Clover.

You could try the SNB patch to increase HD3000 VRAM and see if it makes any difference. Bear in mind that you'll have to verify if the code remained the same in High Sierra. If the code differed, patterns should still look fairly similar so it'd be easy to derive a new patch if required.

System is trying to use the nVidia dGPU, not the Intel iGPU...

Last update: 10 Jul 2018 For those who need an extracted copy of High Sierra kernels to build their manual Chameleon/Enoch-based USB installers, here are copies of the various kernels that have come out so far. I also include copies of the patched AppleIntelCPUPowerManagement kexts that are necessary on SandyBridge/IvyBridge CPUs. Patches courtesy of Pimentel and his tools as published at IM. Vanilla kernels for Core2Duo/Core2Quad, Arrandale and Sandy/Ivy Bridge CPUs: Vanilla_kernel_10.13.zip (Darwin 17.0.0) Vanilla_kernel_10.13.1.zip (Darwin 17.2.0) Vanilla_kernel_10.13.2.zip (Darwin 17.3.0) Vanilla_kernel_10.13.3.zip (Darwin 17.4.0) Vanilla_kernel_10.13.4.zip (Darwin 17.5.0) Vanilla_kernel_10.13.5.zip (Darwin 17.6.0) Vanilla_kernel_10.13.6.zip (Darwin 17.7.0) Patched kernels for Haswell, Broadwell, Skylake CPUs: N/A (Clover and Enoch can patch the vanilla kernel on the fly) Patched AppleIntelCPUPowerManagement kexts for Sandy/Ivy Bridge CPUs: Patched_AICPUPM_10.13.zip Patched_AICPUPM_10.13.1.zip Patched_AICPUPM_10.13.2.zip Patched_AICPUPM_10.13.3.zip Patched_AICPUPM_10.13.4.zip Patched_AICPUPM_10.13.5.zip Patched_AICPUPM_10.13.6.zip NB: kernels go to /System/Library/Kernels as kernel; patched AICPUPM kext goes to /System/Library/Extensions

Doesn't this laptop have a discrete NVidia GPU too? If so, you may have to play with the Optimus settings in BIOS.

Please, pretty please... with sugar on it! https://osxlatitude.com/index.php?/topic/8696-is-my-wireless-card-compatible-with-os-x/

You can re-use what worked for Sierra.