Mar 19

Guardian Angel Linux and the Tritton See2 USB VGA Adapter

By adminNo Comments

I bought a Tritton See2 USB VGAAdapter and configured it to be used with Guardian Angel Linux. Other current Linux versions most likely already have the kernel and the Xorg drivers included as well. To get the Tritton See2 USBVGA functionalusing the Linux sisusbvga kernel module (already supplied with Guardian Angel Linux) and the sisusb Xorg driver (already supplied with Guardian Angel Linux) I just needed to:

  1. Connect the Monitor to the See2 USBVGA adapter
  2. Plug the adapter into the USB port
  3. Configure the Xorg configuration file with the proper values (pay particular attention to the Horizontal and Vertical frequencies)
  4. Restart Xwindows (CTRL-ALT-BACKSPACE)

Potential driver conflicts are with:

  • SANE and USB scanners. Scanning fails and sometimes USBVGA adapter freezes. Both conditions seem to be reset if the USB scanner and/or the USBVGA adapter is unplugged and replugged. Use one or the other… not both.
  • USB Audio Adapter. If both are plugged in during boot up, the Audio does not output sound. Booting with Audio Adapter plugged in and USBVGA adapter not plugged in, allows sound to work. Then plugging in the USBVGA adapter and initializing X-Windows seems to work fine. (I must confirm this)

In summary, the xorg.conf file additions are as follows:
xorg.conf (separate desktops- one standard e.g. laptop monitor and one See2 USBVGA)

Section “Device”
Identifier “Device[SISUSBVGA]”
VendorName “SiS” # Value does not matter
BoardName “SiS” # Value does not matter
Driver “sisusb”
EndSectionSection “Monitor”
Identifier “Monitor[SISUSBVGA]”
VendorName “Monitor Vendor” # value does not matter
ModelName “Monitor Model” # value does not matter
VertRefresh 60-85
HorizSync 60-90
EndSectionSection “Screen”
Identifier “Screen[SISUSBVGA]”
Device “Device[SISUSBVGA]”
Monitor “Monitor[SISUSBVGA]”
DefaultDepth 24
SubSection “Display”
Depth 16
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 8
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 24
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
EndSection

# **********************************************************************
# ServerLayout sections. Add the following:
# **********************************************************************
Section “ServerLayout”

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# left of screen 1.

Screen 0 “Screen 1″
Screen 1 “Screen[SISUSBVGA]” LeftOf “Screen 1″

EndSection



xorg.conf (One desktop across two monitors- one standard e.g. laptop monitor and one See2 USBVGA)

Section “Module”# This loads the DBE extension module.Load “dbe” # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection “extmod”
Option “omit xfree86-dga” # don’t initialise the DGA extension
EndSubSection

# This loads the font modules
Load “type1″
Load “freetype”
#Load “speedo”

# This loads the GLX module
Load “glx”

Load “fbdevhw”
Load “record”
Load “dri”

EndSection

Section “Device”
Identifier “Device[SISUSBVGA]”
VendorName “SiS” # Value does not matter
BoardName “SiS” # Value does not matter
Driver “sisusb”
EndSection

Section “Monitor”
Identifier “Monitor[SISUSBVGA]”
VendorName “Monitor Vendor” # value does not matter
ModelName “Monitor Model” # value does not matter
VertRefresh 60-85
HorizSync 60-90
Option “dpms”
EndSection

Section “Screen”
Identifier “Screen[SISUSBVGA]”
Device “Device[SISUSBVGA]”
Monitor “Monitor[SISUSBVGA]”
DefaultDepth 24
SubSection “Display”
Depth 16
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 8
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 24
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************
Section “ServerLayout”

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# left of screen 1.

Screen 0 “Screen 1″
Screen 1 “Screen[SISUSBVGA]” LeftOf “Screen 1″

Option “Xinerama” “on”
Option “Clone” “off”

EndSection

