public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* Configuring x
@  Shaun Oliver
   ` Kirk Wood
  0 siblings, 1 reply; 16+ messages in thread
From: Shaun Oliver @  UTC (permalink / raw)
  To: speakup

[-- Attachment #1: Type: TEXT/PLAIN, Size: 413 bytes --]

does any one here know how to configure x properly? I want to set it up
for my partner to use but I can't seem to get the mouse to work
properly. attached is a copy of my XF86Config file for those in the know.


Shaun..
"Has anyone ever tasted an "END"? Are they really bitter?"
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667

[-- Attachment #2: Type: TEXT/PLAIN, Size: 21433 bytes --]

# File generated by xf86config.

#
# Copyright (c) 1995 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of 
# this file.
# **********************************************************************

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath	"/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
# 

#    FontPath   "/usr/X11R6/lib/X11/fonts/local/"
    FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
    FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"

# For OSs that support Dynamically loaded modules, ModulePath can be
# used to set a search path for the modules.  This is currently supported
# for Linux ELF, FreeBSD 2.x and NetBSD 1.x.  The default path is shown
# here.

#    ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Module section -- this is an optional section which is used to specify
# which dynamically loadable modules to load.  Dynamically loadable
# modules are currently supported only for Linux ELF, FreeBSD 2.x
# and NetBSD 1.x.  Currently, dynamically loadable modules are used
# only for some extended input (XInput) device drivers.
# **********************************************************************
#
# Section "Module"
#
# This loads the module for the Joystick driver
#
# Load "xf86Jstk.so"
# 
# EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is 
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    NoTrapSignals

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    DontZap

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    DontZoom

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#       DisableVidModeExtension

# Uncomment this to enable the use of a non-local xvidtune client. 

#       AllowNonLocalXvidtune

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings. 

#       DisableModInDev

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#       AllowNonLocalModInDev

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Keyboard section
# **********************************************************************

Section "Keyboard"

    Protocol	"Standard"

# when using XQUEUE, comment out the above line, and uncomment the
# following line

#    Protocol	"Xqueue"

    AutoRepeat	500 30
# Let the server do the NumLock processing.  This should only be required
# when using pre-R6 clients
#    ServerNumLock

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Xleds      1 2 3

# To set the LeftAlt to Meta, RightAlt key to ModeShift, 
# RightCtl key to Compose, and ScrollLock key to ModeLock:

#    LeftAlt     Meta
#    RightAlt    ModeShift
#    RightCtl    Compose
#    ScrollLock  ModeLock

# To disable the XKEYBOARD extension, uncomment XkbDisable.

#    XkbDisable

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    XkbModel    "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#    XkbModel    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    XkbLayout   "de"
# or:
#    XkbLayout   "de"
#    XkbVariant  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    XkbOptions  "ctrl:swapcaps"

# These are the default XKB settings for XFree86
#    XkbRules    "xfree86"
#    XkbModel    "pc101"
#    XkbLayout   "us"
#    XkbVariant  ""
#    XkbOptions  ""

    XkbKeymap   "xfree86(us)"


EndSection


# **********************************************************************
# Pointer section
# **********************************************************************

Section "Pointer"
    Protocol    "Microsoft"
    Device      "/dev/mouse"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Protocol	"Xqueue"

# Baudrate and SampleRate are only for some Logitech mice
# or for the AceCad tablets which require 9600 baud

#    BaudRate	9600
#    SampleRate	150

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

    Emulate3Buttons
    Emulate3Timeout    50

# ChordMiddle is an option for some 3-button Logitech mice

#    ChordMiddle

EndSection


# **********************************************************************
# Xinput section -- this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "Xinput" 
#    SubSection "WacomStylus"
#        Port "/dev/ttyS1"
#        DeviceName "Wacom"
#    EndSubSection
#    SubSection "WacomCursor"
#        Port "/dev/ttyS1"
#    EndSubSection
#    SubSection "WacomEraser"
#        Port "/dev/ttyS1"
#    EndSubSection
#
#    SubSection "Elographics"
#        Port "/dev/ttyS1"
#        DeviceName "Elo"
#        MinimumXPosition 300
#        MaximumXPosition 3500
#        MinimumYPosition 300
#        MaximumYPosition 3500
#        Screen 0
#        UntouchDelay 10
#        ReportDelay 10
#    EndSubSection
#
#    SubSection "Joystick"
#        Port "/dev/joy0"
#        DeviceName "Joystick"
#        TimeOut 10
#        MinimumXPosition 100
#        MaximumXPosition 1300
#        MinimumYPosition 100
#        MaximumYPosition 1100
#        # CenterX 700
#        # CenterY 600
#        Delta 20
#    EndSubSection
#
# The Mouse Subsection contains the same type of entries as the
# standard Pointer Section (see above), with the addition of the
# DeviceName entry.
#
#    SubSection "Mouse" 
#        Port "/dev/mouse2"
#        DeviceName "Second Mouse"
#        Protocol "Logitech"
#    EndSubSection
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "My Monitor"
    VendorName  "Unknown"
    ModelName   "Unknown"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   31.5

#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 50-70

# Modes can be specified in two formats.  A compact one-line format, or
# a multi-line format.

# These two are equivalent

#    ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace

#    Mode "1024x768i"
#        DotClock	45
#        HTimings	1024 1048 1208 1264
#        VTimings	768 776 784 817
#        Flags		"Interlace"
#    EndMode

# This is a set of standard mode timings. Modes that are out of monitor spec
# are automatically deleted by the server (provided the HorizSync and
# VertRefresh lines are correct), so there's no immediate need to
# delete mode timings (unless particular mode timings don't work on your
# monitor). With these modes, the best standard mode that your monitor
# and video card can support for a given resolution is automatically
# used.

# 640x400 @ 70 Hz, 31.5 kHz hsync
Modeline "640x400"     25.175 640  664  760  800   400  409  411  450
# 640x480 @ 60 Hz, 31.5 kHz hsync
Modeline "640x480"     25.175 640  664  760  800   480  491  493  525
# 800x600 @ 56 Hz, 35.15 kHz hsync
ModeLine "800x600"     36     800  824  896 1024   600  601  603  625
# 1024x768 @ 87 Hz interlaced, 35.5 kHz hsync
Modeline "1024x768"    44.9  1024 1048 1208 1264   768  776  784  817 Interlace

# 640x400 @ 85 Hz, 37.86 kHz hsync
Modeline "640x400"     31.5   640  672 736   832   400  401  404  445 -HSync +VSync
# 640x480 @ 72 Hz, 36.5 kHz hsync
Modeline "640x480"     31.5   640  680  720  864   480  488  491  521
# 640x480 @ 75 Hz, 37.50 kHz hsync
ModeLine  "640x480"    31.5   640  656  720  840   480  481  484  500 -HSync -VSync
# 800x600 @ 60 Hz, 37.8 kHz hsync
Modeline "800x600"     40     800  840  968 1056   600  601  605  628 +hsync +vsync

# 640x480 @ 85 Hz, 43.27 kHz hsync
Modeline "640x480"     36     640  696  752  832   480  481  484  509 -HSync -VSync
# 1152x864 @ 89 Hz interlaced, 44 kHz hsync
ModeLine "1152x864"    65    1152 1168 1384 1480   864  865  875  985 Interlace

# 800x600 @ 72 Hz, 48.0 kHz hsync
Modeline "800x600"     50     800  856  976 1040   600  637  643  666 +hsync +vsync
# 1024x768 @ 60 Hz, 48.4 kHz hsync
Modeline "1024x768"    65    1024 1032 1176 1344   768  771  777  806 -hsync -vsync

# 640x480 @ 100 Hz, 53.01 kHz hsync
Modeline "640x480"     45.8   640  672  768  864   480  488  494  530 -HSync -VSync
# 1152x864 @ 60 Hz, 53.5 kHz hsync
Modeline  "1152x864"   89.9  1152 1216 1472 1680   864  868  876  892 -HSync -VSync
# 800x600 @ 85 Hz, 55.84 kHz hsync
Modeline  "800x600"    60.75  800  864  928 1088   600  616  621  657 -HSync -VSync

# 1024x768 @ 70 Hz, 56.5 kHz hsync
Modeline "1024x768"    75    1024 1048 1184 1328   768  771  777  806 -hsync -vsync
# 1280x1024 @ 87 Hz interlaced, 51 kHz hsync
Modeline "1280x1024"   80    1280 1296 1512 1568  1024 1025 1037 1165 Interlace

# 800x600 @ 100 Hz, 64.02 kHz hsync
Modeline  "800x600"    69.65  800  864  928 1088   600  604  610  640 -HSync -VSync
# 1024x768 @ 76 Hz, 62.5 kHz hsync
Modeline "1024x768"    85    1024 1032 1152 1360   768  784  787  823
# 1152x864 @ 70 Hz, 62.4 kHz hsync
Modeline  "1152x864"   92    1152 1208 1368 1474   864  865  875  895
# 1280x1024 @ 61 Hz, 64.2 kHz hsync
Modeline "1280x1024"  110    1280 1328 1512 1712  1024 1025 1028 1054

# 1024x768 @ 85 Hz, 70.24 kHz hsync
Modeline "1024x768"   98.9  1024 1056 1216 1408   768 782 788 822 -HSync -VSync
# 1152x864 @ 78 Hz, 70.8 kHz hsync
Modeline "1152x864"   110   1152 1240 1324 1552   864  864  876  908

# 1280x1024 @ 70 Hz, 74.59 kHz hsync
Modeline "1280x1024"  126.5 1280 1312 1472 1696  1024 1032 1040 1068 -HSync -VSync
# 1600x1200 @ 60Hz, 75.00 kHz hsync
Modeline "1600x1200"  162   1600 1664 1856 2160  1200 1201 1204 1250 +HSync +VSync
# 1152x864 @ 84 Hz, 76.0 kHz hsync
Modeline "1152x864"   135    1152 1464 1592 1776   864  864  876  908

# 1280x1024 @ 74 Hz, 78.85 kHz hsync
Modeline "1280x1024"  135    1280 1312 1456 1712  1024 1027 1030 1064

# 1024x768 @ 100Hz, 80.21 kHz hsync
Modeline "1024x768"   115.5  1024 1056 1248 1440  768  771  781  802 -HSync -VSync
# 1280x1024 @ 76 Hz, 81.13 kHz hsync
Modeline "1280x1024"  135    1280 1312 1416 1664  1024 1027 1030 1064

# 1600x1200 @ 70 Hz, 87.50 kHz hsync
Modeline "1600x1200"  189    1600 1664 1856 2160  1200 1201 1204 1250 -HSync -VSync
# 1152x864 @ 100 Hz, 89.62 kHz hsync
Modeline "1152x864"   137.65 1152 1184 1312 1536   864  866  885  902 -HSync -VSync
# 1280x1024 @ 85 Hz, 91.15 kHz hsync
Modeline "1280x1024"  157.5  1280 1344 1504 1728  1024 1025 1028 1072 +HSync +VSync
# 1600x1200 @ 75 Hz, 93.75 kHz hsync
Modeline "1600x1200"  202.5  1600 1664 1856 2160  1200 1201 1204 1250 +HSync +VSync
# 1600x1200 @ 85 Hz, 105.77 kHz hsync
Modeline "1600x1200"  220    1600 1616 1808 2080  1200 1204 1207 1244 +HSync +VSync
# 1280x1024 @ 100 Hz, 107.16 kHz hsync
Modeline "1280x1024"  181.75 1280 1312 1440 1696  1024 1031 1046 1072 -HSync -VSync

# 1800x1440 @ 64Hz, 96.15 kHz hsync 
ModeLine "1800X1440"  230    1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# 1800x1440 @ 70Hz, 104.52 kHz hsync 
ModeLine "1800X1440"  250    1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync

# 512x384 @ 78 Hz, 31.50 kHz hsync
Modeline "512x384"    20.160 512  528  592  640   384  385  388  404 -HSync -VSync
# 512x384 @ 85 Hz, 34.38 kHz hsync
Modeline "512x384"    22     512  528  592  640   384  385  388  404 -HSync -VSync

# Low-res Doublescan modes
# If your chipset does not support doublescan, you get a 'squashed'
# resolution like 320x400.

# 320x200 @ 70 Hz, 31.5 kHz hsync, 8:5 aspect ratio
Modeline "320x200"     12.588 320  336  384  400   200  204  205  225 Doublescan
# 320x240 @ 60 Hz, 31.5 kHz hsync, 4:3 aspect ratio
Modeline "320x240"     12.588 320  336  384  400   240  245  246  262 Doublescan
# 320x240 @ 72 Hz, 36.5 kHz hsync
Modeline "320x240"     15.750 320  336  384  400   240  244  246  262 Doublescan
# 400x300 @ 56 Hz, 35.2 kHz hsync, 4:3 aspect ratio
ModeLine "400x300"     18     400  416  448  512   300  301  302  312 Doublescan
# 400x300 @ 60 Hz, 37.8 kHz hsync
Modeline "400x300"     20     400  416  480  528   300  301  303  314 Doublescan
# 400x300 @ 72 Hz, 48.0 kHz hsync
Modeline "400x300"     25     400  424  488  520   300  319  322  333 Doublescan
# 480x300 @ 56 Hz, 35.2 kHz hsync, 8:5 aspect ratio
ModeLine "480x300"     21.656 480  496  536  616   300  301  302  312 Doublescan
# 480x300 @ 60 Hz, 37.8 kHz hsync
Modeline "480x300"     23.890 480  496  576  632   300  301  303  314 Doublescan
# 480x300 @ 63 Hz, 39.6 kHz hsync
Modeline "480x300"     25     480  496  576  632   300  301  303  314 Doublescan
# 480x300 @ 72 Hz, 48.0 kHz hsync
Modeline "480x300"     29.952 480  504  584  624   300  319  322  333 Doublescan

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier	"Generic VGA"
    VendorName	"Unknown"
    BoardName	"Unknown"
    Chipset	"generic"

#    VideoRam	256

#    Clocks	25.2 28.3

EndSection

# Sample Device for accelerated server:

# Section "Device"
#    Identifier	"Actix GE32+ 2MB"
#    VendorName	"Actix"
#    BoardName	"GE32+"
#    Ramdac	"ATT20C490"
#    Dacspeed	110
#    Option	"dac_8_bit"
#    Clocks	 25.0  28.0  40.0   0.0  50.0  77.0  36.0  45.0
#    Clocks	130.0 120.0  80.0  31.0 110.0  65.0  75.0  94.0
# EndSection

# Sample Device for Hercules mono card:

# Section "Device"
#    Identifier "Hercules mono"
# EndSection

# Device configured by xf86config:

Section "Device"
    Identifier  "Diamond Stealth 64 Video VRAM (TI RAMDAC)"
    VendorName  "Unknown"
    BoardName   "Unknown"
    #VideoRam    256
   #Option "slow_vram"
   #DacSpeed 220
# Use Option "nolinear" if the server doesn't start up correctly
# (this avoids the linear framebuffer probe). If that fails try
# option "nomemaccess".
#
# Refer to /usr/X11R6/lib/doc/README.S3, and the XF86_S3 man page.
    # Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# The Colour SVGA server

Section "Screen"
    Driver      "svga"
    # Use Device "Generic VGA" for Standard VGA 320x200x256
    #Device      "Generic VGA"
    Device      "Diamond Stealth 64 Video VRAM (TI RAMDAC)"
    Monitor     "My Monitor"
    Subsection "Display"
        Depth       8
        # Omit the Modes line for the "Generic VGA" device
        Modes       "640x400"
        ViewPort    0 0
        # Use Virtual 320 200 for Generic VGA
        Virtual     640 400
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "640x480"
        ViewPort    0 0
        Virtual     0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "640x480"
        ViewPort    0 0
        Virtual     0 0
    EndSubsection
    Subsection "Display"
        Depth       32
        Modes	"640x480"       
        ViewPort    0 0
        Virtual     0 0
    EndSubsection
EndSection

# The 16-color VGA server

Section "Screen"
    Driver      "vga16"
    Device      "Generic VGA"
    Monitor     "My Monitor"
    Subsection "Display"
        Modes       "640x480" "800x600"
        ViewPort    0 0
        Virtual     800 600
    EndSubsection
EndSection

# The Mono server

Section "Screen"
    Driver      "vga2"
    Device      "Generic VGA"
    Monitor     "My Monitor"
    Subsection "Display"
        Modes       "640x480" "800x600"
        ViewPort    0 0
        Virtual     800 600
    EndSubsection
EndSection

# The accelerated servers (S3, Mach32, Mach8, 8514, P9000, AGX, W32, Mach64)

Section "Screen"
    Driver      "accel"
    Device      "Diamond Stealth 64 Video VRAM (TI RAMDAC)"
    Monitor     "My Monitor"
    Subsection "Display"
        Depth       8
        Modes       "640x480"
        ViewPort    0 0
        Virtual     640 400
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "640x480"
        ViewPort    0 0
        Virtual     0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "640x480"
        ViewPort    0 0
        Virtual     0 0
    EndSubsection
    Subsection "Display"
        Depth       32
        Modes	"640x480"       
        ViewPort    0 0
        Virtual     0 0
    EndSubsection
EndSection


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
   Configuring x Shaun Oliver
@  ` Kirk Wood
     ` Janina Sajka
     ` Shaun Oliver
  0 siblings, 2 replies; 16+ messages in thread
