Periodically I have no CUDA work. Typically for two or more weeks.
I don't no why. It seems there is nothing wrong.
Yesterday SETI said:
Ter 10 Jan 2012 14:15:29 WET | SETI@home | Sending scheduler request: To fetch work.
Ter 10 Jan 2012 14:15:29 WET | SETI@home | Requesting new tasks for NVIDIA GPU
Ter 10 Jan 2012 14:15:42 WET | SETI@home | Scheduler request completed: got 0 new tasks
Ter 10 Jan 2012 14:15:42 WET | SETI@home | No tasks sent
Ter 10 Jan 2012 14:15:42 WET | SETI@home | No tasks are available for SETI@home Enhanced
Today:
Qua 11 Jan 2012 13:21:48 WET | SETI@home | Requesting new tasks for NVIDIA GPU
Qua 11 Jan 2012 13:21:52 WET | SETI@home | Scheduler request completed: got 0 new tasks
Qua 11 Jan 2012 13:21:52 WET | SETI@home | No tasks sent
Qua 11 Jan 2012 13:21:52 WET | SETI@home | No tasks are available for SETI@home Enhanced
But also:
03-Jan-2012 09:55:26 [SETI@home] Sending scheduler request: To fetch work.
03-Jan-2012 09:55:26 [SETI@home] Requesting new tasks for NVIDIA GPU
03-Jan-2012 09:55:30 [SETI@home] Scheduler request completed: got 0 new tasks
03-Jan-2012 09:55:30 [SETI@home] Project has no tasks available
This time the problem began before Xmas.

---

Snap but they've just kicked in a few mins ago. I think part of the 'problem' is that I've spent a few days with HT on so the number of threads has doubled, so the server-side limits need time to adjust to this.

i am getting hundreds of them

:)

went to 6.10

I don't believe that Linux supports SETI/CUDA out of the box (though I could be wrong) but take a look at the Linux x64 Cuda Multibeam (x41g) thread and that should get you CUDA crunching.

Cheers.

---

mee three, i get like 1.35 dollars worth while i sleep?

:)

Periodically I have no CUDA work. Typically for two or more weeks.
I don't no why. It seems there is nothing wrong.

As Wiggo says, there is no Stock Linux Cuda app, the only way of doing Seti Cuda work on Linux is to install the x41g 64bit Linux Cuda app, along with Optimised CPU apps:

Setiathome Applications

Claggy

But it was doing Cuda without anything more.
Only since last October (I think) this problem began

---

Periodically I have no CUDA work. Typically for two or more weeks.
I don't no why. It seems there is nothing wrong.
Yesterday SETI said:
Ter 10 Jan 2012 14:15:29 WET | SETI@home | Sending scheduler request: To fetch work.
Ter 10 Jan 2012 14:15:29 WET | SETI@home | Requesting new tasks for NVIDIA GPU
Ter 10 Jan 2012 14:15:42 WET | SETI@home | Scheduler request completed: got 0 new tasks
Ter 10 Jan 2012 14:15:42 WET | SETI@home | No tasks sent
Ter 10 Jan 2012 14:15:42 WET | SETI@home | No tasks are available for SETI@home Enhanced
Today:
Qua 11 Jan 2012 13:21:48 WET | SETI@home | Requesting new tasks for NVIDIA GPU
Qua 11 Jan 2012 13:21:52 WET | SETI@home | Scheduler request completed: got 0 new tasks
Qua 11 Jan 2012 13:21:52 WET | SETI@home | No tasks sent
Qua 11 Jan 2012 13:21:52 WET | SETI@home | No tasks are available for SETI@home Enhanced
But also:
03-Jan-2012 09:55:26 [SETI@home] Sending scheduler request: To fetch work.
03-Jan-2012 09:55:26 [SETI@home] Requesting new tasks for NVIDIA GPU
03-Jan-2012 09:55:30 [SETI@home] Scheduler request completed: got 0 new tasks
03-Jan-2012 09:55:30 [SETI@home] Project has no tasks available
This time the problem began before Xmas.

No tasks sent == the scheduler did not find any tasks in the feeder that match the request. Can be either only VLAR left for GPU or with that additional 'no work for xyz' there were only AP left in the queue.

Project has no tasks available == either there really are no tasks to be had (Check SSP) or the feeder was empty at time of asking. When cricket shows we are maxed out, the feeder is likely to be empty more often than not. Especially in a shortie storm, when you need far more tasks.

Either of those messages == you need more luck with the timing of the scheduler request. Not much you can do except babysit and abuse the update button. (or equivalent commandline)

Additionally you are on BOINC 6.12.x which may have tasks stuck in DL on disproportionate backoffs, preventing further requests.


Also, your latest computer entries show that you are running stock, whereas the system previously was running anonymous/optimised.
That also explains why you were getting CUDA work, but aren't getting any now. ;)

Something you did on or about December 18th lost you your optimised setup.

You need to reinstall the optimised application(s) - preferably x41g as already pointed out by Claggy and Wiggo.

ya and if you use an optimised apps installer, make sure you check the checkbox about you want cuda crunching :) (which i saw doesnt come by default)

(There is no installer for linux...)