From owner-freebsd-current Wed Jul 26 17:37:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from numbertwo.domainfactory.de (numbertwo.domainfactory.de [194.221.134.226]) by hub.freebsd.org (Postfix) with SMTP id 2BC4A37BF84 for ; Wed, 26 Jul 2000 17:37:45 -0700 (PDT) (envelope-from steele@cloaked.de) Received: (qmail 16847 invoked from network); 27 Jul 2000 00:37:38 -0000 Received: from p3e9b9bca.dip0.t-ipconnect.de (HELO steele.intra) ([62.155.155.202]) (envelope-sender ) by numbertwo.domainfactory.de (qmail-ldap-1.03) with SMTP for ; 27 Jul 2000 00:37:38 -0000 Received: (from steele@localhost) by steele.intra (8.9.3/8.9.3) id CAA11090; Thu, 27 Jul 2000 02:36:02 +0200 (CEST) (envelope-from steele) Date: Thu, 27 Jul 2000 02:36:02 +0200 From: Benedikt Schmidt To: Jos Backus Cc: current@FreeBSD.ORG Subject: Re: Mouse frozen in X when returning from text console Message-ID: <20000727023602.B64338@cloaked.de> References: <20000726155315.A493@traitor.artemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000726155315.A493@traitor.artemis.com>; from josb@corp.webtv.net on Wed, Jul 26, 2000 at 03:53:15PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 26, 2000 at 03:53:15PM -0700, Jos Backus wrote: > [This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using > the ati driver module.] > > Something I noticed today: switch to text console from X using C-A-F1; upon > return, the mouse cursor is frozen. moused appears to still work because I > can cut/paste text in the text console. Restarting moused doesn't help. > > Is anybody else seeing this? Same problem here on current (make world + kernel last week) with Xfree86 4.0.1 using a V3000 and and ps2 mouse. I tried using "Device" "/dev/mouse" with moused and "Device" "/dev/psm0" without moused. With both settings the mouse is frozen after switching back to X. I didn't have this problem with Xfree 4.0. It just appeared when I updated to the new 4.0.1 port. I don't have this problem on Linux using Xfree86 4.0.1 on the same computer. Thanks Benedikt Schhmidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message