From: Kirk Wood @  UTC (permalink / raw)
  To: speakup

On Sun, 27 May 2001, Shaun Oliver wrote:
> does any one here know how to configure x properly? I want to set it up
> for my partner to use but I can't seem to get the mouse to work
> properly. attached is a copy of my XF86Config file for those in the know.

There are several configuration programs to use. If you have redhat my
sugestion would be to run "setup". This program will then have an option
to configure X. 

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nothing is hard if you know the answer or are used to doing it.



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
   ` Kirk Wood
@    ` Janina Sajka
       ` Shaun Oliver
     ` Shaun Oliver
  1 sibling, 1 reply; 16+ messages in thread
From: Janina Sajka @  UTC (permalink / raw)
  To: speakup

If you're running Redhat, try using Xconfigurator. That's a command.


On Mon, 28 May 2001, Kirk Wood wrote:

> On Sun, 27 May 2001, Shaun Oliver wrote:
> > does any one here know how to configure x properly? I want to set it up
> > for my partner to use but I can't seem to get the mouse to work
> > properly. attached is a copy of my XF86Config file for those in the know.
>
> There are several configuration programs to use. If you have redhat my
> sugestion would be to run "setup". This program will then have an option
> to configure X.
>
> =======
> Kirk Wood
> Cpt.Kirk@1tree.net
>
> Nothing is hard if you know the answer or are used to doing it.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
   ` Kirk Wood
     ` Janina Sajka