Section “DRI”
Group 0
Mode 0666
EndSection

Check the sisusbvga page for more configuration details for setting up virtual terminals (consoles) and multiple See2 Dongles..

Monitor configuration: The driver does not support DDC. Hence, you need to set up the Monitor section according to your monitor’s specifications, ie give properHorizSync and VertRefresh ranges. See the example XF86Config file in the download section below for an example.

Multiple dongles: If you want to connect more than one of these devices to your box, there is something more to do: The driver uses the BusID tag in the Devicesection for hardware device identification. If you have only one USB2VGA dongle, you don’t need to set the BusID at all then. If you have two or more such devices and want them to be used in a certain order, specify the device node names in the BusID string, such as BusID “USB:/dev/mydevicename” where the parameter following the “USB:” substring is the complete name (including the path) of the device node. Alternatively, you can specify an integer number which will be prepended by “sisusbvga” which is the default device node name (if no udev rule exists).


1) Make sure the USBVGA dongle is seen
lsusb yields

Bus 1 Device 14: ID 0711:0900 Magic Control Technology Corp. SVGA Adapter


2) Make sure the sisusbvga is loaded by checking the output of lsmod

lsmod | grep sisusbvga


If the module is not loaded, load it with the following command:

modprobe sisusbvga


3) Setup the xorg.conf file
This if for two separate monitors with the sisusbvga monitor to the left of the main display.

Example xorg.conf (two separate desktops- one standard e.g. laptop monitor and one See2 USBVGA)

# File generated by xf86config.#
# Copyright (c) 1999 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.
# **********************************************************************

# NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed
# this out to me. :)

# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).

# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# — volkerdi@slackware.com
#

# **********************************************************************
# Module section — this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section “Module”

# This loads the DBE extension module.

Load “dbe” # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection “extmod”
Option “omit xfree86-dga” # don’t initialise the DGA extension
EndSubSection

# This loads the font modules
Load “type1″
Load “freetype”
#Load “speedo”

# This loads the GLX module
Load “glx”

EndSection

# **********************************************************************
# 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/CID/”
FontPath “/usr/X11R6/lib/X11/fonts/Speedo/”
FontPath “/usr/X11R6/lib/X11/fonts/75dpi/”
FontPath “/usr/X11R6/lib/X11/fonts/100dpi/”
FontPath “/usr/X11R6/lib/X11/fonts/cyrillic/”

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

# ModulePath “/usr/X11R6/lib/modules”

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

# Option “NoTrapSignals”

# Uncomment this to disable the VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option “DontVTSwitch”

# Uncomment this to disable the server abort sequence
# This allows clients to receive this key event.

# Option “DontZap”

# Uncomment this to disable the / mode switching
# sequences. This allows clients to receive these key events.

# Option “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.

# Option “DisableVidModeExtension”

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

# Option “AllowNonLocalXvidtune”

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

# Option “DisableModInDev”

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

# Option “AllowNonLocalModInDev”

# Set the basic blanking screen saver timeout.

# Option “blank time” “10″ # 10 minutes

# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don’t enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

# Option “standby time” “20″
# Option “suspend time” “30″
# Option “off time” “60″

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don’t overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option “EstimateSizesAggresively” “0″

EndSection

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

# **********************************************************************
# Core keyboard’s InputDevice section
# **********************************************************************

Section “InputDevice”

Identifier “Keyboard1″
Driver “kbd”
# For most OSs the protocol can be omitted (it defaults to “Standard”).
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option “Protocol” “Xqueue”

# Set the keyboard auto repeat parameters. Not all platforms implement
# this.

# Option “AutoRepeat” “500 5″

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

# Option “Xleds” “1 2 3″

# To disable the XKEYBOARD extension, uncomment XkbDisable.

# Option “XkbDisable”

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

