Created attachment 481100 [details] xrandr -v Description of problem: Setup: LVDS + DVI, both turned on Trying to turn off any of the monitors with xrandr fails. Version-Release number of selected component (if applicable): Software from: gfx_test_week_20110221_x86-64.iso How reproducible: Always Steps to Reproduce: 1. have LVDS and DVI turned on. 2. use xrandr to turn off any of them (eg. "xrandr --output LVDS1 --off") Actual results: Both displays are blank for 1-2 seconds, then they are both turned on again. Expected results: Display specified with "--output" option should be turned off. Additional info: 1. External monitor (DVI) connected via docking station. 2. Smolt profile: http://www.smolts.org/client/show/pub_55f01737-29ac-4707-9ea9-b53af748da2b 3. xrandr -v results in attachment.
Is this a duplicate of bug 680569 just in other direction? (switching off monitor instead of the notebook's display)
No. It's not I believe. #680569 is about problems when using GUI tool. This one is about running xrandr from command line. And the behaviour is slightly different here. 'xrandr' from CLI simply does NOT turn off any monitor, while GUI tool (#680569) turns them BOTH, no matter which one I want to.
well, it could be the same ... we just don't recognize what is LCD and what monitor. anyway, I'll keep these bugs open. Please add drm.debug=0x04 to the kernel command line, and attach (if you are able to collect them) * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
I've just uploaded all the logs in #680569. And I think you're most probably right - both cases are caused by the same issue.
I think I'll rather close this one. If there is anything terribly relevant in this case, we can reopen it anytime. *** This bug has been marked as a duplicate of bug 680569 ***