Configuring Logitech mice (mx500, etc)

[endy]

A complete guide to a Logitech mouse

This is my guide on how to get all the buttons working properly on a logitech mouse, how to use the "logitech_applet" to enable the higher resolutions and cruise control and how to get the side mouse buttons to make forwards and back work in Nautilus and Epiphany.

This works for my mx510, I assume it would work for the similar mx500 and mx518 and the wireless versions like the mx700 however, I haven't got all those mice so I'd appreciate it if anyone get them working to post a reply and I'll make a list of what works.


Section 1: Getting your mouse working on USB with evdev
I once had my mouse plugged in via the PS/2 connector and used the "ExporerPS/2" protocol in my xorg.conf file, this generally worked but the little scroll up button would also make Firefox go back a page. This is not a bug this is because the "ExporerPS/2" is made for Microsoft mice not Logitech. So what can we do about it? Well first off you need to plug your mouse into a USB port, you can't do anything else in this how to until you do that. I have unplugged my mouse from the PS/2 port and plugged it into a USB port while logged into my desktop and it worked fine so go ahead and do that now.


1. Getting all the information you need

Great, so we're all plugged in via USB and ready to go. Before we change anything we need to get some important information about the mouse so run the following command in your favourite terminal:

cat /proc/bus/input/devices You should get a list of details, here's what I get and I'll highlight the bit we need to concentrate on:

endy@ananke:~$ cat /proc/bus/input/devices
I: Bus=0003 Vendor=046a Product=0023 Version=0027
N: Name="046a:0023"
P: Phys=usb-0000:00:02.0-7/input0
H: Handlers=kbd event0
B: EV=120003
B: KEY=7 ff800000 7ff e0b2ffdf 1cfffff ffffffff fffffffe
B: LED=1f

I: Bus=0003 Vendor=046a Product=0023 Version=0027
N: Name="046a:0023"
P: Phys=usb-0000:00:02.0-7/input1
H: Handlers=kbd event1
B: EV=f
B: KEY=1 0 38000 39fa d841d7a9 9e0000 0 0 0
B: REL=40
B: ABS=ffffff01 0

I: Bus=0003 Vendor=046d Product=c01d Version=2100
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:02.0-8/input0
H: Handlers=mouse0 event2 ts0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
H: Handlers=kbd event3
B: EV=40001
B: SND=6 We know this is the correct bit because the name "Logitech USB-PS/2 Optical Mouse". Your output will be different but the bit I've highlighted is all we need.

Note: For mx700 users the mouse name is "Logitech USB Receiver", thanks to everyone for the info!

2. Editing the xorg.conf file

Now we have the information we need to start to set up xorg. So open up your xorg.conf file in your favourite editor, mine is leafpad but as gedit is on everyone elses install by default you can type:
sudo gedit /etc/X11/xorg.conf Now scroll down to the mouse section and instead of deleting it we're going to comment it out, to do this you put a "#" in front of each line in the section, again here is my commented section as an example:

#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "CorePointer"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "ImPS/2"
# Option "Emulate3Buttons" "true"
# Option "ZAxisMapping" "4 5"
#EndSection Again, yours might look different, the important bit is to comment the whole section out, but only this section.

Next up we want to paste in out new section, make a but of room underneath (or above if you prefer) that section we just commented out and paste in the following template:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys"
Option "Device"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection If, when you read the details of the mouse (above) it printed a different name to "Logitech USB-PS/2 Optical Mouse" then edit that so it's right, but I suspect it will be the same. Next you'll have probably noticed there are two fields missing, "Dev Phys" and "Device". We'll fill this in now.

"Dev Phys" needs the detail from the "Phys" line from the output before, so if you look back at my example mine said "Phys=usb-0000:00:02.0-7/input1" so I would put "usb-0000:00:02.0-7/input1" in or better yet as we can use wild cards I would use "usb-*/input0" which, if anything else, looks better :)

"Device" needs the detail from the "Handlers" line, again my example was "Handlers=mouse0 event2 ts0", this time all we need it the name of what "event" it is. For me it's "event2" but before we add it to the xorg.conf file we need to make sure we use the full path which will be "/dev/input/event2".

DancingSun wisely pointed out that the button numbers after "ZAxisMapping" should be the values of the scroll wheel up and down. Use the "xev" tool in a terminal to check which button numbers these are. That is, you run "xev" in a terminal, hover the mouse over the pop up window and on the mouse push the scroll wheel up. The last line of the output in the terminal will tell you what button number you just pressed. Here is a sample from running xev, I've highlighted the button number:
ButtonPress event, serial 29, synthetic NO, window 0x3a00001,
root 0x134, subw 0x0, time 10223576, (111,54), root:(126,151),
state 0x0, button 4, same_screen YES

ButtonRelease event, serial 29, synthetic NO, window 0x3a00001,
root 0x134, subw 0x0, time 10223576, (111,54), root:(126,151),
state 0x800, button 4, same_screen YES Note the button number down and do the same for the scroll wheel down then put it in the xorg.conf file, scroll up goes first, then scroll down. For mx510 users the above "4 5" is correct.

DancingSun also has posted a great way to find out exactly how many mouse buttons you actually have for the "Buttons" setting in your xorg.conf file, it's explained best in DancingSun's post which you can read here (http://www.ubuntuforums.org/showpost.php?p=361478&postcount=30). Thanks again DancingSun!

Note: mx700 users report the name needs to be "Logitech USB Receiver" not "Logitech USB-PS/2 Optical Mouse" like it is for my mx510. Please refer to your output from "cat /proc/bus/input/devices" to be sure. Additionally, iverson0881 found that for the mx700 you can use "/dev/input/ts0" to work. Again check your output from earlier as you may need to change it to "ts1" or "ts2" etc... You can see iverson0881's post here (http://ubuntuforums.org/showpost.php?p=353244&postcount=12).

Make sure you save the changes to your xorg file.

So to conclude, here is my example with everything filled in:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event2"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection Note: If you have another mouse with more or less buttons then you may will have to correct the "Buttons" and "ZAxisMapping" numbers, but mine are correct for the mx510. It may not seem like it has ten buttons but it does if you count every single button


3. Restart X

Warning!
Don't restart X yet! Just before we do I have to warn you if you made a mistake in the xorg file X will not restart. But don't worry that's why we only commented out the previous settings and didn't delete them. If X fails to restart then you will end up in a text console. Log in and type the following to edit the xorg file:

sudo nano /etc/X11/xorg.conf All you need to do is comment out the new section we just added by putting a "#" in front of each line and un-commenting the original section by deleting the "#" which is at the start of each line. Save the xorg file in nano by typing "CTRL + X" press "Y" to confirm the save and type "startx" to get back to your desktop and re-read section two carefully and correct your xorg file.


Ok, I'm ready
Now we're prepared, restart X by pressing "CTRL + ALT + BACKSPACE" simultaneously and hopefully after a moment you can log back in.


4. Editing the Xmodmap file

** THIS SECTION IS REDUNDANT, SKIP TO SECTION 2 BELOW ** as DancingSun pointed out, using correct "ZAxisMapping" settings in your xorg.conf file is the correct way to have your scroll wheel work. See above about editing your xorg file, I will leave this section here for reference.

Note: prelude has found you don't necessarily need this step if you are using an mx1000. Thanks prelude!

You probably already have an Xmodmap file but now we have more buttons available we need to correct it. Open it up with your text editor:
gedit ~/.Xmodmap and paste the following, overwriting any previous "pointer" line:
pointer = 1 2 3 6 7 8 9 10 4 5
Now run xmodmap to apply these settings:
xmodmap ~/.Xmodmap If this is the first time you created a .Xmodmap file then next time you log into gnome it will ask you if you want to automatically load it, add the file and click Ok if this happens.

Now all the buttons should work properly including the little up button above the scroll wheel. The side buttons should also make Firefox go forward and backward a page just like before but they will not work in Nautilus yet. Keep reading to see how to get that to work!

Note: Again, if you're mouse has more or less buttons then you'll need to figure out what button numbers are the two side buttons, you can do this with the utility "xev" which you run from the terminal, hover the mouse over the pop up box and hold it still and press the side buttons. You'll see some output part of which is a button number. The two button numbers for you mouse go last in the .Xmodmap file, look at mine as an example.
Section 2: Side buttons and Nautilus
We can use "xvkbd" and "xbindkeys" to bind the side mouse buttons to "ALT + LEFT" and "ALT + RIGHT" so they work as forward and backwards in Nautilus.


1. xvkbd and xbindkeys

Lets install "xvkbd" and "xbindkeys":

sudo apt-get install xvkbd xbindkeys Next we need to create the configuration for them:

gedit ~/.xbindkeysrc Now paste the following:

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7

Please note, the "L" and "R" from the words "left" and "right" in the square brackets above should be capitalised, this seems like a bug in the forums here that they don't display properly.

Make sure you keep the quote marks, save the file and run "xbindkeys" in the terminal. It runs as a daemon in the background. You should now be able to test if it works in Nautilus by using the side buttons it also works in Epiphany if you use it.

Note: Same as before, if you have different mouse buttons use xev to find out what number they are and change the "b:6" and "b:7" in the above to the correct numbers.

2. Adding it to your session

Now it's working open up the gnome sessions settings "System > Preferences > Sessions" click on the "Startup Programs" tab, click "Add" and enter "xbindkeys". This makes sure it's run each time you log in, you should probably test it by logging out and back in now.
Section 3: The logitech_applet

First of all some people use a program called LMCtl instead, but I've never had it working so I use logitech_applet, which isn't an applet by the way :) This section is for making sure your mouse is using the best resolution it can, making it more accurate which is pretty handy especially in games where that counts like Quake 3 :)


1. Getting everything we need

There is no logitech_applet in Synaptic so I just download the source and use the program "checkinstall" to package it and install it, you'll also need the "build-essential" packages which can be quite large so bear this in mind and the "libusb-dev" library. Once this is done you can uninstall it if you want via Synaptic. Ok so lets download and install logitech_applet:

sudo apt-get install checkinstall build-essential libusb-dev
wget http://freshmeat.net/redir/logitech_applet/53319/url_tgz/logitech_applet-0.4test1.tar.gz
tar xvfz logitech_applet-0.4test1.tar.gz
mv ./logitech_applet-0.4test1 ./logitech-applet-0.4test1
cd ./logitech-applet-0.4test1
./configure --prefix=/usr
make
sudo checkinstall
Just hit enter when checkinstall prompts you. Now it should be installed :)


2. Working logitech_applet

I use the command "logitech_applet -s 800 -e" which you can run now:

sudo logitech_applet -s 800 -e This sets the mouse resolution to it's maximum 800cpi and makes sure the "cruise control" is enabled, you'll probably have to adjust the mouse settings in gnome as it should be much more accurate now. Type "logitech_applet --help" for more information.


3. Load on boot

We need to add this to a start up script so it's done automatically when the machine boots up, to do this I make a file in /etc/init.d/local where I keep local settings, so lets make that now:

sudo gedit /etc/init.d/local Now paste the logitech_applet command, mine like the example above is:

echo "Setting up Logitech mouse..."
logitech_applet -s 800 -e I have the echo line so I can check if it works in the boot messages, it's nice but you don't need it.

To make it executable run the following command:
sudo chmod 755 /etc/init.d/local
Now run the following command to make the "local" script run when the system boots:
sudo update-rc.d local defaults Now the applet loads automatically on boot, huzzah! :)
Conclusion

I think that's everything, phew, this was longer than I expected. I hope it works for you and I haven't made too many mistakes. Please add any corrections and success stories for logitech mice other then the mx510 so we can find out what works. Oh an I can confirm this still works on breezy right now and should still work when it's released.

Thanks to linux-gamers.net who have some great guides and give me good ideas and everyone who gave me feedback and corrections :)

[GoA]

Thanks, will try this @home.

[A-star]

Thanks, will try this @home.
Does this also work with a Logitech Dual Optical

[aboe]

This works with Breezy...I got a logitech mx510 and it works great...
thanks for the great how to....
couldn't figure out the small buttons on top with the other how to's about extra buttons...

but this worked great...

[GoA]

*) Option "Protocol" "evdev"
(**) Configured Mouse: Protocol: evdev
(**) Option "Buttons" "10"
(==) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "9 10"
(**) Configured Mouse: ZAxisMapping: buttons 9 and 10
(**) Configured Mouse: Buttons: 10
(**) Configured Mouse: Protocol: evdev
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Buttons" "10"
(==) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "9 10"
(**) Configured Mouse: ZAxisMapping: buttons 9 and 10
(**) Configured Mouse: Buttons: 10
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) XINPUT: Adding extended input device "evdev brain" (type: evdev brain)
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
(**) Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
(**) Option "Dev Phys" "usb-*/input0"
(EE) Configured Mouse: cannot open input device
(**) Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
(**) Option "Dev Phys" "usb-*/input0"
(EE) Configured Mouse: cannot open input device
No core pointer

Fatal server error:
failed to initialize core devices

Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Didn't work with MX700.

Here is the cat:

I: Bus=0003 Vendor=046d Product=c506 Version=1600
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:02.1-2/input0
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=103

And with xorg I used usb-*/input0 and /dev/input/event1. Don't know anymore what happened. :)

[souled]

I also have the Mx 700 but cannot get it to work.

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Logitech Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 ts0 event1
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

When I change the xorg.conf and put in:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "PS/2 Logitech Mouse"
Option "Dev Phys" "isa0060/serio1/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "10"
Option "ZAxisMapping" "9 10"
EndSection

X starts fine, but I am unable to move my mouse. And yes, I do have my mouse plugged into a USB port.

[rejser]

I run in xorg.conf
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"

then installed imwheel and run following script at startup

#!/bin/sh
exec xmodmap -e "pointer = 1 2 3 6 7 4 5" &
exec imwheel -k -b "67" &
exec $REALSTARTUP

and finaly you have to put

".*"
None, Up, Alt_L|Left
None, Down, Alt_L|Right

"(null)"
None, Up, Alt_L|Left
None, Down, Alt_L|Right

in /etc/X11/imwheel/imwheelrc ( at the bottom is ok)

This tip is from someone in this forum, couldn't find who should have the credz though, so give them to me for the moment and I will pass them on (or not)
__________________

On my logitech MX 700, backward and forward works with nautilus, xffm, firefox...

[souled]

I run in xorg.conf
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"

then installed imwheel and run following script at startup

#!/bin/sh
exec xmodmap -e "pointer = 1 2 3 6 7 4 5" &
exec imwheel -k -b "67" &
exec $REALSTARTUP

On my logitech MX 700, backward and forward works with nautilus, xffm, firefox...

I changed my xorg.conf to look like yours, and I ran that script. Now the scroll up and down buttons work, but the thumb buttons also scroll up and down. The lower thumb button scrolls up and the upper thumb button scrolls down. How can I fix this?

[prelude]

howdies

Ive used this guide on Breezy with a MX1000 mouse, I cant complete the guide, but its not completly fruitless.

first off, I edited my xorg.conf like this

Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB RECEIVER"
Option "Dev Phys" "usb-0000:00:1d.2-2.2/input0"
Option "Device" "/dev/input/event3"
Option "Buttons" "12"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "false"


and restarted X (with sudo killall gdm, logged in on a term and did sudo gdm) back in gnome the mouse worked as before the edit, but with one exception.

the thumbbuttons worked in firefox withouth any other tinkering under the hood \\:D/ the only strangeness was that the wheel-tilt to the right registrers as scroll up while tilt left goes down and the cruise buttons registers as a single 'click' up or down, where it before the editing gave me continius scroll up/down.

then I installed xvkbd and xbindkeys and with both config files as explained in this howto applied on a MX1000 mouse gives erratic behaviour.

HOWEVER, if you leave out the xmodmap step the mouse works as expected.
simply put, with a MX1000 mouse you dont really need xmodmap if you dont plan to use the sidetilt and crouse buttons. if you do want to use xmodmap with this guide you need to put


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

into the .Xmodmap file.

as you can see, the mousebutton-layout in xmodmap doesnt swap around any buttons. (atleast with me, youre milage may vary)
note. when xmodmap is used the continius scrolling by holding down one of the cruisebuttons works again with me.

here ends my experience, Ive havent got past the installation of the logitec applet, when I try to install it this happens.


checking for usb.h... no

ERROR! libusb header not found, get it from
http://libusb.sourceforge.net
or use the --with-libusb-includes option, if you have it installed
in an unusual place


now Ive checked with synaptic, I have libusb. Ive tried re-installing it, Ive tried removing it completly and then installing it again but to no avail and I have no clue where the include files might be ](*,)

ahhwell..

my thumb buttons works, thats the important stuff. :grin:

[endy]

Goa, I notice from the output of "cat /proc/bus/input/devices" you get Name="Logitech USB Receiver", try using that name in the xorg.conf file like this:
"Dev Name" "Logitech USB Receiver"
I hope this works :)

souled, this is strange. It would look like the "event0" is maybe not the right one. What you can do to make sure is "ls /dev/input" and go through trying to cat each event as root and try moving your mouse. If you get loads of garbage in the terminal when you move the mouse then that "event*" is the right one. Here is an example of what I mean:

cat /dev/input/event0
If when you move the mouse nothing happens try /dev/input/event1 etc... Hopefully one of them will work and use that in your xorg.conf.

prelude, thanks for the update on the mx1000 and the Xmodmap file, I've updated the guide :) I also noticed that I did miss out the need to install the "libusb-dev" library to compile the logitech_applet, again I've updated the guide with "sudo apt-get install libusb-dev" :)

[rejser]

I changed my xorg.conf to look like yours, and I ran that script. Now the scroll up and down buttons work, but the thumb buttons also scroll up and down. The lower thumb button scrolls up and the upper thumb button scrolls down. How can I fix this?

