[Bug 89661] [suse sna] failed to set mode: Invalid argument [22]

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=89661

--- Comment #19 from Adam Taciak <taciak at gmail.com> ---
It fail even when I try to set something like:

xrandr --output DP1 --mode 1920x1080 --primary --output LVDS1 --mode 1024x768
--right-of DP1 --output DP2 --mode 1920x1080 --right-of LVDS1 --verbose

I assume that at least on two monitors should be the same refresh rate. Am I
right? In this case I tried to set the same refresh ratio on all three. 

[taciaka at LDZ9343N ~]$ ./mon.sh 
crtc 0: disable
screen 0: 8x8 2x2 mm 101.60dpi
screen 0: 4864x1080 1216x270 mm 101.60dpi
crtc 0:    1920x1080  60.00 +0+0 "DP1"
crtc 1:     1024x768  60.00 +1920+0 "LVDS1"
crtc 2:    1920x1080  60.00 +2944+0 "DP2"
xrandr: Configure crtc 2 failed
crtc 0: disable
crtc 1: disable
crtc 2: disable
crtc 3: disable
screen 0: revert
crtc 0: revert
crtc 1: revert
crtc 2: revert
crtc 3: revert
[taciaka at LDZ9343N ~]$

On Windows all 3 monitors have its native resolution, the biggest one
(1920x1200) is left rotated, but I think is not relevant.

I can add that DP1 (monitor 1920x1080) is connected via DP <==> VGA converter. 
According this page http://www.intel.com/support/graphics/sb/CS-033714.htm
(What three independent display configurations are supported? > View
information for the Intel® HD Graphics 4000/2500 of 3rd Generation Intel... >
View a comprehensive table of supported configurations and notes), my graphic
card should supports such configuration DP + DP + LVDS.

Maybe there is somthing wrong with DP <==> VGA converter... In a few hours I
will try to check this configuration with 3rd monitor connected directly via
DP.
I will also try to provide more information from Windows (if it is possible ;))

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150602/f652c864/attachment.html>