BOINC v6.6.38 has been out for a while and now v6.10.0. Both are development versions. Anyone tried these or have any information on them?

http://boinc.berkeley.edu/dl/

yes, i'm tried both and currently running 6.10.0 on my quad....

6.10.0 = ati support, cal libraries are now seen if present.

6.6.38 a minor bug that i found but is resolved in 6.10.0

I've changed from the 6.6.38 to the 6.10.0 and some hours later this PC detached from GPUGrid without any reason. After manual call from BOINCStats they PC reconnect to GPUGrid and is now working. Any hint, why the system makes a disconnect?

---

bam related....

bam related....

It's not BAM related. I've lost again 2 WUs from my GTX295 on a system start. Look's like a bug in the 6.10.0. Sometimes after login and start of BOINC the GPU isn't correct identified and then the BOINC manager makes a disconnect from GPUGrid. All work is in the project folder, but after a reconnect it's lost.

I've now downgraded to 6.6.38. There I never had such problems.

---

bam related....

Sometimes after login and start of BOINC the GPU isn't correct identified and then the BOINC manager makes a disconnect from GPUGrid. All work is in the project folder, but after a reconnect it's lost.

I have 4 GPU systems running v6.10.0 and haven't seen this misbehavior yet.
So far both my NVidia and ATI GPUs are being properly identified.
Knock on wood...

I tried this new BOINC-version, but only my GPU-task is running and all CPU-tasks were preempted. Fall-back to 6.6.38

I tried this new BOINC-version, but only my GPU-task is running and all CPU-tasks were preempted. Fall-back to 6.6.38

Rom has said there will be a new version out today or tomorrow with a few fixes.

As for cpu tasks being preempted that is simply because it is supposed to be doing them in a slightly different order (ie by date/time downloaded), as long as its running some cpu wu nothing to worry about.

I have had 6.10.0 running for a few days now on an i7 without any issues. There are some reports on the mailing list about the x64 (linux versions in particular) being unable to connect to the core client.

---

BOINC blog

Now I tried the 6.10.1, too. Same behavior: only GPUGrid is running and absolutely no CPU-task!

Now I tried the 6.10.1, too. Same behavior: only GPUGrid is running and absolutely no CPU-task!

This is very strange as I have 8 machines running v6.10.0 and v6.10.1 and haven't seen this behavior at all, maybe just luck or maybe a setting? I do have an issue that on 64bit machines the BOINC v6.10.x manager will not find and start the client on boot. The manager needs to be closed and restarted to start the clients. This is only on 64bit (all machines are Windows), 32bit clients are not affected.

I'm running 6.10.1 and 190.62(WHQL) and I'm getting Communication deferred and the number of hours, the wus are as far as I can tell doing just fine, As this was happening under 6.6.38 and with 186.18 and 190.62 also. Right now I have one gpugrid wu(waiting) and I'm doing 2 MW@H wus on the GTX295(about 7 mins each).

---

@Beyond: I found the error. In my old cc_config from 6.6.38 is in the section 'options' a variable called <ncpus>, which had the value of 0. So no CPU is present for BOINC. I changed this value to 4 because of my quad and now the CPU-tasks compute!

I never touched this option since some experiments on the early time of GPUGrid, when some tried to get an extra core for GPUGrid, which then use a whole core for feeding the GPU. After some experiments I changed the value to default and everything runs fine until then. Strange behavior! But now 6.10.1 computes well until the next error... ;)

Well, is there any experience of successful v6.10.x running of x64-machines? Should I try it to be able at last cruncg gpugrid, or I should just wait to bugfixes?

---

From Siberia with love!

Well, is there any experience of successful v6.10.x running of x64-machines? Should I try it to be able at last cruncg gpugrid, or I should just wait to bugfixes?

I have it running on 3 XP64 boxes. The only problem I've seen is that on all 3 the BOINC v6.10.x manager will not find and start the client on boot. The manager needs to be closed and restarted to start the clients. This is only on 64bit (all machines are Windows), 32bit clients are not affected.

I´m now testing 6.10.1 on Windows 7 64-Bit. By now the client was found on two start procedures.