Hervé

Even though a Skylake iGPU is listed with 1536MB, you don't appear to have graphics acceleration in place (Finder's bar + Dock should be translucent, not greyed out). For Monterey, make sure you use the following settings on your Skylake/HD 520 laptop: MacBookPro13,1 SMBIOS SKL framebuffer layout 0x19160000 iGPU id 0x1916 of your i7-6600u is fully and natively supported so no need to inject it as a property (does no harm though of course). Nothing more to setup for graphics is video memory is set to 64MB in BIOS as stated by Jake. You may only need to patch the connector used for HDMI output if you need/want HDMI audio. Don't hesitate to look here for pointers (my Latitude E7270 is also fitted with i7-6600u CPU + HD 520 graphics) and post a zipped copy of your EFI folder.

http://www.linux-usb.org/usb.ids 05ac:820a is an Apple Bluetooth keyboard so clearly not the built-in one.

Yes, sorry I indeed made a confusion thinking you had the Intel card in that WWAN slot when it's clearly a half-size mini-PCIe card you had in the WLAN slot. E7270's WWAN slot is M.2 Key B so unsuitable for Key A/E Wifi/BT cards. What I meant was that, in the case of my E7270, there is no instant wake issue due to replacement GPRW method not caring for values provided in the GPRW (0x69, 0x04) call programmed under the WLAN ACPI device. It'd be interesting to see what call is made in your DSDT under the RP0x.PXSX device used by the WLAN card/slot.

Afaik, Sandy Bridge Latitude E6x20 laptops do not support installation of OS X/macOS from a USB key/disk in UEFI BIOS mode, only legacy mode. Thereafter, once OS X/macOS has been installed, you may indeed switch to UEFI BIOS mode and, provided you've installed your bootloader accordingly, OS X/macOS will boot and run Ok from internal disk in UEFI mode; I've detailed this in my E6220 guide. Taking that into account, you'll probably have to use Clover rather than Opencore, at least to boot in legacy mode. Is it an E6520 with HD3000 iGPU only or is it also fitted with the Fermi-based nVidia NVS 4200M dGPU? Former is supported OOB up to macOS High Sierra 10.13 (with patches in later macOS versions though poorly supported in Big Sur and later), latter up to Sierra only (no support in later versions). Don't hesitate to read the existing E6x20 threads and guides available on our forum. An E6520 with nVidia graphics will require that you enable Optimus in BIOS (to be able to run on HD3000 iGPU), then disable the dGPU via SSDT to prevent it from draining your battery unnecessarily. If Optimus is disabled, only the dGPU is available. Please note that, in old OS X El Capitan 10.11 and all subsequent macOS versions, HD3000 gets buggy over time and you'll experience graphics artefacts, like horizontal lines across the screen or pixelisation. There are no fixes for this, only reboots will do. Note that, even though they run Win10/Win11 just fine, those E6x20 laptops are to be considered obsolete for Hackintosh purposes. NB: Don't use distros, we don't support those here.

Interesting... No such additional patches required on my E7270 which is fitted with a BCM94360CS2. The card also attached to RP05.PXSX and _PRW method does call on GPRW with (0x69,0x4D) arguments; same applies to SD card reader attached to RP11.PXSX. Add-on patched table SSDT-GPRW.aml does not care for Arg0 being set to 0x69, yet sleep works perfectly well. On the PCIe side, it's kinda weird that wake was working when you had an Intel card in that slot but not when the BCM94360CS2 was installed. Hence why I assumed it would be the USB-based Bluetooth module that caused instant wake. Well done on your fix.

Don't know how you managed to miss it !

Probably not booting because the bootloader was not properly installed, then.

OC not configured properly; check your OC setup/files/version/etc.

