Difference might be I run 64bit BOINC and you seem to run 32bit... Also haven't seen other reports (well, not from other ppl) about this. Are you sure your core client got updated to 6.6.31? I simply extract files from the archive downloaded from BOINC-site, then copy the 3 main files to correct folder, replacing older files.
I simply loaded this file:
boinc_6.6.31_i686_pc_linux_gnu.sh
but it reports as 6.6.29.
Tullio
I've built a client with the latest source code that fixes the "won't finish in time" problem. It is 32bit and Windows only.
Its .RAR archive can be gotten from my Skydrive. It is called BOINC 6.6.76, to make sure I am outside the range of Berkeley products and comes with my own BOINC Manager which shows both the CPU time and Wall Time columns in the Tasks tab.
Steps to follow wrote:
Before you do anything, stop BOINC. Then make sure to backup your original boinc.exe, boinc.dll and boincmgr.exe (sqlite3.dll comes only with 6.6.28 and above and does not necessarily need to be backed up, it's the same file all over the place)
Now unpack the archive into your BOINC directory (default: C:\Program Files\BOINC\). The sqlite3.dll is used by BOINC Manager, so if you do not have it in your BOINC directory, it's at least included in this package.
When that's done, just restart BOINC. It'll start doing benchmarks, since I named my version 6.6.76 (to be outside the possible range Berkeley upholds). And that's it.
You should now have no trouble getting work from projects.
I've built a client with the latest source code that fixes the "won't finish in time" problem. It is 32bit and Windows only.
Its .RAR archive can be gotten from my Skydrive. It is called BOINC 6.6.76, to make sure I am outside the range of Berkeley products and comes with my own BOINC Manager which shows both the CPU time and Wall Time columns in the Tasks tab.
Steps to follow wrote:
Before you do anything, stop BOINC. Then make sure to backup your original boinc.exe, boinc.dll and boincmgr.exe (sqlite3.dll comes only with 6.6.28 and above and does not necessarily need to be backed up, it's the same file all over the place)
Now unpack the archive into your BOINC directory (default: C:\Program Files\BOINC\). The sqlite3.dll is used by BOINC Manager, so if you do not have it in your BOINC directory, it's at least included in this package.
When that's done, just restart BOINC. It'll start doing benchmarks, since I named my version 6.6.76 (to be outside the possible range Berkeley upholds). And that's it.
You should now have no trouble getting work from projects.
I have downloaded it and am running it now, no problems so far! Thanks!!!!!!!!!
... which was resulting in no more work for Einstein.
I've used pretty much every version of BOINC in the v6.6 range since v6.6.14, and I think you're misinterpreting how it works.
It does indeed poll every attached project to see if - just perhaps - it might have launched a CUDA app since it last looked: but it also checks for, and downloads, CPU work according to an independent set of priorities.
There may have been reasons why you didn't get CPU work - the changed definition of existing debt values is a case in point - but it wasn't the result of the fishing expedition for potential CUDA work.
Thanks for the info about fishing expedition. I really wasn't interpreting anything, having only the vagues idea (and no interest in ) how BOINC does its magic. All I knew was that I never saw a request for Einsten CPU work, only GPU, and I hadn't gotten any jobs for a day or so. Maybe the big backlog of SETI jobs (40 or 50) trying repeatedly to upload had something to do with that (shrug>? Anyway, the older version of BOINC I'm using started getting CPU jobs for Einstein as soon as installed and works well for me. No need here for the latest and greatest.
17-7-2009 22:38:25 Einstein@Home Scheduler request completed: got 0 new tasks
17-7-2009 22:38:25 Einstein@Home Message from server: No work sent
17-7-2009 22:38:25 Einstein@Home Message from server: (won't finish in time) BOINC runs 42.7% of time, computation enabled 100.0% of that
A possible bug in BOINC clients later than v6.6.31
It's being investigated.
L.S.,
After reading all this - also at some other message boards (Cosmology e.g.) - and some news in the new experimental Boinc Wiki - I did my own solution. I reinstalled the Boinc software version 6.4.7 . And it's working properly!
/raimond detempe
RE: Difference might be I
)
I simply loaded this file:
boinc_6.6.31_i686_pc_linux_gnu.sh
but it reports as 6.6.29.
Tullio
I've built a client with the
)
I've built a client with the latest source code that fixes the "won't finish in time" problem. It is 32bit and Windows only.
Its .RAR archive can be gotten from my Skydrive. It is called BOINC 6.6.76, to make sure I am outside the range of Berkeley products and comes with my own BOINC Manager which shows both the CPU time and Wall Time columns in the Tasks tab.
RE: I've built a client
)
I have downloaded it and am running it now, no problems so far! Thanks!!!!!!!!!
RE: RE: ... which was
)
Thanks for the info about fishing expedition. I really wasn't interpreting anything, having only the vagues idea (and no interest in ) how BOINC does its magic. All I knew was that I never saw a request for Einsten CPU work, only GPU, and I hadn't gotten any jobs for a day or so. Maybe the big backlog of SETI jobs (40 or 50) trying repeatedly to upload had something to do with that (shrug>? Anyway, the older version of BOINC I'm using started getting CPU jobs for Einstein as soon as installed and works well for me. No need here for the latest and greatest.
RE: RE: What does this
)
L.S.,
After reading all this - also at some other message boards (Cosmology e.g.) - and some news in the new experimental Boinc Wiki - I did my own solution. I reinstalled the Boinc software version 6.4.7 . And it's working properly!
/raimond detempe