From owner-freebsd-questions Tue Apr 8 08:48:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA14431 for questions-outgoing; Tue, 8 Apr 1997 08:48:01 -0700 (PDT) Received: from vdp01.vailsystems.com (root@vdp01.vailsystems.com [207.152.98.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA14408 for ; Tue, 8 Apr 1997 08:47:58 -0700 (PDT) Received: from crocodile.vale.com (crocodile [204.117.217.147]) by vdp01.vailsystems.com (8.8.3/8.7.3) with ESMTP id KAA21389 for ; Tue, 8 Apr 1997 10:47:55 -0500 (CDT) Received: (from daniel@localhost) by crocodile.vale.com (8.8.3/8.7.3) id KAA00787; Tue, 8 Apr 1997 10:47:55 -0500 (CDT) Date: Tue, 8 Apr 1997 10:47:54 -0500 (CDT) From: Dan Riley To: FreeBSD Questions mailing list Subject: Mouse lockups In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I recently added a new keyboard to my system. Now the mouse will not function, either moused, dies as soon as vidcontrol -m on is entered, or the mouse in X, wont repsond to tracking or button press. All worked fine before the new keyboard. The motherboard utilizes the small din connectors for the keyboard and mouse peripherals. Ovbviously I am using the psm driver. I have kernel support for psm0 compiled and have it enabled via sysconfig at startup. Let me mention again that all worked fine before the new keyboard, no other mods to the system hardware or configuration. Can anyone point me in the right direction to get this hardware conflict worked out...I really hated that old Gateway 2000 keyboard...I guess I'll have to use it in the meantime. Thanks alot, Dan