Contribute
Register

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

Thank you for answer. I correct Clover config and play with it. I fix some issues with USB3.0, rebooting, shutdown & etc. but I still cannot get output on HDMI. here is log (FBHDMICON) and updated CLOVER.


@Hex0S,

In your config.plist you are using PlatformID 0x3EA50009 which is not for UHD 630 IGPU :-

Code:
ID: 3EA50009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00830B0A
TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes)
GPU Name: Intel Iris Plus Graphics 655
Model Name(s):
Camelia: V3
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - LVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000001C7 - DP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000001C7 - DP
00000800 02000000 98000000
01050900 00040000 C7010000
02040A00 00040000 C7010000


A better match would be PlatformID 0x3E9B0009 which is for Mobile UHD 630 IGPU :-

Code:
ID: 3E9B0009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0083130A
TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes)
GPU Name: Intel UHD Graphics 630
Model Name(s):
Camelia: V3
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - LVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - DP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - DP
00000800 02000000 98000000
01050900 00040000 87010000
02040A00 00040000 87010000


You will then need to configure one of the the DP connectors as a HDMI port using the guide in post #1 :-



I dont have a Coffee Lake Mobile system to test with, but that is what i would do ...

Why do you have UHD 630 + HD 530 defined in your Hardware Profile ?, does not make any sense ....

Cheers
Jay
 
Last edited:
@Hex0S,

In your config.plist you are using PlatformID 0x3EA50009 which is not for UHD 630 IGPU :-

Code:
ID: 3EA50009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00830B0A
TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes)
GPU Name: Intel Iris Plus Graphics 655
Model Name(s):
Camelia: V3
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - LVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000001C7 - DP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000001C7 - DP
00000800 02000000 98000000
01050900 00040000 C7010000
02040A00 00040000 C7010000


A better match would be PlatformID 0x3E9B0009 which is for Mobile UHD 630 IGPU :-

Code:
ID: 3E9B0009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0083130A
TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes)
GPU Name: Intel UHD Graphics 630
Model Name(s):
Camelia: V3
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - LVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - DP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - DP
00000800 02000000 98000000
01050900 00040000 87010000
02040A00 00040000 87010000


You will then need to configure one of the the DP connectors as a HDMI port using the guide in post #1 :-



I dont have a Coffee Lake Mobile system to test with, but that is what i would do ...

Why do you have UHD 630 + HD 530 defined in your Hardware Profile ?, does not make any sense ....

Cheers
Jay
Jay, I have UHD 630 + AMD 530, but idk why "AMD" is gone. My current PlatformID is 0x3E920000 (Hackintool && DPCIManager said me that.) I already follow that guide, but I may did some mistakes.
Снимок экрана 2019-11-02 в 0.16.24.pngСнимок экрана 2019-11-02 в 0.17.21.png
 
Jay, I have UHD 630 + AMD 530, but idk why "AMD" is gone. My current PlatformID is 0x3E920000 (Hackintool && DPCIManager said me that.) I already follow that guide, but I may did some mistakes.


@Hex0S,

Is this a Lenovo Desktop or Laptop system ?

Cheers
Jay
 
@Hex0S,

Is this a Lenovo Desktop or Laptop system ?

Cheers
Jay
It is monoblock. I think, it based on laptop hardware. I have one HDMI in and one HDMI out on it. HDMI in , I think, is not part of motherboard, it is part of LVDS display.
kernel WhateverGreen: igfx @ SC: AdvSeekI2COverAUX() Error: Failed to start the I2C transaction. Return value = 0xe00002d6.
kernel WhateverGreen: igfx @ SC: AdvReadI2COverAUX() Error: Failed to set the data offset.
kernel WhateverGreen: igfx @ SC: LSPCON::probe() Error: [FB1] Failed to read the LSPCON adapter info. RV = 0xe00002d6.
kernel WhateverGreen: igfx @ SC: fbSetupLSPCON() Error: [FB1] Failed to probe the LSPCON adapter.
kernel WhateverGreen: igfx @ SC: fbSetupLSPCON() Error: [FB1] Abort the LSPCON driver initialization.
 
@Hex0S,

Is this a Lenovo Desktop or Laptop system ?

Cheers
Jay
This is Lenovo Thinkcentre Monoblock. It has only one HDMI out and one HDMI in (I think it not from motherboard.)
kernel WhateverGreen: igfx @ SC: AdvSeekI2COverAUX() Error: Failed to start the I2C transaction. Return value = 0xe00002d6.
kernel WhateverGreen: igfx @ SC: AdvReadI2COverAUX() Error: Failed to set the data offset.
kernel WhateverGreen: igfx @ SC: LSPCON::probe() Error: [FB1] Failed to read the LSPCON adapter info. RV = 0xe00002d6.
kernel WhateverGreen: igfx @ SC: fbSetupLSPCON() Error: [FB1] Failed to probe the LSPCON adapter.
kernel WhateverGreen: igfx @ SC: fbSetupLSPCON() Error: [FB1] Abort the LSPCON driver initialization.
 
This is Lenovo Thinkcentre Monoblock. It has only one HDMI out and one HDMI in (I think it not from motherboard.)


@Hex0S,

I'm not familiar with that system/model at all ... is it some sort of All-In-One (AIO)?

You say it has a AMD HD 530 dGPU ... it could be that the HDMI out port is driven by the dGPU (a common configuration in some other Lenovo systems), the only way to find out for sure is to try and find a schematic for the system .. (maybe in a service manual) the fact that the system has a HDMI in makes me suspect that this is the case.

If the HDMI Out is connected to the IGPU then it should be possible to get it working, if the HDMI Out is connected to the dGPU then your out of luck as unfortunately AMD HD 530 is not supported in MacOS.

