Acer E5-575 black screen after wake

[disrupt]

Hi everyone,

I'm running 10.12.3 on a Acer E5-575-51GG laptop (i5-6200U, 8Gx2 DDR4, BCM94352Z, Elan Trackpad, ALC255) and so far everything works, except that I get a black screen on wake.

The laptop can sleep/wake when I close/open the lid, but the screen stays blank. Backlight does seem to turn on, as some backlight bleeding is visible if in a dark room. Pressing the brightness up key didn't help. And the system is running as there are sounds when the volume keys are pressed, and I can shutdown/restart by blindly operating the top-left menu.

Please see the following kextstat and kextcache output, and patchmatic, ioreg, and clover files attached:

kk@E5-575:~$ kextstat|grep -y acpiplat
   13    2 0xffffff7f82fde000 0x66000    0x66000    com.apple.driver.AppleACPIPlatform (5.0) 867C81BE-EA01-3A65-89F4-06D78E6514CA <12 11 7 6 5 4 3 1>
kk@E5-575:~$ kextstat|grep -y appleintelcpu
kk@E5-575:~$ kextstat|grep -y applelpc
   86    0 0xffffff7f829e9000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) F51595F0-F9B1-3B85-A1C3-F984DAD4107E <80 12 5 4 3>
kk@E5-575:~$ kextstat|grep -y applehda
   91    1 0xffffff7f82f0b000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (278.56) CFB0D0AE-F09A-3660-8F95-7A02FD5FBF07 <90 89 88 12 7 6 5 4 3 1>
  119    0 0xffffff7f83246000 0xb4000    0xb4000    com.apple.driver.AppleHDA (999.1.1fc1) A4EB06C9-A40A-39EF-9C4A-D7F23DB9A2F9 <118 95 91 90 89 88 6 5 4 3 1>
kk@E5-575:~$
kk@E5-575:~$
kk@E5-575:~$ sudo touch /System/Library/Extensions && sudo kextcache -u /
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext SATA-100-series-unsupported.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IntelBacklight.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CodecCommander.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext aDummyHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
KernelCache ID: DF11E2152C571CF519619ADE904C6346
symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>

Thank you!

 

[RehabMan]

Hi everyone,

I'm running 10.12.3 on a Acer E5-575-51GG laptop (i5-6200U, 8Gx2 DDR4, BCM94352Z, Elan Trackpad, ALC255) and so far everything works, except that I get a black screen on wake.

The laptop can sleep/wake when I close/open the lid, but the screen stays blank. Backlight does seem to turn on, as some backlight bleeding is visible if in a dark room. Pressing the brightness up key didn't help. And the system is running as there are sounds when the volume keys are pressed, and I can shutdown/restart by blindly operating the top-left menu.

Please see the following kextstat and kextcache output, and patchmatic, ioreg, and clover files attached:

kk@E5-575:~$ kextstat|grep -y acpiplat
   13    2 0xffffff7f82fde000 0x66000    0x66000    com.apple.driver.AppleACPIPlatform (5.0) 867C81BE-EA01-3A65-89F4-06D78E6514CA <12 11 7 6 5 4 3 1>
kk@E5-575:~$ kextstat|grep -y appleintelcpu
kk@E5-575:~$ kextstat|grep -y applelpc
   86    0 0xffffff7f829e9000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) F51595F0-F9B1-3B85-A1C3-F984DAD4107E <80 12 5 4 3>
kk@E5-575:~$ kextstat|grep -y applehda
   91    1 0xffffff7f82f0b000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (278.56) CFB0D0AE-F09A-3660-8F95-7A02FD5FBF07 <90 89 88 12 7 6 5 4 3 1>
  119    0 0xffffff7f83246000 0xb4000    0xb4000    com.apple.driver.AppleHDA (999.1.1fc1) A4EB06C9-A40A-39EF-9C4A-D7F23DB9A2F9 <118 95 91 90 89 88 6 5 4 3 1>
kk@E5-575:~$
kk@E5-575:~$
kk@E5-575:~$ sudo touch /System/Library/Extensions && sudo kextcache -u /
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext SATA-100-series-unsupported.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IntelBacklight.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CodecCommander.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext aDummyHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
KernelCache ID: DF11E2152C571CF519619ADE904C6346
symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>

