Hervé

No, I2C is not a brand of Touchpads... https://en.wikipedia.org/wiki/I²C Look up Synaptics I2C kexts... if that exist.

No quoting to post replies please; especially if you use Google translator... Just use the Reply box at the bottom of our pages. As a newcomer, I also invite you to read our published rules so that you get familiar with them. Setup is incorrect in a few respects, most of them minor: you use old versions for some of your kexts; update them to the latest versions (eg: Whatevergreen) you've enabled _OSI to XOSI renaming but not the SSDT-XOSI table; these go together... you have some unnecessary kernel quirks enabled (eg: AppleCpuPmCfgLock which is for Sandy/Ivy Bridge) The one thing you must do is update Lilu & WhateverGreen to the latest version. At your next reboot, make sure you Reset NVRAM at the OC Picker. If you still get back screen, you could require to inject your screen's EDID. You can obtain it from Windows with some tools that you can Google for.

Anything is possible, but that does not really help, does it? Did you check the info of the TrackPad driver for Latitude 5510 in the support section of Dell's web site? Edit: Ok, here goes... PCI id 0488:121f -> It's a Synaptics Touchpad.

Afaik, if you want to run only with the nVidia dGPU, you need to disable Optimus. At least that how things worked on the old E6x20/E6x30. With Optimus disabled, the Intel iGPU was off/unused. But then, most of you guys just get a blank built-in LCD which suggests it is not wired to the dGPU.

There is absolutely no need to patch the Haswell framebuffer memory size on Haswell mobile HD4x00. The only thing that needs patching is the HDMI connector if HDMI output is to be used (or system will freeze/crash). The other thing that may need patching is the cursor memory size (to be set to 9MB) if glitches are experienced. The correct settings required to obtain graphics acceleration on Haswell laptop with HD4200/4400/4600 graphics are: 1) use of Lilu + Whetvergreen kexts (WEG normally takes care of iGPU ACPI device renaming to IGPU). 2)injection of the following properties against iGPU@2 (i.e. location PciRoot(0x0)/Pci(0x2,0x0) in Device Properties section of the bootloader config): AAPL,ig-platform-id 0600260A DATA device-id 12040000 DATA 3) SMBIOS of MacBookAir6,2 or MacBookPro11,1 This being, said, please post: 1) your full systems hardware specs. Add them in your signature like most of us do, as expected. 2) a zipped copy of the OC or Clover EFI folder you're using. 3) the version of the bootloader you're using. 4) the target macOS version you try to install/run.

Look under IGPU@2 (HD4600 iGPU) and under GFX0@1 (nVidia dGPU). Again, a built-in LCD registers as AppleBacklightDisplay. External monitors register as AppleDisplay. For iGPUs, connected screens are listed under the various connectors (=output ports) con0/con1/con2/con3 (the various FB@x). For nVidia dGPUs, connected screens are listed under the various connectors (=output ports) A/B/C/D (the various NVDA,Display-A/B/C/D@x). Good thing that the dongle was dead cheap, eh? NB: I noticed you use SMBIOS MBP11,5 rather than MBP11,3. Strange choice given that former is fitted with an AMD dGPU when latter is fitted with an nVidia Kepler dGPU. I'd have opted for the latter.

Check your IOReg; built-in LCD registers as an AppleBacklightDisplay... This kind of generic devices are not so much HDMI dummies but display simulators/virtual displays. I don't think it makes your nVidia K4100M prime GPU for the built-in LCD. To me, it's just a temporary cosmetic thingie whilst the virtual display device is connected. You just need to look at what SysInfo->GraphicsDisplays actually shows under the HD4600 iGPU: ain't that the built-in LCD??? What's listed under the nVidia dGPU ? As for display mirroring, remember that it mirrors the built-in LCD on external screens, not the other way round.

Given that the Latitude 3470 is a Skylake platform, what you probably should not do is patch the connector pipe to 0x12 and flags to 87010000 (those are typical Haswell HD4x00 properties), so I would remove the associated properties injection from your OC config, keeping only the connector type patch/property. If Webcam is USB-internal, it will either work OOB or not at all so no-one will be able to help you further on that point. Re: audio, try and experiment by adding CodecCommander kext. You can Google for it or look for it in the various packs of my various guides.

IOReg shows external monitor connected to con1 (as is the norm), not con2, and the connector-type is already set to HDMI type 00080000. Therefore all looks Ok on that front.

I've compared your DSDT with that of my Skylake E7270 and it's the same ACPI code throughout for AC and BATx devices. Try and adjust your OC config as follows: disable GPRW renaming disable SSDT-GPRW.aml

So you know what to do then...

What's the exact model? It could be one of those unsupported ones. Also try the NVMEFix kext, you never know. https://dortania.github.io/Anti-Hackintosh-Buyers-Guide/Storage.html

SSDT-XOSI is unrelated; keep it. That table's purpose is to set OSYS to the highest possible Windows version equivalent and ensure things such as USB3 is enabled on older systems or that brightness keys will work.

Can you extract your DSDT with maciASL and post it? You run latest BIOS 1.16.1 of March 2021 when Jake ran with BIOS 1.15.0 when he posted his guide back in February. Out of interest, I'd try to downgrade BIOS, you never know... But, Jake may tune in on the matter and he'll be able to assist you a lot better given that I've no such laptop whilst he does.

Ok, so Comet Lake platform with Intel UHD Graphics for 10th gen CPUs, i.e. UHD 620, not HD 520 which is a Skylake iGPU. Of course, you need to enable WhateverGreen to obtain graphics acceleration; don't disable it. Which version of OC are you using? Remove/disable XhciPortLimit quirk, that'll cause problems. I recommend you follow the Dortania's guidance for CML/UHD620 laptops as you're clearly missing some essential settings in your config. For instance, if you do inject the correct graphics framebuffer layout, you're not injecting fake id 0x3E9B as is expected. https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/coffee-lake-plus.html

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.