Hervé

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.

Please refer to post #1. Developments on this kext stopped several years ago.

Is LAN enabled in BIOS? If so, the guide posted here provide the required driver for the standard Intel 82579LM card of those Sandy Bridge/Ivy Bridge E6xx0 generations. You should therefore see your card in the Network PrefPane. You may also see it listed and identify it by MAC address when you type Terminal command: ifconfig But I suspect you're trying to do something unsupported on a Hackintosh more than anything else...

Please refrain from off-topic posting such matters in an unrelated thread such as an E5440 Catalina installation topic. This being said, no difference to be expected as far as performance is concerned. Upgrade or not upgrade, the matter is entirely up to you.

https://osxlatitude.com/forums/topic/11410-dell-latitude-7490-with-i7-8650u-intel-uhd-620-and-1920x1080-lcd-mojavecatalina/?do=findComment&comment=94753

You probably ought to get another card then.

Yup, we have a guide for that model. However I must remind you that DW1820A cards are based on BCM4350 chipset, not BCM94352Z; as such, you ought to verify exactly what you bought before anything else...

Updated for Mojave and Catalina.

In terms of installation, there'll be very little difference between Catalina and, say, Sierra or High Sierra; you just need to check that the minimum requirements for Catalina are met (see the Pick list on forum 1st page) and use latest Clover + updated kexts where/if applicable (eg: Lilu, WEG). Having also posted a full Catalina guide for the D630 nVidia, I invite you to refer to that, keeping in mind that, of course, you cannot use it "as is" but only after you've adjusted the pack for your own system's specs (eg: DSDT, audio, LAN, AGPM, etc.). Bear in mind that those old laptops do not meet the minimum graphics hardware requirement so full graphics acceleration is not natively and entirely supported. Tesla dGPU can only enjoy OpenGL graphics acceleration which does impact overall performance and is not 100% bug free. If you want full performance and full graphics acceleration, the buck stops at High Sierra.

You're mistaken, there is no support for DW1820. It's not compatible with OS X/macOS.

As a nice complement to our wireless inventories, there's a pretty good summary of Broadcom BCM4350, BCM4352 and BCM4360 cards here: https://khronokernel-7.gitbook.io/wireless-buyers-guide/types-of-wireless-card/m2 By far and large, cards are size 2230 and Key A/E with very limited Key E models. As a recap: Broadcom BCM4360 (14e4:43a0): Fenvi BCM94360NG Subsys id 106b:0117 BT id 05ac:828d Key A/E , size 2230 supported OOB up to Ventura Broadcom BCM943602 (14e4:43ba): Dell DW1830 BT id 05ac:6410 Key A/E, size 3030 3 x antennas Broadcom BCM94352 (14e4:43b1): Fenvi AC1200 Key A/E, size 2230 Dell DW1560 Subsys id 1028:0019 BT id 05ac:216f Key A/E, size 2230 AzureWave AW-CB162NF BT id 13d3:34xx Key E, size 2230 seems quite rare Foxconn T77H543 Lenovo 04X6020 Lite-On WCBN802B Key E, size 2230 Broadcom BCM94350: (see our dedicated guide on those) Dell DW1820A (Key A/E, size 2230) Lenovo Foxconn T77H649 (Key A/E, size 2230) Lite-On WCBN808B (Key A/E, size 2230)

USB3.0 requires that you inject Darwin as Vista/Win7 in ACPI, either through direct DSDT patch or through Clover config for instance. But it sounds like you already do. Boot Catalina with USBInjectAll only for USB. Then run Hackintool and generate the SSDT-UIAC table + USBPorts kext. You may then boot with either USBInjectAll kext + SSDT-UIAC table or USBPorts kext on its own.

Then refer to the note on post #1.

Indeed, the patch consists of adding those lines I've detailed. Can't see what difficulty you have here, I've clearly explained things in plain english. NB: There's no need to quote every message you reply to, so -please- don't! Simply use the "Reply to this topic..." box at the bottom of your page to post a reply...

Indeed, you can do it. With minimal research, you'd find that GFX0 and IGPU are interchangeable ACPI device names and that renaming GFX0 to IGPU is actually recommended for Intel iGPUs. It's one of the many ACPI patches offered by Clover Configurator... If you do not want to patch your DSDT, then lookup the alternative posted by Jake Lo; it's based on dedicated supplemental SSDT tables.