Contribute
Register

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

Can you take a video of the boot process with your smartphone? Because verbose mode is enabled, the log messages might provide a clue.

Finally I used an old eGPU (with VGA port) to see what error I was giving. This is the screenshot.
 

Attachments

  • IMG_3211.jpg
    IMG_3211.jpg
    1.7 MB · Views: 66
Finally I used an old eGPU (with VGA port) to see what error I was giving. This is the screenshot.
Apologies for the late reply. Seems I get immersed in the Z390 Designare build thread and forget to check this one...

Anyway, there's no indication of a problem in the screenshot, but we do see this problem (gIOScreenLockState). Because of the 46MB size of the video in your previous post, I'll set a reminder to check it this evening from home.
 
Thanks for this guide and also to this guide I was able to fix the no HDMI output problem.

But now my problem is when I hot unplug the HDMI from my laptop (external monitor is powered ON while unplugging), my laptop monitor turns black screen only (laptop is still functioning normally,I think...) , I tried closing the LID then open again to see if the display will go back to normal but nothing happens, so I have no choice but to turn OFF and ON again my laptop. After restart and login I connect again my laptop to the external monitor thru HDMI then I tried to cold unplug the HDMI from my laptop (external monitor is powered OFF while unplugging), the display on my laptop return as normal. Now I'm confused which part I did wrong.

I am running macOS High Sierra 10.13.6
The Nvidia MX150 powers the built-in LCD screen on your laptop. The iGPU powers the external video ports. Your system therefore has 2 GPUs at 2 different PCIe device paths.

Let's start by reviewing the framebuffer connector patch you applied to enable HDMI. Please post a screenshot of the Hackintool Patch --> Connectors page showing the settings that were applied.
 
Apologies for the late reply. Seems I get immersed in the Z390 Designare build thread and forget to check this one...

Anyway, there's no indication of a problem in the screenshot, but we do see this problem (gIOScreenLockState). Because of the 46MB size of the video in your previous post, I'll set a reminder to check it this evening from home.


Don't worry, when you can :angel:

One question I have is why I fake my device id at 0x3e9b if my i5 9600k device id is 0x3e92. I know that 0x3e92 is headless, but I don't understand why.

I would appreciate if you could explain it to me. Thanks!
 
Don't worry, when you can :angel:

One question I have is why I fake my device id at 0x3e9b if my i5 9600k device id is 0x3e92. I know that 0x3e92 is headless, but I don't understand why.

I would appreciate if you could explain it to me. Thanks!
The 9th Gen Intel processors were first supported natively in MacOS 10.14.4. Prior to that we had to spoof the iGPU device ID, but not anymore. We should in fact delete that parameter so that MacOS auto-detects it as 0x3E98 (not 0x3E92). Additionally, “platform ID” determines whether the IGPU operates in headless mode or normal mode. Platform ID 0x3E980003 is the correct headless platform ID for 9th Gen CPUs.
 
Don't worry, when you can :angel:

One question I have is why I fake my device id at 0x3e9b if my i5 9600k device id is 0x3e92. I know that 0x3e92 is headless, but I don't understand why.

I would appreciate if you could explain it to me. Thanks!
I reviewed the video and the problem is the classic HDMI Black Screen problem! So you've come to the right place, but it seems we may need to use the DisplayPort cable. Have you received the DisplayPort to HDMI cable from Amazon? If so, does the system boot up properly with the EFI/CLOVER folder I provided earlier?
 
one my configuration

i need more information to improve this. is this correct ?



<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
<key>AAPL,GfxYTile</key>
<data>
AQAAAA==
</data>
<key>AAPL,ig-platform-id</key>
<data>
AAASGQ==
</data>
<key>AAPL,slot-name</key>
<string>Internal</string>
<key>device-id</key>
<data>
EhkAAA==
</data>
<key>device_type</key>
<string>Display controller</string>
<key>enable-hdmi-dividers-fix</key>
<data>
AQAAAA==
</data>
<key>enable-hdmi20</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con1-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con1-pipe</key>
<data>
EgAAAA==
</data>
<key>framebuffer-con1-type</key>
<data>
AAgAAA==
</data>
<key>framebuffer-con2-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con2-index</key>
<data>
/////w==
</data>
<key>framebuffer-con2-pipe</key>
<data>
EgAAAA==
</data>
<key>framebuffer-con2-type</key>
<data>
AAgAAA==
</data>
<key>framebuffer-con3-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con3-index</key>
<data>
/////w==
</data>
<key>framebuffer-con3-pipe</key>
<data>
EgAAAA==
</data>
<key>framebuffer-fbmem</key>
<data>
AACQAA==
</data>
<key>framebuffer-patch-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-portcount</key>
<data>
AgAAAA==
</data>
<key>framebuffer-stolenmem</key>
<data>
AAAwAQ==
</data>
<key>framebuffer-unifiedmem</key>
<data>
AAAAgA==
</data>
<key>hda-gfx</key>
<string>onboard-2</string>
<key>model</key>
<string>ATI radeon RX580</string>
</dict>

thanks
 
I reviewed the video and the problem is the classic HDMI Black Screen problem! So you've come to the right place, but it seems we may need to use the DisplayPort cable. Have you received the DisplayPort to HDMI cable from Amazon? If so, does the system boot up properly with the EFI/CLOVER folder I provided earlier?

I received it. But the system doesn't start correctly (black screen).
 
The Nvidia MX150 powers the built-in LCD screen on your laptop. The iGPU powers the external video ports. Your system therefore has 2 GPUs at 2 different PCIe device paths.

Let's start by reviewing the framebuffer connector patch you applied to enable HDMI. Please post a screenshot of the Hackintool Patch --> Connectors page showing the settings that were applied.

When I boot into windows and check the display settings it says that both my laptop display and external monitor are UHD 620.

Please see the screenshot of my Patch > Connectors settings
 

Attachments

  • Screen Shot 2019-08-22 at 10.55.55 PM.png
    Screen Shot 2019-08-22 at 10.55.55 PM.png
    3.5 MB · Views: 85
I received it. But the system doesn't start correctly (black screen).
  • When the black screen problem occurs, are you able to ping your system from another machine on the same network?
  • Do you have Remote Desktop or screen sharing software that you can use to remotely login to the Hack while the black screen is displayed?
I'm trying to determine whether your system:
  1. Crashes --> and thus displays black screen
  2. Continue to work --> but HDMI/DP output is turned off
If your system continues to work, it means that we haven't yet determined the correct BusID and Type for the various connectors. A Remote Desktop application can be very help so we can login to the machine remotely (while black screen is occurring) and run IORegistryExplorer and/or Hackintool.

If you don't have screen sharing software or experience with such applications, the only alternative is to try various combinations of BusID and Type until one of the combinations works.

Also, the use of an adapter or converter is absolutely not recommended during this procedure. In other words, we should use an HDMI-to-HDMI cable (computer and monitor must both be connected via HDMI) or a DP-to-DP cable (computer and monitor must both be connected via DP).

A DP-to-DP connection should almost always work without any frame buffer patch.
 
Last edited:
Back
Top