Configuring Logitech mice (mx500, etc)

PsychoBrat

This may have been covered by one of the other million posts in this thread, but a rehash with slightly different wording can only help for the loveable lost Googlers out there!

To get my Logitech MX510 working from a base Dapper Drake Flight 6 install (with some acceleration tweaks done through UI configuration tools in Gnome), I tried following several over-complicated (for my particular case) guides, then realised I could do away with all their stuff and make only a few small changes. My current /etc/X11/xorg.conf contains an InputDevice section as follows:

Code:

Section "InputDevice"
        Identifier      "Configured Mouse"
        Driver          "mouse"
        Option          "CorePointer"
        Option          "Device"                "/dev/input/mice"
        Option          "Protocol"              "ExplorerPS/2"
        Option          "Buttons"               "10"
        Option          "ZAxisMapping"          "4 5"
        Option          "ButtonMapping"         "1 2 3 6 7"
#       Option          "Emulate3Buttons"       "true"
EndSection

The important (modified) lines are:

Code:

Section "InputDevice"
        Option          "Buttons"               "10"
        Option          "ZAxisMapping"          "4 5"
        Option          "ButtonMapping"         "1 2 3 6 7"
#       Option          "Emulate3Buttons"       "true"
EndSection

...but you should be able to leave Emulate3Buttons on if you really want; it just fakes click from the third mouse button when buttons 1 and 2 are pressed together - not something that's too useful on a 10 button (including both scroll directions) mouse!

ZAxisMapping specifies which buttons to treat as the scroll-wheel. ButtonMapping specifies, in order of physical buttons, a list of button signals to send. So mine tells it that buttons 4 and 5 'pretend' to be 6 and 7 respectively. My other buttons are working as expected too (auto-scroll buttons are fine, window switch button just acts as another left button), so I presume they're implicitly mapped to their 'natural' signals (i.e. 8 to 8, 9 to 9, 10 to 10). (???)

This works fine for me in Firefox, but not other apps such as Nautilus. Does anyone know if this is expected (i.e. that you need to emulate keystrokes like ALT+{LEFT | RIGHT} from mouse clicks anyway)?

makhand

I've asked this before, and i'll try once more.
I'm doing this on a laptop.
These instructions work mostly fine for me. Except there are some catches.
1. I cannot get the mouse to work if it is not plugged in when X starts.
2. If the laptop goes into sleep/screensaver mode, it doesnt wake up and work with the mouse anymore (only the touchpad works at this point).
3. I have a dual monitor setup (I plug a monitor into my laptop) and all the functionality in this thread only works on the laptop lcd screen. As soon as my mouse travels to the other monitor, it loses all its power (beyond just normal point and click).

I made my synaptic touchpad my corepointer because it was the only way i saw to make X start at all without having the mouse plugged in at all times.

please help. Thanks

makhand · 04:02 PM

Quote:

Originally Posted by makhand

I've asked this before, and i'll try once more.
I'm doing this on a laptop.
These instructions work mostly fine for me. Except there are some catches.
1. I cannot get the mouse to work if it is not plugged in when X starts.
2. If the laptop goes into sleep/screensaver mode, it doesnt wake up and work with the mouse anymore (only the touchpad works at this point).
3. I have a dual monitor setup (I plug a monitor into my laptop) and all the functionality in this thread only works on the laptop lcd screen. As soon as my mouse travels to the other monitor, it loses all its power (beyond just normal point and click).

I made my synaptic touchpad my corepointer because it was the only way i saw to make X start at all without having the mouse plugged in at all times.

please help. Thanks

Well, i had a pretty brilliant idea. I've sort of resolved issue 3. To get the mouse keys to work with my second monitor, i simply opened up a terminal in that monitor and started 'xbindkeys' there. Unfortunately, i dont know how to make this automatic since xbindkeys is already being started automatically using System>Preferences>Sessions>Startup Programs. Somehow this does not apply to the second monitor.

Edit: xbindkeys has an optional parameter in which it allows you to specify the displays. for my dual monitor system, i simply have two programs execute (using Startup Programs). I use:

