[GUIDE] General Framebuffer Patching Guide (HDMI Black Screen Problem)

[mehravishay]

I managed to get my display up and running after changing my AAPL,ig-platform-id to 00009B3E on 10.15.5 & got the pink screen. After checking the IOReg I noticed that my HDMI was being flagged as DP. I tried to apply the patch to change framebuffer-conX-type to HDMI but it refuses to change.

Currently it shows a pink screen and keeps going off. The only way to use it is via remote connection.

Any help would be appreciated

 

[mswickley]

Ouch. I am quite stuck at step five of the Preflight Checklist.

The HDMI port on my Gigabyte Z390 Aorus Pro Wifi is the only display port, and I was hoping to sneak by without getting dedicated graphics for budget reasons. As step five suggests, the HDMI port stops working when I boot with accelerated graphics enabled. Since I have no discrete GPU either, I really seem to have no way of getting a display to continue the setup.

I have a MacBook and I've thought of perhaps screen sharing, but I can't seem to enable screen sharing on my Hackintosh without, you know, seeing the screen after I boot.

Is there someone out there who can think of a workaround?

 

[eugene2878]

hi, can someone help me, i've a Asus desktop all in one
Asus Zen AIO z240ic 24" 4k touch
CPU I7 6700T - Intel HD 530 - Geforce GTX960m
Hardisk nvme M2 512GB
Ram DDR4 16GB
Monitor 24" 4k touch
The only way to see desktop is use ig-platform-id 0x19120000 but only 31mb vram, whitout i obtain black screen

Any progress on it?

 

[deeveedee]

@CaseySJ Your first post indicates that adapters (e.g. DP->DVI) should not be used during FB patching. I have found with my HP EliteDesk 800 G4 Mini that using connector-type DigitalDVI with my DP->DVI adapters works perfectly and that framebuffer patching proceeded without issues after I discovered the need to use connector-type DigitalDVI (my system has 3 x DP ports and I use DP->DVI adapters for my displays).

I'm not sure if others have similar experience, but just offering this in case it helps others.

EDIT: Note that when using the DP->DVI adapter, I needed to add device property "no-hda-gfx" to HDEF ( PciRoot(0x0)/Pci(0x1F,0x3) ) in order to prevent AppleALC kernel panic on wake from sleep. You can read more about this in my HP EliteDesk 800 G4 Mini thread.

 

[CaseySJ]

@CaseySJ Your first post indicates that adapters (e.g. DP->DVI) should not be used during FB patching. I have found with my HP EliteDesk 800 G4 Mini that using connector-type DigitalDVI with my DP->DVI adapters works perfectly and that framebuffer patching proceeded without issues after I discovered the need to use connector-type DigitalDVI (my system has 3 x DP ports and I use DP->DVI adapters for my displays).

I'm not sure if others have similar experience, but just offering this in case it helps others.

Added a note in red at the very top of Post #1.

 

[CaseySJ]

Ouch. I am quite stuck at step five of the Preflight Checklist.

The HDMI port on my Gigabyte Z390 Aorus Pro Wifi is the only display port, and I was hoping to sneak by without getting dedicated graphics for budget reasons. As step five suggests, the HDMI port stops working when I boot with accelerated graphics enabled. Since I have no discrete GPU either, I really seem to have no way of getting a display to continue the setup.

I have a MacBook and I've thought of perhaps screen sharing, but I can't seem to enable screen sharing on my Hackintosh without, you know, seeing the screen after I boot.

Is there someone out there who can think of a workaround?

If we fake the iGPU device ID to something like 0x12345678, macOS will use the non-accelerated driver and it may be able to display video through the HDMI port. That may be enough to configure screen sharing...

 

[codedmind]

Hello, can someone please guide me in what i'm doing wrong...

I follow the steps, i have a asus h170-plus with hd 530, my port settings are:
1 -> 0x05 -> hdmi (that i know is mapped for onboard dvi port)
2 -> 0x04 -> hdmi (that i know is mapped for onboard hdmi port)

I always have image if i connect only one monitor:
If i boot connected to dvi port i get image and hackingtool marks 1->0x05 as red
If i boot connected to hdmi port i get image and hackingtool marks 2-> 0x04 as red
If i boot connected to two ports, before login screen the dvi connected monitor turn black and only hdmi monitor keeps working, then in hackingtool only line 2->0x04 is red...

What i'm missing?

 

[deeveedee]

I had a black screen problem after cloning my fully working system to a new NVMe SSD. Solution was to rebuild kextcache after cloning. See full description here.

 

[rob1980]

Working now, I am using the following for my UHD630 Lenovo M720s coffee lake
OC 0.6.0, latest lilu & WEG. 0x3E920000
hackintool shows no connections and all dummy so not sure what's going on there.

This is the only thing to get me past a black screen, thank you!!

 

[tobagin]

Working now, I am using the following for my UHD630 Lenovo M720s coffee lake
OC 0.6.0, latest lilu & WEG. 0x3E920000
hackintool shows no connections and all dummy so not sure what's going on there.

Using this I was able to get the 2 DP and 1 HDMI ports of my Lenovo M720Q Tiny working 100%. Only issue I had was that I had to insert the EDID of my monitor(connected to the main DP) to the config.plist but I think its an issue with my monitor.