[RV280 9200] ati driver with xrandr borked in intrepid and jaunty

I have the same problem. Also around every second time i tried to activate dual head, X freezed ...

a solution is importand for me, cause this is a production mashine ...

Ok. I think I have a solution. First of all, the radon driver would not load because the radeon module was not loaded. So running modprobe radeon and echo radeon >> /etc/modules fixed that.

Secondly it looks like the ouput of lspci changed in intrepid. I used to see each output as a seperate video device. -1:00.0 and 01:00.1. So my xorg.conf used to have two different devices. Now I only see one device in lspci, so my new xorg.conf has one device but two monitors. This setup appears to be working. However, if I ever run a graphical display manager (such as the one in kubuntu) it immediately screws up the displays by putting them into clone mode, and requires a reset to fix it. See the screenshot of display properties.

Yes ... you are right. with your configuration it rudimentarily works ! thx a lot !

i also could confirm that the kubuntu display manager screws it up again ...

Based on the description of the symptoms, it sort of sounds like this might be caused by an incorrect AGPMode setting, which is relevant when DRI is enabled. You should test if changing this makes the issue go away. In your /etc/X11/xorg.conf set AGPMode to various values like this:

 Section "Device"
      ...
      Option "AGPMode" "2"
 EndSection

Possible values include 1, 2, 4, 8. You can see what it's currently set to by looking in /var/log/Xorg.0.log. It's worthwhile to test all four values even once you find one that works. If this takes care of it for you, we may be able to establish a quirk to set it for your hardware combo

For more details on this, please see the "ATI AGP Mode Quirk" section at https://wiki.ubuntu.com/X/Quirks

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

I replied in another bug that I can't seem to be able to find right now. Anyway, the comment about trying agpmode was copied into both bug reports. I asked if it was still applicable if my video card is pci, I was told no. I can still try it if you think it would help.

I've upgraded my ubuntu install to jaunty and still experience ati driver weirdness. Furthermore, simply running the ubuntu made display manager hoses my monitor setup.

[This is an automatic notification.]

A new version of the -ati driver is now available in Karmic.

This is a significant update to -ati which brings in kernel mode-setting
(currently disabled) and scores of fixes for DRI2, EXA, etc.

I've posted the new version of this driver to the following PPA,
would you mind testing it and seeing if it resolves the bug you
reported?

  https://edge.launchpad.net/~bryceharrington/+archive/ppa/+sourcepub/709908/+listing-archive-extra

If you're not running this release of Ubuntu, you can try booting the Karmic
LiveCD and loading the PPA onto it, and then log out/in to restart X.
ISOs are available at http://cdimages.ubuntu.com/releases/

After testing Karmic, report back here whether it's still an issue or not,
and if it is please post a fresh Xorg.0.log and 'dmesg' output.

Note there could be new bugs... please file these as new reports using
the command 'ubuntu-bug xorg'.

So is there an intrepid or jaunty workaround?
I have an RV280 [Radeon 9200 PRO] dual head running with intrepid and am seeing this problem.
My setup works in the gdm login screen (one screen is blank, the other has the gdm login, mouse pans across the monitors) but once gnume starts, both monitors display the same contents.

We're closing this bug since it is has been some time with no response from xian. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.