VectorLinux

The nuts and bolts => Hardware & Drivers => Topic started by: AndyA on May 03, 2009, 12:09:28 pm

Title: Failed To Start Xserver - No GUI on new install
Post by: AndyA on May 03, 2009, 12:09:28 pm
Hi all,
I've just installed Vector Linux 6 Standard on an old Toshiba Satellite 4080XCDT, I'm new to Linux and thought I'd play safe using an old PC. It was running through the display configuration and I chose the AUTO (less questions) method, VL decided to use 640 x 480 instead of the normal 1024 x 768 that this laptop would use. The GUI failed and I'm now left with a text display, I haven't a clue how to use the text method to try and correct the issue, can anyone help ?

Thanks ???
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: AndyA on May 03, 2009, 12:51:52 pm
I've posted this in the wrong section haven't I.  :-\
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: stretchedthin on May 03, 2009, 01:15:59 pm
Hi Andy;

The situation you are in is not very hard to get out of in VL.

Since you are in a text display, login in (if you are not already)
Then login as root.
type
su (press enter)
then enter your root password (press enter)

type
vxconf

Then it should look familiar.
You can get to here from the text display any time this way so feel free to experiment.

I'd first try the vxconf option if you have ati or nvidia drivers.  Don't choose anything smaller than 800*600 res.

If you don't have ati or nvidia just choose vesa.

Let me know how it goes.
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: AndyA on May 03, 2009, 01:26:01 pm
Hi stretchedthin,
I've jumped the gun and started a re-install thinking that I'd have another go at it. I'm not sure what graphics adapter this laptop uses as I've just been given it and haven't investigated the hardware. I'm 'fairly' sure that it won't be either ATI on Nvidia ?

I'll choose a different video selection and will report back asap, the install takes a long time though.
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: AndyA on May 03, 2009, 02:22:16 pm
Oh crumbs, vesa doesn't seem to have been a good choice either, I see 2 small desktops (pink) sise by side at the bottom half of the screen, text is way too small to read. Nuts!
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: stretchedthin on May 03, 2009, 03:07:24 pm
Can you get into a text screen.  Try pressing 'ctrl+alt+f5'.  Do your get a text screen you can work with.  If so you can try the different options of vxconf.

You can also try a command called xorgconfig, but you will have to do some research on your system first.

If someone else is watching this thread and can give a hand that would be appreciated, this is not a strong area for me.
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: AndyA on May 03, 2009, 03:48:24 pm
Thank you again, I'm just about finished with the 3rd installation so will look at another video option. It's getting late and I'm getting a bit disheartened  so will no doubt follow it up tomorrow.

Title: Re: Failed To Start Xserver - No GUI on new install
Post by: AndyA on May 04, 2009, 04:15:24 am
Great it's up and running, had a bit of fuss with the wifi but nothing too troubling. The graphics seem very slow, i.e dragging windows is a bit of a struggle, I think the graphic card has around 2 mb of memory so can't expect much.

Lots to investigate....
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: rbistolfi on May 04, 2009, 06:54:18 am
Maybe trying different drivers or even different options for the same driver. Lowering the resolution and depth color can help. As root, lspci|grep VGA can give you good keywords for researching. You may want to post the output of that command here, maybe some users have the same card and can help you.

Good luck, and keep us informed.
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: AndyA on May 04, 2009, 07:55:17 am
Thanks rbistolfi, the result is:

00:04.0   VGA compatible controller: Trident Microsystems Cyber 9525 (rev 49)

It took me a while to find the | key on the laptop, haven't got it to UK settings it would appear.

Title: Re: Failed To Start Xserver - No GUI on new install
Post by: lagagnon on May 04, 2009, 08:36:46 am
On boot choose "linux-tui", login as root, enter roots password, edit the file /etc/X11/xorg.conf and do the following:

change line: Driver "???" to Driver "trident"
change line: DefaultDepth 24 to DefaultDepth 16

save the file.
Type "startx" and tell us what happens.
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: AndyA on May 04, 2009, 08:50:33 am
I didn't install the tui startup so just have gui, is there something I can do as an alternative to edit the xorg.conf file ?

Thanks lagagnon
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: lagagnon on May 04, 2009, 09:23:32 am
When the X server fails are you not bumped into console mode? You should then be able to login as root in console mode. Either that or try pressing Ctrl-Alt-BkSpace to leave faulty X mode. If that fails try Ctrl-Alt-F1 or Ctrl-Alt-F2 to get a virtual terminal console.

Then use either the nano or vi editor or use mc, find the file and press F4 to edit it.
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: AndyA on May 28, 2009, 07:53:15 am
I'm still messing around with this. I've deleted my xorg.cong thinking that I could generate a fresh one to try ...... I don't know how to, can anyone advise ?

Thanks.
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: rbistolfi on May 28, 2009, 08:01:11 am
run as root vxconf
Title: Re: Failed To Start Xserver - No GUI on new install
Post by: AndyA on May 28, 2009, 08:48:34 am
Thanks very much, now am back to square one with a gui.  ;D

I've found a copy of someone else's (Ubuntu?) XF86Config-4 using the same video card as mine. I've used the monitor refresh rates in my xorg.conf but still have a slow gui, just need to figure out how to use the other setting in my xorg.conf. I have the display set at 'Default' which appears to be 1024 x 768.

