Hervé

AirPortBrcm4360 is indeed a PlugIn kext of IO80211Family kext (hence why you "don't have it alone"...). Now that you have identified the I/O location of your card, all you need to do is follow the in instructions detailed in the guide, keeping in mind that it may not work properly/reliably on your own laptop.

You may want to refer to this recent guide which provides details of all steps, including Clover installation...

I guess you mean DW1560, right? Like any BCM4352 cards, DW1560 does not work OOB and requires patches. Did you do that, knowing that such patches are detailed in this Wireless & BT forum section? If there's anything to provide it's: 1) a zipped copy of your Clover EFI folder (with only ACPI + kexts folders & config.plist) 2) a zipped saved output from IORegistryExplorer

read our forum rules consult our FAQ section; we created it on purpose not by mistake... we have a Search facility on the forum; please use it. Thank you.

There's probably quite a lot to do here... What "instructions" did you follow? Kexts: The add-on kexts you inject are very outdated. You need to update them to the latest versions. You should not need any of those FakePCIID kexts either, just use latest Lilu + WEG kexts. Clover config, lots to do here... Use Clover Configurator app to modify your config: 1/ ACPI section: Your Skylake laptop does not appear to have any USB2.0 controllers, as such, your renaming of EHCx devices to EH0x is irrelevant and unecessary. Do you really need all those tables in your patched folder (especially SSDT.aml which is not present in the folder!) ? Are all of these patched??? I somehow doubt it. I would have removed "Drop OEM" and added "PluginType" + "FixHeaders" 2/ Boot section: Get rid of -xcpm + kext-dev-mode=1 boot options. These are defunct and useless now. 3/ Devices section: You're not injecting any properties for your iGPU in order to adjust DVMT settings. I don't believe you'll be able to boot your system until you do that. You can grab that from any existing Skylake system guide 4/ Graphics section: No need to "Inject Intel" + inject ig-platform-id 0x191b0000 once you use latest Lilu + WEG kexts. Furthermore, these were already injected in your patched DSDT... You can look it up under DSDT device IGPU. 5/ Kernel & Kexts Patches section: Wow! Where do I start? ... Get rid of all those AppleHDA patches. Remove them. Your audio should be handled by AppleALC these days, it's a Lilu Plugin. Get rid of the IOGraphicsFamily patch. Obsolete and irrelevant now. WEG will take car of that. Get rid of the IOAHCIBlockStorage trim patch. It's likely to cause issues with your Samsung 970 NVME SSD. You should not require the AppleBacklight patch either. Do you have a BCM4352 wireless card? If you don't get rid of those AirPortBrcm4360 patches that will be irrelevant to you. You should not require the AppleAHCIPort patch. I'm doubtful you'll ever need the AppleUSBXHCIPCI patch. If you need, make sure you use the patch relevant to Mojave. 6/ SMBIOS section: Select a different SMBIOS profile, then relect MacBookPro13,1 in order to generate all the necessary values that are missing 7/ System Parameters Generate a new "Custom UUID" number 8/ RT Variables section: Generate a new ROM number (from SMBIOS) Copy MLB value displayed in "Info" black box and paste it to the MLB field And, of course, make sure you use a Clover version not older than r4911.

Since your E6420 is fitted with the Sunplus model, it should work OOB as long as your USB ports are all setup properly. In other words, follow Jake's instructions.

This is a Coffee Lake laptop and, on paper, is therefore compatible with all recent macOS versions and forthcoming Catalina. You may look at our Latitude 7490 guide for guidance as your model probably bears some similarities.

E6x20 were fitted with optional USB-internal webcams of 2 x different vendors and no kexts are neither necessary nor available for them: Sonix Technology Sunplus Innovation Technology You can identify your model in SysProfiler->USB. It was found that the Sunplus Innovation models are supported OOB whilst the Sonix models aren't supported at all. For instance: E6220: Sunplus Innovation, ven/dev id = 1bcf:2804, works OOB E6320: Sunplus Innovation, ven/dev id = 1bcf:2980, works OOB / Sonix Technology, ven/dev id = 0c45:6433, unsupported E6420: Sunplus Innovation, ven/dev id = 1bcf:2802, works OOB / Sonix Technology, ven/dev id = 0c45:6437, unsupported On the other hand, it was found that Sonix models fitted to subsequent E6x30 Series are supported. For instance: E6230: Sonix Technology, ven/dev id = 0c45:648b, works OOB

