Date: Fri, 28 Apr 2000 11:23:53 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Dragos Ruiu <dr@dursec.com> Cc: hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Mouse Sync Problems with KVM Message-ID: <200004280223.LAA04611@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Thu, 27 Apr 2000 17:50:17 MST." <0004271752300E.00332@kyxbot.zorg> References: <0004271752300E.00332@kyxbot.zorg>
next in thread | previous in thread | raw e-mail | index | archive | help
>I have a freebsd system(3.4S) on a KVM.... and every time the monitored >system is switched, the mouse driver gets fuxored, and when you switch >back to the system the driver starts outputting oodles of the following >messages to syslog every time the mouse is moved: > >Apr 26 18:49:45 kyxbot /kernel: psmintr: out of sync (00c8 != 0008). >Apr 26 18:49:45 kyxbot /kernel: psmintr: out of sync (0000 != 0008). > >mouse type is PS/2 Which model is it? I suspect it is one of those mice with the "wheel". >Has anyone seen this before? Or do I have to get down and dirty with >the driver? This may be an issue with the KVM switch because it >does this on two different 3.4 systems on different KVMs, both KVM >brands are identical(masterview)... KVMs have presented so many headaches to us... Well, if the mouse works fine when you directly connect the mouse to the host computer, but it doesn't work as expected when you use a KVM, I would say the KVM is not compatible enough and is the cause of the problem.... I would like to see /var/run/dmesg.boot when you directly connect the mouse to your computer and reboot. I also like to compare it with /var/run/dmesg.boot obtained when you are using the KVM. Some KVMs are simple switch boxes which may momentarily cut power to the mouse when you switch between computers. Your mouse will loose internal settings if the power is cut. This will lead to mismatch of protocol between the host and the mouse. Some other KVMs are said to be smart enough to remember settings or understand wheel mouse protocols, and are free from such problem. But, the fact is, it appears that the firmware in many KVMs knows very limited number of various protocols (IntelliMouse protocol is not the only wheel mouse protocol in the market, you know), and can be easily confused and is not able to forward mouse data properly in a timely manner to the host computer. I wonder how many KVM products can handle dual-wheel mice from A4 Tech, IBM ScrollPoint mouse, and Logitech wheel mice when their proprietary drivers are installed in W*ndows95/98... >But the KVM works with Wintendo/NT, >Linux and OpenBSD just fine... on the same HW. If your mouse is a wheel mouse, do you have its driver installed on NT? If it isn't, the mouse is just acting as the standard 2 button mouse without wheel's functionality. That's why you don't see any problem with NT. The PS/2 mouse drivers in Linux and OpenBSD do not detect and initialize the wheel mouse. XFree86 servers try to activate the wheel, if you specify an appropriate wheel mouse protocol in XF86Config. I suspect you will see the mouse cursor go crazy if you switch KVM away from and back to the Linux/OpenBSD box while running the X server in this case. You can force FreeBSD to use the mouse as the standard PS/2 mouse by specifying the flags 0x200 to the psm driver. This way, the mouse should always work. But, you cannot use the wheel. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004280223.LAA04611>