Oh, forgot that you have to put

".*"
None, Up, Alt_L|Left
None, Down, Alt_L|Right

"(null)"
None, Up, Alt_L|Left
None, Down, Alt_L|Right

in /etc/X11/imwheel/imwheelrc ( at the bottom is ok)

[iverson0881]

I have a MX700 and this worked fine although here is what I have in my xorg.conf:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "usb-*/input1"
Option "Device" "/dev/input/ts0"
Option "Buttons" "10"
Option "ZAxisMapping" "9 10"
EndSection

My mouse is connected through the Ps/2 port of the computer while keyboard is connected through USB. I have the Logitech MX Duo

[prelude]

prelude, thanks for the update on the mx1000 and the Xmodmap file, I've updated the guide :) I also noticed that I did miss out the need to install the "libusb-dev" library to compile the logitech_applet, again I've updated the guide with "sudo apt-get install libusb-dev" :)

so thats the little bugger that stopped me from making the logitec 'applet'. when I fiddled with synaptic I saw it but I ignored it as the error message didnt say squat about any missing -dev support :roll:

dont think Ill complete it though, Im just happy my side buttons work allright \\:D/

[souled]

Oh, forgot that you have to put

".*"
None, Up, Alt_L|Left
None, Down, Alt_L|Right

"(null)"
None, Up, Alt_L|Left
None, Down, Alt_L|Right

in /etc/X11/imwheel/imwheelrc ( at the bottom is ok)

I did this, and the thumb buttons work, but now the up scroll button acts as the back button.

souled, this is strange. It would look like the "event0" is maybe not the right one. What you can do to make sure is "ls /dev/input" and go through trying to cat each event as root and try moving your mouse. If you get loads of garbage in the terminal when you move the mouse then that "event*" is the right one. Here is an example of what I mean:

Trying it this way... I get a bunch of "garbage" output when I use /dev/input/event3. Nothing happens for event 0-2. When I used event 3 in the xorg.conf, I get the same problem. Everything works, but I can't move my mouse.

[rejser]

I did this, and the thumb buttons work, but now the up scroll button acts as the back button.


Mine does to, never tested that button, will try to fix during the day

[rejser]

A fixed for Logitech mx510 700 900 1000 (not 500, test 9 buttons)
(on what i wrote earlier)
I run in xorg.conf
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "10" <--- change from earlier post
Option "ZAxisMapping" "6 7"

then installed imwheel and run following script at startup

#!/bin/sh
exec xmodmap -e "pointer = 1 2 3 6 7 8 9 10 4 5" & <--- also a change
exec imwheel -k -b "67" &
exec $REALSTARTUP

and finaly you have to put

".*"
None, Up, Alt_L|Left
None, Down, Alt_L|Right

"(null)"
None, Up, Alt_L|Left
None, Down, Alt_L|Right

in /etc/X11/imwheel/imwheelrc ( at the bottom is ok)

still the same....

[endy]

iverson0881, thanks for the info, I've updated the guide accordingly :)

souled, I suggest you try this too, refer to iverson0881's post (http://ubuntuforums.org/showpost.php?p=353244&postcount=12) as an example but double chek your output from "cat /proc/bus/input/devices" to make sure which "ts" you could try, ie ts0, ts1 etc...

[Shambler]

Works like a charm under Breezy with my MX500, although the correct device name for this model is: "B16_b_02 USB-PS/2 Optical Mouse"

Just 2 small corrections:

1. It has to be sudo apt-get install checkinstall build-essential libusb-dev

2. You have to chmod 755 /etc/init.d/local so that it gets loaded

[GoA]

Works perfectly now with mx700 thank you so much. :)

[endy]

Thanks Shambler, I've amended the guide accordingly. Great to hear it works :)

[poofyhairguy]

This how to just saved my Linux life. For the past few days I could not log into Ubuntu because the Xserver could not detect my mouse driver. I could comment out the mouse device part and get it to work, but the mouse had minimal functions. I was scared I would have to reinstall or quit using Ubuntu because I really like to scroll. But with the info in this how to and thread I have my mouse working better than before. Awesome!

Great how to.

[endy]

Thanks! Ironically I wrote this after a very, very long day when I was completely exhausted but I had this guide in my head for a few days and just wanted to get it out. I thought I'd managed to clear up most of the mistakes but just now noticed I mistyped the topic. That's what happens when you post on forums half asleep :)

Anyway, glad to hear this helped.

[spacemonkey]

What about a MediaPlay Mouse? Any way to get the media control buttons working? I really miss them.

[endy]

If you can get the buttons to register with xev then all you need to do is bind them to shortcuts I guess... I don't have this mouse so I don't know what level of support there is for it. If you try please post any success stories for others to find :)

[DancingSun]

I would like to add that it is NOT necessary to remap the scroll buttons. It seems a bit self-defeating that almost all of the guides tell you to assign buttons 9 and 10 to z-axis, but then remaps the buttons 9 and 10 to the position where buttons 4 and 5 are. Essentially, you are telling X that buttons named 9 and 10 are your z-axis buttons, then you remap the button names so that the physical buttons 4 and 5 are named 9 and 10. You might as well just assign 4 and 5 to the zaxismapping option and do away with remapping the buttons altogether.

I'm using MX510, and I did not go through the remapping stage when I configured my mouse, just as the user with the MX1000 mouse.

Here's how it should work:
Type the following command into your terminal:
xev
This will bring up a little window where you can move your mouse pointer into. You can see all of the events generated by the mouse. Try clicking each of the buttons on your mouse while the mouse pointer is inside the window. Make sure the mouse stays stationary, or else you'll get a bunch of movement events that will make finding the button events harder.

In my case, I can clearly see that my scroll wheel generates the same button events as my cruise buttons. So essentially they are of the same buttons (cruise up = scroll up, cruise down = scroll down). This tells me that my MX510 have 8 functional buttons, not 10! The number of buttons entered in xorg.conf should be the highest button number event, which is 8 in my case. So adjust your number of buttons option accordingly!

Now, to setup the zaxismapping in xorg.conf, take note of the button events generated by the scroll buttons, and enter them into the zaxismapping option. I believe most mice generate button events 4 and 5 for scroll wheels, and this is exactly what I have for the zaxismapping option:
Option "ZAxisMapping" "4 5"

BTW, this is a great guide! I've been wanting to write one myself, but was too lazy. On another note, endy, the first two part of this guide (the xorg.conf using evdev and button binding part) should be generic to any mice. So you could split those parts out as a generic configuration guide to multi-button mice with scroll wheels.

[prelude]

that user would be me :P

on my mx1000 I need to have 12 buttons in xorg to make things work properly, even though xev output only reports 10 diffrent buttons.

xev reports the following buttons.

left click: button 1
middle click: button 2
right click: button 3
scroll forward: button 4
scroll backward: button 5
tilt right: button 4
tilt left: button 5
forward thumb: button 8
app. button: button 6
thumb button: button 7
cruise forward: button 4 and 10
cruise backward: button 5 and 12

as you can see, my mouse reports all buttons from 1 to 12 but skips 9 and 11. I belive those two missing buttons are the tilt-wheel and either xorg/xev is unable to recieve/see them, or logitec has built in a switch that can be sent from the host machine into the mouse telling it to report the extra buttons or not.

anyhows, my point is that not all mice might work if one enters less buttons in xorg.conf than their mice really have.

[DancingSun]

Perhaps I should put it this way:
The number of buttons to be enter in xorg.conf equal the highest button number event recorded in xev.
Does that sound right? I'm not trying to say one should enter less number of buttons that what their mice really have, just that one should enter the "correct" number of buttons that the mice is actually generating.

[KompresZor]

Thanks for the great guide!!
I have an old Logitech 4 (6) button USB mouse ( M-BA47 ) and with a few minor changes this worked perfectly! All I had to do was change the setting in xorg.conf, restart X and everything worked. :grin:

Here is my xorg.conf.
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Mouse M-BA47"
Option "Dev Phys" "usb-0000:00:07.3-1/input0"
Option "Device" "/dev/input/event4"
Option "Buttons" "6"
Option "ZAxisMapping" "4 5"
EndSection

[endy]

Thanks DancingSun, I can't believe I didn't notice that! I've been doing that for over a year and never thought to question what I was doing. Guide updated :)

[DancingSun]

Thanks DancingSun, I can't believe I didn't notice that! I've been doing that for over a year and never thought to question what I was doing. Guide updated :)
No problem! Glad I could contribute! Also, you might want to update the part about the number of buttons to enter in xorg.conf.

Essentially, you should enter the highest button number that is captured by xev. I should note that to start off, one should enter a reasonably large value for the number of buttons in xev, or else some buttons will be prohibited from generating click events and won't be captured by xev. So here's the steps to find out how many buttons your mouse really have:


Choose a reasonably large number (usually the physical count of your mouse buttons plus the scroll wheel up and down), and enter that number in xorg.conf
Use xev to find out what's the largest button number captured. Replace what you had in xorg.conf with this number.

While you could enter more buttons that what your mouse really has, and it'll still work, but you will be using more system resources than what you really need. Since the X server will add hooks to listen to events generated from those extra, non-existent buttons.

endy, you might want to add the following link on xorg.conf mouse options to the guide for reference.
http://www.x.org/X11R6.8.2/doc/mouse5.html#21

prelude, you might want to take a look at the above link. It has a section on zaxismapping with horizontal scrolling. Although from the looks of your xev output, it looks like it won't work, but maybe you can play around with the settings a bit. So, right now you have the tilt wheels doing vertical scrolling as well?

Also, you'll see a "resolution" option documented in the above link. I don't know if this can replace the "logitech applet", but I guess you guys can experiment a bit with this option and see if it makes a difference.

[endy]

No problem! Glad I could contribute! Also, you might want to update the part about the number of buttons to enter in xorg.conf.

Updated, and as your explanation was so good I linked to your post! Thanks again :)

[DancingSun]

Updated, and as your explanation was so good I linked to your post! Thanks again :)
Hmm...I don't see where the link is at? :confused:

[ricesteam]

I just like to say, thanks for a great guide!

However it doesn't work too well with an IBM ThinkPad R31.

When I'm home, I like to plug in a USB Mx700 mouse.

You're tutorial works and everything, but it disables my trackpoint (the little red button that acts as a mouse on these laptops).

Is it possible to have a fully functional Mx700 with trackpoint enabled?

[Mais]

The mx518 supports up to 1600 dpi resolution. Is there anyway to get this working in gnome?

[endy]

Hmm...I don't see where the link is at? :confused:

Sorry I don't know what happened, a forum fart or something? I did add a paragraph but it just disappeared... Well that's fixed now!

