When playing a video clip with Xine (built from the latest stable sources) video clips play normal for a few seconds and then the screen goes blank for about 1 second--then the cycle repeats. The video card is an integrate radeon on a HP Compaq dx5150 system. Because the problem is unique to xine (doesn't happen on totem) I have file a BZ with Xine as well. I don't recall seeing this problem before I updated my ati driver from the Fedora 8 "updates-testing" yum repository.
Xine messes with dpms calls which cause the driver to unblank the screen periodically. It's not really a driver issue.
Alex, The Xine developer had me run the following command which caused the screen to blank just as it does when I play a video: xset dpms force on He stated that running this command would "confirm whether it's a driver issue". I'm assuming that this command should not cause the screen to blank. Here is the respective bug report for context: http://bugs.xine-project.org/show_bug.cgi?id=54
I would like to keep this open until someone convinces me where the problem lies.
(In reply to comment #2) > Alex, > > The Xine developer had me run the following command which caused the screen to > blank just as it does when I play a video: > > xset dpms force on > > He stated that running this command would "confirm whether it's a driver > issue". I'm assuming that this command should not cause the screen to blank. This isn't a driver issue. That command forces the displays on. If you run 'xset dpms force off' your monitors be forced off. If you run 'xset dpms force on' your monitors will be forced on. forcing an output on or off may include some flicker depending on what programming sequence is required to do it. What xine is doing is abusing that command to prevent the screen saver from kicking in by repeatedly executing it.
No, it *is* your bug. I see no reason to blank one monitor to unblank another monitor when it's already unblanked. (Fair enough if it actually needs to be unblanked, though...)
Alex, if you track the state and avoid going thru the entire output power up sequence when not required the flicker should go away. In AtomBIOS terms calling TMDSA/LVTMAOutputControl(enable) should be OK.
Please try latest ati git.
Just tested; looks good to me.
Darren, Alex, Thanks for working together on this. I think this is the quickest turn-around I've experience on an Xorg bugzilla. Bryan
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.