Hervé

@JmW, your question re: wifi is as good as going to the Doctor and say no more than "it hurts" without any additional details... Please consult our FAQ section, follow the provided guidance and exert good general common sense.

Did you try and disable hibernation? See our FAQ section where it's described.

No bootable device, hmm... Make sure your boot disk is physically properly set in its place and has not moved. This error message is typical of situations where SATA connector is not fully fitted in the slot. As for the random wake, did you check your Energy Saver settings? You may have Power Nap or Wake on network access options activated...

Generate P States and Generate C States are settings applicable to old C2D/C2Q/1st gen Core platforms only. They do not apply to Sandy Bridge platforms and beyond, including Broadwell platforms such as yours. In fact, if you call on these, you may find your CPU switching only between that low frequency you reported and the highest nominal frequency; all without Turbo boost and intermediate frequencies, which means CPU inefficiency and hammered performance. In order to enjoy proper CPU power management on your Broadwell Latitude laptops: either you apply/select/set/tick PluginType option in Clover ACPI section to which you may add Plugin Type=1. or you drop SSDT tables with ids CpuPm + Cpu0Ist in Clover ACPI section and generate your CPU-specific power management SSDT with Pike R Alpha's good old SSDT generator script; you'll then place the generated SSDT table in E/C/ACPI/patched folder. E7250/E7450 are fitted with low-power CPUs such as i5-5300U/i7-5600U and you should expect idle frequencies of 800MHz. If Intel datasheets do indeed indicate LFM frequencies as low as 500 or 600MHz, I'm pretty sure these are reserved for the programmable TDP-down/7.5W reduced power mode. In fact, if you download and install Pike R Alpha's complete tool and consult the data files for the Broadwell CPUs, you'll see this: # Broadwell mobile processor data. # gMobileBroadwellCPUList=( # # 5th generation Intel® Core™ i7 Processors (socket FCBGA1164) # i7-5950HQ,47,500,2900,3800,4,8 i7-5850HQ,47,500,2700,3600,4,8 i7-5750HQ,47,500,2500,3400,4,8 i7-5700HQ,47,500,2700,3500,4,8 # # 5th generation Intel® Core™ i7 Processors (socket FCBGA1168) # i7-5650U,15,800,2200,3100,2,4 i7-5600U,15,800,2600,3200,2,4 i7-5557U,28,800,3100,3400,2,4 i7-5550U,15,800,2000,3000,2,4 i7-5500U,15,800,2400,3000,2,4 # # 5th generation Intel® Core™ i5 Processors (socket FCBGA1168) # i5-5350U,15,800,1800,2900,4,4 i5-5300U,15,800,2300,2900,2,4 i5-5287U,28,800,2900,2900,2,4 i5-5257U,28,800,2700,3100,2,4 i5-5250U,15,800,1600,2700,2,4 i5-5200U,15,800,2200,2700,2,4 # # 5th generation Intel® Core™ i5 Processors (socket FCBGA1364) # i5-5350H,47,800,3100,3500,2,4 # # 5th generation Intel® Core™ i3 Processors (socket FCBGA1168) # i3-5157U,28,500,2500,2500,2,4 i3-5020U,15,500,2200,2200,2,4 i3-5015U,15,500,2100,2100,2,4 i3-5010U,15,500,2100,2100,2,4 i3-5005U,15,500,2000,2000,2,4 which lists CPU model, TDP, LFM, HFM, max Turbo, cores and threads. LFM frequencies of those CPUs fitted to our Latitude E7250/E7450 are therefore set at 800MHz, even though you may not encounter them much due to sustained minimum load under macOS. In the same respect, HD5500 iGPU of those processors typically clocks between 300 and 900/950Mhz. With regards to iGPU throttling, bear in mind that your Hackintoshes are not fitted with the same CPUs and iGPUs as those real Macs we fake them to be. For instance former are fitted with HD5500 GT2 iGPUs when latter are fitted with HD6000/Iris 6100 GT3 iGPUs. Not entirely the same thing...

