Contribute
Register

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

CaseySJ said:
Oops, my mistake. For some reason I thought you wanted to switch to headless mode. Because you have a Vega 56, I actually recommend using that exclusively for driving your monitor. The IGPU will be used to accelerate rendering tasks, but will not drive a monitor. Additionally, you’ll be able to run iMovie, Final Cut Pro, etc.

If you really need to drive a monitor with the IGPU, then you can use platform ID 0x3E9B0007 and set your connectors correctly. But in this case iMovie will immediately crash. Final Cut Pro and some other A/V apps will also crash.
Click to expand...
so sry, I did not make my intension clearly. Currently my vega 56 having some fan issues, so I would like to use IGPU to drive monitor for a while until new AMD GPU come out.
but the weird thing is,
  • Devices --> Fake ID --> IntelGFX --> Enter appropriate Device ID = 0x3E9B8086
  • Graphics --> Inject Intel --> Check this ON.
  • Graphics --> ig-platform-id --> Click pop-up menu and choose appropriate ID = 0x3E9B0007
above method make my IGPU work with black screen.
BUT patch to properties method is not working for me, not even a black screen.
Code: 
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>
                BwCbPg==
                </data>
                <key>AAPL,slot-name</key>
                <string>Internal</string>
                <key>device_type</key>
                <string>Display controller</string>
                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>hda-gfx</key>
                <string>onboard-2</string>
                <key>model</key>
                <string>UHD Graphics 630 (Desktop 9 Series)</string>
            </dict>
the code you provided is not works too
Code: 
<key>Properties</key>
<dict>
    <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
    <dict>
        <key>AAPL,ig-platform-id</key>
        <data>BwCbPg==</data>
        <key>device-id</key>
        <data>mz4AAA==</data>
        <key>framebuffer-patch-enable</key>
        <data>AQAAAA==</data>
    </dict>
</dict>
for my understanding,
the properties patch and patch through clover GUI will make no differences? I dont know whats going on,
maybe you know why ?
thank you as always:)
 
shi23ww said:
so sry, I did not make my intension clearly. Currently my vega 56 having some fan issues, so I would like to use IGPU to drive monitor for a while until new AMD GPU come out.
but the weird thing is,
  • Devices --> Fake ID --> IntelGFX --> Enter appropriate Device ID = 0x3E9B8086
  • Graphics --> Inject Intel --> Check this ON.
  • Graphics --> ig-platform-id --> Click pop-up menu and choose appropriate ID = 0x3E9B0007
above method make my IGPU work with black screen.
BUT patch to properties method is not working for me, not even a black screen.
Code: 
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>
                BwCbPg==
                </data>
                <key>AAPL,slot-name</key>
                <string>Internal</string>
                <key>device_type</key>
                <string>Display controller</string>
                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>hda-gfx</key>
                <string>onboard-2</string>
                <key>model</key>
                <string>UHD Graphics 630 (Desktop 9 Series)</string>
            </dict>
the code you provided is not works too
Code: 
<key>Properties</key>
<dict>
    <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
    <dict>
        <key>AAPL,ig-platform-id</key>
        <data>BwCbPg==</data>
        <key>device-id</key>
        <data>mz4AAA==</data>
        <key>framebuffer-patch-enable</key>
        <data>AQAAAA==</data>
    </dict>
</dict>
for my understanding,
the properties patch and patch through clover GUI will make no differences? I dont know whats going on,
maybe you know why ?
thank you as always:)
Click to expand...
You should use the settings from Option 2 in Post 652. Those are already the correct settings.
 