Mais, you could see if lmctl (http://freshmeat.net/projects/lmctl/) works but the freshmeat page doesn't look very hopeful quoting only "800cpi". You could also try emailing the author of lmctl and/or the author of logitech_applet (http://freshmeat.net/projects/logitech_applet/). Maybe they know how to get this done or maybe they might be able to update the tools to support the mx518 with your help :)

EDIT: I just found this page, worth a try I suppose: http://www.linux-gamers.net/modules/news/article.php?storyid=761 :)

[DancingSun]

The mx518 supports up to 1600 dpi resolution. Is there anyway to get this working in gnome?
You might want to try adding the resolution (http://www.x.org/X11R6.8.2/doc/mouse5.html#24) option to your xorg.conf. Let us know if that works or not.

[Brando569]

works perfectly on my mx700 for anyone that has one heres my config file:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "usb-0000:00:1d.1-2/input0"
Option "Device" "/dev/input/event3"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"
EndSection

great job!

[candyman963]

OK, I'd like to add a little twist to this. I've got an MX510 set up more or less exactly as this guide says. However, in my Windows installation I have the cruise control buttons bound to page up and page down, which I find much more useful than the actual cruise control. I've tried various settings in .xbindkeysrc, but have had no luck. Anybody have an idea here?

[DancingSun]

OK, I'd like to add a little twist to this. I've got an MX510 set up more or less exactly as this guide says. However, in my Windows installation I have the cruise control buttons bound to page up and page down, which I find much more useful than the actual cruise control. I've tried various settings in .xbindkeysrc, but have had no luck. Anybody have an idea here?
It's likely that when you bind the cruise up and down buttons to page up and down, the scroll wheel will also do page up and down, because both the cruise buttons and the scroll wheel generate the same button events on the MX510. So to X, they are essentially the same buttons.

[nenotnom]

This guide worked perfectly for me a couple of weeks ago, but now I've reinstalled Ubuntu and despite a complete lack of error messages, I can't get it to work.
The thumb buttons on my MX 510 don't do backwards/forwards, but they're changed from the default state ( where the front button is button2 and the back is b1?) so I know I did something.
Here's some info:
-------------------------------
cat /proc/bus/input/devices:
"
I: Bus=0003 Vendor=046d Product=c01d Version=2100
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:02.1-4/input0
H: Handlers=mouse0 event4 ts0
B: EV=f
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103
B: ABS=300 0
"
My x config:
"
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse" Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event4"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection
"
and I did the "Section 2: Side buttons and Nautilus" exactly as it said.
I want to get my thumbbuttons working, does anybody know where I should start looking?

[DancingSun]

This guide worked perfectly for me a couple of weeks ago, but now I've reinstalled Ubuntu and despite a complete lack of error messages, I can't get it to work.
The thumb buttons on my MX 510 don't do backwards/forwards, but they're changed from the default state ( where the front button is button2 and the back is b1?) so I know I did something.
Here's some info:
-------------------------------
cat /proc/bus/input/devices:
"
I: Bus=0003 Vendor=046d Product=c01d Version=2100
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:02.1-4/input0
H: Handlers=mouse0 event4 ts0
B: EV=f
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103
B: ABS=300 0
"
My x config:
"
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse" Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event4"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection
"
and I did the "Section 2: Side buttons and Nautilus" exactly as it said.
I want to get my thumbbuttons working, does anybody know where I should start looking?
Refer to this post on using "xev" to get the button events generated by your mouse:
http://ubuntuforums.org/showpost.php?p=359467&postcount=25
Then, post the button events generated by each of your buttons.

[nenotnom]

I think this is it:
Front thumbbutton:
LeaveNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0xd6, subw 0x0, time 209594, (150,172), root:(228,269),
mode NotifyGrab, detail NotifyAncestor, same_screen YES,
focus NO, state 16
EnterNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0xd6, subw 0x0, time 209810, (150,172), root:(228,269),
mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
focus NO, state 16
KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 4294967254 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Rear:
LeaveNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0xd6, subw 0x0, time 257818, (146,161), root:(224,258),
mode NotifyGrab, detail NotifyAncestor, same_screen YES,
focus NO, state 16
EnterNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0xd6, subw 0x0, time 258002, (146,161), root:(224,258),
mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
focus NO, state 16
KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 4294967254 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

[DancingSun]

No, that's not it...it should look like something on the first post:
ButtonPress event, serial 29, synthetic NO, window 0x3a00001,
root 0x134, subw 0x0, time 10223576, (111,54), root:(126,151),
state 0x0, button 4, same_screen YES
ButtonRelease event, serial 29, synthetic NO, window 0x3a00001,
root 0x134, subw 0x0, time 10223576, (111,54), root:(126,151),
state 0x800, button 4, same_screen YES
Note the bolded text.

[nenotnom]

No, that's not it...it should look like something on the first post:
ButtonPress event, serial 29, synthetic NO, window 0x3a00001,
root 0x134, subw 0x0, time 10223576, (111,54), root:(126,151),
state 0x0, button 4, same_screen YES
ButtonRelease event, serial 29, synthetic NO, window 0x3a00001,
root 0x134, subw 0x0, time 10223576, (111,54), root:(126,151),
state 0x800, button 4, same_screen YES
Note the bolded text.
I have nothing like that when I press either of my thumb buttons, no buttonrelease or number =(
This is after I changed stuff as mentioned in the guide mind you.



When I changed back to default I get this:

Front:

ButtonPress event, serial 26, synthetic NO, window 0x3000001,
root 0xd6, subw 0x0, time 67358, (127,176), root:(205,273),
state 0x10, button 3, same_screen YES

ButtonRelease event, serial 26, synthetic NO, window 0x3000001,
root 0xd6, subw 0x0, time 67468, (127,176), root:(205,273),
state 0x410, button 3, same_screen YES

Rear:

ButtonPress event, serial 26, synthetic NO, window 0x3000001,
root 0xd6, subw 0x0, time 105532, (153,169), root:(231,266),
state 0x10, button 2, same_screen YES

ButtonRelease event, serial 26, synthetic NO, window 0x3000001,
root 0xd6, subw 0x0, time 105652, (153,169), root:(231,266),
state 0x210, button 2, same_screen YES

[DancingSun]

Follow the guide, and DON'T do the button binding section for Nautilus. And see if the mouse still works correctly. Try the side buttons in "xev" and in Firefox. The forward and backward buttons should work in Firefox.

[nenotnom]

I removed "~/.xbindkeysrc" restarted X by ctrl alt backspace, and lo and behold, the keys are now reported as 7 and 6 by xev, 7 being front button. It works in firefox but not nautilus.

[DancingSun]

Well, at least we now know that your xorg.conf is working alright. The key binding part is definitely weird...are you sure your config file was correct? The instructions looked ok, but then again, I've never tried doing keybindings for my mouse...

Try doing the keybindings again.

[nenotnom]

created ~/.xbindkeysrc again

c&p'ed this:

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7

then I ran xbindkeys from console, then I tried the keys in nautilus, didn't work =/

Weirdness!

[DancingSun]

created ~/.xbindkeysrc again
c&p'ed this:
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7
then I ran xbindkeys from console, then I tried the keys in nautilus, didn't work =/
Weirdness!
What about Firefox and xev? Did the bindings kill the buttons altogether?

[nenotnom]

What about Firefox and xev? Did the bindings kill the buttons altogether?

It killed it allright.

[DancingSun]

It killed it allright.
That's odd...I wonder if endy got it working with the key bindings.

I'll try it out this weekend if I have time.

[jaakko]

Thank you, this is a great guide! :D It worked fine with the new version (5.10) too.
edit: I had problems with the configuration of the file .xbindkeysrc because I didn't notice that in

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7

the correct buttons [Left] and [Right] must be in upper case.

edit: I can't write, I meant first letter must be in upper case. Correct buttons are Left and Right. :)

[bob_c_b]

Thank you, this is a great guide! :D It worked fine with the new version (5.10) too.
edit: I had problems with the configuration of the file .xbindkeysrc because I didn't notice that in

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7

the correct buttons [Left] and [Right] must be in upper case.

Yep, that fixed it for me as well, good find.

[nenotnom]

Thank you, this is a great guide! :D It worked fine with the new version (5.10) too.
edit: I had problems with the configuration of the file .xbindkeysrc because I didn't notice that in

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7

the correct buttons [Left] and [Right] must be in upper case.

What do you mean?

[DancingSun]

What do you mean?
It should be "LEFT" and "RIGHT". Not "left" and "right" in the config file.

Edit:
Try using "left" and "right" all caps in brackets. It seems like it will be auto-converted into lowercase in a post.

[nenotnom]

I tried replacing "\[Alt_L]\[left]" with "smooth" and then I used the button on a terminal, and it typed out smooth, so it seems there's something wrong with "\[Alt_L]\[left]" in particular. I didn't get any results by replacing left with LEFT either.

[jaakko]

I tried replacing "\[Alt_L]\[left]" with "smooth" and then I used the button on a terminal, and it typed out smooth, so it seems there's something wrong with "\[Alt_L]\[left]" in particular. I didn't get any results by replacing left with LEFT either.

Try replacing it with Left (and the other one with Right).

[nenotnom]

Try replacing it with Left (and the other one with Right).

I did, and it works now! I totally owe you a cookie =D

[DancingSun]

I did, and it works now! I totally owe you a cookie =D
Hahaha, I can't believe we got stuck on a capitalization issue for so long! See? It's always the little stuff that get you boggled!

[nenotnom]

Yeah, can't believe I didn't try that to begin with. Such a typical solution to a problem that's just too simple to not function correctly.

[Pulse]

First of all, thanks for the guide, it's been a real help.

I've got everything on my mx500 working with my own customizations, except for one very strange problem - the bottom "cruise control" button doesn't work if I turn cruise control off; even pressing it in xev elicits no response. What makes this so strange is that the top cc button does work; it registers as button 10 in xev and works just like any other other button.

If I turn cc on, they both replicate the mousewheel as intended and both can be bound to any key in Windows with no problems, so what gives?

[DancingSun]

First of all, thanks for the guide, it's been a real help.

I've got everything on my mx500 working with my own customizations, except for one very strange problem - the bottom "cruise control" button doesn't work if I turn cruise control off; even pressing it in xev elicits no response. What makes this so strange is that the top cc button does work; it registers as button 10 in xev and works just like any other other button.

If I turn cc on, they both replicate the mousewheel as intended and both can be bound to any key in Windows with no problems, so what gives?
Can you post your xorg.conf? Also, did you do the Xmodmap part of the guide? It's not needed anymore.

[Téragone]

I tried to configure my mx1000 following the guide. But X server crashed at restart. Even the keyboard doesn't work anymore.
I'm on Hoary AMD 64.
Modification to xorg.conf :
#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "CorePointer"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "ImPS/2"
# Option "Emulate3Buttons" "true"
# Option "ZAxisMapping" "4 5"
#EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB RECEIVER"
Option "Dev Phys" "usb-0000:00:10.0-1/input0"
Option "Device" "/dev/input/event2"
Option "Buttons" "12"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "false"
EndSection
in the Xorg log I have this :
(**) Option "Dev Name" "Logitech USB RECEIVER"
(**) Option "Dev Phys" "usb-0000:00:10.0-1/input0"
(EE) Configured Mouse: cannot open input device
(**) Option "Dev Name" "Logitech USB RECEIVER"
(**) Option "Dev Phys" "usb-0000:00:10.0-1/input0"
(EE) Configured Mouse: cannot open input device
No core pointer
Fatal server error:
failed to initialize core devices
cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=402000000 3802078f840d001 f2ffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
H: Handlers=kbd event1
B: EV=40001
B: SND=6
I: Bus=0003 Vendor=046d Product=c50e Version=2500
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:10.0-1/input0
H: Handlers=kbd mouse0 event2 ts0
B: EV=120007
B: KEY=ffff0000 1000000000000 0 0 0
B: REL=103
B: LED=fc00
Any idea ?

[DancingSun]

Check the first 3 pages of this thread. Your "Dev Phys" entry is somehow wrong.

[Téragone]

Thanks for your reply,

I changed it to:

usb-*/input0

Still the same problem

[DancingSun]

Thanks for your reply,

I changed it to:

usb-*/input0

Still the same problem
Try this part, mentioned in the guide:
Note: mx700 users report the name needs to be "Logitech USB Receiver" not "Logitech USB-PS/2 Optical Mouse" like it is for my mx510. Please refer to your output from "cat /proc/bus/input/devices" to be sure. Additionally, iverson0881 found that for the mx700 you can use "/dev/input/ts0" to work. Again check your output from earlier as you may need to change it to "ts1" or "ts2" etc... You can see iverson0881's post here.

From the errors you're getting, I think you have the same problem as GoA. He somehow got it working. Although I'm not sure which directions he followed, but I believe it's the one above. If that doesn't work, try PMing him and ask him about the details. I, unfortunately, don't have access to a wireless Logitech mouse, so I can't really help much besides pointing you to resources that might be helpful.

[Téragone]

Thanks again,

I found it,

It seem that Dev Name is case sensitive, I changed :

Logitech USB RECEIVER

to

Logitech USB Receiver

(cut and paste error :smile: )

and all is almost ok. Now forward and backward work in Firefox.

The tilt left and right with the wheel doesn't work. That buttons are not trapped by xev.

[DancingSun]

Hahaha, another capitalization error! And I just commented on the last one too! Oh the irony!

[brj]

is it also possible to program the behaviour of the buttons for all applications ?

i'd like to have a double-click when i click the scroll-wheel or the thumb-buttons .

jakob

[tick]

I have a MX 510. My problem ist that when I set "ZAxisMapping" "4 5" the wheel works perfectly, small buttons too, but the side buttons dont respond, not even in xev.

When I set "ZAxisMapping" to "7 8" all buttons are shown in xev correctly:
1 lmb
2 mmb
3 rmb
4 side front
5 side rear
6 top
7 scroll up / small button up
8 scroll down /small button down

But the side buttons are mapped to scrolling up/down and mousewheel up/down is set to leftclick/nothing.

Tick



Identifier "MX510"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"


I: Bus=0003 Vendor=046d Product=c01d Version=2100
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:10.0-1/input0
H: Handlers=mouse0 event1
B: EV=7

B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103

[DancingSun]

I have a MX 510. My problem ist that when I set "ZAxisMapping" "4 5" the wheel works perfectly, small buttons too, but the side buttons dont respond, not even in xev.

When I set "ZAxisMapping" to "7 8" all buttons are shown in xev correctly:
1 lmb
2 mmb
3 rmb
4 side front
5 side rear
6 top
7 scroll up / small button up
8 scroll down /small button down

But the side buttons are mapped to scrolling up/down and mousewheel up/down is set to leftclick/nothing.

Tick



Identifier "MX510"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"


I: Bus=0003 Vendor=046d Product=c01d Version=2100
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:10.0-1/input0
H: Handlers=mouse0 event1
B: EV=7

B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103

Did you happen to have a xmodmap that remaps those buttons?

[endy]

Also, the mx510 has ten buttons, not eight. Here they are (in no particular order):


LMB
MMB
RMB
Scroll Up
Scroll Down
Scroll Up "Cruise Control" button
Scroll Down "Cruise Control" button
Side Forward
Side Back
"Alt-Tab" Button

...even though the "Cruise Control" buttons duplicate the scroll up and down. Hope this helps!

[DancingSun]

Also, the mx510 has ten buttons, not eight. Here they are (in no particular order):


LMB
MMB
RMB
Scroll Up
Scroll Down
Scroll Up "Cruise Control" button
Scroll Down "Cruise Control" button
Side Forward
Side Back
"Alt-Tab" Button

...even though the "Cruise Control" buttons duplicate the scroll up and down. Hope this helps!
Well, I put "8" buttons on my xorg.conf and it works fine. The correct number to put in is the highest button event number X receives. So, basically enter the highest button event number that you see on xev. You can put more, and your mouse will still work just fine. But you'll be telling X to hog resources for button events that will never be generated.

[Pulse]

Can you post your xorg.conf? Also, did you do the Xmodmap part of the guide? It's not needed anymore.
Sorry I took so long to reply, I didn't have access to a computer for a few days there.

Here's the relevant part of my xorg.conf:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "B16_b_02 USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:02.0-2/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "11"
Option "ZAxisMapping" "4 5"
EndSection

And no, I didn't do the Xmodmap thing.

Edit: I suppose now might be a good time to mention that I'm using Breezy. I found this thread with the search function and didn't notice that it was in a forum dedicated to Hoary until after I had already posted. It shouldn't make any difference in this case anyway.

[DancingSun]

Sorry I took so long to reply, I didn't have access to a computer for a few days there.

Here's the relevant part of my xorg.conf:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "B16_b_02 USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:02.0-2/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "11"
Option "ZAxisMapping" "4 5"
EndSection

And no, I didn't do the Xmodmap thing.

Edit: I suppose now might be a good time to mention that I'm using Breezy. I found this thread with the search function and didn't notice that it was in a forum dedicated to Hoary until after I had already posted. It shouldn't make any difference in this case anyway.
Hmm...you mentioned you did your own customizations, what are those? Also by turning cruise control on and off, do you mean the logitech applet? I didn't do the applet part myself and things are working just fine for me. Could you disable the applet, and see if that helps?

Do you have any xmodmap file on the system? How many physical buttons does the mx500 have? Could you list them out and the corresponding button event that they generate? I think generally the scroll buttons should generate button events 4 and 5. If not, something might have remapped the button configurations.

[Pulse]

I just tried disabling the applet and it didn't work... Well, it might have worked, but cruise control is on and the logitech applet seems to be the only way to turn it off. I disable cruise control by using the command logitech_applet -s 800 as opposed to logitech_applet -s 800 -e

By "With my own customizations" I mean that my xbindkeys config file is as follows: "/usr/X11R6/bin/xvkbd -xsendevent -text "\[Page_Down]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Page_Up]""
m:0x0 + b:7
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Delete]""
m:0x0 + b:8
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Home]""
m:0x0 + b:10
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[End]""
m:0x0 + b:9

The mx500 is identical to the mx510 other than the paint job and the maximum resolution, but I'll get the button events in a few minutes anyway.

Edit: Left mouse button is button 1, middle is button 2, right is button 3, mwheelup is 4, mwheeldown is 5, the forward side button is 6, backward is 7, the button in the middle of the mouse (I forget what it's called... the one that starts Logitech's crappy alt-tab replacement in Windows) is 8, the forward cruise control button is 10 (shouldn't it be 9?) and the backward cc button is nothing.

[DancingSun]

I just tried disabling the applet and it didn't work... Well, it might have worked, but cruise control is on and the logitech applet seems to be the only way to turn it off. I disable cruise control by using the command logitech_applet -s 800 as opposed to logitech_applet -s 800 -e

By "With my own customizations" I mean that my xbindkeys config file is as follows: "/usr/X11R6/bin/xvkbd -xsendevent -text "\[Page_Down]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Page_Up]""
m:0x0 + b:7
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Delete]""
m:0x0 + b:8
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Home]""
m:0x0 + b:10
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[End]""
m:0x0 + b:9

The mx500 is identical to the mx510 other than the paint job and the maximum resolution, but I'll get the button events in a few minutes anyway.