Code:

xbindkeys -X :0.0
xbindkeys -X :0.1

detyabozhye · 01:06 AM

I got evdev working on Dapper perfectly (requires xmodmap and xbindkeys).
WARNING: This is not a full guide, please refer to post one in this thread for 800dpi resolution, back/forward in nautilus, etc.

First I did this to find out the name of my mouse:

Code:

cat /proc/bus/input/devices

Here's my output with the info I need in bold:

Code:

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd event0
B: EV=40001
B: SND=6

I: Bus=0003 Vendor=046d Product=c025 Version=1800
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:1d.1-1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0003 Vendor=049f Product=000e Version=0100
N: Name="Compaq Compaq Internet Keyboard"
P: Phys=usb-0000:00:1d.1-2/input0
S: Sysfs=/class/input/input2
H: Handlers=kbd event2
B: EV=120003
B: KEY=10000 7 ff87207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: LED=7fff

I: Bus=0003 Vendor=049f Product=000e Version=0100
N: Name="Compaq Compaq Internet Keyboard"
P: Phys=usb-0000:00:1d.1-2/input1
S: Sysfs=/class/input/input3
H: Handlers=kbd event3
B: EV=3
B: KEY=20000 87a 5000d000 1e0000 0 0 0

Then I did this:

Code:

sudo gedit /etc/udev/rules.d/19-local.rules

and put this into the file and saved it (replace the bold part with the name of your mouse and replace the underlined part with whatever you want to put there, it will be used in xorg.conf):

Code:

KERNEL=="event[0-9]*", SYSFS{../name}=="Logitech USB-PS/2 Optical Mouse", NAME="input/mx500"

Then I changed my mouse section in xorg.conf to this:

Code:

Section "InputDevice"
	Identifier	"Configured Mouse"
	Driver		"evdev"
	Option		"CorePointer"
	Option		"Device"	"/dev/input/mx500" #this should be that underlined name from 19-local.rules
EndSection

Then I made my ~/.Xmodmap look like this:

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

