Just a heads up Intel FB-Patcher has been renamed to Hackintool and the next release will include EDID patching from Andy Vandijck's FixEDID. You can try out a pre-release of it from
here but FYI it hasn't been tested much yet.
Good news, Headkaze.
I tried to use the new version in
another Hackintosh I am trying to put back to work. It's an ASUS H110T, i3 6100 8GB RAM simple system, with 10.13.6 (which was working perfectly with clover and tools available when 10.13.6 come out - for a stupid reason I updated clover, and can't get it back to work again).
I can get accelerated HD530 4K graphics with Lilu+Whatevergreen with ig-platform-id 0x193B0000 (Device ID 0x1912), but most of the time no image on the DP display. Never after boot up, but after switching back and forth my KVM switch, a picture appears on the display. Sometimes for just 1 second, but once or twice picture was stable enough to work for more than one hour. Today flickering was terrible, and only able to work through Screen Sharing.
These are how Connectors are before and after patching Index for each connector.
On Devices-Properties I also inject EDID, even though I don't think the problem is there.
On the new tab for Displays and EDID, I exported DisplayEDID.kext, DisplayVendorID-5e3 directory and a bin file. I put DisplayVendorID-5e3 into System/Library/Displays/Overrides (directory that didn't exist and I had to create).
After rebooting, system gets to login screen with no display on monitor, I can see it on Screen Sharing, and then hangs. Completely. I had to reboot into Clover Shell and delete Overrides directory to get be able to reboot and access it remotely.
I am also following this thread:
[GUIDE] General Framebuffer Patching Guide (HDMI Black Screen Problem) and will understand if change Bus Id will have any positive impact on my problem.
Looking into some other places, I find errors I cannot interpret:
Code:
2019-01-14 23:42:27.558097+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - GetThermalCompensationAttributes: can't get framebuffer red gamma scaling factor on port 19459 (e00002d7)
2019-01-14 23:42:27.558099+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - GetThermalCompensationAttributes: can't get framebuffer green gamma scaling factor on port 19459 (e00002d7)
2019-01-14 23:42:27.558099+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - GetThermalCompensationAttributes: can't get framebuffer blue gamma scaling factor on port 19459 (e00002d7)
2019-01-14 23:42:27.559520+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - GetThermalCompensationAttributes: can't get framebuffer red gamma scaling factor on port 14607 (e00002d7)
2019-01-14 23:42:27.559522+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - GetThermalCompensationAttributes: can't get framebuffer green gamma scaling factor on port 14607 (e00002d7)
2019-01-14 23:42:27.559523+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - GetThermalCompensationAttributes: can't get framebuffer blue gamma scaling factor on port 14607 (e00002d7)
2019-01-14 23:42:27.561100+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - GetThermalCompensationAttributes: can't get framebuffer red gamma scaling factor on port 16399 (e00002d7)
2019-01-14 23:42:27.561102+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - GetThermalCompensationAttributes: can't get framebuffer green gamma scaling factor on port 16399 (e00002d7)
2019-01-14 23:42:27.561103+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - GetThermalCompensationAttributes: can't get framebuffer blue gamma scaling factor on port 16399 (e00002d7)
2019-01-14 23:42:32.071941+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - ColorSyncUtilsUpdateDisplayProfiles display profile info list is NULL
2019-01-14 23:42:32.098448+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - ColorSyncUtilsUpdateDisplayProfiles display profile info list is NULL
2019-01-14 23:42:32.145584+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - ColorSyncUtilsUpdateDisplayProfiles display profile info list is NULL
2019-01-14 23:42:32.626621+0000 localhost WindowServer[207]: (CoreDisplay) <CoreDisplay> [ERROR] - ColorSyncUtilsUpdateDisplayProfiles display profile info list is NULL
=======
After a new boot
2019-01-15 00:35:23.518878+0000 0x49a Fault 0x0 0 0 kernel: (IOAcceleratorFamily2) bool IOAccelDisplayPipe2::init_framebuffer_resource(IOAccelResource2 *): getPixelInformation for framebuffer 2 failed
2019-01-15 00:35:26.605243+0000 0x49a Fault 0x0 0 0 kernel: (IOAcceleratorFamily2) bool IOAccelDisplayPipe2::init_framebuffer_resource(IOAccelResource2 *): getPixelInformation for framebuffer 2 failed
2019-01-15 00:35:27.027596+0000 0x49a Fault 0x0 0 0 kernel: (IOAcceleratorFamily2) bool IOAccelDisplayPipe2::init_framebuffer_resource(IOAccelResource2 *): getPixelInformation for framebuffer 2 failed
2019-01-15 00:35:28.096238+0000 0x49a Fault 0x0 0 0 kernel: (IOAcceleratorFamily2) bool IOAccelDisplayPipe2::init_framebuffer_resource(IOAccelResource2 *): getPixelInformation for framebuffer 2 failed
The question I am asking now is should I continue to try to get this 10.13.6 stable or should I first upgrade it to 10.14.2, and then try to get display/graphics to work...
Hope to hear from you.
PS - Sometimes the system does not detect any display (connectors tab in Hackintool has no lines in red), trying to get to new EDID tab with General breaks the App, it just closes with a dump. If I can reproduce it I will post its details.
PS2 - Injecting EDID in AAPL02,override-no-connect, sometimes plugin and unplugging the KVM switch hangs the system and have to restart it by reseting!