[Solved] Sleep/wake/lid not working after upgrade os to High Sierra

[lemnitz3]

Ok?
Cheers.

 

[RehabMan]

Ok?
Cheers.

Not possible to verify ACPI/origin against ACPI/patched.
The files in ACPI/patched are newer than ACPI/origin. If "Problem Reporting" is followed as written, files in ACPI/origin should be newer than ACPI/patched.

And even if I do compare them, I find SystemMemory addresses are different.
Next time, you compare them yourself before asking...
It is not that hard.
First, after extracting new ACPI/origin, copy CLOVER/ACPI to the Desktop.
Then,

cd ~/Desktop/ACPI/origin
iasl -da -dl DSDT.aml SSDT*.aml
cd ../patched
iasl -da -dl *.aml
diff ../origin ../patched |grep SystemMemory

Differences such as this show the addresses are different, which is a problem:

<         OperationRegion (COMP, SystemMemory, 0x8AF56018, 0x0200)
>         OperationRegion (COMP, SystemMemory, 0x8B257C98, 0x0200)

 

[lemnitz3]

Thanks for clearing, useful information as always!
Yeah,I upgraded to a larger memories from 8gb, to 16gb.and forgotten to make a fresh Acpi patch after that!
Thanks RehabMan,I followed your suggestions. So here comes files....

 

[RehabMan]

Thanks for clearing, useful information as always!
Yeah,I upgraded to a larger memories from 8gb, to 16gb.and forgotten to make a fresh Acpi patch after that!
Thanks RehabMan,I followed your suggestions. So here comes files....

Your ioreg shows CPU PM not implemented.
Guide is linked from the FAQ.
http://www.tonymacx86.com/el-capita...faq-read-first-laptop-frequent-questions.html

 

[LordHung]

Yes (specifically, all valid ig-platform-id).
How did you verify DVMT-prealloc is 128mb?

Sorry for late reply.
I tried all ig-platform-ids: 191e0000, 19160000, 19160002, 19260000, 19260002, 191b0000, 191e0003(stuck at boot)
All of them gives me 1536mb vram but the problem is still there.
"How did you verify DVMT-prealloc is 128mb?": I checked via efishell: setup_var 0x180(my dvmt variable) return 0x02; setup_var2 0x180 return 0x04. I don't know which one is exactly but I can only set dvmt via setup_var2. I have re-set dvmt (just for sure): setup_var2 0x180 0x04 and its successful.

But no luck, the problem still there: I put laptop to sleep, wake it up and the built-in screen turns gray. But it visible on another display. I'm so confused.
Here is my recent problem reporting info. Please help me

p/s: I have re-installed high Sierra but still the same.

 

[RehabMan]

Sorry for late reply.
I tried all ig-platform-ids: 191e0000, 19160000, 19160002, 19260000, 19260002, 191b0000, 191e0003(stuck at boot)
All of them gives me 1536mb vram but the problem is still there.
"How did you verify DVMT-prealloc is 128mb?": I checked via efishell: setup_var gives me 0x02( 64mb); setup_var2 gives 0x04(128mb). I don't know which one is exactly but I can only set dvmt via setup_var2. I have re-set dvmt (just for sure): setup_var2 0x180 0x04 and its successful.

But no luck, the problem still there: I put laptop to sleep, wake it up and the built-in screen turns gray. But it visible on another display. I'm so confused.
Here is my recent problem reporting info. Please help me

Comments:
- Why are you using MacBookPro13,2? Use MacBookPro13,1 or MacBookPro11,1.
- CPU PM not implemented
- AddHDMI_8000000 is a bad idea. Remove.
- with a larger DVMT, you can patch the framebuffer to take advantage of it (look here for clues: https://www.tonymacx86.com/threads/...lensize-patch-with-32mb-dvmt-prealloc.221506/)

 

[LordHung]

Comments:
- Why are you using MacBookPro13,2? Use MacBookPro13,1 or MacBookPro11,1.
- CPU PM not implemented
- AddHDMI_8000000 is a bad idea. Remove.
- with a larger DVMT, you can patch the framebuffer to take advantage of it (look here for clues: https://www.tonymacx86.com/threads/...lensize-patch-with-32mb-dvmt-prealloc.221506/)

Thank for your help. Updated clover.
I think my dvmt is just 64mb(setup_var return 0x02) because I can't set framebuffer, cursor bytes fit 128mb(it's cause a restart). So setup_var2 return 0x04 is something different
I also tried Lilu.kext and Intelgraphicfix.kext and EnableLidWake.kext(http://www.insanelymac.com/forum/to...ake-—-fix-lid-wake-issues-for-intel-graphics/) but still the same.
I'm researching about this thread: http://www.insanelymac.com/forum/to...id-wake-from-sleep-for-skylake-iris-graphics/ but no info for HD 520

I have attached my recent problem reporting info.

p/s: Lid also makes my built-in screen can't wake not only sleep mode.

 

[xShift]

same problem with HD520.

 

[RehabMan]

Thank for your help. Updated clover.
I think my dvmt is just 64mb(setup_var return 0x02) because I can't set framebuffer, cursor bytes fit 128mb(it's cause a restart). So setup_var2 return 0x04 is something different
I also tried Lilu.kext and Intelgraphicfix.kext and EnableLidWake.kext(http://www.insanelymac.com/forum/to...ake-—-fix-lid-wake-issues-for-intel-graphics/) but still the same.
I'm researching about this thread: http://www.insanelymac.com/forum/to...id-wake-from-sleep-for-skylake-iris-graphics/ but no info for HD 520

I have attached my recent problem reporting info.

p/s: Lid also makes my built-in screen can't wake not only sleep mode.

It seems to me you're not manipulating the correct variables with setup_var/setup_var2.
Do an IFR extract so you're certain which variable corresponds to DVMT-prealloc.

 

[RehabMan]

same problem with HD520.

Did you set DVMT-prealloc as required or are you using a patch?

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/