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

[andydupont]

If you're using CLOVER, use gen_debug as I've specified here. It automatically scrubs the sensitive info and provides the IORegistry dump.

gen_debug would open IORegistry but was unable to download it. I got the following notice from gen_debug:

"IOREG dump failed. Retrying by increasing delays...
IOREG dump has failed 3 times. Dumping generic IOREG report instead."

I'm attaching the dump. I was booting using the config-DVI-06.plist file. This one mapped the DVI connector to BusID 6.

 

[tedyun]

@andydupont - it doesn't look like you patched the framebuffers correctly.

Try this config.plist, after you repopulate your SMBIOS. I just simply added the patch but I didn't change anything else.

You have a lot of tweaks and switches that I am not sure would be interfering. Like I said, I recommend that you start with pastrychef's EFI as a foundation.

gen_debug would open IORegistry but was unable to download it. I got the following notice from gen_debug:

"IOREG dump failed. Retrying by increasing delays...
IOREG dump has failed 3 times. Dumping generic IOREG report instead."

I'm attaching the dump. I was booting using the config-DVI-06.plist file. This one mapped the DVI connector to BusID 6.

 

[deeveedee]

gen_debug would open IORegistry but was unable to download it. I got the following notice from gen_debug:

"IOREG dump failed. Retrying by increasing delays...
IOREG dump has failed 3 times. Dumping generic IOREG report instead."

I'm attaching the dump. I was booting using the config-DVI-06.plist file. This one mapped the DVI connector to BusID 6.

gen_debug still includes an IOReg dump as a txt file.
Lots of stuff happening in your config.plist. I looked only at config.plist and not other plists. Here are some observations:

1. Unnecessary ACPI patches/renames when you're using WhateverGreen (e.g. don't rename GFX0): Read this
2. Do you need to drop SSDT tables CpuPm and CpuDist?
3. Unnecessary boot args when using WhateverGreen (e.g. no need for -disablegfxfirmware). Read this. Remove these unnecessary boot args AFTER you get Intel graphics acceleration working.
4. Where are your framebuffer patches? Should be in Devices > Properties
5. Do you need Audio->ResetHDA?
6. I don't believe you should enable "UseIntelHDMI" when using WhateverGreen. Read this.
7. You should not be enabling NVidiaWeb
8. Remove NullCPUPowerManagement.kext - not needed with modern CPUs and you've enabled PluginType

 

[andydupont]

deeveedee, tedyun and PastryChef .... Thanks so much for your help. I found the connector patches that PastryChef used on his z390 M Gaming and now have mine working with only those changes. Actually pastrychef had DP on index 1 (Port 5) that I removed because it doesn't exist on the MB. For others struggling to get the correct connections for a Z390 M Gaming they are:

- DVI Index 2 (Port 6) BusID 0x02
- HDMI Index 3 (Port 7) BusID 0x04

I will now do some clean up as suggested by deeveedee, but the system is running fine despite the unneeded settings.

 

[ronimizy]

I have one monitor connected to mobo via DP another via DVI or HDMI, i did configured all the connectors, when monitor connected it highlights red in Hackintool. BUT. The only one connected via DP is displaying image. The other one is kinda here (if i take a screenshot, there are two monitors), but IRL is blacked out.

1 - DVI
2 - HDMI
3 - DP

 

[andydupont]

1. Where are your framebuffer patches? Should be in Devices > Properties

As I mentioned in my post with the dump, the patches were in config-DVI-06.plist
I created three .plists with different Bus IDs using hackintool. It was quicker to keep generating variations rather than creating one and then rebooting twice and juggle around plists to get to the point in hackintool to create a different patch. Clover allow the Option to choose the .plist to be loaded. Hope this makes sense.

 

[deeveedee]

As I mentioned in my post with the dump, the patches were in config-DVI-06.plist
I created three .plists with different Bus IDs using hackintool. It was quicker to keep generating variations rather than creating one and then rebooting twice and juggle around plists to get to the point in hackintool to create a different patch. Clover allow the Option to choose the .plist to be loaded. Hope this makes sense.

Ok - my mistake. For future reference, gen_debug masks only the private data in config.plist. Your other plists expose your private info on a public forum.

 

[andydupont]

Ok - my mistake. For future reference, gen_debug masks only the private data in config.plist. Your other plists expose your private info on a public forum.

Thanks for letting me know. I have deleted the files.

 

[RockArtist]

Quick update. WhateverGreen 1.4.1 is out. official release build to address black screen 10.15.5+ and Comet Lake CPUs/Mobos.

 

[ronimizy]

Quick update. WhateverGreen 1.4.1 is out. official release build to address black screen 10.15.5+ and Comet Lake CPUs/Mobos.

Updated to Catalina, latest kexts, didn't change anything for me