@    ` Shaun Oliver
  1 sibling, 0 replies; 16+ messages in thread
From: Shaun Oliver @  UTC (permalink / raw)
  To: speakup

I'm using slackware 7.1 and the only tool I see there is the xf86config
tool.


Shaun..
"We realise we have a problem with communication. However, we're not going
to discuss it with our staff."
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667

On Mon, 28 May 2001, Kirk Wood wrote:

> On Sun, 27 May 2001, Shaun Oliver wrote:
> > does any one here know how to configure x properly? I want to set it up
> > for my partner to use but I can't seem to get the mouse to work
> > properly. attached is a copy of my XF86Config file for those in the know.
> 
> There are several configuration programs to use. If you have redhat my
> sugestion would be to run "setup". This program will then have an option
> to configure X. 
> 
> =======
> Kirk Wood
> Cpt.Kirk@1tree.net
> 
> Nothing is hard if you know the answer or are used to doing it.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
     ` Janina Sajka
@      ` Shaun Oliver
         ` Kirk Wood
  0 siblings, 1 reply; 16+ messages in thread
From: Shaun Oliver @  UTC (permalink / raw)
  To: speakup

as I mentioned in an earlier message, I'm using slackware.


Shaun..
"We realise we have a problem with communication. However, we're not going
to discuss it with our staff."
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667

