Date: Mon, 24 Mar 2003 12:50:24 +0200 From: Ruslan Ermilov <ru@FreeBSD.org> To: Chip Norkus <wd@arpa.com> Cc: Alexey Zelkin <phantom@FreeBSD.org>, hackers@FreeBSD.org Subject: Re: KVM mice issues Message-ID: <20030324105024.GE23857@sunbay.com> In-Reply-To: <200303230957.36433.wd@arpa.com> References: <200303230957.36433.wd@arpa.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] I think Alexey was having similar issues, and may have some non-production quality patches for you to try. On Sun, Mar 23, 2003 at 09:57:36AM -0600, Chip Norkus wrote: > > Greetings hackers, > > I have a KVM switch and a fairly new (Logitech MouseMan+ cordless) mouse, > and I've found that while FreeBSD properly detects the mouse and all its > functionality (buttons, scrollwheel, etc) upon boot if I switch to > another port on the KVM and then switch back my mouse "loses" its > functionality. > > After spending a while trying to figure out this problem (and reading PRs > on the issue (esp. i386/25463)) I found that a solution was not > immediately available, but might be somewhat easy to achieve. In > particular, for my mouse, the mouse driver can and does detect invalid > packets, and invalid packets are always received after a return to my > FreeBSD system via the KVM. I found that doing a reinitialization of the > device would fix the mouse, but that doing it from the interrupt handler > (in sys/isa/psm.c around line 2170) caused some intermediate problems. > Normally the mouse would just bounce around and generate click events for > a while and then settle down, but occasionally the driver (or maybe > mouse?) would lock solid and I'd have to reboot the system. > > Anyways, I'd like to work further on this problem and hopefully find a > solution, but I'm having some trouble understanding where and what I > should do. I'm not a novice C hacker, but I *am* a very novice kernel > hacker and would appreciate help from anyone with knowledge of the psm > (and atkbdc) code. I've considered maybe adding an ioctl to reset the > mouse and adding a signal handler to moused to force a reset, but that > seems kind of silly when the kernel driver can detect the problem itself > and resolve it. On the other hand, maybe that's the right way to go? > Advice would be greatly appreciated. > > -chip > -- > chip norkus; renaissance hacker; wd@arpa.com > "question = (to) ? be : !be;" --Shakespeare http://telekinesis.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+fuLvUkv4P6juNwoRAuT8AJ9L6zyNwZoGIkyz7miz4O/ZDaUjQgCfSlKO yPTtxXHtMvrslFUWHozQ7Eg= =mI63 -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030324105024.GE23857>