LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 08-26-2003, 04:15 PM   #1
hollywoodb
Member
 
Registered: Aug 2003
Location: Minnesota, U.S.A.
Distribution: Debian, openSUSE
Posts: 400

Rep: Reputation: 30
nvidia driver problem with X - blank screen


I've installed the nvidia driver, my card is a GeForce4 MX440, my monitor is a CTX VL700. I know I have the refresh rates and everything right in XF86Config, but if I try to change the driver from nv to nvidia X just gives me a black screen. If i hit ctrl-alt-backspace my screen stays black, but I know that bash is back there b/c I can issue shutdown / reboot commands.

here's my xf86config:


# **********************************************************************
# 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 Type1 and FreeType font modules
Load "type1"
Load "speedo"
# Load "freetype"
# Load "xtt"

# This loads the GLX module
# Load "glx"
# This loads the DRI module
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/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

# The module search path. 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 "Dont Zoom"

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

EndSection

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

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "Keyboard"

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

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

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

# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"

EndSection


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

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/mouse"
Option "ZAxis Mapping" "4 5"

# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"

# 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


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# 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 "CTX VL700"

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

# 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 50-130

EndSection


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

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.

# Chipset "generic"

# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# Device configured by xf86config:

Section "Device"
Identifier "nVidia GeForce4 MX440 64MB"
Driver "nv"
#VideoRam 65536
# 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 "nVidia GeForce4 MX440 64MB"
Monitor "CTX VL700"
DefaultDepth 24

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

# Section "DRI"
# Mode 0666
# EndSection

do I need to enable the DRI Mode 0666 at the end ?
 
Old 08-26-2003, 05:43 PM   #2
pilotgi
Member
 
Registered: Apr 2002
Location: ks
Distribution: openSUSE 12.2 64 bit
Posts: 488

Rep: Reputation: 32
I don't use Slackware but I'll give it a shot.

Did you install the GLX file?

At the beginning of your XF86Config file under section "modules", GLX is commented out. That will not work. The GLX module must load to use the nVidia driver.
Quote:
do I need to enable the DRI Mode 0666 at the end ?
In every XF86Config file I've seen, 0666 is enabled.

HTH.
 
Old 08-27-2003, 12:56 PM   #3
hollywoodb
Member
 
Registered: Aug 2003
Location: Minnesota, U.S.A.
Distribution: Debian, openSUSE
Posts: 400

Original Poster
Rep: Reputation: 30
alright, I'm still making no headway on this, I can't boot X at any resolution using the "nvidia" driver. "nv" works fine at any resolution. I have my refresh rates set conservatively, the specsheet for my monitor can be found here:

http://www.ctxintl.com/products/crt_vl700.htm
and my card is a Gainward MX440se 64MB w/ tv-out
if anyone's interested. no matter what I do, no matter what combinations of refresh rates, resolutions, enabling/disabling GLX and DRI, X won't load. I uninstalled and reinstalled the drivers again, no luck. my XF86Config is posted above, except now the applicable sections currently reads like this:

# This loads the GLX module
Load "glx"
# This loads the DRI module
# Load "dri"

// ----------- //

Section "Monitor"

Identifier "CTX VL700"

HorizSync 30 - 70

VertRefresh 50-70

EndSection

// ----------- //

Section "Device"
Identifier "nVidia GeForce4 MX440 64MB"
Driver "nv"
#VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection

// ----------- //

Section "Screen"
Identifier "Screen 1"
Device "nVidia GeForce4 MX440 64MB"
Monitor "CTX VL700"
DefaultDepth 24

Subsection "Display"
Depth 8
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
EndSection


can anyone help me out here? what's the problem? if I change "nv" to "nvidia" = dead screen. then I gotta use ctrl-alt-del to reboot and pico to edit my xf86config before X will load properly.
 
Old 08-27-2003, 01:41 PM   #4
hollywoodb
Member
 
Registered: Aug 2003
Location: Minnesota, U.S.A.
Distribution: Debian, openSUSE
Posts: 400

Original Poster
Rep: Reputation: 30
note: I do also have mesa installed, from reading the nvidia-opengl howto.... should I uninstall this, and if so, how? I saw a post noting that mesa is unecessary with the new drivers and slow.
 
Old 08-28-2003, 02:42 AM   #5
faheyd
Member
 
Registered: Jun 2003
Location: Northern California (NorCal)
Distribution: Ubuntu 7.04 and DSL/Puppy etc
Posts: 342

Rep: Reputation: 30
Copy your config file to a back up.
Run one of the xfconfigurator programs, such as xf86config, and start the config from scratch.
Use the old one for 'techy' answers like horiz/vert info.
Try to start X with the 'new' config.
If it doesn't work, please post the important parts of your /var/log/XFree86.0.log file, while you were using the 'nvidia' config, not the nv.
I noticed your monitor can do:
Frequency Range
Horizontal: 30-72kHz
Vertical: 50-130Hz
so why don't you try:
HorizSync 30-70
VertRefresh 50-125
and see what that does for ya (warning, crappy older crts have been known to burn up when trying to run at spec, no personal insult intended).