You don't need OCLP to install Ventura and I would advise you not to use that tool for installation. OCLP is meant for real Mac computers, not Hackintosh. You've only posted a copy of your OC config file so I can only comment on that: I see a lot of references to E7440 stuff (eg: E7440-SSDT.aml or USBPort_E7440.kext) you use correct MBP14,1 SMBIOS for a regular Ventura installation (i.e. non-OCLP) if you use MBP14,1 SMBIOS, why do you use -no_compat_check boot arg? latest versions of Lilu fully support Ventura so why use -lilubetaall boot arg? Indeed, Ventura dropped support for Haswell HD4200/HD4400/HD4600 and associates so you do need the OCLP graphics patch but in a post-installation phase. So: make a regular Ventura installer (not n OCLP one) install Ventura with MBP14,1 SMBIOS cleanup your setup to remove the unecessary boot args and use the proper ACPI tables + USB port mapping kext install Haswell HD4x00 graphics patch withOCLP at post-install if the OCLP patch requires to return to MBP11,x or MBA6,2 SMBIOS, then, yes, you'll need the -no_compat_check boot arg

As I said, you ned to adjust the power settings attached to the USB port supporting the Bluetooth module of your card. Check your IOReg + ACPI tables.

The slot in question is combo mSATA/WWAN and therefore supports USB on top of SATA + PCIe services. Instant wake is often due to a device not going in sleep mode because it is not powered down; in your case, it would have to be the USB-based Bluetooth module of the card. I'd say you need to adjust power settings of your USB ACPI devices since I expect the WWAN slot was not initially taken into account given that there was no USB device attached to it. I encountered a similar issue when I replaced a (wifi-only) DW1510 card by a (combo Wifi/BT) BCM94360CS2 in my Vostro 200 desktop. See here for details (in my case, a patched DSDT is used; in your case, I expect you use a SSDT). Don't understand what you say about your assertion log and the "Keyboard working fine and not causing instant wake on the Intel Wifi" statement. I fail to see the link between your keyboard and the Intel wireless cards. Anyway, your Intel Wifi may not be fitted with Bluetooth or, at least, a bluetooth module that was detected in macOS. Check your USB ports in SysInfo... So, as indicated above, identify the USB port used by your card and patch/adjust the associated UHC/EHC/XHC ACPI device accordingly.

Boot in verbose mode to see where things hang.

For increased visibility, I'm re-posting here the kext recently compiled by @gelomon whom I thank for his work. Details are available in this thread. It's applicable to Alps Touchpad v3-v5 as fitted to Dell Latitude models such as the E5x40 or E7x40. VoodooPS2Controller.kext.zip

https://osxlatitude.com/articles/news/macos-ventura-is-out-r74/

Could be due to missing HFS module/driver for Clover; try and add this to your CLOVER/drivers/BIOS and/or CLOVER/drivers/UEFI folder: HFSPlus.efi.zip How did you install Clover, if at all? Through an installation package, in which case which version? Or did you simply copy the EFI without making any specific Clover installation?

Ventura dropped support for anything older than Kaby Lake and therefore older than Intel HD61x/620/630 graphics. So, indeed, you'll need to apply the graphics patch offered by latest version of OCLP (v0.5.0 being the earliest one for such Ventura patches). Be careful given that OCLP really is a tool for real Mac computers not Hackintosh computers. Only install the graphics patch and nothing else. You'll probably have to keep Broadwell MBP12,1 SMBIOS and boot with -no_compat_check boot arg to boot Ventura and then apply the OCLP patch. I've not had to use the tool on any of my Hackintoshes (only on a real iMac) but I guess you'll only use it in post-install phase, i.e. do not make a macOS installer for your Hackintosh with OCLP. Make sure to read the OCLP documentation thoroughly and keep in mind that, at this point of time, the OCLP Ventura patches remain in beta stage and aren't bug free. https://dortania.github.io/OpenCore-Legacy-Patcher/POST-INSTALL.html#applying-post-install-volume-patches https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1008 https://github.com/dortania/OpenCore-Legacy-Patcher/releases If you want a fully and properly working Hackintosh, wisdom dictates you stick to Monterey for the time being.

Well it is CoolStar's kext but it's clearly not loaded at boot loader's menu given that macOs has not even launched at that stage yet so something else drives it there...