# These are the default XKB settings for X.Org
#
# Option “XkbRules” “xorg”
# Option “XkbModel” “pc101″
# Option “XkbLayout” “us”
# Option “XkbVariant” “”
# Option “XkbOptions” “”

EndSection

# **********************************************************************
# Core Pointer’s InputDevice section
# **********************************************************************

Section “InputDevice”

# Identifier and driver

Identifier “Mouse1″
Driver “mouse”

Option “ZAxisMapping” “4 5″
Option “Buttons” “3″

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

# Option “Protocol” “Auto”

# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
Option “Protocol” “IMPS/2″

# The mouse device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

Option “Device” “/dev/mouse”
# Option “Device” “/dev/psaux”
# Option “Device” “/dev/ttyS0″
# Option “Device” “/dev/ttyS1″

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

# Option “Protocol” “Xqueue”

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option “BaudRate” “9600″
# Option “SampleRate” “150″

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

# Option “Emulate3Buttons”
# Option “Emulate3Timeout” “50″

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

# Option “ChordMiddle”

EndSection

# Some examples of extended input devices

# Section “InputDevice”
# Identifier “spaceball”
# Driver “magellan”
# Option “Device” “/dev/cua0″
# EndSection
#
# Section “InputDevice”
# Identifier “spaceball2″
# Driver “spaceorb”
# Option “Device” “/dev/cua0″
# EndSection
#
# Section “InputDevice”
# Identifier “touchscreen0″
# Driver “microtouch”
# Option “Device” “/dev/ttyS0″
# Option “MinX” “1412″
# Option “MaxX” “15184″
# Option “MinY” “15372″
# Option “MaxY” “1230″
# Option “ScreenNumber” “0″
# Option “ReportingMode” “Scaled”
# Option “ButtonNumber” “1″
# Option “SendCoreEvents”
# EndSection
#
# Section “InputDevice”
# Identifier “touchscreen1″
# Driver “elo2300″
# Option “Device” “/dev/ttyS0″
# Option “MinX” “231″
# Option “MaxX” “3868″
# Option “MinY” “3858″
# Option “MaxY” “272″
# Option “ScreenNumber” “0″
# Option “ReportingMode” “Scaled”
# Option “ButtonThreshold” “17″
# Option “ButtonNumber” “1″
# Option “SendCoreEvents”
# EndSection

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

# Any number of monitor sections may be present

Section “Monitor”

Identifier “My Monitor”

# 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 – 150.0

# 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 75-85

EndSection

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

# Any number of graphics device sections may be present

Section “Device”
Identifier “VESA Framebuffer”
Driver “vesa”
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection

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

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the “-screen”
# option.
Section “Screen”
Identifier “Screen 1″
Device “VESA Framebuffer”
Monitor “My Monitor”

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32

# “1024×768″ is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# “1152×864″, “1280×1024″, “1600×1200″, and “1800×1400″ (or whatever your
# card/monitor can produce)

Subsection “Display”
Depth 8
Modes “1024×768″ “800×600″ “640×480″
EndSubsection
Subsection “Display”
Depth 16
Modes “1024×768″ “800×600″ “640×480″
EndSubsection
Subsection “Display”
Depth 24
Modes “1024×768″ “800×600″ “640×480″
EndSubsection
Subsection “Display”
Depth 32
Modes “1024×768″ “800×600″ “640×480″
EndSubsection

EndSection

Section “Device”
Identifier “Device[SISUSBVGA]”
VendorName “SiS” # Value does not matter
BoardName “SiS” # Value does not matter
Driver “sisusb”
EndSection

Section “Monitor”
Identifier “Monitor[SISUSBVGA]”
VendorName “Monitor Vendor” # value does not matter
ModelName “Monitor Model” # value does not matter
VertRefresh 60-85
HorizSync 60-90
EndSection

Section “Screen”
Identifier “Screen[SISUSBVGA]”
Device “Device[SISUSBVGA]”
Monitor “Monitor[SISUSBVGA]”
DefaultDepth 24
SubSection “Display”
Depth 16
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 8
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 24
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# “-layout” option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section “ServerLayout”