Next I fixed cruise control (requires the compiling stuff; build-essential and all that I believe):
Download this file: http://bg.rifetech.com/click.tgz
untar it to ~/click (or wherever you want, just remember the dir, you'll need it in the .xbindkeysrc)
then compile it:

Code:

cd ~/click
make

Then I changed my ~/.xbindkeysrc to include this:

Code:

"~/click/click 4"
  m:0x0 + b:11
"~/click/click 5"
  m:0x0 + b:12

Credits: This article and http://floam.sh.nu/guides/mx1000
Let me know if I made any typos or mistakes.
EDIT: I don't think this works in Xgl, I haven't tried, but I doubt it will.

Rizado

Quote:

Originally Posted by detyabozhye

I got evdev working on Dapper perfectly (requires xmodmap and xbindkeys).
WARNING: This is not a full guide, please refer to post one in this thread for 800dpi resolution, back/forward in nautilus, etc.

First I did this to find out the name of my mouse:

Code:

cat /proc/bus/input/devices

Here's my output with the info I need in bold:

Code:

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd event0
B: EV=40001
B: SND=6

I: Bus=0003 Vendor=046d Product=c025 Version=1800
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:1d.1-1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0003 Vendor=049f Product=000e Version=0100
N: Name="Compaq Compaq Internet Keyboard"
P: Phys=usb-0000:00:1d.1-2/input0
S: Sysfs=/class/input/input2
H: Handlers=kbd event2
B: EV=120003
B: KEY=10000 7 ff87207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: LED=7fff

I: Bus=0003 Vendor=049f Product=000e Version=0100
N: Name="Compaq Compaq Internet Keyboard"
P: Phys=usb-0000:00:1d.1-2/input1
S: Sysfs=/class/input/input3
H: Handlers=kbd event3
B: EV=3
B: KEY=20000 87a 5000d000 1e0000 0 0 0

Then I did this:

Code:

sudo gedit /etc/udev/rules.d/19-local.rules

and put this into the file and saved it (replace the bold part with the name of your mouse and replace the underlined part with whatever you want to put there, it will be used in xorg.conf):

Code:

KERNEL=="event[0-9]*", SYSFS{../name}=="Logitech USB-PS/2 Optical Mouse", NAME="input/mx500"

Then I changed my mouse section in xorg.conf to this:

Code:

Section "InputDevice"
	Identifier	"Configured Mouse"
	Driver		"evdev"
	Option		"CorePointer"
	Option		"Device"	"/dev/input/mx500" #this should be that underlined name from 19-local.rules
EndSection

Then I made my ~/.Xmodmap look like this:

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

Next I fixed cruise control (requires the compiling stuff; build-essential and all that I believe):
Download this file: http://bg.rifetech.com/click.tgz
untar it to ~/click (or wherever you want, just remember the dir, you'll need it in the .xbindkeysrc)
then compile it:

Code:

cd ~/click
make

Then I changed my ~/.xbindkeysrc to include this:

Code:

"~/click/click 4"
  m:0x0 + b:11
"~/click/click 5"
  m:0x0 + b:12

Credits: This article and http://floam.sh.nu/guides/mx1000
Let me know if I made any typos or mistakes.
EDIT: I don't think this works in Xgl, I haven't tried, but I doubt it will.

I can't get it working properly

Creatin /dev/input/mx510 and using that works perfect but all extra buttons are recognized as a leftmouse click in firefox

This is what xev tell me when I use my side buttons.

Code:

ButtonPress event, serial 31, synthetic NO, window 0x1000001,
    root 0x135, subw 0x0, time 4219485450, (169,0), root:(1461,76),
    state 0x0, button 8, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x1000001,
    root 0x135, subw 0x0, time 4219485578, (169,0), root:(1461,76),
    state 0x0, button 8, same_screen YES

ButtonPress event, serial 31, synthetic NO, window 0x1000001,
    root 0x135, subw 0x0, time 4219486730, (169,0), root:(1461,76),
    state 0x0, button 9, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x1000001,
    root 0x135, subw 0x0, time 4219486946, (169,0), root:(1461,76),
    state 0x0, button 9, same_screen YES

I guess this looks alright. I'm using Kubuntu Dapper and in konqueror it doesn't seem to use the buttons as left click. And I didn't have any .Xmodmap or .xbindkeysrc so I created them.

detyabozhye

Quote:

Originally Posted by Rizado

I can't get it working properly

Creatin /dev/input/mx510 and using that works perfect but all extra buttons are recognized as a leftmouse click in firefox

This is what xev tell me when I use my side buttons.

Code:

ButtonPress event, serial 31, synthetic NO, window 0x1000001,
    root 0x135, subw 0x0, time 4219485450, (169,0), root:(1461,76),
    state 0x0, button 8, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x1000001,
    root 0x135, subw 0x0, time 4219485578, (169,0), root:(1461,76),
    state 0x0, button 8, same_screen YES

ButtonPress event, serial 31, synthetic NO, window 0x1000001,
    root 0x135, subw 0x0, time 4219486730, (169,0), root:(1461,76),
    state 0x0, button 9, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x1000001,
    root 0x135, subw 0x0, time 4219486946, (169,0), root:(1461,76),
    state 0x0, button 9, same_screen YES

I guess this looks alright. I'm using Kubuntu Dapper and in konqueror it doesn't seem to use the buttons as left click. And I didn't have any .Xmodmap or .xbindkeysrc so I created them.

Do you have xmodmap and xbindkeys installed?
If not:

Code:

sudo apt-get install xmodmap

Code:

sudo apt-get install xbindkeys

From the description of your problem, it seems xmodmap is not installed.

Rizado

Quote:

Originally Posted by detyabozhye

Do you have xmodmap and xbindkeys installed?
If not:

Code:

sudo apt-get install xmodmap

Code:

sudo apt-get install xbindkeys

From the description of your problem, it seems xmodmap is not installed.

xbindkeys wasn't installed but
xmodmap was, the problem was .Xmodmap wasn't autoloaded so I had to make a script to do that.

What is the click tool and script actually doing?

Rizado

Well, there was some updates yesterday and today and I think I remember evdev was updated. Anyway when I rebooted evdev driver doesn't work anymore. Am I the only one with the problems?

BTW this is on dapper.

siorai

Quote:

Originally Posted by Rizado

Well, there was some updates yesterday and today and I think I remember evdev was updated. Anyway when I rebooted evdev driver doesn't work anymore. Am I the only one with the problems?

BTW this is on dapper.

I just had this happen as well. Everything was fine until I actually restarted then X won't start, complaining about not having a valid CorePointer.

kemosabe79

Great HOWTO. I used it with a MX310 and it works great. I tried it because it has essentially the same specs as the MX510, and it worked. Might want to add the MX310 to your list.

This was done in Breezy, BTW...using 8 buttons not 10.

April 8th, 2006	#1
PsychoBrat First Cup of Ubuntu Join Date: Apr 2006 Beans: 5	Re: Configuring Logitech mice (mx500, etc) This may have been covered by one of the other million posts in this thread, but a rehash with slightly different wording can only help for the loveable lost Googlers out there! To get my Logitech MX510 working from a base Dapper Drake Flight 6 install (with some acceleration tweaks done through UI configuration tools in Gnome), I tried following several over-complicated (for my particular case) guides, then realised I could do away with all their stuff and make only a few small changes. My current /etc/X11/xorg.conf contains an InputDevice section as follows: Code: Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device" "/dev/input/mice" Option "Protocol" "ExplorerPS/2" Option "Buttons" "10" Option "ZAxisMapping" "4 5" Option "ButtonMapping" "1 2 3 6 7" # Option "Emulate3Buttons" "true" EndSection The important (modified) lines are: Code: Section "InputDevice" Option "Buttons" "10" Option "ZAxisMapping" "4 5" Option "ButtonMapping" "1 2 3 6 7" # Option "Emulate3Buttons" "true" EndSection ...but you should be able to leave Emulate3Buttons on if you really want; it just fakes click from the third mouse button when buttons 1 and 2 are pressed together - not something that's too useful on a 10 button (including both scroll directions) mouse! ZAxisMapping specifies which buttons to treat as the scroll-wheel. ButtonMapping specifies, in order of physical buttons, a list of button signals to send. So mine tells it that buttons 4 and 5 'pretend' to be 6 and 7 respectively. My other buttons are working as expected too (auto-scroll buttons are fine, window switch button just acts as another left button), so I presume they're implicitly mapped to their 'natural' signals (i.e. 8 to 8, 9 to 9, 10 to 10). (???) This works fine for me in Firefox, but not other apps such as Nautilus. Does anyone know if this is expected (i.e. that you need to emulate keystrokes like ALT+{LEFT \| RIGHT} from mouse clicks anyway)?

April 8th, 2006	#2
makhand A Carafe of Ubuntu Join Date: Dec 2004 Location: Evanston, IL Beans: 92 Ubuntu 7.04 Feisty Fawn	Re: Configuring Logitech mice (mx500, etc) I've asked this before, and i'll try once more. I'm doing this on a laptop. These instructions work mostly fine for me. Except there are some catches. 1. I cannot get the mouse to work if it is not plugged in when X starts. 2. If the laptop goes into sleep/screensaver mode, it doesnt wake up and work with the mouse anymore (only the touchpad works at this point). 3. I have a dual monitor setup (I plug a monitor into my laptop) and all the functionality in this thread only works on the laptop lcd screen. As soon as my mouse travels to the other monitor, it loses all its power (beyond just normal point and click). I made my synaptic touchpad my corepointer because it was the only way i saw to make X start at all without having the mouse plugged in at all times. please help. Thanks

April 25th, 2006	#4
detyabozhye Dipped in Ubuntu Join Date: Oct 2005 Location: California Beans: 580 Kubuntu 9.04 Jaunty Jackalope	Re: Configuring Logitech mice (mx500, etc) I got evdev working on Dapper perfectly (requires xmodmap and xbindkeys). WARNING: This is not a full guide, please refer to post one in this thread for 800dpi resolution, back/forward in nautilus, etc. First I did this to find out the name of my mouse: Code: cat /proc/bus/input/devices Here's my output with the info I need in bold: Code: I: Bus=0010 Vendor=001f Product=0001 Version=0100 N: Name="PC Speaker" P: Phys=isa0061/input0 S: Sysfs=/class/input/input0 H: Handlers=kbd event0 B: EV=40001 B: SND=6 I: Bus=0003 Vendor=046d Product=c025 Version=1800 N: Name="Logitech USB-PS/2 Optical Mouse" P: Phys=usb-0000:00:1d.1-1/input0 S: Sysfs=/class/input/input1 H: Handlers=mouse0 event1 ts0 B: EV=7 B: KEY=ff0000 0 0 0 0 0 0 0 0 B: REL=103 I: Bus=0003 Vendor=049f Product=000e Version=0100 N: Name="Compaq Compaq Internet Keyboard" P: Phys=usb-0000:00:1d.1-2/input0 S: Sysfs=/class/input/input2 H: Handlers=kbd event2 B: EV=120003 B: KEY=10000 7 ff87207a c14057ff febeffdf ffefffff ffffffff fffffffe B: LED=7fff I: Bus=0003 Vendor=049f Product=000e Version=0100 N: Name="Compaq Compaq Internet Keyboard" P: Phys=usb-0000:00:1d.1-2/input1 S: Sysfs=/class/input/input3 H: Handlers=kbd event3 B: EV=3 B: KEY=20000 87a 5000d000 1e0000 0 0 0 Then I did this: Code: sudo gedit /etc/udev/rules.d/19-local.rules and put this into the file and saved it (replace the bold part with the name of your mouse and replace the underlined part with whatever you want to put there, it will be used in xorg.conf): Code: KERNEL=="event[0-9]", SYSFS{../name}=="Logitech USB-PS/2 Optical Mouse", NAME="input/mx500" Then I changed my mouse section in xorg.conf to this: Code: Section "InputDevice" Identifier "Configured Mouse" Driver "evdev" Option "CorePointer" Option "Device" "/dev/input/mx500" #this should be that underlined name from 19-local.rules EndSection Then I made my ~/.Xmodmap look like this: 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 Next I fixed cruise control (requires the compiling stuff; build-essential and all that I believe): Download this file: http://bg.rifetech.com/click.tgz untar it to ~/click (or wherever you want, just remember the dir, you'll need it in the .xbindkeysrc) then compile it: Code: cd ~/click make Then I changed my ~/.xbindkeysrc to include this: Code: "~/click/click 4" m:0x0 + b:11 "~/click/click 5" m:0x0 + b:12 Credits: This article and http://floam.sh.nu/guides/mx1000 Let me know if I made any typos or mistakes. EDIT: I don't think this works in Xgl, I haven't tried, but I doubt it will. __________________ aka anime4christ (I'm a guy, btw.) My personal boring website ^_^ Jesus has changed your life. Save changes? (Y/N) Last edited by detyabozhye; April 25th, 2006 at 01:06 AM..*

May 6th, 2006	#8
Rizado Way Too Much Ubuntu Join Date: Nov 2005 Location: Sweden Beans: 252 Kubuntu 9.10 Karmic Koala	Re: Configuring Logitech mice (mx500, etc) Well, there was some updates yesterday and today and I think I remember evdev was updated. Anyway when I rebooted evdev driver doesn't work anymore. Am I the only one with the problems? BTW this is on dapper.

May 7th, 2006	#10
kemosabe79 Spilled the Beans Join Date: Sep 2005 Location: Rocket City Beans: 14	Re: Configuring Logitech mice (mx500, etc) Great HOWTO. I used it with a MX310 and it works great. I tried it because it has essentially the same specs as the MX510, and it worked. Might want to add the MX310 to your list. This was done in Breezy, BTW...using 8 buttons not 10.

Thread Tools
Show Printable Version Email this Page
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode