[Guide] Intel Framebuffer patching using WhateverGreen

[gulios]

@gulios,

config.plist looks ok ... however as i said Azul framebuffer is know to be problematic.




DCPI Manager has not been updated in a very long time, I tend to use the PCI list in Hacking tool these days which is far superior and allows you to export the data if you want to spoof the devices so that they show up in Sys Info -> PCI

The Description of the IGPU is coming from the PCI spoofing generated by Hackintool's patch generator, it uses a on-line database to get the descriptions (its the same database that DCPIManager uses) and for IGPU's it always tends to be the CPU Generation rather than an exact IGPU model type. (in your case "4th Gen Core Processor")

You can change the string value of "model" in the IGPU device properties to something like "HD 4600 IGPU" if want.

Depending on the system, WhatEverGreen can sometimes not fully patch the AZUL frame buffer correctly, I had this issue on one of my HD 4600 systems, I got around it by using a SSDT Hot Patch to inject the device properties rather than defining them as Device Properties in the config.plist.

You could try the following :-

1. Download the attached zip file (SSDT-IGPU.aml.zip)
2. Unzip the file and copy SSDT-IGPU.aml to /EFI/Clover/ACPI/Patched
3. Remove all the Device Properties for the IGPU from your config.plist
4. Reboot

Clover should use now use SSDT-IGPU.aml to inject the Device Properties along with a suitable _DSM method. I wrote this SSDT to get HD 4600 working on one of my Hacks when all other methods failed to work. It will configure the IGPU with the 0x0D220003 PlatformID and also set the model description to HD 4600.

Give it a go and see if it helps, other than that i'm out of ideas ... i've never seen an IGPU issue quite like the one in your screen shot in post #910.

Cheers
Jay

with that ssdt-igpu still problems.

ok, i've got a list of platforms and started to check one by one.

0x0C060000 (desktop, 3 connectors) ->
0x0C160000 (desktop, 3 connectors) ->
0x0C260000 (desktop, 3 connectors) ->
0x04060000 (desktop, 3 connectors) ->
0x04160000 (desktop, 3 connectors) ->
0x04260000 (desktop, 3 connectors) ->
0x0D260000 (desktop, 3 connectors) ->
0x0A160000 (desktop, 3 connectors) ->
0x0A260000 (desktop, 3 connectors) ->
0x0A260005 (mobile, 3 connectors) ->
0x0A260006 (mobile, 3 connectors) ->
0x0A2E0008 (mobile, 3 connectors) ->
0x0A16000C (mobile, 3 connectors) ->
0x0D260007 (mobile, 4 connectors) ->
0x0D220003 (desktop, 3 connectors) -> 1536 MB glitches
0x0A2E000A (desktop, 3 connectors) -> 1536 MB ok but reboots
0x0A26000A (desktop, 3 connectors) -> 1536 MB glitches

now i use 0x0A2E000A graphics glitches disappeared )) so it's progress but i have some random reboots. ufff

Thank you for your time, i'll try to debug next IDs and try find where are reboots come from.

 

[jaymonkey]

now i use 0x0A2E000A graphics glitches disappeared )) so it's progress but i have some random reboots.

@gulios,

Check to see which is the active connector using Hackintool -> Patch -> Connectors - the active connector will be green :-

Check that the port Type matches the physical port type your using, if it doe snot match that can be the source of reboots.
If it's incorrect then use hackintool to patch the framebuffer for the correct port type, you may have to also change the ports flags as well which you can do by manually adding <key>framebuffer-conX-flags</key> and a data value.

Cheers
Jay

 

[gulios]

@gulios,

Check to see which is the active connector using Hackintool -> Patch -> Connectors - the active connector will be green :-
View attachment 409332
Check that the port Type matches the physical port type your using, if it doe snot match that can be the source of reboots.
If it's incorrect then use hackintool to patch the framebuffer for the correct port type, you may have to also change the ports flags as well which you can do by manually adding <key>framebuffer-conX-flags</key> and a data value.

Cheers
Jay

in my case connector on DP is red.
We'll try with another platform IDs and smbioses because i see that every other reboots there are some graphisc glitches and sometimes it works perfect...

Thank you.

 

[jaymonkey]

in my case connector on DP is red. We'll try with another platform IDs and smbioses because i see that every other reboots there are some graphisc glitches and sometimes it works perfect...

@gulios,

Sorry I should have explained that if the display is external then Hackintool will highlight the port red, if it's internal then it will be green, so red is correct for in your case.

You could try using iMac 15,1 which is what i use on my i7 4790K White Knight system (see sig for specs) however I'm running a Vega 64 so have the IGPU configured as headless.

Cheers
Jay

 

[gulios]

@gulios,

Sorry I should have explained that if the display is external then Hackintool will highlight the port red, if it's internal then it will be green, so red is correct for in your case.

You could try using iMac 15,1 which is what i use on my i7 4790K White Knight system (see sig for specs) however I'm running a Vega 64 so have the IGPU configured as headless.

Cheers
Jay

ok, i've decided to disassemble case and remove GTX and that was it. Now IGPU HD 4600 works fine with HackinTool patch for 0x0DD20003.

Thank you @jaymonkey for your time !!
Now i have to decide what to to with that GTX...

 

[jaymonkey]

ok, i've decided to disassemble case and remove GTX and that was it. Now IGPU HD 4600 works fine with HackinTool patch for 0x0DD20003.

@gulios,

It does not look like Nvidia are going to release updated WebDrivers for Mojave anytime soon, best thing you can do is sell it and buy a second hand Vega 64 ... which is which is what i did ... managed to pick up a Sapphire Vega 64 Liquid Cooled (AIO) on ebay for a very good price ... one of the best moves i ever made on my main hackingtosh system.

