Kaby Lake HD620 working...

[iWanderer]

I will try that I have found my R9 280X as well.

Researching how I can leave both cards in the system and use Radeon for OS X and GTX 1070 for windows/Gaming?

Update:- I have tried DVI port but it is still the same.

Put Radeon 280X in PEG0 and GTX 1070 in PEG1, hook 1 monitor to Radeon 280X for macOS and hook 1 monitor for GTX 1070 for Windows/Gaming. Set the bios to initiate PEG0 first.

 

[gustebeast]

If you're using an old Clover, make sure config.plist/Graphics/InjectEDID=false.
Attach EFI/Clover folder as ZIP (omit 'themes' folder).



To start, use a non-4k display.

I have the latest clover, and non-4k displays work fine. Just trying to get the 4k monitor to get past boot without going black. It sounds like @muhammadqaiser5 may have done just this. I've attached my Clover directory along with my /Library/Extensions folder.

 

[muhammadqaiser5]

I have the latest clover, and non-4k displays work fine. Just trying to get the 4k monitor to get past boot without going black. It sounds like @muhammadqaiser5 may have done just this. I've attached my Clover directory along with my /Library/Extensions folder.

I couldn't sorry that is not the answer you were looking for fighting with XFX R9 280X to get it working but no luck on that even.

 

[gustebeast]

Here's what it looks like on a 1080p monitor with intel injection. Some tearing, but much better than with no injection on the 4k monitor.

 

[RehabMan]

I have the latest clover, and non-4k displays work fine. Just trying to get the 4k monitor to get past boot without going black. It sounds like @muhammadqaiser5 may have done just this. I've attached my Clover directory along with my /Library/Extensions folder.

Devices/FakeID/IntelGFX has no effect without Graphics/Inject/Intel=true.
4k display probably needs the pixel clock patch.

 

[gustebeast]

Devices/FakeID/IntelGFX has no effect without Graphics/Inject/Intel=true.
4k display probably needs the pixel clock patch.

Sorry, I had it disabled so I could boot, but when I enable it it just gives a black screen. Currently I have it disabled by default, when I need to test it I just enable it manually in the clover boot screen settings.

As for the pixel clock patch, I found some tutorials but they seemed to be specific to certain kinds of laptops, do you have a recommended tutorial to follow?

 

[RehabMan]

Sorry, I had it disabled so I could boot, but when I enable it it just gives a black screen. Currently I have it disabled by default, when I need to test it I just enable it manually in the clover boot screen settings.

As for the pixel clock patch, I found some tutorials but they seemed to be specific to certain kinds of laptops, do you have a recommended tutorial to follow?

The pixel clock patch is not specific to laptops. And definitely not specific to "certain kinds of laptops".

But you should also make sure the connector-type matches the physical connector you're trying to use. Usually that means if you're using HDMI, because most existing connector-types are DP by default, you will need a patch for the framebuffer connector...

 

[gustebeast]

The pixel clock patch is not specific to laptops. And definitely not specific to "certain kinds of laptops".

But you should also make sure the connector-type matches the physical connector you're trying to use. Usually that means if you're using HDMI, because most existing connector-types are DP by default, you will need a patch for the framebuffer connector...

Okay so I applied the CoreDisplay patch here: https://github.com/Floris497/mac-pixel-clock-patch-V2 and I am still getting the black screen with the 4k display, and everything working fine on the 1080p display. I am using a DP cable, is this the frame buffer connector patch you're referring to? https://github.com/toleda/graphics_Intel_framebuffers

 

[RehabMan]

Okay so I applied the CoreDisplay patch here: https://github.com/Floris497/mac-pixel-clock-patch-V2 and I am still getting the black screen with the 4k display, and everything working fine on the 1080p display. I am using a DP cable, is this the frame buffer connector patch you're referring to? https://github.com/toleda/graphics_Intel_framebuffers

If you are using a DP port on the computer, then likely no need to patch the framebuffer.
You should check in ioreg to see which framebuffer node the port is connected to and what connector-type it is...

 

[gustebeast]

If you are using a DP port on the computer, then likely no need to patch the framebuffer.
You should check in ioreg to see which framebuffer node the port is connected to and what connector-type it is...

Wait, now it's working. Maybe I just didn't try booting enough times. I think the CoreDisplay patch did it. Thanks for the help! Now off to fix the menu bar glitch.