Re: sleep, try and disable Hibernation; it often causes issues. You can look this up in out FAQ section.

GTX 1070 is Pascal and, as such, unsupported in Mojave (which only supports nVidia dGPUs of Kepler generation). So, no, you cannot have graphics working on that dGPU. In previous OS X/macOs versions, Pascal dGPUs require the nVidia Web Driver because they are not natively supported. You'll have to disable the dGPU through patched SSDT in order to save battery life and run exclusively on the HD 630 iGPU of your Kaby Lake i7-7700HQ. That may also exclude external displays if the secondary output ports are physically wired to the dGPU (eg: DP and/or HDMI). Re: CPU power management, you just have to set your Clover config properly and set PluginType to true in ACPI section; that's all. Use Clover Configurator app to that effect. Re: TouchPad, you probably have an I2C model and those are not entirely supported to date. Re: DW1820A, read all our guides + topics related to this card because you have no guarantee that it'll work in your laptop. Re: Fn-Z, what's that meant to do?

Your Clover graphics settings appear quite incorrect... Where did you get them from, especially that 4K patch ( ) ?

Samsung 960 EVO is fully supported under OS X/macOS (I've got one).

You browse the input devices and right click on the listed input devices to browse their properties. You'll see the device ids in the Driver's Info tab. Can't say I understand what you intend to do once you've obtained the PCI id of your Alps I2C TouchPad though...

Yup, I guess you did not set DualLink to 1 as advised above, did you?

??? If you have Windows, browse Device Manager to identify each piece of HID/mouse/touchpad/keyboard equipment.

Yes, you can.

Let's be honest: Nick Silverstein's so-called Mojave guide for E6x20 is a heap of [censored]! Don't waste your time with it, I'd be surprised if you could even boot the installer with the stuff he posted and actually properly install Mojave. Clearly the guy collected stuff from the Net and made up a so-called guide he must have never used... I really don't recommend running Mojave on those HD3000 laptops. You only get partial/OpenGL-only graphics acceleration and it requires tricks that are getting more and more difficult to apply. Given that HD3000 graphics have always been a little buggy since El Capitan, I'll too advise to stick to High Sierra. You can refer to my updated E6220 to that effect and re-use the pack I posted. You should only have to set DualLink parameter to 1 (true) in your Clover config to get your HiRes LCD fully supported.

-> It's shown just above the lines you've highlighted! 8086:9d60 / 8086:9d61 / 8086:9d62 where 8086 = Intel's vendor id These are the various Intel I2C host controllers.

It'll be one of the device ids listed when you click on each of the 3 x I2Cx@yy devices in IOReg.

No, wont work. And, for your info, no it's not too old for Mojave (or Catalina to that effect) either... It's not the same hardware at all and that Realtek card reader remains currently unsupported. This model been mentioned/discussed several times before, please search the forum before posting.

You're expected to try the various solutions/workarounds detailed throughout this thread... Bear in mind that this card is something of a lottery and may simply not work in your Hackintosh. Should that be the conclusion, you'll just have to consider replacing your card by a properly model (eg: DW1560) or a USB adapter.

This works without Darwin injection and check? Because I had tried that exactly + the additional Darwin injection and it did not work. But I did not rename _OSI and OSID...

Join the queue and the club! -> moved to DW1820A main troubleshooting thread...

Strange, HDMI video output has always worked OOB for me. Only HDMI audio required the SNB framebuffer patch. I'm now running High Sierra and with Clover on the E6220. Maybe you should switch to that. I know it was done quite late for the version but I recently updated the guide for High Sierra too.

Since the original topic is resolved, we can close this thread. For your wireless troubles, we have plenty of DW1820A-related threads on the go, including those I linked you to in 2nd post. Regarding the brightness control keys, Jake, indeed patching through SSDTs would be the ideal route. I did try for a couple of days but it was not working as expected so, in order to post the fix, I went for the easy route and patched my extracted DSDT instead; I'll try and revisit this soon.