Message boards :
Graphics cards (GPUs) :
BOINC Client 6.6.3 after re-installing and rebooting trying to fetch work unsuccessfully
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 9 Oct 08 Posts: 50 Credit: 12,676,739 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Ran into problems finally with BOINC client 6.6.3 and my GTX 260 Core 216 GPU's ran dry. After multiple attempts to get it running again and even down leveling the BOINC client, I've reinstalled 6.6.3 and rebooted. Client says its trying to request new tasks, and recognizes two idle GPUs. Says "scheduler request completed: got 0 new taks"... would that be the GPUGrid WU download problem we've seen in the past, where we see available GPU work on this site, but it doesn't get downloaded? Hard to say if this is a GPUGrid server side problem not providing work for what seems like a valid request from BOINC client, or a BOINC client work fetch problem. I know 6.6.3 has problems, but this time the messages log file says it is trying to download work. Neil |
Paul D. BuckSend message Joined: 9 Jun 08 Posts: 1050 Credit: 37,321,185 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Ran into problems finally with BOINC client 6.6.3 and my GTX 260 Core 216 GPU's ran dry. After multiple attempts to get it running again and even down leveling the BOINC client, I've reinstalled 6.6.3 and rebooted. Client says its trying to request new tasks, and recognizes two idle GPUs. Says "scheduler request completed: got 0 new taks"... would that be the GPUGrid WU download problem we've seen in the past, where we see available GPU work on this site, but it doesn't get downloaded? Try suspending all projects, un-suspend GPU Grid and do an update to get work. I just did that as I was ony running one task and had none in queue. Got 4 right away ... now back to my regularly scheduled running ... |
|
Send message Joined: 17 Aug 08 Posts: 2705 Credit: 1,311,122,549 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I remember GDF said the 6.6.x clients required an update on the server side, which they have not yet done. This may be a sympton of an incompatibility. MrS Scanning for our furry friends since Jan 2002 |
Paul D. BuckSend message Joined: 9 Jun 08 Posts: 1050 Credit: 37,321,185 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
I remember GDF said the 6.6.x clients required an update on the server side, which they have not yet done. This may be a sympton of an incompatibility. As I understand it they made some changes to the request code, though it is supposed to be backwards compatible ... what I hope is that they did not create another situation like with my Power Mac where I cannot upgrade because if I do so i cannot get work from some projects because they don't recognize the new processor ID string from the 6.x versions. It will really stink if you cannot reliably get work from many projects because they farble up the messages and to run the GPUs reliably you have to give up support for many other projects ... well, time will tell ... heck, they have not made a reliable 6.6.x version yet ... :) |
©2025 Universitat Pompeu Fabra