I would try and conform which GPU the HDMI port is connected to before going any further.

Cheers
Jay
 
Hi Casey, et al,

Asrock Fatal1ty Z379 Gaming-ITX/AC
I7-8700(nonK) @ 3.20
Intel 630, NO DGPU
32GB RAM
OSX 10.14.2

EDIT: The "CRASHESONBOOT" config.plist file I posted earlier won't open in Clover Configurator. IT gives me an 'unexpected EOF' error. I then re-inserted the patch using the text mode in Clover Configurator. The computer now boots to the login screen, and the green flicker shows up a few seconds after I've logged in (using the KVM). That newest config.plist is now attached to this post as noted below.

Forgive me if this post sprawls a little bit, I need to describe the underlying issue that brought me to this thread in order to give full context to my issues. I'll try to describe everything as clearly as possible.

The underlying gremlin that I'm *hoping* a patched frame buffer will fix - this computer works great when directly connected to a monitor via Displayport, HDMI, or both at the same time. When I try and use my fancy Displayport KVM (Belkin F1DN104Q-3, which is DP input and HDMI output for some confusing reason), the Hack outputs a video signal plagued by an awful green flicker as shown in this video I posted
that makes it unusable. The Hack boots via clover and Verbose mode seemingly OK, but the flicker shows up as soon as the login screen comes up. I've tried both real Macs and Windows PC's, and they work great with this KVM. Only the Hack has this issue with the KVM. (as a background, this KVM is one of the only ones I found that offer quad monitor support, which I don't need for the Hack, per se, but my windows machine at this desk is my CAD/rendering workstation, which is 3 monitors, so I needed this otherwise overkill KVM)


I'm unable to follow the guide verbatim for the following reasons:
- Hackintool 2.8.6 is newer/different layout, and has more options in the General & Advanced Patch tabs, such as "EDID" & "Use Intel HDMI"
- Hackintool won't let me select/save the patched config.plist in EFI/CLOVER. It's greyed out, so I manually pasted the patch text into my config.plist via bbedit.

When following the guide, In the connectors tab, I plug around with my monitors (directly connected, not via the KVM) and look at my connectors tab, both my DP and HDMI seem to be showing up correctly.

A couple side notes:

If, without finishing the Hackintool patch from this guide, I ONLY change the device ID from 0x0 to 0x3E92 using Clover Configurator, the system boots, and DP video works as I want it to via my KVM, BUT it's unaccelerated and buggy.

I've also tried all the different Darkwake settings in Clover, hoping that that was the problem. I think it's somewhat related, because a couple of the Darkwake settings allowed the Hack to work via the KVM as I wanted, but sleeping botched it, or it was inconsistent in working/not upon boot or wake.

I've attached screenshots of my Hackintool settings, as well as three config.plist files. "GREEN_FLICKER" is the file that boots, and works great with directly connected monitors, but not with my fancy KVM. "config-PATCHED_GREENFLICKER_UPON_LOGIN" is the one with the patched Framebuffer from Hackintool. "no-greenflicker-NO_acceleration" is the one with the device ID changed to 0x3e92

I've been playing around with some other settings, but my head is spinning with all the options (I'm definitely not a coder ; ), so I'm hoping that there's an obvious fix to my gremlin, and that I've been concise enough in my description to provide enough info to help.

Thanks!!!

AJ
 

Attachments

  • config-GREEN_FLICKER_VIA_KVM-11-7-19.plist
    8.5 KB · Views: 83
  • PATCH_GENERAL.png
    PATCH_GENERAL.png
    103.3 KB · Views: 85
  • Connectors.png
    Connectors.png
    141.5 KB · Views: 90
  • PATCH_ADVANCED.png
    PATCH_ADVANCED.png
    154.6 KB · Views: 82
  • config-nogreenflicker-NO_acceleration.plist
    8.5 KB · Views: 104
  • config-PATCHED_GREENFLICKER_UPON_LOGIN.plist
    8.4 KB · Views: 64
Last edited:
@CaseySJ, thanks for the guide, I have two connectors from my motherboard HDMI & VGA. HDMI is working, but VGA has no output. Just want to ask if it is possible to work with my VGA, need your help...regards!
 
Hi Casey, et al,

Asrock Fatal1ty Z379 Gaming-ITX/AC
I7-8700(nonK) @ 3.20
Intel 630, NO DGPU
32GB RAM
OSX 10.14.2
...
I'm unable to follow the guide verbatim for the following reasons:
- Hackintool 2.8.6 is newer/different layout, and has more options in the General & Advanced Patch tabs, such as "EDID" & "Use Intel HDMI"
- Hackintool won't let me select/save the patched config.plist in EFI/CLOVER. It's greyed out, so I manually pasted the patch text into my config.plist via bbedit.
Hello @ajemutt

Even though you'll see grayed-out config.plist when exporting a patch, Hackintool will still export the patch to that grayed-out file! We just need to click on the file anyway and export the patch.

The ASRock Fatal1ty Z390 Gaming-ITX/AC needs these settings (from Post #1, Compilation of Patches...):

Screen Shot 2019-11-14 at 4.44.27 AM.png

I've entered these patched into your config.plist (attached). Please give it a try...
 

Attachments

  • config-patched.plist
    10.7 KB · Views: 85
@CaseySJ, thanks for the guide, I have two connectors from my motherboard HDMI & VGA. HDMI is working, but VGA has no output. Just want to ask if it is possible to work with my VGA, need your help...regards!
Have you followed the Guide in Post #1? If so, which rows turn red in Hackintool?
 
Back
Top