From owner-freebsd-questions  Mon Oct  9 15:16:28 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA26183
          for questions-outgoing; Mon, 9 Oct 1995 15:16:28 -0700
Received: from uswat.advtech.uswest.com (firewall-user@uswat.advtech.uswest.com [130.13.16.1])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA26176
          for <questions@freebsd.org>; Mon, 9 Oct 1995 15:16:26 -0700
Received: from westhub ([148.156.21.6]) by uswat.advtech.uswest.com (8.7/8.6.12) with SMTP id QAA05014 for <questions@freebsd.org>; Mon, 9 Oct 1995 16:16:24 -0600 (MDT)
Received: by westhub.mnet.uswest.com (M-Net Hub.950111)
Message-Id: <n1398866880.10587@denitqm.ecte.uswc.uswest.com>
Date: 9 Oct 1995 16:18:09 -0600
From: "Owen Newnan" <onewnan@denitqm.ecte.uswc.uswest.com>
Subject: Re: PS/2 mouse HOW ??
To: "questions about FreeBSD" <questions@freebsd.org>
X-Mailer: Mail*Link SMTP-QM 3.0.2 GM
Sender: owner-questions@freebsd.org
Precedence: bulk

                      RE>>PS/2 mouse HOW ??                        10/9/95

Yup, I failed to mention this.  XF86Config pointer device should be /dev/psm0
with protocol PS/2.  If you get past the standard configuration stuff and
still have problems (as several of us have) you might try warping into and out
of xterms/consoles via twm define function key.  Some find this alone frees up
the mouse.  I find that it allows me to exit, then when I startx again I'm OK.
 Another fellow finds if he starts up with a "real" PS/2 mouse, then after
that plugs in his Logitech mouse (what I've got) then things work.  See the
bug and hacker archives.