I've run 10+ tasks on my machine with a 590 (dual GPU) and a 580. No problems at all. 320.49 driver. Should I try the 326.41 BETA driver too?

---

Reno, NV
Team: SETI.USA

7.04 all failed for my Titan

http://www.gpugrid.net/results.php?userid=5128&offset=0&show_names=0&state=0&appid=

@+
*_*

---

3 failed, and 1 completed on 780 w/ latest drivers

Is anyone seeing failure of 704 on a card that IS NOT at Titan or 780?

No failures on a GT650M (mobile, Kepler, 384 CUs), BOINC 7.0.64, driver 320.49.

Ok, thanks. Looks like we'll need two apps, CUDA 5.5 (cc 3.5 or driver > 325) and CUDA 4.2 for everything else.

Do you guys think there will be any performance improvements with 5.5?

Is anyone seeing failure of 704 on a card that IS NOT at Titan or 780?

GTX 560Ti W7 64bit driver 320.19: no failures
GTX 260 rev A.2 (65nm) W7 64bit driver 326.80: no failures! That is great.

Do you guys think there will be any performance improvements with 5.5?

Only for cc 3.5, in the sense that those cards will now work!

acemdbeta version 705 now has two variants -

* 705-55 for hosts with cc >= 1.3 and driver >=315.25

* 705-42 for hosts with cc >=1.3 and <3.5 and driver between 295.41 and 315.25.

We've had to do this because:

1) The Windows Cuda 4.2 doesn't work reliably with cc 3.5 cards, and Cuda 5.5 requires a driver too new for general deployment.

2) The cc 3.5 cards (Titan, 7xx, GT640) need the latest driver[1] to fix a stability problem.

If you have a cc 3.5 card but a driver before 315.25, you will receive NO WORK![2].

Unfortunately, Windows users with a cc 3.5 card, Windows, and driver >315.25 and < 326.41 will get work but should expect frequent crashes. If you're in this situation, please upgrade the driver.

MJH
 
[1] Currently this means only 315.25 for Linux and 326.41 for Windows
[2] Assuming the BOINC scheduler does what it's told...

7.05 OK for my TITAN.

http://www.gpugrid.net/results.php?userid=5128

I can reselect all the options preferences calculation GPUGRID my account to receive all types of units ? or must wait until the Beta units?

Great to see I finally end of the tunnel, congratulations.

GeForce 326.58
https://developer.nvidia.com/opengl-driver
Boinc 7.2.11 (x64)
http://boinc.berkeley.edu/dl/?C=M;O=D
Win 8 Pro 64
Double precision = Off


@+
*_*

---

Heading to work so can't test them, but nvidia today released driver 326.80.

Two 7.05(cuda55) downloaded and ran ok.
http://www.gpugrid.net/results.php?hostid=139142

Titan (DP off)
326.41
W7 x64
BOINC 7.2.5

Unfortunately, Windows users with a cc 3.5 card, Windows, and driver >315.25 and < 326.41 will get work but should expect frequent crashes.

MJH,

understood and IMHO good enough for beta. But can't you take the OS into the equation and send 705-55 only to Windows hosts with cc >= 1.3 and driver >=326.41?

(And 705-42 on Windows of course only to hosts with cc >=1.3 and <3.5 and driver between 295.41 and 326.41?)

I can reselect all the options preferences calculation GPUGRID my account to receive all types of units ?

Zarck,

don't think so, at least not for Titan or 780 until a Cuda 5.5 application is released for short and long runs (non-beta):

http://www.gpugrid.net/apps.php

Unfortunately, the 7.05 beta still silently fails here (http://www.gpugrid.net/forum_thread.php?id=3437). Also, my attempts to attach tracing to the short-lived process when it comes available

while true; do pid=$(pgrep -f acemd) && pstree -alcpsU $(pidof boinc) && strace64 -vfp $pid; done

are also failing:

strace64: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted

Same with

while true; do pid=$(pgrep -f acemd) && gdb -p $pid; done

GNU gdb (GDB) 7.6 (Debian 7.6-5)
This GDB was configured as "i486-linux-gnu".
Attaching to process 8561
warning: process 8561 is a zombie - the process has already terminated
ptrace: Operation not permitted.

I understand that you can not put effort into supporting each and every thinkable system, but it must be a small problem and if I'd better understand the cause it'd be easy to fix imho.
Is there the possibility to put a tiny bit more debugging output in the beta versions?

Ubuntu 13.04 64 bit Titan. 325 driver got 7.05 cuda55.

All is ok.

Dear eMPee584,

As I said in reply to your other post - you are most likely missing some important component of a normal 64-bit userspace.

If you wander off into the long grass, don't be surprised when you find snakes.

MJH

Zarck,

We'll roll this build out to the other apps once I'm satisfied that it is working correctly, after a week or so of test.

MJH

So far all WU's of ACEMD beta version v7.05 (cuda55) have been OK what I've gotten http://www.gpugrid.net/results.php?hostid=157253

I put in 2nd Titan to see if it has any effect, but so far no errors.

I'll leave the queues as they are, so the computer will keep doing beta units.

70 ACEMD beta version 7.05(cuda55) downloaded and ran ok. No errors.


7181433 4697366 20 Aug 2013 | 19:06:04 UTC 20 Aug 2013 | 19:13:31 UTC Completo e validado 66.94 61.18 150.00 ACEMD beta version v7.05 (cuda42)
7181426 4697359 20 Aug 2013 | 19:07:00 UTC 20 Aug 2013 | 19:14:29 UTC Completo e validado 64.86 61.53 150.00 ACEMD beta version v7.05 (cuda42)


GenuineIntel Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
NVIDIA GeForce GTX 680 (2048MB) driver: 320.49
Microsoft Windows 7 Home Premium x86 Edition

---

120+ beta v7.05 (cuda55) and no errors.

GTX Titan, nVidia driver 326.41, BOINC 7.2.11, Win 7 SP1 64bit