Hervé

You have to be more specific with regards to your statement about "using MBP14,1, SKL graphics settings". OCLP is to patch unsupported systems. As such, if you want to apply the tool to your system, you have to apply it with MBP13,1 SMBIOS selected in the tool (not MBP14,1 which is a supported platform), then boot with MBP13,1 SMBIOS + -no_compat_check boot arg.

Do try to inject your screen's EDID though if it's not required for Monterey, it should not be for for Ventura. Feel free to experiment with OCLP if the usual tricks don't work for you.

Try the KBL settings for Ventura with Monterey (MBP14,1, KBL faked iGPU settings, boot arg -igfxsklaskbl).. Failing that, try and boot Ventura in VESA mode to check if you can reach the desktop without graphics acceleration. This would confirm whether your issue is iGPU settings related or not.

@EMU7989 I don't think you need some of those properties you inject: I recommend you remove those properties highlighted in red. Never seen any need for dual link properties since Ivy Bridge days (this may be the cause of your black screen), HD520 is not HDMI 2.0 and KBL 0x59160000 framebuffer is natively defined with 3 ports/3pipes. Re: injected kexts, you correctly inject v1.6.3 of Lilu + Whatevergreen but I do wonder what those do and why you inject them: AppleBacklightSmoother AMFIExemption YogaSMC I'd recommend you get rid of those too. One thing you can do with Monterey is call on a Ventura-targeting config in which you add the Lilu/WEG boot arg -igfxsklaskbl which will allow you to test faked KBL graphics in Monterey. If you use Clover, you may just boot Monterey with a specific config file to that effect that you'd call from the Clover main menu->Options->Configs. This being said, do search the forum for black screen in Ventura, I think there are posts about this very matter on Skylake laptops.

@Eldeebo please make every effort to post in a suitable manner. A thread entitled "Precision 7510 Ventura wifi bug" in the Precision x000 section was not appropriate for your predicament. You could have at least indicated the wireless card model and consulted the OpenIntelWireless site where support for Intel wireless cards stops at Monterey with release v2.1.0 of Jan 2022. As indicated by Jake, support for Ventura may only be provided in v2.2.0 which is clearly stated to be at early pre-release alpha stage at this point of time. A link to the Gitter Chat room is also provided as the place to report/discuss issues. https://github.com/OpenIntelWireless/itlwm/releases Meantime, you may either replace your wireless card for a Broadcom model supported in Ventura or opt for macOS Monterey and have proper support for your Intel card.

If everything works Ok, leave it be and enjoy your Hack as it is.

Don't hesitate to scrounge the Net before asking on forums... CCC probably best avoided with Ventura; there are lots of unresolved known issues. https://bombich.com/kb/ccc6/macos-ventura-known-issues https://bombich.com/kb/ccc6/cloning-macos-system-volumes-apple-software-restore https://www.reddit.com/r/MacOSBeta/comments/xah1pm/carbon_copy_cloner_mac_os_ventura/ My understanding is that you will not succeed trying to boot a cloned OCLP-patched Ventura installation; at best -if that works at all !- you would need to either: 1) clone your basic, i.e. unpatched, Ventura installation prior to OCLP patching; you may then patch your cloned disc. or 2) unpatch your Ventura build, clone it, then repatch; and, of course, patch your cloned disc afterwards. Do consider that, since Big Sur -even more so with Ventura-, CCC (and other apps such as SuperDuper) are no longer reliable for macOS disc cloning, especially on Hackintosh running patched installations for unsupported hardware. Issues are related to (sealed and encrypted) snapshots. Many people have written about this if you care to search the Net. Also consider alternative bootable disc cloning solutions for macOS Ventura (if such things do exist and they may not be free): https://www.doyourdata.com/disk-copy/best-disk-clone-software-for-macos-ventura.html https://www.doyourdata.com/disk-copy/make-bootable-backup-clone-for-mac.html https://www.donemax.com/mac-disk-clone/clone-macos-ventura-to-external-hard-drive.html

Don't hesitate to rollback your PS2Controller kexts then.

