![]() ![]() |
Jul 17 2006, 05:05 AM
Post
#1
|
|
|
Group: Members Posts: 138 Joined: 12-February 04 Member No.: 1,830 |
Has anyone else had any problems executing 'apm -s' from X? I have found that when I do this, upon wakeup X runs really slowly, and I get a load of errors about timeouts with read and write pointers. If I use the suspend button, I have no problems. Similarly, running 'apm -s' from the console wakes up with no problems.
So it appears that pressing the suspend button does something more than just call apm.x, and this extra behaviour prevents the X problem from occurring. Does anyone know anything about this? Does it do something with the framebuffer? I'd like to get this working so that I can control automatic suspends if I wakeup the Z in the night to do some night-time processing! I'm running RC12 on an SL-860. Dan |
|
|
|
Jul 17 2006, 06:19 AM
Post
#2
|
|
![]() Group: Members Posts: 1,099 Joined: 17-December 03 From: Athens, Greece Member No.: 1,210 |
'xset dpms force off' ?
|
|
|
|
Jul 17 2006, 06:30 AM
Post
#3
|
|
|
Group: Members Posts: 138 Joined: 12-February 04 Member No.: 1,830 |
|
|
|
|
Jul 17 2006, 12:08 PM
Post
#4
|
|
|
Group: Members Posts: 343 Joined: 3-October 05 From: NZ Member No.: 8,243 |
I think I recall reading about this problem in an earlier thread, and the solution above from pgas was the answer there too.
All the apm stuff is actually in the kernel, so I guess the userland programs are just interfacing with that, rather than apm and xset actually doing any power management. I would presume that pressing the power button would also shortcut straight to the kernel apm... |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 23rd May 2013 - 01:17 PM |