HD520 Screen comes back turned off after waking from sleep.

[RehabMan]

It is the same with apple sleep, and lid close. Always get black screen on waking until I press power button again or any key on keyboard.

Might be an NVRAM problem. Clear NVRAM (nvram -c) and check that your NVRAM is working...

Cannot boot with OsxAptioFixDrv-64.efi. I get and error saying memory cannot be allocated.
This error started after I changed CsrActiveConfig from 0x67 to 0x3 as suggested by Mirone to AppleHDA Patch on 10.12.

CsrActiveConfig should be 0x67.

Tried with 191b and 191e. I get the same results. It seems that system is getting information about my Graphics Card somehow and alway is set with 1916.
Note: I changed this value on clover´s config.plist and DSDT.aml
View attachment 238976

If you inject AAPL,ig-platform-id with ACPI (via _DSM method) it always overrides config.plist/Graphics/ig-platform-id.

 

[Drfrag]

Might be an NVRAM problem. Clear NVRAM (nvram -c) and check that your NVRAM is working...

nvram cleared with -c.

CsrActiveConfig should be 0x67.

Ok. It is 0x67 now. And I am now using OsxAptioFixDrv-64.efi

If you inject AAPL,ig-platform-id with ACPI (via _DSM method) it always overrides config.plist/Graphics/ig-platform-id.

I know, but it is strange that It was injected ig-platform 0x191e0000 on config.plist and "AAPL,ig-platform-id", Buffer() { 0x00, 0x00, 0x1e, 0x19 }, on DSDT, but system keeps showing 0x1916.

And screen is still off after waking from sleep.

 

[RehabMan]

I know, but it is strange that It was injected ig-platform 0x191e0000 on config.plist and "AAPL,ig-platform-id", Buffer() { 0x00, 0x00, 0x1e, 0x19 }, on DSDT, but system keeps showing 0x1916.

What do you mean by "system keeps showing 0x1916"?

 

[Drfrag]

What do you mean by "system keeps showing 0x1916"?

 

[RehabMan]

View attachment 239013
View attachment 239013

That is the device-id. It does not change with changes to ig-platform-id.

 

[Drfrag]

That is the device-id. It does not change with changes to ig-platform-id.

I think a kext or a daemon script that simulates a key press or mouse button click after wake, 1 or 2 seconds after the wake process would be nice to turn my screen on like it should.
Do you think VoodooPs2 can do that for me?

 

[RehabMan]

I think a kext or a daemon script that simulates a key press or mouse button click after wake, 1 or 2 seconds after the wake process would be nice to turn my screen on like it should.
Do you think VoodooPs2 can do that for me?

You should probably try to get at the root of the problem instead.

 

[Drfrag]

You should probably try to get at the root of the problem instead.

I will try removing _OFF from _INI and see if disabling nvidia is causing this issue.

 

[Drfrag]

You should probably try to get at the root of the problem instead.

I will try removing _OFF from _INI and see if disabling nvidia is causing this issue.

No. Having Nvidia enabled did not make screen on after wake.
Tried sleep watcher script to wakeup screen after sleep, but it didn't´t work either.
The script was only loaded after screen was on by pressing a key on my keyboard.
It is like system is on a semi-wake state (keyboard, touchpad, hard drive are surely on) and it only completely wakes after a second keypress.

 

[RehabMan]

No. Having Nvidia enabled did not make screen on after wake.
Tried sleep watcher script to wakeup screen after sleep, but it didn't´t work either.
The script was only loaded after screen was on by pressing a key on my keyboard.
It is like system is on a semi-wake state (keyboard, touchpad, hard drive are surely on) and it only completely wakes after a second keypress.

Did you try a fresh install following all applicable guides?