Hervé

Tap to click isn't usually enabled by default. It can be enabled in the TrackPad PrefPane, if such PrefPane is offered to you of course. Many systems with I2C TrackPads do not get the TrackPad properly recognised as such.

Sounds more like some ACPI tuning is required around the battery and/or AC devices. Is it the pack from this guide? Skylake i5-6440HQ runs @2.60GHz with Turbo boost up to 3.50GHz, depending on core usage: 3.50GHz (1 core), 3.30GHz (2 cores), 3.10GHz (3 and 4 cores).

Please post your system's specs; ideally add them in signature as expected.

Hi and welcome. All good things come to an end and so will Hackintoshing of Intel platforms. But we still have a wee while before the end of that road...

WWAN modules are kind of deprecated nowadays with the advent of shared SmartPhones connection through either Bluetooth, HotSpot or USB cables. Granted the wireless options require the appropriate wireless card in the Hack. This being said, 4G/LTE EM7305/DW5809e 100/50Mbps module (Qualcomm MDM9215 chipset) was reported to be working Ok (see @Crashdoom's posts) so look that up in mini-PCIe format and, if you can't find that (which you most probably won't), consider an M.2 adapter for the WWAN slot. EM5809e is a 3 x antennas model and so, will perfectly be usable in the E6230 (5 x antenna cables). https://source.sierrawireless.com/devices/em-series/em7305/#sthash.toR558bX.c5oN0X4a.dpbs

No Optimus with an AMD dGPU. It's an nVidia technology.

WEG user manual clearly stipulates that for Whiskey Lake UHD620, you must fake iGPU id 0x3EA5. Why don't you try that? You could also try CFL layout 0x3EA50009.

There's a lot of mixed results on these natively unsupported Atheros cards. Some cannot work due to country code set onto the card. Wisdom would dictate to replace your card by a fully supported Broadcom model.

Re: USB type-C, I suggest you run Hackintool app to try and generate the relevant USB ports mapping for your system. The app will generate kexts and SSDT-table; you can use either or but do not mix them. Re: Trackpad, afaik that's the best you will get with an I2C device Re: Sleep, you 1st need to disable hibernation (see our FAQ section on the matter) and make sure you have injected the correct properties for your USB ports (see above about Type-C ports) Re: Fn-F11/Fn-F12 brightness keys, you may manage to enable those with our documented SSDT patching. Details have been provided in my E7270 guides so look those up. Basically, you'll need to add SSDT-XOSI.aml + SSDT-BRT6.aml to your ACPI patched tables and add BRT6 + _OSI + OSID renaming to your bootloader config,

Target macOS release: Catalina 10.15.7 Proceed with the knowledge that, HD3000 lacking compatibility with Metal, only OpenGL graphics acceleration can be achieved. It works Ok but minor graphics defects and/or slightly degraded graphics performance may be noticeable at times. It's not totally as smooth as in High Sierra though entirely usable. Due to installation problems with Catalina versions post 10.15.3, this particular installation relies on dosdude1's Catalina patcher. As such SMBIOS is back to MacBookPro8,1. Also note that, despite several efforts, I never managed to boot the Catalina USB installer, whether native or patched. As such, this installation is one made directly from Mojave (or any other previous macOS version). Working: full graphics acceleration on HD3000 graphics (after specific tuning) HDMI output DVI + DP output through port replicator E-Port K07A002 VGA output (with SNB framebuffer patch) full audio, including jack microphone input and headset output (with AppleALC kext and layout-id 12) HDMI audio (with SNB framebuffer patch) built-in Gigabit Ethernet (with AppleIntelE1000e or IntelMausiEthernet kext) DW375 bluetooth OOB (on/off supported with Broadcom Controller Transport patch injected to FakeSMC kext) native SpeedStep at CPU multipliers x8/10/12/14/16/21/22/25 (with AICPUPM patch + generated CPUPM SSDT) Turbo boost to x32 3.2GHz at Turbo multipliers x26/27/28/29/30/31/32 system sleeps Ok through lid closure, power button, Fn-F1, Apple menu->Sleep and energy savings settings with hibernation mode set to 0 (sleep to RAM) and /var/vm/sleepimage file deleted. Wakes Ok through lid opening and power button wireless & bluetooth with any compatible card battery management and monitoring (with ACPIBatteryManager kext) SD card reader (with injection of compatibility with Apple's default device 14e4:16bc) integrated webcam OOB keyboard backlight control OOB (for backlit models) left combo eSATA/USB2.0 + right USB2.0 ports OOB ExpressCard slot OOB Not Working: N/A Not tested: SmartCard reader 1) Preparation from Mojave or earlier macOS version download latest Catalina installation package off the AppStore download latest DosDude1's patcher from his repository site run the patcher and point to your downloaded Catalina installation package, then choose "Install on this machine", not "Create a bootable Installer" You will then install Catalina either on your existing disk/partition or any specific partition that you may have prepared before whilst the patcher does its stuff, update Clover to a version that fully supports Catalina. You may use version r5119 for instance: Clover_r5119.pkg.zip once Clover is updated, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip open this EFI partition and add the (unzipped) SSDT-EC table below to the EFI/Clover/ACPI/patched folder: SSDT-EC.aml.zip copy the (unzipped) Clover config below to the EFI/Clover folder, overwriting any existing one: Clover_config_E6220_MBP8,1_Cat.zip 2) Catalina installation once the 1st installation phase has completed, system will reboot boot the "macOS Install from..." temporary partition until you're left with only the final Catalina partition DosDude1's patcher does all the necessary patching so there's nothing more to do to get HD3000 supported 3) Catalina updates DosDude1's patcher only operates on Catalina full installation package. If you subsequently install Security Updates, you may not manage to reboot and re-use Catalina as you could find it difficult to repatch the updated installation. Proceed with than in mind if you must. NB: The Clover config provided in the pack contains HD3000 VRAM binary patches in disabled mode. Enable and patch HD3000 kext accordingly if you want to increase VRAM settings.

Target macOS release: Mojave 10.14.x (all versions) Proceed with the knowledge that, HD3000 lacking compatibility with Metal, only OpenGL graphics acceleration can be achieved. It works Ok but minor graphics defects and/or slightly degraded graphics performance may be noticeable at times. It's not totally as smooth as in High Sierra though entirely usable. SMBIOS switched from MacBookPro8,1 to MacBookPro9,2 in order to ensure full compatibility with Mojave. Working: full graphics acceleration on HD3000 graphics (after specific tuning) HDMI output DVI + DP output through port replicator E-Port K07A002 VGA output (with SNB framebuffer patch) full audio, including jack microphone input and headset output (with AppleALC kext and layout-id 12) HDMI audio (with SNB framebuffer patch) built-in Gigabit Ethernet (with AppleIntelE1000e or IntelMausiEthernet kext) DW375 bluetooth OOB (on/off supported with Broadcom Controller Transport patch injected to FakeSMC kext) native SpeedStep at CPU multipliers x8/10/12/14/16/21/22/25 (with AICPUPM patch + generated CPUPM SSDT) Turbo boost to x32 3.2GHz at Turbo multipliers x26/27/28/29/30/31/32 system sleeps Ok through lid closure, power button, Fn-F1, Apple menu->Sleep and energy savings settings with hibernation mode set to 0 (sleep to RAM) and /var/vm/sleepimage file deleted. Wakes Ok through lid opening and power button wireless & bluetooth with any compatible card battery management and monitoring (with ACPIBatteryManager kext) SD card reader (with injection of compatibility with Apple's default device 14e4:16bc) integrated webcam OOB keyboard backlight control OOB (for backlit models) left combo eSATA/USB2.0 + right USB2.0 ports OOB ExpressCard slot OOB Not Working: N/A Not tested: SmartCard reader 1) 10.14 USB installer creation Using a USB key of 8GB minimum, create a Mojave USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Mojave installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_8GB) The process will take several minutes. Once completed: install Clover bootloader on the USB installer with the following non-UEFI/legacy customised settings (my E6220 just would not boot from USB in UEFI mode): Install Clover in the ESP Boot Sectors -> Install boot0af in MBR Clover for BIOS (legacy) booting -> Clover EFI 64-bits SATA BIOS Drivers, 64 bit -> ApfsDriverLoader / FSInject / HFSPlus / SMCHelper BIOS Drivers, 64 bit -> GrubEXFAT / GrubNTFS you may use version r5097 attached below or any subsequent version available at Dids' Github repo: Clover_v2.5k_r5097.pkg.zip once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip open this EFI partition and transfer the files & folders from the E6220 Mojave Clover pack below to the EFI/Clover folder. Clover_Pack_E6220_Moj.zip copy Clover package + Clover Configurator app to the root of your USB installer for subsequent use later 2) Basic 10.14 installation (no HD3000 support/no graphics acceleration) boot the Mojave USB installer at the Clover main menu, select the "Install macOS Mojave" partition but don't press [ENTER] press [SPACE], select -v verbose option in the menu, then boot with the selected options proceed with installation, 1st creating & formatting the target Mojave partition through Disk Utility as/if required (GUID scheme, HFS (journaled) format) on 1st reboot, boot from the USB installer again and boot the freshly created "macOS Install from <target Mojave partition>" temporary partition repeat this reboot sequence until the temporary partition is no longer offered and only the target Mojave partition is offered, marking the effective completion of Mojave's installation 3) Post-installation basic tuning Once the target Mojave partition has booted, complete the 1st boot system setup Once at the desktop, install Clover bootloader on the Mojave partition/disk with the customised non-UEFI/legacy settings listed above or for operation in UEFI mode according to BIOS mode Once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the Mojave partition/disk Open this EFI partition and transfer the files & folders from the above E6220 Mojave Clover pack to the EFI/Clover folder You may then reboot and verify that Mojave boots directly off your disk through Clover If you wish to cache add-on kexts rather than inject them through Clover at boot time, copy them to /L/E folder and rebuild your cache through the following Terminal commands: sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo touch -f /L*/E* sudo kextcache -i / 4) Post-installation graphics tuning Fine-tuning for natively unsupported HD3000 iGPU may now take place using the files available in the package below, as derived from early findings with Mojave and the work done dosdude1 & AsiententBot at MacRumors & InsanelyMac: HD3000_10.14.zip Place an uncompressed copy of the above HD3000_10.14 folder to the root of your Mojave partition/volume Reboot in single-user mode (at Clover main menu, press [SPACE] and select -s option) At the single-user mode prompt, mount your Mojave volume: mount -uw / For Mojave 10.14.4 and later, remove GPUSupport + SkyLight + OpenGL + CoreDisplay vanilla frameworks: rm -Rf /S*/L*/PrivateFrameworks/GPUSupport.framework rm -Rf /S*/L*/PrivateFrameworks/SkyLight.framework rm -Rf /S*/L*/Frameworks/OpenGL.framework rm -Rf /S*/L*/Frameworks/CoreDisplay.framework For Mojave 10.14.4 and later, install 10.14.3's replacement frameworks: cp -Rf /HD3000_10.14/Frameworks/CoreDisplay.framework /S*/L*/Frameworks/ cp -Rf /HD3000_10.14/Frameworks/OpenGL.framework /S*/L*/Frameworks/ cp -Rf /HD3000_10.14/PrivateFrameworks/GPUSupport.framework /S*/L*/PrivateFrameworks/ cp -Rf /HD3000_10.14/PrivateFrameworks/SkyLight.framework /S*/L*/PrivateFrameworks/ Install the legacy kexts required for HD3000 support: cp -Rf /HD3000_10.14/Extensions/*.* /S*/L*/E* chmod -Rf 755 /S*/L*/E* chown -Rf 0:0 /S*/L*/E* touch -f /S*/L*/E* Quit single-user mode and resume normal macOS startup: exit macOS Mojave should then complete full boot and now run with (OpenGL-only) graphics acceleration. Note that this entire graphics-tuning process will require to be repeated after each Mojave update. 5) Mojave updates Once a Mojave update has completed its installation, the above graphics fine-tuning process must be re-applied through single-user mode. NB: The Clover config provided in the pack contains HD3000 VRAM binary patches in disabled mode. Enable and patch HD3000 kext accordingly if you want to increase VRAM settings.

