Bug 66801 - xrandr -q lists only one screen for 2 cards, 2 monitors
Summary: xrandr -q lists only one screen for 2 cards, 2 monitors
Alias: None
Product: xorg
Classification: Unclassified
Component: App/xrandr (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Keith Packard
QA Contact:
Depends on:
Reported: 2013-07-10 21:58 UTC by Duane Voth
Modified: 2013-07-18 20:23 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

xorg.conf (3.38 KB, text/plain)
2013-07-10 21:58 UTC, Duane Voth
no flags Details

Description Duane Voth 2013-07-10 21:58:50 UTC
Created attachment 82303 [details]

Xorg exhibits several problems possibly because of Dual 4550 Radeon cards.
1) 66796 - radeon dual card configure segmentation fault
2) 66799 - 1920x1080 height too large for virtual size (dual radeon)
3) (this bug)  xrandr -q lists only one screen for 2 cards, 2 monitors

With the workaround listed in 66799 applied to the xorg.conf, both cards/monitors are alive and can be used via:

DISPLAY=:0.0 aterm &
DISPLAY=:0.1 aterm &

however xrandr -q only lists the primary:

$ xrandr -q
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DVI-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
   1680x1050      59.9*+
   1280x1024      75.0     60.0  
   1152x864       75.0  
   1024x768       75.1     60.0  
   800x600        75.0     60.3  
   640x480        75.0     60.0  
   720x400        70.1
Comment 1 Alex Deucher 2013-07-10 22:08:27 UTC
xrandr only supports a single GPU per screen.  You need to specify the display to run xrandr against.  E.g.,
DISPLAY=:0.0 xrandr
DISPLAY=:0.1 xrandr
Comment 2 Duane Voth 2013-07-18 20:23:38 UTC
So in this case xrandr can't be used to position displays (since it only knows about one at a time) correct?

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.