Code: [Select]
# XF86Config-4 (XFree86 server configuration file) generated by Dexconf, the
# Debian X Configuration tool, using values from the debconf database.
#
# Edit this file with caution, and see the XF86Config manual page.
# (Type "man XF86Config" at the shell prompt.)

Section "Files"
FontPath "unix/:7110" # local font server
# if the local font server has problems, we can fall back on these
FontPath "/usr/lib/X11/fonts/misc"
FontPath "/usr/lib/X11/fonts/cyrillic"
FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/Type1"
FontPath "/usr/lib/X11/fonts/Speedo"
FontPath "/usr/lib/X11/fonts/100dpi"
FontPath "/usr/lib/X11/fonts/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "ServerFlags"
EndSection

Section "Module"
Load "ddc"
Load "GLcore"
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "pex5"
Load "record"
Load "xie"
Load "bitmap"
Load "freetype"
Load "speedo"
Load "type1"
Load "vbe"
Load "int10"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/psaux"
Option "Protocol" "PS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Generic Mouse"
Driver "mouse"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "Generic Video Card"
Driver "trident"
Option "UseFBDev" "false"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
HorizSync 28-40
VertRefresh 43-75
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Generic Video Card"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "800x600" "640x480" "300x200"
EndSubSection
SubSection "Display"
Depth 15
Modes "800x600"
EndSubSection
SubSection "Display"
Depth 16
Modes "800x600"
EndSubSection
SubSection "Display"
Depth 24
Modes "800x600"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Generic Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection

# end of XF86Config




This is the xorg.conf that I'm using on the laptop, can anyone possibly help me to merge the details so I can improve my desktop performance?

Code: [Select]
# 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.
# **********************************************************************

# This XF86Config file is designed for use with the Linux framebuffer console.
# This generic interface should work with nearly all video cards (although
# not every card will support every resolution).  To use the Linux framebuffer
# console, you need to enable these kernel options:
# Using 'make menuconfig', in 'console drivers', enable:
#   [*] VGA text console
#   [*] Video mode selection support
#   [*] Support for frame buffer devices (EXPERIMENTAL)
#   [*] VESA VGA graphics console
#   [*] Advanced low level driver options
#   <*> 8 bpp packed pixels support
#   <*> 16 bpp packed pixels support
#   <*> 24 bpp packed pixels support
#   <*> 32 bpp packed pixels support
#   <*> VGA characters/attributes support
#   [*] Select compiled-in fonts
#   [*]   VGA 8x8 font
#   [*]   VGA 8x16 font
# If you have a Matrox or ATI Mach64, you might try enabling the options having
# to do with those cards as well.  However, if the card is VESA compliant, you
# don't really need to (and it might cause problems, possibly)
#
# Next, if this file is not already named /etc/X11/XF86Config, make a copy
# with that name.  This file ships with the name XF86Config-fbdev to avoid
# overwriting an existing config file.
#
# To get the kernel to start in VESA framebuffer mode, you need to pass it
# a vga= init string at boot time.  For example, if you use LILO you'll
# probably find a vga=normal string in your /etc/lilo.conf.  If you edit that
# to one of the values in this table:
#
#   Colours   640x480 800x600 1024x768 1280x1024 1600x1200
#  --------+---------------------------------------------
#  256     |   769     771      773      775       796
#  32,768  |   784     787      790      793       797
#  65,536  |   785     788      791      794       798
#  16.8M   |   786     789      792      795       799
#
#  ...such as this for 1024x768x64k:
#  vga = 791
#  and then reinstall LILO by running 'lilo' as root, then at the next boot
#  Linux should start in a VESA framebuffer console mode.
#
# For more information on how to activate the Linux frame buffer, see
# /usr/src/linux/Documentation/fb/vesafb.txt.
#
# 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/share/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/share/fonts/local/"
    FontPath   "/usr/share/fonts/misc/"
    FontPath   "/usr/share/fonts/Type1/"
    FontPath   "/usr/share/fonts/OTF/"
    FontPath   "/usr/share/fonts/TTF/"
    FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/Speedo/"
    FontPath   "/usr/share/fonts/75dpi/:unscaled"
    FontPath   "/usr/share/fonts/100dpi/:unscaled"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/fonts/100dpi/"
    FontPath   "/usr/share/fonts/cyrillic/"

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

#    ModulePath "/usr/lib/xorg/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 <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option     "DontVTSwitch"

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

#    Option     "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> 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"      "pc105"
#    Option     "XkbLayout"     "us"
#    Option     "XkbVariant"    ""
#    Option     "XkbOptions"    ""

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier "Mouse1"
    Driver "mouse"

# 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"    "PS/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   28-40

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

EndSection


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

# Any number of graphics device sections may be present

Section "Device"
    Identifier  "VESA Framebuffer"
    Driver      "fbdev"
    #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"

# You shouldn't need to set a default depth as the server will use
# whatever the framebuffer is set to.  If you insist on setting it, make
# sure it matches the setting for your framebuffer.
#   DefaultDepth 8

    Subsection "Display"
        Depth       8
    EndSubsection
    Subsection "Display"
        Depth       16
    EndSubsection
    Subsection "Display"
        Depth       24
    EndSubsection
    Subsection "Display"
        Depth       32
    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
# right of screen 1.

    Screen "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

Title: Re: Failed To Start Xserver - No GUI on new install
Post by: AndyA on May 28, 2009, 08:58:26 am
Deleted, added to post above