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

[LordHung]

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.

I have attached my extracted rom in my bios file which contain the dvmt preallocated variable is 0x180. Can you explain the diff between setup_var and setup_var2 please? Because I can only set that variable via setup_var2; setup_var return error.

 

[RehabMan]

I have attached my extracted rom in my bios file which contain the dvmt preallocated variable is 0x180. Can you explain the diff between setup_var and setup_var2 please? Because I can only set that variable via setup_var2; setup_var return error.

My understanding of setup_var2 is you use it when setup_var fails.
I have not looked at the code for either, so can't tell you what the true difference is.
Maybe you can find the source and look at it yourself.

 

[LordHung]

My understanding of setup_var2 is you use it when setup_var fails.
I have not looked at the code for either, so can't tell you what the true difference is.
Maybe you can find the source and look at it yourself.

setup_var never works for me. setup_var2 sometime works, sometime it doesn't. But I don't know why dvmt affect lid/wake problem? Because my previous sierra 10.12.6 doesn't has that problem.

 

[RehabMan]

setup_var never works for me. setup_var2 sometime works, sometime it doesn't. But I don't know why dvmt affect lid/wake problem? Because my previous sierra 10.12.6 doesn't has that problem.

With DVMT-prealloc set incorrectly, you must patch the framebuffer.
And the patches to the framebuffer may break assumptions made by Apple's code.
The effects could vary and may be only present in sleep/wake scenarios.
Each version is likely to change behavior as Apple changes the code.

 

[LordHung]

With DVMT-prealloc set incorrectly, you must patch the framebuffer.
And the patches to the framebuffer may break assumptions made by Apple's code.
The effects could vary and may be only present in sleep/wake scenarios.
Each version is likely to change behavior as Apple changes the code.

I have tried your framebuffer patch (0x19160000/etc, 19MB framebuffer 9MB cursor bytes (credit RehabMan)), it works but the sleep/wake issue is still there. And when I custom the patch to 48mb framebuffer, 48mb cursorbytes it causes restart.

 

[RehabMan]

I have tried your framebuffer patch (0x16260006/etc, 32MB BIOS, 19MB framebuffer, 9MB cursor bytes), it works but the sleep/wake issue is still there. And when I custom the patch to 48mb framebuffer, 48mb cursorbytes it causes restart.

To use 48/48, you would need to change your DVMT-prealloc to 128mb.

 

[LordHung]

To use 48/48, you would need to change your DVMT-prealloc to 128mb.

After research about setup_var, I found the original post: http://geektimes.ru/post/258090/, translated: http://geek-mag.com/posts/258090/. setup_var2 command changes value not only in the "Setup variable", but also in the "Custom variable". I think "Setup variable" is the one that affect to DVMT prealloc value in the bios. But when I run setup_var2 it only changes the Custom variable, doesn't changes the Setup variable one. I think this tool is outdated, because its release in 2013.

 

[ben9923]

- 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/)

How increasing the 64MB specified by the system could benefit me? (Not the one who opened the thread, but interested in the subject). It seems the OS is fine with 64MB (55 actually...)
I have 512MB set in BIOS, how should I split them between the frame buffer and cursor bytes? Or maybe I should use a lower amount in my patch?

Talking about my Skylake machine in my profile - Intel HD 520.

 

[RehabMan]

How increasing the 64MB specified by the system could benefit me? (Not the one who opened the thread, but interested in the subject). It seems the OS is fine with 64MB (55 actually...)
I have 512MB set in BIOS, how should I split them between the frame buffer and cursor bytes? Or maybe I should use a lower amount in my patch?

Talking about my Skylake machine in my profile - Intel HD 520.

For the hardware in your profile, there is probably no reason to increase DVMT-prealloc beyond 64mb.
Usually larger values are used with higher resolution screens.

 

[xShift]

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/

I was remove plain patch and use only IntelGraphicsFixup.kext and IntelGraphicsDVMTFixup.kext.

There are files. Patched was writen by you and TheBraveKnight.

Dmitrys-MacBook-Pro:~ xshift$ kextstat|grep -y acpiplat
   15    2 0xffffff7f827d5000 0xa5000    0xa5000    com.apple.driver.AppleACPIPlatform (6.1) 642EF8D6-8F86-3F92-B450-FDC9BAE4F3DD <14 12 11 7 6 5 4 3 1>

Dmitrys-MacBook-Pro:~ xshift$ kextstat|grep -y applehda
  108    0 0xffffff7f826e8000 0x1f000    0x1f000    com.apple.driver.AppleHDAController (280.12) 55162F3D-B7E9-315C-A7E1-C5C4C02F03EC <107 94 63 12 7 6 5 4 3 1>

Dmitrys-MacBook-Pro:~ xshift$ pmset -g assertions
2017-10-11 04:26:15 -0700
Assertion status system-wide:
   BackgroundTask                 0
   ApplePushServiceTask           0
   UserIsActive                   1
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  1
   PreventUserIdleSystemSleep     1
   NetworkClientActive            0
Listed by owning process:
   pid 481(storeassetd): [0x0000027f000b8335] 00:08:53 BackgroundTask named: "com.apple.storeagent.UpdateStaging"
   pid 338(UserEventAgent): [0x0000003e000b8125] 00:18:31 BackgroundTask named: "com.apple.tourist.notify"
    Created for PID: 449.
   pid 338(UserEventAgent): [0x00000038000b8115] 00:18:36 BackgroundTask named: "com.apple.DataDetectorsLocalSource"
    Created for PID: 435.
   pid 40(UserEventAgent): [0x0000018e000b82cb] 00:12:54 BackgroundTask named: "com.apple.mds.Health check (2).0"
    Created for PID: 60.
   pid 40(UserEventAgent): [0x00000023000b8079] 00:18:59 BackgroundTask named: "com.apple.periodic-weekly"
    Created for PID: 204.
   pid 53(powerd): [0x0000021e0008832e] 00:10:30 ExternalMedia named: "com.apple.powermanagement.externalmediamounted"
   pid 196(mds_stores): [0x00000028000b8085] 00:18:53 BackgroundTask named: "com.apple.metadata.mds_stores.power"
   pid 206(softwareupdated): [0x0000028e0001833c] 00:08:38 PreventUserIdleSystemSleep named: "Updating Software (com.apple.SoftwareUpdate.Session)"
    Details: Downloading iTunesXPatch-12.7, macOS High Sierra 10.13 Supplemental Update-
   pid 592(system_installd): [0x0000024b00018334] 00:09:46 PreventUserIdleSystemSleep named: "Installing Software (com.apple.PackageKit.installd.commit)"
    Details: Installing "XProtectPlistConfigData"
   pid 94(hidd): [0x000000220009805c] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294968033.3"
    Timeout will fire in 119 secs Action=TimeoutActionRelease
   pid 60(mds): [0x0000001e000b8041] 00:19:03 BackgroundTask named: "com.apple.metadata.mds.power"
Kernel Assertions: 0x4=USB
   id=500  level=255 0x4=USB mod=12/31/69, 4:00 PM description=com.apple.usb.externaldevice.14500000 owner=USB2.0-CRW
   id=502  level=255 0x4=USB mod=12/31/69, 4:00 PM description=com.apple.usb.externaldevice.14700000 owner=Mass Storage Device
Idle sleep preventers: IODisplayWrangler