View Full Version : New Beta Nvidia Driver 100.14.06
Jupiter
May 22nd, 2007, 03:52 AM
There is a new beta nvidia driver release. From what i read in one forum the
black window/screen bug is fixed. However after reading the readme file, I
found no reference to the problem being fixed. It is possible however that
it is fixed and my understanding of some of the more technical mumbo jumbo
in the readme file explains it.
I have installed this driver and am experiencing higher performance from it.
There are also some recommendations pertaining to options when using the
composite extension, as we do for compcomm/beryl.
[code:551c5]
Section "Device"
Identifier "Nvidia"
Option "DamageEvents" "True"
[/code:551c5]
Anyone who has experienced the black window/screen problem and willing
to try this new driver, please report back. I have installed it but i never have
this problem, so am unable to confirm whether it is fixed or not.
x86
http://www.nvidia.com/object/linux_disp ... 14.06.html (http://www.nvidia.com/object/linux_display_ia32_100.14.06.html)
x64
http://www.nvidia.com/object/linux_disp ... 14.06.html (http://www.nvidia.com/object/linux_display_amd64_100.14.06.html)
Readme info on composite
http://us.download.nvidia.com/XFree86/L ... er-23.html (http://us.download.nvidia.com/XFree86/Linux-x86/100.14.06/README/chapter-23.html)
Readme info on Known issues
http://us.download.nvidia.com/XFree86/L ... er-09.html (http://us.download.nvidia.com/XFree86/Linux-x86/100.14.06/README/chapter-09.html)
delfick
May 22nd, 2007, 10:47 AM
nope, still got the black window bug :(
Jupiter
May 22nd, 2007, 02:07 PM
nope, still got the black window bug :(
Thanks for letting me know delfick. I just left ANOTHER message in the Nvidia
forum letting them know that THIS SUCKS.
delfick
May 22nd, 2007, 04:04 PM
nope, still got the black window bug :(
Thanks for letting me know delfick. I just left ANOTHER message in the Nvidia
forum letting them know that THIS SUCKS.
lol :D
the frustration !!
Jupiter
May 22nd, 2007, 04:25 PM
delfick can you do an experiment for me please.
If you have xorg-7.2 or higher and using the beta driver
Please try your xorg.conf this way
[code:ae94a]
Section "Device"
Identifier "Nvidia"
Driver "nvidia"
Option "RenderAccel" "True" ##Performance will be degraded significantly if option is disabled
Option "TripleBuffer" "True"
# Option "AllowGLXWithComposite" "True" ## automatically enabled when composite enabled
# Option "AddARGBGLXVisuals" "True" ## not needed with >X11R6.9.0
# This option must be either undeclared or false, in order to avoid periodic short-term freezes on beryl and other
# OpenGL intensive programs
Option "UseEvents" "False" ## see above comment
#Use OS-level events to efficiently notify X when a client has performed direct rendering to a window that needs to be #composited. This will significantly improve performance and interactivity when using GLX applications with a #composite manager running. It will also affect applications using GLX when rotation is enabled. This option is #currently incompatible with SLI and Multi-GPU modes and will be disabled if either are used. Enabled by default.
Option "DamageEvents" "True" ### see above comment
# Option "DisableGLXRootClipping" "True" ## needed by older versions of OpenGL-based composite managers
[/code:ae94a]
Everything seems to run fine for me with this type of config. Can you let me know if this helps
performance/black window, on your end. I do see a slight performance increase.
All the information here is gathered from the readme file.
http://us.download.nvidia.com/XFree86/L ... dix-b.html (http://us.download.nvidia.com/XFree86/Linux-x86/100.14.06/README/appendix-b.html)
http://us.download.nvidia.com/XFree86/L ... er-23.html (http://us.download.nvidia.com/XFree86/Linux-x86/100.14.06/README/chapter-23.html)
EXAMPLE: i usually see about 15000+ FPS with my old config/driver, vsync enabled
now i see 17000+ FPS
[code:ae94a]zero@vger ~ $ beryl &
[1] 7186
zero@vger ~ $ ************************************************** ************
* Beryl system compatibility check *
************************************************** ************
Detected xserver : NVIDIA
Checking Display :0.0 ...
Checking for XComposite extension : passed (v0.3)
Checking for XDamage extension : passed
Checking for RandR extension : passed
Checking for XSync extension : passed
Checking Screen 0 ...
Checking for GLX_SGIX_fbconfig : passed
Checking for GLX_EXT_texture_from_pixmap : passed
Checking for non power of two texture support : passed
Checking maximum texture size : passed (8192x8192)
[Warning ]: Relaunching beryl with __GL_YIELD="NOTHING"
************************************************** ************
* Beryl system compatibility check *
************************************************** ************
Detected xserver : NVIDIA
Checking Display :0.0 ...
Checking for XComposite extension : passed (v0.3)
Checking for XDamage extension : passed
Checking for RandR extension : passed
Checking for XSync extension : passed
Checking Screen 0 ...
Checking for GLX_SGIX_fbconfig : passed
Checking for GLX_EXT_texture_from_pixmap : passed
Checking for non power of two texture support : passed
Checking maximum texture size : passed (8192x8192)
Initiating splash
zero@vger ~ $
zero@vger ~ $ glxgears
86507 frames in 5.0 seconds = 17301.324 FPS
87710 frames in 5.0 seconds = 17541.821 FPS
87688 frames in 5.0 seconds = 17537.484 FPS
88093 frames in 5.0 seconds = 17617.349 FPS
87545 frames in 5.0 seconds = 17508.962 FPS
85737 frames in 5.0 seconds = 17147.356 FPS
85995 frames in 5.0 seconds = 17198.842 FPS
[/code:ae94a]
delfick
May 22nd, 2007, 04:37 PM
do i still put in the busID and the NvAgp option ??
so instead of this
[code:fc491]Section "Device"
Identifier "nVidia Corporation NV43 [GeForce 6600 GT]"
Driver "nvidia"
BusID "PCI:1:0:0"
Option "NvAgp" "1"
Option "damageEvents" "True"
EndSection[/code:fc491]
i get this
[code:fc491]
Section "Device"
Identifier "nVidia Corporation NV43 [GeForce 6600 GT]"
BusID "PCI:1:0:0"
Option "NvAgp" "1"
Driver "nvidia"
Option "RenderAccel" "True"
Option "TripleBuffer" "True"
Option "UseEvents" "False"
Option "DamageEvents" "True"
EndSection
[/code:fc491]
??
with that, and i have xorg-7.2, after 8 openoffice windows i get black windows.....
delfick
May 22nd, 2007, 04:39 PM
i get this for glxgears
[code:5b31b]iambob@bob-linux:~$ glxgears
378 frames in 5.0 seconds = 75.505 FPS
376 frames in 5.0 seconds = 75.011 FPS
375 frames in 5.0 seconds = 74.995 FPS
376 frames in 5.0 seconds = 75.055 FPS
366 frames in 5.0 seconds = 73.025 FPS
[/code:5b31b]
Jupiter
May 22nd, 2007, 04:48 PM
Ok so black window bug,,, no difference
Performance = you will have to tell me if it is better
Config works fine without
Option "AllowGLXWithComposite" "True"
Option "AddARGBGLXVisuals" "True"
Option "DisableGLXRootClipping" "True"
Thanks for the info. Am trying to determine what is exactly needed/not needed
to use beryl/compcomm so we can better help users.
You rock.... thanks delfick
lurkinator
May 22nd, 2007, 10:02 PM
tried the new driver and it's fuct(beta though so whaddya gonna do eh). I also got black windows, after starting beryl like this: beryl --indirect-rendering --xgl-binding --use-tfp --replace & instead of this: beryl --force-aiglx --indirect-rendering --xgl-binding --use-tfp --replace & (I don't get them starting it the latter way). I then commented out the '"AIGLX" "true"' option in my xorg.conf and restarted X(I figured if I was going to stop using the force-aiglx option I ought to try removing it from my xorg.conf too). Then I tried to replace with kwin (so I could try again replacing with beryl and no aiglx forcing) but then the computer stopped accepting input (only mouse movement, no clicks or keyboard). Hit the reset button after I couldn't kill X and then I tried to VT switch from the kdm login screen - and then I caught a glimpse of what looked the corruption I used to get on VT-switching with a framebuffer console(8xxx series), before the monitor shut off. I was able to switch back to kdm on vt7 and tried to use the console login from the session menu. Then the same thing happened with what looked like corruption but I couldn't really glimpse it because the monitor was switching off, only this time I couldn't switch back to vt7. I booted into single user mode at that point and installed 9755 again. I learned I don't need the '"AIGLX" "true"' option to use --force-aiglx on startup at least (I guess because I'm not really using AIGLX eh Jupiter?). anyway, too buggy for me to offer better info, sorry.
delfick
May 22nd, 2007, 11:26 PM
you will have to tell me if it is better
i'm not sure....sry :P :D
[quote:a70ac]You rock.... thanks delfick[/quote:a70ac]
no probs :D :D
vBulletin® v3.7.1, Copyright ©2000-2008, Jelsoft Enterprises Ltd.