Last edited by faheyd; 08-28-2003 at 02:43 AM.
 
Old 08-28-2003, 03:39 PM   #6
Nevion
Member
 
Registered: Aug 2003
Distribution: Slackware 9.0
Posts: 31

Rep: Reputation: 15
If your using a framebuffer with nvidia card drivers, you WILL get problems if you have certian framebuffer support in your kernel (namely fb support for nvidia riva/gforce cards)... I did get the same problems but they seem to be gone now... I hope, I just made sure to leave the framebuffer support for nvidia as a module though I never let it get used
 
Old 08-28-2003, 07:03 PM   #7
hollywoodb
Member
 
Registered: Aug 2003
Location: Minnesota, U.S.A.
Distribution: Debian, openSUSE
Posts: 400

Original Poster
Rep: Reputation: 30
still major problems, same problem actually, I'm trying out the EvilEntity distro now, and I can't even start enlightenment b/c of this. anyways, I've tried setting it all the way down to 800x600 @ 16 instead of 24, with horiz rate down to 60 a vert all the way down to 80 (and about everything in between), still no luck... i figure it can't be my monitor, but I'll post up my xfree86.0.log up here soon, i'll try the framebuffer support as module also, hopefully that works.
 
Old 08-28-2003, 08:02 PM   #8
hollywoodb
Member
 
Registered: Aug 2003
Location: Minnesota, U.S.A.
Distribution: Debian, openSUSE
Posts: 400

Original Poster
Rep: Reputation: 30
Angry

frame buffer didn't do the trick.... thought of something though, while I wait for my kernel to recompile, do you guys think it makes any difference that my sys is a little clocked up, i.e., 2100+ @ 2.083 Ghz? I'll try clocking it down and giving it a shot here shortly, but more importantly, does anyone know exactly how gainward's expertool or the omega nv drivers (from driverhaven) work? I was running winxp up until a week ago. Before I found the omega drivers I was using expertool and had my geforce4 mx440 clocked up quite a bit also, but I'm pretty sure that these clock settings only clicked in on winxp startup, since there was a flicker/screen refresh when the utility would load. is it possible that my card is still clocked up and this is causing the problem? I personally doubt it, since that means the vidcard's bios would have had to been edited/flashed from within winxp, right?
 
Old 08-28-2003, 11:19 PM   #9
faheyd
Member
 
Registered: Jun 2003
Location: Northern California (NorCal)
Distribution: Ubuntu 7.04 and DSL/Puppy etc
Posts: 342

Rep: Reputation: 30
Did you read my post?
 
Old 09-02-2003, 03:12 AM   #10
hollywoodb
Member
 
Registered: Aug 2003
Location: Minnesota, U.S.A.
Distribution: Debian, openSUSE
Posts: 400

Original Poster
Rep: Reputation: 30
Angry

could anyone tell me how to interpret the XFree86.0.log file, here's what I'm wondering... I've tried multiple monitors now and every time all i get is scrambled garbage characters on the screen when trying to start X.

here's what I got:
(**) NVIDIA(0): Validated modes for display device CRT-0:
(**) NVIDIA(0): Default mode "1024x768": 94.5 MHz, 68.7 MHz, 85.0 MHz
and then a bunch more below it. anyways, which numbers are which? which is hsync, which is vsync, etc?

also, I get the same scrambled garbage if I set my max refresh rates to 65.0... this is getting annoying....

My monitor config, as it relates in XF86Config is:
I have tried a:
CTX VL700 (have tried 2 of these, one 2-3 yrs old, one 2-3 months old)
Dell M991 (almost new)
VPRMatrix 15" (forget model, 4 months old)

current: CTX VL700, newer version
XF86Config:

Identifier: "Monitor0"
DisplaySize 330 250
HorzSync 30.0 - 65.0
VertRefresh 50.0 - 65.0
Option "dpms"

any suggestions? I've found quite a few people have this problem but I haven't been able to find a solution yet

I'm running an AMD 2100+ @ 2 GHz
Epox 8RDA+ nForce2 chipset
1.0 GB PC2700
Gainward GF4 MX440se 64MB AGP
etc etc

note: I can't even get past the garbage @ 640*480 @ max 64 refresh on horiz and vert, using 16-bit color depth
note: at the moment I can't post my XFree86.0.log or XF86Config due to the fact that I don't have internet access yet (just moved), and the p.o.s. box I'm on now doesn't have a floppy drive, the CD drive crapped out, there's no ethernet card, and I don't have a parallel or serial cable. what a deal, what a deal

