Contribute
Register

DSDT patching issues with Lenovo T410

Status
Not open for further replies.
No idea ... other than it seemed like that was the one thing I was missing to getting sleep working when I was reading other threads/forums about getting sleep working in 10.9 .... nobody mentioned it was for Ivy only and I recalled needing it on the toshiba laptop w/ the 3rd gen i3, thought it applied to all of the i series processors.

So do you know what else I have to patch to get sleep to work on this 1st gen i5?

It depends on specifically what's wrong with sleep.
 
When I tell the system to sleep the display turns off and this is all that is logged.
The machine no longer sleeps at all, when I was using the wrong BIOS version DSDT I was able to almost sleep, as in it would sleep and wake instantly with EHCI being to blame in the logs.

Code:
May  7 17:13:57 eweiman-t410-osx.local DisplayLinkManager[135]: DLUA reports system will sleep
May  7 17:13:57 eweiman-t410-osx.local WindowServer[166]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7fac925b61e0(2001)
May  7 17:13:57 eweiman-t410-osx.local WindowServer[166]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x7fac925b61e0(2001)
May  7 17:14:08 eweiman-t410-osx.local DisplayLinkManager[135]: DLUA reports system will wake
May  7 17:14:08 eweiman-t410-osx.local HWMonitor[278]: ATA block storage device appeared 38915
May  7 17:14:08 eweiman-t410-osx.local HWMonitor[278]: ATA block storage device appeared 39171
May  7 17:14:08 eweiman-t410-osx.local HWMonitor[278]: battery device appeared 39427
May  7 17:14:08 eweiman-t410-osx.local WindowServer[166]: CGXDisplayDidWakeNotification [465906150063]: posting kCGSDisplayDidWake
May  7 17:14:08 eweiman-t410-osx.local WindowServer[166]: handle_will_sleep_auth_and_shield_windows: Deferring.
May  7 17:14:13 eweiman-t410-osx.local HWMonitor[278]: reading SMART data for Samsung SSD 840 EVO 120GB
May  7 17:14:13 eweiman-t410-osx.local HWMonitor[278]: added battery device 42T4791-16240 (39427)
 

Attachments

  • DSDT.aml
    46.4 KB · Views: 181
  • eweiman-t410-osx.ioreg
    1.7 MB · Views: 167
  • system.log.zip
    71 KB · Views: 119
Not sure what happened to my previous post (if it ever shows up)...

It does sleep... it just instantly wakes for EHC2
All this USB bus has on it is the Integrated Webcam which does work in photobooth.

May 7 17:29:02 eweiman-t410-osx kernel[0]: Wake reason: EHC2
May 7 17:29:27 eweiman-t410-osx kernel[0]: full wake (reason 1) 25803 ms
 
If I leave the USB stick in that I'm using to boot from then it will wake due to EHC1 and notify me that I didn't remove the USB device properly.
 
Not sure what happened to my previous post (if it ever shows up)...

It does sleep... it just instantly wakes for EHC2
All this USB bus has on it is the Integrated Webcam which does work in photobooth.

May 7 17:29:02 eweiman-t410-osx kernel[0]: Wake reason: EHC2
May 7 17:29:27 eweiman-t410-osx kernel[0]: full wake (reason 1) 25803 ms

You need DSDT patches: https://github.com/RehabMan/Laptop-DSDT-Patch
Apply: "6-series USB"

Don't worry that your system is 5-series not 6-series. It doesn't matter.
 
Thanks for all the help man.
Can't resume from Hibernate even with ForceWake=Yes as it complains about the system using encrypted sleep image.
I haven't been able to disable secure memory ... any tips?


I've tried various combinations of these:

sudo pmset -a hibernate mode <#>

0 - Old style sleep mode, with RAM powered on while sleeping
1 - Hibernation mode, with RAM contents written to disk, system totally shut down
3 - The default mode RAM is powered on while sleeping, but RAM contents are also written to disk before sleeping.
5 - This is the same as mode 1, but it’s for those using secure virtual memory.
7 - This is the same as mode 3, but it’s for those using secure virtual memory.