Edit: Left mouse button is button 1, middle is button 2, right is button 3, mwheelup is 4, mwheeldown is 5, the forward side button is 6, backward is 7, the button in the middle of the mouse (I forget what it's called... the one that starts Logitech's crappy alt-tab replacement in Windows) is 8, the forward cruise control button is 10 (shouldn't it be 9?) and the backward cc button is nothing.
OK, here's the weird part, on my MX510 the cruise control buttons generate button events 4 and 5 (same as scroll wheel). And the largest button event number generated is 8. Try disabling all your key bindings and see if the mouse generates the correct button events.

[Pulse]

OK, here's the weird part, on my MX510 the cruise control buttons generate button events 4 and 5 (same as scroll wheel). And the largest button event number generated is 8. Try disabling all your key bindings and see if the mouse generates the correct button events.
This is because you have cruise control enabled. If I turn it on, the cc buttons generate button events 4 and 5, just like yours. And yes, I've tried disabling the key bindings, both by having a blank config file and turning xbindkeys off altogether.

[DancingSun]

This is because you have cruise control enabled. If I turn it on, the cc buttons generate button events 4 and 5, just like yours. And yes, I've tried disabling the key bindings, both by having a blank config file and turning xbindkeys off altogether.
Try increasing the number of buttons setting in xorg.conf to something larger, like 15. Then see if xev can capture all of the buttons or not. When doing this, try not to have any of the keybindings on, and make sure no other programs are remapping the buttons.

[endy]

I'd just like to say thanks to DancingSun for helping out so much on this thread, I'm very busy right now so I can't read the forums as much as I would like. Thanks alot!

[DancingSun]

I'd just like to say thanks to DancingSun for helping out so much on this thread, I'm very busy right now so I can't read the forums as much as I would like. Thanks alot!
Hey, not a problem! That's what a community is all about!:)

[zenrox]

works for the logitech lx 500 wireless desktop
and the mouse only has the std buttons on it +1 thats it
works great tho the logitech_applet works too
main reasion why i did this was to get the better res for my mouse:p

[Brando569]

any idea on how to get the (extra) buttons to work on the logitech elite keyboard with a media player (mainly play/pause,stop,skip back and skip forward)

[BLTicklemonster]

I've got an mx 310. My keys for forward and back are 6 and 7. I followed the instructions exactly, and they worked great! Until I set xbindkeys in start programs. I restarted, and now not only do they not work, but it took out another program that was in start up that was working fine before. It was order 50, xbindkeys was 51.

I've gone through twice and it does the same each time.

Not sure where to go from here, but I'll show you what I did:

#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "CorePointer"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "ImPS/2"
# Option "Emulate3Buttons" "true"
# Option "ZAxisMapping" "4 5"
#EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:02.1-2/input0" (tried both ways)
Option "Device" "/dev/input/event2"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"
EndSection

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7


What do I do now?

Huh, I wonder what changing this
Option "Emulate3Buttons" "true"

to this
Option "Emulate8Buttons" "true"

and leaving
"Buttons" "8"
out would do?

Oh, might be perhaps... my scroll will push down, I'm counting that as a button, so

not in order,

1. right click
2. left click
3. scroll up
4. scroll down
5. forward
6. back
7. wierd little button behind the scroll that I never figured out
8. pressing the scroll button down

Now you said that you could enter a higher number and it would be okay, but would use extra resources so I don't think counting number 8 should be a problem.

Suggestions?

[DancingSun]

I've got an mx 310. My keys for forward and back are 6 and 7. I followed the instructions exactly, and they worked great! Until I set xbindkeys in start programs. I restarted, and now not only do they not work, but it took out another program that was in start up that was working fine before. It was order 50, xbindkeys was 51.

I've gone through twice and it does the same each time.

Not sure where to go from here, but I'll show you what I did:

#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "CorePointer"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "ImPS/2"
# Option "Emulate3Buttons" "true"
# Option "ZAxisMapping" "4 5"
#EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:02.1-2/input0" (tried both ways)
Option "Device" "/dev/input/event2"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"
EndSection

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7


What do I do now?

Huh, I wonder what changing this
Option "Emulate3Buttons" "true"

to this
Option "Emulate8Buttons" "true"

and leaving
"Buttons" "8"
out would do?

Oh, might be perhaps... my scroll will push down, I'm counting that as a button, so

not in order,

1. right click
2. left click
3. scroll up
4. scroll down
5. forward
6. back
7. wierd little button behind the scroll that I never figured out
8. pressing the scroll button down

Now you said that you could enter a higher number and it would be okay, but would use extra resources so I don't think counting number 8 should be a problem.

Suggestions?
Ok, you said everything work fine until you did the key bindings. That means the problem lies in the key bindings.

First, revert your xorg.conf to what it was like before you did the key bindings. You might want to disable the key bindings so you can make sure the mouse is working correctly.

Second, in the xbindkeys file, replace "left" and "right" with "Left" and "Right". A few posts ago, a forumer had this problem, and finally found out it was due to the capitalization. The reason that it is all in lowercase in the guide is actually a bug of this forum software. Try typing "Right" in "[]" (brackets), you'll see it being coverted to all lowercase if you preview or submit the post.

[BLTicklemonster]

Totall oddity (2005 A Linux Oddity). Left the machine on last night, got up, got myself a cup o' joe, sat down to see if I could find out how to burn a cd, navigating the site, and automatically hit the back button like I always do, and it went back. .... um.

So I'll keep an eye on it, and try what you said. Thanks.


*edit:

Ooookay, restarted, the mouse buttons work fine.


**edit:

Alllrighty then. Just finished out the entire thing. got the applet going. My mouse is now a little speed demon. Thank you thank you thank you. MrBond watch out, Here I Come. :razz:

[ember]

Hmm ... I tried this howto and my thumb-buttons just do not seem to work. They do not even send events (I have a Logitech MX310).

The relevant configuration part is:
Section "InputDevice"
Identifier "Logitech MX310"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "PS2++ Logitech MX Mouse"
Option "Dev Phys" "isa*/input0"
Option "Device" "/dev/input/event1"
Option "Button" "7"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "false"
EndSection

Any ideas?

[BLTicklemonster]

Hmm ... I tried this howto and my thumb-buttons just do not seem to work. They do not even send events (I have a Logitech MX310).

The relevant configuration part is:
Section "InputDevice"
Identifier "Logitech MX310"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "PS2++ Logitech MX Mouse"
Option "Dev Phys" "isa*/input0"
Option "Device" "/dev/input/event1"
Option "Button" "7"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "false"
EndSection

Any ideas?


Mine is working perfectly now. Try my settings, as we have the same mouse.

[jadugarr]

I tried this guide to setup my mx510 mouse in Kubuntu Breezy. After changing the xorg.conf file I couldn't start X and had no relevant errors, and had to revert to my old config.
Here is what i tried:
#Section "InputDevice"
#Identifier "Configured Mouse"
#Driver "mouse"
#Option "CorePointer"
#Option "Device" "/dev/input/mice"
#Option "Protocol" "ExplorerPS/2"
#Option "Buttons" "7"
#Option "ZAxisMapping" "6 7"
#EndSection


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection

Anyone have any suggestions?

[DancingSun]

I tried this guide to setup my mx510 mouse in Kubuntu Breezy. After changing the xorg.conf file I couldn't start X and had no relevant errors, and had to revert to my old config.
Here is what i tried:
#Section "InputDevice"
#Identifier "Configured Mouse"
#Driver "mouse"
#Option "CorePointer"
#Option "Device" "/dev/input/mice"
#Option "Protocol" "ExplorerPS/2"
#Option "Buttons" "7"
#Option "ZAxisMapping" "6 7"
#EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection

Anyone have any suggestions?
Check your xorg log under /var/log, and see if there's any error output there.

[anonOmus]

I cant seem to get the libXaw3d, from any of the sources including the hoary disto servers(im running breezy) any ideas?

[BLTicklemonster]

I had to do this all again, thanks to me messing up xserver. I didn't even have to set the extra buttons. It did it for me already this time. I did notice that some of the information I culled initially was slightly different this time, which I thought was odd.

But hey, it works. thanks!

[.Danny]

I've done all the steps now and everything works apart from forward/backward in nautilus/firefox. Which is why I did it in the first place.:(

I've got a Logitech MX510, anyone has any ideas what I did wrong?

[DancingSun]

I've done all the steps now and everything works apart from forward/backward in nautilus/firefox. Which is why I did it in the first place.:(

I've got a Logitech MX510, anyone has any ideas what I did wrong?
Without additional info, nope! Does xev show any events generated by the thumb buttons? Let us know if there are any step that you aren't sure of, or think where it might be the problem.

[.Danny]

Nope I've done everything that was there. Didn't get any errors or anything wrong.

This is the xev output for the 2 buttons.

LeaveNotify event, serial 29, synthetic NO, window 0x3a00001,
root 0x133, subw 0x0, time 12312774, (168,177), root:(186,249),
mode NotifyGrab, detail NotifyAncestor, same_screen YES,
focus NO, state 0

EnterNotify event, serial 29, synthetic NO, window 0x3a00001,
root 0x133, subw 0x0, time 12313094, (168,177), root:(186,249),
mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
focus NO, state 0

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 51 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

LeaveNotify event, serial 29, synthetic NO, window 0x3a00001,
root 0x133, subw 0x0, time 12314502, (168,177), root:(186,249),
mode NotifyGrab, detail NotifyAncestor, same_screen YES,
focus NO, state 0

EnterNotify event, serial 29, synthetic NO, window 0x3a00001,
root 0x133, subw 0x0, time 12314830, (168,177), root:(186,249),
mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
focus NO, state 0

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 51 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

[DancingSun]

Nope I've done everything that was there. Didn't get any errors or anything wrong.

This is the xev output for the 2 buttons.

LeaveNotify event, serial 29, synthetic NO, window 0x3a00001,
root 0x133, subw 0x0, time 12312774, (168,177), root:(186,249),
mode NotifyGrab, detail NotifyAncestor, same_screen YES,
focus NO, state 0

EnterNotify event, serial 29, synthetic NO, window 0x3a00001,
root 0x133, subw 0x0, time 12313094, (168,177), root:(186,249),
mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
focus NO, state 0

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 51 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

LeaveNotify event, serial 29, synthetic NO, window 0x3a00001,
root 0x133, subw 0x0, time 12314502, (168,177), root:(186,249),
mode NotifyGrab, detail NotifyAncestor, same_screen YES,
focus NO, state 0

EnterNotify event, serial 29, synthetic NO, window 0x3a00001,
root 0x133, subw 0x0, time 12314830, (168,177), root:(186,249),
mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
focus NO, state 0

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 51 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Ok, it doesn't look like it captured any button events. Did you do the key bindings part? If so, in the xbindkeys file, replace "left" and "right" with "Left" and "Right". A few posts ago, a forumer had this problem, and finally found out it was due to the capitalization. The reason that it is all in lowercase in the guide is actually a bug of this forum software. Try typing "Right" in "[]" (brackets), you'll see it being coverted to all lowercase if you preview or submit the post.

[.Danny]

Nope still doesn't work, altough the xev output changed.

LeaveNotify event, serial 29, synthetic NO, window 0x3400001,
root 0x133, subw 0x0, time 649244, (177,140), root:(261,280),
mode NotifyGrab, detail NotifyAncestor, same_screen YES,
focus YES, state 0

KeyPress event, serial 29, synthetic YES, window 0x3400001,
root 0x133, subw 0x0, time 0, (1,1), root:(1,1),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 29, synthetic YES, window 0x3400001,
root 0x133, subw 0x0, time 0, (1,1), root:(1,1),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:

EnterNotify event, serial 29, synthetic NO, window 0x3400001,
root 0x133, subw 0x0, time 650012, (177,140), root:(261,280),
mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
focus YES, state 0

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 51 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

LeaveNotify event, serial 29, synthetic NO, window 0x3400001,
root 0x133, subw 0x0, time 650748, (177,140), root:(261,280),
mode NotifyGrab, detail NotifyAncestor, same_screen YES,
focus YES, state 0

KeyPress event, serial 29, synthetic YES, window 0x3400001,
root 0x133, subw 0x0, time 0, (1,1), root:(1,1),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 29, synthetic YES, window 0x3400001,
root 0x133, subw 0x0, time 0, (1,1), root:(1,1),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:

EnterNotify event, serial 29, synthetic NO, window 0x3400001,
root 0x133, subw 0x0, time 651452, (177,140), root:(261,280),
mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
focus YES, state 0

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 51 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



This is my xbindkeysrc..

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7

[edit with big Left and Right that is..]

[DancingSun]

I still don't see any button events in your xev output. Basically, if you point in the xev window, without moving the mouse, click on the thumb buttons, and no button events are outputted on the terminal (button event captures are shown in the guide), that means the button is not working.

Try disabling the Logitech applet, restart, and see if the mouse works correctly. If it does, something is wrong with the applet. If not, try the following.

Try disabling the xbindkey, restart, and see if the mouse performs correctly. If the mouse performs correctly, then something must be wrong with the xbindkey configuration. If not, that means most likely your xorg.conf is configured incorrectly. Make sure you are entering the correct information for your mouse.

[.Danny]

I disabled xbindkey and the buttons show correctly in xev now. The question is what is a good whats wrong with my .xbindkeysrc then?

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7

[edit] I just noticed that with xbindkey disabled it's actually working in Firefox now. It would be nice to have it Nautilus as well but Firefox is the main thing why I wanted it. So I guess things are ok. :D

[DancingSun]

I disabled xbindkey and the buttons show correctly in xev now. The question is what is a good whats wrong with my .xbindkeysrc then?

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7

[edit] I just noticed that with xbindkey disabled it's actually working in Firefox now. It would be nice to have it Nautilus as well but Firefox is the main thing why I wanted it. So I guess things are ok. :D
What button event numbers did the thumb buttons generate?

[.Danny]

What button event numbers did the thumb buttons generate?
6 and 7.

[BLTicklemonster]

Hey, do this:

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:

and then see if the buttons don't automagically start working.

If not, delete it all and save it blank and try it that way.

It worked for me the second time around. I can't explain it, because the first time they worked with the numbers entered. I don't remember if it was no numbers or blank which worked for me, and I'm not in front of my machine, but try it and see if it works for you.

[souled]

I have the same problem as Lord Death. In xev I get buttons 6 and 7 as the thumbs, but when i load xbindkeys I get that weird output for the thumb buttons. When I set the mouse buttons to "4 5" the thumb buttons didn' do antyhing, so I changed it to "9 10" and did the xmodmap thing and now the thumb buttons work. Back and forward work for FF, but xbindkeys seem to kill the thumb buttons

Running Breezy with the mx700.

[DancingSun]

I have the same problem as Lord Death. In xev I get buttons 6 and 7 as the thumbs, but when i load xbindkeys I get that weird output for the thumb buttons. When I set the mouse buttons to "4 5" the thumb buttons didn' do antyhing, so I changed it to "9 10" and did the xmodmap thing and now the thumb buttons work. Back and forward work for FF, but xbindkeys seem to kill the thumb buttons

Running Breezy with the mx700.
I'm assuming when you said setting the mouse buttons to "4 5" you actually meant setting the scroll buttons to "4 5". And what's the "weird output for thumb buttons" you're getting?

Without any xmodmap and xbindkey, what butten event numbers did xev report for your scroll wheel?

Also, for reference, you might want to search this thread, I remember some users of MX700 posting their xorg.conf settings.

Generally, I would not suggest the use of xvkbd + xbindkeys to get nautilus working with the thumb buttons. Xbindkeys just send shell commands whenever you press the thumb buttons. Those commands are set in your xbinkey config file, in this case, we tell it to send a command that executes xvbd (the X virtual keyboard) program to input Alt+Left and Alt+Right. That's just a work around, it doesn't change the fact that nautilus does not support the thumb buttons natively. The best solution would be to request a feature for nautilus to support additional button events.

[prelude]

say.. anyone know of a repo that has the xvkbd package for breezy?

for some reason apt-get claims it cant find that package and without it Im kinda stuck withouth tumb buttons.. ;)

[DancingSun]

say.. anyone know of a repo that has the xvkbd package for breezy?

for some reason apt-get claims it cant find that package and without it Im kinda stuck withouth tumb buttons.. ;)
The thumb buttons work without doing any key bindings (or more accurately, command bindings). After you finished the first part of the guide (xorg.conf setup), the thumb buttons should start working. You should be able to see them generate button events in xev, and work in Firefox, and other programs that support thumb buttons.

[anonOmus]

Oopsie!

[Donza]

Ok.. this doesn't work on my laptop. If I try to boot without Logitech mouse plugged in the X-server cannot start because it can't for some reason find my touchpad anymore. With Logitech plugged in both my mouse and touchpad works fine.
My xorg.conf:
#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "CorePointer"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "ImPS/2"
# Option "Emulate3Buttons" "true"
# Option "ZAxisMapping" "4 5"
#EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:1d.1-1/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection

[Sheytan]

The mx518 supports up to 1600 dpi resolution. Is there anyway to get this working in gnome?

I think it already works when you push the + and - button on the mouse pointer goes faster or slower

[jacknel]

hey guys, hope i haven't missed what i'm about to ask...

but ive been using ubuntu for the last few days now and things are running pretty well...

just wandering though in regards to the MXDUO - has anyone been able to get all the buttons to work?

i have followed this guide

http://docs.tenshu.net/Logitech-MX-Duo-mini-HOWTO/

and have got scroll and side buttons to work - what DOESNT work is the 3 small buttons (1 above and 2 below scroll wheell).

Also is there a way to do AUTO scroll for the middle mouse button like in windows?

thx

[DancingSun]

hey guys, hope i haven't missed what i'm about to ask...

but ive been using ubuntu for the last few days now and things are running pretty well...

just wandering though in regards to the MXDUO - has anyone been able to get all the buttons to work?

i have followed this guide

http://docs.tenshu.net/Logitech-MX-Duo-mini-HOWTO/

and have got scroll and side buttons to work - what DOESNT work is the 3 small buttons (1 above and 2 below scroll wheell).

Also is there a way to do AUTO scroll for the middle mouse button like in windows?

thx
Well, I have a MX510 and all of my buttons work. Although I used the guide in linux-gamers.net, it's basically the same as the first part of the guide posted here. Actually, with all the forumer contributions, I think the guide here is more accurate and informative than the one posted on linux-gamers.net.

On my mouse, the cruise buttons are basically recognized as the scroll wheel. And the application switch button works as well, if you use xev (refer to the guide) you can see it generate button events, and I can use it in games to bind it to certain commands.

Auto scroll will work in Firefox if you enable it in Firefox. Go to the menu Edit -> Preferences -> Advanced. Under "Browsing" category check "Use autoscrolling".

[jacknel]

thx for the DancingSun, autoscroll is cool - can u tell me how i might be able to make that a global thing? like for text and such as well...?


I gotta say - I haven't used XP at all today - my only concern about making the switch is outlook on XP, hate the task of learning how to Export/import my messages and such..

Secondly...

any idea how i can do the following - ?

change the top scroll button (09) to Alt+F4, lower scroll button (10) to Ctrl+W and well u get the idea... i read stuff here

http://hocwp.free.fr/xbindkeys/
http://homepage3.nifty.com/tsato/xvkbd/

but don't really have much of an idea...

thx again

[DancingSun]

thx for the DancingSun, autoscroll is cool - can u tell me how i might be able to make that a global thing? like for text and such as well...?
Auto-scroll on works if the application supports it. I remember that's the way it works in Win2K as well. I don't know if any other application that supports auto scroll, but then again, I'm a recent Linux convert, so my experience is limited as well.

I gotta say - I haven't used XP at all today - my only concern about making the switch is outlook on XP, hate the task of learning how to Export/import my messages and such..
I don't use outlook, I just use my web mail, so can't help you there. But you should read some documentation on Evolution. It should be able to import mail from Outlook, as Evolution is made to look and work like Outlook, so that it can be its replacement on Linux.

Secondly...

any idea how i can do the following - ?

change the top scroll button (09) to Alt+F4, lower scroll button (10) to Ctrl+W and well u get the idea... i read stuff here

http://hocwp.free.fr/xbindkeys/
http://homepage3.nifty.com/tsato/xvkbd/

but don't really have much of an idea...

thx again

Well, like I said before, on my Logitech MX510, the button events generated by the cruise buttons are the same as the butten events generated by the scroll wheel. Which means the X.org server (the windowing system) will recognize the cruise up button as the scroll up action, and the cruise down button as the scroll down action.

That means, if I bind the cruise buttons to some command, the scroll wheel actions will also be bind to those same commands. Assuming your mouse works the same way as mine, I don't think you'll want that to happen.

[jacknel]

oh i get it now.... i just checked events thing and you're kinda right... EG my scroll is 4 and 5 i think and my top button is 4 then when u release it's10... odd....


any idea how i can use those tools i posted to change the bottom one (not sure abt the 510, but the 700 has another button below the one below the scroll which is used to select apps in windows)

[DancingSun]

oh i get it now.... i just checked events thing and you're kinda right... EG my scroll is 4 and 5 i think and my top button is 4 then when u release it's10... odd....


any idea how i can use those tools i posted to change the bottom one (not sure abt the 510, but the 700 has another button below the one below the scroll which is used to select apps in windows)
Well, I don't use xbindkey and xvkbd at all, I think when I used it last time it gave me some unexpected results. Can't quite remember the details.

But if you look at the guide in this thread, you'll see the instructions where it teaches you how to bind Alt+Left and Alt+Right keystrokes to the thumb buttons. Similarly, after you get some basic understanding on how to assign the keystrokes, you could just change the button that trigger the commands and the commands itself to whatever you desire.

For example, the guide tells you to assigned button 6 and 7, in the xbindkey configuration file it appears that "b:6" and "b:7" are references to those buttons. I believe that the button numbers follow the butten event numbers that those buttons generate. So, if I'm correct, you should be able to assign button 10 (since that's the button event number generated when you release the cruise up button, this doesn't happen on my mouse however, both press and release all generates button 4 events) to some other keystroke combinations. To assign the switch application button, just assign the button event number that it generates to the corresponding command you want to invoke. On my mouse, that would be button 8.

There's catch with all this button binding though, I think you cannot specify which programs in which certain bindings will work in. So that means whatever program you're working with, when you press those binded buttons, the associated commands will execute. This poses a problem when I want to map the extra buttons to in-game commands when I play my favorate computer games. For example, if I mapped Alt+F4 to my switch application button, when I try to map that button to some other commands in a game, it will type in the keystrokes of Alt+F4 instead of indicating that the command is mapped to button 8.

[humina]

I have a logitech g5 laser mouse. I have two problems. The first is that my mouse can go up to 2000 dpi. Id there any way to get past the 800 dpi limit? Also xev gives buttons 4 and 5 to both my scroll wheel and my tilt wheel. Any way to separate them?

[Doc.Caliban]

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7

Great How To, thanks!

What would the Page Up and Page Down equivelents to "\[Alt_L]\[Left]" and "\[Alt_L]\[Right]" be?

-Doc

[Doc.Caliban]

Great How To, thanks!

What would the Page Up and Page Down equivelents to "\[Alt_L]\[Left]" and "\[Alt_L]\[Right]" be?

