Comment 3 for bug 201342
Revision history for this message
| Adrian Wilkins (adrian-wilkins) wrote Re: Uses single refreshrate for separate X screens | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
Noticed this again recently because the "primary" screen appears to have switched between driver versions.
Despite what's said above, on my hardware the driver seems to pick the screen it syncs to and does not respect the "primary" setting for this purpose.
Previously this meant that I had flipped my monitor cables around (and flipped the screen config around in Windows) so that the synced display was my primary display and the tearing was on the secondary. Now the sync has shifted to the other display so I guess I'll be flipping my cables around again.
This is most noticeable when playing video as one does not drag screens around constantly. I have a feeling that in many cases bugs like #151674 are probably also attributable to this fault.
Isn't this down to some awful kludge in X that identifies displays by a concatenation of their resolution and refresh rate - the end result being that you can't have two displays with identical resolutions and refresh rates because that would mean X couldn't tell them apart? It would seem to be worth checking this rumour out but I don't have the time or grok C and X well enough.