Re: BIOS, I think you're very confused and no OC package can contain a BIOS update. If your BIOS version shows A09, that's what you got. You can only update your BIOS through the DOS/Windows .exe published by Dell, i.e. only from Windows or through a DOS-based USB key for instance. Rest assured OpenCore does not touch BIOS or BIOS settings in any way.

I've completely revamped my E6230 Big Sur guide. See here. I don't believe I changed the PS2Controller kexts between Catalina and Big Sur but feel free to experiment (make sure to boot off a USB key when testing to avoid breaking a running build).

3 wireless cards experiencing the same issues: I think it's safe to say the issue lies elsewhere but with the card themselves. Faulty slot (unlikely)? Defective antennas ? Duff macOS installation? Try and make a new build on a separate partition, even if temporarily so. To rule out a hardware issue, did you try those cards in, say, Windows?

compatible statement carries no value in your OC config; bound to be a problem... You could get rid of the Intel wireless/Bluetooth kexts, at least disable them in your OC config. Can't see anything else.

Nothing to do with AFPS, something macOS uses since High Sierra. So Mojave also uses APFS file system. Audio sometimes requires to patch HPET for IRQs (interruptions). Maybe you need that. You would find typical patched HPET SSDTs at the Dortania repo and can re-use them. I attach an example. SSDT-HPET.aml.zip

Re: brightness control, all was normally included in the patched DSDT I had posted. I've made a fresh (re)install of Big Sur 11.7.2 with Clover r4151; will update my guide accordingly very soon. Meantime, do add/replace the following tables (once unzipped) in the ACPI/patched folder of your Clover EFI (you may also add the SSDT-PNLF table to the list specified tables in your Clover config). SSDT-PNLF.aml.zip DSDT.aml.zip Your IOReg clearly shows Big Sur booted but your Clover config does not show the -no_compat_check that's necessary with MBP10,2 bootpack. Did you use the old alternative method of modifying the macOS file that defines the supported models?

Nothing looks wrong in IOReg. After 3 x different cards, hardware issues being excluded, there can only be an issue with your setup: BIOS settings, macOS installation, bootloader config. Make sure there's nothing disabled in BIOS for Wireless services and do post a zipped copy of your EFI (limit contents to ACPI + kexts folder & config file).

Nothing strange re: Preboot and Recovery, that's what you obtain since Big Sur when using Clover; it'd be the same with Monterey or Ventura. You'll be booting the Preboot partition. Re: Intel Wireless, consult the usual online documentation. Re: screen brightness, all is explained in the dedicated thread I posted here some time ago and the bootpacks I posted in my E6230 guide all contain the necessary ACPI patches in the provided DSDT. Look these up.

Perfectly normal, you can't install Big Sur with the SMBIOS of an unsupported Mac model. As such, you have to use something like SMBIOS MBP11,x or MBP12,1 during installation before switching back to MBP9,x/10,x afterwards. In the same respect, note that you won't get offered any Big Sur updates until you use the SMBIOS of a supported Mac model.

Target macOS release: Monterey 12.x. This is a Clover-based installation based on the standard vanilla method detailed below, followed by OCLP basic root patching to bring back support for HD4000 graphics. Working: full graphics acceleration on Intel HD4000 graphics (with Lilu v1.6.3 + WEG v1.6.3 + OCLP v0.5.3 root patching) multi-display with HDMI after OCLP patching audio, including jack microphone input and headset output (with AppleALC v1.6.4 & layout 12 + CodecCommander v2.7.2) HDMI audio (with Capri Framebuffer properties injection) built-in GigEthernet LAN connection (with AppleIntelE1000e v3.1.0 or latest IntelMausiEthernet kext) wireless and bluetooth with any compatible card integrated webcam (OOB) full CPU power management, including Turbo boost (with CPU-specific generated ssdt) sleep (Lid, Energy Saver settings, Apple menu, Fn-F1, PWR button) & wake (Lid, PWR button) battery management (with ACPIBatteryManager v1.90.1) SD card reader (with DSDT patch or property injection, for compatibility with Apple's default card reader) keyboard (with Dr Hurt's VoodooPS2Controller R6 + DSDT patch for brightness control) touchpad including tap-to-click (with Dr Hurt's VoodooPS2Controller R6) left combo eSATA/USB2.0 + right USB3.0 ports (with Hackintool's generated USBPorts; optional FakePCIID kexts v1.3.15, published here, for multiplexing) ExpressCard slot OOB Not working: VGA output unsupported Not tested: SmartCard reader fingerprint scanner 1) 12.x USB installer creation Using a USB key of 16GB minimum, create a Monterey USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Monterey installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_16GB) The process will take several minutes. Once completed: install Clover boot loader on the USB installer with the following customised settings: Clover for UEFI booting only Install Clover in the ESP UEFI drivers Recommended Drivers (optional) EnglishDxe Human Interface Devices (optional) PS2MouseDxe USBMouseDxe FileSystem Drivers ApfsDriverLoader FAT (optional) Memory fix drivers OpenRuntime Additional Drivers (optional) PartitionDxe Themes (optional) BootLoader Chooser (optional) CloverConfigPlistValidator (optional) you may use version r5150 attached below Clover_r5150.pkg.zip once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip add the (unzipped) HFSPlus driver attached below to the EFI/CLOVER/drivers/UEFI folder HFSPlus.efi.zip open the EFI partition and transfer the files and folders from the Latitude E6230 Monterey Clover pack below to the EFI/CLOVER folder Clover_Pack_E6230_Monterey.zip /!\ If your E6230 is fitted with a different CPU than the i7-3540M, please remove the Power Management SSDT of the pack until you replace it by one applicable to your model (whether an existing SSDT or your own generated one) in the post-install phase. 2) 12.x installation boot the Monterey USB installer at the Clover main menu, go to the "Options->configs" menu and select the "config_MBP11,4" config file. This is required to install (and later update as/when required) Monterey on a supported Mac model. Press [ESC] twice to return to Clover main menu. at the Clover main menu, select the "Install macOS Monterey" partition and press [ENTER] at Monterey main installation screen, select Disk Utility to create & format APFS the target Monterey disk/partition/volume. Note that installation won't work if target disk/partition/volume is formatted HFS+ exit DU and return to Monterey main installation screen, then proceed with installation the installation process will reboot a temporary macOS installer partition to complete the installation. repeat this until the temporary partition is replaced by a final <Monterey partition name> on Preboot entry. Each time, reboot via your USB installer and make sure to select the "config_MBP11,4" config file. when the partition <Monterey partition name> on Preboot is displayed at Clover main menu, no need to call on the "config_MBP11,4" config file, the default one will do (MBP10,2 SMBIOS + -no_compat_check boot arg). 3) Post-installation tuning Once the finalised Monterey installation has booted, complete the 1st boot configuration tuning. This will be very slow due to lack of graphics acceleration, HD4000 having been dropped in macOS Monterey. Once at the desktop, mount the EFI partition of your Monterey disk Copy the EFI folder of the E6230 Monterey Clover pack to the mounted EFI partition You may then modify your SMBIOS info using Clover Configurator app and ensure you have unique numbers or unique combination of numbers (MLB, ROM, SystemSerialNumber and SystemUUID). Please note that, with MBP10,2 SMBIOS, Monterey will not offer any updates because it'll be running on an unsupported platform. You'll only get updated offered if you boot with the MBP11,4 config file, MacBookPro11,4 being a supported model. 4) Post-installation OCLP patching OpenCoreLegacyPatcher (OCLP) app may be used to patch the Monterey build on the E6230 to recover support for HD4000 graphics. Best is to use the latest version of the tool available here. Run the tool and set it up as follows in order to apply post-installation root patching: click Settings button select MacBookPro10,2 SMBIOS, then return to Settings select SIP settings and tick all cases except "CSR_ALLOW_APPLE_INTERNAL" in order to set SIP to 0xFEF, then return to Settings select SMBIOS Settings and make sure everything is left blank, then return to Settings select Misc Settings and tick everything off, leaving Feature Unlock Status as "Enabled, then return to Settings select Non-Metal Settings and make sure everything is ticked off, then return to Settings select Developper Settings and make sure everything is ticked off, then return to Settings return to Main Menu Click Post Install Root Patch, then Start Root Patching OCLP root patches will then be installed. Once completed, reboot into Monterey and you'll have graphics acceleration running on HD4000. Note that OCLP root patching will be required after each Monterey update.

