Xubuntu 12.04 UP-TO-DATE (Linux 3.2.0.24 (AMD64)
Boinc 7.0.27 (X86)
Driver 295.40
GTX 590

I just noticed that Boinc 7.0.27 from advanced distribution is a beta x86 version and not an x64 one .
Does it make a difference for Beta tasks ?
Normal and Long runs seem to run OK with this version of Boinc.
How can I obtain an x64 version of Boinc for ubuntu ?
Wher ecan I obtain the 295.49 version of the driver ?

---

Lubuntu 16.04.1 LTS x64

Wher ecan I obtain the 295.49 version of the driver ?

geforce.com

For example, even though NVIDIA says their stock boost frequency is 1058, mine came out of the box at 1110.

There's not a single boost clock. It actually goes up in fine increments, depending on conditions. The number quoted by nVidia is the average you can expect, measured using many games and settings. The actual boost clock depends on temperature and power consumption - which both depend on chip quality, as well as the executed code.

MrS

---

Scanning for our furry friends since Jan 2002

Well, i think that nvidia-settings doesn't FULL support GTX680
I have 4 levels in nvidia-settings (0 to 3) the levels 2 and 3 are at the same clock.

I tried the coolbits option but the only thing i can change is the fan speed.

BTW, my GTX 680 is an EVGA SC+

I am certain the GTX680 isn't fully supported by the drivers yet; otherwise there would not be driver updates, and there always are. Most of these updates improve specific functions often in an attempt to improve performance on certain games, but occasionally the updates bring additional CUDA capabilities or improved CUDA performances. It's also possible that actual speeds aren't reported correctly!

EVGA say your cards boost is 1124MHz, which is reasonably high.

The purpose of suggesting you use the coolbits option to increase fan speeds was to reduce the chance of downclocking due to overheating or using too much power (cooling can reduce the power/voltage required).

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Xubuntu 12.04 UP-TO-DATE (Linux 3.2.0.24 (AMD64)
Boinc 7.0.27 (X86)
Driver 295.40
GTX 590

I just noticed that Boinc 7.0.27 from advanced distribution is a beta x86 version and not an x64 one .
Does it make a difference for Beta tasks ?
Normal and Long runs seem to run OK with this version of Boinc.
How can I obtain an x64 version of Boinc for ubuntu ?
Wher ecan I obtain the 295.49 version of the driver ?

The app being tested here is,
ACEMD beta version 6.43 x86_64-pc-linux-gnu (cuda42)

I know that a 32bit client does allow 64bit CPU apps to work on 64bit Windows, but I'm not sure about a 32bit client supporting a 64bit GPU app on Linux?

We are testing Beta apps on Beta clients using untested OS with immature drivers!

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

LOL. Got a good chuckle out of that one. Ah being on the front line!!!

Well, i think that nvidia-settings doesn't FULL support GTX680
I have 4 levels in nvidia-settings (0 to 3) the levels 2 and 3 are at the same clock.

I tried the coolbits option but the only thing i can change is the fan speed.

BTW, my GTX 680 is an EVGA SC+

I am certain the GTX680 isn't fully supported by the drivers yet; otherwise there would not be driver updates, and there always are. Most of these updates improve specific functions often in an attempt to improve performance on certain games, but occasionally the updates bring additional CUDA capabilities or improved CUDA performances. It's also possible that actual speeds aren't reported correctly!

EVGA say your cards boost is 1124MHz, which is reasonably high.

The purpose of suggesting you use the coolbits option to increase fan speeds was to reduce the chance of downclocking due to overheating or using too much power (cooling can reduce the power/voltage required).

Well, i tried to increase fan rotation to decrease GPU temp but no effect still stuck @ 705
Anyway GPU temp is low 78°c and Fan @ 55% with my other GTX580 i was @ 63% and 86°c
So, i tried to use nvidia Beta drivers (302.07) no more success, GPU clock still @ 705 Mhz according to nvidia-settings
For your information the Beta work failed with this driver

Wdiz wrote:

The values i have in nvidia-settings are :
Graphics clock : 705 Mhz
Memory clock : 3104 Mhz
Processor clock : 1411 Mhz

This looks almost certainly like nvidia-settings doesn't know about your card. Kepler doesn't have a "hot clock", i.e. doesn't run the shaders at 2x the GPU core speed any more. 705 MHz and 1411 MHz is a factor of 2, so I suppose 1411 is not your CPU speed, but rather the shader clock the tool would report for Fermi cards.

This fits initial Kepler rumors, where the clock speed was reported as ~700 MHz, instead of the actual shipping 1 GHz.

MrS

---

Scanning for our furry friends since Jan 2002

Kepler throttles at both 70 and 80C, but not by that much. Yours is not at 700, you should increase fan though, probably to 65-70%

Here is a pic from NVIDIA forums to show the throttling in action:

Note that the fan remained at 30% throughout - well, except for the early blip.
When the temps reached about 70°C the card was throttled - You can see a slight Voltage and core clock drop at around 70°C, before the Voltage was 1.162V.

Any benchmarks that fail to manage the fans/temps should be completely dismissed as amateurish. Anyone that runs a 28nm GPU so hot (70°C+), with low fan speeds, doesn't know what they're doing!

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Clearly.

They were just showing the throttling in action for this pic. Quite a few discussions on NVIDIA forums about how GPU boost is a bad idea, and how NVIDIAs "stock" fan profile is horrendous. But as I stated, they just wanted to see what sort of throttle was being applied.

Also, why NVIDIA chose 70C and 80C. Sine 70C is not all that hot for gamers (think if Fermi throttled at 70C), for those who don't adjust profiles anyways. Probably should have been like 80 and 85

Like Intel, they seem to be making more products for people that have no idea what they're doing. "Dude did you see how much better their IGP is!!" LOL

Like Intel, they seem to be making more products for people that have no idea what they're doing.

Thats one recipe for success. It worked very well for Gates and Jobs.

Anyway, the beta app runs fine here on my GTX 570 and Linux though I had one heck of a time updating to the 295.40 driver. It and the 295.49 driver hosed my X server about 7 times before I learned you have to suck on a red M&M while installing, not a blue one. How does it know I hate the red ones?

(my machine never sleeps/hibernates so I won't be affected by the bug)

lol, very true.

Nice run times by the way. Stock clocks?

Thanks.

I have to admit I don't know if the clocks are stock or not. I have never OC'd it but I think Asus may have? The nvidia-settings utility says:

Graphics: 742 MHz
Memory: 1900 MHz
Processor: 1484 MHz
PCIe link width: x16
PCIe Link Speed: 5.0 GT/s
Fan Speed: 85%
Temp: 41 C

It's on a low end Asus P8 H67-M EVO mobo.

The temp is pretty low because the machine is outdoors and it's about 12 C outdoors right now (evening). It'll get up to 58 or 60 C in the daytime.

It runs on Linux which I have heard runs the science app faster than Windows. Maybe that's what gives the nice run times. It makes up for other projects whose app runs slower on Linux.

Just a driver note:
Boinc 7.0.26(x64) reports that my NVidia 295.73 driver for Windows supports CUDA4.2,
GeForce GTX 470 (driver version 295.73, CUDA version 4.20, compute capability 2.0, 1280MB, 1203MB available, 1219 GFLOPS peak)

however NVidia Control Panel says,
NVCUDA.DLL 6.14.12.9573 NVIDIA CUDA 4.1.1 driver

Control Panel also said the 296.10 driver was CUDA 4.1.1.

The 301.24 driver is reported as being 4.2.1 by NVidia but as 4.20 by Boinc.
Ditto for the 301.32 driver (which causes my monitor to auto-adjust repeatedly).

Same with Boinc 7.0.27(x64)
GeForce GTX 470 (driver version 301.32, CUDA version 4.20, compute capability 2.0, 1280MB, 1174MB available, 1219 GFLOPS peak)
OpenCL: NVIDIA GPU 0: GeForce GTX 470 (driver version 301.32, device version OpenCL 1.1 CUDA, 1280MB, 1174MB available)

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

You're seeing weird version numbers too, huh? I tried installing the 295.49 drive on Linux and when I rebooted I got:

ERROR: API mismatch: the NVIDIA kernel module has version 295.40, but this NVIDIA driver component has version 295.49

The boot stopped dead at that point.

Seems like NVIDIA got some version numbers wrong or something. Another odd thing is that their site claims the Linux 295.49 driver is more recent than the 302.07. The former is dated May 3/12, the latter May 2/12 according to http://www.nvidia.com/object/linux_amd64_display_archive.html. It shakes my confidence in them to the point where I'll stay with 295.40, which is good enough for the beta app, until the next driver release.

Same at GeForce:

Version 295.49
Release Date Thu May 03, 2012
Operating System Linux 64-bit
Language English (US)
File Size 55.81 MB

Maybe they mixed up 05/03/2012 with 03/05/2012 (US vs UK), or they went back to 295.40 and made an update to that release version?

I used the Ubuntu repository version 295.40 and the same for Boinc (7.0.24 running as a daemon). It worked, despite the black screens and resets, so I'm leaving good enough alone.

- Actually, 302.07 is a Beta while 295.49 is a standard release.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

It worked, despite the black screens and resets, so I'm leaving good enough alone.

I'm not sure where you're getting black screens and needing resets. Are you aware there is a problem with BOINC 7.0.24 from Ubuntu 12.04 repository? Could that be causing the black screens? A temporary solution is given in http://setiathome.berkeley.edu/forum_thread.php?id=67864&nowrap=true#1229806. Their 7.0.27 works fine here.

I upgraded from 11.10 and had to reinstall the driver (Ubuntu repo). When I rebooted it went to a black screen a few times, restarted itself a couple of times and I had to manually click the reset button a few times. I've installed updates since then, and I might have removed the driver and reinstalled it again (this fixed similar issues in the past). All seems to be well for now, so I will leave it be, but if things start playing up again I will apply said fix, thanks.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

A first tentative version for windows is out.

Let's see if it works.

gdf