Section “InputDevice”
Identifier “MX1000”
Driver “evdev”
Option “CorePointer”
Option “Name” “Logitech USB Receiver”
Option “Buttons” “12”
Option “ZAxisMapping” “11 12 10 9”
Option “Resolution” “800”
EndSection

greets
Andreas

Device Drivers —>
Input Device Support —>
Event Interface

USB Support —>
USB Human Interface Device (full HID) support
[*] HID input layer support

– your kernel needs it compiled in
so:
Device Drivers —>
Input Device Support —>
Event Interface

USB Support —>
USB Human Interface Device (full HID) support
[*] HID input layer support

—————————————————————————-

recompile your kernel, and take evdev as driver and _not_ as protocol in your config. set protocol to auto. then reinstall the package with the xorg-evdev driver inside. for debian unstable this is xserver-xorg-input-evdev. then reconfigure this package (dpkg-reconfigure [package]) and restart x.

this should work by then.
it worked for me.

thanks for your help here!
greets, dante

I’ve tried other protocols: with “Logitech” the mouse doesn’t work at all, and with protocols like “ExplorerPS/2” and “auto” not all the buttons work properly (tilt is not detected at all, the app switch button is seen as button 1, etc).

I have a “few” questions. Perhapse someone is able to give me the answers…

I have tried the udev rule above, but with no success. That does not bother me too much because X is happy with event1

But

You tell me to use xvkbd, but I am not able to install it while it is conflicting with x11-common. I am on a debian/sid amd64 box.

I want to use the kcontrol part for logitech mice, but I have no permission to write to the device. My user is in group plugdev (perhaps a debian specific detail). Is there a possibility to set the permisson for the device by the udev rule?

Sorry for asking that much, but I am not able to dig that deep in the mud…

Thank you in advance.
Wolfgang

Identifier “MX1000”
Driver “mouse”
Option “CorePointer”
Option “Protocol” “evdev”
Option “Dev Name” “Logitech USB Receiver”
Option “Buttons” “12”
Option “ZAxisMapping” “11 12”
Option “Resolution” “800”
Option “Emulate3Buttons” “false”
Option “Device” “/dev/mouse”

Maybe somebody else can answer this, it should at /usr/X11R6/lib/modules/input/evdev_drv.so or a similar location.

here is my /proc/bus/input/devices:
I: Bus=0003 Vendor=046d Product=c50e Version=2500
N: Name=”Logitech USB Receiver”
P: Phys=usb-0000:00:11.2-2/input0
H: Handlers=mouse0 event1
B: EV=7
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=143

here is my /proc/bus/input/handlers:
N: Number=0 Name=kbd
N: Number=1 Name=mousedev Minor=32
N: Number=2 Name=evdev Minor=64

I’m guessing that my handler should be event2 instead of event1. I think the problem may be that evdev doesn’t seem to be a module but is compiled into the kernel (modprobe evdev does not find the module). …no clue how to proceed from here. Any help would be appreciated.

Both XFree86 and XOrg should work fine with evdev, I’m using it on several Debian installations. (Debian’s XFree86 has some evdev patches, so if you have a really old XFree86 package there might be problems. XOrg supports evdev without any additional patches.)

To get evdev running with X you need two things:

• A kernel with evdev support: This is an abstract layer, it provides access to all input devices connected to the machine. Both USB and PS/2 input devices should show up in /proc/bus/input/devices. PS/2 devices may have limited event support, though.
  (Standard Debian kernels have evdev built as a module which normally gets loaded by hotplug while booting or when attaching a input device.)
• An InputDevice section in the X configuration that has a Option "Protocol" "evdev" line. Using protocol evdev works at least for the mouse and kbd drivers. The Dev Phys and Dev Name options allow you to specify which input device gets used (you can get the values from /proc/bus/input/devices).

Regarding PS/2 devices. The kernel’s driver is the limiting factor here (AFAIK this applies both to direct PS/2 access and access via the evdev layer). Stock kernels won’t see all buttons. There are some patches which make it work with the tilt wheel of the Microsoft mice (IIRC that required patching X too) but even that wouldn’t make it see all buttons of the MX1000.

and my .xbindkeysrc
# Backward and Forward buttons
“xvkbd -text “\[Alt_L]\[Left]””
m:0x10 + b:8
“xvkbd -text “\[Alt_L]\[Right]””
m:0x10 + b:9

# “Cruise Control” disabled:
#”xvkbd -text “\[Page_Up]””
# m:0x10 + b:11
#”xvkbd -text “\[Page_Down]””
# m:0x10 + b:12

# “Cruise Control” enabled:
# Only use this if you have problems with Mozilla
“NoCommand”
m:0x10 + b:11
“NoCommand”
m:0x10 + b:12

This is my xbindkeysrc in case this helps someone. I like having the center thumb button be control-w, which closes xwindow,firefox tab, whatever running in x — very convenient.

Instead of horizontal scrolling with the y axis of the wheel (which i rare use) i prefer to have my y axis be next and prior so that I can skip move between tabs on firefox/mozilla effortlessly.

And for buttons 4 and 5 that are above and below the scroll wheel i have that set to go up one page and down one page per click on the browser with the control-next and control-prior.

Ydef