On Mon, 28 May 2001, Janina Sajka wrote:

> If you're running Redhat, try using Xconfigurator. That's a command.
> 
> 
> On Mon, 28 May 2001, Kirk Wood wrote:
> 
> > On Sun, 27 May 2001, Shaun Oliver wrote:
> > > does any one here know how to configure x properly? I want to set it up
> > > for my partner to use but I can't seem to get the mouse to work
> > > properly. attached is a copy of my XF86Config file for those in the know.
> >
> > There are several configuration programs to use. If you have redhat my
> > sugestion would be to run "setup". This program will then have an option
> > to configure X.
> >
> > =======
> > Kirk Wood
> > Cpt.Kirk@1tree.net
> >
> > Nothing is hard if you know the answer or are used to doing it.
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
         ` Kirk Wood
@          ` Shaun Oliver
             ` Gregory Nowak
             ` Kirk Wood
  0 siblings, 2 replies; 16+ messages in thread
From: Shaun Oliver @  UTC (permalink / raw)
  To: speakup

I did that all ok I picked the devices and what all else I needed to pick
and it wrote the file, the problem is I can't seem to get the mouse to
move.


Shaun..
"We realise we have a problem with communication. However, we're not going
to discuss it with our staff."
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667

On Wed, 30 May 2001, Kirk Wood wrote:

