Update information on mouse support.
Submitted by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
This commit is contained in:
John Fieber
parent
15d57161a2
commit
633a503c6c
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=2406
2 changed files with 170 additions and 17 deletions
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: hardware.sgml,v 1.2 1997-11-04 03:49:22 steve Exp $ -->
|
||||
<!-- $Id: hardware.sgml,v 1.3 1998-02-01 23:02:35 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect>
|
||||
|
|
@ -144,21 +144,27 @@
|
|||
name="sio"> man page to get more information on configuring such cards.
|
||||
|
||||
<sect1>
|
||||
<heading>I have an unusual bus mouse. How do I set it up?</heading>
|
||||
<heading>I have an unusual bus mouse. How do I set it up?<label id="busmouse"></heading>
|
||||
|
||||
<p>FreeBSD supports the Logitech and ATI Inport bus mice. You need
|
||||
to add the following line to the kernel config file and recompile
|
||||
for the Logitech and ATI mice:
|
||||
<p>FreeBSD supports the bus mouse and the InPort bus mouse from such
|
||||
manufactures as Microsoft, Logitech and ATI. The bus device driver
|
||||
is compiled in the GENERIC kernel by default. If you are building
|
||||
a custom kernel with the bus mouse driver, make sure to add the
|
||||
following line to the kernel config file:
|
||||
|
||||
<verb>
|
||||
device mse0 at isa? port 0x23c tty irq5 vector mseintr
|
||||
</verb>
|
||||
|
||||
<p>The bus mouse usually comes with an dedicatd interface card.
|
||||
It may allow you to set the port address and the IRQ number other
|
||||
than shown above. Refer to the manual of your mouse and the
|
||||
<htmlurl url="http://www.freebsd.org/cgi/man.cgi?mse" name="mse">
|
||||
man page for more information.
|
||||
|
||||
<sect1>
|
||||
<heading>
|
||||
How do I use my PS/2 (``keyboard'') mouse?
|
||||
<label id="ps2mouse">
|
||||
</heading>
|
||||
How do I use my PS/2 (``mouse port'' or ``keyboard'') mouse?<label id="ps2mouse"></heading>
|
||||
|
||||
<p>If you're running a relatively recent version of FreeBSD then you
|
||||
can simply enable it in the kernel configuration menu
|
||||
|
|
@ -172,8 +178,6 @@
|
|||
|
||||
<verb>
|
||||
device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr
|
||||
# Options for psm:
|
||||
options PSM_CHECKSYNC #checks the header byte for sync.
|
||||
</verb>
|
||||
|
||||
<p>See the <url url="../handbook/kernelconfig.html"
|
||||
|
|
@ -190,6 +194,78 @@
|
|||
|
||||
<p>when logged in as root.
|
||||
|
||||
<sect1>
|
||||
<heading>Is it possible to make use of a mouse in any way outside the X Window?<label id="moused"></heading>
|
||||
|
||||
<p>If you are using the default console driver, syscons, you can
|
||||
use a mouse pointer in text consoles to cut & paste text.
|
||||
Run the mouse daemon, moused, and turn on the mouse pointer
|
||||
in the virtual console:
|
||||
|
||||
<verb>
|
||||
moused -p /dev/xxxx -t yyyy
|
||||
vidcontrol -m on
|
||||
</verb>
|
||||
|
||||
<p>Where <tt>xxxx</tt> is the mouse device name and <tt>yyyy</tt>
|
||||
is a protocol type for the mouse. See the
|
||||
<htmlurl url="http://www.freebsd.org/cgi/man.cgi?moused" name="moused">
|
||||
man page for supported protocol types.
|
||||
|
||||
<p>You may wish to run the mouse daemon automatically when the
|
||||
system starts. In version 2.2.1, set the following variables in
|
||||
<tt>/etc/sysconfig</tt>.
|
||||
|
||||
<verb>
|
||||
mousedtype="yyyy"
|
||||
mousedport="xxxx"
|
||||
mousedflags=""
|
||||
</verb>
|
||||
|
||||
In versions 2.2.2 or later, set the following variables in
|
||||
<tt>/etc/rc.conf</tt>.
|
||||
|
||||
<verb>
|
||||
moused_type="yyyy"
|
||||
moused_port="xxxx"
|
||||
moused_flags=""
|
||||
</verb>
|
||||
|
||||
<p>Staring from FreeBSD 2.2.6, the mouse daemon is capable of
|
||||
determining the correct protocol type automatically unless the mouse
|
||||
is a relatively old serial mouse model. Specify ``<tt>auto</tt>'' as
|
||||
the protocol to invoke automatic detection.
|
||||
|
||||
<p>When the mouse daemon is running, access to the mouse needs to be
|
||||
coordinated between the mouse daemon and other programs such as the
|
||||
X Window. Refer to <ref id="x-and-moused" name="another section">
|
||||
on this issue".
|
||||
|
||||
<sect1>
|
||||
<heading>How do I cut and paste text with mouse in the text console?</heading>
|
||||
|
||||
<p>Once you get the mouse deamon running (see <ref id="moused"
|
||||
name="previous section">), hold down the button 1 (left button)
|
||||
and move the mouse to select a region of
|
||||
text. Then, press the button 2 (middle button) or the button 3 (right
|
||||
button) to paste it at the text cursor.
|
||||
|
||||
<p>In versions 2.2.6 and later, pressing the button 2 will paste
|
||||
the text. Pressing the button 3 will ``extend'' the selected region
|
||||
of text. If your mouse does not have the middle button, you may wish
|
||||
to emulate it or remap buttons using moused options. See the
|
||||
<htmlurl url="http://www.freebsd.org/cgi/man.cgi?moused" name="moused">
|
||||
man page for details.
|
||||
|
||||
<sect1>
|
||||
<heading>My mouse has a fancy wheel and buttons. Can I use them in FreeBSD?</heading>
|
||||
|
||||
<p>The answer is, unfortunately, ``It depends.'' These mice with
|
||||
additional features require specialized driver in most cases.
|
||||
Unless the mouse device driver or the user program has specific
|
||||
support for the mouse, it will act just like a standard two, or
|
||||
three button mouse.
|
||||
|
||||
<sect1>
|
||||
<heading>
|
||||
How do I use the mouse/trackball/touchpad on my laptop?
|
||||
|
|
|
|||
91
FAQ/x.sgml
91
FAQ/x.sgml
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: x.sgml,v 1.1 1997-11-03 08:54:00 max Exp $ -->
|
||||
<!-- $Id: x.sgml,v 1.2 1998-02-01 23:02:37 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect>
|
||||
|
|
@ -20,7 +20,7 @@
|
|||
<ref id="xig" name="Xi Graphics"> for more details.
|
||||
|
||||
<sect1>
|
||||
<heading>Why doesn't my mouse work with X</heading>
|
||||
<heading>Why doesn't my mouse work with X<label id="x-and-moused"></heading>
|
||||
|
||||
<p>If you are using syscons (the default console driver), you can
|
||||
configure FreeBSD to support a mouse pointer on each virtual
|
||||
|
|
@ -244,11 +244,13 @@
|
|||
<sect1>
|
||||
<heading>My PS/2 mouse doesn't behave properly under X.</heading>
|
||||
|
||||
<p>Your mouse and the mouse driver have somewhat become out of
|
||||
synchronization. Switching away from X to a virtual terminal
|
||||
and getting back to X again may make them re-synchronized.
|
||||
If the problem occurs often, you may add the following option
|
||||
in your kernel configuration file and recompile it.
|
||||
<p>Your mouse and the mouse driver may have somewhat become out of
|
||||
synchronization.
|
||||
|
||||
<p>In versions 2.2.5 and earlier, switching away from X to a
|
||||
virtual terminal and getting back to X again may make them
|
||||
re-synchronized. If the problem occurs often, you may add the
|
||||
following option in your kernel configuration file and recompile it.
|
||||
|
||||
<verb>
|
||||
options PSM_CHECKSYNC
|
||||
|
|
@ -266,5 +268,80 @@
|
|||
systems and voids the ``tap'' feature of the ALPS GlidePoint
|
||||
device attached to the PS/2 mouse port.
|
||||
|
||||
<p>In versions 2.2.6 and later, synchronization check is done
|
||||
in a slightly better way and is standard in the PS/2 mouse driver.
|
||||
It should even work with GlidePoint. (As the check code has become
|
||||
a standard feature, PSM_CHECKSYNC option is not available in these
|
||||
versions.) However, in rare case the driver may erroneously report
|
||||
synchronization problem and you may see the kernel message:
|
||||
|
||||
<verb>
|
||||
psmintr: out of sync (xxxx != yyyy)
|
||||
</verb>
|
||||
|
||||
and find your mouse doesn't seem to work properly.
|
||||
|
||||
<p>If this happens, disable the synchronization check code by
|
||||
setting the driver flags for the PS/2 mouse driver to 0x100.
|
||||
Enter <em>UserConfig</em> by giving the ``<tt>-c</tt>'' option
|
||||
at the boot prompt:
|
||||
|
||||
<verb>
|
||||
boot: -c
|
||||
</verb>
|
||||
|
||||
Then, in the <em>UserConfig</em> command line, type:
|
||||
|
||||
<verb>
|
||||
UserConfig> flags psm0 0x100
|
||||
UserConfig> quit
|
||||
</verb>
|
||||
|
||||
<sect1>
|
||||
<heading>My PS/2 mouse from MouseSystems doesn't seem to work.</heading>
|
||||
|
||||
<p>There have been some reports that certain model of PS/2 mouse
|
||||
from MouseSystems works only if it is put into the ``high resolution''
|
||||
mode. Otherwise, the mouse cursor may jump to the upper-left
|
||||
corner of the screen every so often.
|
||||
|
||||
<p>Unfortunately there is no workaround for versions 2.0.X and
|
||||
2.1.X. In versions 2.2 through 2.2.5, apply the following patch
|
||||
to <tt>/sys/i386/isa/psm.c</tt> and rebuild the kernel. See the
|
||||
section on <ref id="make-kernel" name="building a kernel">
|
||||
if you've no experience with building kernels.
|
||||
|
||||
<verb>
|
||||
diff -u psm.c.orig psm.c
|
||||
@@ -766,6 +766,8 @@
|
||||
if (verbose >= 2)
|
||||
log(LOG_DEBUG, "psm%d: SET_DEFAULTS return code:%04x\n",
|
||||
unit, i);
|
||||
+ set_mouse_resolution(sc->kbdc, PSMD_RES_HIGH);
|
||||
+
|
||||
#if 0
|
||||
set_mouse_scaling(sc->kbdc); /* 1:1 scaling */
|
||||
set_mouse_mode(sc->kbdc); /* stream mode */
|
||||
</verb>
|
||||
|
||||
<p>In versions 2.2.6 or later, specify the flags 0x04 to the PS/2
|
||||
mouse driver to put the mouse into the high resolution mode.
|
||||
Enter <em>UserConfig</em> by giving the ``<tt>-c</tt>'' option
|
||||
at the boot prompt:
|
||||
|
||||
<verb>
|
||||
boot: -c
|
||||
</verb>
|
||||
|
||||
Then, in the <em>UserConfig</em> command line, type:
|
||||
|
||||
<verb>
|
||||
UserConfig> flags psm0 0x04
|
||||
UserConfig> quit
|
||||
</verb>
|
||||
|
||||
<p>See the previous section for another possible cause of mouse
|
||||
problems.
|
||||
|
||||
</sect>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue