Yes, it's pretty much the same on all the platforms, the <use_all_gpus>1</use_all_gpus> is the one you really need.

<cc_config>
    <log_flags>
        <sched_op_debug>1</sched_op_debug>
    </log_flags>
    <options>
        <dont_contact_ref_site>1</dont_contact_ref_site>
        <use_all_gpus>1</use_all_gpus>
        <save_stats_days>365</save_stats_days>
    </options>
</cc_config>

It goes in the same place as in Windows, and needs to be a BOINC compatible .xml
Easiest way is to duplicate an existing BOINC .xml then change the name to cc_config.xml and replace the contents with the above.

Hey Al

Good to see another join the Linux movement. But now you are moving into experiment territory, you need to edit the xorg file to be able to use all GPU'S. Am at work so I cannot reference mine that I used but have a look in the Linux Cuda 8.0 thread and about half way through there is some ref points to help.

Well, rebooted, and as my rear USB3.0 ports on my MB weren't recognizing my stick when I put it in, I went into the BOIS to check things out, and the first thing I noticed was the date/time was off, set to tomorrow, so I fixed that, and everything USB3.0 was enabled, don't know whats up with that now, but don't really care as it still works on 2.0. So, rebooted, came up fine, went into BOINC to see what was up, and here is the event log. I presume the error 10-20 lines down about the time being ignored is because of what I did, but no idea why 4 of 5 GPU's are being not used/ignored. I think they were not used/ignored if I remember correctly the last time, but BOINC was barely installed, I figured when all the candy was added, everything would straighten itself out, but apparently not. Here it is:

So, no joy in mudville yet, want to get that fixed (and anything else obvious) before I turn it on. Whats next, any thoughts as to where to go from here?

. . Did you check that the execute permissions were set on all the app files?

Stephen

??

That did it for getting to the right folder, had to do the sudo su, and then after muffing up the spelling (apparently) a couple times, copied and pasted what you wrote, it worked like a champ. Thanks! (Linux uses / not \ I see...)

Now, about those ignored vid cards, any thoughts on those?

*edit*
Oh, and somewhat related to what I had mentioned last night, which is happening again. I started up BOINC to get the log info I pasted above, and a minute ago shut it down. I just started it up again, but it's sitting there like last night with the red dot in the taskbar icon, and it isn't attaching to the project. it's just sitting there. I am sure if I reboot it, it will come right up,. but I've never experienced this in Windows, so no idea what might be causing it.

. . On the one machine I have using the repo version of BOINC I find it comes up OK after a reboot but not if I launch manager in running Linux after I have shut it down. So if you try a reboot and see if manager will connect to the BOINC client then ...

Stephen

:)

Hey Al,
How goes the battle? How/Where do you stand now?

PS: Has anyone ever tried using a "weak key" to add a computer to and account?
I'm not having much luck after creating an account_S@H file or using the command line to attach w/key.
Any ideas on what I'm missing?

I'm building a Linux USB setup for a different user, hence the 'weak key' connect.

Hey Brent, I actually got to the shop at a little after 7:30 my time, when I had left home the project was up, so I boogied over and was hoping to pull up this thread, read it and make the changes, and quick get a load of tasks. Wouldn't you know it, in the 9 minutes it takes me to get here, it went down. Grrr. When I went home for a bit late this afternoon, I saw the project come back up, and watched a couple of my high core count machines struggle to get any CPU tasks. There were GUPPIs galore, but not much in CPU land. I figured that I would give it a few hours, so was thinking about going in there now and making the changes, and watching to see how it works before heading home, as hopefully most everybody's caches are full. I'll let you know in the next 15-45 mins how it went.

---

AS I'm also setting up that USB stick for Mark I keep making mental notes of those little things that make life easier ...
I don't think I mentioned to also search for NVidia from the Menu, and drop that on your desktop too
And to bookmark locations ... boinc folder, and S@H folder, in the File Manager for quick access, without hunting.

