PDA

View Full Version : Installed new driver -- mouse not working


jkruer01
04-08-03, 09:37 PM
Hello,

I successfully installed the newest nvidia gforce driver for Suse 8.1 and everything works fine except for my mouse now doesn't work properly.

Whenever I move my mouse it "clicks" at the same time. In other words, the signle for left clicking gets sent to the computer everytime I move the mouse. As you can imagine, this causes a lot of problems. Does anyone know how to correct this. I don't know if it is a result of something I screwed up while installing the drivers or if it is a result of the driver. Any advice would be appreciated.

Thanks!

bwkaz
04-09-03, 07:38 AM
It shouldn't be the video driver... of course, that doesn't mean that it definitely isn't, but in all likelihood it isn't.

What kind of mouse is it? What are you using for the Protocol option in your mouse section in XF86Config(-4)?

jkruer01
04-09-03, 09:56 AM
I didn't think it had anything to do with the video driver either but it happened right after I installed the new drivers. It is a Logitech USB mouse. I'll look in the XF86Config file and let you know what I have under Protocol.

kudrash
04-09-03, 11:04 AM
Originally posted by jkruer01
I didn't think it had anything to do with the video driver either but it happened right after I installed the new drivers. It is a Logitech USB mouse. I'll look in the XF86Config file and let you know what I have under Protocol.

i've got problem like this with logitech USB dual optical, but only in quake3...
tomorrow i've install fresh RedHat 9 on my dual pentium III linux box and install new NVIDIA driver for my GF3/64RAM - all work fine in X, but in quake3 i've got strange problem - q3 start in fullscreen fine but mouse not work (it's "click" only but no movements). when i try to run demo from console (/demo demoname.dm_68) quake3 hang with no errors and i fall back in X with q3 resolution (that's diff from default resolution). tuxracer run fine in fullscrenn with no problem.
in README file from NVIDIA i see this:

Q: Some OpenGL applications (like Quake3 Arena) crash when I start them on Red Hat Linux 9.0.

A: Some versions of the glibc package shipped by Red Hat that support TLS do not properly handle using dlopen() to access shared libraries which utilize some TLS models. This problem is exhibited, for example, when Quake3 Area dlopen()'s NVIDIA's libGL library. Please obtain at least glibc-2.3.2-11.9 which is available as an update from Red Hat.

i've got this new glibc (and i've got new kernel from redhat update: 2.4.20-9smp) - same result...
in logs (ANY) i don't see any error or warning...
Q3 work tomorrow with RedHat 7.3 and new NVIDIA drivers!!!

XF86Config:

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "microsoft"
Option "XkbLayout" "us,ru(winkeys)"
Option "XkbOptions" "grp:ctrl_shift_toggle,grp_led:scroll"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Mitsubishi Diamond Pro 900u (NFJ9905)"
DisplaySize 350 260
HorizSync 30,0 - 95,0
VertRefresh 50,0 - 152,0
Option "dpms"
EndSection

Section "Device"
# no known options
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA GeForce 3 (generic)"
BoardName "NVIDIA GeForce 3 (generic)"

Option "NvAGP" "1"
Option "NoLogo" "1"
Option "HWCursor" "1"
Option "CursorShadow" "1"
Option "UseEdidFreqs" "1"
Option "ConnectedMonitor" "CRT"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24

SubSection "Display"
Depth 8
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection

SubSection "Display"
Depth 16
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection

SubSection "Display"
Depth 24
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

mtrr
04-09-03, 11:30 AM
@kudrash:

what point release?

well known problem, get the latest one.

1.32b (IIRC)

kudrash
04-09-03, 11:49 AM
Originally posted by mtrr
@kudrash:

what point release?

well known problem, get the latest one.

1.32b (IIRC)

hmmm, i've got 1.32... where i can find 1.32b?

kudrash
04-09-03, 12:03 PM
Originally posted by mtrr
@kudrash:

what point release?

well known problem, get the latest one.

1.32b (IIRC)

10x!!! i find 1.32b!!!

kudrash
04-09-03, 01:22 PM
Originally posted by mtrr
@kudrash:

what point release?

well known problem, get the latest one.

1.32b (IIRC)

so... now i've got quake3 1.32b with osp 1.03a - mouse already work fine, but quake3 still hang with no error in log (i try quake3 and quake3-smp variants).
any comments?

kudrash
04-09-03, 01:27 PM
Originally posted by kudrash
so... now i've got quake3 1.32b with osp 1.03a - mouse already work fine, but quake3 still hang with no error in log (i try quake3 and quake3-smp variants).
any comments?

sorry, i'm wrong - ONLY quake3-smp hang!!!

jkruer01
04-09-03, 01:58 PM
Thank you for everyone's suggestions. I went to the Suse site and found an article that told me what to adjust in the XF86Config file and now everything is working great.