Not sure I see the relevance of that Ubuntu-related video for macOS (and it's in Italian!) but where did you get that kext from? Didn't it come with instructions and/or proven usage? If it's the stuff posted on GitHub by Coolstar, that's old preliminary work dating back 2018 that comes with zero documentation and never revisited or updated since initial commit. Maybe you should start by contacting the author but I'm pretty sure it's some very unfinished work... All I can say is, yes, you'll definitely need a driver, i.e. a kext, for this I2C Touchscreen to be supported.

Yes that may work but the easiest remains Windows Device Manager->Driver details where you'll find device's vendor id + device id.

@sensui20 SSDT table "SSDT-PLUG-DRTNIA" is corrupt. Make sure to replace it by a valid one. Other tables look Ok. https://dortania.github.io/Getting-Started-With-ACPI/ssdt-platform.html#laptop

Assuming there's no hardware-related issue with your keyboard, I guess the kext (driver) you're using may not be appropriate. It's probably I2C hardware but from which manufacturer? ALPS, Synaptics, Elan?

Graphics settings look a bit odd to me for a Kaby Lake U/Kaby Lake R laptop with HD 620/UHD 620 graphics (i.e. 7th or 8th gen)... For clarification, you should add your system's specs in signature or post them in your introductory post (we don't have crystal balls, sorry). Never seen the need to change built-in LCD connector's pipe for instance. The recommend settings for an 8th gen Kaby Lake R laptop with UHD 620 graphics used to be: framebuffer layout 0x591b0000 (I used 0x59160000 for Mojave and 0x59160009 for Catalina on my 8th gen KBL R Latitude 7490), 0x87c00000 being for Amber Lake laptops (Dortania's documentation says otherwise but...) fake iGPU id 0x5916 See the WEG user manual. Details of those KBL framebuffers are as follows: ID: 87C00000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000078B TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 103 MB, MAX OVERALL: 104 MB (109588480 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00040000 87010000 ID: 591B0000, STOLEN: 38 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000130B TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 136 MB, MAX OVERALL: 137 MB (144191488 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [2] busId: 0x04, pipe: 10, type: 0x00000800, flags: 0x00000187 - ConnectorHDMI [3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 02040A00 00080000 87010000 03060A00 00040000 87010000 ID: 59160000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00000B0B TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 103 MB, MAX OVERALL: 104 MB (109588480 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000800, flags: 0x00000187 - ConnectorHDMI 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00080000 87010000 ID: 59160009, STOLEN: 38 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00830B0A 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: CamelliaV3 (3), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000001C7 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000001C7 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 C7010000 02040A00 00040000 C7010000 It's worth noting that, on the 7490, HDMI output required connector con1 to be configured (i.e. patched) as follows: 01051200 00080000 87010000 The patch therefore varies according to the FB used. I see no reason why things would be different on an 8th gen 7390.

You use SKL framebuffer atout 0x19120000 which defines the following properties: ID: 19120000, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000110F TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes) Model name: Intel HD Graphics SKL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [255] busId: 0x00, pipe: 0, type: 0x00000001, flags: 0x00000020 - ConnectorDummy [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP FF000000 01000000 20000000 01050900 00040000 87010000 02040A00 00040000 87010000 As suggested by Jake, once you've identified in IOReg which connector your HDMI output attaches to (in all likelihood con1, i.e.AppleIntelFramebuffer@1 but it may be con2, i.e AppleIntelFramebuffer@2), patch its type by adding the following lines to your injected iGPU properties set: framebuffer-conX-enable 1 NUMBER framebuffer-conX-type 00080000 DATA where X is 1 or 2. HDMI output can also be a little difficult at times on Skylake HD5x0. Make sure to add Whatevergreen boot arg igfxonln=1 in your bootloader config. See the Whatevergren documentation and user manual.

HDMI audio only works on Haswell Hackintosh if: you patch the associated framebuffer connector to HDMI type (00080000) -> not the case in the last IOReg you posted but corrected in Jake's last config you rename ACPI device B0D3 device to HDAU -> that was the case in the last IOReg you posted Make sure you select the HDMI audio output, it has to be done manually and volume is controlled on the HDMI device itself, not the laptop.

If you still have Windows, I'd also check it out in Device Manager... But it does not look like the touchscreen of the XPS 12 9Q33 is USB-based but, in fact, connected to the I2C bus alongside the TouchPad. There's probably little chance to get it working under macOS... https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=4p1td&oscode=w864&productcode=xps-12-9q33