And coolbit for fan control in NVidia Panel
In Terminal ... sudo nvidia-xconfig --thermal-configuration-check --cool-bits=28 --enable-all-gpus ... after a reboot, you should have manual fan control.

And ... nvidia-smi -l ... to watch your card use, and temps.

More to follow I'm sure :)

Well, that didn't seem to work, I went into a file manager called Dolphin, navigated to the boinc-client dir, found the cc_config.xml file, opened it with something called Kate, which appears to basically be Notepad, added the contents

    <options>
        <dont_contact_ref_site>1</dont_contact_ref_site>
        <use_all_gpus>1</use_all_gpus>
        <save_stats_days>365</save_stats_days>
    </options> 

to it so it now reads:

!--
This is a minimal configuration file cc_config.xml of the BOINC core client.
For a complete list of all available options and logging flags and their
meaning see: https://boinc.berkeley.edu/wiki/client_configuration
-->
<cc_config>
  <log_flags>
    <task>1</task>
    <file_xfer>1</file_xfer>
    <sched_ops>1</sched_ops>
  </log_flags>
    <options>
        <dont_contact_ref_site>1</dont_contact_ref_site>
        <use_all_gpus>1</use_all_gpus>
        <save_stats_days>365</save_stats_days>
    </options>
</cc_config>

saved it as an xml file, and now my log looks like this:

Tue 18 Jul 2017 09:38:23 AM CDT | | Starting BOINC client version 7.6.31 for x86_64-pc-linux-gnu
Tue 18 Jul 2017 09:38:23 AM CDT | | log flags: file_xfer, sched_ops, task
Tue 18 Jul 2017 09:38:23 AM CDT | | Libraries: libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
Tue 18 Jul 2017 09:38:23 AM CDT | | Data directory: /var/lib/boinc-client
Tue 18 Jul 2017 09:38:32 AM CDT | | CUDA: NVIDIA GPU 0: GeForce GTX 1050 Ti (driver version 375.66, CUDA version 8.0, compute capability 6.1, 4039MB, 3996MB available, 2255 GFLOPS peak)
Tue 18 Jul 2017 09:38:32 AM CDT | | CUDA: NVIDIA GPU 1 (not used): GeForce GTX 950 (driver version 375.66, CUDA version 8.0, compute capability 5.2, 1997MB, 1964MB available, 2158 GFLOPS peak)
Tue 18 Jul 2017 09:38:32 AM CDT | | CUDA: NVIDIA GPU 2 (not used): GeForce GTX 950 (driver version 375.66, CUDA version 8.0, compute capability 5.2, 1997MB, 1964MB available, 1828 GFLOPS peak)
Tue 18 Jul 2017 09:38:32 AM CDT | | CUDA: NVIDIA GPU 3 (not used): GeForce GTX 950 (driver version 375.66, CUDA version 8.0, compute capability 5.2, 1997MB, 1964MB available, 1828 GFLOPS peak)
Tue 18 Jul 2017 09:38:32 AM CDT | | CUDA: NVIDIA GPU 4 (not used): GeForce GTX 950 (driver version 375.66, CUDA version 8.0, compute capability 5.2, 1982MB, 1930MB available, 2158 GFLOPS peak)
Tue 18 Jul 2017 09:38:32 AM CDT | | OpenCL: NVIDIA GPU 0: GeForce GTX 1050 Ti (driver version 375.66, device version OpenCL 1.2 CUDA, 4039MB, 3996MB available, 2255 GFLOPS peak)
Tue 18 Jul 2017 09:38:32 AM CDT | | OpenCL: NVIDIA GPU 1 (ignored by config): GeForce GTX 950 (driver version 375.66, device version OpenCL 1.2 CUDA, 1997MB, 1964MB available, 2158 GFLOPS peak)
Tue 18 Jul 2017 09:38:32 AM CDT | | OpenCL: NVIDIA GPU 2 (ignored by config): GeForce GTX 950 (driver version 375.66, device version OpenCL 1.2 CUDA, 1997MB, 1964MB available, 1828 GFLOPS peak)
Tue 18 Jul 2017 09:38:32 AM CDT | | OpenCL: NVIDIA GPU 3 (ignored by config): GeForce GTX 950 (driver version 375.66, device version OpenCL 1.2 CUDA, 1997MB, 1964MB available, 1828 GFLOPS peak)
Tue 18 Jul 2017 09:38:32 AM CDT | | OpenCL: NVIDIA GPU 4 (ignored by config): GeForce GTX 950 (driver version 375.66, device version OpenCL 1.2 CUDA, 1982MB, 1930MB available, 2158 GFLOPS peak)
Tue 18 Jul 2017 09:38:32 AM CDT | SETI@home | Found app_info.xml; using anonymous platform
Tue 18 Jul 2017 09:38:32 AM CDT | | Host name: al-desktop
Tue 18 Jul 2017 09:38:32 AM CDT | | Processor: 24 GenuineIntel Intel(R) Xeon(R) CPU X5690 @ 3.47GHz [Family 6 Model 44 Stepping 2]
Tue 18 Jul 2017 09:38:32 AM CDT | | 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 smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm tpr_shadow vnmi flexpriority ept vpid dtherm arat
Tue 18 Jul 2017 09:38:32 AM CDT | | OS: Linux: 4.8.0-53-generic
Tue 18 Jul 2017 09:38:32 AM CDT | | Memory: 47.10 GB physical, 47.99 GB virtual
Tue 18 Jul 2017 09:38:32 AM CDT | | Disk: 410.34 GB total, 380.75 GB free
Tue 18 Jul 2017 09:38:32 AM CDT | | Local time is UTC -5 hours
Tue 18 Jul 2017 09:38:32 AM CDT | | Config: GUI RPCs allowed from:
Tue 18 Jul 2017 09:38:32 AM CDT | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 8303688; resource share 100
Tue 18 Jul 2017 09:38:32 AM CDT | SETI@home | General prefs: from SETI@home (last modified 03-Apr-2013 23:59:56)
Tue 18 Jul 2017 09:38:32 AM CDT | SETI@home | Computer location: home
Tue 18 Jul 2017 09:38:32 AM CDT | SETI@home | General prefs: no separate prefs for home; using your defaults
Tue 18 Jul 2017 09:38:32 AM CDT | | Reading preferences override file
Tue 18 Jul 2017 09:38:32 AM CDT | | Preferences:
Tue 18 Jul 2017 09:38:32 AM CDT | | max memory usage when active: 24113.85MB
Tue 18 Jul 2017 09:38:32 AM CDT | | max memory usage when idle: 45816.32MB
Tue 18 Jul 2017 09:38:32 AM CDT | | max disk usage: 100.00GB
Tue 18 Jul 2017 09:38:32 AM CDT | | (to change preferences, visit a project web site or select Preferences in the Manager)
Tue 18 Jul 2017 09:38:32 AM CDT | | gui_rpc_auth.cfg is empty - no GUI RPC password protection

Right now I feel sort of like Tom and his heat struggles he's having with his Z600... Can't say that I didn't kinda expect this much wrestling with it, it _is_ Linux after all... But I was hoping. Well, any thoughts as to what might be going on here and why it doesn't appear to be happy?

*edit* Didn't Petris special sauce do anything special to this file? It looks pretty pedestrian to my untrained eye

---

Does NVidia X Server Settings (search from Menu) show anything unusual?
I'd be interested to see if it recognizes a 950, try swapping that 1050 with another one.

Greetings Al

Need to edit the xorg.conf file to get all 5 gpu's recognised so have a look at the thread links below hopefully it will put you on the right track

