Posts by captainjack

1) Message boards : Number crunching : problem with de_nbody tasks never finishing (Message 73831) Posted 13 Jun 2022 by captainjack Post: According to the example given at https://boinc.berkeley.edu/wiki/client_configuration, it looks to me like it is supposed to be dashes. I have dashes in my app_config.xml and they work fine.
2) Message boards : Number crunching : problem with de_nbody tasks never finishing (Message 73829) Posted 13 Jun 2022 by captainjack Post: Hey mikey, Your app_config.xml has a typo in it. In the line <cmdline>--nthreads> 6</cmdline> there is an extra ">" after --nthreads. Look to me like it should be <cmdline>--nthreads 6</cmdline> I don't know if it will make a difference but thought it might.
3) Message boards : Number crunching : Setting up multiple instances of BOINC in Windows (Message 73767) Posted 1 Jun 2022 by captainjack Post: HRFMguy, It's pretty easy to create a cc_config.xml file using these instructions. https://boinc.berkeley.edu/wiki/client_configuration At one time, I followed the overclock instructions to run 2 BOINC clients and they work like a charm. Best of luck.
4) Message boards : Number crunching : Stuck in task suspended by user (Message 73512) Posted 14 May 2022 by captainjack Post: Just an idea: In Boinc Manager, under the Activity tab, does it show Run Always, Run Based on Preferences, or Suspend?
5) Message boards : News : GPU Issues Mega Thread (Message 66141) Posted 25 Jan 2017 by captainjack Post: Chris Rampson, If you believe that there is a problem with the code, you might ask yourself this question: Why are other Milkyway users able to successfully complete those tasks using Linux and NVIDIA GPU's? Edit: Re: this thread http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4087&postid=66127
6) Message boards : Application Code Discussion : Tons of failed jobs (Message 66130) Posted 21 Jan 2017 by captainjack Post: Seems that the Linux 64 bit version of BOINC has been stuck at 7.2.42 for 3 years now. I was able to get 7.6.33 using the Ubuntu software installer.
7) Message boards : Application Code Discussion : Tons of failed jobs (Message 66128) Posted 21 Jan 2017 by captainjack Post: Chris, It appears that something is missing with your GPU setup. In your computer description, the driver version is not being shown. For example mine shows: [2] NVIDIA GeForce GTX 970 (4036MB) driver: 367.57 OpenCL: 1.2 Your setup shows [2] NVIDIA GeForce GTX 690 (1998MB) OpenCL: 1.2 Note that in your setup the "driver: 367.57" is missing. Suggest that you upgrade to the latest version of BOINC (7.6.33) and verify that your GPU drivers are installed correctly. If that doesn't get you going, please post the first 50 (approximate) lines of your event log after you start up BOINC so we can see what else might be amiss. Your issues are similar to another cruncher. You can read down this thread to see what he did to solve the problem. http://milkyway.cs.rpi.edu/milkyway/show_user.php?userid=113092 Hope that helps.
8) Message boards : News : GPU Issues Mega Thread (Message 66093) Posted 7 Jan 2017 by captainjack Post: wb8ili, Glad you got it fixed. Just in case you are still wondering, most of the client files are in /var/lib/boinc-client (projects folder and slots folder included). The procedure that starts/restarts the boinc client is in /etc/init.d and is called boinc-client. Happy crunching.
9) Message boards : News : GPU Issues Mega Thread (Message 66057) Posted 30 Dec 2016 by captainjack Post: wb8ili, 1) The Linux version on the BOINC Berkeley website isn't kept up to date very well since the BOINC team lost their funding. If you use the Ubuntu Software installer to install BOINC, it will install 7.6.33. From what I understand, it has some improvements at recognizing GPU versions. The Ubuntu installer will install boinc in a different set of folders and run it under the user-id of "boinc". 3) IIRC, I installed the NVIDIA drivers by opening the "System Settings" (icon looks like a gear with a wrench laid over top of it), then open "Software and Updates", then click on "Additional Drivers" folder. There are options to "Use X.Org X server" or "Use NVIDIA binary driver 367.57". I chose NVIDIA binary driver. Maybe those changes will help. Keep us posted on your progress.
10) Message boards : News : GPU Issues Mega Thread (Message 66053) Posted 29 Dec 2016 by captainjack Post: wb8ili, The first thing I noticed is that you are running an older version of BOINC. You might try updating to the latest version and see if that makes a difference. The second thing I noticed is that your event log shows that the driver version of your GPU is unknown. Here is my event log with similar lines. Wed 28 Dec 2016 10:26:18 AM CST \| \| Starting BOINC client version 7.6.33 for x86_64-pc-linux-gnu Wed 28 Dec 2016 10:26:18 AM CST \| \| log flags: file_xfer, sched_ops, task Wed 28 Dec 2016 10:26:18 AM CST \| \| Libraries: libcurl/7.50.1 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.33 librtmp/2.3 Wed 28 Dec 2016 10:26:18 AM CST \| \| Data directory: /var/lib/boinc-client Wed 28 Dec 2016 10:26:19 AM CST \| \| CUDA: NVIDIA GPU 0: GeForce GTX 970 (driver version 367.57, CUDA version 8.0, compute capability 5.2, 4036MB, 3806MB available, 3919 GFLOPS peak) Wed 28 Dec 2016 10:26:19 AM CST \| \| CUDA: NVIDIA GPU 1: GeForce GTX 970 (driver version 367.57, CUDA version 8.0, compute capability 5.2, 4037MB, 3973MB available, 3919 GFLOPS peak) Wed 28 Dec 2016 10:26:19 AM CST \| \| OpenCL: NVIDIA GPU 0: GeForce GTX 970 (driver version 367.57, device version OpenCL 1.2 CUDA, 4036MB, 3806MB available, 3919 GFLOPS peak) Wed 28 Dec 2016 10:26:19 AM CST \| \| OpenCL: NVIDIA GPU 1: GeForce GTX 970 (driver version 367.57, device version OpenCL 1.2 CUDA, 4037MB, 3973MB available, 3919 GFLOPS peak) Wed 28 Dec 2016 10:26:19 AM CST \| \| Host name: Barracuda Wed 28 Dec 2016 10:26:19 AM CST \| \| Processor: 8 GenuineIntel Intel(R) Core(TM) i7-4820K CPU @ 3.70GHz [Family 6 Model 62 Stepping 4] Wed 28 Dec 2016 10:26:19 AM CST \| \| Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts Wed 28 Dec 2016 10:26:19 AM CST \| \| OS: Linux: 4.8.0-32-generic Something might be amiss with your GPU driver installation. What flavor of Linux are you using? And how did you install your GPU drivers. I am using Ubuntu 16.10 and used the standard Ubuntu driver installer.
11) Message boards : News : GPU Issues Mega Thread (Message 66050) Posted 29 Dec 2016 by captainjack Post: wb8ili wrote: Tell me if I am wrong, but - I don't think the combination of LINUX and NVIDIA cards has worked (returned valid results) since the tasks were bundled. At least mine haven't. All of my LINUX (Ubuntu) and NVIDIA tasks are validated. Please post the first 50 or so lines from the event log after a restart so we can see how the system in question is set up. Maybe it will give us some clues.
12) Message boards : Number crunching : Erroneous WU Download for Non-DP GPU (Message 66028) Posted 18 Dec 2016 by captainjack Post: Brian, If you go to the Milkyway home page, then click on "Your Acount", then click on "Milkyway@home Preferences", there are options there to Use CPU, Use ATI GPU, or Use NVIDIA GPU. You can un-check the GPU options and Milkyway will no longer send you GPU tasks. Hope that helps.
13) Message boards : News : Scheduled Maintenance Concluded (Message 65743) Posted 13 Nov 2016 by captainjack Post: wb8ili asked: Just to clarify - I am referring to "Can't Validate" bundled GPU tasks under UBUNTU. Here is an example - (can't figure out to make it a link) http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=1886765954 wb8ili, it looks like all your "bundle" tasks are failing. On that particular task, it was sent to two other computers and they both failed. After failures on three computers, the Milkyway host decided that it might be a bad work unit and gave it a status of "Can't Validate". At this point, the real question is why all of your "bundle" tasks failing. The only major difference I can see between your setup and mine is that you are using an older (February 2014) version on BOINC on your machine. I am using the current one that is distributed by the BOINC software installer. You might try to upgrade BOINC and see if that helps.
14) Message boards : News : Scheduled Maintenance Concluded (Message 65727) Posted 13 Nov 2016 by captainjack Post: wb8ili, When a task is sent to multiple computers and too many of the computers get an error, the status of the task is set to "Completed, can't validate. If you look at the work unit in question, it was sent to 3 other computers and they all got errors. The error text says "Too many errors (may have bug)". I am running some more right now and you should be able to find some that did validate. Hope that helps.
15) Message boards : News : Scheduled Maintenance Concluded (Message 65720) Posted 12 Nov 2016 by captainjack Post: wb8ili asked: Is anybody having there "bundle" tasks validated? Mine are all failing validation. This is for a UBUNTU 16.04 system using the 1.40 MW app Yes, I have some validated for Ubuntu 16.10 with NVIDIA 970's.
16) Message boards : News : Updated Server Daemons and Libraries (Message 65361) Posted 30 Sep 2016 by captainjack Post: Will Guerin, The error message in your task log says that your GPU's do not support double precision which is required for Milkyway processing.
17) Message boards : Number crunching : Computational error on new build (Message 64147) Posted 3 Dec 2015 by captainjack Post: Hi NostradamusJones, I also have an AMD 6950. When I ran Catalyst version 13.1 drivers, I could successfully run both "milky@home" tasks and "milkyway@home separation (modified fit)" tasks. Now that I have upgraded to a more recent version of Catalyst, I can no longer run the "milkyway@home" tasks. It is a known quirk of the AMD 6950. If you really want to run the "milkyway@home" tasks, you will need to install the older drivers. If you want to stay with current drivers you can simply exclude the "milkyway@home" tasks from your project preferences. This is what I chose to do. Hope that helps.
18) Message boards : Number crunching : N-body code - preference to limit # of CPUs? (Message 64037) Posted 25 Oct 2015 by captainjack Post: Ralph Hyre, There is a rather obscure option in the app_config.xml file to limit the number of CPU's used by the multi-thread N-Body tasks. Put together an app_conf.xml file that looks like the one below and store it in the Boinc\projects\milkyway.cs.rpi.edu_milkyway directory. The line that says <avg_ncpus>8</avg_ncpus> tells BOINC how many threads to reserve in it's job scheduling logic for the task. The line that says <cmdline>--nthreads 8</cmdline> tells the N-Body task how many threads to use. You will need to set those two lines to the number of threads that you want the N-Body tasks to use. <app_config> <app> <name>milkyway_nbody</name> <max_concurrent>1</max_concurrent> </app> <app_version> <app_name>milkyway_nbody</app_name> <plan_class>mt</plan_class> <avg_ncpus>8</avg_ncpus> <cmdline>--nthreads 8</cmdline> </app_version> </app_config> After you save the app_config_xml file in the milkyway folder, either restart BOINC or open the BOINC manager and tell it to "Read Config Files" (one of the options that you can get to from the menu bar at the top of BOINC Manager). In the Event Log, you should find a line that says "Milkyway@Home (data time) Found app_config.xml". Then download some N-body tasks and see if they conform to the new parameters. If you run into problems, you should be able to do a search for app_config.xml and find some useful hints. Hope that helps.
19) Message boards : Number crunching : CPU usage increase in modified fit 1.36 (Message 63976) Posted 8 Oct 2015 by captainjack Post: Windows 7 with an HD6950 is showing the same thing. At the start of a Modified Fit job, there is no GPU activity for 40-45 seconds, then there is GPU activity for 15-20 seconds and the job finishes. The Modified Fit tasks used to take 25-30 seconds, now they are taking 55-65 seconds. Sounds like something definitely changed.
20) Message boards : News : New N-Body Runs (Message 62450) Posted 1 Oct 2014 by captainjack Post: dlk, Did you also uncheck the box for the option "If no work for selected applications is available, accept work from other applications"?

Next 20