Hervé

It's best to opt for Clover on these old and obsolete laptops given that OpenCore is really made for systems fully operating in UEFI mode and it's a little painful to configure in legacy mode. Clover is far easier to configure and change in that respect. Look up my E6220 guide for pointers.

Graphics settings to use for KBL R UHD620 iGPU are: KBL framebuffer layout 0x591B0000 or 0x59160000 iGPU device id 0x5916 (or 0x5912 apparently) Layouts 0x87C000-- normally are for Amber Lake systems. SMBIOS should be MBP15,2 with MBP15,4 probably fine as well. Of course, DVMT will need to be set at 64MB minimum in BIOS for 4K output, it won't be achievable with DVMT set to 32MB. There are no workaround to this.

Intel i5-6500 integrates HD 530 iGPU with id 0x1912; this is natively supported, hence no need to fake iGPU is 0x191b. See the WEG user manual: https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md#intel-hd-graphics-510-580-skylake-processors

So... Dell XPS 13 7390: BIOS 1.18.0 Comet Lake i7-10710U @1.10GHz (6 core) Intel UHD graphics for 10th gen CPU (~ Intel UHD 620) -> PCI id 8086:9BCA FHD 1920x1080 built-in screen 16GB LPDDR3-2133 RAM 512GB SK Hynix PC611 NVME SSD Realtek ALC299 High Definition Audio -> PCI id 10EC:0299 Microdia integrated webcam (USB internal) -> PCI id 0C45:6D13 Realtek RTS525a PCIe microSD card reader -> PCI id 10EC:525A Intel Killer AX1650 Wi-Fi 6 802.11ax wireless + Bluetooth 5.2 -> PCI id 8086:2723 I2C Synaptics Touchpad -> PCI id 06CB:76B1 2 x TB3 (USB-c) ports 1 x USB3.1 gen2 (USB-c) port 1 x combo audio jack

When you boot with an invalid framebuffer, macOS operates in what is called VESA mode; consider it like Windows safe mode if you want a comparison. In this mode, you have no graphics driver loaded and the system operates in a very basic graphics mode. This is fully reflected in IOReg where you see no framebuffer whatsoever: When you boot with a valid (CFL) framebuffer, the driver loads/applies the framebuffer's defined output ports. Those will be reflected in IOReg and include the displays against/under their associated connectors (i.e. video output ports), provided these are fully and properly detected. In the case of your internal screen, regretfully it is not (no display registers again FB@0, FB@1 or FB@2): On the other hand, your external display does register as an HDMI monitor attached to 3rd output port FB@2: Now, looking at each output port when you boot with valid CFL layout 0x3e9b007, I see that all 3 x video output ports (i.e. connectors) are set to HDMI type (00080000). In all likelihood, your internal screen is LVDS or DP/mDP and you should try and experiment with that. It should be attached to 1st output port, i.e. FB@0 aka con0. As explained in my previous post, CFL framebuffer layout 0x3e9b007 defines 3 x DP ports. I would suggest you revisit your bootloader's config file and, in the iGPU device properties section, you experiment with con0's type as follows: framebuffer-con0-enable 1 NUMBER framebuffer-con0-type XXXXXXXX DATA where XXXXXXXX corresponds to the desired port type: 00080000 -> HDMI 00040000 -> DP/mDP 02000000 -> LVDS/eDP 04000000 -> digital DVI (or is it dual link DVI ?) 00020000 -> analog DVI (or is it single link DVI?) LVDS/eDP type being the most likely target value. If you stop injecting a port type for con0, you'll revert to default DP type but I assume you may have already tried that. You may also require to inject different values for the connector's flags but I'm not so familiar with that. Say, inject the same flags as for the built-in display of a CFL mobile layout: framebuffer-con0-flags 98000000 DATA Or disable/play with AGPM, that's another possibility.

IOReg taken with invalid/dummy framebuffer layout 0x12345678 is useless. You need to take an IOReg once booted with a valid CFL layout. You can do that either after having setup screen sharing and accessing the Hack from another computer or by using an external HDMI/DP display.

I'm not sure you've understood the limitations of running with alpha versions... Your other possibilities: you run Monterey for which you'll have full ITLWM support with v2.1.0 you replace your Intel card by a compatible Broadcom-based model you wait until ITLWM has proper support for Ventura Nothing else.

You can't just install "any macOS" version on a 10th gen laptop. Please read the information available in our "Technical information" section to be aware of the bare minimum in relation to your hardware platform. It's called homework.