https://setiathome.berkeley.edu/forum_thread.php?id=80636&postid=1855894

https://setiathome.berkeley.edu/forum_thread.php?id=80636&postid=1856503

Regards

Well, that didn't seem to work, I went into a file manager called Dolphin, navigated to the boinc-client dir, found the cc_config.xml file, opened it with something called Kate, which appears to basically be Notepad, added the contents

    <options>
        <dont_contact_ref_site>1</dont_contact_ref_site>
        <use_all_gpus>1</use_all_gpus>
        <save_stats_days>365</save_stats_days>
    </options> 

to it so it now reads:

!--
This is a minimal configuration file cc_config.xml of the BOINC core client.
For a complete list of all available options and logging flags and their
meaning see: https://boinc.berkeley.edu/wiki/client_configuration
-->
<cc_config>
<log_flags>
<task>1</task>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
</log_flags>
<options>
<dont_contact_ref_site>1</dont_contact_ref_site>
<use_all_gpus>1</use_all_gpus>
<save_stats_days>365</save_stats_days>
</options>
</cc_config>

saved it as an xml file, and now my log looks like this:

The cc_config.xml is not working. If it were the startup would look as thus;

Tue 18 Jul 2017 10:11:17 PM EDT | | Starting BOINC client version 7.4.53 for x86_64-pc-linux-gnu
Tue 18 Jul 2017 10:11:17 PM EDT | | log flags: file_xfer, sched_ops, task, sched_op_debug
Tue 18 Jul 2017 10:11:17 PM EDT | | Libraries: libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
Tue 18 Jul 2017 10:11:17 PM EDT | | Data directory: /home/tbar/BOINC
Tue 18 Jul 2017 10:11:17 PM EDT | | CUDA: NVIDIA GPU 0: GeForce GTX 1050 (driver version 375.26, CUDA version 8.0, compute capability 6.1, 1990MB, 1726MB available, 1976 GFLOPS peak)
Tue 18 Jul 2017 10:11:17 PM EDT | | CUDA: NVIDIA GPU 1: GeForce GTX 1050 (driver version 375.26, CUDA version 8.0, compute capability 6.1, 1998MB, 1958MB available, 1960 GFLOPS peak)
Tue 18 Jul 2017 10:11:17 PM EDT | | OpenCL: NVIDIA GPU 0: GeForce GTX 1050 (driver version 375.26, device version OpenCL 1.2 CUDA, 1990MB, 1726MB available, 1976 GFLOPS peak)
Tue 18 Jul 2017 10:11:17 PM EDT | | OpenCL: NVIDIA GPU 1: GeForce GTX 1050 (driver version 375.26, device version OpenCL 1.2 CUDA, 1998MB, 1958MB available, 1960 GFLOPS peak)
Tue 18 Jul 2017 10:11:17 PM EDT | SETI@home | Found app_info.xml; using anonymous platform
Tue 18 Jul 2017 10:11:17 PM EDT | | Host name: TBar-iSETI
Tue 18 Jul 2017 10:11:17 PM EDT | | Processor: 4 GenuineIntel Intel(R) Xeon(R) CPU X3330 @ 2.66GHz [Family 6 Model 23 Stepping 10]
Tue 18 Jul 2017 10:11:17 PM EDT | | 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 lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dtherm tpr_shadow vnmi flexpriority
Tue 18 Jul 2017 10:11:17 PM EDT | | OS: Linux: 3.13.0-117-generic
Tue 18 Jul 2017 10:11:17 PM EDT | | Memory: 5.81 GB physical, 14.99 GB virtual
Tue 18 Jul 2017 10:11:17 PM EDT | | Disk: 92.46 GB total, 77.27 GB free
Tue 18 Jul 2017 10:11:17 PM EDT | | Local time is UTC -4 hours
Tue 18 Jul 2017 10:11:17 PM EDT | | Config: simulate 4 CPUs
Tue 18 Jul 2017 10:11:17 PM EDT | | Config: run apps at regular priority
Tue 18 Jul 2017 10:11:17 PM EDT | | Config: report completed tasks immediately
Tue 18 Jul 2017 10:11:17 PM EDT | | Config: use all coprocessors
Tue 18 Jul 2017 10:11:17 PM EDT | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 6906726; resource share 100
Tue 18 Jul 2017 10:11:17 PM EDT | SETI@home | General prefs: from SETI@home (last modified 19-Dec-2016 05:57:28)
Tue 18 Jul 2017 10:11:17 PM EDT | SETI@home | Computer location: home
Tue 18 Jul 2017 10:11:17 PM EDT | SETI@home | General prefs: no separate prefs for home; using your defaults
Tue 18 Jul 2017 10:11:17 PM EDT | | Reading preferences override file