Using:
0 = works, after wake the power LED continues to breathe
1 = unable to wake due to encrypted sleep image
3 = works, after wake the power LED continues to breathe, unable to wake if powered off due to encrypted image
5 = unable to wake due to size too large
 
Thanks for all the help man.
Can't resume from Hibernate even with ForceWake=Yes as it complains about the system using encrypted sleep image.
I haven't been able to disable secure memory ... any tips?

Hibernate does not work. Disable it:
Code:
# change hibernatemode from 0 to 3
sudo pmset -a hibernatemode 0
# good idea to remove sleepimage
sudo rm /var/vm/sleepimage
# keep OS X from re-creating it
sudo mkdir /var/vm/sleepimage

0 - Old style sleep mode, with RAM powered on while sleeping
...
0 = works, after wake the power LED continues to breathe

Probably an issue with DSDT. Try to find out what code controls the LED and make sure it runs on wake (method _WAK).
 
Thanks I'll check it out.
USB is dead after resume... it logged the following.
Do I assume that means it thinks USB is still sleeping and that I'm missing a WAK method in the USB?

Code:
May  7 21:01:23 eweiman-t410-osx kernel[0]: Wake reason: SLPB LID
May  7 21:01:23 eweiman-t410-osx kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
May  7 21:01:23 eweiman-t410-osx kernel[0]: No interval found for . Using 8000000
May  7 21:01:23 eweiman-t410-osx kernel[0]: Previous Sleep Cause: 5
May  7 21:01:24 eweiman-t410-osx kernel[0]: full wake (reason 1) 1120 ms
May  7 21:01:24 eweiman-t410-osx kernel[0]: USBF:    468.521    AppleUSBEHCI: setPowerState - PCI device still has PME status bit set. PMCSR is 0x8000
May  7 21:01:24 eweiman-t410-osx kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1a000000) may have caused a wake by issuing a remote wakeup (2)
May  7 21:01:24 eweiman-t410-osx kernel[0]: The USB device USB Mass Storage Device (Port 2 of Hub at 0x1a100000) may have caused a wake by being disconnected
May  7 21:01:24 eweiman-t410-osx kernel[0]: [0xffffff8011a25800](0)/(5) Device not responding
 

Attachments

  • DSDT.aml
    46.8 KB · Views: 197
Thanks I'll check it out.
USB is dead after resume... it logged the following.
Do I assume that means it thinks USB is still sleeping and that I'm missing a WAK method in the USB?

Code:
May  7 21:01:23 eweiman-t410-osx kernel[0]: Wake reason: SLPB LID
May  7 21:01:23 eweiman-t410-osx kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
May  7 21:01:23 eweiman-t410-osx kernel[0]: No interval found for . Using 8000000
May  7 21:01:23 eweiman-t410-osx kernel[0]: Previous Sleep Cause: 5
May  7 21:01:24 eweiman-t410-osx kernel[0]: full wake (reason 1) 1120 ms
May  7 21:01:24 eweiman-t410-osx kernel[0]: USBF:    468.521    AppleUSBEHCI: setPowerState - PCI device still has PME status bit set. PMCSR is 0x8000
May  7 21:01:24 eweiman-t410-osx kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1a000000) may have caused a wake by issuing a remote wakeup (2)
May  7 21:01:24 eweiman-t410-osx kernel[0]: The USB device USB Mass Storage Device (Port 2 of Hub at 0x1a100000) may have caused a wake by being disconnected
May  7 21:01:24 eweiman-t410-osx kernel[0]: [0xffffff8011a25800](0)/(5) Device not responding

I would probably use ACPIDebug to trace _WAK and be sure it is executing from beginning to end.

See: https://github.com/RehabMan/OS-X-ACPI-Debug
 
sorry to bring back to life this old thread! i have a T410i (only intel gpu) can´t get full qe/ci working properly, cause when it boots up the screen is distorted! could anyone bring me the config files or clover efi configs or chameleon or whatever!!! its been 2 weeks trying!
 
Status
Not open for further replies.
Back
Top