From owner-freebsd-current@FreeBSD.ORG Sun Aug 10 21:15:48 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF6CA37B492 for ; Sun, 10 Aug 2003 21:15:24 -0700 (PDT) Received: from caboose.shortcircut.org (cpe-66-189-87-244.ma.charter.com [66.189.87.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 546CA44943 for ; Sun, 10 Aug 2003 19:04:17 -0700 (PDT) (envelope-from bogin@yokels.org) Received: from steam (unknown [10.0.1.2]) by caboose.shortcircut.org (Postfix) with ESMTP id BCA272677FD; Sun, 10 Aug 2003 22:04:35 -0400 (EDT) From: Mike Bohan To: Daniel Flickinger In-Reply-To: <20030811011616.yCbL87955@hun.org> References: <20030810105300.spgK73256@hun.org> <20030811011616.yCbL87955@hun.org> Message-Id: <1060567177.14454.8.camel@diesel> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 10 Aug 2003 21:59:37 -0400 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-current@freebsd.org Subject: Re: Problem with PS/2 mouse driver in XFree86 4.3.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2003 04:15:49 -0000 Not to undermine what you guys said, but this is unrelated to the original post I think. The problem I was having related to acpi, which Shizuka pointed out. I'm not trying to play nanny here, just don't want people to get confused =) On Sun, 2003-08-10 at 21:16, Daniel Flickinger wrote: > Sent: Sun, 10 Aug 2003 15:32:28 -0700 (PDT) by Doug White > > + On Sun, 10 Aug 2003, Daniel Flickinger wrote: > + > + > I had the same problem starting about a year ago when I > + > finally gave up and upgraded to X4. The problem appears > + > to be that the X4 driver does not disable the console > + > mouse and the two of them fight over the interrupts. > + > + Well yeah moused and X can't both use the mouse at once. You > + should get a 'device busy' error. If you want to use moused > + then have X gets its events from moused (/dev/sysmouse) and > + not psm0. > > That's what I did, as I had done in the past with X3 > --upgrading to X4 is when the problem came up, and yes, > you get a mouse busy when you move it to /dev/psm0. > However, if you do not start the mouse for the virtual > screens (which I had no need for anyway), /dev/psm0 can > be opened for X4. > > Secondly, at the time, Xconfig would not accept > /dev/sysmouse as a ps2 style mouse and would not track > if I called it a generic mouse... that may have changed. > > CAVEAT: I admit that I have not revisted the problem > since then which was at least a year ago --it works, I > leave it alone despite several X4 upgrades. The remedy > at the time was to use /dev/psm0, not /dev/sysmouse. > Maybe in the next upgrade I'll revisit the aggravation > since I would prefer to be able to use virtual X > sessions on separate logins. >