So your Precision 7720 is indeed a quad core Kaby Lake model. What kind of disk is this Apacer 240GB? If SATA, all should be Ok. If NVME, it would have to be seen. Samsung NMVE SSDs such as the PM981 and PM991 are known to cause issues so I don't know if the same would apply to the PM961 but it looks like you use it for Windows, not for macOS. nVidia Quadro P4000 dGPU is Pascal, therefore unsupported since macOS Mojave. You'll need to disable (through DSDT/SSDT patching) in order to save your battery life. For the rest, all should be Ok though I can't guarantee you'll obtain 4K resolution on your built-in LCD. You'll just have to identify the exact model of SD card reader to assess compatibility. I'd say it's likely to be a Realtek PCIe device of some sort so compatibility is an open question. Will have a detailed look at your posted OC setup which is incorrect for the moment with settings applicable to Broadcom wireless or graphics among other things.

Please start by posting your system's specs; ideally in signature like most of us do.

Precision 7720 is 7th gen Kaby Lake when Precision 7x10 (eg: 7510, 7710) are 6th gen Skylake. Post your hardware specs, get to know your hardware and seek to use a setup appropriate to your own computer, not one from a different model whose name looks close to your own. https://dortania.github.io/OpenCore-Install-Guide/prerequisites.html#prerequisites

