Dual-head fails with ati driver, appears related to 'crtc'

Bug #172601 reported by Anthony Brock
6
Affects Status Importance Assigned to Milestone
X.Org X server
Fix Released
Medium
xserver-xorg-video-ati (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-driver-ati

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. Unfortunately, nothing has had a positive impact. The log file from my current session is attached and my xorg.conf is included below.

Tony

$ xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 3840 x 2400
VGA-0 connected 1280x1024+0+0 (normal left inverted right) 376mm x 301mm
   1280x1024 60.0*+ 75.0 59.9
   1152x864 74.8
   1024x768 75.1 60.0
   800x600 75.0 60.3
   640x480 75.0 60.0
   720x400 70.1
DVI-0 connected (normal left inverted right)
   1280x1024 60.0 + 75.0 59.9
   1152x864 74.8
   1024x768 75.1 60.0
   800x600 75.0 60.3
   640x480 75.0 60.0
   720x400 70.1
LVDS connected (normal left inverted right)
   1920x1200 60.0 +
   1280x1024 59.9
   1280x800 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
S-video disconnected (normal left inverted right)
$

*** BEGIN 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 "1920x1200"
                Modes "1280x1024"
        EndSubSection
EndSection
Section "ServerLayout"
        Identifier "Default Layout"
        Screen "Default Screen"
        InputDevice "Generic Keyboard"
        InputDevice "Configured Mouse"
        InputDevice "Synaptics Touchpad"
EndSection
*** END xorg.conf ***

Revision history for this message
In , Orion-cora (orion-cora) wrote :

Created an attachment (id=12174)
x log

Revision history for this message
In , Orion-cora (orion-cora) wrote :

Created an attachment (id=12175)
xorg.conf

Revision history for this message
Anthony Brock (anthony-brock) wrote :
Download full text (5.4 KiB)

Binary package hint: xserver-xorg-driver-ati

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. Unfortunately, nothing has had a positive impact. The log file from my current session is attached and my xorg.conf is included below.

Tony

$ xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 3840 x 2400
VGA-0 connected 1280x1024+0+0 (normal left inverted right) 376mm x 301mm
   1280x1024 60.0*+ 75.0 59.9
   1152x864 74.8
   1024x768 75.1 60.0
   800x600 75.0 60.3
   640x480 75.0 60.0
   720x400 70.1
DVI-0 connected (normal left inverted right)
   1280x1024 60.0 + 75.0 59.9
   1152x864 74.8
   1024x768 75.1 60.0
   800x600 75.0 60.3
   640x480 75.0 60.0
   720x400 70.1
LVDS connected (normal left inverted right)
   1920x1200 60.0 +
   1280x1024 59.9
   1280x800 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
S-video disconnected (normal left inverted right)
$

*** BEGIN 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"
     ...

Read more...

Revision history for this message
Anthony Brock (anthony-brock) wrote :
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Thanks for the report. I think:
 Monitor "Generic Monitor"
should be taken out of your "Screen" section. Might not fix your issue though.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I will suggest you start without any xorg,conf at all, and see if you can get it work with xrandr commands only.

Changed in xserver-xorg-video-ati:
assignee: nobody → tormodvolden
status: New → Incomplete
Revision history for this message
Anthony Brock (anthony-brock) wrote :

I tried it without an xorg.conf file, but encountered the same issue. I'm attaching a copy of the Xorg.0.log file resulting from this latest attempt.

The biggest difference without the xorg.conf file is that the LVDS screen is chosen for the menu bars. Once disabled via xrandr, the VGA-0 monitor displays "1: Analog Input Cannot Display This Video Mode" just as before. Similarly, the error moves to the DVI-0 monitor when I issue:

xrandr --output DVI-0 --crtc 0 --output VGA-0 --crtc 1

Tony

Revision history for this message
Tormod Volden (tormodvolden) wrote :

The server detects 1920x1200 from your LVDS and adds it as a valid mode. Would it help to remove the Modes "1920x1200" from your Screen section?

Try to include a monitor section for your LVDS where you disable it with Option "Ignore" "true".

Revision history for this message
In , Orion-cora (orion-cora) wrote :

Anyone? This is killing my eyes. Just installed version 6.7.196-2.fc8 but no change. Any way to force 85Hz in xorg.conf?

Revision history for this message
In , Orion-cora (orion-cora) wrote :

Although I think the problem is that X *thinks* it is driving the display at 85Hz, but it really isn't.

Revision history for this message
In , agd5f (agd5f) wrote :

can you attach the output of xrandr? Does it help if you switch to another mode and back?

xrandr --output VGA-0 --mode 1024x768
xrandr --output VGA-0 --mode 1600x1200 --rate 85
xrandr --output VGA-0 --mode 1600x1200 --rate 75

Revision history for this message
In , Orion-cora (orion-cora) wrote :

Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 1600 x 1200
VGA-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 352mm x 264mm
   1600x1200 85.0*+ 75.0
   1024x768 85.0 75.1
   1280x1024 84.8 75.0
   1152x864 75.0
   800x600 84.9 75.0
   640x480 84.6 75.0 60.0
   720x400 70.1
LVDS disconnected (normal left inverted right x axis y axis)
S-video disconnected (normal left inverted right x axis y axis)

Switching to 1024x768 drives the monitor at 117.8kHz/146Hz.
Switching to 1600x1200x75 drives it at 74.5kHz/59Hz.
                       85 73.9kHz/59Hz.

So it doesn't appear to be twiddling the registers properly.

Revision history for this message
In , agd5f (agd5f) wrote :

does VGA work properly when the lid is open and LVDS is active?

Revision history for this message
In , Orion-cora (orion-cora) wrote :

Created an attachment (id=12939)
x log with lid up

With the laptop out of the dock and the lid up, it drives the external monitor fine. Mode is 106.8kHz/85Hz as reported by the monitor.

Revision history for this message
In , agd5f (agd5f) wrote :

(In reply to comment #8)
> Created an attachment (id=12939) [details]
> x log with lid up
>
> With the laptop out of the dock and the lid up, it drives the external monitor
> fine. Mode is 106.8kHz/85Hz as reported by the monitor.
>

seems to be an issue with pll on crtc 0. Seems like it's stuck at the panel clock. I'll investigate once I get access to monitor.

Revision history for this message
Anthony Brock (anthony-brock) wrote :
Download full text (3.9 KiB)

I've move the xorg.conf file back into place. I tried making the following additions to the configuration:

Section "Device"
        Option "Monitor-LVDS" "Laptop Monitor"
EndSection
Section "Monitor"
        Identifier "Laptop Monitor"
        Option "Ignore" "true"
EndSection

However, this resulted in a failed attempt to launch X windows (see the attached log file). The complete configuration file is below. However, this same "Monitor" section will work without the Option "Ignore" "true".

Also, thank you for the suggestion on the mode. Removing it fixes the wierd issue with the menu bars.

Unfortunately, I'm still unable to use a second screen. Is there more information I can pass along that will help in diagnosing the issue?

Tony

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 "Monitor-LVDS" "Laptop Monitor"
        Option "DRI" "false"
EndSection
Section "Monitor"
        Identifier "Generic Monitor"
        Option "DPMS"
EndSection
Section "Monitor"
        Identifier "Generic Monito...

Read more...

Revision history for this message
Tormod Volden (tormodvolden) wrote :

It looks like the server insists on using the LVDS for initial setup.

It would be great if you can file a bug upstream, bugs.freedesktop.org.

In addition to removing the "1920" mode, you can also reduce the Virtual (horizontal) size to 1920+1280 or even 1280+1280, not that it should normally matter.

Changed in xserver-xorg-video-ati:
assignee: tormodvolden → nobody
status: Incomplete → Confirmed
Revision history for this message
In , agd5f (agd5f) wrote :

I think bug 12913 and bug 13533 may be related. It seems pll 0 has issues that may be related to bios init.

Revision history for this message
Harald Meland (hmeland) wrote :

I have a similar setup here:

  Dell Latitude D610 with ATI Technologies Inc M22 [Mobility Radeon X300]
  Docking station
  Two external monitors, each capable of 1600x1200, connected through the DVI and VGA ports of the docking station

and I'm seeing a very similar problem: whichever (external) monitor that's currently using CRTC 0 can't display the signal when I attempt using the 1600x1200 mode. CRTC 1 works nicely with this mode, no matter which of the external monitors is using it. Reducing the mode for the CRTC 0-connected monitor to 1200x1024 makes it usable.

(I'm not seeing any of the LVDS "nonsense" on startup, though. I did see something like that when I tried a very wide "Virtual" setting in xorg.conf, but as I don't need that much width, I reduced it back to 3200, which doesn't cause any artefacts).

The same physical setup was working nicely under feisty (with 2x1600x1200 on Xinerama), so I'm guessing that this is a CRTC 0-specific deficiency in the radeon driver.

I've also tried upgrading the X drivers from Tormod Volden's launchpad archive (deb http://ppa.launchpad.net/tormodvolden/ubuntu gutsy main), but that didn't help.

Let me know if you would like me to attach any diagnostic data for my case.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Anthony, from Harald's comment it sounds like it might would help for you to specify: Virtual 2560 1024

Revision history for this message
Anthony Brock (anthony-brock) wrote :

First, I opened an upstream bug related to this issue:

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

Also, this didn't have an effect. In fact, I changed it to:

Virtual 1280 1024

However, I'm still seeing the "1: Analog Input Cannot Display This Video Mode" on VGA-0. The following command still "moves" the working screen from DVI-0 to VGA-0:

xrandr --output DVI-0 --crtc 0 --output VGA-0 --crtc 1

Here is the output of an "xrandr -q" command:

Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1280 x 1024
VGA-0 connected 1280x1024+0+0 (normal left inverted right) 376mm x 301mm
   1280x1024 60.0*+ 75.0 59.9
   1152x864 74.8
   1024x768 75.1 60.0
   800x600 75.0 60.3
   640x480 75.0 60.0
   720x400 70.1
DVI-0 connected 1280x1024+0+0 (normal left inverted right) 376mm x 301mm
   1280x1024 60.0*+ 75.0 59.9
   1152x864 74.8
   1024x768 75.1 60.0
   800x600 75.0 60.3
   640x480 75.0 60.0
   720x400 70.1
LVDS connected (normal left inverted right)
   1280x1024 59.9
   1280x800 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
S-video disconnected (normal left inverted right)

The attached log is from this attempt.

Revision history for this message
Harald Meland (hmeland) wrote : Re: [Bug 172601] Re: Dual-head fails with ati driver, appears related to 'crtc'

On 10/12/2007, Tormod Volden <email address hidden> wrote:
> Anthony, from Harald's comment it sounds like it might would help for
> you to specify: Virtual 2560 1024

I'd guess that might cause the "nonsense" on LVDS to go away, but
that's not the real issue I'm hoping to have fixed -- do we have a
disconnect on what we consider to be the bug here?

To me, the real issue is that I can't make CRTC 0 drive monitors with
as high a resolution as CRTC 1 can (even though I could do this using
the same hardware under Feisty, so it's not a hardware problem). The
way I'm interpreting Anthony's original bug report, he also considers
the "trying to use CRTC 0 to drive monitor X on its maximum
(preferred) resolution just makes it go black" problem to be the main
issue; the fact that he sees some nonsense on LVDS while trying to set
up VGA-0 *and* DVI-0 with their preferred resolutions might be a clue
to where the problem originates, but isn't the real problem that he
wants fixed.

Anthony, am I interpreting you correctly? If not, should I create a
separate bug report for what I consider to be the main issue?
--
Harald

Revision history for this message
Anthony Brock (anthony-brock) wrote :

Harald,

I suspect that we are discussing related, but not identical issues. You're able to make CRTC 0 monitors work at the same time as a CRTC 1 monitor (which I am NOT able to accomplish). While you're situation does not allow maximum resolution, mines doesn't allow ANY resolution.

The "nonsense" on LVDS-0 is, in my view, simply the way that monitor choses to display the signal it is receiving. The Dell FP1905 monitors chose to display it with the "... Cannot Display This Video Mode" message. So, in my view, the LVDS and VGA-0 display issues are the same in my case. Your issue is likely related, but not as severe (since you're able to see something displayed with a low-enough resolution).

Does that make sense?

Tony

Revision history for this message
Harald Meland (hmeland) wrote :

On 11/12/2007, Anthony Brock <email address hidden> wrote:
> Harald,
>
> I suspect that we are discussing related, but not identical issues.
> You're able to make CRTC 0 monitors work at the same time as a CRTC 1
> monitor (which I am NOT able to accomplish). While you're situation does
> not allow maximum resolution, mines doesn't allow ANY resolution.
>
> The "nonsense" on LVDS-0 is, in my view, simply the way that monitor
> choses to display the signal it is receiving. The Dell FP1905 monitors
> chose to display it with the "... Cannot Display This Video Mode"
> message. So, in my view, the LVDS and VGA-0 display issues are the same
> in my case. Your issue is likely related, but not as severe (since
> you're able to see something displayed with a low-enough resolution).
>
> Does that make sense?

To me it does; I think the issues sound likely to be at least very
closely related, so for now I'll hold off on filing my issue as a
separate bug. Tormod, please let me know if you think otherwise.

I should also mention that as my LVDS has a max resolution of
1400x1050 (i.e. lower than the max resolution of the external
monitors), I'm doing "xrandr --output LVDS --off" whenever I switch[1]
to using the external monitors -- so that might be why I'm not seeing
any "nonsense".

[1] By using the attached shell script.
--
Harald

Revision history for this message
Harald Meland (hmeland) wrote :

It appears that my email attachment didn't make it through, attaching shell script via LP web UI.

Revision history for this message
In , agd5f (agd5f) wrote :

*** Bug 13590 has been marked as a duplicate of this bug. ***

Revision history for this message
In , agd5f (agd5f) wrote :

*** Bug 13533 has been marked as a duplicate of this bug. ***

Revision history for this message
In , agd5f (agd5f) wrote :

should be fixed with commit: f3d2ec3a5ae61215c792018320158750e7aa937c

Revision history for this message
In , Orion-cora (orion-cora) wrote :

Works for me. Thanks!

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Alex from upstream made some changes yesterday, which are in my PPA now. I don't know if the are related, anyway I think he will appreciate a log from using the latest version.

Revision history for this message
Anthony Brock (anthony-brock) wrote :

I'm sorry, but I'm not familiar with the acronym PPA or where to download non-production code. Where would I find this version to apply it?

Revision history for this message
Anthony Brock (anthony-brock) wrote :

Andy said in http://bugs.freedesktop.org/show_bug.cgi?id=12913 that this should be fixed with commit: f3d2ec3a5ae61215c792018320158750e7aa937c

Please let me know when a "PPA" is available with this commit that I can test (and where to download it from). Thanks!

Tony

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Anthony, it was the link in Harald's first comment, but it was not so obvious. In general, watch https://wiki.ubuntu.com/XorgOnTheEdge for pre-releases. I have just made builds with f3d2ec3a5ae61215c792018320158750e7aa937c, but unfortunately they break something on my X700 card, so I am a little reluctant to upload it. I have told Alex and he's working on it.

Revision history for this message
Anthony Brock (anthony-brock) wrote :

I found the PPA site a few hours ago. However, I can appreciate your reluctance to upload a buggy version!

Keep me posted on how things proceed. I would LOVE to have this working again with a dual-head configuration.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I'll temporarily just attach the "buggy" version here. Doesn't work well for me, but might well work for you :)

Revision history for this message
Harald Meland (hmeland) wrote : Re: [Bug 172601] Re: Dual-head fails with ati driver, appears related to 'crtc'

On 12/12/2007, Tormod Volden <email address hidden> wrote:
> I'll temporarily just attach the "buggy" version here. Doesn't work well
> for me, but might well work for you :)

This does indeed work just fine for me. Thanks!
--
Harald

Revision history for this message
Anthony Brock (anthony-brock) wrote :

This appears to resolve the dual-head issue. Both screens are functional!

Should I pursue the "ignore" option with LVDS? It isn't critical as the login screen automatically appears on my external monitor, but it is worth noting that the issue still exists with this version of code.

Another oddity is that the LVDS screen does not display properly when booted in the docking station. It continues to display nonsense, but the external monitors work correctly. In fact, the "xrandr -q" shows "LVDS disconnected", but with a resolution! However, the LVDS stops displaying the color pattern when I issue an "xrandr --output LVDS --auto" and continues to say "LVDS disconnected".

Wait, things changed once I opened the LVDS display (it was closed at boot). Now I am able to initialize it, but it still shows a color pattern with the "xrandr --output LVDS --auto" command and "xrandr -q" shows "LVDS connected (normal left inverted right)". While closed, xrandr insisted that it was "disconnected" (which now makes sense).

Fortunately, the LVDS does work correctly when the laptop is booted outside the docking station, so these are not critical issue for me since I don't use the LVDS when docked. Let me know if you want to pursue them further.

Looking great! Thanks!

Tony

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Anthony, if you want you can file a new bug for the docking station issue. But if it's very hardware-specific, it's not sure it gets much attention.

Changed in xserver-xorg-video-ati:
status: Confirmed → Fix Committed
Changed in xorg-server:
status: Unknown → Fix Released
Revision history for this message
In , Chi-Thanh Christopher Nguyen (chithanh) wrote :

After commit f3d2ec3a5ae61215c792018320158750e7aa937c, the display in my laptop's internal panel is heavily distorted.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Anthony, about the docking station, I just saw an upstream bug: http://bugs.freedesktop.org/show_bug.cgi?id=12546
Please check if that is similar to your issue.

Revision history for this message
In , Anthony Brock (anthony-brock) wrote :

This also resolved my issue. Dual-head is working fine now!

Revision history for this message
Tormod Volden (tormodvolden) wrote :

xserver-xorg-video-ati 1:6.7.197-1 is now in Hardy and should include the fix for this bug. Please update if you are running Hardy. This version will also be included in Hardy Alpha 3, which is scheduled for release next week. If you want to test this version (or newer) in Gutsy, try the test packages from https://wiki.ubuntu.com/XorgOnTheEdge

If you find that this bug is not fixed with the new version in Hardy, please reopen the bug report.

Changed in xserver-xorg-video-ati:
status: Fix Committed → Fix Released
Revision history for this message
In , Glisse (glisse) wrote :

Seems fixed, closing the bug, reopen (and update buginfo) if you still have issue with lastest xf86-video-ati.

Changed in xorg-server:
importance: Unknown → Medium
Changed in xorg-server:
importance: Medium → Unknown
Changed in xorg-server:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.