Arch Linux

Gauvenator

Member

Registered: 2008-04-03

Posts: 172

Nvidia 173.14

Sooo has anyone tried the new nvidia drivers in testing?  I'm curious if on 8 series gpus it will fix the stuttering in compiz fusion.

DeeCodeUh

Member

From: Michigan, USA

Registered: 2007-11-27

Posts: 176

Re: Nvidia 173.14

I'm currently using it.
I have an 8400M in my laptop, and compiz fusion is running a world better with this new driver.
You really should use it. HUGE DIFFERENCE FOR ME.

Kane

Member

Registered: 2006-10-08

Posts: 220

Re: Nvidia 173.14

im getting this error when i try to make it:

The nvidiafb driver conflicts with the NVIDIA driver, please
reconfigure your kernel and *disable* nvidiafb support, then
try installing the NVIDIA kernel module again.

when i know i havnt got nvidiafb as ive compiled my own kernel.

DeeCodeUh

Member

From: Michigan, USA

Registered: 2007-11-27

Posts: 176

Re: Nvidia 173.14

Did you use the ABS when you compiled your kernel?

MAC!EK

Member

Registered: 2005-09-27

Posts: 267

Re: Nvidia 173.14

On my Lenovo Thinkpad R61 new nvidia drivers solved the suspend and hibernate problem.
I tested it now and both work with pm-suspen/hibernate.

GGLucas

Member

Registered: 2008-03-13

Posts: 113

Re: Nvidia 173.14

.

Last edited by GGLucas (2022-06-24 09:05:37)

DeeCodeUh

Member

From: Michigan, USA

Registered: 2007-11-27

Posts: 176

Re: Nvidia 173.14

That's strange...I've used the ABS to compile the beta kernel to remove some drivers that conflicted with others, as well as the beta nvidia drivers, and everything works really well.

krigun

Member

From: Norway

Registered: 2005-06-06

Posts: 122

Website

Re: Nvidia 173.14

Trying to use it (binaries, as well as compiled through abs) brings down the entire system, black screen with no switching out to VT or killing X, I suspect kernel panic.
It also tells me something about nvidia.ko being the wrong format during boot :S

Yeah, me too. Screen goes black (system still reboots with CTRL-ALT-DEL). Installed the nvidia-173.14.05 and nvidia-utils-173.14.05.

Xorg.0.log displays the following:

(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): ACPI display change hotkey events enabled: the X server is new
(II) NVIDIA(0):     enough to receive ACPI display change hotkey events.
(II) NVIDIA(0): Setting mode "1920x1200"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX

Backtrace:
0: X(xf86SigHandler+0x7e) [0x80e39de]
1: [0xb7f35400]
2: X(main+0x2e5) [0x8073d35]
3: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7cf5396]
4: X(FontFileCompleteXLFD+0x211) [0x80731f1]

Fatal server error:
Caught signal 11.  Server aborting

Kane

Member

Registered: 2006-10-08

Posts: 220

Re: Nvidia 173.14

Did you use the ABS when you compiled your kernel?

No, i used the traditional method.

Gauvenator

Member

Registered: 2008-04-03

Posts: 172

Re: Nvidia 173.14

Is it stable for you all?

If I do decide to use it should I ABS or just use the traditional method to install?

Gauvenator

Member

Registered: 2008-04-03

Posts: 172

Re: Nvidia 173.14

OK I went ahead and tried it and it makes compiz-fusion smoother and tab switching in firefox better.  If anyone wants to know, I installed it from the testing repo.

I've reverted back to 169 just because I don't know if 173 is stable.  At least it worked tho   Thanks for the input.

Kane

Member

Registered: 2006-10-08

Posts: 220

Re: Nvidia 173.14

i dont know how it fixed it but after reinstalling my cutom kernel, it worked.

Edit:
It was because i didnt have the kernel sources in my home directory (where the kernel was built)

Is there anyway to prevent this, without needing the kernel in my home dir, is it possible to move it to /usr/src after building or something?
How does the nvidia installer know the source should be in my home dir?

Last edited by Kane (2008-05-30 09:02:26)

GGLucas

Member

Registered: 2008-03-13

Posts: 113

Re: Nvidia 173.14

Trying to use it (binaries, as well as compiled through abs) brings down the entire system, black screen with no switching out to VT or killing X, I suspect kernel panic.
It also tells me something about nvidia.ko being the wrong format during boot :S

Yeah, me too. Screen goes black (system still reboots with CTRL-ALT-DEL). Installed the nvidia-173.14.05 and nvidia-utils-173.14.05.

Xorg.0.log displays the following:

(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): ACPI display change hotkey events enabled: the X server is new
(II) NVIDIA(0):     enough to receive ACPI display change hotkey events.
(II) NVIDIA(0): Setting mode "1920x1200"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX

Backtrace:
0: X(xf86SigHandler+0x7e) [0x80e39de]
1: [0xb7f35400]
2: X(main+0x2e5) [0x8073d35]
3: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7cf5396]
4: X(FontFileCompleteXLFD+0x211) [0x80731f1]

