From owner-freebsd-questions  Sun Nov 15 00:11:25 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA04239
          for freebsd-questions-outgoing; Sun, 15 Nov 1998 00:11:25 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from us.net (laurel.us.net [198.240.72.4])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04227
          for <freebsd-questions@freebsd.org>; Sun, 15 Nov 1998 00:11:24 -0800 (PST)
          (envelope-from sillybug@us.net)
Received: (from sillybug@localhost)
	by us.net (8.8.8/8.8.8) id DAA09873
	for freebsd-questions@freebsd.org; Sun, 15 Nov 1998 03:11:03 -0500 (EST)
X-Provider: US Net - Advanced Internet Services - 301-361-USNET - info@us.net
	    Where Business Connects! (tm) -- http://www.us.net/
From: brian skrab <sillybug@us.net>
Message-Id: <199811150811.DAA09873@us.net>
Subject: Mouse + Modem problem...
To: freebsd-questions@FreeBSD.ORG
Date: Sun, 15 Nov 1998 03:11:02 -0500 (EST)
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello.

        I've just installed FreeBSD 2.2.7 on my 486 home 'puter and got
        Xwindows configured and running and was quite happy with its
        performance until I had it make a ppp connection to my ISP.  Once
        the modem connection was up, *everything*  s l o w e d  down.  What's
        weird about it is that if I move the mouse, things speed up.  If I
        just let the mouse sit, performance drags heavily.  I checked out
        what was going on with 'top' and found that while the mouse is at
        rest, nearly 50% of the CPU is used in 'interrupt' It's usually at
        just a smidge above 0.0% interrupt when the modem isn't connected.
        Weird, no?  Think it has something to do with the fact that both
        devices (modem & mouse) are on the machines 2 serial ports.

        Here's how the ports are set.

        Mouse:  Serial (Microsoft)      COM1
        Modem:  External 56k            COM2

        I tried running the mouse both through moused as well as letting X
        talk to it straight through the serial port (cuaa1).  No real
        difference in performance, and still the symptoms continue.

        Does anyone have an idea about how I can go about getting this
        fixed?  On my 486, performance is a scarce commodity, and this type
        of loss makes the machine virtually unusable without a third arm to
        move the mouse about...  The sad thing is that until this key point,
        X has out-performed and out-featured Windoze95 which I have
        installed on the other half of the drive.	

	Can anyone help?  Pretty Please?

	~brian skrab

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message