LinuxQuestions.org - Logitech Mouseman Optical Duel Sensor does not work

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - Logitech Mouseman Optical Duel Sensor does not work (https://www.linuxquestions.org/questions/linux-hardware-18/logitech-mouseman-optical-duel-sensor-does-not-work-145269/)

Logitech Mouseman Optical Duel Sensor does not work

My mouse (Logitech Mouseman Optical Duel Sensor) does not seem to work at all after I load KDE.

Here are my settings from my XF86Config file for my mouse. I running Slackware 9.1.

Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "dev/mouse"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"

KDE seems to load fine. I just cannot use my mouse for anything. I have to navigate the desktop with the keyboard.

What port is your mouse connected to (USB or PS/2)? If it is connected to USB, make sure you have the correct kernel modules loaded (try "modprobe hid"). I think you might also have to set the "Protocol" to "usb" (so the line reads: Option "Protocol" "usb").

It is connected through the PS/2 port through an adapter than came with the mouse.

I've got the almost the same problem as you,
my mouse does work but only for 15 minutes or something.
after that i have to kill KDE and restart it.
it's also connected on ps2 port coz with usb it won't work at all.
hope someone helps us out :)

here are my settings:

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping""4 5"
Option "Buttons" "3"

Try "xf86cfg". Its generally pretty good at detecting mice and deciding on protocols, etc. Or else you could try removing the adapter and using the usb port.

Quote:

I've got the almost the same problem as you,
my mouse does work but only for 15 minutes or something.
after that i have to kill KDE and restart it.
it's also connected on ps2 port coz with usb it won't work at all.
hope someone helps us out

here are my settings:

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping""4 5"
Option "Buttons" "3"

If you have ZAxisMapping set to buttons "4 5" then why do you indicate that you only have 3 buttons???

Try setting your Options "Buttons" "5" and see if that does the trick. This way your left mouse button is "1", the right button "2", the middle wheel if you click it in is "3" and the mouse wheel up "4" and mouse wheel down "5".

rberry88

Quote:

If you have ZAxisMapping set to buttons "4 5" then why do you indicate that you only have 3 buttons???

As it turns out, you only need three buttons. This has been the subject of many threads. I have tried 5 buttons and 3 buttons and they both work. Don't ask me why, they just do.

I disagree on this, and this is taken from
The XFree86 site itself :

Code:

5.1. Buttons



This option tells the X server the number of buttons on the mouse. 

Currently there is no reliable way to automatically detect the correct number. 

This option is the only means for the X server to obtain it. The default value is three.



Note that if you intend to assign Z axis movement to button events using

the ZAxisMapping option below, you need to take account of those buttons into N too.



        Option        "Buttons"        "N"



5.2. ZAxisMappping



This option maps the Z axis (wheel) motion to buttons or to another axis.



        Option        "ZAxisMapping"        "X"

        Option        "ZAxisMapping"        "Y"

        Option        "ZAxisMapping"        "N1 N2"

        Option        "ZAxisMapping"        "N1 N2 N3 N4"



The first example will map the Z axis motion to the X axis motion. Whenever 

the user moves the wheel/roller, its movement is reported as the X axis motion.

When the wheel/roller stays still, the real X axis motion is reported as is. The third 

example will map negative Z axis motion to the button N1 and positive Z axis motion

to the button N2. If this option is used and the buttons N1 or N2 actually exists in 

the mouse, their actions won't be detected by the X server.



The last example is useful for the mouse with two wheels of which the second wheel is 

used to generate horizontal scroll action, and the mouse which has a knob or a stick 

which can detect the horizontal force applied by the user. The motion of the second 

wheel will be mapped to the buttons N3, for the negative direction, and N4, for the 

positive direction. If the buttons N3 and N4 actually exist in this mouse, their actions 

won't be detected by the X server.



NOTE #1: horizontal movement may not always be detected by the current version of 

the XFree86 X servers, because there appears to be no accepted standard as to how 

the horizontal direction is encoded in mouse data.



NOTE #2: Some mice think left is the negative horizontal direction, others may think otherwise. Moreover, there are some mice whose two wheels are both mounted vertically, and the direction

of the second vertical wheel does not match the first one's.



Currently this option can not be set in the XF86Setup program. You need to edit the XF86Config 

file by hand to add this option.

rberry88

I have 3 buttons in my XF86Config file, and my mouse scroll works fine. Whether or not it should work doesn't worry me, as long as it does.