> So what happens when you run xfconfig?
> 
> I would recomend choosing the most conservative settings to start.
> 
> =======
> Kirk Wood
> Cpt.Kirk@1tree.net
> 
> Nothing is hard if you know the answer or are used to doing it.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
       ` Shaun Oliver
@        ` Kirk Wood
           ` Shaun Oliver
  0 siblings, 1 reply; 16+ messages in thread
From: Kirk Wood @  UTC (permalink / raw)
  To: speakup

So what happens when you run xfconfig?

I would recomend choosing the most conservative settings to start.

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nothing is hard if you know the answer or are used to doing it.



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
           ` Shaun Oliver
@            ` Gregory Nowak
               ` Janina Sajka
               ` Shaun Oliver
             ` Kirk Wood
  1 sibling, 2 replies; 16+ messages in thread
From: Gregory Nowak @  UTC (permalink / raw)
  To: speakup

Did you disable gpm at startup? I believe the settings for that are in /etc/rc.d/rc.gpm, but I'm not sure of the filename.
Greg


On Wed, May 30, 2001 at 10:42:31PM +1000, Shaun Oliver wrote:
> I did that all ok I picked the devices and what all else I needed to pick
> and it wrote the file, the problem is I can't seem to get the mouse to
> move.
> 
> 
> Shaun..
> "We realise we have a problem with communication. However, we're not going
> to discuss it with our staff."
> EMAIL: shauno@goanna.net.au ICQ: 76958435
> YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
> www.jong.com:6667
> 
> On Wed, 30 May 2001, Kirk Wood wrote:
> 
> > So what happens when you run xfconfig?
> > 
> > I would recomend choosing the most conservative settings to start.
> > 
> > =======
> > Kirk Wood
> > Cpt.Kirk@1tree.net
> > 
> > Nothing is hard if you know the answer or are used to doing it.
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
             ` Gregory Nowak
@              ` Janina Sajka
               ` Shaun Oliver
  1 sibling, 0 replies; 16+ messages in thread
From: Janina Sajka @  UTC (permalink / raw)
  To: speakup

You need to enable GPM for run level 5. It can most certainly still be off
in run level 3.

On Wed, 30 May 2001, Gregory Nowak wrote:

> Did you disable gpm at startup? I believe the settings for that are in /etc/rc.d/rc.gpm, but I'm not sure of the filename.
> Greg
>
>
> On Wed, May 30, 2001 at 10:42:31PM +1000, Shaun Oliver wrote:
> > I did that all ok I picked the devices and what all else I needed to pick
> > and it wrote the file, the problem is I can't seem to get the mouse to
> > move.
> >
> >
> > Shaun..
> > "We realise we have a problem with communication. However, we're not going
> > to discuss it with our staff."
> > EMAIL: shauno@goanna.net.au ICQ: 76958435
> > YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
> > www.jong.com:6667
> >
> > On Wed, 30 May 2001, Kirk Wood wrote:
> >
> > > So what happens when you run xfconfig?
> > >
> > > I would recomend choosing the most conservative settings to start.
> > >
> > > =======
> > > Kirk Wood
> > > Cpt.Kirk@1tree.net
> > >
> > > Nothing is hard if you know the answer or are used to doing it.
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
           ` Shaun Oliver
             ` Gregory Nowak
@            ` Kirk Wood
               ` Shaun Oliver
               ` John Covici
  1 sibling, 2 replies; 16+ messages in thread