Fatal server error:
Caught signal 11.  Server aborting

Yeah, I get a backtrace and signal 11 too
Did you have any luck finding a way to fix this ? I'd like to use the new glyph cache.

(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6a) [0x4a035a]
1: /lib/libc.so.6 [0x7fa40fab7ec0]
2: /usr/lib64/tls/libnvidia-tls.so.1 [0x7fa40d8e067e]

Fatal server error:
Caught signal 11.  Server aborting

Is what I get.

krigun

Member

From: Norway

Registered: 2005-06-06

Posts: 122

Website

Re: Nvidia 173.14

Yeah, I get a backtrace and signal 11 too
Did you have any luck finding a way to fix this ? I'd like to use the new glyph cache.

Unfortunately not; it was so frustrating to test since it freezed the display until I rebooted, so I reverted to the old drivers.

Ink-Jet

Member

From: London

Registered: 2008-03-27

Posts: 64

Website

Re: Nvidia 173.14

It works fine for me, and seems to have stopped my random freezing problem I was having.

Bapman

Member

From: Ottawa, Canada

Registered: 2007-09-02

Posts: 140

Re: Nvidia 173.14

OK I went ahead and tried it and it makes compiz-fusion smoother and tab switching in firefox better.  If anyone wants to know, I installed it from the testing repo.

I've reverted back to 169 just because I don't know if 173 is stable.  At least it worked tho   Thanks for the input.

This is the new stable driver from Nvidia !

Compiz is smoother too here with my 8400m, for cube rotation for example. But some other stuff like resizing windows are still soooooo slow !

INCSlayer

Member

From: Sweden

Registered: 2007-09-06

Posts: 296

Website

Re: Nvidia 173.14

resizing is MUCH better on my 9600gt with the new drivers but they still stutter alot

---

dovie andi se tovya sagain

Gauvenator

Member

Registered: 2008-04-03

Posts: 172

Re: Nvidia 173.14

OK I went ahead and tried it and it makes compiz-fusion smoother and tab switching in firefox better.  If anyone wants to know, I installed it from the testing repo.

I've reverted back to 169 just because I don't know if 173 is stable.  At least it worked tho   Thanks for the input.

This is the new stable driver from Nvidia !

Compiz is smoother too here with my 8400m, for cube rotation for example. But some other stuff like resizing windows are still soooooo slow !

Why is it in the Testing repo then?

kumico

Member

Registered: 2007-09-28

Posts: 224

Website

Re: Nvidia 173.14

because like every other pkg it needs testing (refer to previous posts in this thread(i.e 'Signal 11, etc'))

Last edited by kumico (2008-05-31 06:30:50)

GGLucas

Member

Registered: 2008-03-13

Posts: 113

Re: Nvidia 173.14

Has this been fixed yet ? I'd like to switch to the new nvidia drivers but I can't do that if they make it crash..

jacko

Member

Registered: 2007-11-23

Posts: 840

Re: Nvidia 173.14

Has this been fixed yet ? I'd like to switch to the new nvidia drivers but I can't do that if they make it crash..

patience is a virtue... at least nvidia is trying to fix known bugs, what else can you ask of them?

klixon

Member

From: Nederland

Registered: 2007-01-17

Posts: 525

Re: Nvidia 173.14

i dont know how it fixed it but after reinstalling my cutom kernel, it worked.

Edit:
It was because i didnt have the kernel sources in my home directory (where the kernel was built)

Is there anyway to prevent this, without needing the kernel in my home dir, is it possible to move it to /usr/src after building or something?
How does the nvidia installer know the source should be in my home dir?

This is possible, but you have to update two symlinks in your /lib/modules/${kernver} directory. This is also how the nvidia-installer knows the location of the tree you used to build the running kernel. The symlinks are called "build" and "source"

---

Stand back, intruder, or i'll blast you out of space! I am Klixon and I don't want any dealings with you human lifeforms. I'm a cyborg!

DanielW

Member

Registered: 2008-01-27

Posts: 23

Re: Nvidia 173.14

There is still the very poor 2D perfomance with series 8 cards :-(

On my Geforce 8600m-gt I have a lot faster 2D with plain Vesa.   (i can proof that with gtkperf). It is even worse in QT4. 

I have to use KDE4 with vesa driver.

Here some benchmarks an other kde (and arch) user has done:  (i hope he is fine with me posting it here)

The numbers there are seconds (so low numbers are good).

"I recently "upgraded" my graphics card from 7300GT to 8600GT.  I plugged in my
old card and did some benchmarking with gtkperf:

$ gtkperf -a -c 100

8600GT - nv:   13.xx
8600GT - nvidia:  13.xx
8600GT - vesa  6.xx

7300GT - nv:   13.xx
7300GT - nvidia:  6.xx
7300GT - vesa  6.xx"

That is sooo bad. It forces me to use vesa driver. And that means: No Hardware 3D. No google earth, no marbe and so on..

And as that is a notebook i can not even by me a new graphic card. Even my Eee is faster on kde4.

I hope nvidia can fix that in the next months.

DanielW