Thank you!

What happens if you remove the unneeded injections from config.plist/Devices/AddProperties?

 

[disrupt]

What happens if you remove the unneeded injections from config.plist/Devices/AddProperties?

Thanks for the reply RehabMan!

I tried removing them all, but the issue persists

By the way, could you shed some light on determining which Devices/AddProperties injections are necessary? I added them following https://www.tonymacx86.com/threads/fix-skylake-menu-bar-glitch-fix.206400/. I don't really know what does each of the injections mean, other than that "AAPL,GfxYTile" fixes the menu bar glitch (which I did get without the patch.) Should I assume all the others are unnecessary?

 

[RehabMan]

Thanks for the reply RehabMan!

I tried removing them all, but the issue persists

By the way, could you shed some light on determining which Devices/AddProperties injections are necessary? I added them following https://www.tonymacx86.com/threads/fix-skylake-menu-bar-glitch-fix.206400/. I don't really know what does each of the injections mean, other than that "AAPL,GfxYTile" fixes the menu bar glitch (which I did get without the patch.) Should I assume all the others are unnecessary?

The AAPL,GfxYTile is the only injection required to fix the menu bar glitch.

 

[disrupt]

The AAPL,GfxYTile is the only injection required to fix the menu bar glitch.

Ok, thanks!

I have some more findings about the issue:

It has to do with the specific eDP panel (I've replaced the original screen with an IPS panel.)
- with original TN panel N156HGE-EAB: screen wakes normally
- with AUO IPS panel B156HAN01.2: screen wakes normally
- with Samsung IPS panel LTN156HL01: blank screen after wake

It's such a pity... the LTN156HL01 is the most gorgeous 1920x1080 LCD I've ever seen. Guess I'll have to live with no sleep/wake functionality for now...

 

[RehabMan]

Ok, thanks!

I have some more findings about the issue:

It has to do with the specific eDP panel (I've replaced the original screen with an IPS panel.)
- with original TN panel N156HGE-EAB: screen wakes normally
- with AUO IPS panel B156HAN01.2: screen wakes normally
- with Samsung IPS panel LTN156HL01: blank screen after wake

It's such a pity... the LTN156HL01 is the most gorgeous 1920x1080 LCD I've ever seen. Guess I'll have to live with no sleep/wake functionality for now...

It could be that your ACPI implementation has some dependencies on particular internal screens (based on EDID info).
A bit like finding a needle in a haystack though...
You might consider using ACPIDebug to trace the code path on _WAK both with working screens and with non-working screen. Maybe you can see how the code path differs.

 

[disrupt]

It could be that your ACPI implementation has some dependencies on particular internal screens (based on EDID info).
A bit like finding a needle in a haystack though...
You might consider using ACPIDebug to trace the code path on _WAK both with working screens and with non-working screen. Maybe you can see how the code path differs.

Thanks for the suggestion RehabMan. I did the tracing, but didn't find a difference in the code path. Also tried a few other DSDT tweaks to no avail.

I came to the conclusion that the issue is mainly specific to the LCD hardware. Because, previously I used it on another Acer E5-575G-53VG laptop (same CPU, MB, and BIOS version as this one, only difference is 940MX dGPU), it had a different kind of issue on wake - screen turns on but flickers badly. I also googled a bit and found out flickering seems to be a commonly reported issue (even on Windows) on this LCD.

I'm applying the arguably easiest fix for this now - ordered a different LCD panel
This time LG LP156WF6-SP-A1

 

[disrupt]

I have black screen after wake with this This time LG LP156WF6-SP-A1 on my Yoga.

Well... fingers crossed as I wait for my LP156WF6-SP-A1 to arrive...

I also tried a LP156WF4-SP-L1 taken from a Chromebook (it's got terribly pale colors BTW), and it wakes normally too, so hopefully my issue is specific to the Samsung panel...

 

[disrupt]

So the LP156WF6-SP-A1 panel arrived and it had no issue with sleep/wake. Confirming the issue is specific to this Samsung panel + Acer motherboard combination. Thanks everyone for the help!