From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 03:10:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD92C16A4CE for ; Fri, 19 Nov 2004 03:10:55 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 384F543D45 for ; Fri, 19 Nov 2004 03:10:55 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from april.chuckr.org (localhost [127.0.0.1]) by april.chuckr.org (8.12.11/8.12.11) with ESMTP id iAJ3b69n038393 for ; Thu, 18 Nov 2004 22:37:06 -0500 (EST) (envelope-from chuckr@chuckr.org) Received: from localhost (chuckr@localhost)iAJ3b5te038390 for ; Thu, 18 Nov 2004 22:37:06 -0500 (EST) (envelope-from chuckr@chuckr.org) X-Authentication-Warning: april.chuckr.org: chuckr owned process doing -bs Date: Thu, 18 Nov 2004 22:37:05 -0500 (EST) From: Chuck Robey To: FreeBSD-current@FreeBSD.org Message-ID: <20041118222536.R38351@april.chuckr.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Fri, 19 Nov 2004 12:59:33 +0000 Subject: mouse problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 03:10:55 -0000 OK, I've done my homework this time, read all the mail archives, looked at the man pages, I may not know the answer but I'm not embarrassed to ask anymore. The assumption I'm working on is that there is a conflict between the usb keyboard&mouse combination and a competing PS/2 keyboard/mouse combination. [g'wan, correct me if I'm wrong, from the mail archives, there are a LOT of folks who will be reading this, and you will be doing a lot of olks a big favor] Just my own problem is on a amd64, but tit doesn't look to me like the problem connects to that platform alone. Apparently it connects more with driver design/modifications; it has occurred sometime after 5.2.1 became 5.3, and affected a large range of users. I would like now to experiment ... I was reading the man pages, the atkb driver, and it appears that one can disable the PS/2 keyboard. The problem is, such a procedure is mildly dangerous; you might not be able to reconnect, if you screw it up; you might have to reinstall. Because of that, I would appreciate it if someone who has more recent driver experience than I do would please help me (and all of the community, believe me) by making me a full and (hopefully) correct task list, things that need to be done, to turn off the PS/2 keyboard and enable the usb keyboard (mouse also at the same time, please). I will take the risk and try it for us, but please take as much care as you can. You do your best, and I promise not to come gunning after you if it breaks anyhow. Well, can I find any takers? ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary (on the wall at my old fraternity, Signa Phi Nothing). ----------------------------------------------------------------------------