Works flawlessly, MacOS UI is much smoother (no stutters when scrolling .. etc) and super fast renders in FCPX.

Cheers
Jay

 

[gulios]

@gulios,

It does not look like Nvidia are going to release updated WebDrivers for Mojave anytime soon, best thing you can do is sell it and buy a second hand Vega 64 ... which is which is what i did ... managed to pick up a Sapphire Vega 64 Liquid Cooled (AIO) on ebay for a very good price ... one of the best moves i ever made on my main hackingtosh system.

Works flawlessly, MacOS UI is much smoother (no stutters when scrolling .. etc) and super fast renders in FCPX.

Cheers
Jay

yeah i know but... it's 1080TI ;( killer in games. For now i think i'll work on IGPU only (I've changed fans position so no GTX is disconnected) or i sell GTX and case and put all into smaller case without GPU...

or... maybe it's time to change Nvidia to AMD.

Does Sapphire Vega 64 works OOB?
Does "Asus Radeon RX Vega 64 ROG STRIX O8G Gaming, 8192 MB HBM2" will work OOB ?

 

[nicksoph]

Im following trs96's guide for a Dell 7020 and troubleshooting one of the issues - the on board Intel 4600 graphics. The image is fine when it works but in my dual monitor setup one of the monitors has to be turned off before starting the machine or neither monitor will display anything. I have looked at the Hackintool but dont really understand how to convert the info it shows into actions that I should do and wonder if someone can point me to an overview for noobs. 7020 Guide here.
Edit: seems this a known issue with iMac sys Def's which use a variation of the dispalyport standard for in built screens. Any ideas about how or if this is worth pursuing appreciated. There is a simplerfix to use an dedicated graphics card.
Edit 2: Used 14,3 sys defs and it worked.

 

[jaymonkey]

Does Sapphire Vega 64 works OOB?
Does "Asus Radeon RX Vega 64 ROG STRIX O8G Gaming, 8192 MB HBM2" will work OOB ?

@gulios,

When using a Vega GPU it's advisable to install Lilu + WhatEverGreen which applies a few patches and ensures that the correct frame buffer is configured (usually "Kamarang")

Most Sapphire cards are based on the AMD reference designs as such they tend to be more compatible with MacOS which is why i favour them .... I have no experience of the Asus so cant really comment, however the 10.14.5 update resolved a lot of thermal issues (mainly fan control) with OEM Vega cards so it will most likely be ok but i would recommend you search the forums and find someone with a success story of using the "Asus Radeon RX Vega 64 ROG STRIX O8G Gaming" card before committing to one.

For more info on AMD GPU's on MacOS see the Compatibility Guide :-

Radeon Compatibility Guide - ATI/AMD Graphics Cards

Radeon Compatibility Guide ATI/AMD Graphics Cards Last Change: December 2nd, 2017 The "boot to black screen" issue as well as the broken sleep/wake have been fixed! Read below for details. 0. Introduction Most of you might have noticed that the Buyer's Guide doesn't list a single...

www.tonymacx86.com

However it might be worth holding fire for a month or so, AMD have recently released details of the new Navi cards (Radeon RX 5700 series) which go on sale July 7th ... and early support for them has already been seen in Apples AMD drivers for MacOS.

I don't think they are going to be as powerful as Radeon VII but they use a new architecture (RDNA) that may be better optimised on MacOS.

I would wait and see how they benchmark against Vega 64 before making a decision, also when they hit the market its likely that Vega Gen 1 cards will probably get cheeper.

Cheers
Jay

 

[gulios]

@gulios,

When using a Vega GPU it's advisable to install Lilu + WhatEverGreen which applies a few patches and ensures that the correct frame buffer is configured (usually "Kamarang")

Most Sapphire cards are based on the AMD reference designs as such they tend to be more compatible with MacOS which is why i favour them .... I have no experience of the Asus so cant really comment, however the 10.14.5 update resolved a lot of thermal issues (mainly fan control) with OEM Vega cards so it will most likely be ok but i would recommend you search the forums and find someone with a success story of using the "Asus Radeon RX Vega 64 ROG STRIX O8G Gaming" card before committing to one.

For more info on AMD GPU's on MacOS see the Compatibility Guide :-

Radeon Compatibility Guide - ATI/AMD Graphics Cards

Radeon Compatibility Guide ATI/AMD Graphics Cards Last Change: December 2nd, 2017 The "boot to black screen" issue as well as the broken sleep/wake have been fixed! Read below for details. 0. Introduction Most of you might have noticed that the Buyer's Guide doesn't list a single...

www.tonymacx86.com

However it might be worth holding fire for a month or so, AMD have recently released details of the new Navi cards (Radeon RX 5700 series) which go on sale July 7th ... and early support for them has already been seen in Apples AMD drivers for MacOS.

I don't think they are going to be as powerful as Radeon VII but they use a new architecture (RDNA) that may be better optimised on MacOS.

I would wait and see how they benchmark against Vega 64 before making a decision, also when they hit the market its likely that Vega Gen 1 cards will probably get cheeper.

Cheers
Jay

Thank you @jaymonkey

I've decided to finish that battle with GPUs and back to "games only on console" work on PC so i'm trying to sell all parts i needed before because of WIN and stick just to motherboard+CPU and now i'm on Streacom ST-FC8B Alpha case + motherboard + cpu and problem disappeared. HD 4600 on i7 4790K works great and stable on latest macOs.

Thank you!