Page 1 of 1
DPMS (Suspended Display) Does Not Resume on Keypress / Mouse
Posted: Mon Sep 11, 2006 3:39 pm
by tangel
Running completely current system (BIOS 1.09) and Windows XP (SP2+hotfixes, ATI Driver Package 8.241.1) as of this post. Maybe 1 out of 30 times my LCD suspends (laptop still running), it will not "awaken" after a key is pressed or mouse is clicked. Only solution appears to be closing the lid and opening it again. Not a major pain but annoying nonetheless.
Anyone else experience something similar?
Posted: Mon Sep 11, 2006 3:49 pm
by whakojacko
i have this problem sometimes when the display turns off automatically. When I manually suspend it, the mouse always resumes it
Posted: Tue Sep 12, 2006 3:03 am
by nelson
I have this problem, and it's very annoying! I have my system plugged into AC, configured to never lower brightness or refresh rate; just turn off display after 25 minutes. If it doesn't come back I find suspending the laptop (by shutting the lid) and resuming fixes it.
Posted: Tue Sep 12, 2006 9:35 am
by whakojacko
nelson wrote:I have this problem, and it's very annoying! I have my system plugged into AC, configured to never lower brightness or refresh rate; just turn off display after 25 minutes. If it doesn't come back I find suspending the laptop (by shutting the lid) and resuming fixes it.
well you can configure it not to turn off the display
Control Panel -> Power options And then change the hd off monitor off standby and hibernate settings. I think this thread is more about annoyance that theyre monitor wont reumse properly, not that it turns off in the first place
Posted: Tue Sep 12, 2006 11:58 am
by Mobile_Mike
Posted: Tue Sep 12, 2006 6:48 pm
by Scratch
I've now applied the updated bios, latest video package and the MS WinXP hotfix mentioned in Mobile Mike's reply above to 4 T60p systems that had this issue. None have had the problem since, but I continue to monitor them.
This has been the only "fix" that has lasted this long so I'm fairly confident that the issue has been put to bed...fingers crossed and all that...
Posted: Thu Sep 21, 2006 6:30 am
by JohnDrake
If you are not using the factory image, the hotfix package (now on the device driver matrix, near the bottom) usually fixes this.
Anyone who built their own image should apply the hotfix package.
Posted: Thu Sep 21, 2006 8:13 am
by nelson
The fix that Mobile_Mike is referring to is
Microsoft KB 917332. The fix isn't on Windows Update; if you feel lucky you can try downloading a Microsoft hotfix from
this unauthorized site. I haven't.
