nV News Forums


nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   ALL kernels, black screen, sometimes prints ASCII (http://www.nvnews.net/vbulletin/showthread.php?t=23329)

nailchipper 01-09-04 09:03 PM

ALL kernels, black screen, sometimes prints ASCII
1 Attachment(s)
The screen used to go black, and flicker blue once, and stop responding. number lock works... i can SSH into machine to get logs.. if i try and kill X it crashes the machine hard... complete lock out...

when i run ps aux i can see X is running 99% of CPU

All the options enabled in XFConfig below have been added (when options are removed the flicker happens.. if not:) I now get a screen with ASCII printed.. just junk.. no flicker.

I have:
Athlon XP 2200
Soyo Ultra Platinum, KT333
PNY GeForce 3 Ti200
Crucial 512 DDR-333
ALL tested kernels (2.4.22+, 2.6.x)
ALL distributions (Fedora, Redhat, Debian)

I have tested with following kernel options on and off:

The Log is attached below and this is my XFConfig File:

# XFree86 4 configuration created by redhat-config-xfree86

Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "DevInputMice" "AlwaysCore"

Section "Files"

# RgbPath is 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 (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"

Section "Module"
Load "dbe"
Load "extmod"
# Load "fbdevhw"
Load "glx"
# Load "record"
Load "freetype"
Load "type1"

Section "InputDevice"

# Specify 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 non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# 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"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"

Section "InputDevice"

# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Identifier "DevInputMice"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Quantex TE1564M - Super View 1280"
HorizSync 31.5 - 82.0
VertRefresh 50.0 - 90.0
Option "dpms"

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "Videocard vendor"
BoardName "NVIDIA GeForce 3 (generic)"
Option "ReqAGPRate" "4"
Option "NvAgp" "0"
Option "ConnectedMonitor" "CRT"
Option "IgnoreDisplayDevices" "DFP, TV"
Option "IgnoreEDID"
Option "DPMS"

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 16
Modes "1280x1024"
SubSection "Display"
Depth 24
Modes "1280x1024"

#Section "DRI"
# Group 0
# Mode 0666

rednuht 01-16-04 08:04 AM

were you running xscreensaver
were you running xscreensaver or another gfx intensive process ?

Lots of ppl are having the same issue, you can try NvAgp "0"

but for me i just turn of xscreensaver.

All times are GMT -5. The time now is 08:24 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2015, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.