From owner-freebsd-current  Tue Oct 15 15:56:40 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA14770
          for current-outgoing; Tue, 15 Oct 1996 15:56:40 -0700 (PDT)
Received: from rosie.scsn.net (scsn.net [206.25.246.12])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14762
          for <current@FreeBSD.org>; Tue, 15 Oct 1996 15:56:38 -0700 (PDT)
Received: from rhiannon.scsn.net (cola79.scsn.net [206.25.247.79])
          by rosie.scsn.net (post.office MTA v2.0 0813 ID# 0-13529)
          with ESMTP id AAA61; Tue, 15 Oct 1996 18:55:43 -0400
Received: (from root@localhost) by rhiannon.scsn.net (8.7.6/8.6.12) id SAA00399; Tue, 15 Oct 1996 18:56:54 -0400 (EDT)
From: "Donald J. Maddox" <root@rhiannon.scsn.net>
Message-Id: <199610152256.SAA00399@rhiannon.scsn.net>
Subject: Re: Bug with moused and XFree86
In-Reply-To: <199610152153.RAA00793@rhiannon.scsn.net> from "Donald J. Maddox" at "Oct 15, 96 05:53:06 pm"
To: dmaddox@scsn.net
Date: Tue, 15 Oct 1996 18:56:53 -0400 (EDT)
Cc: current@FreeBSD.org
Reply-To: dmaddox@scsn.net
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> > You should be running moused on /dev/cuaa0 telling it you have a 
> > 'mouseman' mouse.  You should then tell X that you have a mouse systems
> > mouse on /dev/sysmouse.  Having both moused and X using the same
> > device is bound for trouble since you don't know which of them will
> > get each event.
> > 
> 
>     Okay, now I see! :-)  Thanks for the help...  I have been avoiding
> using moused at all, since it was clearly fighting with X over the
> pointer.  Now I'll finally be able to use both!

    Forgive me for replying to my own message, but it looks like I spoke
too soon...  Following your (Jason's) advice above, moused works ok,
but...

    When I start the Xserver, the pointer appears at the center of the
screen, as always.  The first time I move the mouse, however, the pointer
goes to the upper left corner of the screen and pretty much stays there.
It moves when I move the mouse, but it pretty much stays locked up in
that corner.  In short, X is now getting mouse events, but obviously the
wrong ones.

    Again, my mouse works fine when /dev/mouse is a link to /dev/cuaa0,
I just cannot use X and moused concurrently.

    For clarity, here is the situation:

    From /etc/XF86Config:
-----------------------------------------------------------------
      Section "Pointer"
          Protocol    "MouseMan"
          Device      "/dev/mouse"
-----------------------------------------------------------------

    From /etc/sysconfig:
-----------------------------------------------------------------

# Set to
# {microsoft|mousesystems|mmseries|logitech|busmouse|mouseman|ps/2|mmhittab}
# to activate system mouse cursor support (or NO for none)
# Use 'vidcontrol -m on' command to activate it on particular screen
mousedtype=mouseman

############## Next block activated only if mousetype != NO ################

# Set to your mouse port (required)
# Use real device here, because /dev/mouse usually linked with /dev/sysmouse
mousedport=/dev/cuaa0

# Moused options:
# -s: 9600 baud mouse
# -c: enable ChordMiddle
# see moused usage info for complete options list
mousedflags=""

-------------------------------------------------------------------

    From /dev:
#ls -l /dev/sysmouse
crw-------  1 root  wheel   12, 128 Oct 15 18:19 /dev/sysmouse

# ls -l /dev/consolectl 
crw-------  1 root  wheel   12, 255 Oct 15 17:18 /dev/consolectl

(/dev/mouse is a symbolic link to /dev/sysmouse)

--------------------------------------------------------------------

    What's wrong here?

-- 


                                            Donald J. Maddox
                                            (dmaddox@scsn.net)