Hervé

Please post your debug files. Consult FAQ section if you need assistance on the matter.

1) it's a DW1820A 2) I don't know where you read it was Plug & Play, but you sure got that totally wrong 3) please consult our R&D->Wireless section on the matter but opting for a DW1820A before checking could prove a poor choice/decision...

On paper, this computer meets the minimum specs to run any recent macOS flavour. For the rest, you'll have to make up the list of hardware components, ideally with their PCI ids. I'm talking stuff such as LAN, audio, card reader, webcam, etc. This is mandatory to obtain adequate assistance. You may collect this information from Windows Device Manager (PCI ids are available in driver info tabs) or through dedicated apps that lookup the components of computers. Obviously, Lenovo web site would be the 1st place to look things up too but manufacturers don't always provide full details of the hardware components.

Use the recommended version available here, not beta version R6B6. The final version certainly worked perfectly when used in the (non-touch) E7250 I had a few months ago; it's included in the bootpacks I posted in my guides.

FAQ section -> debugging.

Please consult the FAQ section and search the forum (where this model has been discussed at length) or others. All those questions have existing answers and everyone is expected to do basic homework. Haswell platforms are supported in all OS X/macOS versions since ML 10.8.5. FAQ Guides for Dell E5xxx support OS X/macOS info etc. etc. NB: No double post please...

Post split to its own thread... You should find all you need here, especially on last page.

Obviously you replace the files you have in your Clover EFI folder by those provided in the proven bootpack.

It is.

There can be no comparison between CPU utilisation under windows and that under macOS. Both OS operate differently and latter is more power hungry than the former due to reliance on graphics. So yes, battery life is very often reduced under macOS in comparison to Windows.

I've no USB Type-C flash drive or no adapter to test a Type A USB key directly off the USB Type-C port.

Because, on any given laptop: dGPU is located @1 (IO address 0x00010000) iGPU is located @2 (IO address 0x00020000) in the same respect that HDEF audio device is always located @1b or XHC USB3 controller device is located @14. That's standard across the board.

Wifi support depends entirely on the card you have; support is not generic and, over the years, gradually reduced to some specific Broadcom chips. Transition from mini-PCIe to M.2 format reduced choice even further. Check our FAQ section and inventories on the matter.

Kexts folder is a bit of a mess: Lilu + WEG but alongside, there is FakePCIID_Intel_HD_Graphics + AppleBacklightFixup AirportBrcmFixup alongside AtherosWiFiInjector.kext + IOath3kfrmwr.kext USBInjectAll + USBPorts_E7440 and SSDT-UIAC-E7440.aml in ACPI/patched folder That ain't gonna work properly... Clover config: ACPI patch to rename ECDV to EC alongside a patched table SSDT-EC in ACPI/patched folder Drop of CpuPm + Cpu0Ist SSDT tables without a generated CPUPM SSDT whilst PluginType is enabled Methink things need to be cleaned up and the packs available in existing guides used... And, of course, installing the debug tool would require to unlock the protected file system...

Darwin 17.7, so High Sierra it would appear... I've split OP's threads into 3 x separate Mojave/El Capitan/High Sierra threads for clarity's sake; especially as everything had just been added to another member's thread related to HD520 graphics acceleration under High Sierra on that E7270 platform.

All you need to to to upgrade from Mojave to Catalina is: add the necessary Embedded Controller ACPI device renaming update Clover to a version that supports Catalina of not already done The kexts you used for Mojave should do for Catalina, you may only need to update those such as Lilu & Plugins (WEG, AppleALC); the rest should be Ok. Once you've initiated the upgrade to Catalina, you have to complete it (starting at booting temporary partition "install Catalina from...") and that takes a few reboots. No way to revert to Mojave... If you've done something differently, you 'll have to be specific about it. Right now, we've no idea about what you've done and what you're using.

By now, you should know the drill... If you want assistance, please provide the supporting material... FAQ section to be consulted on that matter if necessary.

Patched DSDT is irrelevant here (it's only provided to support Fn-F11/Fn-F12 brightness control). I had no patched DSDT when I 1st tested the WD15 Dock. I've no way to say whether your USB Type-C works or not.

It's not just SNB graphics kexts from High Sierra, it also involves replacing several graphics related frameworks and repairing permissions. The trouble is that it's not sustainable to updates and needs to be redone after each update, pending which you may encounter trouble booting or actually using the computer (like not being able to open up a Finder window or executing programs). Given that it also remains buggy since there is no Metal graphics acceleration, it's not worth the hassle in my opinion.

Please, no "bro" here, it's considered disrespectful. No support for distros here either so if that's the path you choose, I invite you to seek assistance elsewhere (the one you mentioned has its own forum after all). Before you even contemplate engaging on this Hackintosh road, please note that: GeForce G610M is based on Fermi GF119 and would not be properly supported beyond El Capitan (if supported at all given you're using a dual-GPU laptop and that Optimus is not supported on Hackintosh) HD3000 graphics has no support beyond High Sierra 10.13; it's not compatible with Metal and was therefore dropped in Mojave (there are tricks to run HD3000 in Mojave/Catalina with OpenGL graphics acceleration only but it's increasingly difficult and complex to support and not bug free; I discourage it). So, if you want to run macOS, I recommend that you: proceed with a vanilla-only installation call on a dedicated SSDT table to disable your nVidia dGPU and save battery stick to High Sierra, it'll run perfectly or so, HD3000 being a little buggy at times in macOS Good luck.

Standard/default VRAM settings for HD3000 are: 2GB RAM -> 256MB VRAM 4GB RAM -> 384MB VRAM 8GB RAM -> 512MB VRAM That's Apple's own settings, defined in the SNB framebuffer. As such, what you obtain is perfectly normal. Any changes from those settings result from framebuffer patching and I've included those (in disabled mode) in the Clover config files I posted in my guide, at least the latest ones, probably not the earliest ones. Details for HD3000 VRAM increase are available in many Mac and Hackintosh forums. Here for instance.

I can certainly use external USB HDD/USB keys through the WD15 Dock connected to the USB Type-C of my 7490.

CMD+Shift+3 for full screenshot CMD+Shift+4 for selected window screenshot -> Look up your Preference Panels...

It does not really matter you got the old kext from a different thread, it's the exact same one (HiSie's v328)... Allow me to correct your statement about the patch. The Clover binary patch applicable to Catalina simply is: Kext: AppleAHCIPort Find: 40600200 Replace: 00000000 The other 2 x patches you referred to (and those were mentioned for Mojave) appear totally irrelevant because the target (i.e. Find) binary code (hex strings) does not exist in the vanilla kext. At least not in 10.15.2.'s... By the way, Clover Configurator includes a Base64 to Hex converter.

I very much doubt the patched DSDT of the E6230 has anything to do with your issue... Your patched AppleAHCIPort kext is of High Sierra (beta?) origin (v328), re-versioned to v999. It probably came from here or here and details of the alternative to reverting kext (i.e. binary patch) were posted here. Given the very origin of the kext, I'm not too surprised it now causes KP in Catalina. What you ought to do is find the alternative to replacing/superseding Catalina's vanilla AppleAHCIPort kext by a now inappropriate older version and actually apply the relevant binary patch to Catalina's own kext. Once you find details of the patch, simply apply them to the kext cache through Clover's built-in on-the-fly patching facility. I suggest you start here and/or Google for "Hotplug Catalina" / "Hotswap Catalina"... More suitable than kext superseding here. As usual, the key is to know what you're doing and why you're doing it.