Nvclock 0.8B3 released, with Geforce 8 support

[dsio]

A new version of the NVclock Nvidia overclocking application for Linux has been released, this time with support for Geforce 8 GPUs:

NVClock - Nvidia overclocking on Linux!

This might be a big thing for Daniel among others, as it brings overclocking to users of newer GPUs.

There is no Fedora RPM at present, so it must be compiled by source.

[dsio]

I just noticed, that the author is now supporting it under Fedora and says it will soon be added into Fedora 8's official repos, this means that soon you will just be able to do a 'yum install nvclock' and have it install on its own direct from fedora, ready to go.

[dsio]

Just checked, and it in fact IS IN the fedora repos now

To install nvclock, su to root and type:

yum install nvclock nvclock-gtk

Its possible that you /may/ have to upgrade to the new nvidia 167.xx drivers to get GF8 OC working, but it might work as is as well.

[ccperf721p]

It's been awhile since I have heard anything about nvclock, I had forgot all about it. The Beta3 is not in portage as of yet, did not find any 3rd party ebuilds in a quick search so I built from source.

Thanks for the heads up dsio..

[Daniel ~]

By way of a thank you!":O}

[Daniel@dhcppc1 ~]$ su
Password:
[root@dhcppc1 Daniel]# yum install nvclock nvclock-gtk
livna 100% |=========================| 2.1 kB 00:00
primary.sqlite.bz2 100% |=========================| 146 kB 00:01
fedora 100% |=========================| 2.1 kB 00:00
adobe-linux-i386 100% |=========================| 951 B 00:00
updates 100% |=========================| 2.3 kB 00:00
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package nvclock-gtk.x86_64 0:0.8-0.3.b3a.fc8 set to be updated
---> Package nvclock.x86_64 0:0.8-0.3.b3a.fc8 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================== ===========================
Package Arch Version Repository Size
================================================== ===========================
Installing:
nvclock x86_64 0.8-0.3.b3a.fc8 updates 60 k
nvclock-gtk x86_64 0.8-0.3.b3a.fc8 updates 212 k

Transaction Summary
================================================== ===========================
Install 2 Package(s)
Update 0 Package(s)
Remove 0 Package(s)

Total download size: 272 k
Is this ok [y/N]: y
Downloading Packages:
(1/2): nvclock-0.8-0.3.b3 100% |=========================| 60 kB 00:00
(2/2): nvclock-gtk-0.8-0. 100% |=========================| 212 kB 00:01
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing: nvclock ######################### [1/2]
Installing: nvclock-gtk ######################### [2/2]

Installed: nvclock.x86_64 0:0.8-0.3.b3a.fc8 nvclock-gtk.x86_64 0:0.8-0.3.b3a.fc8
Complete!
[root@dhcppc1 Daniel]#

[Daniel ~]

Have no idea why but can't change the settings and have them stick, keeps reverting to defaults... Not a big thing at the moment and I'm unsure if it's "Them or me".

But it installed rather nicely! ":O}

[dsio]

I believe its designed that way as a failsafe, it resets on reboot.

[Daniel ~]

No, I mean I change a setting and close, reopen and it's at default again. I've done some more checking...other settings stick! Only the O/C fuction reverts.

This isn't something I'd ask you to spend your valuable time on. I'm mostly PS3 these days and I have a hunch that the creator will right things soon...if it's them rather than me, that is.":O}

Very much appreceate your posting this! ":O}

[dsio]

Hmmm...

I would advise to check the "test speeds before applying" box, and then are you setting sliders and leaving it?

Or are you setting the sliders and THEN clicking the "change speeds" button?

because its a bit weirdly named, but "change speeds" really means "apply"

<edit> btw when I try using this, it scrambles my screen... but I'm getting artifacts when playing games at stock, and am running above 95C core temps so I'm not surprised. Think my much loved 6800GT has just started coughing up blood.

[Daniel ~]

OK then! Box is checked. I move the sliders to a very modest O/c...just seeing and making sure it's not a failed O/c causing problems....

When I hit the Change speed button two things happen:
1. the sliders revert to default,
2. at the same time a box pops up and asks if the change is OK, which it is as there is no change now, so I say yes.

fortunately no problems in quake 4. with nclock installed..but then, I'm not over clocked now am I? LOL

[dsio]

hmmmmm

hmmmmm

hmmmmm

It could be that you need the new Nvidia beta drivers.

Not in livna at the moment though...

Well let me think about this problem a bit. I might even email the developer and see what he thinks (one of the perks of open source is that you /can/ email the devs and say "hey I'm wondering if you can help me")

It does install correctly though, so the glass is half full!

[Daniel ~]

And other settings are useful! (You can tell him I said that, don't want to ruin his whole day...unless you think that will help? ":O}

Dsio? Do you remember back a ways I was having problems with saving my monitor settings in X server settings? The "Save to X configuration file" Couldn't save and I'd get this message

"Unable to remove old X config backup file '/etc/X11/xorg.conf.backup'.

Well since updating to Fedora 8, I have the same problem, but, it was actually keeping my setting where I wanted them, so didn't bother over it. Now I'm wondering if this may have something to do with being unable to save O/c settings?

[dsio]

Na mate its a different thing, I'm sure of it.

[Daniel ~]

Just checking":O}

[ccperf721p]

I'm not at a rig with Fedora so I can't check for right files and such, if you could Daniel, run this and see if the file exists for me. If so I can throw a few lines that will boot with your overclocked settings..

Run as normal user

 less .nvidia-settings-rc

[Daniel ~]

WAIT! LOL! Make it a minor O/c...Really all I'm runing is occasional Quake4, no sense in stressing over Quake 4. Also, how will this effect the nclock apt, will it be assessable once fixed?

#
# /home/Daniel/.nvidia-settings-rc
#
# Configuration file for nvidia-settings - the NVIDIA X Server Settings utility
# Generated on Wed Jan 9 13:55:53 2008
#

# ConfigProperties:

RcFileLocale = C
ToolTips = Yes
DisplayStatusBar = Yes
SliderTextEntries = Yes
IncludeDisplayNameInConfigFile = Yes
ShowQuitDialog = No
Timer = PowerMizer_Monitor_(GPU_0),Yes,1000
Timer = Thermal_Monitor_(GPU_0),Yes,1000

# Attributes:

dhcppc1:0.0/DigitalVibrance[DFP-1]=0
dhcppc1:0.0/SyncToVBlank=0
dhcppc1:0.0/AllowFlipping=1


also seems to do strange things to the terminal...can't scroll back up...just saying...':O}

[Daniel ~]

WHOAH!
Very strange! I started to type Exit (Habit I was just a user":O} and suddendly this jumped out!

#
# /home/Daniel/.nvidia-settings-rc
#
# Configuration file for nvidia-settings - the NVIDIA X Server Settings utility
# Generated on Wed Jan 9 13:55:53 2008
#

# ConfigProperties:

RcFileLocale = C
ToolTips = Yes
DisplayStatusBar = Yes
SliderTextEntries = Yes
IncludeDisplayNameInConfigFile = Yes
ShowQuitDialog = No
Timer = PowerMizer_Monitor_(GPU_0),Yes,1000
Timer = Thermal_Monitor_(GPU_0),Yes,1000

# Attributes:

dhcppc1:0.0/DigitalVibrance[DFP-1]=0
dhcppc1:0.0/SyncToVBlank=0
dhcppc1:0.0/AllowFlipping=1
dhcppc1:0.0/LogAniso=0
dhcppc1:0.0/FSAA=0
dhcppc1:0.0/TextureSharpen=1
dhcppc1:0.0/ForceGenericCpu=0
dhcppc1:0.0/GammaCorrectedAALines=1
dhcppc1:0.0/CursorShadow=1
dhcppc1:0.0/CursorShadowXOffset=4
dhcppc1:0.0/CursorShadowYOffset=2
dhcppc1:0.0/CursorShadowAlpha=64
dhcppc1:0.0/CursorShadowRed=0
dhcppc1:0.0/CursorShadowGreen=0
dhcppc1:0.0/CursorShadowBlue=0
dhcppc1:0.0/FSAAAppControlled=1
dhcppc1:0.0/LogAnisoAppControlled=1
dhcppc1:0.0/GPUScaling[DFP-1]=131073
dhcppc1:0.0/FSAAAppEnhanced=0
dhcppc1:0.0/RedBrightness=0.000000
dhcppc1:0.0/GreenBrightness=0.000000
dhcppc1:0.0/BlueBrightness=0.000000
dhcppc1:0.0/RedContrast=0.000000
dhcppc1:0.0/GreenContrast=0.000000
dhcppc1:0.0/BlueContrast=0.000000
dhcppc1:0.0/RedGamma=1.000000
dhcppc1:0.0/GreenGamma=1.000000
dhcppc1:0.0/BlueGamma=1.000000
dhcppc1:0.0/OpenGLImageSettings=0
dhcppc1:0.0/XVideoTextureBrightness=0
dhcppc1:0.0/XVideoTextureContrast=4096
dhcppc1:0.0/XVideoTextureSyncToVBlank=1
dhcppc1:0.0/XVideoSyncToDisplay=131072
~
~
~
~
(END)

[ccperf721p]

less is what's known as a pager, it will just show you the output of a file. Sorry, should have mentioned. Hit "q" to exit..

I promise not to blow up your card. You get to pick your own frequencies.. You will not need nvclock after this, unless you need it for fan control..

Once you determine the OC you want to run, open up a terminal and:

 sudo nano -w .nvidia-settings-rc

Then insert these lines. The format is easy as you can see. I'm using the stock clocks for my 8800GTS adjust to fit your card. Add anywhere, I usually put it at the top so it easy to change..

GPUOverclockingState=1
GPU2DClockFreqs=513,792
GPU3DClockFreqs=513,792

If you are not familiar with nano, hit CTRL+x to exit, it will ask if you are sure, hit y then enter..

[Daniel ~]

Easy it may be, but this is me your trying to help! ":O}

eveything looks stright forward...But I'd like a better understanding of the settings...

GPUOverclockingState=1
GPU2DClockFreqs=513,792
GPU3DClockFreqs=513,792

Can you explain what these numbers come from what one would do to increase or decrease the amount of O/c? I did get the 2D 3 D thing...I am trying! ":O}

[ccperf721p]

You are not in as bad a shape as you think.. Given the time frame you are moving quite fast.. I am still trying to break old habits and get used to the ease of recent Linux. I will still open a terminal to move a folder from one place to another when I could just copy and paste..

GPUOverClockingState= 1 is on and you can change clock speeds, 0 is off and it will always boot with stock speeds..
GPU"2D/3D"ClockFreqs= the first is core clock, the second is memory clock.

NVClock will give you the stock speeds and allow you to test OC settings, but since it doesn't save them it doesn't do a whole lot of good. Setting them in the rc file will apply them when the driver loads.

After setting the clocks and saving them in the rc file, you will need to log out and back in for the settings to take effect. CTRL+ALT+Backspace, then log back in..