From: Kirk Wood @  UTC (permalink / raw)
  To: speakup

On Wed, 30 May 2001, Shaun Oliver wrote:
> I did that all ok I picked the devices and what all else I needed to pick
> and it wrote the file, the problem is I can't seem to get the mouse to
> move.

First, thanks for the information. It is much easier to troubleshoot a
specific problem. Do you have gpm loaded? If you don't, I would start
there. If memory serves correct, the "normal" means of getting the mouse
are taking info from gpm. It will also help find any problem that may
exist in hardware. If it is working you should be able to move a large
block cursor arround in a text screen. If you leave the mouse alone the
cursor drops from view.

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nothing is hard if you know the answer or are used to doing it.



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
             ` Gregory Nowak
               ` Janina Sajka
@              ` Shaun Oliver
                 ` Kirk Wood
                 ` Gregory Nowak
  1 sibling, 2 replies; 16+ messages in thread
From: Shaun Oliver @  UTC (permalink / raw)
  To: speakup

no I didn't. does gpm present a problem for x?


Shaun..
"We realise we have a problem with communication. However, we're not going
to discuss it with our staff."
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667

On Wed, 30 May 2001, Gregory Nowak wrote:

> Did you disable gpm at startup? I believe the settings for that are in /etc/rc.d/rc.gpm, but I'm not sure of the filename.
> Greg
> 
> 
> On Wed, May 30, 2001 at 10:42:31PM +1000, Shaun Oliver wrote:
> > I did that all ok I picked the devices and what all else I needed to pick
> > and it wrote the file, the problem is I can't seem to get the mouse to
> > move.
> > 
> > 
> > Shaun..
> > "We realise we have a problem with communication. However, we're not going
> > to discuss it with our staff."
> > EMAIL: shauno@goanna.net.au ICQ: 76958435
> > YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
> > www.jong.com:6667
> > 
> > On Wed, 30 May 2001, Kirk Wood wrote:
> > 
> > > So what happens when you run xfconfig?
> > > 
> > > I would recomend choosing the most conservative settings to start.
> > > 
> > > =======
> > > Kirk Wood
> > > Cpt.Kirk@1tree.net
> > > 
> > > Nothing is hard if you know the answer or are used to doing it.
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
             ` Kirk Wood
