LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 05-29-2004, 11:22 PM   #1
nwhite
LQ Newbie
 
Registered: Oct 2003
Location: UK
Distribution: Slackware 10.0, 2.6.9 Custom Kernel
Posts: 23

Rep: Reputation: 15
Strange behaviour of Mx700


Hi,
Whenever I use the "Cruise Control" Up button (just above the scroll, for constant upward scrolling), rather than behaving correctly as the bottom one does and acting like I am scrolling continuously, it instead at the start and end of the button press also sends Button 6, causing a firefox (and other browsers) to go back if I scroll up using it. The output from xev explains it best (button 4 is what I want, scroll up, button 6 I don't (when this button is pressed), as it is configured to back in most applications):

ButtonPress event, serial 25, synthetic NO, window 0x2000001,
root 0xaf, subw 0x0, time 734489, (109,0), root114,540),
state 0x0, button 6, same_screen YES

ButtonPress event, serial 25, synthetic NO, window 0x2000001,
root 0xaf, subw 0x0, time 734505, (109,0), root114,540),
state 0x0, button 4, same_screen YES

ButtonRelease event, serial 25, synthetic NO, window 0x2000001,
root 0xaf, subw 0x0, time 734505, (109,0), root114,540),
state 0x800, button 4, same_screen YES

ButtonRelease event, serial 25, synthetic NO, window 0x2000001,
root 0xaf, subw 0x0, time 734561, (109,0), root114,540),
state 0x0, button 6, same_screen YES

As I said, this does not occur when using the down button.

The same thing happens regardless of whether imwheel (1.0.0pre6) is running, so presumably either the XF86Config file is at fault (though I can see nothing wrong with it), or the xmodmap instructions in initrc are misbehaving. I include the relevent parts of each:
XF86Config:
Identifier "Logitech Mx700"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/mouse"
Option "ZAxisMapping" "6 7"
Option "Buttons" "7"

initrc:
xmodmap -e "pointer = 1 2 3 6 7 4 5"
imwheel

Also, this does not occur in Windows XP, so it can't be a hardware problem.

Thanks...this confuses me...
 
Old 05-30-2004, 04:35 AM   #2
motub
Senior Member
 
Registered: Sep 2003
Location: The Netherlands
Distribution: Gentoo (main); SuSE 9.3 (fallback)
Posts: 1,607

Rep: Reputation: 46
What is the ExplorerPS/2 Protocol? Never heard of it (and I've just checked two XF86Config How-Tos to try and find out about it).

Do you mean ImPS/2 (which is the standard for PS/2 wheel mice, and also is said to work with USB mice)? Have you tried using "Auto" in this setting?

And may I point out that the fact that any given piece of hardware "works in Windows XP" does not mean that the hardware is not faulty (although I don't think your mouse is faulty in this instance).

Microsoft has not become one of the most powerful corporations in the world, and their product has not achieved overwhelming market dominance, by being standoffish from hardware manufacturers. The fact that Microsoft works closely with hardware manufactureres and uses the information gained in this way to "bend the rules" so that cheap or unreliable hardware works perfectly under Windows has long been a key support in achieving said market dominance.

As soon as you take Windows away, though, and replace it by an OS that has stricter requirements, you lose those hackarounds, and suddenly the hardware doesn't work. What a shock.
 
Old 05-30-2004, 05:01 PM   #3
nwhite
LQ Newbie
 
Registered: Oct 2003
Location: UK
Distribution: Slackware 10.0, 2.6.9 Custom Kernel
Posts: 23

Original Poster
Rep: Reputation: 15
I'm using ExplorerPS/2 as the several setup guides I found on the web, as well as various Logitech Mx700 topics here all said to use it. Therefore I presume it is the correct protocol to use.

I just tried using the Auto protocol - the scroll wasn't detected and it took about 5 seconds of moving the mouse before it was registerred.

As for the ImPS/2 protocol, it only supported 5 of the 7 buttons, which is unacceptable (the thumb buttons were listed as 1 and 2 as well as the left and right mouse buttons). The same thing still happened using ImPS/2, only button 2 was incorrectly registerred at the beginning and end of pressing cruise up, rather than button 6.

Presumably therefore the ExplorerPS/2 protocol is an extension of ImPS/2, with 7 button support.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Strange behaviour Anmol Suse/Novell 2 10-27-2005 11:05 PM
Strange bootsplash behaviour abisko00 Linux - Software 14 04-11-2005 03:04 PM
Strange Nmap behaviour ? ? ? lub0 Linux - Security 7 10-07-2003 08:45 PM
strange behaviour of back up cd salparadise Linux - Software 1 04-04-2003 07:08 PM
Strange Behaviour mikeyt_3333 Linux - General 4 08-06-2001 03:07 PM


All times are GMT -5. The time now is 07:16 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration