Logitech MX1000 lazer mouse

chopp · 11-17-2005, 04:05 PM

I'd sure like to get all the buttons working on this overpriced mouse I bought.

From what I can find, I need to have evdev support. Well I have that compiled as a module, and the mouse show's up fine with

Code:

#cat /proc/bus/input/devices
I: Bus=0003 Vendor=046d Product=c50e Version=2500
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1f.2-1/input0
H: Handlers=mouse0 event0
B: EV=7
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=143

From what I can see from the very last entry in this post, I need evdev as a stand-alone driver, but that also require's x11-sdk.
http://www.linuxquestions.org/questi...ogitech+MX1000

I'm very confused, what the heck is x11-sdk. From that post, I do have scroll working, but no other button's work.
I can find rpm's of x11-sdk, but that doesn't seem like what I want to be doing.

Can anyone provide me with any assistance with this?

Thank you.

thingee · 11-18-2005, 03:49 PM

edit /etc/X11/XF86Config-4:

Code:

Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB Receiver"  # cat /proc/bus/input/devices
Option "Dev Phys" "usb-0000:00:1d.1-1/input0"  # cat /proc/bus/input/devices
Option "Device" "/dev/input/event0"  # (/dev/input/mice also appears to work)
Option "Buttons" "12"
Option "ZAxisMapping" "11 12"
Option "Resolution" "800"
EndSection

edit /etc/X11/xinit/.Xmodmap:

Code:

pointer = 1 2 3 6 7 8 9 10 11 12 4 5

Then restart X

Found this at: http://www.linuxquestions.org/questi...05/01/4/247340

Hope this helps

.

chopp · 11-19-2005, 12:29 AM

thank's for the reply thingee.

How are you using the evdev in slackware? From what I could understand from the link in my above post, the evdev module I allready have in my kernel will not work. They say I need a stand-alone version of it, which I could find, but also x11-sdk which I can't seem to get my hand's on.

Your's work's with "evdev" as the protocol?

This is the quote from the other post I found, and is just what happen's on my box:

Quote:

X Server shipped with slackware doesn't have EVDEV support so it will crash if you change the config.

This is a quote from the linuX-gamers how to:

Quote:

To compile the evdev driver you need the X.Org SDK package and the evdev-driver archive. The SDK package should ship with your distro. If you have compiled Xorg by yourself, you simply need a make install.sdk.

I did get the evdev driver, but it complain's about no xorg-x11-sdk on compile.

My scroll wheel work's just fine, just nothing else. This is relevent part of my xorg:

Code:

Identifier  "Mouse1"
    Driver      "mouse"
    Option      "Protocol"  "IMPS/2"
    Option      "Device"    "/dev/mouse"
    Option      "Buttons" "12"
    Option      "ZAxisMapping" "11 12"
    Option      "Resolution" "800"

and of course my Xmodmap:

Code:

pointer = 1 2 3 6 7 8 9 10 11 12 4 5

thingee · 11-19-2005, 02:24 AM

I haven't used this mouse before, nor messed with evdev. I did however find an article from newsforge that gives the code on how they got the "wheel scroll, scroll rocker, and browser rocker" working. Below is the code they gave...

xorg.conf

Code:

Option    "Buttons" "7"
Option    "ZAxisMapping" "6 7"

and .Xmodmap

Code:

pointer = 1 2 3 6 7 4 5

Found code from: http://hardware.newsforge.com/articl...1643256&tid=87

If this works, the side scroll button should be the only thing that doesn't work. This seems a lot easier to me than messing with evdev unless you really want the side scroll buttons to work. Sorry I'm not much of assistance, but that's as much as I found.

imitheos · 11-19-2005, 07:35 AM

Quote:

Originally posted by chopp
thank's for the reply thingee.

How are you using the evdev in slackware? From what I could understand from the link in my above post, the evdev module I allready have in my kernel will not work. They say I need a stand-alone version of it, which I could find, but also x11-sdk which I can't seem to get my hand's on.

The evdev from the kernel is the Event Interface. You need that.
The module you compile that requires the x11-sdk is the X server module that uses the kernel interface.

Quote:

Originally posted by chopp

Your's work's with "evdev" as the protocol?

This is the quote from the other post I found, and is just what happen's on my box:

The confusion is that there are many "evdev" ones

thingee you mention XF86Config so i guess you are using XFree (or an older Slackware version)
Did you compile it with the evdev patches ?

There were some patches from Debian or Gentoo that used the "mouse" driver and the "evdev" protocol as chopp pointed.
These were poorly written.
The new evdev code that you can compile as a module and exists natively in the CVS version of the XOrg server uses the "evdev" driver, is a better
implementation and doesn't need all the options that thingee mentions.

