nV News Forums - NVIDIA Linux http://www.nvnews.net/vbulletin Support forum for running NVIDIA based graphics under Linux. en Sat, 21 Nov 2009 11:33:30 GMT vBulletin 60 http://www.nvnews.net/vbulletin/images/misc/rss.jpg nV News Forums - NVIDIA Linux http://www.nvnews.net/vbulletin Lockup Using VDPAU on F12 http://www.nvnews.net/vbulletin/showthread.php?t=141625&goto=newpost Sat, 21 Nov 2009 06:11:16 GMT Playing H264 video on F12 x86_64 with VDPAU via XBMC causes a hard lock-up. The bug report doesn't contain the kernel stack trace, but I grabbed it from a previous lock-up. It happens when the video first starts or 5-10 minutes in.
Attached Files
File Type: gz nvidia-bug-report.log.gz (32.4 KB)
File Type: gz kernel.txt.gz (1.3 KB)
]]> NVIDIA Linux aronparsons http://www.nvnews.net/vbulletin/showthread.php?t=141625 geforce 7600GT / nvclock question http://www.nvnews.net/vbulletin/showthread.php?t=141622&goto=newpost Sat, 21 Nov 2009 02:26:20 GMT Currently, I have a geforce 7600GT here that I was sent though I had ordered a geforce 7600GS! First question: Should I stay with the 7600GT instead? Looks like it is better than the 7600GS, right? Second and more important question: nvclock -i tells me among other things: -- Memory info... Currently, I have a geforce 7600GT here that I was sent though I had ordered a geforce 7600GS!

First question:
Should I stay with the 7600GT instead? Looks like it is better than the 7600GS, right?

Second and more important question:
nvclock -i tells me among other things:

-- Memory info --
Amount: 512 MB
Type: 128 bit DDR
Clock: 265.500 MHz

-- Sensor info --
Sensor: GPU Internal Sensor
GPU temperature: 54C

-- VideoBios information --
Version: 05.73.22.40.01
Signon message: GeForce 7600 GT VGA BIOS
Performance level 0: gpu 400MHz/memory 532MHz/1.10V/100%


So the core clock is 400 MHz, and the memory clock 532 MHz (2x266).


I wonder if this is okay this way, or if I got some product of inferior quality...

The "Axle nvidia geforce 7600GT" is being advertized as having a core clock of 400 MHz and a memory clock of 800 MHz.

So I ask myself why nvclock shows me only 532 Mhz...


Since I am no expert here, let me have a guess:
Is the 532 MHz due to the FSB of my old motherboard (K7S41GX), 2x133MHz=266MHz, not 532 MHz, though...

But is this the reason for the nvclock results?
And would nvclock show me the advertized 800 MHz if I had a more recent system?

Sorry if this sounds all too easy and if it is not precisely Linux specific, but not everybody outside of Linux knows anything about nvclock, and I think, we have some good experts here.

I also noticed that my glxgears fps values at 1680x1050, 16 bit depth, are only around 6800 (with AGP 8x) enabled and not like the 10000 or more fps that I often find reports about... This is with nvclock default values of 400 core and 532 memory clock.

Overclocking those values caused a drastic increase in fps, though.


Thanks, especially for answers to my question about the memory clock!


Petersen ]]> NVIDIA Linux Petersen http://www.nvnews.net/vbulletin/showthread.php?t=141622 Install on slack64 fails if run in a script with installer options http://www.nvnews.net/vbulletin/showthread.php?t=141621&goto=newpost Sat, 21 Nov 2009 00:51:29 GMT I am attempting to install the driver on Slackware64, using the standard 'huge' kernel.

If I run the installer with the following command line:
NVIDIA-Linux-x86_64-190.42-pkg2.run
it completes with no problems. The driver appears to work as well.

If I run it in a script, with the following command line:
NVIDIA-Linux-x86_64-190.42-pkg2.run \
--accept-license \
--no-network \
--no-questions \
--silent
I get the following error:


-> Performing Xen check.
ERROR: The kernel you are installing for is a Xen kernel!

The NVIDIA driver does not currently work on Xen kernels. If
you are using a stock distribution kernel, please install
a variant of this kernel without Xen support; if this is a
custom kernel, please install a standard Linux kernel. Then
try installing the NVIDIA kernel module again.
ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find suggestions
on fixing installation problems in the README available on the Linux
driver download page at www.nvidia.com.


I am not positive how the installer is determining that I have a Xen kernel, but I would expect it to do the same check (and the log says it does) when running without the options.

The reason that I am attempting to run the installer in a script is that I convert everything I install on my machines into a slackware package. This allows me to recover from any disk crashes, etc with minimal downtime. This also provides me with a documentation trail on how to install these additional items. ]]> NVIDIA Linux jimfitz http://www.nvnews.net/vbulletin/showthread.php?t=141621 New libvdpau released 0.3 http://www.nvnews.net/vbulletin/showthread.php?t=141620&goto=newpost Sat, 21 Nov 2009 00:22:31 GMT Hello, new vdpau released: 0.3. http://lists.freedesktop.org/archives/xorg-announce/2009-November/001200.html Hello,

new vdpau released: 0.3.
http://lists.freedesktop.org/archive...er/001200.html ]]> NVIDIA Linux zbiggy http://www.nvnews.net/vbulletin/showthread.php?t=141620 glxgears is 5 fps http://www.nvnews.net/vbulletin/showthread.php?t=141619&goto=newpost Sat, 21 Nov 2009 00:07:56 GMT Seems like glxgears and 3D screensavers are not accelerated after installing the 190.42 driver. Everything else is working great (rotated twinview, compositing). 6600GT that was properly accelerated on Mandriva 2008 + 180.60. Not properly 3D accelerated under Mandriva 2010 + 190.42 Is there... Seems like glxgears and 3D screensavers are not accelerated after installing the 190.42 driver. Everything else is working great (rotated twinview, compositing). 6600GT that was properly accelerated on Mandriva 2008 + 180.60. Not properly 3D accelerated under Mandriva 2010 + 190.42

Is there something obviously incorrect below?

# ldd /usr/bin/glxgears
linux-vdso.so.1 => (0x00007ffffe7ff000)
libGL.so.1 => /usr/lib64/nvidia-current/libGL.so.1 (0x00007fb2b4c88000)
libm.so.6 => /lib64/libm.so.6 (0x00007fb2b4a06000)
libc.so.6 => /lib64/libc.so.6 (0x00007fb2b46a8000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fb2b436e000)
libGLcore.so.1 => /usr/lib64/nvidia-current/libGLcore.so.1 (0x00007fb2b2f11000)
libnvidia-tls.so.1 => /usr/lib64/nvidia-current/tls/libnvidia-tls.so.1 (0x00007fb2b4f7b000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007fb2b2cff000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fb2b2afb000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb2b4e80000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fb2b28df000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fb2b26dc000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007fb2b24d6000)
# ]]> NVIDIA Linux xorbe http://www.nvnews.net/vbulletin/showthread.php?t=141619 NVIDIA(0): Failed to allocate clip rectangle in kdm.log http://www.nvnews.net/vbulletin/showthread.php?t=141614&goto=newpost Fri, 20 Nov 2009 22:30:49 GMT Hi. Recently upgraded from kubuntu 9.04 to kubuntu 9.10. Ever since, unable to launch the x windows. kdm.log reports this: (EE) NVIDIA(0): Failed to allocate clip rectangle (EE) NVIDIA(0): *** Aborting *** (EE) NVIDIA(0): Failed to allocate clip rectangle (EE) NVIDIA(0): *** Aborting *** (EE)... Hi. Recently upgraded from kubuntu 9.04 to kubuntu 9.10. Ever since, unable to launch the x windows.

kdm.log reports this:

(EE) NVIDIA(0): Failed to allocate clip rectangle
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Failed to allocate clip rectangle
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Failed to allocate clip rectangle
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Failed to allocate clip rectangle
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***

and that's it. Black & blank screen. :(

Can you please help? Coming from a Solaris world, a bit disheartened here.

Thank you! ]]> NVIDIA Linux logastellus http://www.nvnews.net/vbulletin/showthread.php?t=141614 twinview + rotate, no randr http://www.nvnews.net/vbulletin/showthread.php?t=141613&goto=newpost Fri, 20 Nov 2009 22:08:35 GMT Because I have my panels rotated using TwinView and XRandR is automatically disabled, every time I start a program it spews out:
Xlib: extension "RANDR" missing on display ":0.0".
Yes, I'm well aware of that. How to I squelch this noise? Thanks! ]]> NVIDIA Linux xorbe http://www.nvnews.net/vbulletin/showthread.php?t=141613 Gnome-shell with TripleBuffer enabled crashes X.org http://www.nvnews.net/vbulletin/showthread.php?t=141610&goto=newpost Fri, 20 Nov 2009 19:27:30 GMT As the title says... when tripplebuffer is enabled in x.org, starting gnome-shell will crash X imediately. I'm using nvidia-driver 190.42 on a thinkpad R61 with quadro NVS140. The X.org-Server is 1.6.5 (Debian unstable).
It would be real nice if both could run together as tripplebuffer increases speed with normal metacity enormous for me. ]]> NVIDIA Linux packermann http://www.nvnews.net/vbulletin/showthread.php?t=141610 Flickering below mouse pointer http://www.nvnews.net/vbulletin/showthread.php?t=141605&goto=newpost Fri, 20 Nov 2009 17:29:42 GMT I have this strange problem that the screen flickers, but only the part that is lower than the current mouse pointer position. The temporary fix is to keep the pointer at the bottom of the screen but I'm looking for something more permanent. The flickering occurs when there is a lot of graphics to refresh on the screen, e.g. scrolling through Picasa, loading a very large image in Firefox, watching a video in Totem.

I have an nVidia GeForce 8200, the latest 190.42 drivers, and Ubuntu 9.10 64-bit. The problem doesn't occur if I load the standard drivers that come with Ubuntu, but that forces me into a lower resolution. I attach a bug report log.

I'd be grateful if anyone could help because I've been searching for a solution for a long time now. Thanks!
Attached Files
File Type: gz nvidia-bug-report.log.gz (62.0 KB)
]]> NVIDIA Linux SSSimon http://www.nvnews.net/vbulletin/showthread.php?t=141605