No such settings in the BIOS of the E6230. It's just Standard or Express Charge. No custom mode. For a generic/non-Dell battery, I reckon Standard is the desired mode of operation.

No such thing as "battery health" for our E6x30 Series and probably most (if not all) Hacks. It's a feature available for some Apple Macs with TB3 ports only. Don't know where you got that it was available on Hackintosh platforms. Your screenshot shows everything you can expect to see in your Energy Saver PrefPane; you won't get anything else. You should, of course, disable those 2 x options to ensure Sleep works at its best on your E6230. If you want more detailed info about your battery, go to SysInfo->Power.

@scram69 Just got an mDP-to-DVI adapter for pennies. I can confirm that mDP output works OOB and out of con2. I could therefore get built-in LCD + mDP-to-DVI + HDMI-to-DVI outputs all working together in a triple display mode with 2 x DVI monitors. You may want to consider this as an alternative to dual-DVI out of your docking station which does not appear to be achievable.

No such limitation in macOS; check your BIOS settings. Note that non-Dell batteries can also behave a little strangely. Injected kexts (from Clover or OC) do not get listed in SysInfo->Software->Extensions, only cached kexts (cached from /S/L/E or /L/E).

No kext library, no; just Google for it though you'll probably find it with a Search on the forum and in many old packs; probably is in some of the packs I posted for the old D series too. Re: BIOS settings, I just told you where you'll find the thread...

