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

[KriptonSecret]

I confirm the copy-pasted config.plist section for "Asus Prime H370M-Plus, ASUS Prime Z390-A, Asus ROG Strix B360-I, and Coffee Lake CPU" works for Asus TUF Z390M-Pro Gaming. The only minor issue - I have to hot-plug or turn off/on the second (hdmi) display in order to make it work after boot.

 

[CaseySJ]

I confirm the copy-pasted config.plist section for "Asus Prime H370M-Plus, ASUS Prime Z390-A, Asus ROG Strix B360-I, and Coffee Lake CPU" works for Asus TUF Z390M-Pro Gaming. The only minor issue - I have to hot-plug or turn off/on the second (hdmi) display in order to make it work after boot.

View attachment 380651

Thanks for reporting compatibility with Asus TUF Z390M-Pro Gaming. I've added this motherboard name to the Spoiler description.

The hot-plug issue is still an issue! Now that we're actually able to activate our HDMI ports hopefully we'll find a solution for hot-plug.

 

[CaseySJ]

Also, with respect to the above, could I manually add flags to convert all possible connectors to HDMI? Something like the config attached?

The Designare Z390 configuration is:

• Index 1 = DP
• Index 2 = DP
• Index 3 = HDMI

Because your motherboard has one 1 port, you could try something like this (with Platform ID 0x3E9B0007):

• Index 1 : BusID 0x04, Type HDMI
• Index -1 : BusID 0x00, Type DUMMY
• Index -1 : BusID 0x00, Type DUMMY

If this fails then try:

• Index 2 : BusID 0x04, Type HDMI
• Index -1 : BusID 0x00, Type DUMMY
• Index -1 : BusID 0x00, Type DUMMY

If this also fails then try:

• Index 3 : BusID 0x04, Type HDMI
• Index -1 : BusID 0x00, Type DUMMY
• Index -1 : BusID 0x00, Type DUMMY

There's a good (but not 100%) chance that one of these will work. But if not, you would have to repeat the three trials by replacing BusID 0x04 with 0x01 or 0x06.

 

[kundhali]

Casey,

Thanks for the response. Im a bit new to this, but I can use hackintool (v1.7.7) to build the xml language for these patches, correct?

 

[CaseySJ]

Casey,

Thanks for the response. Im a bit new to this, but I can use hackintool (v1.7.7) to build the xml language for these patches, correct?

Correct, but v1.7.7 has a problem where it does not highlight video connectors in red. So if you can find an earlier version please use that for the time being.

 

[kundhali]

Will do, thanks. Also, just so I am clear, when adding these entries into the Properties section of Devices the "ig-platform-id" entry should be deleted from "Graphics"? I was using a generic entry to boot and access hackintool. The code from my Graphics section that allows me to boot is shown below.

<key>Graphics</key>
<dict>
<key>Inject</key>
<dict>
<key>ATI</key>
<false/>
<key>Intel</key>
<false/>
<key>NVidia</key>
<false/>
</dict>
<key>ig-platform-id</key>
<string>0x59120003</string>
</dict>

 

[CaseySJ]

Will do, thanks. Also, just so I am clear, when adding these entries into the Properties section of Devices the "ig-platform-id" entry should be deleted from "Graphics"? I was using a generic entry to boot and access hackintool. The code from my Graphics section that allows me to boot is shown below.

<key>Graphics</key>
<dict>
<key>Inject</key>
<dict>
<key>ATI</key>
<false/>
<key>Intel</key>
<false/>
<key>NVidia</key>
<false/>
</dict>
<key>ig-platform-id</key>
<string>0x59120003</string>
</dict>

Yes we should remove it from Graphics in order to avoid a conflict. Because you have only one port and it happens to be HDMI (hence black screen) you could install TeamViewer or some other remote screen sharing application and login through another PC!

 

[kundhali]

Yes we should remove it from Graphics in order to avoid a conflict. Because you have only one port and it happens to be HDMI (hence black screen) you could install TeamViewer or some other remote screen sharing application and login through another PC!

Alright, so my USB drive got a bit of a workout. I systematically tried every option presented, but was unsuccessful. The results of these tests and an example of the config I have been using are below. Any thoughts on how I should proceed? I suspect there is some option in my config that I am overlooking? Or perhaps I am patching something incorrectly.

i7-8700k
Intel UHD 630
Gigabyte Z390 Aorus Elite
Hackintool v1.7.7
PlatformID: 0x3E9B0007
Device ID: 0x3E92


BusID: 0x04 / BAAAAA==
Index 1 / AQAAAA==: Apple Loading Screen -> Black Screen
Index 2 / AqAAAA==: Apple Loading Screen -> Black Screen
Index 3 / AwAAAA==: Apple Loading Screen -> Hangs during loading

BusID: 0x01 / AQAAAA==
Index 1 / AQAAAA==: Apple Loading Screen -> Black Screen
Index 2 / AqAAAA==: Apple Loading Screen -> Black Screen
Index 3 / AwAAAA== Apple Logo -> Stop Sign

BusID: 0x06 / BgAAAA==
Index 1 / AQAAAA==: Apple Loading Screen -> Black Screen
Index 2 / AqAAAA==: Apple Logo -> Stop Sign
Index 3 / AwAAAA==: Apple Loading Screen -> Black Screen

 

[Lansmac]

Spoiler: Gigabyte H370M-DS3H and Coffee Lake CPU
Row 1: Index 1, BusID 0x05, Type DP
Row 2: Index 2, BusID 0x06, Type DVI-D <-- may not be operational
Row 3: Index 3, BusID 0x04, Type HDMI

Thanks for all the tips!!
So, DVI may not be operational, that's my problem. Anyone more info on this? Can we make it operational somehow?
Also hdmi works only when you plug it in, not when you restart. Then you have to take it out and plugin again.
I am making the Mac for someone with a disability, so it's important to get the hdmi working all the time...
Hope anyone has more info on this for the H370M DS3H!

 

[fixpol]

Hi,
I was trying above method with my hd 530 ASrock h170 mainboard with only two outputs DVI and HDMI. DVI works fine using both platform id 19120000 and 193B005. HDMI turns black during booting. FB patch installed due to manual above but no result.My connectors always look same after patching.