Jump to content

Yosemite sleeps only first time


Paologas91
 Share

46 posts in this topic

Recommended Posts

Hi there, i have a problem with sleep/wake. My yosemite auto-sleeps on the first time, then i wake and on the second time he does not sleeps more...screen stays black and computer does not suspend... i tried all darkwake options... i read somewhere that could be fixed by modifying dsdt... u could help me? thanks for help! 

Link to comment
Share on other sites

Hi,

 

After the first time sleep/wake, open up terminal and type: 

pmset -g assertions

The output should be similar to this: 

Assertion status system-wide:
   BackgroundTask                 0
   ApplePushServiceTask           0
   UserIsActive                   0
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  0
   PreventUserIdleSystemSleep     1
   NetworkClientActive            0
Listed by owning process:
   pid 1479(Unison): [0x000000950001017e] 11:57:31 NoIdleSleepAssertion named: "Unison Transfers" 
Kernel Assertions: 0x4=USB
   id=500  level=255 0x4=USB mod=27-05-15 02:43 description=EHC1 owner=AppleUSBEHCI
   id=501  level=255 0x4=USB mod=27-05-15 02:55 description=XHC1 owner=AppleUSBXHCI
   id=502  level=255 0x4=USB mod=27-05-15 02:48 description=EHC2 owner=AppleUSBEHCI

In my case Unison will prevent sleep. 

  • Like 2
Link to comment
Share on other sites

Hi,

 

After the first time sleep/wake, open up terminal and type: 

pmset -g assertions

The output should be similar to this: 

Assertion status system-wide:
   BackgroundTask                 0
   ApplePushServiceTask           0
   UserIsActive                   0
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  0
   PreventUserIdleSystemSleep     1
   NetworkClientActive            0
Listed by owning process:
   pid 1479(Unison): [0x000000950001017e] 11:57:31 NoIdleSleepAssertion named: "Unison Transfers" 
Kernel Assertions: 0x4=USB
   id=500  level=255 0x4=USB mod=27-05-15 02:43 description=EHC1 owner=AppleUSBEHCI
   id=501  level=255 0x4=USB mod=27-05-15 02:55 description=XHC1 owner=AppleUSBXHCI
   id=502  level=255 0x4=USB mod=27-05-15 02:48 description=EHC2 owner=AppleUSBEHCI

In my case Unison will prevent sleep. 

This is what happens to me :

 

Last login: Wed May 27 14:52:42 on console

Paolos-iMac:~ paologasparro$ pmset -g assertions

2015-05-27 15:00:41 +0200 

Assertion status system-wide:

   BackgroundTask                 0

   ApplePushServiceTask           0

   UserIsActive                   0

   PreventUserIdleDisplaySleep    0

   PreventSystemSleep             0

   ExternalMedia                  0

   PreventUserIdleSystemSleep     0

   NetworkClientActive            0

Kernel Assertions: 0x10c=USB,BT-HID,MAGICWAKE

   id=502  level=255 0x4=USB mod=27/05/15 17:02 description=XHC1 owner=AppleUSBXHCI

   id=503  level=255 0x100=MAGICWAKE mod=27/05/15 15:10 description=en0 owner=en0

   id=505  level=255 0x8=BT-HID mod=01/01/70 01:00 description=com.apple.driver.IOBluetoothHIDDriver owner=IOAppleBluetoothHIDDriver

Paolos-iMac:~ paologasparro$ 

Link to comment
Share on other sites

The intel 9 series usb patch from palms repo was applied? 

It does not differ from the 7/8 series patch, so i applied the usb3.0 multiplex patch.

 

Don't know if it is an USB issue, but worth a try. 

 

Can you also type in terminal: 

syslog |grep -i "Wake reason"

DSDT.aml.zip

  • Like 1
Link to comment
Share on other sites

 

The intel 9 series usb patch from palms repo was applied? 

It does not differ from the 7/8 series patch, so i applied the usb3.0 multiplex patch.

 

Don't know if it is an USB issue, but worth a try. 

 

Can you also type in terminal: 

syslog |grep -i "Wake reason"

this is the output...

post-1374472-0-32600400-1432733957_thumb.png

Link to comment
Share on other sites

Sometimes removing _PRW in USB Devices into DSDT can resolve.

Did not work for me in the past, in my own DSDT i used the patch from RehabMan's repo: 

                Name (_PRW, Package (0x02)  // _PRW: Power Resources for Wake
                {
                    0x6D, 
                    0x03
                })

Changed from the standard 0x09, 0x04. 

 

Might just be that just disabling the Network thing solves it. 

  • Like 1
Link to comment
Share on other sites

Did not work for me in the past, in my own DSDT i used the patch from RehabMan's repo: 

                Name (_PRW, Package (0x02)  // _PRW: Power Resources for Wake
                {
                    0x6D, 
                    0x03
                })

Changed from the standard 0x09, 0x04. 

 

Might just be that just disabling the Network thing solves it. 

i tried disabling the network option but it has no effect.....still having problem... :(

 

EDIT: I found this link where a guy has my problem and fixed it......what do u think?

http://olarila.com/forum/viewtopic.php?f=31&t=4065

Link to comment
Share on other sites

I added this to my XHC Device:

            Method (_DSM, 4, NotSerialized)
            {
                Store (Package (0x04)
                    {
                        "device-id", 
                        Buffer (0x04)
                        {
                            0x03, 0x0C, 0x30, 0x00
                        }, 
                        "AAPL,clock-id", 
                        Buffer (One)
                        {
                            0x01
                        }
                    }, Local0)
                DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                Return (Local0)
            }

It may only get my USB recognized.  If that's all it does, sorry.  My H_EC device does not have/need a _PRW method and our chipsets aren't that different.

Link to comment
Share on other sites

It comes down to what Alan and i discussed above. I made the changes to _PRW under EHC1 EHC2 and XHC1. 

 

If it does not work, remove _PRW from those devices and see if that changes anything. 

ok so i tried but still not working.....but i noticed something weird...

after the first sleep, there is another problem: cpu speedstep minimum does not get more 0.80mhz... and the red light on the case ( i think is hdd light)  is flashing every second........ maybe its this the problem it wont let me sleep the second time......  so i think the answer to my problem is that the system after the first sleep is not like when i start pc for the first time..... i dont know if i am explaning..... but this is what i see! 

 

anyway a friend gave me this new dsdt that i am using (with LCP loading) so i am using this now.

DSDT.aml.zip

Link to comment
Share on other sites

Besides the DSDT, do you also have an SSDT? And which boot loader are you using? 

I am using UEFI clover bootloader. Clover generates me SSDT...that is what my friend said to me when he gave me the config.plist today....

Link to comment
Share on other sites

Sometimes removing _PRW in USB Devices into DSDT can resolve.

how can i remove _PWR in USB devices? i attach my dsdt ....thank u !

can be a problem with bluetooth or wifi , but this wake reason GLAN is some with Ethernet, try change the kext Ethernet for other that work to your card

i already disabled wake-up by ethernet on power saving with no results......

EDIT: GLAN is not some with ethernet because i press the mouse button to resume system .. i am sure of this...

DSDT.aml.zip

Link to comment
Share on other sites

 

Well, the DSDT has been edited multiple times, the Network option has been disabled, could you do another:

syslog |grep -i "Wake reason" 

And also: 

pmset -g assertions

it tells GLAN but i only left-click mouse to wake the system (the first sleep)

post-1374472-0-49116800-1432760502_thumb.png

Link to comment
Share on other sites

 Share

×
×
  • Create New...