Only the USBPorts kext, CPU-specific SSDT and patched DSDT can really be re-generated. Also think of checking your BIOS settings against those that are recommended:

It's been stated for years: don't use/re-use the DSDT of a different computer model. Even though E6220 and E6320 are evidently very close, I cannot vouch that the patched DSDT of the E6220 applies to the E6320. I strongly recommend you seek the E6320 patched DSDT instead.

Are the specs of your E6320 identical to those stated in my guide? Same CPU for instance? If it's different, you cannot re-use the provided CPU power management SSDT but generate your own as explicitly stated. You'll also need to regenerate the USBPorts kext with Hackintool app since your E6320 probably has a different USB ports arrangement.

You've not entirely followed the instructions I provided above.

Make sure you use the same Clover version as your USB installer + same EFI folder...

DW1510 is now an old dual-band 802.a/b/g/n half mini-PCIe. It was last natively supported in Mojave 10.14 and dropped in Catalina with which it's only supported with those specific actions described in out wireless cards inventory thread where you'll also find references of better 802.11ac half mini-PCIe cards based on BCM4352 or BCM4360 chipsets. Those are also available at very reasonable cost. If Wikidevi died a few months ago, you can still look up specifications of wireless cards on alternative wikis if you Google a little... http://en.techinfodepot.shoutwiki.com/wiki/Dell_Wireless_1510_(DW1510) DW1510 is stated at 300Mbps card, i.e. most people will only get it to operate at 150Mbps max in any given direction, not at 300Mbps per sé. In practice, that means real-life rates around 100-120Mbps on 5GHz networks and around 70-100Mbps on 2.4GHz depending on surrounding environment. Here's what I get out of my own DW1510 card on a 5GHz and a 2.4GHz network at approximately 10m from my Box (300Mbps Internet access). In comparison, I get 300Mbps both ways out of my Apple 802.11ac BCM94360CD in my Latitude E6230. Generally speaking (and that should go without saying), wireless cards are of course compatible with any PC, laptop or desktop, unless computer BIOS applies a whitelist (eg: some HP or Lenovo laptops). Rest assured DW1510 is available for peanuts for a reason: it's old and, today, somehow limited performance-wise, though still entirely suitable to many people...

I believe there is no need to repeat things unnecessarily...

I assume that by "FakeSMC files", you actually meant FakeSMC's plugin kexts which are mandatory for HWMonitor app to display information. https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/ Can't see why you'd have issues with FakeSMC unless you're using it alongside similar kexts such as VirtualSMC... As usual, if you want proper assistance, please post a zipped copy of your Clover EFI or your debug files. By now, you should know the drill... Consult our FAQ section if in doubts. There are alternatives apps of course; iStat Menus for instance. https://bjango.com/mac/istatmenus/

You 1st need to install Clover on your target disk/partition. Your screenshots suggest you did not do that. If that's the case, copying the EFI folder from a provided package will be of very little use...

Ok, then layout 0x01660003 that you're using is indeed the correct one. The being said, a few things to be said about your Clover config. It's probably an old one you picked up somewhere and it needs some adjustment. Proceed as described below, using Clover Configurator app: ACPI section: Add patches that rename legacy USB controllers from EHC1/EHC2 to EH01/EH02 Select FixDarwin7 fix Remove Drop OEM + Generate P States + Generate C States (these are for C2D/C2Q/1st gen Core platforms) Apply Drop tables for SSDT with id CpuPm and Cpu0Ist Select FixHeaders Boot section: Remove boot parameter kext-dev-mode=1 (it was only for Yosemite and has long been obsolete and useless) Add boot parameter nv_disable=1 Devices section: Remove all those zero/null values entered in the 8 x Faking ID fields; leave them blank Remove those nVidia properties in the Add Properties part Graphics section: Remove NVCAP value (it's for nVidia GPUs) Remove Display-cfg value (I don't believe this to be required at all) Remove ig-platform-id value (should be taken care of by Lilu + WEG) Kernel and kext Patches section: Add AppleRTC patch Once you've finished adjusting your Clover config: generate your CPU-specific power management SSDT with Pike R Alpha's well-known generator script/tool (you can Google for it) and copy it to ACPI/patched folder of your Clover EFI. remove AppleBacklightFixup kext. Not required with Lilu + WEG check that you use latest versions of your add-on kexts, especially Lilu + WEG; update as/if required

