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>
next in thread | previous in thread | raw e-mail | index | archive | help
--3XA6nns4nE4KvaS/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: >=20 > Greetings hackers, >=20 > I have a KVM switch and a fairly new (Logitech MouseMan+ cordless) mouse,= =20 > and I've found that while FreeBSD properly detects the mouse and all its= =20 > functionality (buttons, scrollwheel, etc) upon boot if I switch to=20 > another port on the KVM and then switch back my mouse "loses" its=20 > functionality. >=20 > After spending a while trying to figure out this problem (and reading PRs= =20 > on the issue (esp. i386/25463)) I found that a solution was not=20 > immediately available, but might be somewhat easy to achieve. In=20 > particular, for my mouse, the mouse driver can and does detect invalid=20 > packets, and invalid packets are always received after a return to my=20 > FreeBSD system via the KVM. I found that doing a reinitialization of the= =20 > device would fix the mouse, but that doing it from the interrupt handler= =20 > (in sys/isa/psm.c around line 2170) caused some intermediate problems. = =20 > Normally the mouse would just bounce around and generate click events for= =20 > a while and then settle down, but occasionally the driver (or maybe=20 > mouse?) would lock solid and I'd have to reboot the system. >=20 > Anyways, I'd like to work further on this problem and hopefully find a=20 > solution, but I'm having some trouble understanding where and what I=20 > should do. I'm not a novice C hacker, but I *am* a very novice kernel=20 > hacker and would appreciate help from anyone with knowledge of the psm=20 > (and atkbdc) code. I've considered maybe adding an ioctl to reset the=20 > mouse and adding a signal handler to moused to force a reset, but that=20 > seems kind of silly when the kernel driver can detect the problem itself= =20 > and resolve it. On the other hand, maybe that's the right way to go? =20 > Advice would be greatly appreciated. >=20 > -chip > --=20 > chip norkus; renaissance hacker; wd@arpa.com > "question =3D (to) ? be : !be;" --Shakespeare http://telekinesis.org/ >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message --=20 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 --3XA6nns4nE4KvaS/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+fuLvUkv4P6juNwoRAuT8AJ9L6zyNwZoGIkyz7miz4O/ZDaUjQgCfSlKO yPTtxXHtMvrslFUWHozQ7Eg= =mI63 -----END PGP SIGNATURE----- --3XA6nns4nE4KvaS/-- 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?20030324105024.GE23857>