Posts by Rick A. Sponholz

1) Message boards : BOINC client : BOINC 7 development discussion thread. (Message 52584)
Posted 16 Feb 2014 by Rick A. Sponholz
Post:
When upgrading to 7.2.39 (it also happened upgrading to 7.2.38) from 7.2.33, yoyo@home no longer communicates with it project's site. WU uploads become abandoned, and no new work can be retrieved. reinstalling 7.2.33 makes this condition immediately disappear, and download/upload becomes normal. Already tried to reset project with no positive result. Also tried to detach project, and reattach, but then I could not reattach yoyo@home, until I downgraded to 7.2.33, then reattach worked perfectly. Not sure why, but thought I'd let you know. Occurred on all 5 of my Windows 7 desktops.
Regards,
Rick
2) Message boards : News : New BOINC installer includes VirtualBox (Message 51493)
Posted 24 Nov 2013 by Rick A. Sponholz
Post:
... which requires BOINC 7.0.28 or above ...

That is indeed what I read at http://climateathome.com/climateathome/.

But you said

LinuxMint ... still have version 7.2.27 of BOINC in their App Store.

Surely 7.2.27 is 'above' 7.0.28?


Oops, sorry. I meant 7.0.27 is currently in their App Store. Rick
3) Message boards : News : New BOINC installer includes VirtualBox (Message 51488)
Posted 23 Nov 2013 by Rick A. Sponholz
Post:
The bundling of BOINC and VirtualBox installers applies to Windows only.

They are two different applications, and (if the Windows experience can be followed - I have no Linux experience) an installation of VirtualBox by itself will be detected and utilised by BOINC v7.2.27

VirtualBox availability for Linux is described at https://www.virtualbox.org/wiki/Linux_Downloads. You should check that the version of VirtualBox you install is compatible with the BOINC project you wish to run - some, like Test4Theory, are having problems with the latest releases.


Thanks for your reply Richard. I've already installed Vitualbox on my Linux machines, but I'm running climate@home, which requires BOINC 7.0.28 or above, hense my request. Thanks for the feedback though. Regards, Rick
4) Message boards : News : New BOINC installer includes VirtualBox (Message 51482)
Posted 23 Nov 2013 by Rick A. Sponholz
Post:
David,
Not sure if you have any contacts with the folks who manage LinuxMint, but they still have version 7.2.27 of BOINC in their App Store. If you can, (I've already requested via email) could you request they update their version, so I (we) can start using VirtualBox with BOINC? Thanks In Advance, Rick
5) Message boards : Questions and problems : Only using one of two GPUs (Message 32290)
Posted 19 Apr 2010 by Rick A. Sponholz
Post:
Jord,
Thank you SO MUCH!!! It worked and I'm very excited to use all of my new GPU's. Thanks again.
Rick
6) Message boards : Questions and problems : Only using one of two GPUs (Message 32288)
Posted 19 Apr 2010 by Rick A. Sponholz
Post:
Jord,
I tried creating a cc_config.xml file like the one shown in this thread. Mine is shown below:

<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
</options>
</cc_config>

But something is still missing (I'm a novis) because I'm getting this message when starting BOINC:

4/19/2010 12:16:51 PM Missing start tag in cc_config.xml

What am I missing? Thanks in advance for the help.
Rick

7) Message boards : BOINC client : 6.6.9 Windows Notes & Bugs (Message 23315)
Posted 26 Feb 2009 by Rick A. Sponholz
Post:
Jord,

BOINC 6.6.11 completed 1 GPUGRID CUDA work unit, and started another without a problem, and continues to supply my GPU with work. The next test is to see how BOINC 6.6.11 will finish all GPUGRID work, and switch to Seti CUDA work units. This switch should be in about 12 hours. I've started upgrading my other computers to 6.6.11, and will let you know if I encounter any problems.

Rick
8) Message boards : BOINC client : 6.6.9 Windows Notes & Bugs (Message 23306)
Posted 26 Feb 2009 by Rick A. Sponholz
Post:
Jord,
After 5 hours of running 6.6.11, I have not had a single instance of CUDA work units stopping. Next test will be when my GPUGRID work unit finishes in about 1.75 hours. Tested 6.6.11 on computer:

#3 Intel 2 Quad Q6600@2.40GHz 1.98GB RAM
GeForce 9600GT 512MB RAM Driver 6.14.11. 8206

Tomorrow, I'll install 6.6.11 on 9 of my 10 other computers (1 laptop is in the shop) as a double check. It looks like the BOINC programers did a great job!
Rick
9) Message boards : BOINC client : 6.6.9 Windows Notes & Bugs (Message 23302)
Posted 25 Feb 2009 by Rick A. Sponholz
Post:
Jord,
I'll get right on it.
Rick
10) Message boards : BOINC client : 6.6.9 Windows Notes & Bugs (Message 23297)
Posted 25 Feb 2009 by Rick A. Sponholz
Post:
I am still experiencing stopping CUDA work units, but strangely only on one (Computer #3 below) CUDA capable machine. This happens to GGPUGrid, and SETI@Home work units on ALL (I’ve tested each one) versions of BOINC higher than 6.6.5. The work units show "waiting to run", but no CUDA work units are running. Exiting, and restarting BOINC, restarts a CUDA work unit, but within a few minutes no CUDA work units are running. This issue also occurred on computer #3 with video driver 6.14.11.8122. I had also experienced this issue on all 5 computers using BOINC 6.6.7, but only computer #3 continues to have a problem with BOINC 6.6.9. The issue above is different than the hanging SETI CUDA work unit problem well documented in other threads. I have 5 CUDA capable computers (Windows XP Service Pack 3) and I'm running SETI@ Home (CUDA 6.08 on BOINC 6.6.9) (also GPUGRID) on all 5, as well as World Community Grid, & Einstein@home. Below are the specs for my 5 CUDA capable computers:

#1 Intel Core 2CPU 6600@2.40Ghz 1.98GB RAM
GeForce 9600GT 512RAM Driver 6.14.11.8206

#2 Intel 2 Quad Q6600@2.40GHz 1.98GB RAM
GeForce 9800GTX+ 512MB RAM Driver 6.14.11. 8206

#3 Intel 2 Quad Q6600@2.40GHz 1.98GB RAM
GeForce 9600GT 512MB RAM Driver 6.14.11. 8206

#4 Intel 2 Quad Q9550@2.83GHz 1.98GB
RAM GeForce 9600GT 512MB RAM Driver 6.14.11. 8206

#5 Intel 2 Quad Q9550@2.83GHz 3.25GB RAM
GeForce 9800GT 1.024GB RAM Driver 6.14.11.8206

I have rolled back computer #3 to BOINC 6.6.5, and the problem has gone away.
Rick




Copyright © 2022 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.