-Doc


Got it. Here is my config file set up the way I like it. Button 8 is the bottom button in the wheel area.


"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Page_Down]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Page_Up]""
m:0x0 + b:7
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Home]""
m:0x0 + b:8


Thanks again for the great guide!

-Doc

[Tomas_B]

I've got the MX1000 and I've had some problems getting it to work.

First of all : Not using xmodmap and just setting "ZAxisMapping" "4 5" does NOT work with the MX1000 (at least not for me)

Second : After setting the ~/.xmodmap file as I wanted it nothing happened. Found out that xvkbd wasn't in the path by default !

Now it works in both Firefox and Nautilus !! So I thought I would post some of my config for other MX1000 owners to see :

/etc/X11/xorg.conf :

Section "InputDevice"
Identifier "MX1000"
Driver "mouse"
Option "CorePointer"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB RECEIVER"
Option "Buttons" "12"
Option "ZAxisMapping" "11 12 10 9"
Option "Resolution" "800"
Option "Emulate3Buttons" "no"
EndSection


/etc/gdm/PostLogin/Default

xmodmap -e "pointer = 1 2 3 6 7 8 11 12 9 10 4 5"


~/.gnomerc

# Lets start xbindkeys
xbindkeys


~/.xbindkeys

# Backward and Forward buttons
"xvkbd -text "\[Alt_L]\[Left]""
m:0x10 + b:6
"xvkbd -text "\[Alt_L]\[Right]""
m:0x10 + b:7

# Application-Switch button
# A-Tab doesn't work
# Use it as another Forward for now
"xvkbd -text "\[Alt_L]\[Right]""
m:0x10 + b:8


Thats it !!

Note : With xbindkeys running it seems like the Alt + Left combo is activated just a little too long for Firefox because FF keeps "scrolling" back through the history of webpages you have visited in the past sometimes. "killall xbindkeys" solves that problem, but then it won't work in Nautilus.

[Rev. Nathan]

Say, this worked out greatly! Sort of. Umm... for some odd reason I didn't have to install xvkbd and xbindkeys, and the back and forward buttons worked. However, I have another problem; the middle-click 'scroller' doesn't show up. That little graphic circle that comes on and helps you coast along webpages. Any idea as to what I can do to activate it?

[DancingSun]

Say, this worked out greatly! Sort of. Umm... for some odd reason I didn't have to install xvkbd and xbindkeys, and the back and forward buttons worked. However, I have another problem; the middle-click 'scroller' doesn't show up. That little graphic circle that comes on and helps you coast along webpages. Any idea as to what I can do to activate it?
Please refer to this (http://ubuntuforums.org/showpost.php?p=453371&postcount=111) post.

[Rev. Nathan]

Please refer to this (http://ubuntuforums.org/showpost.php?p=453371&postcount=111) post.
Aww yes! Thank very much sir.

[jonyo]

I have a logitech g5 laser mouse. I have two problems. The first is that my mouse can go up to 2000 dpi. Id there any way to get past the 800 dpi limit? Also xev gives buttons 4 and 5 to both my scroll wheel and my tilt wheel. Any way to separate them?

I have the MX 1000, and was having the same issue. I found out, if you comment out the ZAxisMapping part, and put 15 for the buttons, then xev will show the tilt left and right, and the scroll up and down not at all. So then I changed ZAxisMapping to "4 5 10 11" to see what happens, now scrolling uses 4 and 5, and tilting uses 9 and 10.

So with these settings:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "usb-0000:00:02.0-1/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "12"
Option "ZAxisMapping" "4 5 9 10"
EndSection

result in this mapping:
Left Button = 1
Middle = 2
Right = 3
Scroll up = 4
Scroll down = 5
cruise up = 4
cruise down = 5
Back Thumb Button = 6
Forward Thumb Button = 7
Change App button = 8
Tilt Right= 9
Tilt Left = 10

So now I can scroll up and down, middle click, go back and forward in firefox, but I can't figure out how to change apps or get the tilt to make it go to the left and right...

I tried using the map keys thing to change aps, but all that did for the app switcher is send alt tab to the window, not to the windows manager, so the actual active window ended up having a tab entered. Is there a way to make the system interpret the keystroke, and not the focused window?

I don't know where to begin to figure out the tilt button mapping... Like I said it is recognizing it seperately from the scroll up and down, but button 9 and 10 don't get translated into scrolling left and right, and I don't know how to get it to. The obvious way is to map it to left and right keys, but it seems there should be a better way to do it?

[DancingSun]

I have the MX 1000, and was having the same issue. I found out, if you comment out the ZAxisMapping part, and put 15 for the buttons, then xev will show the tilt left and right, and the scroll up and down not at all. So then I changed ZAxisMapping to "4 5 10 11" to see what happens, now scrolling uses 4 and 5, and tilting uses 9 and 10.

So with these settings:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "usb-0000:00:02.0-1/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "12"
Option "ZAxisMapping" "4 5 9 10"
EndSection

result in this mapping:
Left Button = 1
Middle = 2
Right = 3
Scroll up = 4
Scroll down = 5
cruise up = 4
cruise down = 5
Back Thumb Button = 6
Forward Thumb Button = 7
Change App button = 8
Tilt Right= 9
Tilt Left = 10

So now I can scroll up and down, middle click, go back and forward in firefox, but I can't figure out how to change apps or get the tilt to make it go to the left and right...

I tried using the map keys thing to change aps, but all that did for the app switcher is send alt tab to the window, not to the windows manager, so the actual active window ended up having a tab entered. Is there a way to make the system interpret the keystroke, and not the focused window?

I don't know where to begin to figure out the tilt button mapping... Like I said it is recognizing it seperately from the scroll up and down, but button 9 and 10 don't get translated into scrolling left and right, and I don't know how to get it to. The obvious way is to map it to left and right keys, but it seems there should be a better way to do it?
In reguards to mapping the tilt buttons, have you tried just mapping it to "Left" and "Right" keystrokes?

[jonyo]

In reguards to mapping the tilt buttons, have you tried just mapping it to "Left" and "Right" keystrokes?

I've already tried it, and it works ok. I was just wondering if there was a way to do it without mapping it to keystrokes, I'd rather do it the "proper" way if such a way exists...

About the application switching... after thinking about it I remember reading something mentioned on these forums somewhere, but now I can't find it. Anyone know of a howto somewhere that says how to set up app switching?

UPDATE: I was playing with it some more, and I set the number of buttons to 20... Now when tilt right, on key release it says button 120... How is it possible that it's reporting button 120 if my max is 20? By the way, my cruise up and down do button 11 and 12 on key release... I didn't mention that before.

[souled]

Hmmm... When I run xbindkeys, button 6 and 7 stop working. Here is the output from xev when xbindkeys is running:

MotionNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 635499, (52,52), root:(56,121),
state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 635507, (53,52), root:(57,121),
state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 635515, (65,52), root:(69,121),
state 0x10, is_hint 0, same_screen YES

EnterNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x0, time 635523, (75,54), root:(79,123),
mode NotifyNormal, detail NotifyInferior, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 72 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

And

LeaveNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 670473, (62,62), root:(895,229),
mode NotifyGrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeyPress event, serial 29, synthetic YES, window 0x2c00001,
root 0x48, subw 0x0, time 0, (1,1), root:(1,1),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 29, synthetic YES, window 0x2c00001,
root 0x48, subw 0x0, time 0, (1,1), root:(1,1),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:

EnterNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 671097, (62,62), root:(895,229),
mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 72 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

For the other button.

However, when xbindkeys is not running, buttons 6 and 7 work. Here is the output of xev when xbindkeys is not running:

KeymapNotify event, serial 30, synthetic NO, window 0x0,
keys: 72 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 761612, (33,42), root:(866,209),
state 0x10, button 6, same_screen YES

LeaveNotify event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x0, time 761612, (33,42), root:(866,209),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

ButtonPress event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 761732, (33,42), root:(866,209),
state 0x10, button 6, same_screen YES

EnterNotify event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x0, time 761732, (33,42), root:(866,209),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

And

KeymapNotify event, serial 30, synthetic NO, window 0x0,
keys: 72 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 822497, (33,32), root:(866,199),
state 0x10, button 7, same_screen YES

LeaveNotify event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x0, time 822497, (33,32), root:(866,199),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

ButtonPress event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 826993, (33,32), root:(866,199),
state 0x10, button 7, same_screen YES

EnterNotify event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x0, time 826993, (33,32), root:(866,199),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 16


I would like to get buttons 6 and 7 working in nautilus, but if I can't then oh well. Anyone have any ideas? Using an Mx700 on Breezy.

[jonyo]

Hmmm... When I run xbindkeys, button 6 and 7 stop working. Here is the output from xev when xbindkeys is running:

MotionNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 635499, (52,52), root:(56,121),
state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 635507, (53,52), root:(57,121),
state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 635515, (65,52), root:(69,121),
state 0x10, is_hint 0, same_screen YES

EnterNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x0, time 635523, (75,54), root:(79,123),
mode NotifyNormal, detail NotifyInferior, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 72 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

And

LeaveNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 670473, (62,62), root:(895,229),
mode NotifyGrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeyPress event, serial 29, synthetic YES, window 0x2c00001,
root 0x48, subw 0x0, time 0, (1,1), root:(1,1),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 29, synthetic YES, window 0x2c00001,
root 0x48, subw 0x0, time 0, (1,1), root:(1,1),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:

EnterNotify event, serial 29, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 671097, (62,62), root:(895,229),
mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
focus YES, state 16

KeymapNotify event, serial 29, synthetic NO, window 0x0,
keys: 72 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

For the other button.

However, when xbindkeys is not running, buttons 6 and 7 work. Here is the output of xev when xbindkeys is not running:

KeymapNotify event, serial 30, synthetic NO, window 0x0,
keys: 72 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 761612, (33,42), root:(866,209),
state 0x10, button 6, same_screen YES

LeaveNotify event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x0, time 761612, (33,42), root:(866,209),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

ButtonPress event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 761732, (33,42), root:(866,209),
state 0x10, button 6, same_screen YES

EnterNotify event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x0, time 761732, (33,42), root:(866,209),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

And

KeymapNotify event, serial 30, synthetic NO, window 0x0,
keys: 72 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonRelease event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 822497, (33,32), root:(866,199),
state 0x10, button 7, same_screen YES

LeaveNotify event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x0, time 822497, (33,32), root:(866,199),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 16

ButtonPress event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x2c00002, time 826993, (33,32), root:(866,199),
state 0x10, button 7, same_screen YES

EnterNotify event, serial 30, synthetic NO, window 0x2c00001,
root 0x48, subw 0x0, time 826993, (33,32), root:(866,199),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 16


I would like to get buttons 6 and 7 working in nautilus, but if I can't then oh well. Anyone have any ideas? Using an Mx700 on Breezy.

I'm a newb to Ubuntu, but I'm learning fast ;) When you run xbindkeys the forward and back keys work in nautilus, but the break everywhere else right? This is kinda tedious but you might just make a shell script which calles xbindkeys, runs nautilus, waits for it to close, and when nautilus closes it kills xbindkeys... Thats kinda overkill but it seems like it should work. Also, anything else you are doing while you have nautilus open would not have working forward and back buttons...

[souled]

I'm a newb to Ubuntu, but I'm learning fast ;) When you run xbindkeys the forward and back keys work in nautilus, but the break everywhere else right? This is kinda tedious but you might just make a shell script which calles xbindkeys, runs nautilus, waits for it to close, and when nautilus closes it kills xbindkeys... Thats kinda overkill but it seems like it should work. Also, anything else you are doing while you have nautilus open would not have working forward and back buttons...

Thanks for the idea, but when xbindkeys is running, the buttons don't work in nautilus. They don't work anywhere :???:

[jonyo]

Thanks for the idea, but when xbindkeys is running, the buttons don't work in nautilus. They don't work anywhere :???:

What is in your .xbindkeysrc file?

[DancingSun]

I've already tried it, and it works ok. I was just wondering if there was a way to do it without mapping it to keystrokes, I'd rather do it the "proper" way if such a way exists...

About the application switching... after thinking about it I remember reading something mentioned on these forums somewhere, but now I can't find it. Anyone know of a howto somewhere that says how to set up app switching?

UPDATE: I was playing with it some more, and I set the number of buttons to 20... Now when tilt right, on key release it says button 120... How is it possible that it's reporting button 120 if my max is 20? By the way, my cruise up and down do button 11 and 12 on key release... I didn't mention that before.
To have "proper" support for those additional buttons, the applications will need to support the additional button events themselves, such is the way firefox work with the thumb buttons.

You might want to submit a feature request to www.gnome.org for GNOME to support the thumb buttons in places where it makes sense, and allow GNOME to pickup the Application Switch button to invoke the alt-tab switcher. It might never get implemented, but you'll never know.

[souled]

What is in your .xbindkeysrc file?


"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7


Just copied what the HOWTO said.

[DancingSun]

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7


Just copied what the HOWTO said.
It should be noted that the "left" and "right" is intended to have capitalized first characters, as in "Left" and "Right". However, the forum software will convert those letters to lowercase when they are enclosed in brackets.

[teaker1s]

reading the howto I have no output for scroll wheel left/right in xev which leaves me confused as I have a ps2 cordless mouse that is a logitech click!plus but identified as logitech explorer model 66 and I'm unsure if it's possibe to get an output and xbindkeys new and get key causes xbindkeys to crash

[souled]

It should be noted that the "left" and "right" is intended to have capitalized first characters, as in "Left" and "Right". However, the forum software will convert those letters to lowercase when they are enclosed in brackets.

Wow that did the trick! Thanks a lot.

[maser]

First of all, thanks for the guide, it's been a real help.

I've got everything on my mx500 working with my own customizations, except for one very strange problem - the bottom "cruise control" button doesn't work if I turn cruise control off; even pressing it in xev elicits no response. What makes this so strange is that the top cc button does work; it registers as button 10 in xev and works just like any other other button.

If I turn cc on, they both replicate the mousewheel as intended and both can be bound to any key in Windows with no problems, so what gives?

I had the same problem with my Logitech Cordless Optical TrackMan. The bottom cruise control button happens to be 12, and buttons 9 and 11 don't exist.

But now that the button works, I can't assign Ctrl+Shift+Tab to it with xbindkeys. I tried [Shift] and [Shift_L], but it just does a Ctrl+Tab.

Thanks for the guide! I don't think I'd still be using Ubuntu if I hadn't got the mouse buttons working!

maser

[blitz666]

endy: I have an mx550 (basically a recolor of the MX510)... you must say the EXACT USB or it wont boot x (ie, I cant use that "usb-*/input0" you used, I had to type out the entire *.

Do you know any way to make button 8 (the app switch button) to be foreward and the default thumb side button for forward to be enter key? How about to make the cruise move larger intervals? I am hoping to make this match the Win config I have for the same mouse.

When I say "sudo logitech_applet -s 400 -e", I get buttons 1-8 with the ccu and ccd being the same as wu and wd (this has been rehashed ad litem).
When I say "sudo logitech_applet -s 400", I get buttons 1-10 with the ccu being #10, and ccd does absolutely nothing. Ap-switch is still 8, thumbs are 6/7, etc.

How can I make 9 appear, rather than have a bum button?

[teaker1s]

is evdev protocol usb only or can it be used with cordless ps2

[DancingSun]

is evdev protocol usb only or can it be used with cordless ps2
It should work with any mouse.

[keitsi]

Anyone else having weird mouse speed problems with MX518?
http://www.ubuntuforums.org/showthread.php?p=543013#post543013

[CompShrink]

Ok, I have the Mediaplay cordless mouse working for all but 2 buttons (not bad considering it has the standard 2 buttons, tilting clickable scroll whell, 6 media buttons, and forward/back(the broken) buttons)

So, I followed the directions for lmpcm driver, but only to a certain point. Basically, a slightly altered version follows:

Compilation
Get lmpcm_usb source tarball and uncompress it: # tar zxf lmpcm_usb-0.5.2.tar.gz
Now, change to the created directory, compile and install the driver: # cd lmpcm_usb-0.5.2
$ sudo make
$ sudo make install
Installation script installed lmpcm_usb.ko (lmpcm_usb.o for kernel 2.4) into /lib/modules/your-kernel-version/misc/ and added an entry to modules.dep file, using depmod.

Loading modules
Edit /lib/modules/your-kernel-version/misc/modules.dep and remove usbmouse and usbhid entries. This is required because these modules "steal" any kind of mouse, so we have to load lmpcm_usb first. If usbmouse and/or hid are required for any other device, just load them after lmpcm_usb. But don't forget, lmpcm_usb SHOULD LOAD FIRST that any generic mouse driver.
Loading support:
(these 3 commands should be unneccessary unless you removed these modules for something else)
Kernel 2.6
$ sudo modprobe usbcore
$ sudo modprobe uhci-hcd

$ sudo modprobe evdev


Ensure usbmouse and hid are not loaded:

Kernel 2.6
$ sudo rmmod usbmouse
$ sudo rmmod usbhid
$ sudo modprobe lmpcm_usb

At this time, your mouse should work.


Ok, DO NOT DO ANYTHING MORE! If you read the official instructions from the guy who made it, you will probably screw up your system. I did, and now after a long and painstaking reverting process, I figured out, it works after this point.

Once you do the following, it works after reboot only when you execute the following in a terminal:
$ sudo rmmod usbhid
$ sudo rmmod lmpcm_usb
$ sudo modprobe lmpcm_usb
*note, after you execute the first line, you lose your mouse completely until you remove and reinitiate lmpcm_usb

I mapped the mediabuttons by: System > Preferences > Keyboard Shortcuts

I will update if I get the two side buttons working, and get the mouse loading automated. At least for me, if I removed usbhid completely, my mouse didn't work at all. I use them relatively frequently in windows, so I'd be nice if I could get them working. It's definately a lot more functional in Linux than it was yesterday at least.

[Golgoth]

Hi,

First of all, thanks for the how-to!

I want to add my config for a Logitech LX7 :

1) golgoth@laptop:~$ cat /proc/bus/input/devices

