I've run 45 tasks now without error, or any other problems. Last night I started getting this appear in BOINC manager running 6.4.2.

12/12/2008 08:23:55|GPUGRID|Message from server: No work sent
12/12/2008 08:23:55|GPUGRID|Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
12/12/2008 08:23:55|GPUGRID|Message from server: (won't finish in time) BOINC runs 43.9% of time, computation enabled 98.3% of that

I'm getting this as well across a couple of hosts. I did have some odd DCF values which now seem to have started to rectify.
I got more work by suspending all other projects on the PC and then manually updating GPUGrid .... when I got my allocation, I restarted the other work. GPU WUs run normally - they don't wait - when I have some.
It doesn't feel like I have a reliable work flow at the moment somewhere between client & application without manual intervention.

I'm getting this as well across a couple of hosts. I did have some odd DCF values which now seem to have started to rectify.
I got more work by suspending all other projects on the PC and then manually updating GPUGrid .... when I got my allocation, I restarted the other work. GPU WUs run normally - they don't wait - when I have some.
It doesn't feel like I have a reliable work flow at the moment somewhere between client & application without manual intervention.

...... under 6 hours on that Black Edition - that's good going.

P.

...... under 6 hours on that Black Edition - that's good going.

.... you sure? I bought a second at eBuyer last week - although they don't have any at the moment - Dabs are showing them in stock although at £252 (ouch). Great cards.

P.

Thanks, Burdett, for the tip.

The workaround did it here, too, I'm using BOINC client version 6.3.21 for windows_x86_64 and a GeForce GTX 260.

However, this message (and its sudden appearence) is a bit odd. I remember I got the same message once when I attached to the project with a pc with no compatible coprocessor at all. I also noticed that the communication delay is something slightly below 24 hrs, so my PC would only poll once a day without forcing it manually. Furthermore, I got only 1 workunit and not 2 on my dualcore as before.

When I poll manually after receiving one workunit (and after starting the other cpu-bound project, currently ABC@home, again) I'm getting now the message:

Yes, as mentioned in the other forum thread "BOINC 6.4.5 released....", the DCF seems to be way out. When I downloaded a WU, BOINC manager said 9.30hrs to completion which I thought didn't seem to bad, but, as soon as it started, it jumped to 180hrs. Hopefully this will correct itself fairly quickly and then work will flow a lot smoother.

@Burdett: You are right they seem to back in stock. More expensive now though.

The server should be now ignoring dcf for the time being.
I will reuse it in a couple of weeks when things are stabilized.
Let me know if the situation improves.

gdf

On my i7 with 2x260's estimated time at download now shows as 259 hours. This has 'dropped' from 278 hours over the past 5 or 6 WUs returned. If this is the pace of correction by WU return then this isn't going to rectify anytime soon - and this particular host normally returns 7 or 8 WUs a day.

P.

I think my last WU dropped a little over 2hrs from the previous one: from 180hrs to ~178hrs. At this rate it will be weeks for me before it corrects itself.

Is there no way to manually set the estimated time to say 16hrs or 20hrs and then let the DCF correct from there? That would take into account users with slower cards and still benefit those with faster ones.

Do not do this if you are not comfortable editing xml. Any errors may trash your Boinc installation - Use at your own risk!

Manual adjustment of the dcf is not advised, but it is possible:

https://setisvn.ssl.berkeley.edu/beta/forum_thread.php?id=1308

Substitute the references to Seti Beta for GPUGrid



/edit: a WU running on a 8800GT started with 1375hrs to completion, using the above method, I returned it to 14hrs.
____________

Tried it on one host - got the estimated time down to about 14 hours - which I thought seemed a reasonable start time to let it correct/refine itself from .... subsequent requests for work are now greeted with the 'no work for your tye of computer and work won't finish in time' message as above.

Any ideas as to why?

.... take it all back. After a couple of false starts work does again flow. Thanks Nightlord - great tip.

Mark, you should try this.....

.... take it all back. After a couple of false starts work does again flow. Thanks Nightlord - great tip.

Mark, you should try this.....

.... subsequent requests for work are now greeted with the 'no work for your tye of computer and work won't finish in time' message as above.

Any ideas as to why?

.... subsequent requests for work are now greeted with the 'no work for your tye of computer and work won't finish in time' message as above.

Any ideas as to why?

I've noticed that too. The problem seems to be that BOINC treats GPU like any other project when it is working out its work buffer. To see this for yourself take a computer running just one project (not GPU) and check the work buffer in the project tab on Boincview. Now connect GPU to that computer. The work buffer will double (assuming the resource share for both projects is the same).

The solution (pending any change to BOINC code) is to adjust your maintain enough work parameters down or possiblly fiddle with the resource share (I've not tried that with GPU yet).

Phoneman1

that doesn't work either.....manually changing the rdcf got me 2 tasks for the moment but thereafter get the message won't finish in time...I have ample std and ltd to be able to keep a 4 task cache on a quad but until they fix the BOINC client and/or the task est time my boxes will run out of work unless constantly babysat which can't happen....the 24hour back-off time increases the chances of idle time :(

........ it was good whilst it lasted - managed to 'fill-up' on WUs .... but the last 2 are now showing estimates of 297hrs.... DCF has gone back up to 28.xxxxxx.
At what point is the DCF set in the client and by what?

I've got an empty cache and still cannot get any WU. Does anybody else have this problem?

13/12/2008 11:29:09|GPUGRID|Message from server: No work sent
13/12/2008 11:29:09|GPUGRID|Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
13/12/2008 11:29:09|GPUGRID|Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.

I have ample std and ltd to be able to keep a 4 task cache on a quad but until they fix the BOINC client and/or the task est time my boxes will run out of work unless constantly babysat which can't happen....the 24hour back-off time increases the chances of idle time :(

The same problem here. Without manually updating my PCs are very fast without work. I'm really enthusiastic at the start of the project and purchased 6 big graphic cards, but at the moment I'm really frustrated. Since the version 6.3.19 I can't see any enhancement. It's much more important to feed the 8800GT up to GTX260²/GTX280 with enough work then satisfy the user with the 8500GT. Better 3 WUs in reserve than no WU for a half day on this fast cards.
____________

........ Thanks GDF.

I see the number of WUs in progress is dropping steadily - at least I think it is, unless the past few days have been uncharacteristically high. Which I guess is hosts running dry.

On a plus note - my son's PS3 happily bumbles along without need of intervention (until he wants to use it!).

At some future stage could we see a differentiation on the Server Status page between PS3 and GPU work?

It's a strange one.
Can you do anything about the 24 hour back off that accompanies the messages?

Still getting the following message. It then backs off for 24 hrs and my comp goes idle. Lucky for me wu's take a day of crunching, but I'm still idle for 4hrs. DCF has been manually set to 1.0.

14/12/2008 6:03:14 AM|GPUGRID|Sending scheduler request: To fetch work. Requesting 112428 seconds of work, reporting 0 completed tasks
14/12/2008 6:03:19 AM|GPUGRID|Scheduler request completed: got 0 new tasks
14/12/2008 6:03:19 AM|GPUGRID|Message from server: No work sent
14/12/2008 6:03:19 AM|GPUGRID|Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
14/12/2008 6:03:19 AM|GPUGRID|Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
14/12/2008 6:03:19 AM|GPUGRID|Message from server: (won't finish in time) BOINC runs 99.9% of time, computation enabled 100.0% of that

Estimated wu time was only 4hrs with a dcf of 1. Things appear to have come good now. I have 4 wu's in the cache.

I'm now seeing wu's that only claim 2435 credits vs 3232.

nothing good now - just got a fresh WU - estimated runtime for a 260: 1901 hours.

this is going to be a reasonable attempt for gaining that fubar@home badge. :(