Contribute
Register

lid sleep fix possible without disabling it?

Status
Not open for further replies.

the-braveknight

Moderator
Joined
Nov 24, 2015
Messages
1,220
Motherboard
Lenovo Legion Y520 (Clover)
CPU
i7-7700HQ
Graphics
HD 630 (1920x1080) + Nvidia GTX 1060
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Hello all,
Today, I found out that I didn't need the GPRW USB patch, turns out that it's not needed when having correct USB configuration (when certain ports are disabled)... then I wondered if it's possible to fix the lid sleep instead of renaming _PRW to XPRW... Is it possible?

Thanks.
 
Bump to top xD

Any ideas? :D
 
Hello all,
Today, I found out that I didn't need the GPRW USB patch, turns out that it's not needed when having correct USB configuration (when certain ports are disabled)... then I wondered if it's possible to fix the lid sleep instead of renaming _PRW to XPRW... Is it possible?

Thanks.

Broken lid sleep with _PRW present is due to something not working correctly with the GPE methods/events.
 
Broken lid sleep with _PRW present is due to something not working correctly with the GPE methods/events.
Anyway to fix it?
 
Not that I know of.
Too bad... :(

I thought it had something to do with USB wake being disabled, like I stated earlier, my USB card reader was causing the instant wake issues, so after I disabled it, I no longer had to disable USB wake (GPRW)...

Well what if we remove the LID _PRW object, this way the laptop will sleep when the lid is closed, and in the DSDT, we trigger another _PRW object in the lid method (_Qxx) maybe? Is such a workaround possible?
 
Too bad... :(

I thought it had something to do with USB wake being disabled, like I stated earlier, my USB card reader was causing the instant wake issues, so after I disabled it, I no longer had to disable USB wake (GPRW)...

Well what if we remove the LID _PRW object, this way the laptop will sleep when the lid is closed, and in the DSDT, we trigger another _PRW object in the lid method (_Qxx) maybe? Is such a workaround possible?

I have never run into it on any of my laptops. But I suspect it has to do with the corresponding GPE method (_Lxx) not being triggered or not working correctly.
 
Status
Not open for further replies.
Back
Top