Bug 57230

Summary: [psm] [patch] psm(4) incorrectly identifies an IntelliMouse Explorer attached through an Avocent SwitchView KVM
Product: Base System Reporter: Tom Convery <tpc>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 5.1-CURRENT   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
intellimouse.patch
none
intellimouse.patch none

Description Tom Convery 2003-09-26 04:20:18 UTC 
psm(4) identifies an IntelliMouse Explorer (4 buttons + wheel) as a standard
IntelliMouse (2 buttons + wheel) when the Explorer is attached through an
Avocent SwitchView KVM. According to Avocent's documentation, the SwitchView
is compatible with the IntelliMouse Explorer.

As best I can tell, the misidentification happens because psm doesn't probe
the Explorer exactly as described by Microsoft at
http://www.microsoft.com/whdc/hwdev/tech/input/5b_wheel.mspx, and the 
SwitchView needs the exact probe sequence to be happy.

Fix: This patch fixes the problem for me. It does not break detection of either
a plain Intellimouse or an Intellimouse Explorer attached directly to the
PS/2 port.

This patch should apply to -STABLE as well.
How-To-Repeat: Attach an IntelliMouse Explorer through an Avocent SwitchView to a PS/2 
mouse port.
Comment 1 Tom Convery 2003-12-21 04:52:58 UTC 
Attached is an update patch that applies cleanly to 5-CURRENT as of 
mid-December 2003.
Comment 2 Andriy Gapon 2008-02-07 15:59:03 UTC 
Could you please check if the patch from the following bug helps you?
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/118578

It doesn't have any KVM-specific logic though.
But it has IntelliMouse Explorer probing corrected.

-- 
Andriy Gapon
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2008-02-07 17:11:52 UTC 
State Changed
From-To: open->feedback

Note that submitter has been asked for feedback.
Comment 4 Volker Werth freebsd_committer freebsd_triage 2008-05-11 16:00:50 UTC 
State Changed
From-To: feedback->closed


We're sorry to not see any feedback received for quite some time. 
If you think this is still an issue that should be worked on, 
please provide the requested information and we'll be happy to 
re-open this ticket. 
Thank you for bringing this problem to attention!