Hervé

I'm pretty sure you're mistaken here... What you've illustrated is an Intel sensor of some sort. I don't believe it's the touchscreen at all. Dell has been fitting Atmel touchscreens to their XPS and Latitude laptops for years.

Absolutely nothing with the IOHIDFamily kext, it's just a patch to be specified in the bootloader config. I have the same patch in the OpenCore pack I posted in my Vostro 200 guide if you want to double check the patch in OC. Make sure to reset NVRAM at OC Picker when you reboot. Again, this can only work if your touchscreen is USB-based. Do you see it in SysInfo->Hardware->USB? Would be something looking like this:

If the stuff I posted on p1 does not work or suffice, you may seek inspiration from here. For graphics, an old Nvidia (Tesla) card would be a lot easier to get working. I don't know if the dGPU is MXM-based or soldered. If former, you may manage to replace your Radeon HD 3670 by an Nvidia Quadro FX 7xxM model (supported OOB up to High Sierra).

So... BIOS: F.20 (with AHCI support it would seem) CPU: Intel Penryn C2D P8400 FSB-1066 @2.26GHz RAM: 4GB DDR2-800 (PC2-6400) dGPU: ATI Mobility Radeon HD 3670 2GB (PCI id 1002:9593) Display: 1680x1050 built-in LCD Audio: Analog Devices AD1984A Codec IO Controller: Intel ICH9-M USB: USB2.0 ports Disk: 160GB Hitachi HTS543216L9A300 5400rpm SATA-II HDD LAN: Intel 82567LM Gigabit Ethernet Wireless: Intel Wifi Link 5300 AGN TouchPad: Synaptics SD card reader: Ricoh R/RL/5C476(II) (PCie) Optical drive: TSSTcorp TS-L633M CD/DVD writer Should run macOS High Sierra pretty well, though it'll be slow on that SATA-II 5400rpm HDD which you should consider replacing by a SATA SSD. I see the you've been posting on various forums these last few months to try and get macOS installed on this old laptop so I assume you're now familiar with bootloader, etc. I suggest that: you use Clover and start with an older version installed as follows: Clover for UEFI booting only Install Clover in the ESP UEFI Drivers AudioDxe DataHubDxe FSInject SMCHelper ApfsDriverLoader AptioMemoryFix Fat PartitionDxe Ps2MouseDxe UsbMouse.Dxe VBoxHfs Themes (optional) Install Clover Preference Pane (optional) you may use version r5035 for instance: Clover_v2.5k_r5035.pkg.zip once Clover is installed, run Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip open this EFI partition and transfer the files & folders from the Clover pack below to the EFI/Clover folder. The pack may not be100% complete to match all of your hardware (keep looking for kexts as required) but should get you going: EliteBook_8730w_Clover_Pack.zip For audio, experiment with the various layout ids specified in the AppleALC wiki. For your Synaptics touchpad, look here though it's old stuff (I've no experience with anything other than ALPS touchpads). For your Intel Wireless card, look here. For graphics acceleration, you'll have to experiment with the various ATI framebuffer personalities that may apply to Mobility Radeon HD 3670 (I've no experience with this): This is all without any guarantee of any kind so be prepared for additional home work. Good luck!

You did reset NVRAM at OC Picker after you changed your config and rebooted, right? I also note you never got rid of the stolenmem patch...

Touchscreens usually are USB based. However, recent macOS versions require that you apply a patch (called "USB HID fix") to support those USB accessories because, since Big Sur, Apple dropped support for older/legacy USB technology. The patch is readily available on Hackintosh forums and provided in my E7270 guide. Look it up.

I'm very pessimistic about likely success of graphics acceleration in Big Sur for R7 240. There were many many posts at IM on the matter with zero success afaik. Does not appear to be supported beyond Mojave with which it already required patching.

Ok, good to know. Thanks for posting the solution you found through experimentation. Azul FB in question is natively defined as follows: ID: 0A260005, STOLEN: 32 MB, FBMEM: 19 MB, VRAM: 1536 MB, Flags: 0x0000000F TOTAL STOLEN: 52 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 116 MB, MAX OVERALL: 117 MB (123219968 bytes) Camellia: CamelliaDisabled (0), Freq: 2777 Hz, FreqMax: 2777 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000030 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP [2] busId: 0x04, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP 00000800 02000000 30000000 01050900 00040000 87000000 02040900 00040000 87000000 Compared to the other 2 you tried: ID: 0A260006, STOLEN: 32 MB, FBMEM: 19 MB, VRAM: 1536 MB, Flags: 0x0000000F TOTAL STOLEN: 52 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 116 MB, MAX OVERALL: 117 MB (123219968 bytes) Camellia: CamelliaDisabled (0), Freq: 2777 Hz, FreqMax: 2777 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000030 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP [2] busId: 0x04, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP 00000800 02000000 30000000 01050900 00040000 87000000 02040900 00040000 87000000 ID: 0D260007, STOLEN: 64 MB, FBMEM: 34 MB, VRAM: 1536 MB, Flags: 0x0000031E TOTAL STOLEN: 99 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 227 MB, MAX OVERALL: 228 MB (239616000 bytes) Camellia: CamelliaDisabled (0), Freq: 1953 Hz, FreqMax: 1953 Hz Mobile: 1, PipeCount: 3, PortCount: 4, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000030 - ConnectorLVDS [1] busId: 0x05, pipe: 11, type: 0x00000400, flags: 0x00000107 - ConnectorDP [2] busId: 0x04, pipe: 11, type: 0x00000400, flags: 0x00000107 - ConnectorDP [3] busId: 0x06, pipe: 3, type: 0x00000800, flags: 0x00000006 - ConnectorHDMI 00000800 02000000 30000000 01050B00 00040000 07010000 02040B00 00040000 07010000 03060300 00080000 06000000 Go figure it out!

You can look at the guides I've posted for old Penryn-based Dell Latitude D630 and/or D830 in the Guides section (obviously). They're specific to those Dell and without your full systems specs (eg: audio codec, LAN card, wireless card, type of keyboard/touchpad, etc.), we won't be able to give you any working EFI, but you'll get pointers out of those guides. Target macOS High Sierra 10.13, that's the last version to officially support (and to the full) your hardware platform.

You're using Azul framebuffer 0x0d260007 instead of the expected 0x0a260006 which is what works on 4th gen Haswell Hackintosh laptops. Try and change your injected property from this: to this: AAPL,ig-platform-id 0600260a DATA and add this: framebuffer-patch-enable 1 NUMBER framebuffer-portcount 4 NUMBER

Clover probably better suited for legacy C2D platforms with non-UEFI BIOS.

I invite you to experiment with a bootable USB key on which you'll install your current bootloader setup with a modified config file where you'd remove all those connector's patches, i.e. all those framebuffer-conX-YYYY lines.

If VGA does not work OOB, don't expect it to work at all; saying that you have to make it work won't make it work... macOS just has no official support for VGA output off iGPUs anymore. There's no known patch to that effect so there you go. Video patches for 4th gen Haswell graphics is of no use to you and your CFL UHD 630 iGPU. According to the Dortania documentation, AMD R7 240 remains supported up to Monterey but success rate varies according to make and models (you'll have to make some extensive reading and experimenting): https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/amd-gpu.html#r7-r9 Apart from repairing your HDMI port or getting graphics acceleration working out of your R7 240, the only option you have is installing a supported discrete graphics card. You can get nVidia Kepler cards for next to nothing and these remain fully and natively supported in Big Sur (eg: GeForce GT710/720/730).

https://osxlatitude.com/forums/topic/2998-platforms-requirements-for-os-xmacos https://osxlatitude.com/forums/topic/8238-supportedunsupported-gpus-graphics-cards https://dortania.github.io/OpenCore-Install-Guide/config.plist/penryn.html

No such thing as "clear PRAM" on a Hackintosh; that's for real Mac computers only. You can of course re-install Mavericks (or any subsequent compatible OS X/macOS version) over an existing build.

-> ALC688 codec. Use AppleALC PlugIn of Lilu and configure according to the AppleALC wiki. Same as you had with Monterey really; provided you did not install any OCLP patch for audio; that would be unsuitable.

Patch what?

If the flags patch still makes no difference, the AGDP patch probably is the last and most likely resort. Details are in my old HD4600 patching guide I linked on p1. Totally linked to device (i.e. Mac model) official capabilities and therefore SMBIOS model selected.

All Dell Latitude have a BIOS section about LAN & Wireless devices. Please look this up in your BIOS settings. If in doubt, look up the documentation for your Latitude model on Dell's site (support section). NB: As per our published rules, please refrain from quoting entire posts to reply; forum provides a Reply box at the bottom of each page so use that instead.

Too many models to choose from! We've posted threads about minimum requirements for CPUs and iGPUs. Obviously, the best models are 10th gen Comet Lake and Ice lake laptops since these are the last Intel platforms used by Apple.

You did not specify if both disk use the same identical Bootloader and/or same Bootloader version. I'd recommend you reset NVRAM before you attempt to boot back in Monterey after using Ventura. That should clear out any leftovers that may cause issues. You'd do the same when booting back into Ventura from Monterey.

System freeze on cable connection/disconnection was/is typical behaviour with HDMI on Haswell/HD4600 laptops; this is fixed by patching the connector con1 (0105) pipe value from 0x09 to 0x12; you need to do that same for DP connector con2 (0204) as described in this old Haswell HD4600 patching guide for reference. Edit: Never mind, that's what Jake's done his the adjusted config file he posted just above.

Haswell framebuffer layout 0x0a260006 defines the following graphics properties: ID: 0A260006, STOLEN: 32 MB, FBMEM: 19 MB, VRAM: 1536 MB, Flags: 0x0000000F TOTAL STOLEN: 52 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 116 MB, MAX OVERALL: 117 MB (123219968 bytes) Camellia: CamelliaDisabled (0), Freq: 2777 Hz, FreqMax: 2777 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000030 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP [2] busId: 0x04, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP 00000800 02000000 30000000 01050900 00040000 87000000 02040900 00040000 87000000 DP should work OOB off connector con2. HDMI requires to change connector con1's type to HDMI and pipe to 0x0A. Check out your connectors behaviour in IOReg (using an app such as IORegistryExplorer) when you hook up your external screens.

Check your port settings/patches in your OC config and in IOReg. We've had reports of similar thing over HDMI with KBL R UHD 620 graphics for instance and it was fixed by setting the connector to the correct type. See here or here. Please make the effort to: read our published rules before posting add your systems specs in signature or in your post(s) post a zipped copy of your OC config post a zipped copy of IOReg extract when TV is connected. It really is the bare minimum to expect assistance...