Bug 306691

There is no attachment :-)

Created attachment 161352 [details]
SaX.log

Now *really* attaching SaX.log ;-)

The attached configuration file is a single head configuration.
I don't see any dualhead related options like MergedFB,MonitorLayout,etc..

* It seems you did not configure dualhead, or the attached file
  doesn't reflect your latest change. More information is provided by
  the following workflow:
 
     init 3
     sax2
     ==> click on the dualhead checkbox
     ==> save the configuration
     ==> send the /var/log/SaX.log
     ==> send the /etc/X11/xorg.conf

* If you can see a dualhead enabled screen with the attached configuration
  file this setup has been done by the driver itself (by default or some
  driver magic which I can't influence)

Thanks

OK, I just tried again:
- rm /etc/X11/xorg.conf /var/log/SaX.log
- sax2 -r

first try: activate dualhead and 3D - results in dualhead being unchecked, but still both screens working in the test (and moving around when hitting the screen border)

second try (saved in this state): switched off 3D, switeched on dualhead (and verified that it's still on while saving)

Result: still both screens working, with the same problem as in the initial comment.

I'll attach the logfile and the generated xorg.conf.

Created attachment 162073 [details]
SaX.log, with dualhead checked for sure

Created attachment 162074 [details]
the generated xorg.conf

The generated configuration file looks good to me it includes
what you requested. I think the mentioned behavior is a driver "feature"
of the radeon driver.

- Stefan could you confirm that the radeon driver sets up virtual screen
  of the size of the biggest resolution which leads to a scrolling area for
  the smaller screens ?

- Could the use of the radeonrandr12 help Christian ?

Thanks

Yes, panning seems to be the default for the radeon MergedFB. radeonrandr12 would be worth a try for Christian, since panning is not supported (yet) by RANDR 1.2. But ... 

1) radeonrandr is an experimental driver (completely unsupported)
2) don't complain if apps are started in the (now) hidden area and you can't
   see them any longer

So I set this to later

[note: I have installed beta3 right now]

(In reply to comment #8 from Stefan Dirsch)
> Yes, panning seems to be the default for the radeon MergedFB. 

Indeed, it's even documented in man radeon:
(This doesn't make it better though.)

       Option "MergedNonRectangular" "boolean"
              If  you are using MergedFB with two modes of different sizes,
              turn this option on to keep the smaller head from scrolling
              within the larger virtual desktop [...]
              The default value is FALSE.

I have added 
    Option        "MergedNonRectangular"
in the radeon Device section.

Unfortunately MergedNonRectangular seems to be buggy - it removes only about 1/3 of the invisible section :-(  and the screen is still scrolling around...


> radeonrandr12 would be worth a try for Christian, since panning is not 
> supported (yet) by RANDR 1.2. But ... 
> 
> 1) radeonrandr is an experimental driver (completely unsupported)

I'd say _very_ experimental. I just tested it - clicking the test button in sax2 froze my laptop :-/  (Yes, really frozen. Not even SysRQ worked.)

> 2) don't complain if apps are started in the (now) hidden area and you can't
>    see them any longer

I never had this problem on 10.2 (with xinerama), so this is my smallest 
worry ;-)

if this option is not stable I'm not willing to integrate it. It's not
sax2's fault if the X-Server test crashed your system. From my experience
the "test" button always is a major pain in the ass because running multiple
X-Server instances gets more and more unstable

(In reply to comment #14 from Marcus Schaefer)
> if this option is not stable I'm not willing to integrate it. It's not
> sax2's fault if the X-Server test crashed your system.

Sorry for not making it clear - I reopened the bug because the MergedNonRectangular option doesn't work as expected. I'll reassign to Stefan because this is more an X issue and not related to SaX2...

@Stefan: see comment #13

I don't think this will still get fixed. Does it work with radeonold driver on RC1 to be released later this week?

Some negative test results:
- sax2 -r -m 0=radeonold  doesn't offer dualhead config
- replacing "radeon" with "radeonold" in the configfile generated with 10.3 
  doesn't help
- running sax2 from a tty with the external monitor attached hangs up my laptop
  (not even SysRQ works). No problems when the external monitor isn't present.
  Is this worth a separate bugreport? (If so: How do I get logs? I guess they 
  aren't synced to the harddisk fast enough...)
- and there's still the broken MergedNonRectangular (see comment #13) - another 
  bugreport?

Fortunately I found a working configuration:
- using the xorg.conf from 10.2 and replacing "radeon" with "radeonold" makes
  the desktop non-scrolling :-)

(In reply to comment #17 from Christian Boltz)
> Some negative test results:
> - sax2 -r -m 0=radeonold  doesn't offer dualhead config
Yes, the dualhead magic only works for drivers registered for the graphics card.

> - replacing "radeon" with "radeonold" in the configfile generated with 10.3 
>   doesn't help
ok.

> - running sax2 from a tty with the external monitor attached hangs up my
>   laptop (not even SysRQ works). No problems when the external monitor isn't
>   present.
>   Is this worth a separate bugreport? (If so: How do I get logs? I guess
>   they aren't synced to the harddisk fast enough...)
I don't think so.

> - and there's still the broken MergedNonRectangular (see comment #13) -
>   another bugreport?
No. See comment #16. The current radeon driver will get replaced by the 
RANDR 1.2 radeon driver currently in development for next openSUSE release.

> Fortunately I found a working configuration:
> - using the xorg.conf from 10.2 and replacing "radeon" with "radeonold"
>   makes the desktop non-scrolling :-)
Ok. Use this workaround for now.

Closing as WONTFIX.