Date: Fri, 30 Jul 1999 20:39:54 +0000 (GMT) From: Ryan Thompson <freebsd@sasknow.com> To: David Coder <dacoder@dcoder.com> Cc: Jonathan Chen <jonc@pinnacle.co.nz>, freebsd-questions@FreeBSD.ORG Subject: Re: Dead serial mouse on /dev/cuaa0 Message-ID: <Pine.BSF.4.10.9907302021580.4885-100000@sasknow.com> In-Reply-To: <Pine.BSF.4.10.9907291154290.1456-100000@doc.dcoder.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9907302021580.4885-100000>