Can't get hardware acceleration to work with HD 630 on i5 7600k

[EliteMacx86]

View attachment 9687

Here is exact settings as suggested above... and as I said with a screenshot above... doesnt boot with these settings. I removed -igfxvesa
But now instead of being stuck on the text it goes to black screen and monitor turns off.

You're using a CFL ig-platform-id. Ensure the following:

- DVMT set to 64MB in BIOS
- ig-platform-id to 00001259
- stolenmem shouldn't be required in your case when you set the DVMT in BIOS.
- Remove -igfxvesa boot arg.

If you get a black screen, then you need to patch connectors accordingly.

 

[EliteMacx86]

here is the behavior when changing platform ID to the recommended 00001259

https://imgur.com/WIRrQMi

Black screen means the system booted up fine but there is no display. Two things to do here:

- Patch the connectors
- Inject EDID if it doesn't work even after patching connectors

See Patching Connectors below:

GUIDE Thread 'How to Enable Intel HD and UHD Graphics on macOS - Intel Framebuffer Patching Guide'

Jun 15, 2022

How to Enable Intel HD and UHD Graphics on macOS - Intel Framebuffer Patching Guide

An EliteMacx86 Exclusive Guide - This guide covers fixing Intel HD and UHD Graphics on macOS. By following this guide, you'll be able to enable Intel Graphics with acceleration on macOS with full QE/CI on your system. This guide also covers Intel Framebuffer patching and other important Graphics and Display aspects.

I. Overview

---

macOS supports a wide range of Intel HD Graphics (also referred to as iGPU) but some of them might not work out of the box if you have not followed...

• EliteMacx86
• black screen bus id patching clover connector patching desktop dvmt edid frambuffer framebuffer patching graphics ig-platform-id igpu intel intel hd graphics intel uhd graphics laptop macos opencore qe/ci whatevergreen
• Replies: 78
• Forum: Graphics and Displays

• 

 

[Duxa]

Black screen means the system booted up fine but there is no display. Two things to do here:

- Patch the connectors
- Inject EDID if it doesn't work even after patching connectors

See Patching Connectors below:

GUIDE Thread 'How to Enable Intel HD and UHD Graphics on macOS - Intel Framebuffer Patching Guide'

Jun 15, 2022

How to Enable Intel HD and UHD Graphics on macOS - Intel Framebuffer Patching Guide

An EliteMacx86 Exclusive Guide - This guide covers fixing Intel HD and UHD Graphics on macOS. By following this guide, you'll be able to enable Intel Graphics with acceleration on macOS with full QE/CI on your system. This guide also covers Intel Framebuffer patching and other important Graphics and Display aspects.

I. Overview

---

macOS supports a wide range of Intel HD Graphics (also referred to as iGPU) but some of them might not work out of the box if you have not followed...

• EliteMacx86
• black screen bus id patching clover connector patching desktop dvmt edid frambuffer framebuffer patching graphics ig-platform-id igpu intel intel hd graphics intel uhd graphics laptop macos opencore qe/ci whatevergreen
• Replies: 78
• Forum: Graphics and Displays

• 

Yes I already have the iGPU memory allocation in BIOS set to 64Mb, it was set to 128Mb but I set it to 64Mb now.

I removed stolenmem, and -igfxvesa

I have set ig-platform-id to 00001259

My EFI with all the changes is attached.

However now the only way for me to get into it is either via SSH, or via adding -igfxvesa, because without it its a black screen.

And so when I run ioreg like the guide says, I cant follow the guide.. because my "Display0" is not under any framebuffers, its at the root by itself. I suspect this is because I have -igfxvesa set? But how do I get to GUI to even run ioreg if I get black screen without -igxvesa?

id be more than happy to run things via SSH since I have full access with black screen. But the guide doesnt have any steps for doing this via SSH.

 

[EliteMacx86]

Yes I already have the iGPU memory allocation in BIOS set to 64Mb, it was set to 128Mb but I set it to 64Mb now.

I removed stolenmem, and -igfxvesa

I have set ig-platform-id to 00001259

My EFI with all the changes is attached.

However now the only way for me to get into it is either via SSH, or via adding -igfxvesa, because without it its a black screen.

And so when I run ioreg like the guide says, I cant follow the guide.. because my "Display0" is not under any framebuffers, its at the root by itself. I suspect this is because I have -igfxvesa set? But how do I get to GUI to even run ioreg if I get black screen without -igxvesa?

id be more than happy to run things via SSH since I have full access with black screen. But the guide doesnt have any steps for doing this via SSH.

View attachment 9688

View attachment 9690

