I put some power on GPU Grid so DNet is just rumbling along now. Waiting for some Simap tasks on July 1.
Printable View
I put some power on GPU Grid so DNet is just rumbling along now. Waiting for some Simap tasks on July 1.
Congrats vaughan on 25,000,000 credits! :icon_thumright:
I hope you forgive me for this, I hate to be a spoiler, but I love to see a good race going... :icon_mrgreen:
Liuqyn, you better start your engines again if you want to keep your #1 spot, vaughan is right on your tail... just a million credits away from you! :icon_razz:
Ya, I see ya coming, But I'm busy working on 100M on collatz. so go ahead and pass me, FOR NOW
Geez... These GPU projects are killing my BAM stats. I had to earn the 3,650,224 the hard way!! :lol:
I'll never catch up!!! :sad5:
It seems DNETC has swallowed a fur ball. Somethings up my systems will not download any new work units and everything keeps banging away at telling me CUDA 3.1 is needed. What the heck is that? Then when researching what the heck is going on, the Server for the web site goes down. Ah Rats.....
Hmm. It didn't so much swallow a fur ball as cough one up.
PS - the site is back up.
Yes.
They provided a new upgraded the client with a minimum CUDA driver version 25x.x and higher.
BUT the existing CUDA 2.3 is also still valid.
I have tested that this 2.3 app is still available: Linux_AMD64 is anyway
I am not sure why your machine has deferred to the 3.1 client unless your driver compatible with that version but there is a client-app compile problem.
e.g. the new client deos not defer back to the old client if the new client fails to work.
I can't recall ever seeing two client apps for the same base architecture on any project (regardless of GPU version).
They have managed it well so far.
But it is not surprising that they would run into a problem with this eventually.
Scan the project forums.
If anyone else is having the same problem I am sure we will hear more about it very soon.