Created attachment 15335 [details]
xorg.conf

"no longer working" means what?

I did have a similar sounding problem, in that if I made a big virtual screen I could then get the external monitor to switch to its native resolution via xrandr, but not by default.  For me, using RROutputOrder to declare the second, larger monitor to be the primary one got things to set up automatically.  I then also no longer needed the Virtual declaration either.

        Option      "monitor-DVI-D_1"  "DoubleSightDVI"
        Option      "monitor-PANEL" "ThinkpadLCD"
# This fixes the problem of DVI-D_1 coming up in PANEL's resolution
        Option      "RROutputOrder"           "DVI-D_1"

No longer working means that it worked before I reinstalled the whole OS, with the same xorg.conf.
That was also using a earlier revision of the driver, but I unfortunately don't know which revision that was.

Since you updated the entire system I would assume a change in behavior elsewhere.
The randr code in the server is still under development and it behavior may change from time to time.

(In reply to comment #3)
> That was also using a earlier revision of the driver, but I unfortunately don't
> know which revision that was.

You should at least be able to verify the behavior of a driver that was released the last time it did work for you. When you have that you can git-bisect this and point us to the bad commit.

Sebastian, do you know approximately when you got the previous version of the driver?
If you do you can get one that predates this and retest. If the problem is gone (using your current version of X) it points to a problem in the driver. Then we should use git-bisect to locate it.
If you need help doing so we can assist you.
Reassigning to reporter for feedback. (Sebastian, please assign back to the default assignee once you have commented, thanks).

I just checked several older revision, all the way to November, which definately worked with my old OS installation, but those don't work with my current installation.
Is there any other information I can provide to help fix this bug?

Ok, weird.
When I remove these Screen and ServerLayout sections from xorg.conf,
it works correctly. Is that supposed to be that way?

Section "Screen"
       Identifier      "Default Screen"
       Monitor         "Asus"
        SubSection "Display"
                Depth     24
        EndSubSection
EndSection

Section "ServerLayout"
       Identifier      "Default Layout"
       Screen          "Default Screen"
       Inputdevice     "Generic Keyboard"
       Inputdevice     "Configured Mouse"
EndSection

(In reply to comment #8)
> Ok, weird.
> When I remove these Screen and ServerLayout sections from xorg.conf,
> it works correctly. Is that supposed to be that way?

Err - yes, and no.

You have a monitor referenced, that shouldn't be used any more:

> Section "Screen"
>        Identifier      "Default Screen"
>        Monitor         "Asus"
[...]

This ought to be ignored by our driver (it tells RandR so), but apparently behavior there has changed lately. You are on the safe side, if you never specify a monitor the old way when using any(!) RandR 1.2 capable driver with the current Xserver version.

This is also tracked in

  https://bugzilla.novell.com/show_bug.cgi?id=370656

Stefan Dirsch:

Nearly the same problem with nv driver on G80. As long as 

  Monitor "M1"

in Section Screen is not removed/commented out, the monitors cannot be
positioned side by side with the error message similar to this:

(EE) Monitor(1) cannot be positioned right of Monitor[0] without a mode
     specified.

Specifying modes explicitetly for both monitor doesn't help at all. Only
the workaround mentioned above does.

Sorry, wrong bug :-]

Marking as duplicate now, because the root has been identified as a known issue.

*** This bug has been marked as a duplicate of bug 15352 ***