Logitech mx1000 under Ubuntu 6.06LTS (Dapper Drake)
Most stuff on my mx1000 worked fine from install in ubuntu, all except the forward, back & task buttons, heres how i got them working:
step 1: install dependencies
sudo apt-get install xorg-dev xserver-xorg-dev xbindkeys xvkbd build-essential
step 2: edit /etc/udev/rules.d/01_mx1000.rules
sudo gedit /etc/udev/rules.d/01_mx1000.rules
Paste in the following, then save:
ACTION==”add”,
KERNEL==”event*”,
SUBSYSTEM==”input”,
SYSFS{manufacturer}==”Logitech”,
SYSFS{product}==”Logitech USB Receiver”,
NAME=”input/mx1000″
Then restart udev:
sudo /etc/init.d/udev restart
Re-plug your mouse, and check if its device node is there
parag0n@Aura:~$ ls /dev/input/ event0 event2 event3 event4 mice mouse0 mx1000 ts0
It is, so we can carry on…
step 3: edit xorg
sudo gedit /etc/X11/xorg.conf
Change the “Configured Mouse” Device section to read:
Section "InputDevice" Identifier "MX1000" Driver "evdev" Option "CorePointer" Option "Name" "Logitech USB Receiver" EndSection
and change DefaultMouse in the server section to “MX1000″
Save and exit.
step 4: edit ~/.xbindkeysrc
sudo gedit ~/.xbindkeysrc
Paste in the following:
# Activate Backward and Forward buttons "xvkbd -text "[Alt_L][Left]"" m:0x10 + b:8 "xvkbd -text "[Alt_L][Right]"" m:0x10 + b:9 # This enables the click up / down buttons to move you further: "/usr/bin/click 4" m:0x10 + b:11 "/usr/bin/click 5" m:0x10 + b:12 #I take lots of screenshots, so i mapped the middle button of forward / back to printscreen "gnome-screenshot" m:0x10 + b:10
step 5: make gnome run xbindkeys at startup
edit ~/.gnomerc
gedit ~/.gnomerc
And add:
xbindkeys
step 6: compile click
now we are going to make ‘click’, the program that makes the scroll wheel work properly:
wget http://www.ussg.iu.edu/hypermail/linux/kernel/0504.0/1371/click.tgz tar xzf click.tgz cd click make sudo cp click /usr/bin/click
reboot, and enjoy!
Thanks to Jürgen Kreileder, for his blog entry that this is based upon, and various other places i found while trying to fix the problems i had with his config.

September 24th, 2006 at 12:35 am
Hi, I am stuck right before the point three. When re-pluged my mouse, and typing ls /dev/input/ could not find the node with MX 1000 got this:
anthony@anthony-desktop:~$ ls /dev/input/
event0 event1 event2 mice mouse0 ts0
I don’t know why I cannot get it but the file in /etc/udev/rules.d/01_mx1000.rules does exist, so I tried to reboot without result. Could it be wrong that when the mouse was installing first it was in PS2 socket? Plugged latter in usb got this
anthony@anthony-desktop:~$ ls /dev/input/
event0 event1 event2 event3 event4 mice mouse0 mouse1 ts0 ts1
I am not sure if I can carry on. Running ubuntu on amd64. Thanks for any help
October 1st, 2006 at 12:24 am
nobody? :s
October 1st, 2006 at 12:42 pm
I’ve heard that on some people’s mice, the line
SYSFS{product}==”Logitech USB Receiver”
needs to be
SYSFS{product}==”Logitech USB RECEIVER”
See if that helps.
I’m not sure exactly why it changes depending on the version of the receiver, but hopefully that should help.
Sorry i missed your post, i normally get emailed about them, but i diddn’t :/
October 4th, 2006 at 11:39 pm
I tried to changed it to Logitech USB RECEIVER but then realized that :
I know where might be the problem! I’ve got Logitech Cordless Desktop MX3100.
Although there is MX 1000 packed I completely forgot about the keyboard (It sounds stupid but it sometimes happens). There is one Cordless Desktop Receiver (C-B 034) but for both keyboard and MX1000 which is where it may be cousing the trouble.
I am sorry for previous post but thank you for any other idea how to get it work altogether. Cheers
October 17th, 2006 at 8:53 pm
Hi, I also tried to install my MX1000 correctly on linux. Of course, the standard buttons work fine. After step 2, I got stuck, I can’t find the mx1000 in udev
I exactly did what was written, so I don’t know what to do now. Could someone help please
Thx
October 17th, 2006 at 10:31 pm
You should check your /proc/bus/usb/devices, and check for an entry that looks like:
I have highlighted the bits you’re interested in, its these you need in your /etc/udev/rules.d/01_mx1000.rules file
October 18th, 2006 at 4:20 pm
I did just the thing you said. The /proc/bus/usb/devices file looked quite similar, I filled in the manufacturer and the product, but still my mouse doesn’t show up in de udev listing. Even worse, my mouse is starting to jump around my screen and react very weird on my clicks. Linux is fine, but configuring a mouse is easier in Windows.
Help? Anybody?
October 20th, 2006 at 5:11 pm
I’m having an unrelated problem with gcc and compiling click.
i get:
[code]m3r1k@reborn:~/click$ make
gcc -Wall -o click click.o -L /usr/X11R6/lib/ -lX11 -lXtst
/usr/bin/ld: cannot find -lXtst
collect2: ld returned 1 exit status
make: *** [click] Error 1
[/code]
I dunno what -lXtst is
November 2nd, 2006 at 2:02 pm
Cudaman73: did you definately install the development packages for your xserver? if you are using xfree86, you’ll need different packages, if not, step 1 should be sufficiant to install them.
November 23rd, 2006 at 8:40 pm
I had same problem than anthony. If you copy-pasted the udev rule in step 2, just replace all ” signs. It’s not ascii character ” if you copy-paste. And try again, works for me. It’s not really nice to use something different (??unicode??) than ascii characters in code sections of webpages.
April 4th, 2007 at 5:45 pm
I’ve tried just about every guide I could find, and cannot get my MX1000 to be recognized and all buttons to work. By default only some of the buttons work for me.
My xorg.conf has this input device assigned
Section “InputDevice”
Identifier “Mouse1″
Driver “evdev”
Option “Name” “Logitech USB Receiver”
Option “Resolution” “800″
Option “Emulate3Buttons” “no”
Option “ButtonNumber” “12″
Option “Buttons” “12″
Option “ButtonMapping” “1 2 3 8 9 10 11 12″
Option “ZAxisMapping” “4 5″
Option “XAxisMapping” “6 7″
EndSection
But I get this error in the xorg log. So far every config I’ve tried has led to this error.
(II) evdev brain: Rescanning devices (1).
(EE) PreInit returned NULL for “Mouse1″
July 12th, 2007 at 11:47 pm
[...] using xmodmap: pointer = 1 2 3 4 5 7 6 The back and forward buttons can be used with a rather ugly workaround by Bob Clough (though others have come up with the same [...]