From owner-freebsd-questions Fri Jul 30 19:39:34 1999 Delivered-To: freebsd-questions@freebsd.org Received: from sasknow.com (h139-142-245-96.ss.FiberONE.NET [139.142.245.96]) by hub.freebsd.org (Postfix) with ESMTP id 9338014D6A for ; Fri, 30 Jul 1999 19:39:20 -0700 (PDT) (envelope-from freebsd@sasknow.com) Received: from localhost (freebsd@localhost) by sasknow.com (8.9.3/8.9.3) with ESMTP id UAA04922; Fri, 30 Jul 1999 20:39:54 GMT (envelope-from freebsd@sasknow.com) Date: Fri, 30 Jul 1999 20:39:54 +0000 (GMT) From: Ryan Thompson To: David Coder Cc: Jonathan Chen , freebsd-questions@FreeBSD.ORG Subject: Re: Dead serial mouse on /dev/cuaa0 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 Thu, 29 Jul 1999, David Coder wrote: > > On Thu, 29 Jul 1999, Jonathan Chen wrote: > > > On Tue, 27 Jul 1999, Ryan Thompson wrote: > > > > [...] > > > Unless I missed it, there shouldn't be any hardware conflicts (the only > > > new hardware, my NIC, is on IRQ 12. sio0 is on IRQ 4). I'll attach my > > > dmesg output for your perusal. > > > > > > moused -d /dev/cuaa0 reports that it cannot determine the mouse type. > > That means there is nothing there. If the mouse were there and detected, > you would get a "device busy" message. Maybe it's on cuaa1. > > dc Nope. Definitely cuaa0. Refer to my original message for the details, but I know that the mouse is connected to cuaa0 (port/IRQ settings from dmesg for cuaa0 match what they've always been. cuaa1 has never been used. (Although, I don't think I've ever bothered to take it out of the kernel. Oh well :-)). And, the mouse itself (not to mention the serial port) worked flawlessly in the same FreeBSD installation before, and STILL works in other operating systems under COM1 (read=_FIRST_ COM port) with the same port/IRQ settings. Go figure. Maybe it's time to try out speech recognition again. Virtually yours, Ryan Thompson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message