# The Identifier line must be present
Identifier “Simple Layout”

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# left of screen 1.

Screen 0 “Screen 1″
Screen 1 “Screen[SISUSBVGA]” LeftOf “Screen 1″

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include “CorePointer”, “CoreKeyboard” and
# “SendCoreEvents”.

InputDevice “Mouse1″ “CorePointer”
InputDevice “Keyboard1″ “CoreKeyboard”

EndSection


OR

If you want 1 desktop across 2 monitors you must use a Xinerama configuration. This is for two separate monitors with the sisusb monitor to the left of the main display.

Example xorg.conf (one desktop across two monitors- one standard e.g. laptop monitor and one See2 USBVGA)

# File generated by xf86config.#
# Copyright (c) 1999 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.
# **********************************************************************

# NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed
# this out to me. :)

# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).

# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# — volkerdi@slackware.com
#

# **********************************************************************
# Module section — this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section “Module”

# This loads the DBE extension module.

Load “dbe” # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection “extmod”
Option “omit xfree86-dga” # don’t initialise the DGA extension
EndSubSection

# This loads the font modules
Load “type1″
Load “freetype”
#Load “speedo”

# This loads the GLX module
Load “glx”

Load “fbdevhw”
Load “record”
Load “dri”

EndSection

# **********************************************************************
# 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/CID/”
FontPath “/usr/X11R6/lib/X11/fonts/Speedo/”
FontPath “/usr/X11R6/lib/X11/fonts/75dpi/”
FontPath “/usr/X11R6/lib/X11/fonts/100dpi/”
FontPath “/usr/X11R6/lib/X11/fonts/cyrillic/”

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

# ModulePath “/usr/X11R6/lib/modules”

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

# Option “NoTrapSignals”

# Uncomment this to disable the VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option “DontVTSwitch”

# Uncomment this to disable the server abort sequence
# This allows clients to receive this key event.

# Option “DontZap”

# Uncomment this to disable the / mode switching
# sequences. This allows clients to receive these key events.

# Option “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.

# Option “DisableVidModeExtension”

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

# Option “AllowNonLocalXvidtune”

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

# Option “DisableModInDev”

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

# Option “AllowNonLocalModInDev”

# Set the basic blanking screen saver timeout.

# Option “blank time” “10″ # 10 minutes

# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don’t enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

# Option “standby time” “20″
# Option “suspend time” “30″
# Option “off time” “60″

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don’t overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option “EstimateSizesAggresively” “0″

EndSection

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

# **********************************************************************
# Core keyboard’s InputDevice section
# **********************************************************************

Section “InputDevice”

Identifier “Keyboard1″
Driver “kbd”
# For most OSs the protocol can be omitted (it defaults to “Standard”).
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option “Protocol” “Xqueue”

# Set the keyboard auto repeat parameters. Not all platforms implement
# this.

# Option “AutoRepeat” “500 5″

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

# Option “Xleds” “1 2 3″

# To disable the XKEYBOARD extension, uncomment XkbDisable.

# Option “XkbDisable”

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

# These are the default XKB settings for X.Org
#
# Option “XkbRules” “xorg”
# Option “XkbModel” “pc101″
# Option “XkbLayout” “us”
# Option “XkbVariant” “”
# Option “XkbOptions” “”

EndSection

# **********************************************************************
# Core Pointer’s InputDevice section
# **********************************************************************

Section “InputDevice”

# Identifier and driver

Identifier “Mouse1″
Driver “mouse”

Option “ZAxisMapping” “4 5″
Option “Buttons” “3″

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

# Option “Protocol” “Auto”

# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
Option “Protocol” “IMPS/2″

# The mouse device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