I: Bus=0003 Vendor=046d Product=c50e Version=2510
N: Name="Logitech USB RECEIVER"
P: Phys=usb-0000:00:1d.1-2/input0
H: Handlers=mouse1 event3 ts1
B: EV=7
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=143

2) golgoth@laptop:~$ sudo gedit /etc/X11/xorg.conf

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB RECEIVER"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event3"
Option "Buttons" "9"
Option "ZAxisMapping" "4 5 8 9"
Option "Resolution" "800"
EndSection

3) no .Xmodmap

4) golgoth@laptop:~$ gedit ~/.xbindkeysrc

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:9
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:8
"gnome-terminal"
m:0x0 + b:7
"nautilus"
m:0x0 + b:6

5) :) :) :) :) :) :) :) :)

[BLTicklemonster]

Question:

What can be done for other mouse types? The beginnings look like they are pretty much generic. Suppose all I really worry about is getting forward and back buttons working, will the initial steps work?

(and if I change from one video card to another, why must I redo the mouse settings?)

[Golgoth]

Why is this thread in this section?

Why not move it to the general Customization Tips & Tricks instead of the hoary one?

Moreover, Endy, you should rename the title and erase "logitech" since I have installed my Microsoft Intellimouse Optical following your how-to!

Here is my settings:

1) golgoth@fixe:~$ cat /proc/bus/input/devices

I: Bus=0003 Vendor=045e Product=0039 Version=0300
N: Name="Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)"
P: Phys=usb-0000:00:0a.1-2/input0
H: Handlers=mouse1 event3 ts1
B: EV=7
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=103

2) golgoth@fixe:~$ sudo gedit /etc/X11/xorg.conf

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event3"
Option "Buttons" "7"
Option "ZAxisMapping" "4 5"
EndSection

3) no .Xmodmap

4) golgoth@fixe:~$ gedit ~/.xbindkeysrc

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7

:)

[daedalusman]

Well everything worked fine until I tried to use the logitech_applet. When I try the command you use I'm getting this error...

sudo logitech_applet -s 800 -e
001/003 046D/C50B 967300-0403 Cordless MX Duo Receiver
Channel 1 Battery: 7 Single channel No 800cpi support No Horiz Roller No Vert Roller 3 butt.

What is this all about, I have the MX Duo (MX700 mouse) with both running out of the USB port? Is something not setup right, all the mouse bottuns are working as they should so its not a major problem I just thought I would post it so everybody knows about it. Thanks for the great guide.

[Golgoth]

I have the same with a LX7 mouse...

[Chris Tucker]

mx510 here...
before changeing my xorg.conf, (By the way, about that, i had a lot of frustration without using /dev/input/mice as the "Device", it killed xorg on a lot of occasions with the other mentioned device names!)
anyway, since changeing xorg.con, the scroll up button just above my scroll wheel triggers two buttons! both 4 and 6.

ButtonRelease event, serial 29, synthetic NO, window 0x4200001,
root 0x4b, subw 0x0, time 178452, (166,4), root:(191,144),
state 0x800, button 4, same_screen YES

ButtonRelease event, serial 29, synthetic NO, window 0x4200001,
root 0x4b, subw 0x0, time 178636, (166,4), root:(191,144),
state 0x0, button 6, same_screen YES

how could i fix this?
note: button 4 is scroll up, button 6 is the BACK button... so ... yea.. its kind of.. not useable.

[DancingSun]

mx510 here...
before changeing my xorg.conf, (By the way, about that, i had a lot of frustration without using /dev/input/mice as the "Device", it killed xorg on a lot of occasions with the other mentioned device names!)
anyway, since changeing xorg.con, the scroll up button just above my scroll wheel triggers two buttons! both 4 and 6.

ButtonRelease event, serial 29, synthetic NO, window 0x4200001,
root 0x4b, subw 0x0, time 178452, (166,4), root:(191,144),
state 0x800, button 4, same_screen YES

ButtonRelease event, serial 29, synthetic NO, window 0x4200001,
root 0x4b, subw 0x0, time 178636, (166,4), root:(191,144),
state 0x0, button 6, same_screen YES

how could i fix this?
note: button 4 is scroll up, button 6 is the BACK button... so ... yea.. its kind of.. not useable.
It's probably useful if you post your xorg.conf...it sounds like you've misconfigured the mouse to use the intellimouse/MS mouse driver or something. I remember I had that very same problem when I configured my mouse as intellimouse (I have MX510). The older guides will direct you to use that driver to enable the thumb buttons.

[Chris Tucker]

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protovol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mous$ Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/mice"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection

Note: Synaptics touchpad hasnt been configured yet.. i dont use its scroll button... the rest of that touchpad works fine.
i have tried changing the ZAxisMapping to 6 7 and it switches the forward and back buttons to different numbers, then xev shows 6 & 7 as my sroll events for my scrollwheel, and the proper button for the extra scroll down button. BUT the extra scroll up button is the same thing as pressing the back button AND scrolling up. regardless of the ZAxisMapping.

[DancingSun]

Option "Dev Name" "Logitech USB-PS/2 Optical Mous$ Option "Dev Phys" "usb-*/input0"
You merged 2 option lines into 1, plus you have that dollar sign in place of an "e" and a double quote. This is how my mouse confirguration in xorg.conf looks like:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Protocol" "evdev"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Dev Phys" "usb-*/input0"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"
EndSection

Edit: And you spelled "Protovol" wrong, it's suppose "Protocol".

[Chris Tucker]

Option "Dev Name" "Logitech USB-PS/2 Optical Mous$ Option "Dev Phys" "usb-*/input0"
You merged 2 option lines into 1, plus you have that dollar sign in place of an "e" and a double quote.
Edit: And you spelled "Protovol" wrong, it's suppose "Protocol".
Oops. sorry, the line doesnt REALLY have that $ there and the Dev Phys line is a seperate line. when i copied that it was from pico, and the terminal was just a little narrow to show the whole word "Mouse""
And that typo in Protocol did it, its working great now, thanks for the help!

[snellgrove]

Hey all,

Think I may have something useful to add to this thread, as another slightly frustrated Logitech user!

I have the MX1000 (great mouse btw) and thanks to this guide, I have it working nicer than before.

But, I think the problem lies with firefox! (or nautilus)

If I have xbindkeys running, so the side-buttons on the mouse are mapped to Alt+Left, and Alt+Right nautilus runs great, I can navigate back and forward with my mouse (yay)

but firefox now pages up, and down with these buttons.

Killing xbindkeys, so the buttons are not mapped to anything... I guess, and suddenly firefox runs just fine, back/forward changes pages ! but suddenly nautilus doesn't do anything lol.

So we need a way of making firefox understand alt+Left/Right I would say?

or have I done something wrong! great guide guys though, my mouse is working nicer than before, definately something for the Wiki if its not already in there :)

:edit:

uhhhhh ignore me or something?!?!?!? LOL suddenly I just found its all working .. dunno what the heck i've just done though :p :o

[DancingSun]

Hey all,

Think I may have something useful to add to this thread, as another slightly frustrated Logitech user!

I have the MX1000 (great mouse btw) and thanks to this guide, I have it working nicer than before.

But, I think the problem lies with firefox! (or nautilus)

If I have xbindkeys running, so the side-buttons on the mouse are mapped to Alt+Left, and Alt+Right nautilus runs great, I can navigate back and forward with my mouse (yay)

but firefox now pages up, and down with these buttons.

Killing xbindkeys, so the buttons are not mapped to anything... I guess, and suddenly firefox runs just fine, back/forward changes pages ! but suddenly nautilus doesn't do anything lol.

So we need a way of making firefox understand alt+Left/Right I would say?

or have I done something wrong! great guide guys though, my mouse is working nicer than before, definately something for the Wiki if its not already in there :)

:edit:

uhhhhh ignore me or something?!?!?!? LOL suddenly I just found its all working .. dunno what the heck i've just done though :p :o
By default, in firefox, the back and forward buttons are binded to the alt+left/right keys. But firefox also responds to the button events generated by the thumb buttons, and it maps them to the forward and backward buttons. Nautilus, on the other hand, does not respond to the thumb buttons, so that's why you need the button mappings to make the thumb buttons work in Nautilus.

[Chris Tucker]

ok, i for one am NOT happy. i swap my mouse around depending on what computer i am using. sometimes i do not plug it in at all, and use my trackpad. but with this howto, so far, when my mouse is disconnected, if reconnected to another usb port, its unusable without an X server restart. and if the mouse is not plugged in when the system powers on, X server will not start. in this case i find myself backing up my xorg.conf and then deleting the "configured mouse" sections, only to later have to re-add them and restart my xserver AGAIN later.

is there any way to correct these inconvieniences?

[Rev. Nathan]

I used this tutorial before, blindly following the instructions, not observing what went into the tutorial. Well, I found where the keys were assigned, and I added a Play/Pause control for the 'Window Switcher' button for the MX5xx series! Awesome.

But, can you set it to where it works when the window to pause it out of focus?

Lastly, my back and forward buttons stopped working since I changed the capitalization; now no matter which I save, it doesn't work. Help?

[DancingSun]

But, can you set it to where it works when the window to pause it out of focus?I'm not sure as I don't use any keyboard bindings for my mouse. But in the System menu, there is an item called "Keyboard Shortcuts" under Preferences. Inside, you'll see that you can bind a keyboard shortcuts for "Play (or play/pause)" under the "Sound" category. You might want to try that and see if you can set a keyboard shortcut to it, and then bind the mouse button you want to use to that shortcut.
Lastly, my back and forward buttons stopped working since I changed the capitalization; now no matter which I save, it doesn't work. Help?What do you mean? Are you talking about the xbindkey configuration file? If so, make sure that "Left" and "Right" have their first character capitalized.

[fabs0028]

thanx a lot for the howto ... i allready had done the first part but i was wondering how to enable the side buttons with nautillus and then i fell on your guide and it worked like a charm :)

Really great thanx :)

[BLTicklemonster]

I tried following the first part to get a microsoft optical intellimouse to have forward back buttons, and it messed everything up. Had to redo either xorg or x11 or whatver pertains to mouseses.


What can I do to get an intellimouse to work right?

[DancingSun]

I tried following the first part to get a microsoft optical intellimouse to have forward back buttons, and it messed everything up. Had to redo either xorg or x11 or whatver pertains to mouseses.


What can I do to get an intellimouse to work right?
Someone on this thread has an intellimouse too, and he also posted his configuration:
http://ubuntuforums.org/showthread.php?p=566023&highlight=intellimouse#post566023

[Sp@z]

Nice job man! Worked great for me and My MX 510!!!!!!!

[kingzasz]

I am stuck on the first step. My mouse does not work when I plug it into the USB.

The output from "cat /proc/bus/input/devices" only lists the keyboard, with no entry for a mouse.

I've had problems in the past with getting any USB device to work (actually, I don't think I've ever gotten a USB device to work). Could this be the problem?

Thanks.

[DancingSun]

I am stuck on the first step. My mouse does not work when I plug it into the USB.

The output from "cat /proc/bus/input/devices" only lists the keyboard, with no entry for a mouse.

I've had problems in the past with getting any USB device to work (actually, I don't think I've ever gotten a USB device to work). Could this be the problem?

Thanks.
Yes, sounds like your USB ports are not functioning at all. You best bring your question over to the hardware support forum.

[Sapper2ID]

I have an MX700 and I don't understand what the advantage is of doing all these steps. All I did was change 2 lines in xorg.conf.

Change "Protocol" from "ImPS/2" to "ExplorerPS/2"
Added Option "Buttons" "7"

That's it and I have all functions in my mouse. I'm just doing what I accidently did when I used Warty, I 'm still new to Linux. I didn't install Imwheel or anything. Like I said, I originally screwed up and this worked. I've used this method on 5 different PC's I've built.

Am I missing something?

[DancingSun]

I have an MX700 and I don't understand what the advantage is of doing all these steps. All I did was change 2 lines in xorg.conf.

Change "Protocol" from "ImPS/2" to "ExplorerPS/2"
Added Option "Buttons" "7"

That's it and I have all functions in my mouse. I'm just doing what I accidently did when I used Warty, I 'm still new to Linux. I didn't install Imwheel or anything. Like I said, I originally screwed up and this worked. I've used this method on 5 different PC's I've built.

Am I missing something?
It is my experience that, when using the "ExplorerPS/2" protocol, the cruise up button will generate 2 button events. That is, it will scroll up once, and then generate the "back" thumb button's event. So, in firefox, when I cruise up, it'll scroll up by one line, then take me to the previous page that I viewed. Using the "evdev" protocol is the only way that I've found so far to have made every button on my mouse (MX510) to work correctly.

In fact, even the "switch application" button at the center of the mouse is usable. Just that it has no function in Linux, but the button generates events and can be binded to other commands. I use it to bind commands when playing games.

[Killerdackel]

Most of the buttons work good now but two things are not completly done now.

1.I have the same problem that one user some pages earlyer mentioned. Sometimes when I click one of the thumb buttons my X acts if I had pressed the buttons a 100 times. I played a little bi with xbindkeys and now my configuration is the following:


"/usr/X11R6/bin/xvkbd -no-jump-pointer -no-repeat -xsendevent -text "\[Alt_L]\[Left]""
b:8
"/usr/X11R6/bin/xvkbd -no-jump-pointer -no-repeat -xsendevent -text "\[Alt_L]\[Right]""
b:9
"/usr/X11R6/bin/xvkbd -no-jump-pointer -no-repeat -xsendevent -text "\[Super_L]b""
b:10
"echo ButtonPress 4 ButtonRelease 4 | xmacroplay -d 0 :0.0"
b:11
"echo ButtonPress 5 ButtonRelease 5 | xmacroplay -d 0 :0.0"
b:12


The -no-jump-pointer seems to work and keeps the xbkbd from jumping pointer to top of the active window.

2. How can I say xvkbd to pres WIN_L+b? the keysim for win is Super_L but my configuration as shown above causes xvkbd to release WIN+L bevor pressing b that does't do the trick.

[fabs0028]

Hello
well i just wanted to add a newer version of the /etc/init.d/local script that will fit better with the boot process : juste copy this


#!/bin/sh

. /lib/lsb/init-functions

case $1 in
start)
log_begin_msg "Setting up Logitech mouse..."
if logitech_applet -s 800 -e > /dev/null; then
log_end_msg 0
else
log_end_msg 1
fi
;;

stop)
;;
esac


It should produce a clean output such as all the other init scripts

[nutshell]

This tutorial works fine for me, as long as I boot the computer with the mouse plugged in the one specific USB port I used when setting it up ... Not really useful as this is a laptop and I don't always plug in the mouse ... If I don't X won't even start!
Maybe you could add this as a warning for laptop users. Otherwise everything works fine execpthorizontal scrolling (but I havent used xmodmap).

[Rizado]

I've got a problem...
I: Bus=0003 Vendor=046d Product=c01d Version=2100
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:1d.2-2/input0
H: Handlers=mouse0 ts0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103I've got a MX510 and as you can see I don't have any "event"... Now I have absolutely no idea what to do. Help?

[BLTicklemonster]

Someone on this thread has an intellimouse too, and he also posted his configuration:
http://ubuntuforums.org/showthread.php?p=566023&highlight=intellimouse#post566023
Thank!!! I just I mean santa just got my 11 year old a motherboard with a amd smpron 2200+ and I'm redoing everything, and it will be nice having his mouse right.

[Brent Dax]

Awesome tutorial--thank you. I used this to get my Logitech MX600 (comes with the MX3000 kit) working pretty nicely. However, its "zoom in" and "zoom out" buttons don't seem to be recognized. (The "100%" button shows up as button 8.) Any thoughts on this? I have Buttons set to 12 just in case, but no dice.

I: Bus=0003 Vendor=046d Product=c513 Version=3200
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1d.7-3.3/input1
H: Handlers=kbd mouse0 event2 ts0
B: EV=f
B: KEY=ff0001 0 38000 39fa d841d7a9 9e0000 0 0 0
B: REL=1c3
B: ABS=ffffff01 0

[atlas95]

Hello,
I have yet some problem after read all this post!

With my new mx1000 (i have buy a logitech mx3100), the button for swith task and buttons, scroll left and right generate any code with xev...

I don't know how repair this...

I past my xorg.conf below:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "ImExPS/2 Logitech Explorer Mouse"
Option "Dev Phys" "isa0060/serio1/input0"
Option "Device" "/dev/input/event2"
Option "Buttons" "12"
# Option "ZAxisMapping" "4 5"
Option "ZAxisMapping" "4 5 10 9"
Option "Emulate3Buttons" "false"
Option "Resolution" "800″
#Option "CorePointer"
EndSection


device

I: Bus=0011 Vendor=0002 Product=0006 Version=0042
N: Name="ImExPS/2 Logitech Explorer Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 event2 ts0
B: EV=7
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=103

say me if you want something else

ps: sorry for my english i'm french.

[Rizado]

I've got a problem...
I: Bus=0003 Vendor=046d Product=c01d Version=2100
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:1d.2-2/input0
H: Handlers=mouse0 ts0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103I've got a MX510 and as you can see I don't have any "event"... Now I have absolutely no idea what to do. Help?I got it working. The problem was that the evdev module wasn't loaded. Just added evdev to /etc/modules and it worked fine. I removed the old modules too.

[ow50]

