HD P4000 screen garble when spoof with device-id

[kingofnewdays]

Hi, i am try to install big sur in my old PC, if install without device-id, graphic only display 3mb vram, no QE/CI, if I spoof with device-id 66010000 the screen will garble , if i try to screenshot when that happen, i see QE/CI look like worked because topbar was transparent, plz help me fix this screen garble

i am use opencore 0.68

My PC:
CPU : xeon 1245v2
ram: 8gb kingston
GPU: HD P4000 (iGPU of xeon cpu)
Mainboard: P8b75 MLX Plus
output display : DVI (i am use dvi to hdmi to work with my screen)

screen without device-id


screen tearing after use device-id 66010000



but when i managed to login and screenshot, look like QE/CI was working


some one please help, efi was attached please take a look

 

[Edhawk]

Try changing the AAPL,ig-platform-id from 05006201 to 0A006601 (if you haven't already).

There are a few alternative Intel Framebuffers that work with Ivy Bridge Desktop HD4000 IGPU's to drive a display, which might work better with your P4000. You could try each of these in place of your current Framebuffer entry, to see if one works with your system.

Device ID - Framebuffer
0x01660000 - 00006616
0x01660003 - 03006616
0x0166000B - 0B006616

You may need to clear the NVRAM between each change of Framebuffer (from the OC boot screen or picker list), so the old one isn't used from the NVRAM store. You would need to add the ClearNvram tool to your /OC/Tools folder and add an entry to your config.plist. As currently you only have the OpenShell.efi in your Tools folder.

In ages past using FakePCIID.kext and FakePCIID_Intel_HD_Graphics.kext, fixed this issue. It may still work in place of using a fake device-id in your /OC/config.plist.

 

[kingofnewdays]

Try changing the AAPL,ig-platform-id from 05006201 to 0A006601 (if you haven't already).

There are a few alternative Intel Framebuffers that work with Ivy Bridge Desktop HD4000 IGPU's to drive a display, which might work better with your P4000. You could try each of these in place of your current Framebuffer entry, to see if one works with your system.

Device ID - Framebuffer
0x01660000 - 00006616
0x01660003 - 03006616
0x0166000B - 0B006616

You may need to clear the NVRAM between each change of Framebuffer (from the OC boot screen or picker list), so the old one isn't used from the NVRAM store. You would need to add the ClearNvram tool to your /OC/Tools folder and add an entry to your config.plist. As currently you only have the OpenShell.efi in your Tools folder.

In ages past using FakePCIID.kext and FakePCIID_Intel_HD_Graphics.kext, fixed this issue. It may still work in place of using a fake device-id in your /OC/config.plist.

Thank for reply, due to i use opencore with whatevergreen, i was change device-id base on whatevergreen github but nothing work, all the same

WhateverGreen/Manual/FAQ.IntelHD.en.md at master · acidanthera/WhateverGreen

Various patches necessary for certain ATI/AMD/Intel/Nvidia GPUs - acidanthera/WhateverGreen

github.com

Native supported DevIDs :

• 0x0152
• 0x0156
• 0x0162
• 0x0166

after that i try to update bios and enable CSM like other said, the screen look better, but still garble

next i find out that this may be relate with edid, i was try to use this script

A script to fix EDID problems on external monitors in macOS

A script to fix EDID problems on external monitors in macOS - patch-edid.md

gist.github.com

after unplug the screen and re-connect screen, the screen work perfect at resolution 1280x1024, if i change resolution to 1920x1080, the screen will garbled again, have you any idea with this, i want to change it to 1920x1080 or 2k resolution because my monitor is 16:9 screen, if i use 1280x1024 resolution everything is stretch

thank you

 

[Edhawk]

The issue isn't with the Display, but rather the IGPU, so I doubt that EDID script will help. I think you have to disable SIP to get the script working, which isn't always the best option.

What is the device-id of your HD P4000 IGPU(8086:016A)? Look in your IOReg and it will confirm the device-id for your IGPU.

You may need to try one of the Mobile framebuffers with your HD P4000 to see if that changes how if behaves.

0x1660040 - 04006616 is reported to have worked in Clover, along with the device-id=16668086, plus the FakePCIID kexts mentioned in post #2.

Here is a thread from a few years ago regarding the same IGPU issue, but with Clover not OpenCore. Check out pages 2 and 3 in the thread - https://www.tonymacx86.com/threads/solved-intel-hd-graphics-p4000-hd4000.192545/

 

[kingofnewdays]

The issue isn't with the Display, but rather the IGPU, so I doubt that EDID script will help. I think you have to disable SIP to get the script working, which isn't always the best option.

What is the device-id of your HD P4000 IGPU(8086:016A)? Look in your IOReg and it will confirm the device-id for your IGPU.

You may need to try one of the Mobile framebuffers with your HD P4000 to see if that changes how if behaves.

0x1660040 - 04006616 is reported to have worked in Clover, along with the device-id=16668086, plus the FakePCIID kexts mentioned in post #2.

Here is a thread from a few years ago regarding the same IGPU issue, but with Clover not OpenCore. Check out pages 2 and 3 in the thread - https://www.tonymacx86.com/threads/solved-intel-hd-graphics-p4000-hd4000.192545/

thank you, i was tried it but suddent my Graphic card return to 5mb Vram and QE/CI is gone, i think i will try to use clover as that thread said, thank you very much