Nvidia 19.29-22.1 suse 11.3 dual monitor mouse flickers when moved to 2nd monitor

English Hardware
1

Hello all,

just setup suse 11.3 , put on the Nvidia 19.29-22.1 drivers via yast , no kms is set in inetd , nomodeset on grub boot line etc…

Even tried installing the driver " the hard way "

dual monitors come up, setup xinerama to “Extend” my desktop , and the main monitor ( right side ) is good, visually the left monitor (2ndary) is good… but whenever I move my mouse over to the left screen the mouse pointer dissapears, flickers along the right hand border of that screen…
and if i move the cursor back to the original screen i have to really fight to get it back to the main screen…

any suggestions???

Copy of my xorg.conf , still very basic…

nvidia-settings: X configuration file generated by nvidia-settings

nvidia-settings: version 260.19.29 (buildmeister@swio-display-x86-rhel47-04.

nvidia.com) Wed Dec 8 12:27:27 PST 2010

Section “ServerLayout”

Removed Option “Xinerama” “0”

Identifier     "Layout0"
Screen      0  "Screen0" RightOf "Screen1"
Screen      1  "Screen1" 0 0
InputDevice    "Keyboard0" "CoreKeyboard"
InputDevice    "Mouse0" "CorePointer"
Option         "Xinerama" "1"

EndSection

Section “Files”
EndSection

Section “InputDevice”

# generated from default
Identifier     "Mouse0"
Driver         "mouse"
Option         "Protocol" "auto"
Option         "Device" "/dev/psaux"
Option         "Emulate3Buttons" "no"
Option         "ZAxisMapping" "4 5"

EndSection

Section “InputDevice”

# generated from default
Identifier     "Keyboard0"
Driver         "kbd"

EndSection

Section “Monitor”
Identifier “Monitor0”
VendorName “Unknown”
ModelName “ViewSonic VX2235wm-3”
HorizSync 30.0 - 82.0
VertRefresh 50.0 - 75.0
Option “DPMS”
EndSection

Section “Monitor”
Identifier “Monitor1”
VendorName “Unknown”
ModelName “AOC 2330V”
HorizSync 24.0 - 80.0
VertRefresh 56.0 - 75.0
EndSection

Section “Device”
Identifier “Device0”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “GeForce GTX 260”
BusID “PCI:3:0:0”
Screen 0
EndSection

Section “Device”
Identifier “Device1”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “GeForce GTX 260”
BusID “PCI:3:0:0”
Screen 1
EndSection

Section “Screen”
Identifier “Screen0”
Device “Device0”
Monitor “Monitor0”
DefaultDepth 24
Option “TwinView” “0”
Option “metamodes” “DFP: nvidia-auto-select +0+0”
SubSection “Display”
Depth 24
EndSubSection
EndSection

Section “Screen”
Identifier “Screen1”
Device “Device1”
Monitor “Monitor1”
DefaultDepth 24
Option “TwinView” “0”
Option “TwinViewXineramaInfoOrder” “CRT-0”
Option “metamodes” “CRT: nvidia-auto-select +0+0”
SubSection “Display”
Depth 24
EndSubSection
EndSection

2

Try to install the repository

# zypper addrepo <url of your graphics' card driver>
3

So, if you are installing the nVIDIA proprietary graphics driver, I would read through the following document.

SDB:Configuring graphics cards - openSUSE

I can say that I always add the nomodeset kernel load option in my grub /boot/grub/menu.lst file and I set the YaST / System /etc/sysconfig Editor kernel option NO_KMS_IN_INITD=yes from no and saved that setting. I always load my nVIDIA driver the hard way. I have a script file you can use for this purpose here:

LNVHW - Load NVIDIA (driver the) Hard Way from runlevel 3

Message #12 has the most recent script version for LNVHW. I must ask, why you would not follow all of the suggestions first and leave it that way, for nomodeset, NO_KMS_IN_INITD and to load the nVIDIA driver the hard way and then ask for help if it still works as you say? I would uninstall any YaST nVIDIA drivers as you only need to load one driver. I always do what I have suggested to you and all works just fine. I am using the 64 bit version of openSUSE which seems to work best under KDE. I have removed the xorg.conf file which is not required when using openSUSE 11.3.

Thank You,

4

exactly the same problem with 4 screens. I did not have this problem in opensuse 11.2

Please help. It looks like a bug.

5

exactly the same problem with 4 screens. I did not have this problem in opensuse 11.2

Please help. It looks like a bug.
mr_lukes, you will need to tell us more about your video hardware. Let me say that using two monitors with Intel Video on my work Laptop, after trying openSUSE 11.3, I opted to drop back to openSUSE 11.2. Its still supported and you can get most everything you need in the older version. With nVIDIA graphic cards, using two monitors with openSUSE 11.3 and using DVI connections, everything has worked OK for me. So, I have not tried three or four monitors and nVIDIA combined with DVI connections works with openSUSE 11.3. If you want to use openSUSE 11.3 with four monitors, your options are limited in my opinion, even if its a bug with Intel. For the most part, fixing it all means moving to openSUSE 11.4 in a month, but then you must deal with KDE 4.6.