Try removing the part in Red. If that doesn't work, try my suggestion about using an Existing .xml file and just saving the results, not doing a Save AS.

The BOINC client version 7.4.53 I'm running Now has the same problem as all the others above 7.2.42. The Task Page jumps to the bottom on Random scheduler Updates (RPC Events).
If anyone else wants to test their BOINC Manager, go to the Tasks Tab and sort it by Progress with the Active tasks at the Top of the page. See how long they stay at the Top of the page.
On the ones I've tested, they don't stay there long.

Thanks for the suggestions guys, tomorrow morning I'll check my work when I get back in. I had to bail, had enuf for one evening, and the A/C was on the fritz to boot. The unit up on the roof apparently needs a board, it looks like it was partially damaged when the disconnect on it dead shorted (480v!) this spring due to corrosion, and now running the A/C looks to have done it in. 85 degrees in there, even with a fan, with a couple computers pumping it out, well, it gets to be a bit much after a while, especially when you're frustrated and seemingly not making any forward progress. So, I figured it was a good time to walk away and wait for some good suggestions here, and look at it with fresh eyes in the morning. Thanks again, I'll let you know how it goes.

---

You know what? I think it's time to pug the plug on the first install of Mint. I think you have a really good idea of how to do things right now. That ID has no history or tasks, so it's time ...

AND what you're going to end up with is a Hack-a-Cinnamon which at some time in future updates will likely rear it's ugly head at you and say no, no, no!

So compress (it retains permissions of files) the S@H folder which you have setup, you BOINC Folder .xml files which will contain your ID and what you have changed. And ZAP it!

When you reinstall BOINC, Don't start it .... copy the files back, and it should fire right up, attached to project with same ID.

My thought anyways .... 90 minutes of time, and a fresh install.

And coolbit for fan control in NVidia Panel
In Terminal ... sudo nvidia-xconfig --thermal-configuration-check --cool-bits=28 --enable-all-gpus ... after a reboot, you should have manual fan control.

And ... nvidia-smi -l ... to watch your card use, and temps.

More to follow I'm sure :)

I've tried this, but I don´t get any fan control.

Except from that, my Mint 18 installation now works correctly regarding the cinnamon desktop, before it would crash every time
i booted , it asked if I would restart the desktop but it didn't help.

First time I ran the command I got

WARNING: Unable to locate/open X configuration file.

