If this resolution worked with the other driver (nv), you'll want to use this option: Option "IgnoreEDID" "boolean" Disable probing of EDID (Extended Display Identification Data) from your monitor. Requested modes are compared against values gotten from your monitor EDIDs (if any) during mode validation. Some monitors are known to lie about their own capabilities. Ignoring the values that the monitor gives may help get a certain mode validated. On the other hand, this may be dangerous if you don't know what you are doing. Default: Use EDIDs. hth,
From Ron Cordell to Curtis Rey and suse-linux-e@suse.com about Re: [SLE]...:
I snuck some time from work to play with this a little more. Booting to the command line instead of the graphical prompt allowed me to see quite a bit more information about what errors were for the display when attempting to start X. Turns out that the nvidia driver did not like my 1600x1200 display resolution. I ran SAX2 from the command line, and lo and behold, there is a cool NVidia screen coming up on my X Server! Wow!
I set for 1024x768 and that worked. I then set up 1280x1024 and that is what I am using now. I don't know why 1600x1200 doesn't work - oh well. I suppose that will give my eyes a rest. :-) Still, a 21" monitor does will at that resolution, and 1280x1024 looks HUGE ;-)
So I ran gears, and at the default window size that comes up I get 1008 FPS. At full screen I get something like 264 FPS.
The only thing that I changed in my XF86Config file was the setting for videoram and the driver from "nv" to "nvidia". I wonder if it was the videoram setting that made the difference.
-ronc
On Tuesday 05 June 2001 11:19, you wrote:
This may or may not help. Modules:
Load "dbe" #double buffer extension Load "glx" #you did that #Load "dri" #useless under nvidia #Load "GLcore #loads implicitly, no need to delcare Load "extmod" #think this lets and driver extensions load?
Then, another thing; the mesa drivers. It's ok (and even desireable) to leave the mesa lib in, but the driver conflicts - therefore: "rpm -e mesasoft".
And also, in the user account: login when in gui to the console using "sux" (the x give SU user privileges to the X-server of the user) and then root password. Now give command "switch2nvidia_glx" (that's after switching the Driver from nv to nvidia) > also you can change "Identifier" for Device[0] to "NV AGP" and add Videoram "32768" or whatever size the vid-ram is in Kb's.
Also, some have stated that the rpm's don't load/install the kernel modules correctly. Might also try to use tarballs.
Cheers, Curtis
On Monday 04 June 2001 09:23 am, Ron Cordell wrote:
Ok, now it's my turn :-)
I downloaded the latest NVIDIA drivers for SuSE and installed them. I then ran the switch2nv_glx shell script.
I added "glx" to the Loaded Modules in XF86Config, and then restarted X.
I noticed that the xconsole indicated the following: Jun 4 10:12:31 linux kernel: NVRM: loading NVIDIA kernel module version 1.0-1251
Now when I attempt to run gears, I get the following error message: Xlib: extension "NV-GLX" missing on display ":0.0". Segmentation fault
If I try to enable and run an OpenGL screensaver, I get the KDE Krash handler.
Here is the portion of my XF86Config file for the TNT2 Ultra card: Section "Device" BoardName "Riva TNT2 Ultra" Driver "nv" Identifier "Device[0]" Screen 0 VendorName "Nvidia" EndSection
I have tried to set the Driver to "nvidia" from "nv", but when I do that, X will not start at all.
I don't really run 3D stuff on this machine, but it would be nice to have the card working, somewhat.
If I am missing something obvious, please let me know. I've been monitoring the NVIDIA thread for a few weeks, now, but haven't seen anything that seems applicable.
Thanks,
Ron Cordell
On Saturday 02 June 2001 05:46, you wrote:
* Brian Dunaway (brian@fusionwerks.com) [010602 02:40]: ->> The latest drivers need to be 'activated' for 3D. The file tells you to ->> install them in a particular order and then run the ->> "switch2nvidia.glx"(sp?) file to activate the 3D. -> ->I have tried it two ways both on fresh installs. I installed 7.2 personal ->edition straight out of the box and downloaded the drivers from Nvidia ->following their intructions. I get OpenGL support in my games no ->problem...but my GL screensavers and Blender both look for Mesa drivers. I ->also tried getting the software update from the Yast Control Center before I ->installed the Nvidia drivers from Nvidia....I get the same bugginess before ->and after I install the Nvidia drivers from Nvidia's site. -> ->> I did what it said and mine works fine on a very similar system to your own ->> (V550, AMD450). Without the switch-file being run I got about 50fps in ->> 'gears', afterwards I got over 400. (Just type "gears" in the console and ->> that should run it - it prints the FPS in the console window so you can see ->> if your 3D accel is working) -> ->I ran gears and I get a little more than 600 FPS.
Ok..it wouldn't look for the Mesa drivers if you installed nVidia's GLX and run the modified 'switch2nv_glx' script I've posted twice. It really does work. I just ran the pipes GL screen saver in KDE2 in order to check.. :)
Here ya go...
-- dieter