We do not support distros, nor do we advocate them. You will not find much discussions about distros on this forum for sure. I totally refute that claim of yours in that respect. Distros are a pain in the backside, you don't know what's been added or removed in them. They're trouble, they're bad news, we always say to stay away from them. You've been seeking assistance and getting people to try and help you for days without the courtesy to mention that key fact until now. This is quite disrespectful to be honest. You issues clearly result from that very fact: you're using a distro. Use a standard vanilla installation and you'll find things will work much better. You're totally free to use a distro, that's your own respectable choice. Just don't come here afterwards when you find it does not work. Niresh have their own forum, go there.

What is the screen resolution?

Guys, seriously, now we learn that all these installations attempts related to a distro !!!

If you use Dr Hurt's version available here, it's clearly indicated that there is limited support for Alps v7/v8 versions and that there are issues on wake. You may want to consider an external mouse...

You're using a recovery image; that's not the recommended way to install macOS. Download a proper installation package and follow our installation guides for that model. In anticipation to eventual questions on the download matter, please refer to our Pick-list. We have no OpenCore-based guides so your original post is quite misleading... As for the Ethernet, I believe you're making erroneous conclusions. You say you don't know what the NIC is, yet I gave you the model specifics. Since you appear to have Windows, you can easily confirm the model yourself.

Doesn't mean much; please provide details...

Sorry, yes, that's what I meant.

Looking at your posted Clover config + posted EFI folder, I believe I see several issues: 1) posted Clover config: you stated you have an Intel i7-8750H CPU, i.e. a mobile processor; I therefore assume your computer is a laptop. If this were to be confirmed, I would ask why you use the SMBIOS of an iMac, an incomplete one to that effect? SMBIOS of a MacBookPro15,x would certainly be more suitable and appropriate. your config only shows you're injecting layout-id 0x039B0000 for your UHD 630 iGPU; I'm pretty sure this is incorrect and that you need more, especially on the DVMT front. I'll look that up to make some suggestion. 2) posted EFI folder: it's unclear as to which config you use but the file "config.plist" appears to carry the same SMBIOS mistake as mentioned above. one of the configs showed many properties being injected for your UHD 630 iGPU and I would need to look into their suitability. I would suggest you try them out with the correct SMBIOS. If you had looked at CloverConfigurator's own recommendation re: graphics, you may have noticed this: I would suggest you try those recommended settings for Coffee Lake UHD graphics: injection of ig-plaform-id 0x3E9B0006 + MBP15,1 SMBIOS. You may also want to read this though it's kinda heavy stuff...

Please refrain from quoting every message you reply to; it's unnecessary. Just use the Reply box at the bottom of your pages, that'll suffice.

Of course faking the Intel iGPU id with that of a non-exiting one removes the error; no graphics driver loads in that case, hence the minimal VRAM. You have not fully understood how things worked. When you stop faking that invalid id, macOS tries to load CFL graphics drivers. What you need to ensure is that your iGPU properties are Ok for the OS to properly boot. Look up existing guides/threads pertaining to CFL UHD 630 and adjust your Clover properties injection accordingly. Of course and as suggested by Jake Lo, check your BIOS settings too.

Do you actually understand that by faking id 0x12345678 for your iGPU, you're actually telling the OS your have a non-existing Intel iGPU? This makes the OS boot in VESA (un-accelerated/default/basic graphics) mode. The error message you see in the boot log is not necessarily an issue. Make sure you actually inject the correct properties for your CFL UHD 630 iGPU. The info is readily available.