Just an update on my experiences with the new nVidia drivers (and install routine) under Mandrake 9.1.Mine was slower ( 289.400 FPS -- was about 410 FPS ) I am guessing it's because of being set up different i.e. 24 bit (my card only has 32 MB so I am going to try 16 bit and restart X to see --( after I send this reply)) The number of bits would have an effect on a card like mine, as far as I know for texture handling, so this might not give me better results running glxgears ----- <attempting to switch OFF babel mode> -----
1: Faster 3D frame rates, estimate around 25% based on glxgears
I have found xine-check to be a good basic diagnostic. Also with mplayer I have seen reference to setting mplayer as root SUID to let it have enough direct access to the vidio card to do all the extream accelleration
2: Others claim better 2d performance also, I have not seen this, or am I sure as to how to check.
Humm, have you tried adding the mem=nopentium append to your lilo.conf file ?
3: Running xawtv steadily in a small window, I used to get lots of screen refresh's, depending on where the cursor moved. Mostly anoying but noticed they would go away if I closed down xawtv. All is stable now but I am not sure if this is a result of the new XFree86, Mandrake or the nVidia drivers.
4: Still no dual x-sessions on dual monitor setup
5: Random reboots of system. Yeah the bad news, at least for me and my setup. Since my default OS on boot is Redhat, if I leave MDK on and wake up to the Redhat login, pretty clear what happened. It has also happend once while working, just out of the blue system rebooted. I did not notice this at all with the Mandrake provided "nv" drivers so likely related to the new drivers from nVidia, at least with my system. Might try changin or disabling screen saver but since I have seen this behavior without the screen saver on, might not help.
I added this after some one at the second last clug meeting suggested I try this. I too, had a long history of very strange X stability problems and lock ups. Like using a brouser at times.
this was part of the lilo.conf mdk9.1 made (I'm not using it now) which seemed to work OK the first half day I was booting off of it.
========================
image=/boot/vmlinuz
label="linux"
root=/dev/hda1
initrd=/boot/initrd.img
append="quiet devfs=mount hdd=ide-scsi acpi=off"
vga=788
read-only
( try changing to :
append="quiet devfs=mount hdd=ide-scsi acpi=off mem=nopentium"
=========================================================END of lilo.conf mdk9.1 quote
eg from my lilo.conf generated from my Debian boot
default=Linux
image=/vmlinuz
label=Linux
root=/dev/hdc2
append="quiet devfs=mount hdd=ide-scsi ide-cd ignore=hdd mem=nopentium"
# vga=788
# initrd=/initrd.img
read-only
# restricted
# alias=1
==================END of my Debian lilo.conf
I think you will want to look at how X was setup on your system with: less /var/log/XFree86.0.log
Ah, the trick now will be to look up were the custom setting are done with the new auto (almost magic ) nvidia driver.
That may very as to how nvidia wanted to do its job on each system setup. I'm still going to look at this (later) on my system.
HOPE that this reference to men=nopentium may help you sort things out.
Mel
<hr> <b><font color=blue size=4>Open Enterprise Solutions</font></b> <b><font color=red>Linux & Open Source Solutions for Business</font></b>
Johnny Stork, BA Calgary, AB Canada
<a href="http://www.openenterprise.ca";> www.openenterprise.ca</a>
--------------------------------------------------- The Webtop Personal Web-based Email System http://www.yourwebtop.com