Here's one fully working Logitech G5 configuration using imwheel.

/etc/X11/xorg.conf mouse section
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB Gaming Mouse"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5 7 6"
Option "Resolution" "800"
EndSection

/etc/X11/imwheel/startup.conf
IMWHEEL_START=1
IMWHEEL_PARAMS="-b "45678""

~/.imwheelrc
Configures a double click for the thumb button.
".*"
None, Thumb1, Button1, 2

As a result all buttons work. The DPI adjustment buttons work purely on hardware basis.

[Mr_J_]

I have a Logitech MX 518.
Not everything works perfect.

1 - I use InitNG and that makes your last part about adding logitech_applet to the start is not very fruitfull.
2 - Although all the buttons you had me configure threw the howto work fine, i have still to configure 3 buttons.

The main problem is not the first, but the second.
I would like to make the extra 3 buttons work in a game, but they aren't detected at all.
I miscalculated at first and put 9 buttons in my xorg.conf, the second button below the scroll wheel registered in xev as button 8. The good news is I successfully now learned to count to 10 and modified the xorg.conf to make 10 buttons. The bad news is my mouse now does not show any of the scroll wheel surrounding buttons. Neither up or down. Not even in xev.

I tried to add some extra lines to .xbindkeysrc by copying the last line a total of 3 extra times and modifying the number of the button, but of course since xev shows none of them...they don't quite work at all.


I was thinking of why can't I just add that line about logitech_applet to sessions.

[atlas95]

Hey, anybody can answer to me?
Mx1000 only works "fully" when it is in USB ?

If it is taht, I will buy a switch ps2>usb but you must say me if it's really this.

Thanks, sorry for my english

[Balachmar]

Hi,

Does anyone got the solid state pad of the V500 working?
It works for the up and down scrolling, but not for the left and right scrolling...
Just wondering if someone had got that to work...
I will give you some extra info:
mouse button1 = left button
mouse 2 = go left on solid state
mouse 3 = right button
mouse 4 = up on solid state
mouse 5 = down on solid state.

So to me this looks like, there is no way I would get the left right scrolling working, because it looks like it is just 1 button...

[_simon_]

I have an MX700

I have all the buttons except for cruise up and cruise down working. (i don't have the app button working but don't use it)

What do i need to do to get cruise up/down working?


I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=1 80000004 2000000 3002078 f840d001 f2ffffdf ffefffff ffffffff ffffffff
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=046d Product=c506 Version=1600
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:02.0-1/input0
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0003 Vendor=045e Product=00b0 Version=0110
N: Name="Microsoft Microsoft\uffff Digital Media Pro Keyboard"
P: Phys=usb-0000:00:02.1-1/input0
H: Handlers=kbd event2
B: EV=120003
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: LED=7

I: Bus=0003 Vendor=045e Product=00b0 Version=0110
N: Name="Microsoft Microsoft\uffff Digital Media Pro Keyboard"
P: Phys=usb-0000:00:02.1-1/input1
H: Handlers=kbd event3 js0
B: EV=10000f
B: KEY=c000000 1 10000 38007 ff8739fa d941d7ff febeffdf ffefffff ffffffff fffffffe
B: REL=40
B: ABS=ffffff01 701ff

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



Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "0000:00:02.0-1/input0"
Option "Device" "/dev/input/mice"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection

[lindejos]

Thanks a bunch. This is the first thing that I have been able to do without having to bother my brother!

I have the MX 700 and all I had to change was the mouse name and the scroll to buttons 9 and 10, but otherwise your how to was perfect.

Thank you!:razz:

[lindejos]

you might want to double check your scroll with xev. I have the same mouse and I needed to change my z-axis mapping to buttons 9 and 10 instead of 4 and 5.

[Balachmar]

Could anyone help me out with my V500?
All info I got is in my previous post. I would really like to get the horizontal scrolling to work...

[Big-Wayne]

Greetings,
I have been trying for a few days to get the thumb button working on my Logitech Mousman Dual Optical. I don't however use it via usb as it is plugged into a KVM switcher via a PS/2. I have succeeded in getting the scroll wheel to send webpages backwards and forwards, and the thumb button to scroll, but that was not really what I was after. I want the thumb button to send webpages/nautilus back.

Here is my cat proc output;

I: Bus=0011 Vendor=0002 Product=0006 Version=005f
N: Name="ImExPS/2 Logitech Explorer Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=103

xev shows buttons as follows;

left click button 1
wheel press button 2
right click button 3
scroll up button 4
scroll down button 5
thumb button 2

Notice thumb and middle wheel click are the same

My xorg.conf is edited as follows;

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Protocol" "ImPS/2"
Option "Device" "/dev/input/mice"
Option "Dev Name" "ImExPS/2 Logitech Explorer Mouse"
Option "Buttons" "7"
Option "ZAxisMapping" "4 5"
EndSection

Now I know people will probably say that is not how the tutorial said to edit my xorg.conf, but I had to edit it for a PS/2 not a usb.
I did add the lines
Option "Dev Phys" "isa0060/serio1/input0"
Option "Device" "/dev/input/event1

That crashed my xserver, so I took them out.
Any help on this matter would be greatly appreciated.

[Big-Wayne]

Greetings,
I have been trying for a few days to get the thumb button working on my Logitech Mousman Dual Optical. I don't however use it via usb as it is plugged into a KVM switcher via a PS/2. I have succeeded in getting the scroll wheel to send webpages backwards and forwards, and the thumb button to scroll, but that was not really what I was after. I want the thumb button to send webpages/nautilus back.

Here is my cat proc output;

I: Bus=0011 Vendor=0002 Product=0006 Version=005f
N: Name="ImExPS/2 Logitech Explorer Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=103

xev shows buttons as follows;

left click button 1
wheel press button 2
right click button 3
scroll up button 4
scroll down button 5
thumb button 2

Notice thumb and middle wheel click are the same

My xorg.conf is edited as follows;

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Protocol" "ImPS/2"
Option "Device" "/dev/input/mice"
Option "Dev Name" "ImExPS/2 Logitech Explorer Mouse"
Option "Buttons" "7"
Option "ZAxisMapping" "4 5"
EndSection

Now I know people will probably say that is not how the tutorial said to edit my xorg.conf, but I had to edit it for a PS/2 not a usb.
I did add the lines
Option "Dev Phys" "isa0060/serio1/input0"
Option "Device" "/dev/input/event1

That crashed my xserver, so I took them out.
Any help on this matter would be greatly appreciated.


Ignore the above, must have had a typo or something thumb button works as a back button in Firefox but not in nautilus.
This is my submission in xorg.conf;

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Protocol" "evdev"
Option "Device" "/dev/input/mice"
Option "Dev Name" "ImExPS/2 Logitech Explorer Mouse"
Option "Dev Phys" "isa0060/serio1/input0"
Option "Device" "/dev/input/event1
Option "Buttons" "7"
Option "ZAxisMapping" "4 5"
EndSection

[blitz666]

Post 1, section 2:

tells the user how to make the thumb's work in Nautilus

[TheForumTroll]

Great guide!

FYI my mx 500 mouse was called "B16_b_02 USB-PS/2 Optical Mouse". Dont know why, but everything works fine.

[M3lted]

woowooo

i follow the instructions and it works ,well didnt work at first , but that was bc i made a typo lol :P
after 1 hour of looking at the cfg i noticed i put in event 0 insted of 1 lol :P
so changed it and it works great :)


Edit
now after a reboot it stopped working :(
xbindkeys is starting up but the side button dont work anymore :S
any idea's guys ?

[Chris Tucker]

is anyone else having a problem where if you unplug the mouse and plug it back in, the system does not recognize it? or if you boot without the device plugged in, xserver wont start?
the unplug/plug in problem i think is something to do with the driver not talking to hotplug.. but the boot up not finding the mouse im not sure. is there another protocol other than "evdev" you can use?

[lleberg]

This is great!

The only problem i've got, is that i can't get the sideways scrolling to work..
It detects the sideway-scrolling actions as the same buttons as scroll up and scroll down..

There was a link explaining how to fix this in the howto, but it is broken!

[programgeek]

I have a Logitech MX 518.
Not everything works perfect.

1 - I use InitNG and that makes your last part about adding logitech_applet to the start is not very fruitfull.
2 - Although all the buttons you had me configure threw the howto work fine, i have still to configure 3 buttons.

The main problem is not the first, but the second.
I would like to make the extra 3 buttons work in a game, but they aren't detected at all.
I miscalculated at first and put 9 buttons in my xorg.conf, the second button below the scroll wheel registered in xev as button 8. The good news is I successfully now learned to count to 10 and modified the xorg.conf to make 10 buttons. The bad news is my mouse now does not show any of the scroll wheel surrounding buttons. Neither up or down. Not even in xev.

I tried to add some extra lines to .xbindkeysrc by copying the last line a total of 3 extra times and modifying the number of the button, but of course since xev shows none of them...they don't quite work at all.


I was thinking of why can't I just add that line about logitech_applet to sessions.

Would you mind posting you xorg.conf and other related files for other people to see? Thank you.

[Sandlst]

Thanks Endy! Great guide, everything workd perfect for me, and now my mouse is so fast its ridiculous :)

[cs378]

This works great :KS :KS :KS

Thank you so much for writing this up. I also learned a lot of new stuff here too hehe

But there is one problem with me, because i am on laptop. Somtimes I unplug the Mouse from the computer so i only use the touchpad but with the xorg.conf set to the logitech mouse I can't start up X, like u said it won't start if there is error. I have to have my mouse plugged in. So my question is, is there a way so that it works even if my mouse is not plugged in?

I only did the xrog.conf, n thats it hehe

[DancingSun]

This works great :KS :KS :KS

Thank you so much for writing this up. I also learned a lot of new stuff here too hehe

But there is one problem with me, because i am on laptop. Somtimes I unplug the Mouse from the computer so i only use the touchpad but with the xorg.conf set to the logitech mouse I can't start up X, like u said it won't start if there is error. I have to have my mouse plugged in. So my question is, is there a way so that it works even if my mouse is not plugged in?

I only did the xrog.conf, n thats it hehe
This has been a common question for laptop users. I do not own a laptop, so I do not know the correct answers. But I did a little searching on the forum and found this thread that sounds related:

http://ubuntuforums.org/showthread.php?t=110945&highlight=laptop+usb+mouse+touchpad

[marcog]

Finally a step-by-step guide on how to get the forward/back buttons working that actually works!

I have one small problem though. Pasting by clicking left+right buttons together no longer works. It worked fine before making the changes. I'm beginning to wonder what is more important - the forward/back buttons or pasting using left+right buttons.

I'm using an mx518 on an HP nx7010.

[blitz666]

Where it says "emulate 3 button mouse" change that to yes instead of no.

[marcog]

I couldn't find an "emulate 3 button mouse" option.

Instead I found an "Emulate3Buttons" option set to true in my old configuration. So I copied that line into my new config.

Now the left+right click does paste, however I can no longer select text with the mouse! :-(

So I've removed the line again until I can find a way that works properly.

This is a section of my current xorg.conf file:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:1d.0-2/input0"
Option "Device" "/dev/input/event1"
# Option "Emulate3Buttons" "true"
Option "Buttons" "7"
Option "ZAxisMapping" "4 5"
EndSection

[RaptorRaider]

This worked perfectly for my (partly broken) MX510; I think this thread deserves a small kick. ;)

[r!ots]

first of all thx for this great guide. i use a logitech mx500 and it worked perfectly for me.

i also tried to make the mouse button, which moves between windows, work by editing the ~/.xbindkeysrc so it looks like this:

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Tab]""
m:0x0 + b:8


somehow it doesn't work and i don't have any idea why not. can anyone help plz?

[Balachmar]

Still don't know how to do a correct install of the vertical scrolling with my V500.
Because sliding to the left or right results in the same button being reported by the program.

[marcog]

Have you tried changing the "Buttons" option to a higher number?

[Balachmar]

Well, it is the output generated by xev.
It only detects 5 buttons, and I thought it would be able to track any amount of buttons... How do I specify the amount of buttons then for xev?
left = 1
scroll left =2
right =3
scroll up = 4
scroll down = 5
scroll right doesn't show up anything. It does work in windows by the way.

[RaptorRaider]

This worked perfectly for my (partly broken) MX510; I think this thread deserves a small kick. ;)
Had to do a reinstall of Ubuntu today, and somehow I can't get my side buttons to work correctly, even though I'm doing exactly the same as last time as far as I know.
Did something change?

Edit: I have no idea why, but after a couple of reboots it is working perfectly once again.

[Mr_J_]

Hi!

This is the second time I followed this howto and it has worked for the most part.

I've had trouble getting my extra buttons to work both times.
I WILL get it to work even if it exausts the life out of me.:D

Xorg.conf :
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:02.0-1/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"
Option "CorePointer"
EndSection
I was thinking of adding:
Option "Resolution" "1600"
Which I will do later and report what it does, if anything.

Before I remember trying out the number of buttons and ending up at 8 threw trial and error, but I've a few sites which seem to indicate it's 10 buttons I should count.
The mouse has + and - buttons which I thought were hardware controlled and not software. Can anyone clear this one up for me?

I have yet to get any extra button working. Even tho I did have gdm restarts and full reboots in case I missed anything.

Xbindkeys:
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:7
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[TAB]""
m:0x0 + b:8


At first I had a bunch of problems with getting the mouse recognized under X, but after considerable fidling it seems to no longer give me too many problems.

I recomend changing the Howto in order to download all the necessary files before you even start. I think that was one of the steps that helped fix the problem with my X not starting.

X didn't find any protocol to use, and the wildcard use in the "Dev Phys" had to be corrected, also didn't find a Core Pointer. Which was probably because I changed my existing Mouse section and didn't coment it out.
Even tho that last statement makes little sense to me, it did seem to work when I added the Core Pointer option.

[aliencds]

this worked for my g5 mouse on the first step now my side button works.. i didnt even have to to any of the other side button xmapping stuff :/

[calgarystevens]

I have an MX700 and I don't understand what the advantage is of doing all these steps. All I did was change 2 lines in xorg.conf.

Change "Protocol" from "ImPS/2" to "ExplorerPS/2"
Added Option "Buttons" "7"

That's it and I have all functions in my mouse.

MX1000 here on mine, and this worked for me also, 7 buttons working perfectly. Anyone with the ps/2 adaptor might want to try this first, it might work. Then, if not, switch to usb and follow the guide.

[Craig Caldwell]

It only took me most of the day:-k but forward and back now work on my mx 700 thumb buttons. I usually have to do a lot more than this to feel good about myself. Linux rules... but seriously that was so much more satisfying than just plugging in a mouse and using it.


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB Receiver"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/event3"
Option "Buttons" "8"
Option "ZAxisMapping" "4 5"
EndSection

#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "CorePointer"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "ImPS/2"
# Option "ZAxisMapping" "4 5"
#EndSection


Section 2: Side buttons and Nautilus

We can use "xvkbd" and "xbindkeys" to bind the side mouse buttons to "ALT + LEFT" and "ALT + RIGHT" so they work as forward and backwards in Nautilus.


1. xvkbd and xbindkeys

Lets install "xvkbd" and "xbindkeys":
Code:
sudo apt-get install xvkbd xbindkeys
Next we need to create the configuration for them:
Code:
gedit ~/.xbindkeysrc
Now paste the following:
Code:
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[right]""
m:0x0 + b:7


Please note, the "L" and "R" from the words "left" and "right" in the square brackets above should be capitalised, this seems like a bug in the forums here that they don't display properly.
Thank you endy and every one else who had tips tricks crushing failure and sweet success.

[R3linquish3r]

thx alot :) back and forward buttons work as soon as i set it up in xorg cause im using firefox :)

[kayrune]

Has anyone gotten the MX1000 working with Xgl ? When running Xgl, my MX1000 is detected as a 7 button mouse with the evdev driver.

[bender unit]

Hello Folks,