CaseySJ said:
You should use the settings from Option 2 in Post 652. Those are already the correct settings.
Click to expand...
I do have output but graphic glitch on all icons :( anything that I can do to get it display well? I did enable -disablegfxfirmware
Code: 
        <key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>
                BwCbPg==
                </data>
                <key>AAPL,slot-name</key>
                <string>Internal</string>
                <key>device-id</key>
                <data>
                mz4AAA==
                </data>
                <key>device_type</key>
                <string>VGA compatible controller</string>
                <key>enable-hdmi20</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con0-busid</key>
                <data>
                AgAAAA==
                </data>
                <key>framebuffer-con0-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con0-flags</key>
                <data>
                xwMAAA==
                </data>
                <key>framebuffer-con0-index</key>
                <data>
                AgAAAA==
                </data>
                <key>framebuffer-con0-pipe</key>
                <data>
                CgAAAA==
                </data>
                <key>framebuffer-con0-type</key>
                <data>
                AAgAAA==
                </data>
                <key>framebuffer-con1-busid</key>
                <data>
                BAAAAA==
                </data>
                <key>framebuffer-con1-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con1-flags</key>
                <data>
                xwMAAA==
                </data>
                <key>framebuffer-con1-index</key>
                <data>
                AwAAAA==
                </data>
                <key>framebuffer-con1-pipe</key>
                <data>
                CAAAAA==
                </data>
                <key>framebuffer-con1-type</key>
                <data>
                AAgAAA==
                </data>
                <key>framebuffer-con2-busid</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con2-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con2-flags</key>
                <data>
                xwMAAA==
                </data>
                <key>framebuffer-con2-index</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con2-pipe</key>
                <data>
                CQAAAA==
                </data>
                <key>framebuffer-con2-type</key>
                <data>
                AAQAAA==
                </data>
                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-unifiedmem</key>
                <data>
                AAAAgA==
                </data>
                <key>hda-gfx</key>
                <string>onboard-2</string>
                <key>model</key>
                <string>UHD Graphics 630 (Mobile)</string>
            </dict>
        </dict>
current setting with BIOS 19.1
 
Last edited:
CaseySJ said:
I'm sorry I don't understand the question. Can you post an image?
Click to expand...
Hello CaseySJ
use HD4600 see question post 643

408659


408663
 
Hi I had read a lot of post of this EXCELLENT THREAD! good explanation!
Can't config AOURUS RX 580 Gaming 8GB to use the HDMI output and DVI-D simultaneously.
any help?. I disable the onboard graphic. Its seems all ask to config on board graphic or the download.
This config in the hackintool its related? or I understand its only for onboard graphic?
 

Attachments

  • Screen Shot 2019-05-28 at 17.08.35.png
    Screen Shot 2019-05-28 at 17.08.35.png
    87.1 KB · Views: 65
  • Screen Shot 2019-05-28 at 17.28.32.png
    Screen Shot 2019-05-28 at 17.28.32.png
    67.4 KB · Views: 55
  • Screen Shot 2019-05-28 at 17.28.50.png
    Screen Shot 2019-05-28 at 17.28.50.png
    99.7 KB · Views: 62
Last edited:
Hackintosh for graphic design
Z390 AORUS ULTRA |  i7 9700K |  AORUS Radeon RX 580
kochfede said:
Hi I had read a lot of post of this EXCELLENT THREAD! good explanation!
Can't config AOURUS RX 580 Gaming 8GB to use the HDMI output and DVI-D simultaneously.
any help?. I disable the onboard graphic. Its seems all ask to config on board graphic or the download.
This config in the hackintool its related? or I understand its only for onboard graphic?
Click to expand...
This guide is for patching the iGPU. To patch the AMD RX 580, however, the process is a lot more complicated. Please have a look here:
www.tonymacx86.com

Guide How to Patch AMD Framebuffers for High Sierra using Clover

So if you recently installed High Sierra and have an AMD graphics card and were greeted at the end of the installation with black screens and Lilu.kext and WhateverGreen.kext wasn't able to resolve it, then try patching the framebuffer that corresponds to your graphics card to try resolving it...
www.tonymacx86.com www.tonymacx86.com

In most cases, however, you should not need to make any changes. MacOS 10.14.5 along with latest versions of Clover, Lilu, and WhateverGreen should be able to make full use of your AMD GPU.
 
fabio71 said:
Hello CaseySJ
use HD4600 see question post 643

View attachment 408659

View attachment 408663
Click to expand...
That by itself is okay. MacOS uses two different video drivers:
  • During first 2/3 of the startup process it uses a default VESA driver (non-accelerated) and default resolution.
  • During the last 1/3 of the startup process it switches to the accelerated display driver and uses the video resolution that was last used. If the last-used resolution is smaller than the default resolution, then everything in the monitor will appear bigger.
    • For example, if default resolution is 2560x1440 and the last-used resolution is 1024x768, then of course everything will look bigger at 1024x768.
The real question is whether the boot process can finish and you can log in?

If you can log in, you can go to System Preferences --> Displays and change the resolution.
 
CaseySJ said:
This guide is for patching the iGPU. To patch the AMD RX 580, however, the process is a lot more complicated. Please have a look here:
www.tonymacx86.com

Guide How to Patch AMD Framebuffers for High Sierra using Clover

So if you recently installed High Sierra and have an AMD graphics card and were greeted at the end of the installation with black screens and Lilu.kext and WhateverGreen.kext wasn't able to resolve it, then try patching the framebuffer that corresponds to your graphics card to try resolving it...
www.tonymacx86.com www.tonymacx86.com

In most cases, however, you should not need to make any changes. MacOS 10.14.5 along with latest versions of Clover, Lilu, and WhateverGreen should be able to make full use of your AMD GPU.
Click to expand...
Yes I saw that there is an option a boot argument -raddvi to solve this problem with whaevergreen, I dont know where to put it, in the clover bootloader dont work, I never put an argument to load a kext... do you know?
 
Hackintosh for graphic design
Z390 AORUS ULTRA |  i7 9700K |  AORUS Radeon RX 580
kochfede said:
Yes I saw that there is an option a boot argument -raddvi to solve this problem with whaevergreen, I dont know where to put it, in the clover bootloader dont work, I never put an argument to load a kext... do you know?
Click to expand...
Please try this:
  • Mount EFI partition of your Mojave SSD.
  • Run Clover Configurator and open your config.plist (it will be in the EFI disk and the EFI/CLOVER folder).
  • Then make the change shown and save the file.
  • Reboot.
Screen Shot 2019-05-28 at 2.46.09 PM.png
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top