My MX1000 mouse is (usually) misconfigured by evdev. It seems to be almost always, although it was working fine for a while last night. I haven't figured out how to reproduce it reliably.
The buttons reported via evtest (and correspondingly triggering events
in Xorg's evdev driver) are quite wrong:
> [EMAIL PROTECTED]:~$ sudo evtest /dev/input/event6
> Input driver version is 1.0.0
> Input device ID: bus 0x3 vendor 0x46d product 0xc50e version 0x2510
> Input device name: "Logitech USB RECEIVER"
> Supported events:
> Event type 0 (Reset)
> Event code 0 (Reset)
> Event code 1 (Key)
> Event code 2 (Relative)
> Event type 1 (Key)
> Event code 114 (VolumeDown)
> Event code 115 (VolumeUp)
> Event code 158 (Back)
> Event code 159 (Forward)
> Event code 163 (NextSong)
> Event code 164 (PlayPause)
> Event code 165 (PreviousSong)
> Event code 200 (PlayCD)
> Event code 272 (LeftBtn)
> Event code 273 (RightBtn)
> Event code 274 (MiddleBtn)
> Event code 275 (SideBtn)
> Event code 276 (ExtraBtn)
> Event type 2 (Relative)
> Event code 0 (X)
> Event code 1 (Y)
> Event code 8 (Wheel)
> Testing ... (interrupt to exit)
Consequently, the horizontal scroll is reported as a volume-change
keyboard event, the side buttons are 6/7, the cruise-control buttons
come through as forward-backward web events, and generally is just not
very usable.
The Vendor/Product information in /proc/bus/input/devices is correct:
> I: Bus=0003 Vendor=046d Product=c50e Version=2510
> N: Name="Logitech USB RECEIVER"
> P: Phys=usb-0000:00:1d.7-3.5/input0
> S: Sysfs=/class/input/input24
> H: Handlers=kbd mouse1 ts1 event6
> B: EV=7
> B: KEY=1f0000 0 100 38 c0000000 c0000 0 0 0
> B: REL=103
The relevant /proc/bus/usb/devices entry:
> T: Bus=05 Lev=02 Prnt=25 Port=04 Cnt=03 Dev#= 30 Spd=1.5 MxCh= 0
> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=046d ProdID=c50e Rev=25.10
> S: Manufacturer=Logitech
> S: Product=USB RECEIVER
> C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 70mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=lmpcm_usb
> E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
Not sure where else to go with this.
When in this incorrect state it also seems to suffer from a lack of
sysfs information:
> [EMAIL PROTECTED]:~# udevinfo -a -p $(udevinfo -q path -n /dev/input/event6)
>
> Udevinfo starts with the device specified by the devpath and then
> walks up the chain of parent devices. It prints for every device
> found, all possible attributes in the udev rules key format.
> A rule to match, can be composed by the attributes of the device
> and the attributes from one single parent device.
>
> looking at device '/class/input/input25/event6':
> KERNEL=="event6"
> SUBSYSTEM=="input"
> DRIVER==""
> ATTR{dev}=="13:70"
>
> looking at parent device '/class/input/input25':
> KERNELS=="input25"
> SUBSYSTEMS=="input"
> DRIVERS==""
>
> ATTRS{modalias}=="input:b0003v046DpC50Ee2510-e0,1,2,k72,73,9E,9F,A3,A4,A5,C8,110,111,112,113,114,r0,1,8,amlsfw"
> ATTRS{uniq}==""
> ATTRS{phys}=="usb-0000:00:1d.7-3.5/input0"
> ATTRS{name}=="Logitech USB RECEIVER"
No idVendor or idProduct information is present here, which stopped my
usual udev rule from working.
Any debugging or correction suggestions welcome.
signature.asc
Description: Digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