Package xorg-server was not found in the pkg-config search path.
Perhaps you should add the directory containing `xorg-server.pc'
to the PKG_CONFIG_PATH environment variable
No package 'xorg-server' found
Option "ThermalConfigurationCheck" "True" added to Screen "Screen0".
Option "ThermalConfigurationCheck" "True" added to Screen "Screen1".
New X configuration file written to '/etc/X11/xorg.conf'

After a reboot I had no fan control, but there was a lot of info that was not there before and the desktop did not crash, so I ran the command a 2nd time

Using X configuration file: "/etc/X11/xorg.conf".

WARNING: Unable to find CorePointer in X configuration; attempting to add new
CorePointer section.


WARNING: The CorePointer device was not specified explicitly in the layout;
using the first mouse device.


WARNING: Unable to find CoreKeyboard in X configuration; attempting to add new
CoreKeyboard section.


WARNING: The CoreKeyboard device was not specified explicitly in the layout;
using the first keyboard device.

Option "ThermalConfigurationCheck" "True" added to Screen "Screen0".
Option "ThermalConfigurationCheck" "True" added to Screen "Screen1".
Backed up file '/etc/X11/xorg.conf' as
'/etc/X11/xorg.conf.nvidia-xconfig-original'
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'

Clearly there is/was something not correct with the mint installation, even though BOINC runs OK.

And coolbit for fan control in NVidia Panel
In Terminal ... sudo nvidia-xconfig --thermal-configuration-check --cool-bits=28 --enable-all-gpus ... after a reboot, you should have manual fan control.
And ... nvidia-smi -l ... to watch your card use, and temps.

I've tried this, but I don´t get any fan control.

. . I think he forgot to mention to launch nvidia xconfig. and lock it to the launch bar. You will need to manually start it each time you reboot the system.
[quote]

You know what? I think it's time to pug the plug on the first install of Mint. I think you have a really good idea of how to do things right now. That ID has no history or tasks, so it's time ...

AND what you're going to end up with is a Hack-a-Cinnamon which at some time in future updates will likely rear it's ugly head at you and say no, no, no!

So compress (it retains permissions of files) the S@H folder which you have setup, you BOINC Folder .xml files which will contain your ID and what you have changed. And ZAP it!

When you reinstall BOINC, Don't start it .... copy the files back, and it should fire right up, attached to project with same ID.

My thought anyways .... 90 minutes of time, and a fresh install.

Well, think I will take your advice, I have some time this evening, and I guess the only thing I don't know about is archiving BOINC, what program should I use to do that? You know what, I think I will just blow it away, the heck with it, and start fresh. With my luck something will get put in the wrong place, or the wrong way, or who knows what, and then I'll be fighting the battle all over again. So, got the Cinnamon DL'd onto a USB stick, I will be nuking the drive and starting all over again. Fun Stuff! :-D

---

You know what? I think it's time to pug the plug on the first install of Mint. I think you have a really good idea of how to do things right now. That ID has no history or tasks, so it's time ...

AND what you're going to end up with is a Hack-a-Cinnamon which at some time in future updates will likely rear it's ugly head at you and say no, no, no!

So compress (it retains permissions of files) the S@H folder which you have setup, you BOINC Folder .xml files which will contain your ID and what you have changed. And ZAP it!

When you reinstall BOINC, Don't start it .... copy the files back, and it should fire right up, attached to project with same ID.

My thought anyways .... 90 minutes of time, and a fresh install.

Well, think I will take your advice, I have some time this evening, and I guess the only thing I don't know about is archiving BOINC, what program should I use to do that? You know what, I think I will just blow it away, the heck with it, and start fresh. With my luck something will get put in the wrong place, or the wrong way, or who knows what, and then I'll be fighting the battle all over again. So, got the Cinnamon DL'd onto a USB stick, I will be nuking the drive and starting all over again. Fun Stuff! :-D

. . It is not hard to copy your BOINC directory to another USB drive, but you can get 7zip from the repository for Linux, it works well.

. . If you choose to backup the folders are /var/lib/boinc-client and /etc/boinc-client

Stephen

.

Hi Al,

I’m pretty sure this makes you the resident Mint expert. Congrats ;-)

Cheers
Mark

---

. . I think he forgot to mention to launch nvidia xconfig. and lock it to the launch bar. You will need to manually start it each time you reboot the system.

If you mean the NVIDIA X Server Settings, you should be able to put that in your Startup Applications, so manual start isn't needed.

Hi Al,

I’m pretty sure this makes you the resident Mint expert. Congrats ;-)

Cheers
Mark

God help us all....

---