Bug 381745

Summary: radeon/Xinerama: touchpad can't move mouse pointer to second screen
Product: [openSUSE] openSUSE 11.0 Reporter: Christian Boltz <suse-beta>
Component: X.OrgAssignee: Matthias Hopf <mhopf>
Status: RESOLVED WONTFIX QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Normal    
Priority: P5 - None CC: sndirsch
Version: Beta 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: xorg.conf
Xorg.0.log
some SaX logfiles

Description Christian Boltz 2008-04-20 19:12:33 UTC
Created attachment 209173 [details]
xorg.conf

After updating to 11.0 beta1, I have a very interesting problem on my laptop. You probably remember my setup: radeon driver, laptop + external TFT in Xinerama setup.

The problem: When I use the Synaptics touchpad, I can use the mouse pointer around on the laptop display, but _not_ to the second screen.

Fortately, my USB mouse can move the mouse pointer to the second screen.

Even more interesting: When the pointer is on the second screen, it can be moved there with the touchpad. But as soon as I move it back to the laptop display, it is "imprisoned" there again.

I'll attach xorg.conf and Xorg.0.log.
If you need more information or want me to test something, just ask.
Comment 1 Christian Boltz 2008-04-20 19:13:20 UTC
Created attachment 209174 [details]
Xorg.0.log
Comment 2 Stefan Dirsch 2008-04-21 09:06:41 UTC
So the USB mouse is your monitor switcher. ;-)
Comment 3 Stefan Dirsch 2008-04-21 09:11:03 UTC
I noticed that you're using a Xinerama configuration. Maybe it works with a MergedFB configuration (AFAIK the default since a long time now)

  sax2 -r -b /usr/share/sax/profile/Radeon_DualHead_DriverOptions

or using the new RANDR 1.2 capable driver "radeonrandr12"

  sax2 -r -m 0=radeonrandr12

For the latter you need the keyword Virtual for a multihead setup as long as 
you don't configure it in a static way.
Comment 4 Christian Boltz 2008-04-21 17:04:25 UTC
Created attachment 209398 [details]
some SaX logfiles

This tarball contains several logs from the things I tried. For two of them the console output is also included.

a) sax2 -r -b /usr/share/sax/profile/Radeon_DualHead_DriverOptions
   Files: DualHead-profile-*
   - doesn't save the config to /etc/X11/xorg.conf

b) sax2 -r -m 0=radeonrandr12
   Files: radeonrandr-*
   - also doesn't save the config to /etc/X11/xorg.conf
   - the "Dualhead" and "3D" options in SaX2 are not available (greyed out)
   - console framebuffer is totally broken (black, backlight on) after SaX 
     exits, I had to reboot. Therefore tty not captured.

c) sax2 -r
   Files: sax2_-r*
   - also doesn't save the config to /etc/X11/xorg.conf

Note: I always tested with the external screen disconnected - otherwise the laptop display was switched off at SaX startup. This makes the config proposal nearly unusable because I can't select a 1400x1050 screen.#
If the external screen is disconnected, I can setup the second screen with 1280x1024 without problems.

The most important problem for now seems to be that the xorg.conf file is never written.
Comment 5 Stefan Dirsch 2008-04-21 17:43:59 UTC
Oh no. So we first need to fix a SaX2 bug before I can investigate this issue. :-( 

Marcus, please have a look at this and reassign back once the "sax2 doesn't save the config" issue has been addressed?
Comment 6 Stefan Dirsch 2008-04-21 17:55:11 UTC
See also Bug #382036.
Comment 7 Stefan Dirsch 2008-04-21 21:03:52 UTC
I think the dependancy should be resolved once Bug #382036 has been resolved.
Comment 8 Stefan Dirsch 2008-04-21 21:28:52 UTC
Could you try it without the "-r" option? When running it on the console the option should not be required anyway.
Comment 9 Christian Boltz 2008-04-22 19:34:51 UTC
SaX2 also doesn't create an xorg.conf when running without parameters (tested after init 3 and rm /etc/X11/xorg.conf, called sax2 multiple times). I'm afraid this bug will have to wait until bug 382036 is fixed :-(

If you have an idea what I {c,sh}ould manually change in my xorg.conf, I can test this in the meantime.
Comment 10 Stefan Dirsch 2008-04-22 19:53:05 UTC
Sorry, no time for explaining this. Otherwise this would become a 3digit comment bug rather soon.
Comment 11 Stefan Dirsch 2008-04-23 08:43:10 UTC
(In reply to comment #3 from Stefan Dirsch)
> I noticed that you're using a Xinerama configuration. Maybe it works with a
> MergedFB configuration (AFAIK the default since a long time now)
> 
>   sax2 -r -b /usr/share/sax/profile/Radeon_DualHead_DriverOptions

This is the default, when you enable Dualhead Mode in SaX2.
Comment 12 Stefan Dirsch 2008-05-06 16:53:18 UTC
I don't think it makes sense to wait until the SaX2 bug is fixed. Reassigning to Matthias instead. Hopefully he has better ideas to investigate this issue.
Comment 15 Stefan Dirsch 2008-06-02 17:23:24 UTC
I've tried to reproduce this issue with openSUSE 11.0 RC1 on a laptop with 

  "Radeon Mobility X600 (M24) 3150 (PCIE)" (1002:3150)

1) radeon/Xinerama --> Xserver crashes (No, I won't debug this. We no longer
   support this setup since some years now.)
2) radeon/MergedFB --> works
3) radeonrandr12/xrandr --> works

==> WONTFIX

Please switch to radeon/MergedFB or give the radeonrandr12 driver a try. It seems sax2 has been fixed meanwhile.
Comment 16 Christian Boltz 2008-06-02 20:24:43 UTC
Just FYI:

(In reply to comment #15 from Stefan Dirsch)
> 1) radeon/Xinerama --> Xserver crashes (No, I won't debug this. We no longer
>    support this setup since some years now.)

OK, understandable - however this config still works on my laptop (11.0 beta3plus) except the imprisoned mouse pointer.

> 2) radeon/MergedFB --> works

From the synaptics point of view: yes - but bug 306691 reappears...

> 3) radeonrandr12/xrandr --> works

I haven't tested this driver yet.

> Please switch to radeon/MergedFB or give the radeonrandr12 driver a try.

I'll try the radeonrandr12 driver. In case it doesn't fix the scrollable screen, you'll see a new bugreport ;-)

BTW: Would using the ATI binary driver be an option?
To make it more difficult: My graphics card is only supported by the old binary driver, which means I would need the patch to fake the X.org version (which was in the buildservice packages a year ago) and of course some luck regarding compatibility with the latest X.org version... (yes, I know that this would be completely unsupported.)

> It seems sax2 has been fixed meanwhile.

Yes, it creates a working config file for 2) by default.
Comment 17 Stefan Dirsch 2008-06-02 20:48:18 UTC
Forget about the fglrx driver. R200 chips are no longer supported by current drivers. And for current X.Org versions (openSUSE >= 10.2) you need a current driver ...