From 0c4b5d07eb4654fb5830d8ef5810526978731649 Mon Sep 17 00:00:00 2001 From: Brian Somers Date: Fri, 11 Apr 1997 15:45:35 +0000 Subject: YAMFC: Update FAQ with sysmouse section, add comment before mousedtype setting in sysconfig. --- FAQ/FAQ.sgml | 40 ++++++++++++++++++++++++++++++++++++++-- 1 file changed, 38 insertions(+), 2 deletions(-) (limited to 'FAQ/FAQ.sgml') diff --git a/FAQ/FAQ.sgml b/FAQ/FAQ.sgml index a69058a1e2..59a545e8c7 100644 --- a/FAQ/FAQ.sgml +++ b/FAQ/FAQ.sgml @@ -1,5 +1,5 @@ - +
@@ -7,7 +7,7 @@ Maintainer: Peter da Silva -Last updated: $Date: 1997-04-10 21:28:16 $ +Last updated: $Date: 1997-04-11 15:45:35 $ This is the FAQ for FreeBSD systems version 2.X All entries are @@ -1605,6 +1605,42 @@ options "CMD640" available at a very reasonable price. See section for more details. + + Why doesn't my mouse work with X + +

+ If you are using syscons (the default console driver), you can + configure FreeBSD to support a mouse pointer on each virtual + screen. In order to avoid conflicting with X, syscons supports + a virtual device called ``sysmouse''. All mouse events + received from the real mouse device are written to the sysmouse + device, using the MouseSystems protocol. If you wish to use your + mouse on one or more virtual consoles, + /etc/sysconfig: + mousedtype=ps/2 # or whatever your actual type is + mousedport=/dev/psm0 # or whatever your real port is + + /etc/XF86Config + Section Pointer + Protocol "MouseSystems" + Device "/dev/sysmouse" + ..... + + +

+ Some people prefer to use ``/dev/mouse'' under X. To + make this work, ``/dev/mouse'' should be linked to + ``/dev/sysmouse'': + + + cd /dev + rm -f mouse + ln -s sysmouse mouse + + ghostscript gives lots of errors with my 386/486SX. -- cgit v1.3