Hmm, might want to use latest Clover release r5150 by now. I never updated my guide since it was 1st published for Big Sur initial release back in 2020... I had been running with r513x for yonks before updating to r5141 some time ago. Very recently replaced my Big Sur build by Monterey 12.6.2 with r5150 (applied basic OCLP root patch for HD4000 graphics). Would have to try out Big Sur installation again on the basis that current package (at time of writing) will indeed be version 11.7.2. Points to note: make sure you update Lilu & PlugIns (AppleALC, WhateverGreen, etc.) to latest versions. good old FakePCIID + FakePCIID_XHCIMux kexts for USB2.0/USB3.0 multiplexing will be Ok up to Big Sur but need replacing by this version for Monterey. Bear with me and I'll post something soon but if you can't wait, update your setup according to the above.

Not sure it'll make much difference using MBA6,2 or MBP11,1 compared to MBP11,4 for CPU Power Management but you may want to observe this and make some comparison; can be an interesting experiment to make, it certainly used to make a difference on old C2D Merom/Penryn laptops.

Absolutely, HD 5500 iGPU of i7-5500U carries device id 0x1616 (i.e. PCI id 8086:1616). Aso, Whatevergren's default BDW framebuffer layout being 0x16260006 for Broadwell mobile graphics, it's not necessary to specify that either with SMBIOS MBP12,1. See the WEG user manual: Re: audio, you inject full AppleALC kext that goes with Lilu. Recommendation is to use latest versions of the kexts. How did you establish that audio was ALC290? If in doubt, remove AppleALC and replace, even if only temporarily, with VoodooHDA (+AppleHDADisabler accompanying kext). You may then check the audio codec in Hackintool or, better, DPCIManager app. https://github.com/MuntashirAkon/DPCIManager

Support for old Tesla cards stopped at High Sierra. No drivers were provided in subsequent macOS versions. The patch was a pretty easy thing in Mojave and early versions of Catalina up to 10.15.3. From 10.15.4, Apple changed things and the patch required to adjust/change many additional things (to cover for issues such as AMFI). See my (old) D630 guide for instance. From 10.15.4 onwards, you'll need to use special patching tools such as dosdude1's Catalina patcher. You need the Tesla patch and the boot arg amfi_get_out_of_my_way=1 to bypass AppleMobileFileIIntegrity (AMFI) to be able to boot Catalina 10.15.4 and subsequent 10.15 updates. https://dosdude1.com/catalina/ For Big Sur & later, you'll need to look for OCLP, which is a much better tool. https://github.com/dortania/OpenCore-Legacy-Patcher/ If your system can run Catalina, you might just go for Big Sur or Monterey and apply the OCLP Tesla patch, that'd probably be better and easier; unless you absolutely need to run old and abandoned Catalina of course.

Please add your system's specs in signature. Looks like your settings are correct: SMBIOS MacBookPro12,1 BDW framebuffer layout if 0x16260006 Re: EDID, as I said, you need to look it up on the web. Extract it with tools/apps such as Monitor Asset Manager, then inject it by adding the following property to the graphics settings of your bootloader's config: AAPL00,override-no-connect <XXXXXXXXX> DATA where <XXXXXXXX> is your 20bytes (or so) EDID info in one long consecutive hexadecimal string. See the WhateverGreen user manual. PS: Thanks for the donation offer. You can do this off the main page, there's a button for it.

I don't know what you mean by "bad screen refresh" but, yes, you indeed have a display issue with your Hackintosh build. I've modified your thread title to properly reflect the problems you've mentioned. 2 x possible causes to your screen problem: wrong configuration (you do not inject the correct settings for HD5500 and/or wrong SMBIOS) you need to inject your screen's EDID information (you can look this up on the Web: how to extract and how to inject in macOS through bootloader's property). It's very common to require this on HP laptops.

Hello and welcome.