New NVIDIA beta 185.19 speeds up 2D operations

whoops · 2009-04-16 16:15:00

vi3dr0 wrote:

Desktop is surely flying now, however something odd happened to ut2004 It shows even slight performance progress in theory(like 180 instead of 150fps), however mouse has 0.5 sec lags every few seconds, and general gaming experience is definetly worse. I hope it will get fixed when it goes out of beta.:rolleyes:

Did you check the temperature? I had exactly the same problem playing ut2004 a few years ago every other driver version - but only in summer. You can try to under-clock your card - did help me trade back the 20fps more for no lag on some occasions.

Devastator · 2009-04-16 21:48:10

Satchmo wrote:

Devastator wrote:
It seems that NVidia drivers are sometimes broken for some specific cards... 177.82 were fine in my case, but I've got troubles on 180.18 and 180.22, so I skipped 180.25, went for 180.27 which were ok...
Which card? Because I have a 7300LE, and I was sticking with 180.16, since 180.18, 180.22 and 180.44 give me constant freezes. So does 185.19.

I have 8600M GT in an Asus laptop.
I've read some issues people keep posting on nvnews and it seems that almost every release fixes bugs fore some people, but creates new bugs for other people... kinda strange.

vi3dr0 · 2009-04-17 08:10:39

whoops wrote:

Did you check the temperature? I had exactly the same problem playing ut2004 a few years ago every other driver version - but only in summer. You can try to under-clock your card - did help me trade back the 20fps more for no lag on some occasions.

It's about 70-75 C, so i'm not worried, but thanks for the idea - i would be happy to trade some FPS for lower temperature while playing on my laps

Devastator · 2009-04-17 17:21:32

vi3dr0 wrote:

whoops wrote:
Did you check the temperature? I had exactly the same problem playing ut2004 a few years ago every other driver version - but only in summer. You can try to under-clock your card - did help me trade back the 20fps more for no lag on some occasions.
It's about 70-75 C, so i'm not worried, but thanks for the idea - i would be happy to trade some FPS for lower temperature while playing on my laps

