Is the project out of work for GPU?

Not getting Seti GPU work either but it's set to 100 resources while Asteroids is 1000 resources.
One of the 3 machines has a failing GPU (black screen o death) so set it's prefs to 999999 idle minutes and verified the server side prefs don't reflect that local choice.
Verified both GPU healthy machines are set to run GPU always.

Event log shows request for GPU work was made and 0 packets returned.

I was receiving packets about 5 days ago.

There is no difference between WUs "for CPU" and WUs "for GPU" (read also next few posts):
http://asteroidsathome.net/boinc/forum_thread.php?id=263&postid=3681#3681

Work is available now ("Tasks ready to send"):
http://asteroidsathome.net/boinc/server_status.php

Which computer?:
http://asteroidsathome.net/boinc/hosts_user.php?userid=34237

"The apps are for NVIDIA with CUDA 5.5 and Compute Capability 2.0"
http://asteroidsathome.net/boinc/forum_thread.php?id=233&postid=2227#2227

Check if your GPUs have at least 'Compute Capability 2.0':
https://developer.nvidia.com/cuda-gpus

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

Oh, the GPU's are all 1.1 compatibility.

The GPU packets received last week were from SETI and ran on the Quadro FX 2800m.

For some reason the SETI project won't d/l GPU units while I'm attached to Asteroids. I'll try pausing Asteroids and doing only SETI.

Update:
I was able to get ID: 52516 with the 2800m to run a GPU SETI unit only after I suspended Asteroids project but it is the failing GPU.

Suspending the Asteroids project on ID: 125480 with the 1600m (also 1.1 CUDA) refuses to allow a GPU unit starting.
Going to delete Asteroids and reset SETI and see if I can get GPU packets back. This machine ran them all the time a few months back.
Dragging the column headings out I notice that the 2800m machine is getting cuda23 applications but the 1600m isn't receiving any cuda23. I'll check over there for obsolescence but it's odd since both cards are 1.1 CUDA capable.

I think the problem is here:
http://setiathome.berkeley.edu/forum_thread.php?id=75633

Drivers post 340.52 are causing calculation errors. Going to drop back the driver versions and see if the problem is fixed.

Website won't let me edit the last post so another new message...

You can see that, finally, the machine is on an older version of nVidia drivers, and still not getting packets. Even increased the SETI resource slice but no luck.

Going to sleep on it and try again later.

Website won't let me edit the last post so another new message...

You can see that, finally, the machine is on an older version of nVidia drivers, and still not getting packets. Even increased the SETI resource slice but no luck.

Going to sleep on it and try again later.

Your gpu do NOT have 2.0 compatibility, that means that no matter how much you try they just won't work here. It is a project decision and I see you asked why in another thread, an Admin should be able to answer that.

Website won't let me edit the last post so another new message...

You can see that, finally, the machine is on an older version of nVidia drivers, and still not getting packets. Even increased the SETI resource slice but no luck.

Going to sleep on it and try again later.

Your gpu do NOT have 2.0 compatibility, that means that no matter how much you try they just won't work here. It is a project decision and I see you asked why in another thread, an Admin should be able to answer that.

Yeah, I was posting that for BilBg (or anyone else running SETI) since he and I both run SETI packets. It seems pretty clear I was referring to SETI GPU units; sorry for the confusion.

If the fact I was attached to Asteroids and it was preventing me from getting SETI GPU packets, happened to be the case (you can see this if you read further up the thread), then it would still involve Asteroids or the BOINC software. Since I finally got a GPU work unit today, this isn't in the troubleshooting decision path anymore.

So obviously it's a SETI@Home issue and posting over there about it now.
There's many nVidia drivers that have had problems and trying to find a driver blacklist.

Just for info: SETI@home accepts my NVIDIA GeForce 8400 GS (511MB) driver: 266.58
which is probably/almost the lowest GPU that have CUDA
http://setiathome.berkeley.edu/show_host_detail.php?hostid=7396088

I run SETI@home v7 CUDA apps (CUDA 3.2 is 2-3% faster on this GPU than CUDA 2.3) using app_info.xml from the Lunatics installer

P.S.
CUDA and Compute Capability versions are not the same thing
Here they want "CUDA 5.5 and Compute Capability 2.0"

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

Just for info: SETI@home accepts my NVIDIA GeForce 8400 GS (511MB) driver: 266.58
which is probably/almost the lowest GPU that have CUDA
http://setiathome.berkeley.edu/show_host_detail.php?hostid=7396088

I run SETI@home v7 CUDA apps (CUDA 3.2 is 2-3% faster on this GPU than CUDA 2.3) using app_info.xml from the Lunatics installer

Which of these drivers listed in my last message (http://setiathome.berkeley.edu/forum_thread.php?id=75978&postid=1593087#1593087) should I go with? The machine received a cuda unit but someone claims the driver I installed also caused math errors. 266.58 is not available for Quadro but 266.45 and 267.79 from the same era are available.

I also have 259.57, 305.93 and 306.97 d/l so far. A blacklist or whitelist chart would be great!

P.S.
CUDA and Compute Capability versions are not the same thing
Here they want "CUDA 5.5 and Compute Capability 2.0"

Oops, I can't edit that message to correct my mistake nor delete the message.
I was working without sleep at 5am then.