Differences between revisions 5 and 18 (spanning 13 versions)
Revision 5 as of 2004-02-18 15:33:34
Size: 1149
Editor: anonymous
Comment:
Revision 18 as of 2009-03-16 03:30:34
Size: 2634
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## Auto-converted by kwiki2moinmoin v2005-10-07
===== Translations =====
*["XFreeConfigSpanish"] : spanish / español.
-----
#language
 {i} XFree86 (up to [[DebianSarge|Debian/Sarge]]) has been replaced by Xorg since [[DebianEtch|Debian/Etch]]
Line 7: Line 5:
["XFree86"] and ["XFreeFour"] can both be configured in Debian (woody+) using DebConf. This is done when the package is installed, but can be re-run any time by executing::{{{ XFree86 can both be configured in Debian (woody+) using [[debconf]]. This is done when the package is installed, but can be re-run any time by executing::{{{
Line 10: Line 8:
where '<package-name>' is the name of the xserver. Use 'xserver-xfree86' for ["XFreeFour"], and 'xserver-<type>' for ["XFree86"]. Editing your /etc/X11/ config file is only necessary if you have some special needs or are particularly curious. If you must... where '<package-name>' is the name of the xserver. Use 'xserver-xfree86' or 'xserver-<type>'. Editing your /etc/X11/ config file is only necessary if you have some special needs or are particularly curious. If you must...
Line 12: Line 10:
== Manual XFree86 Version 3.x Configuration ==
["XFree86"] may be configured by editing the file{{{
 /etc/X11/["XF86Config"]
== Manual XFree86 ==
[[XFree86]] may be configured by editing the file{{{
 /etc/X11/XF86Config
Line 17: Line 15:
== XFree86 Version 4.0 Configuration ==
["XFreeFour"] uses the file{{{
 /etc/X11/["XF86Config"]-4
If you use XFree 4.x try the command {{{
 $ XFree86 -configure
Line 21: Line 18:
=== USB mouse ===
Your Universal Serial Bus ([[USB]]) mouse may be configured correctly by adding this section to your !XF86Config-4.
{{{
 Section "InputDevice"
     Identifier "USB Mice"
     Driver "mouse"
     Option "CorePointer"
 # Option "SendCoreEvents"
     Option "Protocol" "IMPS/2"
     Option "Device" "/dev/input/mice"
     Option "["ZAxisMapping"]" "4 5"
     Option "Buttons" "5"
 EndSection
}}}
If you ''only'' use a USB mouse use the !CorePointer option, otherwise use the !SendCoreEvents option.
Line 22: Line 34:
Of you use ["XFreeFour"] try the command {{{
 $ ["XFree86"] -configure
== Using XFree86 with GPM ==
==== Configure XFree86 ====
In your XF86Config (-4) file:
{{{
 Section "InputDevice"
        Identifier "Generic Mouse"
        Driver "mouse"
 # Option "CorePointer"
        Option "SendCoreEvents"
        Option "Device" "/dev/gpmdata"
        Option "Protocol" "IntelliMouse"
 EndSection
Line 25: Line 47:
If you use a USB mouse use ["USBMouseConfig"]. The !IntelliMouse driver corresponds to the "{{{repeat_type=ms3}}}" option in {{{gpm.conf}}}, which is the default repeat type in Debian.
Line 27: Line 49:
If you use gpm use this ["GPMMouseConfig"] . ==== On the gpm side of things ====
To configure gpm use program {{{gpmconfig}}}. For most of the scroll wheel mice I use a type of imps2. That seems to work best.
Line 29: Line 52:
== DRI ==
If you're using ["XFreeFour"] then DirectRendering is easy to do.

If you're not...
In a normal setup gpm listens to the port the mouse is connected to and repeats/relays the mouse events to a unix socket {{{/dev/gpmdata}}}. This allows console applications like mc (Midnight Commander) to get mouse events. For X windows to hear the mouse it should be configured to listen to {{{/dev/gpmdata}}}. I've always had the best luck configuring gpm to repeat in raw mode and configure X windows to use whatever protocol the mouse uses. In this setup the mouse type should be set in two places, in gpmconfig and in your X windows configuration. I get the feeling this is a non-standard approach but it's alway given me the least problems.

Configuring XFree86

DebConf configuration

XFree86 can both be configured in Debian (woody+) using debconf. This is done when the package is installed, but can be re-run any time by executing::

 $ dpkg-reconfigure <package-name>

where '<package-name>' is the name of the xserver. Use 'xserver-xfree86' or 'xserver-<type>'. Editing your /etc/X11/ config file is only necessary if you have some special needs or are particularly curious. If you must...

Manual XFree86

XFree86 may be configured by editing the file

 /etc/X11/XF86Config

If you use XFree 4.x try the command

 $ XFree86 -configure

USB mouse

Your Universal Serial Bus (USB) mouse may be configured correctly by adding this section to your !XF86Config-4.

 Section "InputDevice"
     Identifier "USB Mice"
     Driver "mouse"
     Option "CorePointer"
 #   Option "SendCoreEvents"
     Option "Protocol" "IMPS/2"
     Option "Device" "/dev/input/mice"
     Option "["ZAxisMapping"]" "4 5"
     Option "Buttons" "5"
 EndSection

If you only use a USB mouse use the CorePointer option, otherwise use the SendCoreEvents option.

Using XFree86 with GPM

Configure XFree86

In your XF86Config (-4) file:

 Section "InputDevice"
        Identifier "Generic Mouse"
        Driver     "mouse"
 #      Option     "CorePointer"
        Option     "SendCoreEvents"
        Option     "Device"   "/dev/gpmdata"
        Option     "Protocol" "IntelliMouse"
 EndSection

The IntelliMouse driver corresponds to the "repeat_type=ms3" option in gpm.conf, which is the default repeat type in Debian.

On the gpm side of things

To configure gpm use program gpmconfig. For most of the scroll wheel mice I use a type of imps2. That seems to work best.

In a normal setup gpm listens to the port the mouse is connected to and repeats/relays the mouse events to a unix socket /dev/gpmdata. This allows console applications like mc (Midnight Commander) to get mouse events. For X windows to hear the mouse it should be configured to listen to /dev/gpmdata. I've always had the best luck configuring gpm to repeat in raw mode and configure X windows to use whatever protocol the mouse uses. In this setup the mouse type should be set in two places, in gpmconfig and in your X windows configuration. I get the feeling this is a non-standard approach but it's alway given me the least problems.