Thank You,

6

Hi,

I have two Nvidia GT9800 cards connected with SLI on Opensuse 11.3 and Gnome.

the problem is only with 4 screens. If I enable only two screens on one card everything is fine, but if I enable another two, and i move the mouse on the other screen that is connected to separate card, than the cursor start jumping between screens and nothing you can do. you cannot even restart X Server. What I found out, is when you press a few time “Tab” then the xserver goes down with some message and you can see command line prompt.

if you need anything else, please tell me what and I can post it. I will also look into logs, maybe some errors will make everything more clear.

7

So, basically, this is an SLI issue as opposed to the normal video issue then. Of course, there is a newer nVIDIA driver out now at 260.19.36 which you could try, but I have not used SLI before. That does leave the option to drop back to openSUSE 11.2 which I still use on one PC. I know that it seems crazy to go backwards, but really, you can get it all right now with 11.2 OR wait for the final to come out with openSUSE 11.4 and give it a try. When openSUSE went to 11.3, sax2 was removed and the kernel changed from 2.6.31 to 2.6.34, a big change in video support. Those video cards will not do any better than the support you had in openSUSE 11.2 I believe and somehow I think the drop back to openSUSE 11.2 would be the thing to do.

Thank You,

8

Well, I agree… actually I am using still 11.2 and I just wanted to uprate to 11.3 because I bought SSD drive, so I thought that brand new installation is a good idea.
I am pretty sure that I am using the lates Nvidia drivers, but i will give a try to new Nvidia beta drivers (270.18 BETA). also i can try using two video cards without SLI. I will put some updates to the topic tomorrow.

9

Well, I agree… actually I am using still 11.2 and I just wanted to uprate to 11.3 because I bought SSD drive, so I thought that brand new installation is a good idea.
I am pretty sure that I am using the lates Nvidia drivers, but i will give a try to new Nvidia beta drivers (270.18 BETA). also i can try using two video cards without SLI. I will put some updates to the topic tomorrow.
Also, if having a newer kernel would help with those new SSD drives, you can install any kernel version you like using SAKC. Here is a link to this script file:

S.A.K.C. - SUSE Automated Kernel Compiler - Version 2.00

Message #17 has the most recent version of this script file.

Thank You,

10

So, I have tried everything… new beta drivers, no SLI, SLI and nothing… still the same problem. Everything looks normal, I can move the mouse accross two screen that are connected to one card, but when I move the cursor to another screen that is connected to the second card, the mouse cursor starts jumping between screens and everything is frozen.

When I press a few times “Tab” the Xserver restarts and outputs some errors, like Segmentation fault, etc.

This is gdm log that shows some errors:

Xlib:  extension "RANDR" missing on display ":0.0".
Xlib:  extension "RANDR" missing on display ":0.0".
gdm-simple-greeter[3010]: Gtk-WARNING: gtkwidget.c:5628: widget not within a GtkWindow
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c0003a (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c0003a (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
gdm-simple-greeter[3010]: WARNING: Unable to parse history: (null)   4

gdm-simple-greeter[3010]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width 496 and height -1
gdm-simple-greeter[3010]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width 496 and height -1
Failed to play sound: File or data not found
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
gdm-simple-greeter[3010]: WARNING: Failed to send buffer

** (gnome-power-manager:3008): WARNING **: Failed to send buffer
Window manager warning: Log level 16: Failed to send buffer

(gnome-power-manager:3008): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-power-manager:3008): atk-bridge-WARNING **: IOR not set.

(gnome-power-manager:3008): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-power-manager:3008): atk-bridge-WARNING **: IOR not set.
Window manager warning: Log level 16: Failed to send buffer

(gnome-settings-daemon:2989): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2989): atk-bridge-WARNING **: IOR not set.
gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gnome-settings-daemon: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
The application 'polkit-gnome-authentication-agent-1' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.

Also, I believe SSD works perfectly, it is very fast. I worked with it for an hour or so (off course with only two screens) and no problems at all :wink: With 6GB of RAM, i7 and super fast SSD - opensuse rules :wink:

11

I’m not going to be able to offer any help, but

I moved to 11.3 (kde) early on and had a similar problem. 3 screens; 2 Nvidia GTS250’s, non SLI. When I configure the 3rd screen to be left of the other 2 and moved the cursor onto the 3rd screen I got the unmanageable jumping cursor issue. When the 3rd screen was configured to the right of the other 2 I didn’t get the issue. Shortly after I rearranged the furniture and went back to 2 screens 1 card so the issue went away.

So, no help, but a bit of empathy.

12

I had the same problem with a Thinkpad laptop with NVidia.
Using nvidia-settings the mouse always flickered in the external monitor, when Xinerama was set on.Turning off Xinerama and setting up the other monitor as separate X, I managed to get the mouse over there without flickering, but I couldn’t get any useful desktop action, just a mouse pointer.

I finally changed the device driver to “nouveau” by adding to /etc/X11/xorg.conf.d/50-device.conf:

Driver “nouveau”

Now I have to login to KDE4 and open Personal Settings/Display and setup the relative position of the external monitor every time, but then everything works like a charm.