Hervé

Nothing strange at all... Kepler NVIDIA GT730 supports 4K completely natively in macOS. Nothing to do but plug the 4K monitor and off you go. I've got the Asus GT730-2GD5-BRK model (low-profile version with HDMI 1.4/DVI-D/VGA ports) in my old C2D desktop and obtain 4K@30Hz out of HDMI OOB. With the Intel Skylake iGPU, you usually need to set DVMT pre-allocated memory to at least 64MB, if it ain't 96MB. That's certainly what we have to do on our Skylake E7x70 laptops to gain 4K output out of the mobile HD520/HD530 iGPU over mDP/HDMI. 4K@60Hz is only supported out of mDP/DP with 4K@30Hz only out of HDMI 1.4. I would assume the same to apply to desktop Skylake graphics. Check your BIOS settings for any option/parameter allowing to adjust DVMT and, if there's nothing at all, give a shot at the process detailed in our FAQ section by @Jake Lo (based on Firewolf's work) to try and identify the default amount of DVMT pre-allocated memory and adjust it through Grub shell mod.

I'm not certain you need to change pipe value or inject flags for your iGPU connectors. Injecting/faking the iGPU's own device id is, of course, of no use. I also believe injecting enable-hdmi20 to be inapplicable on platforms that only support HDMI 1.4... All I do on my Skylake i7-6600U/HD520 E7270 is inject HDMI type (00080000) to con1 and use boot arg igfxonln=1. I have adjusted DVMT pre-allocated memory through Grub shell-based BIOS data mod. Try that and see if these settings makes a difference. I detailed my observed behaviour with HDMI in my E7270 guides. I believe all you need to inject is: AAPL,ig-platform-id 00001619 DATA AAPL,slot-name Built-in STRING framebuffer-patch-enable 1 NUMBER framebuffer-fbmem 00009000 DATA -> not needed if you change DVMT pre-alloc mem to 96MB through Grubshell framebuffer-stolenmem 00003001 DATA -> not needed if you change DVMT pre-alloc mem to 96MB through Grubshell framebuffer-con1-enable 1 NUMBER framebuffer-con1-type 00080000 DATA

USB-based Atmel Touchscreen fully operational in Big Sur and Monterey once the USB HID Fix kext patch is added to the Clover config.

Have you considered opting for a more traditional set of ACPI patched tables such as those provided in the Dortania documentation rather than your single unified SSDT which may not be entirely adequate? Also bear in mind that you may have to inject power settings for your USB controller/ports to obtain proper sleep. I'm thinking about tables such as this one: SSDT-XHC.aml.zip You may also find it useful to check your power assertions which may provide hints as to why sleep isn't working. Use the following Terminal commands: pmset -g assertions pmset -g assertionslogs

Good, well done! I don't think you need the SSDT-PNLF table or -igfxmpc boot arg though, given that these target the iGPU...

According to Dell, no such thing as a Latitude E7275 but a Latitude 12 7275 (tablet/2-in1 model) so thread renamed and moved to the relevant section. Your Clover config needs some serious clean-up, it's full of unsuitable stuff. For audio/LAN/SD card reader, it all seems to be Realtek but you'll have to provide the exact model of hardware components (or PCI ids for subsequent identification).

GTX 970M is a Maxwell dGPU. As such, it is not natively supported by macOS but it should be once you install the nVidia Web Driver for your given High Sierra build. Cf. my initial answer above. All versions of the driver for High Sierra are available here. No property injection required. If you enable Optimus in BIOS, you'll only be able to run macOS on the Intel HD530 iGPU and you'll need to disable the dGPU through DSDT/SSDT patching to prevent your battery from being drained by the dGPU. Optimus technology is not supported by OS X/macOS so you cannot run dual GPUs on a Hackintosh. It's basically as follows: Optimus disabled in BIOS -> nVidia dGPU only Optimus enabled in BIOS -> Intel iGPU only with nVidia dGPU disabled by ACPI patches Of course, if you opt for the nVidia dGPU (i.e. Optimus disabled), you're stuck at High Sierra since there are no Web Drivers for Mojave and later. See here for our most recent summary on such matters. Like any Intel iGPUs, HD530 is not really suitable for games, only so in limited ways. You can look this up yourself on the Web.

See our FAQ section. There should also be no need for HibernationFixup kext. Probably the same for RestrictEvents kext.

Difficult to be specific but possibly a Bluetooth keyboard and/or mouse left switched on when laptop goes to sleep. Post your sleep/hibernation settings + bootloader's zipped EFI.

What do you mean?

With Optimus disabled, you'll only get the nVidia dGPU activated whereas with Optimus enabled, you'll have Intel iGPU + nVidia dGPU activated (dual GPU but unsupported on Hackintosh). So, if you want to try and run on the nVidia dGPU in High Sierra you should: disable Optimus in BIOS refrain from injecting any properties for your nVidia dGPU install the nVidia Web Driver

See here: https://osxlatitude.com/forums/topic/15661-acpi-patch-for-brightness-keys-on-dell-laptops/#comment-108703 The boot packs posted in my E6230 guide do cater for this.

I invite you to consult the wireless cards inventories we publish in our Hardware->Wifi section since 2013. Had you done so, you'd have seen your Broadcom card is totally unsupported and has to be replaced.

HD3000 being the poor iGPU that it is, you'd be struggling with Big Sur and even more so with Monterey. As Jake stated, High Sierra is last macOS version to support HD3000 graphics. You can get it supported in Mojave with a patch fairly simple to install. It gets far more complicated with Catalina (see my Latitude E6220 guides). Beyond Catalina, i.e. Big Sur and Monterey, you're likely to meet further difficulties and instability so those are really not recommended on an old HD3000 laptop.

You can either start afresh with a default OC 0.7.6 config file that you'll tune to your system according to your existing setup or update according to the changes that are required to make from one version to the other. https://www.insanelymac.com/forum/782-opencore-releases/

If you use an Intel wireless card, why do you inject properties for Broadcom DW1820A in your OC config? You should remove that.

Try one of those USB power settings add-on SSDTs like the one included in the pack I posted in my E7270 guides.

It's not a Hackintosh-related issue then. Did you check any eventual USB power settings in BIOS? What about the WD disk's own documentation?

Meaning, in your bootloader config, inject the HDMI type properties to your iGPU device @2: PciRoot(0x0)/Pci(0x2, 0x0) -> framebuffer-patch-enable 1 NUMBER // enables patching of framebuffer -> framebuffer-con1-enable 1 NUMBER // enables patching of connector 1 (i.e. 2nd output port) -> framebuffer-con1-type 00080000 DATA // sets connector 1 type to HDMI See the WEG user manual.

Your set of ACPI patched tables look wrong or incomplete to me. Follow the recommendations posted at Dortania.

The zipped archive you posted suggests your config may be incorrect so do post a zipped copy of your actual boot loader's EFI folder.

Some external disks require more power than a single USB port can output on its own; in such cases, you may either use a cable that plugs in 2 x USB ports so that you bring more power to the disk or, if applicable to the disk, plug an external power supply. It really depends on what you have.

No such thing on my E7270 which is the E7470's little brother. Can you check your DVMT settings (through Grub shell as detailed here by Jake Lo) and post a zipped copy of your bootloader's EFI folder? Of course, detailing your system's specs in signature would be great too so that we know what hardware you have...

If you're running Clover, you may have NVRAM leftovers from OpenCore in which case, boot an OpenCore USB and reset NVRAM at the OC Picker. If you're running OpenCore, just reset NVRAM at OC Picker.

-> Moved to Wifi hardware support given that this matter relates to a wireless card more than the laptop it's fitted in. Please identify your hardware if you want further assistance. "Dell wifi" means absolutely nothing. You may open up your laptop's case and look at the label glued on the card or look in IOReg for your card's PCI id. Once you've done that, consult our published inventories to verify likely compatibility. This being said, you state that the card works in Monterey with itlwm so it has to be be an Intel card. If it Is so, bear in mind that the OpenIntelWireless tools remain at a development stage with limited support and limited performance. Please note that the behaviour pattern you described is also indicative of a potential forthcoming hardware failure (happened to me recently).