[solved] Sierra HD4000 5MB VRAM problem

[Dr.Aequitas]

Hmm. How can I find out what causes this problem?

 

[RehabMan]

Hmm. How can I find out what causes this problem?

What problem are you referring to?
The backlight guide is very clear on what you need to do to inject a proper display product ID.
Please read the entire backlight guide carefully.

 

[warra]

AGPM will load with GFX0->IGPU rename.
The problem of it being external (due to DP connector-type) is known.
Maybe you can patch it for LVDS.
Make sure you implement backlight control correctly before giving up on it (you didn't attach "Problem Reporting" files, so I can't tell whether you did it or not).

Hello, here are my files. I still need to generate the SSDT for the processor (I don't have internet yet to use ssdtPRGen), patch the AppleHDA and enable ethernet and wifi / bluetooth. I applied the basic patches to the DSDT and disabled the Nvidia graphics card.

 

[RehabMan]

Hello, here are my files. I still need to generate the SSDT for the processor (I don't have internet yet to use ssdtPRGen), patch the AppleHDA and enable ethernet and wifi / bluetooth. I applied the basic patches to the DSDT and disabled the Nvidia graphics card.

Your ioreg shows you're not running macOS Sierra at all.
Kernel 13.4.0 is OS X 10.9.5 (Mavericks).
Why are you posting in the Sierra forum?

According to your ioreg, the main problem you're faced with now is that your internal display is detected as external, likely due to the ig-platform-id you're using (0x0166000a is a desktop ig-platform-id).

 

[Dr.Aequitas]

Wow, now see.. 0x0166000a is for desktops and a desktop cannot have an internal display so I cannot control backlight if I put this as ig-platform-id.
I'm really sorry, because I'm aware of how I'm causing you trouble and discomfort, but I'm really a noob but I'm learning, thanks to you.
I tested this issue by putting 0x01660004 - as it should be in the first place - as ig-platform-id and checked if backlight control works. Here's the result:

But I have display issues when I assign 0x01660004. Screen becomes like the one I've posted in the opening post, like old TVs.
And I guess, the reason for this is EDID.
I readed ''Display ID dependencies'' part. I put 0x9c7c to EDID product ID part, EDID=true, ig-platform-id to 0x01660004 but still the same display problem, that old TV look.

 

[RehabMan]

Wow, now see.. 0x0166000a is for desktops and a desktop cannot have an internal display so I cannot control backlight if I put this as ig-platform-id.
I'm really sorry, because I'm aware of how I'm causing you trouble and discomfort, but I'm really a noob but I'm learning, thanks to you.
I tested this issue by putting 0x01660004 - as it should be in the first place - as ig-platform-id and checked if backlight control works. Here's the result:

But I have display issues when I assign 0x01660004. Screen becomes like the one I've posted in the opening post, like old TVs.
And I guess, the reason for this is EDID.
I readed ''Display ID dependencies'' part. I put 0x9c7c to EDID product ID part, EDID=true, ig-platform-id to 0x01660004 but still the same display problem, that old TV look.

What connector does the display attach to with 0x01660004?
What is DVMT-prealloc set to?
Did you include the patch for 0x01660004 that adjusts BIOS memory (DVMT-prealloc) to 64mb? (it is in my guide plists).

 

[Dr.Aequitas]

Well, I don't know how I can answer those questions exactly, because I lack knowledge, but I think we've changed the connector type from DP to LVDS, if that's what you mean by connector.
I don't know what DVMT-prealloc is. I searched a bit, found this post, which says it's about Broadwell/Skylake/KabyLake processors. Mine is IvyBridge as far as I know. If that's not important, then I have no idea how I can see what it is set to.
As for the latest question: I don't know what you mean. Can you give links to your comments, please? I googled ''rehabman plist guide'' but cannot find it.

 

[RehabMan]

Well, I don't know how I can answer those questions exactly, because I lack knowledge, but I think we've changed the connector type from DP to LVDS, if that's what you mean by connector.
I don't know what DVMT-prealloc is. I searched a bit, found this post, which says it's about Broadwell/Skylake/KabyLake processors. Mine is IvyBridge as far as I know. If that's not important, then I have no idea how I can see what it is set to.
As for the latest question: I don't know what you mean. Can you give links to your comments, please? I googled ''rehabman plist guide'' but cannot find it.

If you don't know what you're doing, you have to upload "Problem Reporting" files as per FAQ.

My Clover guide is linked from the FAQ.
Here is a direct link:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

 

[Dr.Aequitas]

OK, I'll upload necessary files again but as for you to know, I'm using 0x0166000A normally, because this is how I can get a clean display output. Should I provide the files with this code or should I use 0x01660004 first, then produce the files?
On the other hand, it still says ''DVMT-prealloc on Broadwell/Skylake/Kaby Lake'', so my processor is IvyBrdige. Is it OK for me to proceed nevertheless?

 

[RehabMan]

OK, I'll upload necessary files again but as for you to know, I'm using 0x0166000A normally, because this is how I can get a clean display output. Should I provide the files with this code or should I use 0x01660004 first, then produce the files?

You couldn't answer my questions regarding your configuration with 0x01660004, hence the suggestion to provide "Problem Reporting" files. Then I can tell you what you're doing.

On the other hand, it still says ''DVMT-prealloc on Broadwell/Skylake/Kaby Lake'', so my processor is IvyBrdige. Is it OK for me to proceed nevertheless?

DVMT-prealloc is a setting on all IGPU.
There are more explicit checks (that cause panic) in the kexts for Broadwell and later.