nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   [260.19.12 regression] Clock changes don't work (http://www.nvnews.net/vbulletin/showthread.php?t=156164)

artem 10-17-10 02:28 AM

[260.19.12 regression] Clock changes don't work
 
Code:

nvclock -m 300 -n 240
Requested memory clock:        300.000 MHz
Requested core clock:          240.000 MHz

Adjusted Coolbits 2D/3D clocks on a nVidia Geforce 8800GT
Memory clock:  950.000 MHz
GPU clock:      660.000 MHz

Why do you break this functionality every new release, guys?

artem 10-17-10 09:12 AM

Re: [260.19.12 regression] Clock changes don't work
 
It's actually the fourth (sic!) time this regression is being introduced.

Please, stop breaking it :)

drhirsch 10-17-10 05:33 PM

Re: [260.19.12 regression] Clock changes don't work
 
On my 8800GS (G92) i am unable to change clocks too, on each 260.* driver.

Neither nvclock nor nvidia-settings do work. 256.* was the last version which did work.

hgkabde 10-18-10 09:01 AM

Re: [260.19.12 regression] Clock changes don't work
 
Quote:

Originally Posted by artem (Post 2332961)
Why do you break this functionality every new release, guys?

May be they want to sell new graphic cards.

It seems every G92 chip is affected. I have the same problem on my GTS 250.
People with newer cards in OpenSuse forum have no problems.

artem 10-19-10 08:21 AM

Re: [260.19.12 regression] Clock changes don't work
 
Or maybe too many people work on the same code thus every time a new programmer sees something like this:

/* This needs to be fixed meanwhile it's probably safe to delete this code */

he/she eagerly erases/comments it out and we again have broken controls. :)

artem 10-20-10 06:06 PM

Re: [260.19.12 regression] Clock changes don't work
 
Aaron, Zander, has anyone noticed this report?

artem 10-22-10 03:30 AM

Re: [260.19.12 regression] Clock changes don't work
 
Is there anybody relevant here? ;)

lightmans 10-22-10 03:10 PM

Re: [260.19.12 regression] Clock changes don't work
 
i have the same problem

installed the actual nvidia driver and i can not change the overclocking values for ram and gpu

then i decided back to install the old 256.53 and nows working again.

so guys you have a bug here

artem 10-25-10 03:52 AM

Re: [260.19.12 regression] Clock changes don't work
 
Here comes the first bump.

Ulukai 10-25-10 08:01 AM

Re: [260.19.12 regression] Clock changes don't work
 
Not a solution to fix the bug, you'll need a reply from the devs for that to happen, but a permanent workaround for the problem could be flashing your card's BIOS.

Did it with my GTX 470 and I'm glad I never have to worry about my clocks again. Want to lower it again? Quickly edit your BIOS values and reflash, it only takes a couple of minutes.

artem 10-25-10 09:29 AM

Re: [260.19.12 regression] Clock changes don't work
 
Ulukai
Quote:

but a permanent workaround for the problem could be flashing your card's BIOS.
You must be new here. I know how to deal with NVIDIA developers and reflashing BIOS is absolutely not an option for me and for all other people who have this problem, because it's not a GPU problem, it's a regression in NVIDIA drivers.

Ulukai 10-26-10 06:12 AM

Re: [260.19.12 regression] Clock changes don't work
 
I know it's not a BIOS problem, it is an issue that has to be fixed in the drivers. All I'm saying is that flashing higher clock speeds to your card's BIOS is a way to always have your card running at the speeds you desire, just like you would overclock your card via driver software. It's just more permanent and imo easier to maintain.

Flashing really isn't that hard and I understand it's a risk I'm taking (concerning warranty etc) but I think it's someting to consider doing if higher clock speeds than default are important to you.

You say you know how to handle the devs, well I wish you good luck. I've been around for some time too and my experience tells me that sometimes they can simply ignore you to death. But bump all you want and I hope they will at least fix the regression.


All times are GMT -5. The time now is 05:49 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.