@              ` Shaun Oliver
               ` John Covici
  1 sibling, 0 replies; 16+ messages in thread
From: Shaun Oliver @  UTC (permalink / raw)
  To: speakup

kirk right at the moment, gpm is loaded. I don't use it personally but who
knows, it might come in handy.


Shaun..
"We realise we have a problem with communication. However, we're not going
to discuss it with our staff."
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667

On Wed, 30 May 2001, Kirk Wood wrote:

> On Wed, 30 May 2001, Shaun Oliver wrote:
> > I did that all ok I picked the devices and what all else I needed to pick
> > and it wrote the file, the problem is I can't seem to get the mouse to
> > move.
> 
> First, thanks for the information. It is much easier to troubleshoot a
> specific problem. Do you have gpm loaded? If you don't, I would start
> there. If memory serves correct, the "normal" means of getting the mouse
> are taking info from gpm. It will also help find any problem that may
> exist in hardware. If it is working you should be able to move a large
> block cursor arround in a text screen. If you leave the mouse alone the
> cursor drops from view.
> 
> =======
> Kirk Wood
> Cpt.Kirk@1tree.net
> 
> Nothing is hard if you know the answer or are used to doing it.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
                 ` Kirk Wood
@                  ` Shaun Oliver
  0 siblings, 0 replies; 16+ messages in thread
From: Shaun Oliver @  UTC (permalink / raw)
  To: speakup

I honestly wouldn't know.
I'll give it a try and get back to u.


Shaun..
"We realise we have a problem with communication. However, we're not going
to discuss it with our staff."
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667

On Thu, 31 May 2001, Kirk Wood wrote:

> On Thu, 31 May 2001, Shaun Oliver wrote:
> > no I didn't. does gpm present a problem for x?
> 
> Umm, no I think I mentioned that the default method is for X to get mouse
> info from gpm. Would be a problem if they conflicted. The point is does
> gpm work?
> 
> If the answer here is no, then focus on that instead of X.
> 
> =======
> Kirk Wood
> Cpt.Kirk@1tree.net
> 
> Nothing is hard if you know the answer or are used to doing it.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
               ` Shaun Oliver
@                ` Kirk Wood
                   ` Shaun Oliver
                 ` Gregory Nowak
  1 sibling, 1 reply; 16+ messages in thread