I was just linked to this thread from the Wiki page based off it that explains how to configure a MX1000 mouse with Ubuntu (https://wiki.ubuntu.com/MX1000Mouse). Just wanted to say that I simply followed this guide and got my Logitech MX610 working (almost) perfectly under Linux now! The mouse wheel left/right scrolling as well as the side buttons for forward/backward work flawlessly now.

Never bothered to check until now, but what amazed me even more was that the additional buttons for volume control work, too! I'm not sure if they worked before, or if this was the effect of changing the mouse driver in xorg.conf, but they work now, anyways, and do exactly what they're supposed too, even though I did nothing at all to achieve this behavior (I mean, the guide was just for the other buttons, right?).

Now the only thing that's missing is a tool that lights up the two buttons that are supposed to show incoming mails and IMs, respectively. Pressing the mail button already starts Gnome's default mail program, but if I could get the mail notification applet to light up the button when new mail arrives, I would be even happier with Ubuntu. Has anyone heard of a way to do this? Or is it rather that nobody on the forum (except me) even owns such a mouse, since searching for "mx610" doesn't return a single result? (except my post now, I guess...)

[LycoLoco]

I've got an MX518 and using this guide I got the left and right buttons working, but now I can't get the up/down/program buttons working (the 3 in the middle). When I run xev, the up and down buttons don't show anything as being read, but I know that they work in XP, so it's not dead hardware. Anyone have any ideas? :confused:

[asktoby]

When I bought my logitech mouse for kubuntu, the wheel originally didn't
work. I tried following the instructions in this thread and, while they worked, I found that my hotswapping of things like mice,
usb keys, mp3 players etc seemed a bit flakey. Sometimes the mouse died and wouldn't come back to life (light underneath was off) until I rebooted.

Anyway, after some tweaking, I found that I didn't need to do half of
the fiddly stuff described in that thread, and now I have the following
mouse section in my /etc/X11/xorg.conf

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection

This is for a Logitech Optical Mouse M/N:M-BT96a which I bought last
month.

HTH

[maclaxguy]

Great article, but I'm having some problems.

After following the directions, my mouse works great.
I'm on a laptop, so I constantly need to unplug and plug my mouse. Unfortunately, after unplugging and then replugging in, the mouse does not do anything. The trackpad still works fine, but I can't use the mouse without restarting.

When plugging it in, /var/log/messages shows this:
Mar 2 20:52:55 localhost kernel: [4295319.826000] usb 2-2: new low speed USB device using uhci_hcd and address 5
Mar 2 20:52:56 localhost kernel: [4295319.998000] input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.1-2
Mar 2 20:52:56 localhost input.agent[10082]: tsdev: already loaded
Mar 2 20:52:56 localhost input.agent[10082]: mousedev: already loaded
Mar 2 20:52:56 localhost input.agent[10082]: evdev: already loaded
Mar 2 20:52:56 localhost usb.agent[10094]: usbhid: already loaded
Mar 2 20:52:56 localhost input.agent[10187]: evdev: already loaded
Mar 2 20:52:56 localhost input.agent[10197]: evdev: already loaded
Mar 2 20:52:56 localhost input.agent[10203]: evdev: already loaded


Anyone have any ideas on what to do?

I appreciate the help.

[asktoby]

When my hotplug system was glitchy, before streamlining my xorg.conf as I described 2 posts previously, I found that I could sometimes 'resurrect' a dead mouse by pressing ctrl-alt-F8 then ctrl-alt-F7 (assuming there was a 2nd login on F8). i.e. switch to a different GUI login and back again.

I have no idea how or why this worked. It didn't always work.

[Maupertus]

This may have been a problem handled in this thread, but it's so large that I'm losing oversight.

I edited the xorg.conf as stated above, and X doesn't want to load now.
So I tried to edit the file using the "sudo nano /etc/x11/xorg.conf" command offered above, but I only get a blank screen without the file I have just edited.

As a result I cannot log in to the graphical enviroment and am a bit stumped as to what to do?

So please, what do I have to do now?

[asktoby]

Capital X in your path.

sudo nano /etc/X11/xorg.conf

If in doubt, use [tab] to autocomplete whilst you type :)

[phux]

Hi,

i have trouble, getting my MX1000 to work as i want.

Vertical-Scrolling does not work at all an the output of
sudo logitech_applet -s 800 is
001/003 046D/C50E M-RAG97 MX1000 Laser Mouse
Channel 1 Battery: 7 Single channel No 800cpi support No Horiz Roller No Vert Roller 2 butt.

How can i enable 800cpi and cruise control?

Buttonmapping: (Button-xevNumber)
Left-1, Right-3, Middle-2, Scrollup-4, Scrolldown-5, ThumbForward-9, ThumbBackward-8, ThumbMiddle-10, WheelClickUpper-11, WheelClickLower-12

thx

[joe_geek]

For those of you who managed to get an LX7 working:

my xev only recognizes as following
left click: button 1
right click: button 3
scroll click: button 2
scroll up: button 4
scroll down: button 5

here's where it gets weird:
scroll left: button 2
scroll right: nothing comes up

for those two buttons that would do page back/forward in Windows:
page back: button 2
page forward: button 3

I followed Golgoth (http://ubuntuforums.org/showthread.php?p=561025&highlight=lx7#post561025)'s tutorial, but I'm not getting the page back/forward and scroll left/right for obvious reasons.
Does anyone know how to get xev to recognize the mouse buttons on the LX7?

[beerorkid]

Has anyone gotten the MX1000 working with Xgl ? When running Xgl, my MX1000 is detected as a 7 button mouse with the evdev driver.

This guide has been awesome for the last 10 or so times I have installed breezy. I am using dapper flight 5 with the compiz XGL and this fix does not work anymore.

Is that a dapper issue or a compiz/XGL problem. I am betting it is the compiz/XGL cuz it does some pretty strange stuff which I hardly understand dealing with xorg.conf.

Just wondering if anybody has any ideas.

[fizz]

Not sure whats up, i followed the guide to a t, but for whatever reason, when i start X, i get

Unknow Protocol "evdev"

Im using a MX700 and set it up according to how others have done it also.

thanks

[souled]

Not sure whats up, i followed the guide to a t, but for whatever reason, when i start X, i get

Unknow Protocol "evdev"

Im using a MX700 and set it up according to how others have done it also.

thanks

Edit: Oops. I thought this was in a different thread. Haha, my mistake.

[r3n0z]

worked great for my mx310, think i have the lowest model number so far :P

anyhow there's something satisfying about configuring it yourself

[Brunellus]

This guide has been awesome for the last 10 or so times I have installed breezy. I am using dapper flight 5 with the compiz XGL and this fix does not work anymore.

Is that a dapper issue or a compiz/XGL problem. I am betting it is the compiz/XGL cuz it does some pretty strange stuff which I hardly understand dealing with xorg.conf.

Just wondering if anybody has any ideas.
Just wanted to confirm the dapper issue. I suspect it is an XGL/Compiz issue, because I actually had my MX510 thumb buttons up and running in "vanilla" Dapper.

Just the same, I'd be interested to know how a fix might be effected.

[pwner4once]

Well I am sure it's a compatibility issue between Dapper and XGL. I am using Dapper 6.04 right now and all my side buttons are working. I am using Logitech MX510.

Hearing about the no side button news, it makes me want to avoid trying out XGL.

btw regarding the guide. Everyone is using Option "Protocol" "evdev" and seem to be working for you guys. Well for me, I would get something saying evdev doens't exist and such. Think this is rather a Dapper issue. anyways, it works flawless even if you use Option "Protocol" "ExplorerPS/2"

so try that if u can't get X working again with evdev.

alright, my mouse is finally working. WOOT! thanks to all contributers :D

[kayrune]

The evdev, buttons not working is a XGL issue, it has nothing to do with ubuntu/dapper. The same thing happens on Gentoo.

[beerorkid]

I have not gotten all of it to work correctly yet, still messing with it.

but from this post: http://ubuntuforums.org/showthread.php?t=135360

good ol xmodmap like back in hoary.

I at one time had the two buttons on the top and bottom of the wheel to work like page forward/backward, but the wheel did the same as well.

I am hoping that I can get it to work with dapper/XGL
will let you know if I do.

mx510

[makhand]

Ok, there are a couple of big problems that i'm having that I think are quite ridiculous. I'm using an MX1000

1. If i dont have the mouse plugged in when I start up, X crashes. I have to plug the mouse in to get my laptop to work now. Pretty annoying

2. I have a dual monitor setup. These shortcuts only work for one of the monitors!! On the laptop screen, i can side scroll and go back and forward in history, on the other monitor (crt), i get none of this functionality.

any ideas?

[tellnes]

The guide worked great! thanx alot:)

However i cannot install the logitech applet..

When i try to apt-get install checkinstall build-essential libusb-dev
I know the output is in Norwegian, however, it basically says some of the packages it needs is still under "incomming", while in synaptic it says it is installed.
------------------------------------------------------------------
i get this meesage: Les pakkelister ... Ferdig
Byggjer kravtre ... Ferdig
Nokre av pakkane kunne ikkje installerast. Dette kan koma av at du har
valt ein umogleg situasjon. Dersom du brukar den ustabile utgåva av
distribusjonen, kan det òg henda at nokre av pakkane som trengst ikkje
er laga enno eller at dei framleis ligg i «Incoming».
Følgjande informasjon kan hjelpa med å løysa situasjonen:

Følgjande pakkar har krav som ikkje er oppfylte:
libusb-dev: Krav: libusb-0.1-4 (= 2:0.1.10a-17ubuntu1) men 2:0.1.11-6 skal installerast
-------------------------------------------------------------------

Seems like i have a wrong ver of libbus, i have the 2.0.1.11-6, but it says in the output its gonna be installed..

Anyone know howto get the right ver of libus installed without meesing up everything leaving me with a system without mouse;)

[sYs^]

Not sure whats up, i followed the guide to a t, but for whatever reason, when i start X, i get

Unknow Protocol "evdev"

Im using a MX700 and set it up according to how others have done it also.

thanks

I have the same problem with MX510, any ideas?

[Corbelius]

I have the same problem with MX510, any ideas?

Run modprobe -l in console and check if u have evdev driver, example:

/lib/modules/2.6.15.5-ck7-ubuntu/kernel/drivers/input/evdev.ko

Put "evdev" string in ur /etc/modules and try again.

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

evdev
#lp
#mousedev
#psmouse
#rtc
#sbp2
#sr_mod
#usbcore
#sd_mod

[sYs^]

Thanks for the answer, but

I had evdev in modules, there was another problem (just figured out, in this minute:p) , I had to change the xorg.conf:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
# Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-*/input2"
Option "Device" "/dev/input/event0"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection


But there's still another problem, if I scroll up fast in FireFox (1.5.0.1 swiftfox) it goes back one page.

[detyabozhye]

Works awesomely! Now, what should I map button 8 to? hmm...

"/usr/bin/dominate_the_world -muahahahahaha""
m:0x0 + b:8

[irjason]

I have a Logitech MX518. By following these directions I was able to get it working. However, I use an Iogear MiniView USB KVM switch to change between my Ubuntu PC and my XP box. When I would toggle PC's the mouse would not respond while I was using the evdev protocol. It seems the KVM causes problems here.
I discovered that if I used "ExplorerPS/2" all buttons work, and the mouse continues to work when I toggle back and forth with the KVM.
Below is the mouse section of my xorg.conf in case anyone else is having this problem.


Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "CorePointer"
Option "Dev Phys" "usb-*/input0"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection

[detyabozhye]

When I set it up, I had a problem, like someone else here, that when scrolling up using the cruise control button, it would also select text, and the button acted like a left-click as well as scroll up. in xev it would report it as button 4 and 10, I fixed it by changing:

Option "ZAxisMapping" "4 5"
to:

Option "ZAxisMapping" "4 5 9 10"

[scooper]

I have a Logitech MX518. By following these directions I was able to get it working. However, I use an Iogear MiniView USB KVM switch to change between my Ubuntu PC and my XP box. When I would toggle PC's the mouse would not respond while I was using the evdev protocol. It seems the KVM causes problems here.
I discovered that if I used "ExplorerPS/2" all buttons work, and the mouse continues to work when I toggle back and forth with the KVM.


I have the same mouse and the same problem when using a KVM. The mouse just freezes when I switch back to the Linux session using evdev. One time it did recover somehow, but other times it didn't.

Is there a way to force it to recover? I could tolerate binding a script to a key and restarting the mouse manually.

Otherwise what does the ExplorerPS/2 setup look like? Does it require xmodmap?

I mainly wanted to confirm another KVM problem with this great solution. I'll search for an answer in the meantime.

Cheers,
Steve

[evergreen]

Hi I have a mx518 when I run "cat /proc/bus/input/devices" in terminal I get this

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

so I tryed this in my config

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB-PS/2 Optical Mouse"
Option "Dev Phys" "usb-0000:00:02.0-2/input0"
Option "Device" "/dev/input/event1"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
EndSection

This doesn't work

I don't see anyone getting S: Sysfs=/class/input/input1 when they run "cat /proc/bus/input/devices"

What is S: Sysfs=/class/input/input1 and do i need to add it to my config somehow? Any help would be great, thanks

[Baikonur]

Could someone help please, I have an mx500, but when I use the xorg.conf configures given, I get a kernel panic, saying "0Kernel panic - not syncing: Fatal exception in intterrupt".

[beerorkid]

well I found a simple fix for me mx510, XGL, dapper only works in dapper

from trorion here: http://ubuntuforums.org/showthread.php?t=150116&highlight=mx510

make your xorg.conf have this in it. Of course comment out your currently working one just in case ;)
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "false"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7"
Option "Resolution" "800"
EndSection

As trorion mentions, make sure that this line: Option "Device" "/dev/input/mice" matches your old working line

[gamerzl]

does this work in kubuntu?

[detyabozhye]

100% sure it should work, that file is the Xorg configuration, if the config works, it'll work regardless of the desktop environment.

[evergreen]

Thanks beerorkid I Tryed out your config & It works great In Firefox, Giving the forward & back page functions :-D Gonna have a play about to try & get it working in Nautilus.

[beerorkid]

well the thanks goes to trorion (http://ubuntuforums.org/member.php?u=72350)

I was home nursing a sprained ankle and decided I was gonna figure out the last little thing that bugged me.

Glad it is working for others.

[mfarley]

Has anone been able to get speed / acceleration working using an xorg.conf like this?


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


I've tried both driver "mouse" and driver "evdev" -- no matter what happens I can't change the resolution / speed / accel.

I'm using a PS/2 mouse.

[evergreen]

Hi mfarley just to let you know the above config allows me to change my resolution with the two arrow buttons above & bellow the scroll wheel to the three different settings i think 400/800/1200? I'm kind of new to linux so I don't know how much I can help. The only thing I see is I have my mouse plugged into a USB port not PS/2

[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:

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:

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! :P

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

[whector]

hi! does anyone know how to get mx700 work in Dapper?

[antidrugue]

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.


I tryed numerous complicated guides as well, without much success (some combinations of udev, evdev, xbindkeys, etc.).


My current /etc/X11/xorg.conf contains an InputDevice section as follows:

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

WOW! That works!

Many thanks to you, "PsychoBrat". That was EXACTLY what I was looking for.

Works perfectly with my Logitech MX500, on Debian Etch (KDE 3.5.2).

[Craig Caldwell]

I tryed numerous complicated guides as well, without much success (some combinations of udev, evdev, xbindkeys, etc.).



WOW! That works!

Many thanks to you, "PsychoBrat". That was EXACTLY what I was looking for.

Works perfectly with my Logitech MX500, on Debian Etch (KDE 3.5.2).
PsychoBrat's method got my mx700 mouse working in firefox but not nautilus.
I'll try the xbindkeys method next but I'm not sure it works with dapper 64.

[Craig Caldwell]

Ok the xbindkeys method does work with 64 bit dapper.

[Grimmy]

I should start reading howto threads backwards!

Thanks PsychoBrat.. This worked fine for my MX518 under Dapper Flight 6:


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


Now maybe I can help you:


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)?

I got it working in Nautilus using the following from the first post:


1. xvkbd and xbindkeys

Lets install "xvkbd" and "xbindkeys":

sudo apt-get install xvkbd xbindkeys Next we need to create the configuration for them:

gedit ~/.xbindkeysrc Now paste the following:

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7

Please note, the "L" and "R" from the words "left" and "right" in the square brackets above should be capitalised, this seems like a bug in the forums here that they don't display properly.

Make sure you keep the quote marks, save the file and run "xbindkeys" in the terminal. It runs as a daemon in the background. You should now be able to test if it works in Nautilus by using the side buttons it also works in Epiphany if you use it.

[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:

xbindkeys -X :0.0
xbindkeys -X :0.1

[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:
cat /proc/bus/input/devices
Here's my output with the info I need in bold:
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:
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):
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:
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:
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:
cd ~/click
make
Then I changed my ~/.xbindkeysrc to include this:
"~/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.

[ashrack]

I ahve a MS INTELLI MOUSE OPTICAL. And my side 2buttons work great in FIREFOX. But I still want them to work in NAUTILUS so I followed the following guide to the letter:
A complete guide to a Logitech mouse

Section 2: Side buttons and Nautilus
We can use "xvkbd" and "xbindkeys" to bind the side mouse buttons to "ALT + LEFT" and "ALT + RIGHT" so they work as forward and backwards in Nautilus.


I have a MICROSOFT INTELLIMOSE OPTICAL. And I got side buttons working great in Firefox. So then I wanted them to also work in NAUTILUS. So I followed this guide:
1. xvkbd and xbindkeys

Lets install "xvkbd" and "xbindkeys":

sudo apt-get install xvkbd xbindkeys Next we need to create the configuration for them:

gedit ~/.xbindkeysrc Now paste the following:

"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:6
"/usr/X11R6/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:7

Please note, the "L" and "R" from the words "left" and "right" in the square brackets above should be capitalised, this seems like a bug in the forums here that they don't display properly.

Make sure you keep the quote marks, save the file and run "xbindkeys" in the terminal. It runs as a daemon in the background. You should now be able to test if it works in Nautilus by using the side buttons it also works in Epiphany if you use it.

[I]Note: Same as before, if you have different mouse buttons use xev to find out what number they are and change the "b:6" and "b:7" in the above to the correct numbers.

But they dont work and even worse also they stop working in FF!
This is my XEV output when pressing the side buttons:
ButtonPress event, serial 26, synthetic NO, window 0x3600001,
root 0x4c, subw 0x0, time 3488431120, (86,50), root:(493,393),
state 0x10, button 6, same_screen YES

ButtonRelease event, serial 26, synthetic NO, window 0x3600001,
root 0x4c, subw 0x0, time 3488431272, (86,50), root:(493,393),
state 0x10, button 6, same_screen YES

ButtonPress event, serial 26, synthetic NO, window 0x3600001,
root 0x4c, subw 0x0, time 3488431560, (86,50), root:(493,393),
state 0x10, button 7, same_screen YES

ButtonRelease event, serial 26, synthetic NO, window 0x3600001,
root 0x4c, subw 0x0, time 3488431712, (86,50), root:(493,393),
state 0x10, button 7, same_screen YES

and my XORG.CONF
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
#for IntelliMouse's 7 buttons
Option "Buttons" "7"
Option "ButtonMapping" "1 2 3 6 7"

ps. Am using DAPPER BETA! Could this be the cause for it not workin?
ps2. In NAUTILUS I checked if ALT_L and ALT_D if they go back and forth and they do