The above IOReg shows that the IGPU is disabled via the boot arg "-igfxvesa". If you're getting black screen, then you can use VNC viewer to patch the connectors. If that doesn't work for you, simply patch the connectors blindly. Define con1, con2 and set them as 00080000 and 04000000. If it still results in black screen, you must inject EDID then.

 

[Duxa]

The above IOReg shows that the IGPU is disabled via the boot arg "-igfxvesa". If you're getting black screen, then you can use VNC viewer to patch the connectors. If that doesn't work for you, simply patch the connectors blindly. Define con1, con2 and set them as 00080000 and 04000000. If it still results in black screen, you must inject EDID then.

When I connect via VNC there is no Display section under iGPU at all.
My boot args do not have "-igfxvesa".

How do I inject EDID?

 

[EliteMacx86]

When I connect via VNC there is no Display section under iGPU at all.
My boot args do not have "-igfxvesa".

How do I inject EDID?

View attachment 9692


View attachment 9693
View attachment 9694

As expected, macOS fails to find the monitor which results in black screen. There's a guide on Injecting EDID. Check that out.

Also, just enabling the connectors will not help. You must define the connectors as well.

 

[Duxa]

As expected, macOS fails to find the monitor which results in black screen. There's a guide on Injecting EDID. Check that out.

Also, just enabling the connectors will not help. You must define the connectors as well.

Following the guide, first option via IOreg I cant do because there is no Display section.

Doing DarwinDumper... the dump ended up with an empty folder. Here it is attached.

Going to try Ubuntu next...

Why am I having so much trouble with this? its the most run of the mill processor, most run of the mill config... standard desktop motherboard and standard i5 7600k.... with standard iGPU HD 630...

EDIT: Ubuntu dumped it... now to inject it...

edid-decode (hex):

00 ff ff ff ff ff ff 00 10 ac d0 a0 51 44 33 31
27 19 01 03 80 3c 22 78 0e ee 91 a3 54 4c 99 26
0f 50 54 21 08 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 56 5e 00 a0 a0 a0 29 50 30 20
35 00 56 50 21 00 00 1a 00 00 00 ff 00 4e 4e 56
35 34 35 39 4e 31 33 44 51 20 00 00 00 fd 00 18
3c 1e 8c 1e 01 0a 20 20 20 20 20 20 00 00 00 fc
00 44 65 6c 6c 20 53 32 37 31 36 44 47 0a 01 f0

02 03 1a c1 47 90 1f 04 13 03 12 01 23 09 07 01
83 01 00 00 65 03 0c 00 10 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c1

 

[Duxa]

Follow up from previous post... guide has only one HEX block, my dump (via Ubuntu) has two... do I use both? Do I use one? How to know which to use?

Also guide tells me to open FixEDID App.... where do I get that, with such a generic name its impossible to google for it.

Found something on github, but it cant be opened:


Is this step only for retrieving via Windows? Because its not clear if thats only for that or if it should be followed after every way.

Also not clear for pasting the EDID... we are adding overide-no-connect.... but are we keeping APPL,ig-platform-id? or are we deleting that?

Also when it says paste... do we need to delete spaces/whitespace/new lines etc? or paste as is (as a block with all the whitespace and new lines?)


(click on it so it zooms so you can see the text).

Ive tried both top and bottom hex, just top, just bottom, with and without the APPL,ig-platform-id....

All combinations lead to black screen still.

 

[Duxa]

Ok, I started reading what EDID was... since none of the guides actually tell you what it is. And if I understand correctly doing EDID patch basically marries you to a specific monitor? Which would not work in my case since I am just setting up this Hackintosh on my main monitors but the plan is to run it through an HDMI switcher, which would not register as the same monitor...

I was initially using a 1440p monitor (but all I need is 1080p), so I pulled out another monitor (1080p one) and hooked up to it. Starting the process over, going through all of the different AAPL,ig-platform-id on the new monitor....

I got to this one:


And instead of the usual, boot text, then black screen, it actually got to login screen. But then after about 30 seconds the monitor turns off again, just like before... BUT, through VNC I can see that it got full HW acceleration...



So.. its close... it can clearly drive the monitor, since it sits on logon screen for like 30 seconds before going dark... how do I fix that?

EDIT: Went through the rest of them, this is the only one that detects HW acceleration. Its so weird. If I type in password fast, I can get to Desktop, even do some stuff, like open things, or check About This Mac... but like before about 30 seconds later... screen goes black.

 

[macpro]

Starting the process over, going through all of the different AAPL,ig-platform-id on the new monitor....

there is no list, there is only the one id for your kabylake desktop cpu