Stefan, Sorry to trouble you again; by all means tell me "this is too off-topic for you" or "someone else is fixing it" or perhaps point me at a suitable place to discuss this (I'm wary of contributing directly because I'l not really an OS hacker -- I'm more of a compiler person).
Anyway you remark: > This looks like https://bugzilla.novell.com/show_bug.cgi?id=197858 > I don't think it is related to suspend at all, it is an Xserver bug. Well, yes and no. I've read the above bugzilla, and it certainly looks like this (I note this thread seems not to be active recently, so more input may be welcome?). In particular I note the following interaction of X and suspend (which I didn't see reported there) 1. I power up, and login directly to FVWM2 (i.e. little messing around) 2. then powersave events (I use plug/unplug laptop power) then do *not* cause the backlight to be turned on. So X is working properly. 3. However, if I then force suspend with /usr/bin/powersave -u and then resume then: 4. powersave events now *do* cause the backlight to turn on :-( So, is this more a matter of the X-server (or some hardware) not being reset properly after resume? [Of course, it may be localised to my hardware, but the bugzilla report seems to indicate it's a more general (and unsolved) problem. Incidentally, if instead of 3, I do: 3'. force hibernate with /usr/bin/powersave -U then the same situation occurs 4. powersave events now *do* cause the backlight to turn on :-( [There seems an additional oddity -- my testing "xset dpms 0 0 5" (which I set before set before the suspend/hibernate) is still reflected in xset -q afterwards, but its effect has been lost by the Xserver.] I suspect the Xserver perhaps needs reloading after suspend/hibernate. Is there a forum I can contribute positively to this, instead of bugging you? Cheers, Alan > > OK. There is a further PM issue which I've only just pinned down > > after installing SUSE 10.2. I can chase more, esp. if you give me > > some pointers, but I thought I'd mention in now in case you've seen > > it before. > > > > I'm running FVWM2 on standard SUSE 10.2, so the desktops are not > > interfering/(taking proper control) ;-) > > :-) > > > Anyway, the curio I've notices is that: > > 1. *boot up* in SUSE 10.2, and FVWM (as default WM) > > 2. my .profile contains "xset dmps 0 0 300" [I've also tried just > > "xset dmps 300" and "xset dmps 0 300" so the screen correctly powers > > off after 5 mins inactivity. > > 3. BUT, after running "/usr/bin/powersave" and restore, > > then I find that while the screen powers off after 5 mins, after a few > > seconds (3-40 seems to be the range I can make, rather variable but > > I can't accurately control it [= some daemon?]) the backlight turns > > on, even though the screen shows no video. > > This looks like https://bugzilla.novell.com/show_bug.cgi?id=197858 > > > I believe is also the case with s2ram and pm-suspend. > > This suggests that powersave/s2ram does not reset enough of the video > > controller (unfortunately I'm not an expert on the h/w control here). > > I don't think it is related to suspend at all, it is an Xserver bug. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
