LinuxQuestions.org - X-windows doesn't work anymore, strange error Nvidia driver

hi,

I configured the X-windows on installation and ran the script for the Nvidia drivers after that. Xwindows started rather straightforward, no problem. However, only recently I get the following error. I haven't yet configured anything else kernel or modulewise.

Code:

#

Module Loader present

Markers: (--) probed, (**) from config file, (==) default setting,

        (++) from command line, (!!) notice, (II) informational,

        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 11 19:23:30 2009

(==) Using config file: "/etc/X11/xorg.conf"

(II) Module "ramdac" already built-in

(EE) NVIDIA(GPU-0): Your GeForce 7600 GS graphics card does not have the necessary

(EE) NVIDIA(GPU-0):    external power cables attached; X will not start unless

(EE) NVIDIA(GPU-0):    this is rectified.  Please shut down your computer, open

(EE) NVIDIA(GPU-0):    its case, and attach the appropriate power connectors.

(EE) NVIDIA(GPU-0):    Your video card may have multiple power connectors.  If

(EE) NVIDIA(GPU-0):    so, each must be attached to a separate power cable.

(EE) NVIDIA(GPU-0):    Please see the documentation provided with your video card

(EE) NVIDIA(GPU-0):    for more details.  If you think you have received this

(EE) NVIDIA(GPU-0):    message in error, you may specify the

(EE) NVIDIA(GPU-0):    "NoPowerConnectorCheck" X configuration option in the

(EE) NVIDIA(GPU-0):    Screen section of your X config file.

(EE) Screen(s) found, but none have a usable configuration.



Fatal server error:

no screens found



waiting for X server to begin accepting connections

giving up.

xinit:  Connection reset by peer (errno 104):  unable to connect to X server

xinit:  No such process (errno 3):  Server error.

I don't see any error in the xorg.conf file (below), and don't understand the message of lack of power for my videocard. The cable is properly connected. No problems under Windows, and shortly not under Linux too. No usable configuration for video screens?
I have no clue what causes this behaviour?

Code:

# # nvidia-xconfig: X configuration file generated by nvidia-xconfig

# nvidia-xconfig:  version 1.0  (buildmeister@builder63)  Tue Jan  6 10:03:02 PST 2009



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

# **********************************************************************

#

# **********************************************************************

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

# **********************************************************************

# **********************************************************************

# Server flags section.

# **********************************************************************

# **********************************************************************

# Input devices

# **********************************************************************

# **********************************************************************

# Core keyboard's InputDevice section

# **********************************************************************

# **********************************************************************

# Core Pointer's InputDevice section

# **********************************************************************

# 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

# **********************************************************************

# Graphics device section

# **********************************************************************

# Any number of graphics device sections may be present

# **********************************************************************

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

# **********************************************************************

# 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

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

# 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".

    Identifier    "Simple Layout"

    Screen        "Screen 1" 0 0

    InputDevice    "Mouse0" "CorePointer"

    InputDevice    "Keyboard1" "CoreKeyboard"

EndSection



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.

# 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).

# 

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

    RgbPath        "/usr/share/X11/rgb"

    FontPath        "/usr/share/fonts/local/"

    FontPath        "/usr/share/fonts/misc/"

    FontPath        "/usr/share/fonts/OTF/"

    FontPath        "/usr/share/fonts/TTF/"

    FontPath        "/usr/share/fonts/Type1/"

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

EndSection



Section "Module"



# This loads the DBE extension module.

# This loads the miscellaneous extensions module, and disables

# initialisation of the XFree86-DGA extension within that module.

# This loads the font modules

# This loads the GLX module

    Load          "dbe"          # Double buffer extension

    SubSection    "extmod"

        Option        "omit xfree86-dga"  # don't initialise the DGA extension

    EndSubSection

    Load          "type1"

    Load          "freetype"

    #Load        "speedo"

    Load          "glx"

EndSection



Section "InputDevice"



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

    Identifier    "Keyboard1"

    Driver        "kbd"

EndSection



Section "InputDevice"



# Identifier and driver



    Identifier  "Mouse0"

    Driver      "mouse"

    Option      "Protocol" "IMPS/2"

    Option      "Device"  "/dev/mouse"

    Option      "Buttons" "5"

    Option      "ZAxisMapping" "4 5"



# The mouse device.  The device is normally set to /dev/mouse,

# which is usually a symbolic link to the real device.



#  Option "Device"      "/dev/psaux"

#  Option "Device"      "/dev/ttyS0"

#  Option "Device"      "/dev/ttyS1"



EndSection



Section "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        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.

    Identifier    "NEC VR17"

    HorizSync      30.0 - 70.0

    VertRefresh    50.0 - 150.0

EndSection



Section "Device"



    #VideoRam    4096

    # Insert Clocks lines here if appropriate

    Identifier    "VESA Framebuffer"

    Driver        "nvidia"

EndSection



Section "Screen"



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

# is highly recommended.

#  DefaultDepth 8

#  DefaultDepth 16

#  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)

    Identifier    "Screen 1"

    Device        "VESA Framebuffer"

    Monitor        "NEC VR17"

    DefaultDepth    24

    SubSection    "Display"

        Depth      8

        Modes      "1024x768" "800x600" "640x480"

    EndSubSection

    SubSection    "Display"

        Depth      16

        Modes      "1024x768" "800x600" "640x480"

    EndSubSection

    SubSection    "Display"

        Depth      24

        Modes      "1024x768"

    EndSubSection

    SubSection    "Display"

        Depth      32

        Modes      "1024x768" "800x600" "640x480"

    EndSubSection

EndSection