Bug 1947

Summary: Logitech MX 1000 mouse: xorg does not see all 12 buttons
Product: xorg Reporter: Sergey V. Udaltsov <svu>
Component: Input/MouseAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: highest    
Version: 6.8.1   
Hardware: x86 (IA32)   
OS: Linux (All)   
URL: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140963
Whiteboard:
i915 platform: i915 features:

Description Sergey V. Udaltsov 2004-11-27 07:30:53 UTC
Description of problem:
I plugged in Logitech MX 1000 mouse. Xorg server does not distinguish
some of its buttons. xev shows button numbers up to 5 - the side
buttons do not work. There is a discussion here:
http://www.linux-gamers.net/modules/wfsection/print.php?articleid=46.
I tried the approach described there (writing 12 buttons and other
options into xorg.conf) - but found that protocol "evdev" is not
supported.

xorg server would need ability to work with "evdev" Protocol directly
(there are some patches mentioned on that page).

Version-Release number of selected component (if applicable):
xorg-x11-6.8.1-12.FC3.1

How reproducible:
Always

Steps to Reproduce:
1. Plug in Logitech MX 1000 mouse (USB port)
2. Configure xorg.conf to use 12 buttons 
3. xmodmap -e "pointer = 1 2 3 6 7 8 9 10 11 12 4 5"

    

Actual Results:  xmodmap says it only sees 7 buttons, so cannot map 12
of them

Expected Results:  swapping buttons 11/12 and 4/5
Comment 1 Niko Mirthes 2004-12-01 00:09:48 UTC
I've got the same or similar problems with a Logitech MX510. i can use up to
seven buttons using the ExplorerPS/2 protocol by adding 

Option "ZAxisMapping" "6 7" 

to xorg.conf, and using

xmodmap -e "pointer = 1 2 3 6 7 4 5" 

to remap events. One extra problem i'm seeing that's not described here is one
of the "cruise control" buttons (button 4 or forward/upward scroll) produces
simultaneous ButtonRelease events. Pressing it gives ButtonRelease events for
both buttons 4 and 6.

I did have all buttons working as ecpected with the evdev patches while using
fedora's xorg 6.7.0. I've yet to bother adding them to fedora's xorg 6.8.1.
Having just purchased a Logitech keyboard that is also giving me trouble, i'm
hoping a driver(s) that can use the event interface will make it into upstream soon.
Comment 2 Niko Mirthes 2004-12-04 15:56:18 UTC
I came across http://bugzilla.kernel.org/show_bug.cgi?id=1786 reported against a
Logitech mx500 mouse quite a while ago. Can anyone say where this problem
originates? Kernel input layer, or X input? That bug report seems to indicate
it's not a kernel problem, and it does go away using debian's evdev patches.
Comment 3 arias hung 2005-01-18 20:18:23 UTC
Use the evdev version 3 patch named  9000_all_6.7.99.2-lnx-evdev-core-v3.patch
Comment 4 Sergey V. Udaltsov 2005-01-19 16:01:27 UTC
(In reply to comment #3)
> Use the evdev version 3 patch named  9000_all_6.7.99.2-lnx-evdev-core-v3.patch

Could you attach it please?

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.