STARTX problem!!! *(&@&^#@$**

charlie_mp3 · 07-14-2007, 08:19 PM

Sorry,
this is probably old news to most of you, but I have recently dared to dual boot XP and Suse 10, all well with the dual boot, until I tried to login into my freshly installed SuSe drive. I can login but there's no X window, I get the error of a "no screens found".... looking around different threads, I see people talking about the XF86Config file, which I've looked and the monitor settings are are such:

Section "Monitor"
DisplaySize 380 310
HorizSync 30-80
Identifier "Monitor[0]"
VertRefresh 43-75
UseModes "Modes[0]"

There are a couple other lines within this section, but I think these are the most relevant, so what I need to know is what here am I missing? I have also looked at dpkg-reconfigure, that doesn't exist for some reason in this machine. Unless someone knows the exact path. I have a CTX monitor and I can't find anything on the net about specific settings for it.

So any ideas would be greatly appreciated.

Charlie.

jay73 · 07-14-2007, 08:28 PM

Do this from the command line:

su -
root password
vi /etc/X11/xorg.conf

Locate the "device" section and use "vesa" as a driver instead of whatever is there. Vesa is universal and should always work. Editing in vi is done pressing i to enter edit mode, and ESC to leave it again. Saving the file is done using :wq (and quitting vi without saving anything is :q!).

You should install the proper driver as soon as you manage to get in.

charlie_mp3 · 07-14-2007, 09:18 PM

Thanks for replying, unfortunately it didn't work, I made the change in /etc/X11/xorg.conf and rebooted then tried running startx and nothing, same deal.

Am I missing a video driver or a driver for my monitor?

Thanks for your help.

J.W. · 07-14-2007, 09:21 PM

Welcome to LQ. Please post the exact monitor and video card you are using, and your /etc/X11/xorg.conf file. That's a fair amount of data but will give everyone the complete picture

perry · 07-14-2007, 09:26 PM

that's an old favorite of mine, here's the best solution i can offer, it's from jet black's simply linux workmanship:

Quote:

Installing SuSE 9

In mid 2004, SuSE Linux 9.1 Personal Edition has been available for

free.

YaST, short for Yet another Setup Tool, is the core of SuSE Linux.

Everything from installation, configuration, software and account

management to viewing logs is done in YaST.

SuSE CD boots to YaST installer that is so easy that any button pusher

could use it. The installer speaks different languages, fits different

screen resolutions, and runs on different hardware.

The entire system can be installed in one of the many languages. SuSE

worked their rears off on hardware detection and configuration. And it

shows. Every major part of my nForce-2 PC with GeForce3 3D accelerator

and HP PhotoSmart USB printer was detected and configured. The only

exception was my Samsung 17" monitor, which was a breeze to set up in

YaST.

After install and reboot, YaST guided me through the post-install config

including setting root password, adding a user account, and configuring

some hardware. There was no reboot next. I could start exploring the

freebie right away in KDE style.

At first log-in, SuSE Greeter provides pointers to some programs and

information. SuSE desktop is all green and plain. SuSE Plugger detects

and configures USB Plug-and-Play devices. SuSE Watcher notifies you of

any new software updates. Accessing optical and floppy disks in SuSE is

as easy as it is in Windows. On the desktop is SuSE Greeter, Support,

OpenOffice, SuSE Linux User Guide, My Computer, Trash can, Printer and

Network Browsing. KDE menu lists only common applications in Games,

Graphics, Internet, Multimedia, Office, System and Utilities sub menus.

SuSE defaults to KDE applications such as Konqueror for Web browsing.

You can install software from CD, DVD, hard disk or Internet. There is

no registration to get new software and updates. Updating the system and

managing software are just point-and-click.

At this price, free, SuSE can't get any better. YaST works flawlessly.

The gecko is clearly leaping its way to the top spot as the most popular

and user-friendly distro.

On the CD are Acrobat Reader 5.08, Advanced Linux Sound Architecture

1.0.3, Common UNIX Printing System 1.1.20, dvd+rw-tools 5.17.4.8.6,

Flash Player 6.0.81, GNU Binary Utilities 2.15.90.0.1.1, GNU C Library

2.3.3, GNU Core Utilities 5.2.1, GNU Image Manipulation Program 2.0.0,

Graphical User Interface ToolKit 1.2.10 and 2.2.4, Iomega ZIP and JAZ

Tools 1.4.0, iptables 1.2.9, Java 2 Runtime Environment 1.4.2, K3b CD/

DVD recording tool 0.11.7, KDE 3.2.1, kernel 2.6.4, Mozilla Firefox 0.8,

Ocrad Optical Character Recognition 0.7, OpenLDAP 2.2.6, OpenOffice

1.1.1, OpenSLP 1.1.5, OpenSSH 3.8p1, OpenSSL 0.9.7d, Perl 5.8.3, PPP

2.4.2, Qt 3.3.1, RealPlayer 8.0.3.465, RPM Package Manager 4.1.1, Samba

file and print sharing 3.0.2a, Scanner Access Now Easy 1.0.13, SuSE

Firewall 2 3.1, Tcl/Tk 8.4.6, XFree86 4.3.99.902, Xine 0.99.rc3a, XMMS

1.2.10, YaST2 Control Center 2.9.11...

Getting SuSE

Download SUSE-9.1-personal-x86.iso and MD5SUMS files from ftp://

ftp.rz.uni-ulm.de/pub/mirrors/suse/i386/9.1-personal-iso/ or any mirror

in the same subdirectory. Verify the download in Linux:

md5sum -c MD5SUMS

If it returns ok or nothing on the ISO, burn the ISO on a 700 MB CDR/

W disk. If it returns "fail", download the ISO image and MD5 checksum

files from another mirror.

Starting SuSE

Insert the CD in the first optical drive, usually the one in the top.

Reboot the computer. At the SuSE boot screen, press F2 key, select a

screen resolution using up/down direction keys, press Enter key,

highlight "Installation", and press Enter key to start the installer. If

the CD doesn't boot, see your computer's manual on how to set it up to

boot from CD/DVD drive first.

Alternatively, you can press F3 key to select install media such as CD-

ROM, F4 key to select installer language such as English, F5 key to

select silent boot splash or verbose boot messages, or F6 key to load

drivers such as RAID from a floppy disk.

Selecting Language

Select a language to be installed as the primary language for SuSE,

[Accept].

Changing Install Settings

Verify that the hardware is correctly detected. If it isn't, click

[Change...] to change any setting, and follow on-screen instructions.

Partitioning Hard Drive

SuSE needs a pair of Linux and swap partitions to install. You can skip

this part if you have made them previously, and you are installing SuSE

over the old system. Before skipping this part, double-check that the

target Linux and swap partitions are the ones to be formatted.

Click [Change...] > Partitions... > choose "Base partition setup on this

proposal" to use the current partition layout if you have partitioned

the hard drive previously.

If SuSE is using an existing Linux partition as the install location and

you want to keep it, highlight the Linux partition, [Edit], click "Do

not format", set "Mount Point" to nothing, [OK]. Your existing Linux

distro on that partition will continue to exist.

Highlight a 5 GB or larger partition for SuSE, [Edit], click "Format",

set "File system:" to Ext3 to choose Third Extended Filesystem as the

filesystem for SuSE, set "Mount Point" to / or root directory, [OK].

If SuSE isn't any partition as swap, highlight a 512 MB or smaller

partition for swap, [Edit], click "Format", set "File system:" to swap,

[OK].

If you wish to access a Windows partition in SuSE, highlight the Windows

partition, [Edit], [Fstab Options] to set Filesystem Table options,

check "Mountable by user" and "Do Not Mount at System Start-up", [OK],

set "Arbitrary option value" to "users,gid=users,umask=0007", [OK], set

"Mount Point" to "/mydoc" or something meaningful, [OK].

Make sure an F for format is in the Linux and swap partition rows,

[Next].

Configuring Boot Loader

SuSE will installs GRand Unified Bootloader on the master boot record

unless the user configures it to install elsewhere. You can skip this

part if SuSE is the only operating system on the computer.

Click [Change...] > Booting... > highlight "Boot Loader Location",

[Edit], click "Boot Sector of Boot Partition", [OK], [Finish].

Selecting Time Zone

Click [Change...] > Time Zone... > set "Hardware clock set to:" to

"local time", select a region in the left panel, and time zone in the

right panel, if nothing matches the local time, select Etc and GMT-/+ a

number until the displayed time on screen matches your local time,

[Next].

Installing SuSE

Click [Accept], [Yes, install] to install SuSE. Install takes around 15

minutes on a modern computer. When install is over, click [OK] to reboot

the system. When computer restarts, remove the CD from the optical

drive. Boot SuSE.

Entering root Password

The root account is used for system administration.

Type a root password in each of the password text boxes in the right

panel, [Next].

Configuring Network

If there is an Internet connection, set up your network device.

Click [Next], any network device should be detected and configured,

click "No, Skip This Text", [Next].

Adding User Accounts

A user account is used for daily operation. Add as many user accounts as

you wish.

Click "Stand-Alone Machine" if the computer isn't locally networked,

[Next], type a full name in "Full User Name" text box, type a one-word

user name in "User Login" text box, type a user password in Password

text box, type the same password again in "Verify Password" text box,

check "Auto Login" if you want to log into this user automatically at

boot, [Next], [Yes].

Reading Release Notes

There is last-minute information about SuSE Linux 9.1 in the release

notes. After reading them, click [Next].

Configuring Visual Devices

This part is where you configure the graphical card and monitor.

Click [Change...] > Graphics Cards... > Monitor > [Properties...] >

highlight a monitor brand and model, [OK], [Finish].

Click-open Desktop in the left panel > Graphics Card > [Change

configuration] > Graphics Card > [Properties...] > Color and Resolution

> [Change configuration] > [Properties...] > select "16.7 Mio. [24 bit]"

from "Color Selection" drop-down menu if it's supported, [OK], [Finish].

Configuring Input Devices

This part is where you configure the mouse.

Click-open "Input-Devices" in the left panel > Mouse > [Change

configuration] > [Properties...] > highlight a mouse model in the left

panel and protocol in the right panel (i.e. PS/2 mouse and IMPS/2),

[OK], [Finish], [Finalize>>], [Test], [Save], [OK].

Configuring Output Devices

This part is where you configure the printer.

[Change configuration] > Printers... > [Configure...] > click the

printer type [Next], highlight the printer device, [Next], type a name,

description and location for the printer, [Next], highlight the printer

manufacturer in the left panel, and model in the right panel, [Next],

[Test] if you wish to print a print-out, [OK], [Finish].

Ending Install

Click [Next], [Finish].

Congrats! You've installed SuSE Linux 9.1 Personal Edition on the

computer. You should waste no time and start exploring the free

operating system right away without rebooting.

Check out Configuring SuSE 9.

International Download Mirrors

http://www.suse.com/us/private/downl...t_mirrors.html

just in case you feel like reinstalling it again

- perry

perry · 07-14-2007, 09:28 PM

just in case your a little confused with configuring suse linux

Quote:

CHAPTER 3

------------------------------------------------------------------------------

Configuring SuSE 9

In this section, you will run SuSE Greeter, read SuSE User Guide, run

YaST Control Center, get online updates, change install sources, install

and remove software, remove necessary services, enable firewall, tighten

security settings, and view system logs.

Welcome to SuSE Linux 9

The first time a user logs in KDE desktop, SuSE Greeter pops up. In the

window is a number of links to SUSE Homepage, SUSE Portal, free

Installation support, unique SUSE Hardware Database and Release Notes.

To run the greeter again, click SuSE shortcut on the desktop.

Reading SuSE User Guide

Click User Guide on desktop. The guide covers release notes, system

installation, system repair, system configuration, Yet another Setup

Tool, KDE and GNOME desktops, common multimedia, office and CD/DVD

recording applications, ergonomics, system utilities, KDE user's manual,

system administration and software development tools. Even though some

of them were written by the software developers, SuSE took the time to

put their user guide and others together. SuSE User Guide can get the

new user started in SuSE Linux.

Running YaST Control Center

YaST Control Center manages hardware, software, accounts, services and

security. The installer detects and configures most hardware. The system

administrator or computer owner can configure hardware that is new or

wasn't properly detected and configured during install. YaST Online

Update updates the system. SuSE Package Manager installs, updates and

removes software. The install source can be hard drives, CD media and

Internet.

Click main menu > System > YaST > enter root password. The left panel is

the top categories: software, hardware, system, network devices, network

services, security and users, and misc. The right panel is sub

categories. Moving the mouse cursor over a sub category displays a short

description of it. Everything is a single click away.

Getting Online Updates

After installing and rebooting to SuSE, the first thing to do would be

to update the system with security, recommended and application patches.

Run YaST if not already > click Software on the left > Online Update on

the right > in YaST Online Update (YOU), select "Germany: University

Ulm" from the installation source drop-down menu, check "Manually Select

Patches", uncheck "Reload All Patches from Server", [Next].

In the top-left list, leave the security and recommended updates checked

if the Internet connection is broadband, or check only small security

updates that total around 5-10 MB if it is dial-up, take a look at the

"Total Download Size" in the lower-right corner of the left Patch

Description panel, [Accept] > [Install Patch], wait until every patch is

downloaded and installed, [Skip Patch] if there is an error downloading

the patch, [Finish] or [Close], YaST then updates the system

configurations.

In YOU, there is about a dozen download sites to choose from. "Germany:

University Ulm" worked for me every time. If none of them works, you can

always get one from International Mirrors link below. i.e. ftp://

ftp.solnet.ch/mirror/SuSE/ can be used as the update source. It is best

to use a complete mirror that include all distributions and updates.

YaST takes a few minutes to retrieve information about the updates the

first time. The second time it takes a few seconds. The time for

downloading and installing patches depends on the computer and Internet

connection. Avoid peak hours and running any other programs.

Changing Install Sources

By default, the CD media that was used to install SuSE is the install

source for software management. SuSE Package Manager lets you change the

install source. Be it CD, hard disk or Internet.

Run YaST if not already > click Software on the left > click "Change

Source of Installation" on the right > click and hold [Add] > move mouse

cursor to FTP and release mouse button > under Protocol, click FTP (File

Transfer Protocol), under Server Name, copy and paste a ftp mirror such

as "ftp.solnet.ch" minus quotes, under Directory on Server, copy and

paste "mirror/SuSE/i386/9.1" minus quotes, check "Anonymous", [OK].

The source should be added to the Software Source Media list. Make sure

that the status is on. [Enable or Disable] toggles between on and off. I

would suggest you turn on only ONE source at a time. Otherwise, there

may be duplicate selections when installing software. If there was a

problem adding a source, highlight the problem source, click [Edit] >

Replace... > and make corrections, [OK]. Finally, click [Finish].

Installing and Removing Software

YaST Package Manager reads the package information from all install

sources, and then lets the user install and remove available software

and documentation. Both install and remove are done in the same program.

To install a package, check the status checkbox next to a package in the

package list. To remove a package, click the status checkbox next to the

to-be-removed package in the package list until it looks like a garbage

can.

Run YaST if not already > click Software on the left > click "Install

and Remove Software" on the right > wait until YaST finishes reading the

package information, select "Package Groups" from the Filter drop-down

in the top-left corner, click open a package group that contains to-be-

installed software in the Package Groups list on the left (i.e.

Productivity > Networking > Web > Browsers), check the status checkbox

next to a package to install (i.e. MozillaFirefox), or uncheck a package

to remove in the Package list on the right, [Check Dependencies], [OK]

to dismiss "All package dependencies are ok" dialog, [Accept] to install

software.

The newly installed application software will appear in KDE menu. Others

such as libraries will not. Firefox will be in main menu > Internet >

Web Browser. On the contrary, the recently removed application software

will disappear from KDE menu.

Removing Unnecessary Services

Services are init scripts that start and stop in the correct run levels.

There is a few unnecessary services that the average home Internet

desktop computer doesn't need. They can pose a security risk. Why didn't

you tell me to remove the services earlier, you ask? Because Online

Update reverts some changes to defaults.

Run YaST if not already > click System on the left > click "Runlevel

Editor" on the right > click "Simple Mode", highlight a service in the

Service list, [Disable], [OK], [Finish], [Yes] to save changes.

The services to remove are isdn (Integrated Services Digital Network),

nfsboot (Network Filesystems), nscd (Name Service Cache Daemon), portmap

(RPC port mapper), postfix (e-mail server), powersaved (Power Saving

Daemon for laptops), smbfs (Samba file and print sharing) and sshd

(Secure Shell Daemon).

Enabling Firewall

A firewall protects the computer from cyber intruders, in theory. As

soon as you're done enabling the firewall, it will be up and running.

Run YaST if not already > click Security and Users on the left > click

Firewall on the right > click "Reconfigure Firewall Settings", [Next] >

select an external interface to protect (i.e. eth0 for broadband

connections), leave Internet interface empty, [Next] > uncheck every

server and service, [Next] > check only "Protect from Internal Network",

"Protect All Running Services" and "Allow Traceroute" firewall features,

[Next] > check only "Log Critical Dropped Packets" and "Log Critical

Accepted Packets" standard logging options, [Next], [Continue].

Tightening Security Settings

The default security settings don't let the user reboot and shut down

the computer, yet they let the user view any system logs. It should be

the other way around since the distro is a personal edition.

Run YaST if not already > click Security and Users on the left > click

"Security Settings" on the right > click "Custom Settings", [Next] >

[Next] > change "Shutdown Behavior of KDM:" to "Local users", [Next] >

uncheck "Allow Remote Graphical Login" if it is checked, [Next] > [Next]

> change "Setting of File Permissions:" to "Secure", and "User Launching

updatedb" to "root", uncheck all checkboxes, [Finish].

Viewing System Logs

Software logging can be post deployment debugging in the software

development cycle. The logs help software developers analyze and assess

any problems running their software without on-site physical presence.

For a system administrator or computer owner, the logs can tell you what

is going on in the system, and help online forum goers troubleshoot any

problem.

Run YaST if not already > click Misc on the left > click "View System

Log" on the right > select any available log from the top drop-down, the

end of the log is displayed in the center panel, after viewing logs,

[OK].

Online Help

http://www.suse.com/us/private/suppo...elp/index.html

SuSE Linux Documentation

http://elibrary.fultus.com/technical...m.fultus.suse/

index.html

International Mirrors

http://www.suse.de/en/private/downlo...t_mirrors.html

German Mirrors

http://www.suse.de/de/private/download/ftp/inland.html

Kernel Vulnerabilities

http://www.linuxsecurity.com/advisor...sory-4728.html

http://www.linuxsecurity.com/advisor...sory-4535.html

http://www.linuxsecurity.com/advisor...sory-4630.html

----------------------------------------------------------------------------

Copyright (C) 2002-2004 by jet_blackz@lycos.com

chadl · 07-14-2007, 09:31 PM

I have found that the /var/log/Xorg.0.log file is very helpful when attempting to figure out why Xorg decided not to start. As the text at the top of the log explains, lines starting with (EE) represent an error, so they are the lines that you will need to look out for.

This might help to filter the errors out from the noise:

Code:

grep '(EE)' /var/log/Xorg.0.log

You might want to keep an eye out for warnings (WW) too, but they generally are not the cause of the X server failing to start.

perry · 07-14-2007, 09:34 PM

Here's something from the Slackware 10 install:

Quote:

Enabling Graphical Login

Slackware boots to command line interface. You can boot to the default

GNOME Desktop or Login Manager. Change the run level to 4 in inittab:

vi /etc/inittab

id:4:initdefault:

Configuring X Window

Before starting X Window, configure X:

xorgconfig

Follow the on-screen instructions. Start the X Window System:

startx

Configuring Acceleration, Mouse, Screen and Video RAM

The mouse speed is slow, any mouse wheel is disabled, screen is off

center, monitor power saving mode is off, and video RAM isn't set. My

mouse is a Microsoft Wheel Mouse Optical on PS/2.

Open a terminal or console, run video mode tuner, center the screen,

[Apply], [Show], [Quit], highlight to copy your mode line, uncomment

OpenGL for X (glx) for primarily nVidia video or Direct Rendering

Infrastructure (dri) for primarily ATI video in Module section,

uncomment Resolution option and add the ZAxisMapping option in

InputDevice section, paste your ModeLine with middle mouse button, add

DPMS option in Monitor section, and uncomment VideoRam option in Device

section, of xorg.conf:

xvidtune

vi /etc/X11/xorg.conf

Section "Module"

Load "dbe"

SubSection "extmod"

Option "omit xfree86-dga"

EndSubSection

Load "type1"

Load "speedo"

Load "freetype"

Load "glx"

# Load "dri"

EndSection

...

Section "InputDevice"

Identifier "Mouse1"

Driver "mouse"

Option "Protocol" "IMPS/2"

Option "Device" "/dev/mouse"

Option "Resolution" "256"

Option "ZAxisMapping" "4 5"

EndSection

...

Section "Monitor"

Identifier "My Monitor"

HorizSync 30-70

VertRefresh 50-160

ModeLine "1024x768" 94.50 1024 1088 1184 1376 768 769 772

808 +hsync +vsync

Option "DPMS" "true"

EndSection

...

Section "Device"

Identifier "NVIDIA GeForce"

Driver "nv"

VideoRam 65536

EndSection

You should try configuring your card to work with Vesa first, just to get some sort of graphical login from there you should be able to make incremental changes to your xorg.conf file but each time you do, be sure to cp your last working xorg.conf to a xorg.conf.bak or xorg.conf.n where n is a number. This gives you a backup should your latest modification go bad. Also, change your inittab mode to a 3 so that your boot ups will take you to a prompt rather than attempt the gui till you get startx working properly.

ex.
vi /etc/inittab
id:3:initdefault:

hope this helps

- perry

perry · 07-14-2007, 09:36 PM

Just in case your suse doesn't come with a default vesa configuration here's one from mine:

Quote:

# 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 <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" "pc101"
# 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 31.5 - 50.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 40-90

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

# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
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

charlie_mp3 · 07-14-2007, 10:08 PM

Well, thanks perry and everyone that's posted a response, I'm going to sort through this information tonight, and I'll update the thread either way.

Thanks so much for responding so quickly, I'm liking this Linux community.

Charlie.