PS/2 Optical Mouse Trouble
 

Hi there,

I have installed Linux Suse 10.0 and i am using a PS/2 Im Micro Innovations optical mouse which does respone but behaves erratcally...currently i am using a Generic PS/2 wheel mouse which works perfectly fine....i just would rather have the optical mouse working..

I have tryed some thing from some forum posts i.e. messing with Xorg.conf Section "InputDevice"
i tryed Auto and also tryed IMPs protocal unfortunatlly this still does not work if anyone has any idea to how i can solve this problem would be greatly apprecated

Thank you
P.S. ( Attual Xorg.conf )

Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Buttons" "5"
Option "Device" "/dev/input/mice"
Option "Name" "ImPS/2 Generic Wheel Mouse"
Option "Protocol" "Auto" ( Tryed Auto Obvouslly and ImPS/2 )
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
EndSection

Fuck it....bunch of ignorant bastards i apprecate the help and will seek it elsewhere
...........................................................
Sorry about above...bad day!!!

Its sad you have chosen to insult everyone here. Patience is a virtue because people who can help you could be busy or live in different timezones so not see your post for ages.

What exactly is not working when you configure your optical mouse as a generic mouse.

i apologize for that insult there just was frustrated.....i just really want to get everything working under linux so i can ditch windows forever.

Anyways it is the optical mouse itself that does not work like it should do i am guessing its the same problem that the majority of people have with the optical mouse all i am looking for is instructions on how to get it functioning as it show in my first post i have given as much details as i know if you need any more information please let me know exaclty what you would like to know and i will be more than happy to supply this information

once again sorry about the rage problem

peace

I've used 4 different vender's optical mice and have never seen problems like you're experiencing. I suggest you try this mouse on another system. I may be mistaken but, it appears to me that there is no perceivable difference from an interface perspective. The benefit of the optical mouse are realized within the mouse. I've seen lots of erratic mechanical mice and was for ever cleaning them out.

@ fragos

i would be happy to post several links from this forum which contain similar if not exacly the same problems....but anyways this mouse does work flawlessly under windows and is fairly new.

What is the correct protocal an optical mouse uses...the answer to this question may solve my problem....i hope

thanks and peace out

I usually use IMPS/2 or ExplorerPS/2 depending on the mouse or number of buttons. I usually select generic wheel mouse or intellimouse and never have any problems.

@ Reddazz Thanks i have already tryed IMPS/2 and unfortualy did not help me i will try the ExplorerPS/2 and post my finding....finger crossed

peace

............
Ok qucik update on that explorerPS/2 protocal...i tryed it and it some how cause kde to crash upon loading....anyways i just re edited my xorg.conf back and and then "startx" and it loaded thankfully...don't scare my like that again man :P...lol...j/k

2 years later and still no joy
 

I have also now been googling and posting for two full days and I still cannot use my wheel. No replies. Suggestions that include "imwheel" that the SuSE config program has never heard of. I guess it is supposed to be working now. I first used a wheel mouse almost 20 years ago. The system mouse configurator does recognize the wheel correctly. It would just be more useful if it would pass along that information to the applications.

I suggest you try the following in xorg.conf.

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Thank you for the suggestion, but that's not it. The solution is....

Once upon a time, long ago, the scroll wheel was assigned buttons 4 and 5 for the scrolling motion. Applications came to know and expect that. Then someone improved the mouse with side to side motion. Those became 4 and 5 and the scrolling action went to 6 and 7. That caused consternation for a time, but that got fixed by configuring "xmodmap" to map buttons 4 and 5 to 6 and 7, and vice versa. All was well again. Between SuSE 10.3 and 11.0, I think somebody "fixed" the driver so the scroll wheel now shows up as buttons 4 and 5 once again. That is really well and good for those folks new to SuSE 11 (Linux 2.6.whatever), but not so good for those of us with pre-existing configurations that had the remapping, and were also expecting that remapping to be correct.

The correct content for my .Xmodmap file is now:
pointer = 1 8 3 4 5 6 7 2 9

and I only need it because it is too hard to click the middle button without also scrolling the scroll wheel. (The first thumb button becomes my "paste" button.)