Problem with PS/2 mouse driver in XFree86 4.3.0
Mike Bohan
bogin at yokels.org
Sun Aug 10 21:15:49 PDT 2003
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.
>
More information about the freebsd-current
mailing list