Hi!

Im running a Debian Etch with a MX-518 mouse. I followed the instructions of the how-to "Get all mouse buttons working". But still not all buttons work. The bottons above and bellow the scrollwheel ("+" and "-") won't issue an event when tested with xev
here the relevant part of my 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:11.2-1/input0"
Option "Device" "/dev/input/mice"
Option "Buttons" "10"
Option "ZAxisMapping" "4 5"
Option "Resolution" "800"
EndSection

Anyone any luck with the MX-518?

THX

timmy

have a look at: http://lomoco.linuX-gamers.net

unfortunately we've got problems with our svn server, you can find a package of the source at: http://piie.net/index.php?section=lomoco

Thanks!

"lomoco -p c01e --no-sms" and a xserver restart solved the problem.

Quote:

Shouldn't you be using one of the /dev/input/event* devices instead of /dev/input/mice when using the evdev protocol?

Quote:

I had a closer look to the lomoco source and realized that for the MX518 the sms feature is not yet implementet . I guess the only feature to the MX518, changing the resolution, somehow "woke up" the buttons. Now again only the front one "+" works . I checked out the new proposition by ZlatkO. The change to the event device should help because a "cat /dev/input/event1" responds to all button clicks with some output.
Just to lazy to restart my Xserver at the moment .

Thank you for all suggestions

timmy

Ok, here is my final solution and ALL buttons work!

Prerequisites:
- Kernel module: evdev (>=2.6.?)
- evrouter:evrouter

xorg.conf:
Quote:
As you can see from the xorg.conf I pretend to the X manager having only a 5 button mouse. This was necessary because some software like my browser already implement more than 5 buttons and my initial mapping got lost.

My evrouterrc looks like this:
Quote:

If you want your mouse buttons setup on x manager start use the following skript. In the gnome case, add a line like sh /path/to/home/.evrouterstart into the gnome-session-properties
evrouterstart:
Quote:

Happy mousing

Timmy

Hoi!

I tried using your solution to the problem but it wont work correct for me. I encountered several problems... maybe someone can help me.

First: my Mouse seems to give signal to /dev/input/event2 (this event device writes crap to the console as soon as I move my mouse if I cat it). The problem with this is, that this device (among others) has restricted rights to users except root. They cannot read from it. I tried chmod it to 664 which worked fine but after restarting the machine the chmod was lost - access was 660 only. What happened here?

Second: I set up everything just as you described (except I changed event1 to event2 everywhere it occured). Basicly some of the mouse functions seem to work. I changed the "top button" command to Shell/aterm which works fine if evrouter is running. However, the other buttons dont funtion as described in .evrouterrc. The Left Up and Down buttons function as if they where Button 1 and 0 (If pressed in the WM eg they open context menus etc) and the + and - buttons dont do anything at all (evrouterrc is configuted to let them raise and lower volume, just as in your example; yes, I'm using alsa as my sound system). How is this?! Can anybody help solving my problems?

Thanks alot,

Daniel

PS: I played a little more around trying to gather some more information and here is what I found out:

If I test my mouse functions using xev, input is recognized upon pressing the top button, the buttons on the left side and the 3 "normal" buttons (including middle "mouswheel button"). However these 6 buttons only provide 3 different signals. Each of the "normal" buttons functions is also provided by another of the 3 other buttons (Top button, 2 Left buttons). Mouswheel Up and Mouswheel Down is recognized as button 4 and 5. The + and - buttons are not recognized at all, the - button is not even recognized by cat /dev/input/event2, some output is provided through the + though.
Another thing I recognized is, that my rules for the buttons xev recognizes are executed correct (not only shell commands but also XKey commands eg). However, not only the evrouter commands are executed but alos the normal button behaviour (eg if I press the Left Back button, my WM cycles to the next window [which is the behaviour I assigned through evrouterrc) but there are also popup menus opened (which is the behaviour for button2, which is double assigned through the Left Back button). I hope you understand my explenation :)

Hi theSorcerer,

I've experienced exactly the same problems, but I did make one step further. I disabled the "double" action (that is, when a click on a button caused two actions, one by evrouter and one by X server).

Here is my input section:
Section "InputDevice"
Driver "mouse"
Identifier "Mouse[3]"
Option "Buttons" "7"
Option "Device" "/dev/input/mice"
Option "Name" "ExplorerPS/2 on USB"
Option "Protocol" "ExplorerPS/2"
Option "Vendor" "USB-Mouse"
Option "ZAxisMapping" "4 5"
EndSection

"+"/"-" button still don't send any events, but they actually do some other job. They silently change CPI! As you press "+" your cpi increases (mouse gets faster), as you press "-" your cpi decreases (mouse gets slower).

As for now, all buttons work exactly as described in file .evrouterrc
and I am happy about it.

My distro is full SuSE 10.0 with default 2.6.13-15 kernel.

I still haven't rebooted my computer, but I suspect my "chmod 644 /dev/input/event3" will disappear (like in your case) and I'll have to do it again after reboot.

Yeah, the same problem. Privileges on /dev/input/event3 become crw-rw----.

There are two different ways to fix it. Both are quite ugly in terms of security:
FIRST WAY:
Set GUID bit of /usr/bin/evrouter
Quote:

That's it! Now evrouter has access to /dev/input/event* since it is now a member of root group

SECOND WAY:
Create a small prog that will change privileges for you.
I created a simple file, called enable_event3.c:
Quote:

In order to compile it just run
Quote:

Then copy the enable_event3 executable somewhere to /usr/local/bin, change owner to root and (the most dangerous part!!) set suid flag
Quote:

Now you are able to change privileges of the file without logging in as root and without running evrouter as member of root group.

This is not pretty solution, but I don't know the pretty way to change default privileges of /dev/input/event* to something that we need.

I believe i have a similar problem with the MX518. Lomoco works fine up to 800dpi. But, if you try to set it to 1200 or 1600 dpi, the sensitivity buttons +/- no longer function correctly. + becomes a mouse3, and I think - does nothing.

Any ideas?

I don't really need to remap the +/-... i'd like them to work as sensitivity buttons still :).

Does anyone have the lomoco svn/git because i don't really feel inclined to copy and paste out of trac...

Cheers.