View previous topic :: View next topic |
Author |
Message |
Jonas Witt n00b
Joined: 15 Apr 2003 Posts: 43 Location: Leipzig (Germany)
|
Posted: Fri Sep 03, 2004 5:04 pm Post subject: Extra buttons of the MX1000 |
|
|
Hi,
today I got my new Logitech MX1000. First I have to say that I'm impressed by this nice mouse. Now I am trying to get the extra buttons to work in X11, which does not seem to be easy.
Whatever I try, the 3 buttons on the left side only produce mouse events with button = [1,2,3], and the two buttons beside the wheel only produce events 4 and 5, which lets you use them like a scroll wheel. However, I can't get them to produce 'their own' events. From my xorg.conf:
Code: | Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "6 7"
Option "Buttons" "7"
EndSection |
Has anyone already made experiences with this mouse and got the buttons to work? |
|
Back to top |
|
|
MetatronX99 n00b
Joined: 24 Jul 2004 Posts: 70 Location: Warren, MI
|
|
Back to top |
|
|
bastiaannaber n00b
Joined: 03 Sep 2004 Posts: 1
|
Posted: Fri Sep 03, 2004 6:07 pm Post subject: |
|
|
I also bought an MX1000 today and I am very pleased with it! I got all 12! buttons working by putting the following in my /etc/X11/XF86Config-4 (I am a debian user)
Code: |
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Protocol" "evdev"
Option "Dev Name" "Logitech USB Receiver" #cat /proc/bus/input/devices
Option "Dev Phys" "usb-0000:00:03.1-1/input0" #cat /proc/bus/input/devices
Option "Device" "/dev/input/mice" # Choose the correct input event here.
Option "Buttons" "12"
Option "ZAxisMapping" "11 12"
Option "Resolution" "800"
Option "CorePointer"
EndSection
|
After that I did:
Code: | xmodmap -e "pointer = 1 2 3 11 12 6 7 8 9 10 4 5" |
You probably will want imwheel to do something usefull with the other buttons. |
|
Back to top |
|
|
scoobydu Veteran
Joined: 16 Feb 2003 Posts: 1076 Location: 'Mind the Gap'
|
Posted: Fri Sep 03, 2004 6:17 pm Post subject: |
|
|
Think I'll wait for the bluetooth puppy to come out
Nice mouse though, what are you going to do with all those buttons! _________________ Tyan Tiger K8W, 2xOpteron 240,Powerbook5,6 15" 1.5g, Macbook Black 2g, Mac Mini 1g, Ipod P60g.
| Linux - From a windows user perspective| |
|
Back to top |
|
|
Jonas Witt n00b
Joined: 15 Apr 2003 Posts: 43 Location: Leipzig (Germany)
|
Posted: Sat Sep 04, 2004 9:56 am Post subject: |
|
|
I tried bastiannaber's solution, but my xorg-x11-6.7.0 doesn't know the protocol 'evdev'. I think that I am missing the event device support; does anyone know how I get this?
@bastiannaber: Which kernel do you use? It looks like 2.6 to me.
@MatatronX99: This is about the solution I tried. But I will try to use protocol explorerps/2. |
|
Back to top |
|
|
Jonas Witt n00b
Joined: 15 Apr 2003 Posts: 43 Location: Leipzig (Germany)
|
Posted: Sat Sep 04, 2004 10:43 am Post subject: |
|
|
Now I have
Code: | Section "InputDevice"
Identifier "MX1000_2"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/input/mice" # Choose the correct i
nput event here.
Option "Buttons" "12"
Option "ZAxisMapping" "11 12"
Option "Resolution" "800"
Option "CorePointer"
EndSection |
And without any xmodmap -e "pointer = ..." modifications I get 11 and 12 on the wheel, 4 and none on the two wheel buttons, none for the horizontal wheel, and 4, 1, 5 on the left side buttons. This means that I can at least map 11 and 12 to the forward and backward buttons. |
|
Back to top |
|
|
Archangel1 Veteran
Joined: 21 Apr 2004 Posts: 1212 Location: Work
|
Posted: Sat Sep 04, 2004 10:52 am Post subject: |
|
|
Jonas Witt wrote: | I tried bastiannaber's solution, but my xorg-x11-6.7.0 doesn't know the protocol 'evdev'. I think that I am missing the event device support; does anyone know how I get this?
|
When you compile your kernel, there's an option in Input Devices for the event protocol. I suppose you might have it compiled as a module already - if it is all you'll have to do is modprobe evdev I guess. Otherwise it's a kernel recompile. |
|
Back to top |
|
|
oberyno Guru
Joined: 15 Feb 2004 Posts: 467 Location: /bin/zsh
|
Posted: Sat Sep 04, 2004 11:09 am Post subject: |
|
|
AFAIK, you also need xorg-x11-6.7.0-r2 or newer for evdev. I have an mx700 and evdev is the only protocol that supports all the buttons, so I would imagine that evdev would be the only protocol that would properly support the mx1000. |
|
Back to top |
|
|
Jonas Witt n00b
Joined: 15 Apr 2003 Posts: 43 Location: Leipzig (Germany)
|
Posted: Sat Sep 04, 2004 12:04 pm Post subject: |
|
|
OK, I have the evdev module now; thanks for pointing that out, Archangel1.
Anyway, oberyno is apparently right, because xorg-x11-6.7.0 won't use the evdev protocol for me. Now I have to wait a few hours to test -r2. |
|
Back to top |
|
|
Jonas Witt n00b
Joined: 15 Apr 2003 Posts: 43 Location: Leipzig (Germany)
|
Posted: Sat Sep 04, 2004 2:47 pm Post subject: |
|
|
Wow! With xorg-x11-6.7.0-r2 and evdev all 12 buttons of this great piece of hardware work. Time to fire imwheel up. Thanks, boys! |
|
Back to top |
|
|
Jonas Witt n00b
Joined: 15 Apr 2003 Posts: 43 Location: Leipzig (Germany)
|
Posted: Sun Sep 05, 2004 9:36 am Post subject: |
|
|
Grmpf. When using the evdev protocol, my mouse hangs about every 5 minutes. Switching to console and back solves the problem for the next few minutes. Any ideas? |
|
Back to top |
|
|
Illissius Guru
Joined: 31 Jul 2004 Posts: 395 Location: Hungary
|
Posted: Sun Sep 05, 2004 10:38 am Post subject: |
|
|
I'm using evdev with an MX500 and don't have that, so no idea what could be causing it. Isn't it just the mouse powering down to conserve batteries? |
|
Back to top |
|
|
Jonas Witt n00b
Joined: 15 Apr 2003 Posts: 43 Location: Leipzig (Germany)
|
Posted: Sun Sep 05, 2004 11:05 am Post subject: |
|
|
Are you using the XFree or X.org's Server? |
|
Back to top |
|
|
ashtray n00b
Joined: 31 Jan 2004 Posts: 8
|
Posted: Mon Sep 06, 2004 11:07 am Post subject: |
|
|
I just got my MX1000 today and I am wondering if anybody got it working right. All 12 buttons are working but CruiseControl returns two events: button 4,7 and 5,8. Is it possible to get horizontal scrolling? |
|
Back to top |
|
|
Illissius Guru
Joined: 31 Jul 2004 Posts: 395 Location: Hungary
|
Posted: Mon Sep 06, 2004 12:59 pm Post subject: |
|
|
Jonas Witt wrote: | Are you using the XFree or X.org's Server? |
X.org 6.70r2 _________________ Work is punishment for failing to procrastinate effectively.
last.fm |
|
Back to top |
|
|
alv n00b
Joined: 06 Sep 2004 Posts: 58
|
Posted: Mon Sep 06, 2004 5:10 pm Post subject: |
|
|
ashtray wrote: | I just got my MX1000 today and I am wondering if anybody got it working right. All 12 buttons are working but CruiseControl returns two events: button 4,7 and 5,8. Is it possible to get horizontal scrolling? |
Could it be the same bug that I have with the new MS mouse?
https://bugs.gentoo.org/show_bug.cgi?id=62920 |
|
Back to top |
|
|
Jonas Witt n00b
Joined: 15 Apr 2003 Posts: 43 Location: Leipzig (Germany)
|
Posted: Mon Sep 06, 2004 7:04 pm Post subject: |
|
|
Illissius wrote: | Jonas Witt wrote: | Are you using the XFree or X.org's Server? |
X.org 6.70r2 |
Hm, exactly the same that I am using. I'll try other kernels, which one are you using?
To answer your last question: Yes, the mouse is powering down but comes back up very quickly. This is definitely not the problem.
Horizontal scrolling: I may be wrong, but I thought that this was not possible with Linux atm. If I am wrong, how does one achieve horizontal scrolling? |
|
Back to top |
|
|
Illissius Guru
Joined: 31 Jul 2004 Posts: 395 Location: Hungary
|
Posted: Tue Sep 07, 2004 3:52 pm Post subject: |
|
|
I'm currently on 2.6.8-nitro5, but have used it with a lot of kernels without any issues (multiple iterations of nitro, 2.6.7-ck5, and a few xx-sources as well).
Note that I'm using an MX500 though.
Horizontal scrolling: X recognizes vertical scrolling as merely two extra buttons... doesn't it do the same for horizontal? _________________ Work is punishment for failing to procrastinate effectively.
last.fm
Last edited by Illissius on Tue Sep 07, 2004 3:53 pm; edited 1 time in total |
|
Back to top |
|
|
alv n00b
Joined: 06 Sep 2004 Posts: 58
|
Posted: Tue Sep 07, 2004 3:53 pm Post subject: Horizontal scrolling |
|
|
Quote: | Horizontal scrolling: I may be wrong, but I thought that this was not possible with Linux atm. If I am wrong, how does one achieve horizontal scrolling? |
EDIT: I believe that you NEED evdev XMouse driver. IMPS/2 does not support it.
I think KDE/QT by default will treat buttons 6 7 as horizontal scroll wheel. So if you would map the wheel to those keys, it would cause the window to scroll. Try it in konq, if you have those buttons. (Konq treats 8 9, as forward back.)
EDIT: Never said how to actually do it.
Just set ZAxisMapping to "a b c d", where a b c d are unused buttons Then proceed to use xmodmap to remap those to 4 5 6 7. This should give you side scrolling in KDE.
Funny, but it seems that this goes very much against what mozilla is doing, causing my side scrolling to be interpreted as forward and back. Not sure what it thinks of the buttons 8 9.
I am sure there is a configuration for this somewhere. |
|
Back to top |
|
|
Ghostryder Apprentice
Joined: 10 Dec 2003 Posts: 216
|
Posted: Wed Sep 15, 2004 5:28 pm Post subject: |
|
|
Well,
I have bought the MX1000 too. I tried using the "evdev"-Protocoll, but when I use it the wheel doesn't do anything. I changed "ZAxisMapping" to different values but that doesn't change the situation.
The mouse works with ExplorerPS/2. But the horizontal buttons don't work.
My X-Free Version is 4.3.0-r6. Has anybody got a solution for the horizontal feature? Or can anybody tell me how to use the "evdev"-Protocoll correctly....
thanks g. |
|
Back to top |
|
|
alv n00b
Joined: 06 Sep 2004 Posts: 58
|
Posted: Wed Sep 15, 2004 6:03 pm Post subject: evdev |
|
|
You should really switch to X.org....but anyway. IIRC the xfree was also patched to provide evdev, but if you get messages saying that evdev protocol is not recognized, you should upgrade to the newest xorg or xfree.
My xorg.conf (XF86Config equivalent)
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
# The mouse protocol and device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.
Option "Protocol" "evdev"
Option "Device" "/dev/input/event1"
Option "Buttons" "9"
Option "ZAxisMapping" "6 7 8 9"
Option "Dev Phys" "usb-0000:00:10.1-1/input0"
EndSection
Dev Phys or Device need to be specified (and need to match).
Ideally you should use just the Dev Phys. That way the driver will find the right event file to use.
Buttons needs to be specified to the number of buttons + 4 for the tiltwheel.
(Your numbers will differ -- my mouse is actually MS Wireless IM Explorer v2)
The hardware will map the actual buttons into buttons 1 through X.
This means that you should pass "X+1 X+2 X+3 X+4" to the ZAxisMapping.
Sometimes the hardware will map the buttons into non-consecutive button numbers, in which case you should use the gaps. The main point is to give nonused buttons for the Zaxismapping, or you will start mixing them.
After that you should use
Code: | xmodmap -e "pointer = ..." |
to remap the buttons, so that the wheel becomes buttons 4 5, the tilt becomes buttons 6 7, and the other buttons fall in the right place as well. Notice that the tilt has no dedicated place. KDE/QT assume that tilt is 6 7, while mozilla will think that 6 7 is a forward / back. Use imwheel to assign keyboard commands to the buttons on a per application basis.
Furthermore, I am not certain whether the logitech mouse driver actually supports tiltwheel. I also do not believe that MX1000 uses the usbhid driver. So I can not tell you anything about it. If the tiltwheel is not mapped to the REL_HWHEEL event in the linux input driver, then there is no chance that it will work.
In short..you need REL_HWHEEL support in the kernel, and evdev driver to be able to use HWHEEL events to use the tilt.
Oh and please persuade people to fix this bug. https://bugs.gentoo.org/show_bug.cgi?id=62920
It is very annoying . And it will affect your "scroll accelerator" buttons or whatever logitech calls them. |
|
Back to top |
|
|
Ghostryder Apprentice
Joined: 10 Dec 2003 Posts: 216
|
Posted: Thu Sep 16, 2004 10:12 am Post subject: |
|
|
Thanks at first for your answer!
But I don't know exactly where to get the "Dev Phys". An output of lsusb gives me that:
Bus 004 Device 002: ID 0a81:0101 Chesen Electronics Corp.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 006: ID 046d:c50e Logitech, Inc.
Bus 001 Device 002: ID 05e3:0660 Genesys Logic, Inc.
Bus 001 Device 001: ID 0000:0000
Do I have to take it from here? (it looks kinda different than yours)
And "cat /dev/bus/usb/devices" gives me that:
.......
T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 6 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=c50e Rev=25.00
S: Manufacturer=Logitech
S: Product=USB Receiver
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 70mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
So I think the usbhid are in use... Any suggestions?
thanks a lot! |
|
Back to top |
|
|
Jonas Witt n00b
Joined: 15 Apr 2003 Posts: 43 Location: Leipzig (Germany)
|
Posted: Thu Sep 16, 2004 3:13 pm Post subject: |
|
|
From bastiaannabers config: Try
Code: | cat /proc/bus/input/devices |
|
|
Back to top |
|
|
Doikor Tux's lil' helper
Joined: 15 Dec 2003 Posts: 83 Location: Finland, Jyväskylä
|
Posted: Sun Sep 19, 2004 8:41 pm Post subject: |
|
|
Anyone know if the mx1000 goes to 800dpi on default or does it need the logitech_applet. And does the 500hz hack work on it? |
|
Back to top |
|
|
anarchist Apprentice
Joined: 12 Jul 2002 Posts: 264
|
Posted: Fri Sep 24, 2004 6:05 pm Post subject: |
|
|
It doesnt look like as if the logitech applet could switch the mx1000 to 800dpi, it says it does not support it |
|
Back to top |
|
|
|