I describe the different configs & evdevs in this post (http://www.linuxquestions.org/questi...hreadid=378482)
It is for a MX510 but the same principles are for the MX1000 too.

Anyway, in a few words.
Chopp you can get the scroll and forward/back buttons working by simply using the "ExplorerPS/2" protocol
Otherwise, your solutions are.
1)Get the 3 old evdev patches from either Debian or Gentoo and recompile the X server
2)Get the SDK header files (slackware doesn't include them) and compile the new evdev module
3)Compile the Xorg CVS version

The primary guide is http://www.linux-gamers.net/modules/...p?articleid=46
People that do a search for mouse buttons here get confused because the same linux-gamers article used to have directions about the old evdev patches
and now it contains the new patch. So older posts here mention the config that thingee posted and newer posts use the "evdev" driver and not protocol
That is why people get confused.

thingee · 11-19-2005, 05:10 PM

Quote:

thingee you mention XF86Config so i guess you are using XFree (or an older Slackware version)
Did you compile it with the evdev patches ?

Actually no I don't. I referenced Xf86config and xorg in case Chopp was using an older version, in which I should've read his distribution tag to begin with. Like I said before, I never messed with evdev. I just hope the change in xorg.conf will help him get everything working on the mouse besides the side scroll button. I'm sorry if this assistance was waste.

chopp · 11-19-2005, 06:27 PM

Quote:

I'm sorry if this assistance was waste.

Not at all thingee, both your's, and imitheos's replies have helped me to understand what was going on here.

Thank you both, and happy slacking.

edit: happy 100 post's tooooooo me.

dive · 11-19-2005, 08:05 PM

I've just set up my MX510 with evdev. This is how i did it

Recompiled kernel (2.6.12) with event device support
Used #cat /proc/bus/input/devices to find my event no - H: Handlers=mouse0 event1
Edited xorg.conf:

Code:

Section "InputDevice"
Identifier  "Mouse0"
Driver      "evdev"
Option      "Device" "/dev/input/event1"
Option      "Name" "Logitech MX510"
EndSection

Installed IMWheel and edited my .xinitrc to start it when X starts

Edited /etc/X11/imwheel/imwheelrc:

Code:

".*"
,       Left, Page_Down 
,       Right,  Page_Up

Edit my .Xmodmap:

Code:

pointer = 1 3 2 4 5 8 9 6 7 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

This allows the side thumb buttons to works page up/down.

I think thats pretty much all I had to do but maybe I forgot something? Should be a start anyway, and I didn't need and sdk.

chopp · 11-20-2005, 02:45 AM

dive: I've got the mouse working, but I thought I would give your method a go. What the heck, I've only tried about five other method's.

Do you have the event device as a module, or compiled in the kernel. Mine is a module, and same as every other time I've used "evdev" in xorg.conf, it crash's X.

I'm also wondering about your .Xmodmap. Isn't that a few to many button's?

dive · 11-20-2005, 04:27 AM

Quote:

Originally posted by chopp
dive: I've got the mouse working, but I thought I would give your method a go. What the heck, I've only tried about five other method's.

Do you have the event device as a module, or compiled in the kernel. Mine is a module, and same as every other time I've used "evdev" in xorg.conf, it crash's X.

I'm also wondering about your .Xmodmap. Isn't that a few to many button's?

I compiled mine into the kernel and yeah thats quite a few buttons lol
Seriously only need 10 but since I was copying and pasting stuff from Linux Gamers site without really thinking too hard, thats how it ended up

When X crashes did you check that the dev event file system is actually making the correct files in /dev? That would be the culprit. If not I will have anoth look and see if theres anything else I installed.

dive · 11-20-2005, 05:02 AM

Well heres something - I just edited my .Xmodmap to 10 buttons and X crashes!
Try it with 32 and see what happens - maybe you need those extra ones defined somehow.

imitheos · 11-20-2005, 07:23 AM

chopp when you say X crashes what error message do you get ?
Is it about "Core Pointer" ?
If this is the case then you don't have the right device.
run "cat /proc/bus/input/devices" and see

"Well heres something - I just edited my .Xmodmap to 10 buttons and X crashes!"

X crashes because a command in xinitrc crashes (in this case xmodmap)
If during a X session you run

Code:

xmodmap -e "pointer = 1 2 .. 10"

you will get something like "i want 32 buttons and you specifies 10"

dive · 11-20-2005, 08:12 AM

Maybe thats why Chopp is also crashing - I say that because I have an MX510 and he a 1000 and maybe they need the .Xmodmap to specify 32 (or perhaps more) buttons?
That was the point I was trying to make