Jump to content

Can’t Patch graphics with OCLP on Intel intel hd graphics 4400 ventura


11 posts in this topic

Recommended Posts

I have installed Ventura 13.2 (22D49) on a Dell latitude 3440 - intel hd graphics 4400 OC.0.8.9

Successfully installed but can't patch with OCLP
The Start Root Patching button cannot be pressed. How do I fix it?

 

https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1008?fbclid=IwAR1_DlaUkuQOH_baIWOYHLUEZViY7CjocLw5G-yE47ELkdCAmQDPUVurpj0

 

 

Screenshot 2566-02-01 at 12.12.40.png

Screenshot 2566-02-01 at 12.13.26.png

Screenshot_2566-02-01_at_12_14_09.jpg

Edited by diamondhackintosh
Link to comment
Share on other sites

OCLP tries to automatically detect what patches are needed by device ID/devices that exist within your system. Because OCLP mostly looks at devices that exist in apple devices, it doesn't look for the HD 4400 as it was never in any apple devices.
You likely need to spoof the device ID anyway to get the graphics kexts to work (even after OCLP patched them in), so it is probably worth seeing if you can set your device-id to match one of those listed in the link above.

Edited by 1Revenger1
  • Like 2
Link to comment
Share on other sites

20 minutes ago, 1Revenger1 said:

OCLP tries to automatically detect what patches are needed by device ID/devices that exist within your system. Because OCLP mostly looks at devices that exist in apple devices, it doesn't look for the HD 4400 as it was never in any apple devices.
You likely need to spoof the device ID anyway to get the graphics kexts to work (even after OCLP patched them in), so it is probably worth seeing if you can set your device-id to match one of those listed in the link above.

 

Thanks a lot, I'll try it out.

Link to comment
Share on other sites

Do you have Whatever green or have an ACPI patch to rename the iGPU device to IGPU? Looking a bit closer, it seems like OCLP checks the ioregistry to detect the device, and it specifically looks for devices named IGPU with the right device id. Whatever green will rename it automatically. The device id you have set currently looks fine.

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...
On 2/1/2023 at 8:47 AM, diamondhackintosh said:

I still have no luck I don't know if I set this up correctly or not.
I've attached the EFI, just in case it's useful.

i use MacbookPro 14,1 My smbios

 

EFI

 

 

Config_plist_-_for_Official_OpenCore__0_8_8_Release_Configuration_.jpg

 

like that it's ok !!!!image.png.a7d6b8778eb85db5d0cace231205b9e0.png

 

image.thumb.png.fb99d6864678ba650ac4289f64a8b5e2.png

  • Like 2
Link to comment
Share on other sites

  • 3 weeks later...
On 2/23/2023 at 10:44 AM, arcade33 said:

 

like that it's ok !!!!image.png.a7d6b8778eb85db5d0cace231205b9e0.png

 

image.thumb.png.fb99d6864678ba650ac4289f64a8b5e2.png

 

 

Hello,

Is it Haswell?

Which SMBIOS did you choose?

Is Metal working? (are you able to set "Deriva" as screensaver, just for example...?)

Let me know

Link to comment
Share on other sites

8 hours ago, Iceman said:

 

 

Hello,

Is it Haswell?

Which SMBIOS did you choose?

Is Metal working? (are you able to set "Deriva" as screensaver, just for example...?)

Let me know

yes is an Haswell processor 

smbios 15.2 macbook pro 

metal is working and also DERIVA as Screensaver 

Link to comment
Share on other sites

i have a strange behaviour, because system is graphic accelerated, but any "metal" thing is freezing the system.

After tried different platform-id, i realized the most important flag is "framebuffer-cursormem", because without it, i can't open neither "Terminal" (freezing suddenly on click... Safari too, for example)

On bios i switched AUTO to 64MB, but i don't know how important it is... because i set even framebuffer-stolenmem/framebuffer-fbmem    

Link to comment
Share on other sites

  • 4 weeks later...

Just to let you (all) know, i solved by changing CPU... my i3-4150 had HD4400 that has glitching (choosing, for example, Drift as screensaver, the system freeze for a couple of seconds).

No mem patches has worked... i really tried EVERY SINGLE ONE...

Leaving 128MB share size on BIOS (exactly how it was when trying with i3), without making anything else,  and just switching CPU to an i5-4460, everything works perfect now... because this CPU has HD4600

I upgraded my Catalina system installed previously with the i3, straight to Monterey and everything went better than making it on a real Mac 😂

Edited by Iceman
Link to comment
Share on other sites

 Share

×
×
  • Create New...