Option “Device” “/dev/mouse”
# Option “Device” “/dev/psaux”
# Option “Device” “/dev/ttyS0″
# Option “Device” “/dev/ttyS1″

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

# Option “Protocol” “Xqueue”

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option “BaudRate” “9600″
# Option “SampleRate” “150″

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

# Option “Emulate3Buttons”
# Option “Emulate3Timeout” “50″

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

# Option “ChordMiddle”

EndSection

# Some examples of extended input devices

# Section “InputDevice”
# Identifier “spaceball”
# Driver “magellan”
# Option “Device” “/dev/cua0″
# EndSection
#
# Section “InputDevice”
# Identifier “spaceball2″
# Driver “spaceorb”
# Option “Device” “/dev/cua0″
# EndSection
#
# Section “InputDevice”
# Identifier “touchscreen0″
# Driver “microtouch”
# Option “Device” “/dev/ttyS0″
# Option “MinX” “1412″
# Option “MaxX” “15184″
# Option “MinY” “15372″
# Option “MaxY” “1230″
# Option “ScreenNumber” “0″
# Option “ReportingMode” “Scaled”
# Option “ButtonNumber” “1″
# Option “SendCoreEvents”
# EndSection
#
# Section “InputDevice”
# Identifier “touchscreen1″
# Driver “elo2300″
# Option “Device” “/dev/ttyS0″
# Option “MinX” “231″
# Option “MaxX” “3868″
# Option “MinY” “3858″
# Option “MaxY” “272″
# Option “ScreenNumber” “0″
# Option “ReportingMode” “Scaled”
# Option “ButtonThreshold” “17″
# Option “ButtonNumber” “1″
# Option “SendCoreEvents”
# EndSection

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

# Any number of monitor sections may be present

Section “Monitor”

Identifier “My Monitor”

# 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 – 150.0

# 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 75-85
Option “dpms”

EndSection

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

# Any number of graphics device sections may be present

Section “Device”
Identifier “VESA Framebuffer”
Driver “vesa”
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection

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

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the “-screen”
# option.
Section “Screen”
Identifier “Screen 1″
Device “VESA Framebuffer”
Monitor “My Monitor”

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32

# “1024×768″ is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# “1152×864″, “1280×1024″, “1600×1200″, and “1800×1400″ (or whatever your
# card/monitor can produce)

Subsection “Display”
Depth 8
Modes “1024×768″ “800×600″ “640×480″
EndSubsection
Subsection “Display”
Depth 16
Modes “1024×768″ “800×600″ “640×480″
EndSubsection
Subsection “Display”
Depth 24
Modes “1024×768″ “800×600″ “640×480″
EndSubsection
Subsection “Display”
Depth 32
Modes “1024×768″ “800×600″ “640×480″
EndSubsection

EndSection

Section “Device”
Identifier “Device[SISUSBVGA]”
VendorName “SiS” # Value does not matter
BoardName “SiS” # Value does not matter
Driver “sisusb”
EndSection

Section “Monitor”
Identifier “Monitor[SISUSBVGA]”
VendorName “Monitor Vendor” # value does not matter
ModelName “Monitor Model” # value does not matter
VertRefresh 60-85
HorizSync 60-90
Option “dpms”
EndSection

Section “Screen”
Identifier “Screen[SISUSBVGA]”
Device “Device[SISUSBVGA]”
Monitor “Monitor[SISUSBVGA]”
DefaultDepth 24
SubSection “Display”
Depth 16
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 8
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
SubSection “Display”
Depth 24
Modes “1024×768″ “800×600″ “640×480″
EndSubSection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# “-layout” option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section “ServerLayout”

# The Identifier line must be present
Identifier “Simple Layout”

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# left of screen 1.

Screen 0 “Screen 1″
Screen 1 “Screen[SISUSBVGA]” LeftOf “Screen 1″

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include “CorePointer”, “CoreKeyboard” and
# “SendCoreEvents”.