I think you're a little confused. EFI are small partitions (not disk sectors) where bootloaders and bootloaders config files reside. They're not partitions you'd be expected to boot per sé nor select in Clover or Opencore boot menu to boot macOS. Instead, you're expected to select your target macOS partition (eg: Big Sur, Monterey, Ventura, etc.) where the OS has been installed. Don't hesitate to Google about this. As for UEFI, consider it as a kind of computer BIOS/Setup operating mode (though it's more a replacement of BIOS as we know it), not a type of partitions or disks. Don't hesitate to Google about this. You have 2 SSDs and each appear to have an EFI partition. Your screenshot shows said partition mounted on ADATA SSD but not mounted on SPCC SSD. I assume the device going by the name "Patriot Memory" is the USB device (whether external disk or USB key) you referred to. All in all, I can't see the issue you're having here; you need to properly describe your problem, it's not clear at all.

https://openintelwireless.github.io/itlwm/FAQ.html https://github.com/OpenIntelWireless/itlwm/releases

Didn't I write "in the Ventura pack of my E7270 guide" ? It's all there; don't know what else we can do here...

Please describe what you boot and how, in a proper and explicit enough manner. The above is far too poor. I assume your request is macOS-related since you're posting here. Please provide your full system's specs and a zipped copy of your boot loader. Do specify the target macOS version and the bootloader version.

Just modify your OC config using any plist editor app (eg: Xcode, ProperTree, PlistEditPro, etc.) or basic text editor (eg: TextEdit) or dedicated app such as OpenCoreConfigurator (OCC). How else did you build your setup? Or did you just copy/paste a complete OpenCore EFI folder from somewhere and somehow got lucky?

IOReg and OC config show you're using KBL mobile framebuffer 0x591e0000 rather than desktop framebuffer 0x59120000 as expected and recommended by the WhateverGreen User Manuel. ID: 59120000, STOLEN: 38 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000110B TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 115 MB, MAX OVERALL: 116 MB (122171392 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP [3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 01050900 00040000 87010000 02040A00 00040000 87010000 03060A00 00040000 87010000 Note that this framebuffer defines 3 x DP outputs so you may have to patch the connectors depending on your own physical output ports. No support for VGA of course. Your OC config currently changes connectors con1 and con2 to HDMI type, leaving con0 unmodified. You should also change SMBIOS from iMac18,2 to iMac18,1 since former uses AMD dGPU whilst latter uses KBL iGPU only. NB: you're injecting iGPU unifiedmem property with value 0x80000000, i.e. 2GB; as such your graphics info should show 2048MB in About this Mac, not "[...] 1532MB or whatever the MB [...]".

You may try the PS2 controller kext posted in the Ventura pack of my E7270 guide.

You'll need to be specific about your wireless card and tell us what model it is. ITLWM support for Ventura is currently at early alpha stage so, indeed, you may find your model is not fully supported at the present time. Re: audio, you'll have to identify the codec; being an E5440, I'm tempted to say ALC292 as per other Haswell Latitude E Series in which case injecting layout-id 12 normally does the trick. Basically, the exact same thing as per previous macOS versions. Again, make sure to stay away from any OCLP audio patches as that will affect your system.

Perfectly normal; you can't install Ventura without a supported SMBIOS; same goes for OTA updates. Once Ventura is installed, revert to Haswell SMBIOS and boot with -no_compat_check boot arg. Then apply the OCLP root patches.

You must revert to the SMBIOS of unsupported Haswell platform for the OCLP patch to work: MBP11,x or MBA6,2. You installed Ventura with SMBIOS MBP14,1 which is a Kaby Lake platform. That's unsuitable for OCLP patching. Make sure you apply the OCLP root patches and absolutely nothing else on your Hackintosh.

No, he did not; he's got no graphics acceleration -> Intel HD Graphics 4400 4MB. It's not "Ventura done" per sé but Ventura installed and running in reduced VESA mode for the time being... NB: As per our published rules, no double post on the forum please.

@ABOFE, if your touchscreen is USB, I expect you'll need to apply the USB HID Fix patch. You can look it up on the Web but this patch is mandatory since Big Sur (because Apple then dropped support for older USB technology) and it's missing in the OC config you uploaded in post #1. Please follow the link I gave you above and apply the patch in your config accordingly. Make sure you've properly mapped all your USB ports, including the internal ones of course. It's as simple as that...

Development for Intel wireless cards under macOS Ventura remains at alpha stage for the moment as clearly indicated on the ITLWM Github repo. Support under alpha version 2.2.0 is known to be pretty poor for some cards as can be expected; there should be not surprise there. Best indeed to opt for Monterey unless using a supported Broadcom card. https://github.com/OpenIntelWireless/itlwm/releases https://openintelwireless.github.io/itlwm/FAQ.html#installation

Should do but only one way to know... https://dortania.github.io/Anti-Hackintosh-Buyers-Guide/Storage.html Make sure you use the NVMEFix kext.

Logs? Zipped copy of OC EFI/setup? Something? Anything?

Identify the model and nature of touchscreen (PCIe/IC2 vs. USB) through SysInfo or IOReg. If USB, expect an Atmel device and look here to apply the USB HID Fix which is likely to be necessary. This is what the touchscreen looks like on my Skylake Latitude E7270: