Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 11-03-10, 08:34 PM   #25
yeknom82
Registered User
 
Join Date: Dec 2007
Posts: 3
Default Re: [260.19.12 regression] Clock changes don't work

I'll probably start a separate thread for it and post the debug log and what not when i get home....no need to hijack this thread for a separate issue.
yeknom82 is offline   Reply With Quote
Old 11-04-10, 09:33 AM   #26
artem
Registered User
 
Join Date: Jun 2006
Posts: 713
Default Re: [260.19.12 regression] Clock changes don't work

zander,

thank you again!
artem is offline   Reply With Quote
Old 11-11-10, 06:39 AM   #27
artem
Registered User
 
Join Date: Jun 2006
Posts: 713
Default Re: [260.19.12 regression] Clock changes don't work

This bug is not resolved in 260.19.21.

Who has forgotten to push the changes?
artem is offline   Reply With Quote
Old 11-11-10, 10:12 AM   #28
NvFuchs
Registered Fox
 
NvFuchs's Avatar
 
Join Date: Oct 2007
Location: Confoederatio Helvetica
Posts: 530
Default Re: [260.19.12 regression] Clock changes don't work

Quote:
Originally Posted by artem View Post
This bug is not resolved in 260.19.21.

Who has forgotten to push the changes?
Quote:
Originally Posted by zander View Post
FWIW, I debugged and fixed the NV-CONTROL overclocking interface regressions today. They should be fixed in a future 260.19.xx driver release (though likely not the next one).
emphasis added.

Fuchs
NvFuchs is offline   Reply With Quote
Old 11-11-10, 10:42 AM   #29
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: [260.19.12 regression] Clock changes don't work

Right, I didn't expect this to be fixed in 260.19.21. I'll update this bug when a BETA candidate with the fixes has been built. I can't promise anything, but I hope that this will happen in the next week or two (there are a few other fixes that need to be picked up).
zander is offline   Reply With Quote
Old 11-11-10, 11:08 AM   #30
artem
Registered User
 
Join Date: Jun 2006
Posts: 713
Default Re: [260.19.12 regression] Clock changes don't work

I'm sorry for being inattentive, NvFuchs.

Thanks for letting us know, zander!
artem is offline   Reply With Quote
Old 11-30-10, 04:20 AM   #31
artem
Registered User
 
Join Date: Jun 2006
Posts: 713
Default Re: [260.19.12 regression] Clock changes don't work

This problem is semi-fixed in 260.19.26 beta drivers, see the next messages.

Last edited by artem; 12-06-10 at 02:57 AM.
artem is offline   Reply With Quote
Old 11-30-10, 04:50 AM   #32
drhirsch
Registered User
 
Join Date: Jul 2005
Posts: 61
Default Re: [260.19.12 regression] Clock changes don't work

Unfortunately, not completely fixed.

This was done on a 8800GS with 575 MHz default core clock.

Downclocking for 2D is ok:
Code:
# nvclock -n 300
Requested core clock:           300.000 MHz

Adjusted Coolbits 2D/3D clocks on a nVidia Geforce 8800GS
Memory clock:   300.000 MHz
GPU clock:      300.000 MHz
Overclocking more than 25% does not work:
Code:
# nvclock -n 376
Requested core clock:           376.000 MHz

Adjusted Coolbits 2D/3D clocks on a nVidia Geforce 8800GS
Memory clock:   300.000 MHz
GPU clock:      300.000 MHz
But exactly 25% seems ok:
Code:
# nvclock -n 375
Requested core clock:           375.000 MHz

Adjusted Coolbits 2D/3D clocks on a nVidia Geforce 8800GS
Memory clock:   300.000 MHz
GPU clock:      375.000 MHz
Again, more than 25%:
Code:
# nvclock -n 469
Requested core clock:           375.000 MHz

Adjusted Coolbits 2D/3D clocks on a nVidia Geforce 8800GS
Memory clock:   300.000 MHz
GPU clock:      375.000 MHz
Code:
# nvclock -n 468
Requested core clock:           375.000 MHz

Adjusted Coolbits 2D/3D clocks on a nVidia Geforce 8800GS
Memory clock:   300.000 MHz
GPU clock:      468.000 MHz
Rinse and repeat until you are at the desired clock.
Using nvidia-settings yields exactly the same result.
drhirsch is offline   Reply With Quote

Old 11-30-10, 08:59 AM   #33
artem
Registered User
 
Join Date: Jun 2006
Posts: 713
Default Re: [260.19.12 regression] Clock changes don't work

So, actually, clock changes work, but a bit incorrectly and inconsistently.
artem is offline   Reply With Quote
Old 12-04-10, 04:05 PM   #34
artem
Registered User
 
Join Date: Jun 2006
Posts: 713
Default Re: [260.19.12 regression] Clock changes don't work

This issue is not fully resolved in the latest beta drivers (260.19.26):

While you can easily downclock you RAM/GPU clocks, NVIDIA driver will only allow to increase GPU clocks by ~25% increments, so jumping from 200MHz back to 650MHz is not possible without some chore (200->220->250->300->...->650).

So I have to agree with drhirsch that these beta drivers haven't fully fixed the issue.
artem is offline   Reply With Quote
Old 12-05-10, 09:26 AM   #35
hgkabde
Registered User
 
Join Date: Aug 2009
Posts: 9
Default Re: [260.19.12 regression] Clock changes don't work

Instead with little steps back to the full power of your card you can use this:

nvidia-settings -a GPUOverclockingState=0

This disable OC and the card is running with factory settings.
hgkabde is offline   Reply With Quote
Old 12-06-10, 02:56 AM   #36
artem
Registered User
 
Join Date: Jun 2006
Posts: 713
Thumbs up Re: [260.19.12 regression] Clock changes don't work

Quote:
Originally Posted by hgkabde View Post
Instead with little steps back to the full power of your card you can use this:

nvidia-settings -a GPUOverclockingState=0

This disable OC and the card is running with factory settings.
This command worked perfectly, thank you.
artem is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 07:54 PM.


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