From owner-freebsd-current Mon May 22 1:39:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by hub.freebsd.org (Postfix) with ESMTP id 6CED037BA4F for ; Mon, 22 May 2000 01:39:30 -0700 (PDT) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.9.3/8.9.3) id KAA59299 for freebsd-current@freebsd.org; Mon, 22 May 2000 10:40:47 +0200 (CEST) (envelope-from stijn) Date: Mon, 22 May 2000 10:40:46 +0200 From: Stijn Hoop To: freebsd-current@freebsd.org Subject: Re: Anyone else seeing jumpy mice? Message-ID: <20000522104046.A59034@pcwin002.win.tue.nl> References: <200005220335.MAA07327@zodiac.mech.utsunomiya-u.ac.jp> <200005220341.UAA02277@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200005220341.UAA02277@mass.cdrom.com>; from msmith@freebsd.org on Sun, May 21, 2000 at 08:41:57PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just one more "problem" report: I see those messages, however I do not have any problems mousing afterwards. I'm using a switchview, which at least resets the mouse when I switch. On Sun, May 21, 2000 at 08:41:57PM -0700, Mike Smith wrote: > > Um, if you don't see the above message but see erratic mouse > > behavior, then there may be a configuration problem (for moused or > > X), or a hardware problem. My configuration works fine, the mouse worked without messages until I installed 5.0-current. > You can also get this if you have moused running but have configured X to > point to the physical mouse device rather than /dev/sysmouse. I do have /dev/psm0 in my XF86Config. You're saying it is better to use /dev/sysmouse, Protocol moused? BTW, it's a standard Logitech PS/2 3-button mouse. --Stijn -- FreeBSD: | Antonym, n.: The opposite of the word you're trying to The power to serve | think of. www.freebsd.org | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message