Riva TNT problem

vertigo

Here, you're configuring the framebuffer device. Don't do that; it's unnecessary, and conflicts with the "video mode selection support" that will let you run your console at higher text resolutions. The standard video driver works just fine.

Here, you're configuring support for the NVIDIA NForce-Nforce2 motherboard chipsets. If you don't have an NVidia chipset on your motherboard, don't do this.

What's the output of "lspci"?

Also, I'm seeing a pattern here. You appear to be selecting options based on their names, not necessarily based on what they do. What method did you use to configure the kernel?

I would suggest "make menuconfig" over any of the others. It's got a clean and simple interface, so it's much easier to examine *every* option before compiling the kernel. (The clean interface is because it's not overdesigned, and has nothing to do with the fact that it's

Don't select kernel options just because of their names. You want to look at the buttociated documentation, which you can access easily if you're using "make config" "make menuconfig" "make xconfig" or "make gconfig".

snip

Both my current primary machines (Compaq 5WV270s) originally came with these cards. One of them still has it. Though I'll admit I don't run X on that system. I use X's networking functionality to display any graphical apps on that system on my desktop machine. (What started as a learning excercise in X turned into a love affair...but I digress.)

FYI...you won't be able to get 3D acceleration on that system without NVidia's binary drivers. I stopped using them when I switched to 2.6.0-test1 way back when, but I hear they now ship compatible by default with the 2.6 kernel series.

I'm not sure your kernel configuration has anything to do with X failing at this point. But disabling the framebuffer kernel options *might* help.