From owner-freebsd-stable Wed Jul 21 13:10:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by hub.freebsd.org (Postfix) with ESMTP id BC2A214CE7 for ; Wed, 21 Jul 1999 13:10:42 -0700 (PDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id QAA17048; Wed, 21 Jul 1999 16:10:38 -0400 (EDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Date: Wed, 21 Jul 1999 16:10:37 -0400 (EDT) From: Greg Lynn To: David Coder Cc: freebsd-stable@FreeBSD.ORG Subject: Re: sio problems on 3.2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Jul 1999, David Coder wrote: > I don't believe your mouse is on the first com port. If it were, the output > of "moused -i all -p /dev/cuaa0" would be "device busy." The message you got > is generated when there is nothing on the device at all. Check whether it > isn't on the second com port. > You know I was *just* thinking about! I mean 1 sec ago! Yeah, I plan to shutdown the machine and check the hardware io ports over. One thing that sometimes pees me off is when motherboard manufacturers mix up com1 and 2 and whatever else in the documentation!! That's prob what has happened here... -Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message