@hardevil, not that I want to come harsh but: we don't advocate nor support distros here and you appear to be using one the config you use is a pice of cr*p Please obtain a legitimate copy of macOS from Apple servers (we've got a detailed thread pinned to Our Picks section on the main forum page to that effect) and follow our existing guides for your laptop model.

No AHCI option for the Latitude D620, the disk can only be run in IDE mode. As for EDP, it was abandoned many years ago and it's no longer relevant. The bootpacks I posted cater for everything and all is fully tuned. Your issue has nothing to do with FakeSMC, which is unrelated to CPU. FakeSMC does what its name implies: it fakes the SMC of an Apple Mac. What you're experiencing is a KP on CPU power management, which is unexpected because you seem to have applied our bootpack properly and I can see in your screenshot that VoodooTSCSync kext is loaded. SpeedStep should be enabled in BIOS (or system will run like a dead dog). You could always try and add NullCPUPowerMangement kext to the Extra/Extensions folder as a temporary workaround until you suss out the problem. You'll need to re-run MyHack->myFix afterwards of course. One thing I find very odd, though, is your BIOS screenshot which shows: Dual Core Present = no. You can't run Lion without a dual core 64bit Core2Duo CPU at minimum. What CPU model did you go for when you upgraded? Merom T7400? Make sure you set your BIOS settings as per the recommendations specified in our dedicated our thread on the matter. It's available at the top of this very D6x0 forum section. On top of SpeedStep, Multi Core Support must be enabled!

