Date: Mon, 22 May 2000 16:18:06 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Andy Sparrow <andy@geek4food.org> Cc: stable@freeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Weird rodent behaviour Message-ID: <200005220718.QAA16478@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Sun, 21 May 2000 23:38:33 MST." <200005220638.XAA93206@mega.geek4food.org> References: <200005220638.XAA93206@mega.geek4food.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>A recent thread on -STABLE prompted me to type up the following >description of oddities I've been noticing with my mouse under 4.0-STABLE: > >I've been using a Logitech Marble FX for 18 months now - it used to be directl >y >plugged into my "main" machine. It wasn't correctly recognised by the psm driv >er >(which used to report a MouseMan+, IIRC), but it worked well enough - modulo It IS detected correctly :-) As far as the mouse firmware is concerned, Logitech Marble FX uses the PS/2++ protocol which is the Logitech's proprietary protocol since MouseMan+/FirstMouse+. Marble FX and MouseMan+ are software compatible and the mouse driver does not need to distinguish the two. >some odd behaviour when scrolling down the 'VT Options' menu in Xterm using >Ctrl-"Real Middle Button" (looked like it was seeing lots of spurious >"button-up/button-down" events, but I never really worried about it too much). > >However, the "middle" button (this guy has 4 buttons) worked fine for 'paste' >operations in both syscons and X (3.3.6, mouse is sysmouse) until I recently >supped -STABLE (4.0-STABLE FreeBSD 4.0-STABLE #0: Wed Apr 26 14:33:22 PDT 2000 >), >at which point I noticed that I now have to "chord" the 1st and 3rd buttons to > >get the "middle" button (this is an SMP kernel, just in case that has any >relevance). This is strange. I would like to see your mouse settings in /etc/rc.conf and XF86Config. I also would like you to give "boot -v" at the boot loader prompt and send me /var/run/dmesg.boot after the system is started. (Do not use a KVM when you do this please.) >The mouse is now /much/ less responsive than it used to be - press events are >often missed, rubber-banding is prone to weird behaviour, it just generally fe >els >much less "snappy" than it used to - just moving windows around feels "laggy". If you add "-3" option for moused (in moused_flags in /etc/rc.conf), you may need to tweak the 3-button emulation timeout in the "-E" option as well. But, as Marble FX does have the middle button, you shouldn't need to use the "-3" option in the first place. Are you absolutely sure that the middle button suddenly became inoperable? >Even more recently (last w/e), I added a Linksys 4 port KVM switch, and took >the M$ mouse off another machine and plugged it into the KVM. > >I now notice that: > >* The KVM switch seems to prevent the mouse being detected correctly, psm "see >s" > only a generic PS/2 mouse on both machines - dmesg says: > > psm0: failed to get data. > psm0 irq 12 on isa > psm0: model Generic PS/2 mouse, device ID 0 I don't know which M$ mouse model you are using. But, if it is a 2-button model, without a wheel, the above message is correct. The 2-button MS mouse is very "generic" :-) The psm driver cannot distinguish every single mouse model on the market. There are too many of them. It only detects and distinguishes as many models and protocols as it needs to know to operate the mouse correctly. If this MS mouse is IntelliMouse (it has a wheel), then your KVM is not compatible with IntelliMouse and the psm driver cannot do anything about it ;-< Kazu > on both machines. > >* A kernel/world, 3.4-STABLE from Apr 2nd seems to work fine still. The > mouse is as "snappy" as I recall, and the "centre" button works fine, in bo >th > syscons and X. > >The only difference is that one machine is running 4.0-STABLE. When both were >running 3.4-STABLE, they both worked fine. > >Any comments? I notice that the 'psm' driver has changed a fair bit recently, >and obviously this has changed the behaviour for this mouse. Unfortunately, th >e >code looks like it contains many chicken entrails ;-O - anything I can do to >help improve the support for this mouse? > >Cheers, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005220718.QAA16478>