I'm experiencing problems with dual-head setup and xrandr 1.2 following a recent upgrade to Ubuntu 7.10 (Gutsy) from Ubuntu 7.04 (Feisty) on my Dell Latitude D810 laptop with docking station. This worked on Feisty with the ati driver and it still functions when I change over to the "fglrx" driver (which rules out bad hardware). I have a striped down configuration xorg.conf (see below) with two identical Dell FP1905 monitors connected through a docking station, one via VGA-0 and the other via DVI-0. On startup the DVI-0 monitor functions as expected and the LVDS monitor initializes but displays nonsense (some wierd color patterns). I then issue the following command to disable the LVDS: xrandr --output LVDS --off At this point, I can then activate the VGA-0 monitor with this command: xrandr --output VGA-0 --auto However, VGA-0 then displays "1: Analog Input Cannot Display This Video Mode". But, the working screen will "shift" from DVI-0 to VGA-0 when I issue the following command: xrandr --output DVI-0 --crtc 0 --output VGA-0 --crtc 1 At this point, my desktop is properly displayed on VGA-0 while DVI-0 displays "2: Digital Input Cannot Display This Video Mode". Is it possible that this bug is related to "crtc 0" on the ATI x600 (M24)? I have tried turning the "LVDSBiosNativeMode" option to "false", turning the "DRI" option to "off" and playing around with the "Virtual" option. I've even tried completely removing the xorg.conf file, but nothing has had a positive impact. I opened a bug report with Ubuntu ( https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/172601 ) and am opening this at their request. I can supply a log file upon request and my current xorg.conf is included below. The Ubuntu package description for this driver lists the version as "1:6.7.195-1ubuntu2". Tony /etc/X11/xorg.conf: Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device" "/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents" "true" Option "Device" "/dev/psaux" Option "Protocol" "auto-dev" Option "HorizEdgeScroll" "0" EndSection Section "InputDevice" Driver "wacom" Identifier "stylus" Option "Device" "/dev/input/wacom" Option "Type" "stylus" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice" Driver "wacom" Identifier "eraser" Option "Device" "/dev/input/wacom" Option "Type" "eraser" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice" Driver "wacom" Identifier "cursor" Option "Device" "/dev/input/wacom" Option "Type" "cursor" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "Device" Identifier "ATI Technologies Inc M24 1P [Radeon Mobility X600]" Driver "ati" BusID "PCI:1:0:0" Option "Monitor-DVI-0" "Generic Monitor" Option "Monitor-VGA-0" "Generic Monitor 2" Option "DRI" "false" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" EndSection Section "Monitor" Identifier "Generic Monitor 2" Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies Inc M24 1P [Radeon Mobility X600]" Monitor "Generic Monitor" DefaultDepth 24 SubSection "Display" Virtual 3840 2400 Modes "1280x1024" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "Synaptics Touchpad" EndSection
Please attach your log file.
Created attachment 13020 [details] X11 log from current session
As reported on launchpad (https://bugs.launchpad.net/bugs/172601) I have a rather similar problem, with the following setup: Dell Latitude D610 laptop Dockingstation 2 external monitors, each capable of 1600x1200 (one connected via VGA, and one via DVI) Tormod Volden requested that I try with the latest version of the driver from his PPA archive (xserver-xorg-video-ati 1:6.7.196+git20071210-0ubuntu0tormod), and post the results/logs. I had no better luck with this version than with prior versions from Ubuntu Gutsy -- the external monitor that's being driven by CRTC 0 goes black (or displays a monitor-generated warning that it's unable to display the signal it gets, for the DVI-attached monitor) when I try to use its preferred mode, while the monitor being driven by CRTC 1 works fine. If I swap which external monitor is being driven by which CRTC around, it's always the one driven by CRTC 0 that's unable to display the preferred mode. I tested this by running "xinit" from a text vt as root, and performing the following commands in the resulting xterm: # Initial output was on LVDS + DVI-0. xrandr --output LVDS --off --output VGA-0 --auto # Monitor LVDS went black, and monitor VGA-0 stayed black. xrandr --output VGA-0 --off --output LVDS --auto # Monitor LVDS came alive again. xrandr --verbose -q > /tmp/xrandr-q.lvds+dvi xrandr --output LVDS --off --output VGA-0 --auto xrandr --verbose -q > /tmp/xrandr-q.vga+dvi # Repeat to get copies of xrandr output. Monitor VGA-0 still black. xrandr --output LVDS --off --output VGA-0 --auto --mode 1280x1024 # Monitor VGA-0 now came alive, but with a non-optimal resolution. xrandr --verbose -q > /tmp/xrandr-q.vga-reduced+dvi # Capture more xrandr output xrandr --output VGA-0 --off --output LVDS --auto # Move back to LVDS, before quitting. I'll attach my xorg.conf and the X log resulting from this exercise shortly; let me know if there's other data you'd like me to collect.
Created attachment 13026 [details] Harald Meland's xorg.conf
Created attachment 13027 [details] Harald's X11 log from testing 1:6.7.196+git20071210-0ubuntu0tormod
I've fixed this and will be committing it shortly once I've finished testing a few things. bugs 12913 and 13533 are also related.
*** This bug has been marked as a duplicate of bug 12913 ***
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.