Hide Forgot
Description of problem: I've two display cards in system and running xrandr -q shows only one card. I need the other card for dual-head setup to span the desktop to the second screen. Version-Release number of selected component (if applicable): xorg-x11-drv-ati-6.14.1-2.20110525gitfe5c42f51.fc15.x86_64 How reproducible: Always. Steps to Reproduce: 1. Boot system with two display cards 2. run xrandr -q 3. examine output Actual results: % xrandr -q Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 DisplayPort-1 disconnected (normal left inverted right x axis y axis) DVI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 60.0*+ 1920x1200 59.9 1600x1200 60.0 1680x1050 60.0 1280x1024 75.0 60.0 1280x800 59.8 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 % Expected results: Two interfaces. Additional info: System does not have xorg.conf file and actually I don't want one. It should be automatic. :) # lspci |grep VGA 01:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4550] 02:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4550]
Yeah, well, multiple GPU setup isn't automatic because too many things break (like GLX), and isn't likely to be any time soon.
Let's keep this report open anyway to track this matter, shall we. Couple questions raised and would appreciate for any clarification: a) Would it be possible to implement without GLX and others (somehow lobotomizing 'em) if they're not needed for regular office desktop? b) Does this matter only affect physical cards or just GPUs visible in PCI bus that would be on same single card? c) When xorg.conf is still needed, what would be the minimal set of sections required? * ServerLayout * 2 x Device (for BusID) Can Monitor and Screen sections can be omitted and autoprobed?
I came up with following minimal xorg.conf - can't get it smaller: ---8<-----/etc/X11/xorg.conf---------------------------------------- Section "ServerLayout" Identifier "l0" Screen "s0" Screen "s1" RightOf "s0" EndSection Section "ServerFlags" Option "Xinerama" "on" EndSection Section "Device" Identifier "d0" Driver "ati" BusID "PCI:1:0:0" EndSection Section "Device" Identifier "d1" Driver "ati" BusID "PCI:2:0:0" EndSection Section "Screen" Identifier "s0" Device "d0" EndSection Section "Screen" Identifier "s1" Device "d1" EndSection -------->8------------------------------------------------------------ PCI addresses are from lspci output as listed in initial description.
(In reply to comment #2) > a) Would it be possible to implement without GLX and others (somehow > lobotomizing 'em) if they're not needed for regular office desktop? gnome-shell requires GLX. So, not really, no. > b) Does this matter only affect physical cards or just GPUs visible in PCI bus > that would be on same single card? It affects any scenario with multiple GPUs.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
This is a feature enchangement, not a bug for any particular release.
This bug is currently assigned to an unsupported release. If you think this bug is still valid and should remain open, please re-assign it to a supported release (F22, F23) or to rawhide. Bugs which will be assigned to an unsupported release are going to be closed as EOL (End Of Life) on January 26th, 2016.