View previous topic :: View next topic |
Author |
Message |
the_crowbar n00b
Joined: 28 Jan 2004 Posts: 21 Location: US
|
Posted: Wed Jan 28, 2004 11:42 pm Post subject: Logitech Marble Mouse USB |
|
|
Hello all,
I have been trying to get a new Logitech trackball working. I have had an older one since something like 2000 or so. The new trackball has the addition of two extra scroll buttons. Here is a link to a picture http://www.logitech.com/index.cfm?page=products/details&CRID=6&CONTENTID=5003&countryid=19&languageid=1
I am unable to get the scroll buttons to "scroll."
When looking at the mouse the two large buttons map to button 1 and 3. The left scroll button maps to button 2 and the right scroll button maps to button 3 just like the large button. I have been unable to get X to recognize each button as separate.
Here is the relavent section of my XF86Config-4 file:
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
EndSection
If anyone has any ideas on what I am missing please advice.
Thanks,
James |
|
Back to top |
|
|
CheshireCat Guru
Joined: 25 Aug 2002 Posts: 572
|
Posted: Thu Jan 29, 2004 1:34 am Post subject: |
|
|
You'll probably need to set the "buttons" option to the number of buttons (add 2 to that count for the scroll wheel). Also, ZAxisMapping AFAIK must always map to the two highest buttons. If you have a scroll wheel, normal left/middle/right buttons, and 2 extra scroll buttons, you should set buttons to 7 and zaxismapping to "6 7". You will then need to use xmodmap to remap the buttons. Add something like this to your Xsetup:
Code: | xmodmap -e "pointer = 1 2 3 6 7 4 5" |
|
|
Back to top |
|
|
fernandotcl Veteran
Joined: 20 Nov 2003 Posts: 1396 Location: Sao Paulo, Brazil
|
Posted: Thu Jan 29, 2004 2:29 am Post subject: |
|
|
Try opening a terminal, and executing xev. Adjust XF86Config according to the output of scrolling down and up each scroll. |
|
Back to top |
|
|
the_crowbar n00b
Joined: 28 Jan 2004 Posts: 21 Location: US
|
Posted: Fri Jan 30, 2004 11:35 pm Post subject: So far no luck |
|
|
The trackball ( mouse is only a part of the name) has four buttons. It has two large normal left/right click buttons and two smaller "scroll buttons" instead of a scroll wheel.
If I open an xterm and execute xev it says that the large buttons are 1 and 3. The smaller scroll buttons map to 2 and 3. So I can get mouse buttons 1, 2, 3, and 3 from the trackball.
Does anyone have any idea how to tell if the mouse is indeed sending the same signal when the large button (3) and the scroll button (3) are pressed?
Thanks,
James |
|
Back to top |
|
|
Andersson Guru
Joined: 12 Jul 2003 Posts: 525 Location: Göteborg, Sweden
|
Posted: Wed Aug 25, 2004 3:21 pm Post subject: |
|
|
Seven months later, odds are you've solved the problem yourself or returned the trackball to the store But this is a great trackball, other people will buy it and hopefully search the archives, so here's a working configuration (with an optional wheel emulation setting).
By the way, I think the duplicate buttons problem is caused by using the wrong protocol. I use "auto" and it works fine.
This configuration isn't perfect, there are a few things I need some help with: If the small buttons are used for scrolling, it would be great to be able to keep them pressed for constant scrolling (instead of having to click for each line scrolled).
The wheel emulation is a little too jerky when scrolling. It could need some tweaking as well. I may edit this post later when I've used the trackball for a while.
I use the PS2 connection, not the usb one, I don't know if the configuration would be different. Also, note that I changed the Identifier variable to MarbleMouse. You should edit the ServerLayout section to make this the default pointer or change the identifier back to mouse0. Anyway, here goes:
Code: | Section "InputDevice"
# Logitech marble mouse
Identifier "MarbleMouse"
Driver "mouse"
Option "Device" "/dev/mouse"
Option "Protocol" "auto"
Option "Buttons" "5"
# If the three lines below (Option...EmulateWheel) are
# commented out, then the device will work like this:
# Large left/right button: left/right click
# Large buttons together: middle click
# Small left/right button: scroll up/down
# If the EmulateWheel option is set, it will work this way:
# Large left/right button: left/right click
# Large buttons together: middle click
# Small left button: Keep pressed to scroll with the
# trackball
# Small right button: Button 5, use as you wish
Option "EmulateWheel" "1"
Option "EmulateWheelButton" "4"
Option "EmulateWheelInertia" "3"
EndSection |
_________________ Must...resist...posting....
One...step...closer...to...getting...stupid...l33t...ranking... |
|
Back to top |
|
|
jpalko n00b
Joined: 12 Mar 2003 Posts: 65 Location: Piispanristi, Finland
|
Posted: Tue Nov 16, 2004 10:00 am Post subject: How about PS/2? |
|
|
How about if the mouse is connected via PS/2?
Personally I seem to be able to get only 3 mouse buttons out of the Logitech® Cordless TrackMan® Optical when attaching it to PS/2 via my KVM.
Setting of Auto in Protocol makes this work and not bug out on KVM display change, but it also causes this in Xorg.0.log
Code: | (**) Option "Protocol" "Auto"
(**) kvm_logitrackman: Device: "/dev/psaux"
(**) kvm_logitrackman: Protocol: "Auto"
(**) Option "CorePointer"
(**) kvm_logitrackman: Core Pointer
(**) Option "Device" "/dev/psaux"
(**) Option "Buttons" "5"
(**) Option "Emulate3Buttons" "off"
(**) Option "ZAxisMapping" "4 5"
(**) kvm_logitrackman: ZAxisMapping: buttons 4 and 5
(**) kvm_logitrackman: Buttons: 5
(**) kvm_logitrackman: SmartScroll: 1
...
(II) XINPUT: Adding extended input device "kvm_logitrackman" (type: MOUSE)
(--) kvm_logitrackman: PnP-detected protocol: "PS/2"
(II) kvm_logitrackman: ps2EnableDataReporting: succeeded |
Which apparently throws the mouse to dumbest mode available, and thus disables the scroll wheel?
My current xorg.conf setting is (a lot of commented portions, been testing a bit):
Code: | Section "InputDevice"
Identifier "kvm_logitrackman"
Driver "mouse"
# Option "Name" "AutoDetected"
# Option "Protocol" "MouseManPlusPS/2"
# Option "Protocol" "ExplorerPS/2"
# Option "Protocol" "ImPS/2"
Option "Protocol" "Auto"
# Option "Device" "/dev/input/mice"
# Option "Device" "/dev/psaux"
# Option "Emulate3Buttons" "off"
# Option "SampleRate" "150"
Option "Buttons" "10"
# Option "EmulateWheel" "on"
# Option "EmulateWheelButton" "4"
# Option "XAxisMapping" "6 7"
# Option "YAxisMapping" "4 5"
Option "ZAxisMapping" "4 5"
Option "SampleRate" "1200"
Option "Resolution" "500"
# Option "EmulateWheelInertia" "12"
# Option "InputFashion" "Mouse"
EndSection |
Suggestions for my case? _________________ Jukka Palko
Piispanristi, Finland
Linux Counter ID #219161 |
|
Back to top |
|
|
altorus Tux's lil' helper
Joined: 17 Aug 2003 Posts: 89 Location: Melbourne, Australia
|
Posted: Tue Nov 16, 2004 1:14 pm Post subject: |
|
|
I have a working config for the cordless trackman optical. Very nice trackball, and thanks for the marble mouse solution (my old lady uses one of those)
Anyway, for the cordlesS:
Code: |
Section "InputDevice"
Driver "mouse"
Identifier "Mouse[6]"
Option "InputFashion" "Mouse"
Option "Name" "Logitech Mouseman Dual Optical"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"
EndSection
|
and for your ~/.Xmodmap
pointer = 1 2 3 6 7 4 5
Gnome and firends seem to load xmodmap on default, for other wm's just add it to your startup sequence
The only thing that doesn't work in this instance is the drag-lock button, but that i beleive is just a windows thing.
Back forward buttons work, scroll wheel/cruise control buttons work, etc. Its fully funcitonal
edit: you also need the event device kernel modules - evdev. Its under input devices if i recall correctly |
|
Back to top |
|
|
Chickpea l33t
Joined: 03 Jun 2002 Posts: 846 Location: Vancouver WA
|
Posted: Sun Jun 05, 2005 8:28 pm Post subject: |
|
|
Andersson wrote: | Seven months later, odds are you've solved the problem yourself or returned the trackball to the store But this is a great trackball, other people will buy it and hopefully search the archives, so here's a working configuration (with an optional wheel emulation setting).
By the way, I think the duplicate buttons problem is caused by using the wrong protocol. I use "auto" and it works fine.
This configuration isn't perfect, there are a few things I need some help with: If the small buttons are used for scrolling, it would be great to be able to keep them pressed for constant scrolling (instead of having to click for each line scrolled).
The wheel emulation is a little too jerky when scrolling. It could need some tweaking as well. I may edit this post later when I've used the trackball for a while.
I use the PS2 connection, not the usb one, I don't know if the configuration would be different. Also, note that I changed the Identifier variable to MarbleMouse. You should edit the ServerLayout section to make this the default pointer or change the identifier back to mouse0. Anyway, here goes:
Code: | Section "InputDevice"
# Logitech marble mouse
Identifier "MarbleMouse"
Driver "mouse"
Option "Device" "/dev/mouse"
Option "Protocol" "auto"
Option "Buttons" "5"
# If the three lines below (Option...EmulateWheel) are
# commented out, then the device will work like this:
# Large left/right button: left/right click
# Large buttons together: middle click
# Small left/right button: scroll up/down
# If the EmulateWheel option is set, it will work this way:
# Large left/right button: left/right click
# Large buttons together: middle click
# Small left button: Keep pressed to scroll with the
# trackball
# Small right button: Button 5, use as you wish
Option "EmulateWheel" "1"
Option "EmulateWheelButton" "4"
Option "EmulateWheelInertia" "3"
EndSection |
|
Yes, I am replying to an old post. After several hours of trying to get this to work, I finally was able to get this working using this configuration. I really think that the "auto" option is the key. None of the other things I tried worked for me and I was getting discouraged...until I found this answer. Thank the Lord for the "Search" function. |
|
Back to top |
|
|
zaiyon Apprentice
Joined: 19 May 2004 Posts: 219 Location: Germany
|
Posted: Tue Aug 02, 2005 3:34 am Post subject: |
|
|
Hi, I am using this Marble Mouse.
I tried all the suggestions of this thread for my mouse. If I set Protocol to "auto", only the large keys show up in xev, if I choose the mouseman protocol, it acts like this:
the large left key is button 1, the tiny left key is button 2, the large right key is button 3 and the tiny right key is also button 3. Putting the two large keys together is button 2.
Sounds just like the_crowbar's problems.
So the Protocol "auto" doesn't fit my needs. The mouse reacts exactly the same way with or without the ps/2 connector.
I fooled around a lot, but cannot figure it out. This is InputDevice Section:
Code: |
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
|
That's how it looked, before I started to tune it. And that's how it looks now. Have to get along with 2(3) Buttons.
Did anyone yet solve that Button-3-Issue? _________________ What do you have when you have six lawyers buried up to their necks in sand? Not enough sand.
My Project - open Outcast |
|
Back to top |
|
|
jpalko n00b
Joined: 12 Mar 2003 Posts: 65 Location: Piispanristi, Finland
|
Posted: Tue Aug 02, 2005 3:50 am Post subject: 3 button issue |
|
|
Well, that 3 button issue that I had was solved thus that I stopped using my KVM...
I had some small changes with monitors and now got 2 nice flat screens. I can move these babies around much easier than that previous 19" CRT. _________________ Jukka Palko
Piispanristi, Finland
Linux Counter ID #219161 |
|
Back to top |
|
|
zaiyon Apprentice
Joined: 19 May 2004 Posts: 219 Location: Germany
|
Posted: Wed Aug 03, 2005 5:24 pm Post subject: |
|
|
Well, I solved it.
I had to add:
Code: |
Option "Buttons" "7"
|
And for Scrolling:
Code: |
Option "ZAxisMapping" "6 7"
|
And now scrolling works. This is my full mouse configuration:
Code: |
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "auto"
Option "Device" "/dev/input/mice"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"
EndSection
|
Xev now recognizes 5 buttons.
the Large on the left is 1,
the Large buttons together are 2,
the Large on the right is 3,
the Small on the left is 4 and
the Small on the right is 5.
That's how it's supposed to be.
I don't understand this solution myself, why the heck does setting Buttons count to seven solve that problem? This mouse has only four buttons!
I found that solution googling, tried it out without expecting it to work.
I hope that helps some of you.
And now I hope some ouf you can help me
There are four things I would like to get to work:
1. Exchanging the buttons used for scrolling. The one with the array up is right now scrolling down. I would like to make this button scroll up and the other scroll down, but changing "ZAxisMapping" "6 7" to "ZAxisMapping" "7 6" does not change anything.
<edit>
I found a temporary usable solution for this, using Xmodmap like altorus did.
Code: |
pointer = 1 2 3 5 4 6 7
|
to ~/.Xmodmap does the trick as described above.
But I cannot accept this as an absolute solution, because there is (afaik) no global way to use Xmodmap, and this mouse is plugged in for every user and every session.
</edit>
2. I am using several USB mice, (right now 2) and I would like to use all of them at the same time. This worked fine, but now that I changed the Buttons and ZAxisMapping Options, I cannot scroll with the other mice anymore. I changed the Device for the logitech mouse specific setting to /dev/input/mouse2 and made a new section for /dev/input/mice with default settings. This does unfortunately not work. The trackball works just fine, but the other one doesn't seem to be recognized at all.
Even changing /dev/input/mice to /dev/input/mouse1 (which is not what I need, because I love to hotplug mice without restarting the XServer) doesn't solve my problem.
<edit>
I got an idea right now, but I don't know how to realise it.
xev recognizes the trackball scroll buttons as key 4 and 5, and the regular-usb-mice' mouse wheel are the keys 6 and 7.
Now I want to modify my ~/.Xmodmap to make 6 and 5 equal, 7 and 4 too.
So it could look like this:
Code: |
pointer = 1 2 3 5 4 6 7
mousebuttonassign 6 = 5
mousebuttonassign 7 = 4
|
Well, the sad thing is, that I made this mousebuttonassign-nonsense up, I could not find out how to realise something like that .... but it would be amazing, if someone could tell me.
</edit>
3. Keep scrolling when I keep the scroll keys pressed down, right now I have to keep clicking them (I often read about this problem without solution)
4. Clicking the two small buttons at the same time (and holding them down) as button for wheel emulation would be nice. (Is there some sort of ... 6-Button-Emulation? I guess not ...) _________________ What do you have when you have six lawyers buried up to their necks in sand? Not enough sand.
My Project - open Outcast |
|
Back to top |
|
|
zaiyon Apprentice
Joined: 19 May 2004 Posts: 219 Location: Germany
|
Posted: Sat Apr 22, 2006 12:07 am Post subject: |
|
|
Another resurrection for this zombie thread.
I upgraded to xorg 7, and now my marble mouse seems to be messed up. I didn't change my mouse configuration, here it is again:
Code: |
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"
EndSection
|
Scrolling doesn't work anymore. If I try to run my usual xmodmap line (pointer = 1 2 3 5 4 6 7), xmodmap complains that this mouse has 11 and not 7 buttons (it still has only 4 in reality), and xev shows my scroll buttons (that have been 4 and 5 until now) as 8 and 9.
I tried to fool around with the X configuration and xmodmap, but couldn't solve it. This is what I tried:
- Removing and changing the button number in xorg.conf
- Removing and changing the zaxismapping in xorg.conf
- trying around with xmodmap. this line: "pointer = 1 2 3 8 9 4 5 6 7 10 11" makes the buttons be recognized as 6 and 7, but still not as 4 and 5.
Ideas anyone? I'm stuck. _________________ What do you have when you have six lawyers buried up to their necks in sand? Not enough sand.
My Project - open Outcast |
|
Back to top |
|
|
davidgurvich Veteran
Joined: 23 Apr 2004 Posts: 1063
|
|
Back to top |
|
|
JohnY Guru
Joined: 26 Jul 2002 Posts: 305
|
Posted: Sat Apr 22, 2006 3:10 am Post subject: |
|
|
I have the same model Marble. When I changed to Xorg 7 modular scrolling was messed up. Button def seems to change as the mouse is configured. This is the config that works for me.
Code: | Section "InputDevice"
Driver "mouse"
Identifier "Mouse0"
Option "Device" "/dev/input/mouse0"
Option "Name" "AutoDetected"
Option "Protocol" "ExplorerPS/2"
Option "Vendor" "AutoDetected"
Option "Buttons" "9"
Option "ZAxisMapping" "6 7"
# Option "YAxisMapping" "4 5"
Option "EmulateWheel" "1"
Option "EmulateWheelButton" "8"
# Amount to scroll:
Option "EmulateWheelInertia" "12"
EndSection
|
No xmodemap, I'm using it as a ps/2 device at the moment.
JohnY |
|
Back to top |
|
|
pa4wdh l33t
Joined: 16 Dec 2005 Posts: 815
|
Posted: Fri May 19, 2006 6:15 pm Post subject: |
|
|
Hi,
Sorry for picking up this old thread (again). I recently bought a Logitech Mable Mouse (partly because of the information in this thread ), and i thought my configuration was worth sharing with you.
I use the trackball left-handed, and i use the right small button as a "middle" button on a normal mouse, and the left small for scrolling down (this seemed the most usefull for web browsing).
My XFree86 4.0.2 config (I know, this is really old ):
Code: | Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Device" "/dev/psaux"
Option "InputFashion" "Mouse"
Option "Name" "Logitech Marble Mouse"
Option "Protocol" "ExplorerPS/2"
Option "Vendor" "Logitech"
Option "Buttons" "7"
EndSection |
And my .Xmodmap contains:
Code: | pointer = 3 4 1 5 2 6 7 |
It sometimes seems to click randomly, but i think that's a very-old-x-server-issue But it's not annoying me enough to upgrade
Best regards,
pa4wdh |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|