From owner-freebsd-questions Tue Sep 8 11:06:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16184 for freebsd-questions-outgoing; Tue, 8 Sep 1998 11:06:18 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16178 for ; Tue, 8 Sep 1998 11:06:16 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with SMTP id LAA16185 for ; Tue, 8 Sep 1998 11:06:08 -0700 (PDT) Date: Tue, 8 Sep 1998 11:06:08 -0700 (PDT) From: Brooks Davis Reply-To: brooks@one-eyed-alien.net To: freebsd-questions@FreeBSD.ORG Subject: Re: Mouse problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 4 Jul 1998, Doug White wrote: > On Thu, 2 Jul 1998, Brooks Davis wrote: > > > > I've tried the following: > > moused -p /dev/psm0 > > moused -p /dev/psm0 -t 'ps/2' > > moused -p /dev/psm0 -t auto > > moused -p /dev/psm0 -t sysmouse > > and even > > moused -p /dev/psm0 -t intellimouse > > which doesn't work since it's a PS/2 port not a serial port. > > No clue then, I assume you are running vidcontrol -m on afterwards and > have moused disabled from /etc/rc.conf while you are playing with this. This is ancient, but since I finaly had time to look at the problem again and found a solution, I figured I'd post a follow up. The problem was that the PS/2 port was disabled in BIOS. I guess it's a feature that the Tyan lets you detect the mouse, but not use it when it's disabled. ;-) Thanks for your help, Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message