That bit from xf86config file is wrong.

Driver "nv"

MUST be changed to:

Driver "nvidia"

When you say; "I ran xf86config -4" I'm guessing you ran the MDK GUI thing for X?

If so stop it. Its breaking everything your working so hard to fix. Get comfy with the command line and manually editing these files.

Make that change to your xf86config file MANUALY (must be root) and lets try to go with that. It will be called XF86Config (if memory serves) or xorg.conf. the path is:

/etc/X11

You can either edit this file while X is running or not. (MUST be root) If the above example of your X config is what your running on it will NOT work ever. You MUST edit the X config file manually. Save it and then restart X or reboot.

rivafb is a frame buffer device and is a kernel module if I'm not mistaken. you should be able to run:

locate rivafb

OR


find rivafb

That frame buffer may be what's keeping you going right now. That's why I say make the edit to the xf86config file and try that first.

If possible paste the content of your X configuration file.

While doing this its impossible to keep flipping back and forth from X to CLI. You need to know some tools and get comfy with the Command Line Interface. While working with X it is very possible to loose X functionality.

A good, easy command line text editor for new Linux users is joe. MDK ships with it on disk or at least used to but does not install it by default. Some others around here will smirk for my selection of text editors but oh well.

After joe is installed and you are at the Command Line you open text files like so:

joe /etc/X11/xorg.conf

that opens my X configuration file. Do you always have to use the entire path? No. but that's another topic.

to navigate the document use arrow keys.

to save changes and exit use the key combo:

CTRL+K+X

to quit without saving changes:

CTRL+C

to get help within joe;

CTRL+K+H

Other wise it operates like any simple text editor.

Just wanted to give you a tool tip in case flopping back and forth is driving you batty.

Its possible if not prudent to do all of this work via Command Line.

Also in Command Line if want to have multiple files open on different "screens" use the following key combo:

ALT+F2

F1 - F12 are valid so you could have 12 consoles running in the same session each performing a seperate task.

OK guys finally got it to work the only problem is everytime I reboot my computer i have to reinstall the nvidia drivers just to get x to load the GUI. Anyone have a clue how to get it to stay loaded?

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

# Device configured by xf86config:

Section "Device"
Identifier "Chaintech Geforce FX 5500"
Driver "nvidia"
#VideoRam 262144
# Insert Clocks lines here if appropriate
EndSection


Also does anyone know how to overclock video cards in Linux

That file looks good. You still have something trying to load a bad driver. Check your /etc directory again for modules or modules.conf or something similar and either comment out or completely remove any mention of Nvidia.

What your experiencing is what happened to me. It's what prompted to me search what modules were being loaded.

Can anyone else think of a file that may be calling the unwanted driver at startup?

Have you found that rivafb file? If none of the start up or module related files in /etc mention anything concerning Nvidia (one of them pretty much has too.) then try renaming that rivafb module like so:

navigate to the directory housing the rivafb file and:

mv rivafb rivafb.old

use the entire file name like if the file name is rivafb.o then:

mv rivafb.o rivafb.o.old

I don't feel super good about doing that to a kernel module when something out there is still trying to load it. Especialy when I know that something simple is the hold up. Might be an invitation to disaster. Only do it when there is no hope left and your at the verge of suicide.

I really hate even suggesting it.

look in the file inittab in your /etc directory. might be something there.

for overclocking there once was an app known as nvclock. don't know if its still around or maintained.

when i locate rivafb i get:
/lib/modules/2.6.8.1-12mdksmp/kernel/drivers/video/riva/rivafb.ko.gz

can i delete that file or will it screw up my kernel?

Also NVclock doesn't support FX series yet.

Does glxgears come with MDK 10.1 or do I have to DL it?

Thanks a lot guys
Erick

have you exauhsted every file that I mentioned above for ANY listing of NVIDIA anything? I mean in the file not the directory.

Seems like when I had you search for glx earlier I remember seeing glxgears in the output you posted so you should already have it. Just run it in console. some distros want you to be root to run it some don't.

I wouldn't delete it. Just rename it like I stated earlier. If you have exhausted every effort ( I almost guarantee you that one of those text files has and Nvidia entry and is calling the bad driver). God I'm afraid if you ditch that Frame Buffer device you won't be able to even achieve command line. Buddy its your call but I'm posotive I'm right about one of those text files.

If you do rename that file like: rivafb.ko.gz TO rivafb.ko.gz.old then you will be more likely to recover if something goes awry.


does anybody else want to advise him about deleting this kernel module?

It won't screw up your kernel. Its a module. Modules don't load unless something tells them to. I'm afraid that when whatever is making the call doesn't find the module it will hang. I've been in your boat and I know what its like to see light at the end of the tunnel then screw the pooch.

your one step away. we just have to know why that other driver wont quit bumping your good drivers.

Been burning up google a little. Found a guy here haveing pretty the same prob as you.

look for a file in the /etc directory called modprobe.preload and add the line nvidia no quotes no nothing save and reboot. My system doesn't have the file so I can't paste a sample. Sounds like it will preempt the bad driver with the good one.


Also found some folks who have stated that there first install of the kernel source had gotten corrupted somehow. When the re-installed the kernel source their drivers then installed fine.

Your drivers seem to have installed just fine they just aren't recieving the call. Next time you boot instead of reinstalling the drivers issue the command:

modprobe nvidia

and see if that gives you X without re-install.

I think the first solution (modprobe.preload) comes much closer to your problem. The second one will certainly not hurt.