Whoops... mine is reaching 96 C in extreme cases... (some say it's okay though...)

so...

how can I underclock the nvidia card?

buttons · 2009-04-17 19:18:40

Damn. My desktop card sees 55C tops (with aftermarket air cooling). I'd be quite afraid of seeing 96C in any enclosed space; it's likely to cause permanent damage elsewhere (such as the oh so slow hot hard drive death, where it gets slower by tiny increments over time.)

Fackamato · 2009-04-17 20:10:07

buttons wrote:

Damn. My desktop card sees 55C tops (with aftermarket air cooling). I'd be quite afraid of seeing 96C in any enclosed space; it's likely to cause permanent damage elsewhere (such as the oh so slow hot hard drive death, where it gets slower by tiny increments over time.)

Graphic cards are fine with ~90 degrees celsius.

whoops · 2009-04-17 21:06:06

With a modern card I think 95 and sometimes up to 110° should still be OK. After that, nvidia cards are throttling down as far as I know. I guess what caused most of my problems (had a lot of heat issues besides playing UT & lag over the last year in this oven-like apartment here ) was when the CPU doesn't get cool enough air any more and starts to throttle. No Idea how exactly that works, but it felt like everything had to wait for CPU or RAM, while the graphics card that caused the heat was still running at max speed (those things can roast your mainboard and your cat, set your house on fire and still complain to the bus/harddisk that it's not getting the textures fast enough while it's melting itself through the ground towards the middle of the earth!).

Nvidia-Settings has an option "Clock Frequencies" that is only visible if you activate Screen Option
Option "Coolbits" "1"
in xorg.conf. For me, settings GPU from 513 to 400 and Memory from 792 to 600 made the Graphics Card Temperature drop from 67° down to 64 and the overall temp go down by 5 to 15° (I don't know what the other 5 sensors are, I think maybe chassis is down from 44 to 34 and CPU is down from 64 to 48 edit: omg, the many numbers confuse me, forget those and replace it by: "gets cooler I think").

Compiz Desktop still running smooth, for some reason my Wlan-Stick is vibrating but I guess that means a fan slowed down which would be a good thing in theory (Maybe I should really actually use the cable binders instead of stuffing everything that's not connected behind the hard-drives and only just entageling this black thing that hangs to close to the cpu with a surplus earthing cable so it doesn't get into the fan )

Last edited by whoops (2009-04-17 21:17:45)

ungoliant · 2009-06-25 15:50:24

broch wrote:

xstaticxgpx wrote:

haxit wrote:

New driver not working with new kernel?

I had issues with 185.19 building against 2.6.30-rc1 too if that's what you're talking about.

**
Yup, 185.13/19 and 180.44 have the same failure when building against 2.6.30-rc1...

-> Building kernel module:
   executing: 'cd ./usr/src/nv; make module SYSSRC=/lib/modules/2.6.30-rc1-ARCH
   /source SYSOUT=/lib/modules/2.6.30-rc1-ARCH/build'...
   NVIDIA: calling KBUILD...
   make CC=cc KBUILD_OUTPUT=/lib/modules/2.6.30-rc1-ARCH/build KBUILD_VERBOSE=1
   -C /lib/modules/2.6.30-rc1-ARCH/source SUBDIRS=/tmp/selfgz2357/NVIDIA-Linux-
   x86_64-185.19-pkg0/usr/src/nv modules
   make -C /lib/modules/2.6.30-rc1-ARCH/build \
       KBUILD_SRC=/home/xsx/Build/kernel/linux-2.6.30-rc1 \
       KBUILD_EXTMOD="/tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv" 
   -f /home/xsx/Build/kernel/linux-2.6.30-rc1/Makefile \
       modules
   test -e include/linux/autoconf.h -a -e include/config/auto.conf || (        \
       echo;                                \
       echo "  ERROR: Kernel configuration is invalid.";        \
       echo "         include/linux/autoconf.h or include/config/auto.conf are mis
   sing.";    \
       echo "         Run 'make oldconfig && make prepare' on kernel src to fix it
   .";    \
       echo;                                \
       /bin/false)
   mkdir -p /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/.tmp_ver
   sions ; rm -f /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/.tm
   p_versions/*
   make -f /home/xsx/Build/kernel/linux-2.6.30-rc1/scripts/Makefile.build obj=/
   tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv
     cc -Wp,-MD,/tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/.nv.
   o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-unknown-linux-gnu/4.3.3/include 
   -Iinclude -Iinclude2 -I/home/xsx/Build/kernel/linux-2.6.30-rc1/include -I/ho
   me/xsx/Build/kernel/linux-2.6.30-rc1/arch/x86/include -include include/linux
   /autoconf.h   -I/tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv -
   D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-ali
   asing -fno-common -Werror-implicit-function-declaration -O2 -m64 -march=core
   2 -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args 
   -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -pipe -Wno-sign-compare -fn
   o-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -fno-sta
   ck-protector -fno-omit-frame-pointer -fno-optimize-sibling-calls -Wdeclarati
   on-after-statement -Wno-pointer-sign -fwrapv   -I/tmp/selfgz2357/NVIDIA-Linu
   x-x86_64-185.19-pkg0/usr/src/nv -Wall -Wim
   plicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wparentheses -Wpoi
   nter-arith -Wno-multichar -Werror -mcmodel=kernel -mno-red-zone -MD -Wsign-c
   ompare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_S
   TRING=\"185.19\" -UDEBUG -U_DEBUG -DNDEBUG  -DMODULE -D"KBUILD_STR(s)=#s" -D
   "KBUILD_BASENAME=KBUILD_STR(nv)"  -D"KBUILD_MODNAME=KBUILD_STR(nvidia)"  -c 
   -o /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.o /tmp/self
   gz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c
   In file included from include/linux/bitops.h:17,
                    from include/linux/kernel.h:15,
                    from include/linux/sched.h:52,
                    from include/linux/utsname.h:35,
                    from /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/sr
   c/nv/nv-linux.h:19,
                    from /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/sr
   c/nv/nv.c:14:
   /home/xsx/Build/kernel/linux-2.6.30-rc1/arch/x86/include/asm/bitops.h: In fu
   nction 'set_bit':
   /home/xsx/Build/kernel/linux-2.6.30-rc1/arch/x86/include/asm/bitops.h:64: wa
   rning: pointer of type 'void *' used in arithmetic
   /home/xsx/Build/kernel/linux-2.6.30-rc1/arch/x86/include/asm/bitops.h: In fu
   nction 'clear_bit':
   /home/xsx/Build/kernel/linux-2.6.30-rc1/arch/x86/include/asm/bitops.h:102: w
   arning: pointer of type 'void *' used in arithmetic
   /home/xsx/Build/kernel/linux-2.6.30-rc1/arch/x86/include/asm/bitops.h: In fu
   nction 'change_bit':
   /home/xsx/Build/kernel/linux-2.6.30-rc1/arch/x86/include/asm/bitops.h:178: w
   arning: pointer of type 'void *' used in arithmetic
   In file included from include/linux/utsname.h:35,
                    from /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/sr
   c/nv/nv-linux.h:19,
                    from /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/sr
   c/nv/nv.c:14:
   include/linux/sched.h: In function 'object_is_on_stack':
   include/linux/sched.h:2119: warning: pointer of type 'void *' used in ar
   ithmetic
   In file included from include/linux/dma-mapping.h:7,
                    from include/asm-generic/pci-dma-compat.h:7,
                    from /home/xsx/Build/kernel/linux-2.6.30-rc1/arch/x86/inclu
   de/asm/pci.h:129,
                    from include/linux/pci.h:1098,
                    from /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/sr
   c/nv/nv-linux.h:86,
                    from /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/sr
   c/nv/nv.c:14:
   include/linux/scatterlist.h: In function 'sg_virt':
   include/linux/scatterlist.h:199: warning: pointer of type 'void *' used 
   in arithmetic
   In file included from /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/sr
   c/nv/nv-linux.h:113,
                    from /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/sr
   c/nv/nv.c:14:
   include/linux/highmem.h: In function 'zero_user_segments':
   include/linux/highmem.h:147: warning: pointer of type 'void *' used in a
   rithmetic
   include/linux/highmem.h:150: warning: pointer of type 'void *' used in a
   rithmetic
   In file included from include/linux/compat.h:14,
                    from /home/xsx/Build/kernel/linux-2.6.30-rc1/arch/x86/inclu
   de/asm/mtrr.h:167,
                    from /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/sr
   c/nv/nv-linux.h:142,
                    from /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/sr
   c/nv/nv.c:14:
   /home/xsx/Build/kernel/linux-2.6.30-rc1/arch/x86/include/asm/compat.h: In fu
   nction 'compat_alloc_user_space':
   /home/xsx/Build/kernel/linux-2.6.30-rc1/arch/x86/include/asm/compat.h:210: w
   arning: pointer of type 'void *' used in arithmetic
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c: In function
   'nvos_proc_create':
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c:591: error: 
   'struct proc_dir_entry' has no member named 'owner'
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c:592: error: 
   'struct proc_dir_entry' has no member named 'owner'
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c:593: error: 
   'struct proc_dir_entry' has no member named 'owner'
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c:613: error: 
   'struct proc_dir_entry' has no member named 'owner'
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c:627: error: 
   'struct proc_dir_entry' has no member named 'owner'
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c:638: error: 
   'struct proc_dir_entry' has no member named 'owner'
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c:648: error: 
   'struct proc_dir_entry' has no member named 'owner'
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c:658: error: 
   'struct proc_dir_entry' has no member named 'owner'
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c:669: error: 
   'struct proc_dir_entry' has no member named 'owner'
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c:676: error: 
   'struct proc_dir_entry' has no member named 'owner'
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c: In function
   'nvos_proc_add_warning_file':
   /tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.c:703: error: 
   'struct proc_dir_entry' has no member named 'owner'
   make[4]: *** [/tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/src/nv/nv.
   o] Error 1
   make[3]: *** [_module_/tmp/selfgz2357/NVIDIA-Linux-x86_64-185.19-pkg0/usr/sr
   c/nv] Error 2
   make[2]: *** [sub-make] Error 2
   NVIDIA: left KBUILD.
   nvidia.ko failed to build!
   make[1]: *** [module] Error 1
   make: *** [module] Error 2
-> Error.
ERROR: Unable to build the NVIDIA kernel module.
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.

This was explained so many times, that I don't any point to do this again. Anyway, this is very simple fix and nvidia will build.

It wouldnt hurt to provide a link for those who have never had this problem, and are reading this problem, so they are aware of what could happen.

Ranguvar · 2009-06-25 16:14:25

buttons wrote:

And with this release, nvidia FINALLY fixes the horrible >4GB of ram on X86_64 bug on all of their release lines. It's about bloody time.

What bug was that? Google isn't giving me much. I have Arch x86_64 with 6GB of RAM, but never had any trouble?

Arch Linux

#26 2009-04-16 16:15:00

Re: New NVIDIA beta 185.19 speeds up 2D operations

#27 2009-04-16 21:48:10

Re: New NVIDIA beta 185.19 speeds up 2D operations

#28 2009-04-17 08:10:39

Re: New NVIDIA beta 185.19 speeds up 2D operations

#29 2009-04-17 17:21:32

Re: New NVIDIA beta 185.19 speeds up 2D operations

#30 2009-04-17 19:18:40

Re: New NVIDIA beta 185.19 speeds up 2D operations

#31 2009-04-17 20:10:07

Re: New NVIDIA beta 185.19 speeds up 2D operations

#32 2009-04-17 21:06:06

Re: New NVIDIA beta 185.19 speeds up 2D operations

#33 2009-06-25 15:50:24

Re: New NVIDIA beta 185.19 speeds up 2D operations

#34 2009-06-25 16:14:25

Re: New NVIDIA beta 185.19 speeds up 2D operations

Board footer