You are not logged in.
I just upgraded to 185.19, and 2D really speeds up!
Release Highlights:
* Added support for the following new GPUs:
o Quadro FX 3800
o Quadro FX 1800
o Quadro FX 380
o Quadro FX 580
o GeForce GTS 250
o GeForce GT 140
o GeForce GT 130
o GeForce 9600 GSO 512
* Fixed SDI presentation time queries returning unexpected values.
* Removed the 'AllowDFPStereo' X config file option, which is now enabled by default.
* Fixed a bug that caused certain programs to hang when multiple threads call functions in libdl at the same time.
* Fixed a driver crash when OpenGL applications use an extremely large number of textures.
* Text rendering to PseudoColor windows with the glyph cache enabled no longer causes GPU errors.
* The X driver now allows pixmaps smaller than 32x32 pixels to be placed in video memory.
* Fix a problem that prevented the driver from retraining a DisplayPort link after a device is hotplugged.
* nvidia-bug-report.sh now automatically gzips the resulting log file.
* Fix VDPAU to eliminate some cases of GPU hangs when decoding H.264 video on G84, G86, G92, G94, G96, or GT200 GPUs, and supplying a DPB missing some reference frames.
* The VDPAU presentation queue now syncs to VBLANK in the blit path. The environment variable VDPAU_NVIDIA_SYNC_DISPLAY_DEVICE selects which display to sync to when TwinView is enabled; see the README for details.
* On systems using integrated graphics, VDPAU now uses system RAM instead of video RAM for many purposes. This should prevent "out of resources" problems in most cases, even when the video RAM carve-out is configured as low as 128M.
* Added support for Quad-Buffered Stereo in the main plane simultaneously with the Color Index Overlay; i.e., both Stereo GLX FBConfigs and Color Index Overlay FBConfigs can be advertised and used at the same time, though no single GLX FBConfig contains both Stereo and Overlay capabilities.
What's interesting here from a 2D perspective is the support for smaller than 32x32 pixmaps. This really speeds things up on my system (8600M GT), Firefox is faster (not using beta), as is moving around windows (for example gnome-terminal with pseudo-transparency).
Highly recommended!
nvidia-utils-beta: http://aur.archlinux.org/packages.php?ID=19224
nvidia-beta: http://aur.archlinux.org/packages.php?ID=15152
Offline
Installing!
Offline
Thanks for the heads up, it feels dramatically faster.
Kind of amazed that they didn't hold <32x32 pixmaps before. So many applications have user interface pixmaps under that size, like the minimize/maximize/close buttons of a window decoration, all the little icons on a panel, most app toolbars (including firefox), etc...
Offline
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.
Cthulhu For President!
Offline
much, much faster with my 8800 GT.
openbox, conky and my wallpaper loaded up in about half a second flat, almost feels like using a solid-state drive.
Offline
much, much faster with my 8800 GT.
openbox, conky and my wallpaper loaded up in about half a second flat, almost feels like using a solid-state drive.
Wow, I might just have to install.
Doing it now.
Edit: Hopefully, fb will be fixed on my computer. Btw, I have a 8800gt Alpha Dog card.
Last edited by haxit (2009-04-07 20:42:21)
Archi686 User | Old Screenshots | Old .Configs
Vi veri universum vivus vici.
Offline
Wow. It is faster. Next, I will try the fb.
Archi686 User | Old Screenshots | Old .Configs
Vi veri universum vivus vici.
Offline
Wow. It is faster. Next, I will try the fb.
You mean framebuffer? uvesafb or just vesafb?
Offline
haxit wrote:Wow. It is faster. Next, I will try the fb.
You mean framebuffer? uvesafb or just vesafb?
uvesafb doesn't support my res. vesafb, doesn't work i think. And yes I mean framebuffer. http://bbs.archlinux.org/viewtopic.php?id=62079
Archi686 User | Old Screenshots | Old .Configs
Vi veri universum vivus vici.
Offline
Yeah the 185.19 is faster than previous drivers but
I get the dreadful and infamous screen corruption & hang
with this and the 180.44 driver (the problems for others started
with 180.* set)
More info at nvnews.net's forums:
http://www.nvnews.net/vbulletin/showthread.php?t=123912
P.S. I haven't had the energy to try older drivers yet >.<
Last edited by Rehto (2009-04-08 11:35:43)
Offline
Wow, these new drivers do clean up the GUI experience A LOT.
Also, I just found out about yaourt,,,its awesome as well.
Offline
cant test them, because any nvidia driver > 180.29 causes several kde4 components to use 100% cpu..
any idea whats going wrong here ?
rainbow networks - we bring colour to your gibs
Offline
Really? I'm using KDEmod 4.2.2 with these new drivers and everything runs fantastic.
Offline
Really? I'm using KDEmod 4.2.2 with these new drivers and everything runs fantastic.
on i686 ? xorg 1.5.3 or 1.6 ? qt version ?
rainbow networks - we bring colour to your gibs
Offline
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...
But I must admit that 185.19 is fast, fast, fast, fast!!!
Some applications are WYSIWYG, and some are WYSIWTF.
Offline
jpe30 wrote:Really? I'm using KDEmod 4.2.2 with these new drivers and everything runs fantastic.
on i686 ? xorg 1.5.3 or 1.6 ? qt version ?
I'm using X.Org 1.6, xf86-input-evdev 2.1.3, and qtmod 4.5.0-4 on i686.
Offline
New driver not working with new kernel?
Archi686 User | Old Screenshots | Old .Configs
Vi veri universum vivus vici.
Offline
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.
Last edited by xstaticxgpx (2009-04-11 19:48:38)
Offline
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.
Offline
I have the problem that PowerMizer won't work properly with the new driver.
I enabled fixed performance on battery (lowest level = 0x3) and adaptive strategy on ac, but when running on battery the driver boosts to performance level 2...
Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x2233; PowerMizerDefault=0x3"
I followed this tutorial http://tutanhamon.com.ua/technovodstvo/ … IX-driver/
can anyone confirm the same experience?
Offline
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.
Offline
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:
Thinkpad T61p : T7700 | 4GB RAM | nVidia FX 570M | Intel 4965
Arch64 @ Openbox
Offline
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:
It won't get fixed unless you provide a bug report on the NVIDIA forums.
Offline
It won't get fixed unless you provide a bug report on the NVIDIA forums.
I had the same problem with few 177.xx versions, first releases of 180.xx, and last one - that's why i switched to beta.
However I'd post that on NVIDIA, thx for good idea.
Thinkpad T61p : T7700 | 4GB RAM | nVidia FX 570M | Intel 4965
Arch64 @ Openbox
Offline