To your 2) ? "version of BOINC Manager that would allow me to change the number of application tasks depending on each GPU or class of GPUs."
There is a way to run different GPUs with the settings they each like.
Set up a plethora (multiple) of boinc clients on the same machine!
Each of them will have a ....xml file where you can tell 'use/do not use' gpu 1, 2, n, m, and the other boinc instances will obey their own set of rules set by their individual ...xml files.
I have not done that myself, but I have read it is possible.
If I'm correct it is possible to run one GPU with one boinc - should you have N boinc instances runnig (each in its own directory/folder).
Those who know better can correct/clarify me. (Please!!)
To your 2) ? "version of BOINC Manager that would allow me to change the number of application tasks depending on each GPU or class of GPUs."
if you have something like a mixed nvidia/AMD system, you can setup different parameters this way in the app_config since the application and plan class will be different for nvidia vs AMD/"ati" using the <app_version> flag in app_config. see the specifics here: https://boinc.berkeley.edu/wiki/Client_configuration
otherwise you have to setup multiple BOINC instances as mentioned above, but this comes with the caveat that it splits up your stats into "logical" hosts.
it would be nice if BOINC had some tighter project level configuration on a per device level (not just by plan class or type). For example one of my systems has an RTX 3070 with a GTX 1660Super. I get a little better production with the RTX3070 running 2x, but the GTX1660S occasionally will freeze up when running 2x, and doesnt see much benefit in doing so. So I want to run the RTX3070 at 2x but the 1660S at 1x on the same GR app without splitting the host into two instances, but at the moment BOINC just can't be configured this way since they both have the same plan class and the same app. the only solution for my situation is to give up some production and run 1x to avoid the occasional freezing on my 1660S
Keith,I have now skimmed the thread. Once I have re-created the inability to run an Rx 570/580 card and an Rx 5700 card under Ubuntu 2.0 I will see if I can correctly explain what I did and how it is not working.
It appears my Boinc Manager (I run the A-I-O under Linux) may not be working.
If you feel brave, maybe you can try out the new BoincTasks-Js application from eFMer.
He announced it awhile ago today on the BOINC website Questions and Answers forum.
I tried the Snap install and it didn't work because of missing dependencies.
But the normal Debian install via a regular .deb file worked fine.
But I can't get it to connect to any of my hosts. Seems it is looking for a regular stock Linux BOINC installation in /var/lib/boinc/ which I don't use since I run the AIO version.
But since that is how you installed your latest version, maybe you can give the new Javascript version of BoincTasks a tryout and see if it works for you.
If you feel brave, maybe you can try out the new BoincTasks-Js application from eFMer.
While I am not feeling brave I am feeling motivated. Will investigate.
I can now see a clear path to a 9 GPU system without buying another larger mining rack. 5 Rx 5700's, 2 Rx 580's, and 2 Rx 570's. Just have to get those pesky riser cards combo's all working (ordered 4 more this morning).
This does mean the box that is currently running the 5 Rx 5700's is going to have to start subsisting on two Rx 570's. But it also means I might make it to a much higher RAC (plus two 1600 watt PSU's?).
Tom M
A Proud member of the O.F.A. (Old Farts Association).
After running into assorted gpu hardware glitches that required "cable" troubleshooting I ended up with 9 Amd video cards on one box.
And then the dreaded "Logon Loop" struck. There are still to many ways Linux/Ubuntu can end up with those symptoms. So I swapped HD's and now have the rig running under a "test" version of Windows 10.
And was able to issue an (automated) Amd driver bug report shortly thereafter.
I now have the joy, once again, of having so many gpu tasks active I can't get them on one screen (dinky/old/modest sized) of my Monitor :)
Tom M
A Proud member of the O.F.A. (Old Farts Association).
Just in case you didn't know,
)
Just in case you didn't know, Bridgman is an AMD Linux developer. He should know of what he speaks.
Hi TOM M, To your
)
Hi TOM M,
To your 2) ? "version of BOINC Manager that would allow me to change the number of application tasks depending on each GPU or class of GPUs."
There is a way to run different GPUs with the settings they each like.
Set up a plethora (multiple) of boinc clients on the same machine!
Each of them will have a ....xml file where you can tell 'use/do not use' gpu 1, 2, n, m, and the other boinc instances will obey their own set of rules set by their individual ...xml files.
I have not done that myself, but I have read it is possible.
If I'm correct it is possible to run one GPU with one boinc - should you have N boinc instances runnig (each in its own directory/folder).
Those who know better can correct/clarify me. (Please!!)
--
petri33
Yes, that is the correct
)
Yes, that is the correct method to run different gpu parameters/projects with concurrent independent BOINC instances.
https://www.overclock.net/threads/guide-setting-up-multiple-boinc-instances.1628924/
petri33 wrote: To your 2) ?
)
if you have something like a mixed nvidia/AMD system, you can setup different parameters this way in the app_config since the application and plan class will be different for nvidia vs AMD/"ati" using the <app_version> flag in app_config. see the specifics here: https://boinc.berkeley.edu/wiki/Client_configuration
otherwise you have to setup multiple BOINC instances as mentioned above, but this comes with the caveat that it splits up your stats into "logical" hosts.
it would be nice if BOINC had some tighter project level configuration on a per device level (not just by plan class or type). For example one of my systems has an RTX 3070 with a GTX 1660Super. I get a little better production with the RTX3070 running 2x, but the GTX1660S occasionally will freeze up when running 2x, and doesnt see much benefit in doing so. So I want to run the RTX3070 at 2x but the 1660S at 1x on the same GR app without splitting the host into two instances, but at the moment BOINC just can't be configured this way since they both have the same plan class and the same app. the only solution for my situation is to give up some production and run 1x to avoid the occasional freezing on my 1660S
_________________________________________________________________________
Tom M wrote:Keith,I have now
)
It appears my Boinc Manager (I run the A-I-O under Linux) may not be working.
Here is the results of: lspci | grep VGA
And here is the first 30 odd lines of my Boinc Mgr log.
So apparently it is not a driver issue. Apparently it is a Boinc Mgr.
I could "revert" to the generic Ubuntu install for the Boinc Mgr system.
I could try out "Pandora". I could download yet another copy of Tbar's All-In-One.
Any other ideas? I will start with another download of the AIO archive.
====edit===
The link on the GPUUG page to the Wiki via S@H seems to have stopped working. So I can't download another copy.
===edit====
Apparently the Rx 5700 is not being recognized at all. Will try adding the OCL driver manually like we used to have to do with the Nvidia cards.
Nope.
===edit===
Installed the generic Ubuntu version of Boinc client/manager.
And figured out where the cc_config.xml file lives.
Now have a mixed rx 570 (2) and rx 5700 (1) running on system.
Now to find where the app_config.xml files live.
===edit---
Tom M
A Proud member of the O.F.A. (Old Farts Association).
Tom M wrote: Installed the
)
The app_config.xml file lives in: tom@gpu-server:/var/lib/boinc/projects/einstein.phys.uwm.edu$
And I now have 3 gpu Gamma Ray tasks per GPU running on the gpu-server (Ubuntu).
I am much more used to the AIO from a compaq and non-security conscious form.
Tom M
A Proud member of the O.F.A. (Old Farts Association).
If you feel brave, maybe you
)
If you feel brave, maybe you can try out the new BoincTasks-Js application from eFMer.
He announced it awhile ago today on the BOINC website Questions and Answers forum.
I tried the Snap install and it didn't work because of missing dependencies.
But the normal Debian install via a regular .deb file worked fine.
But I can't get it to connect to any of my hosts. Seems it is looking for a regular stock Linux BOINC installation in /var/lib/boinc/ which I don't use since I run the AIO version.
But since that is how you installed your latest version, maybe you can give the new Javascript version of BoincTasks a tryout and see if it works for you.
Just another datapoint for Fred to debug.
Keith Myers wrote: If you
)
While I am not feeling brave I am feeling motivated. Will investigate.
I can now see a clear path to a 9 GPU system without buying another larger mining rack. 5 Rx 5700's, 2 Rx 580's, and 2 Rx 570's. Just have to get those pesky riser cards combo's all working (ordered 4 more this morning).
This does mean the box that is currently running the 5 Rx 5700's is going to have to start subsisting on two Rx 570's. But it also means I might make it to a much higher RAC (plus two 1600 watt PSU's?).
Tom M
A Proud member of the O.F.A. (Old Farts Association).
After running into assorted
)
After running into assorted gpu hardware glitches that required "cable" troubleshooting I ended up with 9 Amd video cards on one box.
And then the dreaded "Logon Loop" struck. There are still to many ways Linux/Ubuntu can end up with those symptoms. So I swapped HD's and now have the rig running under a "test" version of Windows 10.
And was able to issue an (automated) Amd driver bug report shortly thereafter.
I now have the joy, once again, of having so many gpu tasks active I can't get them on one screen (dinky/old/modest sized) of my Monitor :)
Tom M
A Proud member of the O.F.A. (Old Farts Association).
You should never get a "logon
)
You should never get a "logon loop" problem if you do one simple thing to preempt it.
I have told you multiple times but you seem to forget every install you do.