Leaderboard

You don't understand, no support for Intel iGPU before Kaby Lake generation. The trick of using Kaby Lake framebufffer and faking KBL iGPU id only works for Skylake because KBL is a small evolution or optimization of SKL (Skylake microarchitecure is shared by subsequent Intel generations up to Comet Lake). This trick does not work for older iGPUs such as Haswell or Broadwell though and it's not bug free on Skylake.

You must have missed the minimum requirements... https://osxlatitude.com/articles/news/macos-13-ventura-unveiled-r61/ https://osxlatitude.com/forums/topic/17292-macos-ventura-130-beta1-early-feedback-and-findings/ Broadwell iGPU is not supported and patches may never be provided. Ventura only officially supports Kaby Lake iGPUs and later and provides no driver whatsoever for older generations. You can go back to Monterey and stick to it.

As stated and shown at Applelife & InsanelyMac, works with OpenCore + AvoidRuntimeDefrag=No. Not sure about the need to add -lilubetaall boot arg. Boot loop with Clover (r5142) for the moment on my E7270 Skylake laptop with same config as used for Big Sur and Monterey, only SMBIOS changed to MBP14,1. I confirm that support for Haswell, Broadwell and Skylake iGPU is dropped, the only graphics framebuffers available in /S/L/E being KBL, CFL and ICL ones. For AMD, all GPUs older than Polaris generation are dropped. AppleIntelCPUPowerManagement is dropped too, something we still required on good old C2D, C2Q, 1st gen Core, Sandy Bridge and Ivy Bridge platforms so that could add a few nails in their coffin.

'working on my Clover setup and manage to significantly reduce the freezes though not entirely. Sometimes, system still freezes a few seconds after reaching desktop. But it seems to run pretty stable most of the time. Graphics acceleration is acceptable at this stage though not bug free: occasional slow movements on screen and some contents leftovers after closing a window for instance. Or unrecoverable limping system of complete freeze after attempting to watch a Youtube video in Safari. But, hey, what can we expect out of a KBL framebuffer on a Skylake system? Other than than, everything appears to work properly on the E7270: graphics acceleration: Ok with some defects and reduced/degraded performance brightness control: Ok touchscreen: Ok HDMI output: Ok mini-DP output: Ok audio (incl. DP audio): Ok LAN: Ok wireless & Bluetooth (BCM9460CS2): Ok touchPad: Ok USB ports: Ok sleep & wake: Ok SD card reader: Ok Whether this ends up sustainable in the long run for Skylake laptops remains to be seen but you never know... Is it usable for the time being? Clearly not. Edit: Instant wake issue on sleep and HDMI output now sorted. EFI_Clover_r5146_E7270_13.0.b1.zip EFI_Clover_r5146_E7270_13.0.b1_v2.zip EFI_Clover_r5146_E7270_13.0.b1_v3.zip EFI_Clover_r5146_E7270_13.0.b1_v4.zip

As suggested by @aben at IM, I experimented with KBL framebuffer settings on my Skylake/HD520 Latitude E7270. I also updated all add-on kexts to latest versions (Lily & PlugIns) and replaced good old ACPIBatteryManager + FakeSMC by their VirtualSMC equivalent. This allowed me to boot Ventura b1, complete 1st boot setup and reach desktop; the laptop still freezes shortly afterwards so something's still iffy but at least I can boot and with apparent full graphics acceleration: I don't know about older generations but there seems to be hope for Skylake laptops.

Ventura b1 installation completed after updating Clover to r5146. But E7270 struggling to even complete 1st boot setup due to lack of graphics acceleration so I can't even finish that and reach Ventura desktop. So, unless you have a Kaby Lake/HD615 laptop minimum, no point wasting your time until an eventual patch is made available...