Dell Latitude E7270 (PCIe v3.0 x2 M.2 slot) with Samsung 960 EVO M.2 2280 250GB NVME SSD (Gen3 x4) SSD's available performance is obviously wasted on a computer with a NVME slot limited to 2 x PCI channels...

Don't get confused with the patching of Capri layout 0x01660004; it's a single-port (LVDS/eDP) framebuffer so those laptops with HiRes screen that use it have to add ports for any HDMI/DP/DVI outputs. It's a little different for 3-ports SKL framebuffers though the principles remain the same. I don't have any mini DP adapter but if you have 2 x DVI monitors, I'd say you should be able to get them working concurrently through mDP + HDMI with specific adapters directly off the laptop; therefore no need for the docking station.

https://dortania.github.io/OpenCore-Post-Install/#how-to-follow-this-guide

Hooked my E7270 to my E-Port PR03X docking station (it's the smaller dock model with 1 x DP, 1 x DVI and 1 x VGA, I no longer have the wide PR02X model for testing, sorry). Plugged an external Dell monitor to the DVI port and immediately obtained DVI output on con2, no SKL framebuffer patching required. I did not need to close the LID to get both screens active like it is necessary with HDMI. I also tried DP output out of the E-Port DP port with DP-to-HDMI + HDMI-to-DVI coupled adapters and that also worked OOB and through con2. Given that -as is usually the case with most Dell laptops-: con0 is built-in LCD (LVDS/eDP) con1 is HDMI output con2 is DP/DVI output and that SKL FB 0x19160000 is a 3 x port layout, maybe you would need to patch the SKL framebuffer to convert it to 4 x port layout. SKL FB 0x19160000 is defined as follows: ID: 19160000, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000090F TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes) Model name: Intel HD Graphics SKL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00040000 87010000 You could experiment with the following additional properties in your bootloader config for your iGPU: framebuffer-portcount 4 NUMBER framebuffer-memorycount 4 NUMBER framebuffer-con3-enable 1 NUMBER framebuffer-con3-alldata 03060A000004000087010000 DATA I don't know what you meant by "adding an additional port/busID (0306) to both con1 (results in kernel panic) or con2 (nothing happens)", probably just an error of vocabulary because you cannot add anything to con1 or con2, you can only change their settings, whether BusID, pipe, connector-type or flags. The 1st octet of each connector lines 0000/0105/0204/0306 is the connector index, indicating con0/con1/con2/con3. You may also use and experiment with the 4 x port SKL mobile layout 0x193b0005 (I booted successfully with it): ID: 193B0005, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0023130A TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 137 MB, MAX OVERALL: 138 MB (145244160 bytes) Model name: Intel Iris Pro Graphics 580 Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 4, FBMemoryCount: 4 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000001C7 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000001C7 - ConnectorDP [3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x000001C7 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 C7010000 02040A00 00040000 C7010000 03060A00 00040000 C7010000 I've tried HDMI (directly out of the laptop) + DVI (out of the PR03X dock) and got triple display with the default SKL framebuffer 0x19160000, the only patch in place was con1 type set to HDMI (for usual HDMI audio purposes): I disconnected the HDMI monitor and connected a 2nd DVI screen to the DP port of the PR03X dock (with the DP-to-HDMI + HDMI-to-DVI coupled adapters) and both external screens were active as long as they used commonly supported resolutions (one is 1920x1080, the other 1680x1050) given that they only acted mirrored, proving that they run off that same con2 port. In that mode of operation, the Display PrefPane only showed dual, not triple displays. DVI screen appeared to take precedence and if I chose a resolution not supported by the smaller screen, it would go dark in power save mode with an (expected) "Out of range signal" error message. I was not able to get the DVI and DP screens working independently, whether through adding a 4th connector con3 to SKL framebuffer 0x19160000 or running with 4 x port SKL framebuffer 0x193b0005. You may find interesting to know that VGA worked OOB out of the PR03X dock (off con2). As a 2nd independent display alongside the built-in LCD or as a mirror of the DVI/DP output. Without the correct hardware to test further, I cannot say whether dual independent DVI is something achievable or not but it does not look that way.