Message boards : Graphics cards (GPUs) : Development BOINC v6.10.0
| Author | Message |
|---|---|
 Beyond Send message Joined: 23 Nov 08 Posts: 1112 Credit: 6,162,416,256 RAC: 0 Level  Scientific publications    | |
|
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? | |
ID: 11985 | Rating: 0 | rate:
 /   Reply
Quote
| |
|
yes, i'm tried both and currently running 6.10.0 on my quad.... | |
| ID: 11986 | Rating: 0 | rate:
/ Reply
Quote
| |
Kokomiko   Send message Joined: 18 Jul 08 Posts: 190 Credit: 24,093,690 RAC: 0 Level  Scientific publications   | |
|
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? | |
| ID: 12027 | Rating: 0 | rate:
/ Reply
Quote
| |
|
bam related.... | |
| ID: 12028 | Rating: 0 | rate:
/ Reply
Quote
| |
|
Kokomiko Send message Joined: 18 Jul 08 Posts: 190 Credit: 24,093,690 RAC: 0 Level Scientific publications | |
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. ____________   | |
| ID: 12063 | Rating: 0 | rate:
/ Reply
Quote
| |
|
Beyond Send message Joined: 23 Nov 08 Posts: 1112 Credit: 6,162,416,256 RAC: 0 Level Scientific publications | |
bam related.... 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... | |
| ID: 12065 | Rating: 0 | rate:
/ Reply
Quote
| |
|
[boinc.at] Nowi Send message Joined: 4 Sep 08 Posts: 44 Credit: 3,685,033 RAC: 0 Level  Scientific publications   | |
|
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 | |
| ID: 12076 | Rating: 0 | rate:
/ Reply
Quote
| |
|
MarkJ Volunteer moderator Volunteer tester Send message Joined: 24 Dec 08 Posts: 738 Credit: 200,909,904 RAC: 0 Level  Scientific publications | |
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 | |
| ID: 12128 | Rating: 0 | rate:
/ Reply
Quote
| |
|
[boinc.at] Nowi Send message Joined: 4 Sep 08 Posts: 44 Credit: 3,685,033 RAC: 0 Level Scientific publications | |
|
Now I tried the 6.10.1, too. Same behavior: only GPUGrid is running and absolutely no CPU-task! | |
| ID: 12139 | Rating: 0 | rate:
/ Reply
Quote
| |
|
Beyond Send message Joined: 23 Nov 08 Posts: 1112 Credit: 6,162,416,256 RAC: 0 Level Scientific publications | |
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. | |
| ID: 12155 | Rating: 0 | rate:
/ Reply
Quote
| |
|
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). | |
| ID: 12158 | Rating: 0 | rate:
/ Reply
Quote
| |
|
[boinc.at] Nowi Send message Joined: 4 Sep 08 Posts: 44 Credit: 3,685,033 RAC: 0 Level Scientific publications | |
|
@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! | |
| ID: 12166 | Rating: 0 | rate:
/ Reply
Quote
| |
|
Rabinovitch  Send message Joined: 25 Aug 08 Posts: 143 Credit: 64,937,578 RAC: 0 Level  Scientific publications | |
|
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? | |
| ID: 12168 | Rating: 0 | rate:
/ Reply
Quote
| |
|
Beyond Send message Joined: 23 Nov 08 Posts: 1112 Credit: 6,162,416,256 RAC: 0 Level Scientific publications | |
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. | |
| ID: 12173 | Rating: 0 | rate:
/ Reply
Quote
| |
|
[boinc.at] Nowi Send message Joined: 4 Sep 08 Posts: 44 Credit: 3,685,033 RAC: 0 Level Scientific publications | |
|
I´m now testing 6.10.1 on Windows 7 64-Bit. By now the client was found on two start procedures. | |
| ID: 12181 | Rating: 0 | rate:
/ Reply
Quote
| |
Message boards : Graphics cards (GPUs) : Development BOINC v6.10.0
