From owner-freebsd-questions Sun Jan 26 12:17:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA21655 for questions-outgoing; Sun, 26 Jan 1997 12:17:46 -0800 (PST) Received: from netcom2.netcom.com (stanb@netcom2.netcom.com [192.100.81.108]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA21648 for ; Sun, 26 Jan 1997 12:17:44 -0800 (PST) Received: (from stanb@localhost) by netcom2.netcom.com (8.6.13/Netcom) id PAA25652; Sun, 26 Jan 1997 15:17:42 -0500 From: stanb@netcom.com (Stan Brown) Message-Id: <199701262017.PAA25652@netcom2.netcom.com> Subject: Still having moused problems. To: freebsd-questions@freebsd.com (Free BSD Questions list) Date: Sun, 26 Jan 1997 15:17:42 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I still can't get moused to work on my recently upgraded to 2.2 BETA machine. Running moused with the -f -d options returns an error message saying a read returned -1 and the device is ot available. I am using a ps/2 mouse on /dev/psm0. This device works great under X. What could be wrong hee? I ran this test as root to eliminate a permissions problem. Any Ideas? -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1997 Stan Brown. Redistribution via the Microsoft Network is prohibited.