From: Kirk Wood @  UTC (permalink / raw)
  To: speakup

On Thu, 31 May 2001, Shaun Oliver wrote:
> no I didn't. does gpm present a problem for x?

Umm, no I think I mentioned that the default method is for X to get mouse
info from gpm. Would be a problem if they conflicted. The point is does
gpm work?

If the answer here is no, then focus on that instead of X.

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nothing is hard if you know the answer or are used to doing it.



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
               ` Shaun Oliver
                 ` Kirk Wood
@                ` Gregory Nowak
  1 sibling, 0 replies; 16+ messages in thread
From: Gregory Nowak @  UTC (permalink / raw)
  To: speakup

I'm not sure about that. However, the docs say that if x refuses to start and complains about your mouse,
that's what you should do.
Greg

On Thu, May 31, 2001 at 08:12:54PM +1000, Shaun Oliver wrote:
> no I didn't. does gpm present a problem for x?
> 
> 
> Shaun..
> "We realise we have a problem with communication. However, we're not going
> to discuss it with our staff."
> EMAIL: shauno@goanna.net.au ICQ: 76958435
> YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
> www.jong.com:6667
> 
> On Wed, 30 May 2001, Gregory Nowak wrote:
> 
> > Did you disable gpm at startup? I believe the settings for that are in /etc/rc.d/rc.gpm, but I'm not sure of the filename.
> > Greg
> > 
> > 
> > On Wed, May 30, 2001 at 10:42:31PM +1000, Shaun Oliver wrote:
> > > I did that all ok I picked the devices and what all else I needed to pick
> > > and it wrote the file, the problem is I can't seem to get the mouse to
> > > move.
> > > 
> > > 
> > > Shaun..
> > > "We realise we have a problem with communication. However, we're not going
> > > to discuss it with our staff."
> > > EMAIL: shauno@goanna.net.au ICQ: 76958435
> > > YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
> > > www.jong.com:6667
> > > 
> > > On Wed, 30 May 2001, Kirk Wood wrote:
> > > 
> > > > So what happens when you run xfconfig?
> > > > 
> > > > I would recomend choosing the most conservative settings to start.
> > > > 
> > > > =======
> > > > Kirk Wood
> > > > Cpt.Kirk@1tree.net
> > > > 
> > > > Nothing is hard if you know the answer or are used to doing it.
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Configuring x
             ` Kirk Wood
               ` Shaun Oliver
@              ` John Covici
  1 sibling, 0 replies; 16+ messages in thread
From: John Covici @  UTC (permalink / raw)
  To: speakup

Well, I had to disable gpm to get my mouse to work at all under x.
Then I changed the mouse device to /dev/psaux and away it went.

Kirk Wood <cpt.kirk@1tree.net> writes:

> On Wed, 30 May 2001, Shaun Oliver wrote:
> > I did that all ok I picked the devices and what all else I needed to pick
> > and it wrote the file, the problem is I can't seem to get the mouse to
> > move.
> 
> First, thanks for the information. It is much easier to troubleshoot a
> specific problem. Do you have gpm loaded? If you don't, I would start
> there. If memory serves correct, the "normal" means of getting the mouse
> are taking info from gpm. It will also help find any problem that may
> exist in hardware. If it is working you should be able to move a large
> block cursor arround in a text screen. If you leave the mouse alone the
> cursor drops from view.
> 
> =======
> Kirk Wood
> Cpt.Kirk@1tree.net
> 
> Nothing is hard if you know the answer or are used to doing it.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
         John Covici
         covici@ccs.covici.com


^ permalink raw reply	[flat|nested] 16+ messages in thread

end of thread, other threads:[~ UTC | newest]

Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 Configuring x Shaun Oliver
 ` Kirk Wood
   ` Janina Sajka
     ` Shaun Oliver
       ` Kirk Wood
         ` Shaun Oliver
           ` Gregory Nowak
             ` Janina Sajka
             ` Shaun Oliver
               ` Kirk Wood
                 ` Shaun Oliver
               ` Gregory Nowak
           ` Kirk Wood
             ` Shaun Oliver
             ` John Covici
   ` Shaun Oliver

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).