InputDevice “Mouse1″ “CorePointer”
InputDevice “Keyboard1″ “CoreKeyboard”

Option “Xinerama” “on”
Option “Clone” “off”

EndSection

Section “DRI”
Group 0
Mode 0666
EndSection

4) Restart Xwindows (CTRL-ALT-BACKSPACE)

Guardian Angel Linux
Dec 06

GAL and UT-41 GPS

By adminNo Comments

GPS devices are getting very inexpensive. USB and Bluetooth GPS devices are in the sub $35 range and the UT-41 is once such device. As part of the SSI Smart Car Initiative, low cost GPS and Mobile Internet solutions are being evaluated. G.A.L. is the perfect in car Operating System since it is small, memory and USB based, and has drop in expandability.


First I compiled gpsd from the source code. It was easy, just a get the source,
gpsd Project Home Page

configure;make;make install

I connected the UT-41 GPS to the PC and then typed the following at the command prompt:

gpsd /dev/tts/USB0

Yes that is a ‘tts’

Then I nc localhost 2947 on the G.A.L. box, hit return and at the GPSD prompt typed “r” and data began popping up. COOL!

Note: If you reboot without replugging in the UT-41 GPS, you will not see the device. To see it, do the following:

rmmod pl2303
modprobe pl2303

Then I took on the task of compiling RoadNav and GPSDrive. G.A.L. has all the needed dependencies needed for both applications. The compilation was a snap… just a typical ./configure;make;make install.

Just for the curious, the following (at least) are used:

glib-2.12.4
atk-1.9.1
fontconfig-2.4.1
freetype-2.2.1
jpeg-6b
libpng-1.2.8
tiff-3.7.4
cairo-1.2.0
pango-1.14.7
gtk+-2.10.6
wxWidgets-2.6.3

RoadNav and GPSDrive were simple to build and install but if you don’t want to experience to code rush of compilation, you can just download and install the needed modules. You can find the needed modules here:

-module references here-

RoadNav

RoadNav is an in-car navigation system capable of running on a variety of operating systems, including Linux, Windows, and Mac OS X. Roadnav can obtain a car’s present location from a GPS unit, plot street maps of the area, and provide verbal turn by turn directions to any location in the USA. Roadnav uses the free TIGER/Line files from the US Census Bureau to build the maps, along with the GNIS state and topical gazetteer data from the USGS to identify locations.
Project Home page: roadnav.sourceforge.net

GPSDrive
GpsDrive is a car (bike, ship, plane) navigation system. GpsDrive displays your position provided from your NMEA capable GPS receiver on a zoomable map, the map file is autoselected depending of the position and prefered scale. Speech output is supported if the “festival” software is running. The maps are autoselected for best resolution depending of your position and can be downloaded from Internet. All Garmin GPS reveiver with a serial output should be usable, also other GPS receiver which supports NMEA protocol.
GpsDrive is written in C with use of the GTK+ graphic toolkit and runs with Linux and FreeBSD.
Project Home Page:www.gpsdrive.cc

The UT-41 is a USB based GPS.
geeks.com has this to say about it:
“This UT-41 NMEA-0183 output USB GPS receiver is a compact all-in-one GPS solution suitable for a broad range of end product applications, where fast and easy system integration and minimal development risk is required.

This UT-41 features 12 parallel channels and 4100 time/frequency search bins provide short start-up time and fast signal acquisition. Having fast time-to-first-fix and enhanced sensitivity, the UT-41 offers good navigation performance even in urban canyons. The satellite-based augmentation systems, such as WAAS and EGNOS, are supported to yield improved accuracy.

What all this means is that if you have software that can take a GPS unit, but no GPS, then this is the answer you’ve been looking for! Because the output is a GPS standard protocol (NMEA-0183), many applications work with it out of the box!”

Note: The GPS packages will be included with Kommando-Installer in a later release.

Guardian Angel Linux
Blue Taste Theme created by Jabox