Last edited by hollywoodb; 09-02-2003 at 03:58 AM.
 
Old 09-02-2003, 04:04 AM   #11
faheyd
Member
 
Registered: Jun 2003
Location: Northern California (NorCal)
Distribution: Ubuntu 7.04 and DSL/Puppy etc
Posts: 342

Rep: Reputation: 30
How to interpret the XFree86.0.log file...

First lines in log file below
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
So, look for WW and EE 's when in the log file.


I again, noticed, that your monitor, according the specs, can do higher freq's, so use them:
... noticed your monitor can do:
Frequency Range
Horizontal: 30-72kHz
Vertical: 50-130Hz
so why don't you try:
HorizSync 30.0-70.0
VertRefresh 50.0-125.0


"this is getting annoying...'
I understand you are getting frustrated, but please try and

...Run one of the xfconfigurator programs, such as xf86config, and start the config from scratch.

It really sucks when we've hit a brick wall that can't be solved. There are alot of people here willing and able to help ya out. But let's take it one thing at a time, so we can solve your X problem. Please try and keep the variables static, and don't start changing things around the system. It's hard to hit a moving target.

"here's what I got:
(**) NVIDIA(0): Validated modes for display device CRT-0:
(**) NVIDIA(0): Default mode "1024x768": 94.5 MHz, 68.7 MHz, 85.0 MHz
and then a bunch more below it. anyways, which numbers are which? which is hsync, which is vsync, etc?"

Try and not worry about those numbers above, as X now figures out all that Mhz freq stuff for ya, ref http://www.xfree86.org/4.3.0/RELNOTES4.html#12 .
When running the X configuration program, limit your responses to 'what you know' and keep it simple, do 'tune ups' and 'hacks' later, after you have a running xfree system. Run it at a default bit depth of 16, you can change it later. System bus timings have a way of getting messed up when overclocking. Not to doubt your abilities, but did you use the instructions from 'known' good overclockings source for specs, instructions? If not, your system bus could be overclocked way out of proportion to the specs. For troubleshooting purposes, please set everything to 'factory' defaults, later on you can wig out and toast your marshmellows, and thanks for telling us about it, as sometimes, overclocking is the problem, but we don't know that yet.

after 'reconfig', if it doesn't work ,post your config file, and the WW and EE's of the X log file. Hopefully there will be something there as far as clues go.
 
Old 09-02-2003, 06:53 PM   #12
hollywoodb
Member
 
Registered: Aug 2003
Location: Minnesota, U.S.A.
Distribution: Debian, openSUSE
Posts: 400

Original Poster
Rep: Reputation: 30
XF86config & log

my complete XF86Config and XFree86.0.log can be found here:

XF86Config :
http://www.hollywoodb.netfirms.com/temp/XF86Config.txt

XFree86.0.log :
http://www.hollywoodb.netfirms.com/temp/XFree86.log

note: I disabled dpms just for kicks, and now some of the garbage characters show up in blue, not just white :P
 
Old 09-03-2003, 12:35 AM   #13
faheyd
Member
 
Registered: Jun 2003
Location: Northern California (NorCal)
Distribution: Ubuntu 7.04 and DSL/Puppy etc
Posts: 342

Rep: Reputation: 30
First off, did you do anything I asked, if so, please tell me what you've done, and what order. In the mean time,
In your XF86Config-4 file, to keep things simple as requested before, remark out fb, record, dri:

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

Enable only ONE mouse thingy until things work
Remark OUT one of them.

Section "Monitor"
# remark the display size until things work
# DisplaySize 330 250
#Remark this non-player until things work
#Keep it simple
# Option "NvAGP" "3"

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
# DefaultDepth 24 (change to 16 as requested)
DefaultDepth 16
SubSection "Display"
Depth 16
# Change modes to see what works
Modes "640x512" "640x480" "800x600" "1024x768"
EndSubSection
Remark out the
Keep DRI remarked out.
start X again and see what happens.

Also, tell me what document you are using as a FAQ/Manual to tell you how to configure your X server, as I'm not following your methods at all.
Thanks.

Last edited by faheyd; 09-03-2003 at 12:38 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] nvidia driver fails to start X (blank screen) gimblefish Linux - Hardware 2 08-30-2010 02:15 PM
nVidia driver : blank screen oonoon Ubuntu 7 12-20-2009 11:47 PM
Blank screen in konsole after nvidia driver installation J_Szucs Linux - Hardware 7 08-20-2005 12:07 PM
NVidia driver problem with screen resolution dabump Mandriva 3 12-20-2004 08:32 AM
screen goes blank after nvidia upgrade bitterjack Linux - Newbie 5 09-24-2003 07:41 AM


All times are GMT -5. The time now is 06:59 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration