I might be able to help a little
I have used both Kensington and MS optical USB mice in several distros.
Here's the relevant portion of my XF86Config:
CODE - CODE - CODE - CODE - CODE - CODE - CODE - CODE - CODE
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse[1]"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/input/mice"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"
EndSection
END CODE - END CODE - END CODE - END CODE - END CODE SE
Notice the "Buttons" and "ZAxisMapping" items. Now when X starts, my wheel doesn't work right, and my 4th and 5th buttons still don't do anything, so I run the following in a script everytime KDE starts:
xmodmap -e "pointer = 1 2 3 6 7 4 5"
This fixes the mapping of the mouse keys so everything works as expected.
Now, your mouse might be different or have more/less buttons than mine, so, in X open a terminal and run "xev"
place your cursor in the little window that appears and without moving your mouse at all, click each button in turn, including wheelup, wheeldown and wheel click. In the terminal, for each click, you will see how X sees each button on your mouse, as simply "buttonx", where x is one through whatever. If your have more than 7 buttons, including wheelup and wheeldown, edit your XF86Config accordingly. Don't forget the pressing the scrollwheel down counts as one button. Once you know how X sees each button, you can play with the mapping until it works right. If X doesn't see all your buttons, I don't have a clue what to do. Try a different protocol, maybe?
I hope this helps.
Last edited by urinal cake; 12-28-2002 at 03:15 AM.
|