Having BOINC report more GPUs than exist in the system is also pretty easy & doesn't require modifying any code. Just tweaking some configs.

I tried that when I found that out from the source code, however it did not work for me. That is why I had to make some modifications to the boinc client code and I wanted make it to be visible for everyone and that is why the Ti is called Tu.

I'm still a week off. (browsing through the threads and vanishing -- screaming as I distance from the real world for a week off from duty <3)

It seems to work for me.
On my host 5837483 with one R9 390X.
I originally only wanted to change the GPU display name from Radeon (TM) R9 390 Series (Hawaii) to Radeon R9 390X (Grenada XT).
The same basic method works to have BOINC report more GPUs as well. Perhaps it only works in the Windows client or with Radeon GPUs?
While running SETI@home with the config changes the server was more than happy to send the system 200 GPU tasks for the single GPU.
Since most people would use the it to bypass the limits and horde work I don't feel it it should be be openly documented. No one likes the database to get all crashy.
It's pretty simple when you understand how BOINC works with GPUs.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I gave the config mod a try on one of my notebooks and it does seem to work for CUDA & iGPUs.

10/13/2017 7:34:30 PM		CUDA: NVIDIA GPU 0: GeForce GTX 950M (driver version 384.76, CUDA version 9.0, compute capability 5.0, 2048MB, 2048MB available, 1188 GFLOPS peak)
10/13/2017 7:34:30 PM		CUDA: NVIDIA GPU 1: GeForce GTX 950M (driver version 384.76, CUDA version 9.0, compute capability 5.0, 2048MB, 2048MB available, 1188 GFLOPS peak)
10/13/2017 7:34:30 PM		OpenCL: NVIDIA GPU 0: GeForce GTX 950M (driver version 384.76, device version OpenCL 1.2 CUDA, 2048MB, 2048MB available, 1188 GFLOPS peak)
10/13/2017 7:34:30 PM		OpenCL: NVIDIA GPU 1: GeForce GTX 950M (driver version 384.76, device version OpenCL 1.2 CUDA, 2048MB, 2048MB available, 1188 GFLOPS peak)
10/13/2017 7:34:30 PM		OpenCL: Intel GPU 0: Intel(R) HD Graphics 530 (driver version 21.20.16.4542, device version OpenCL 2.0, 3225MB, 3225MB available, 202 GFLOPS peak)
10/13/2017 7:34:30 PM		OpenCL: Intel GPU 1: Intel(R) HD Graphics 530 (driver version 21.20.16.4542, device version OpenCL 2.0, 3225MB, 3225MB available, 202 GFLOPS peak)
10/13/2017 7:34:30 PM		OpenCL: Intel GPU 2: Intel(R) HD Graphics 530 (driver version 21.20.16.4542, device version OpenCL 2.0, 3225MB, 3225MB available, 202 GFLOPS peak)

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

It seems to work for me.
On my host 5837483 with one R9 390X.
I originally only wanted to change the GPU display name from Radeon (TM) R9 390 Series (Hawaii) to Radeon R9 390X (Grenada XT).
The same basic method works to have BOINC report more GPUs as well. Perhaps it only works in the Windows client or with Radeon GPUs?
While running SETI@home with the config changes the server was more than happy to send the system 200 GPU tasks for the single GPU.
Since most people would use the it to bypass the limits and horde work I don't feel it it should be be openly documented. No one likes the database to get all crashy.
It's pretty simple when you understand how BOINC works with GPUs.

. . Sigh! :(

. . It seems I am destined to continue rescheduling tasks every Tuesday :(

Stephen

:(

I gave the config mod a try on one of my notebooks and it does seem to work for CUDA & iGPUs.

. . Tease! :)

Stephen

:)

I gave the config mod a try on one of my notebooks and it does seem to work for CUDA & iGPUs.

. . Tease! :)

Stephen

:)

Even if many users tried to go nuts I seem to recall there is a hard limit in the scheduler code where it will only assign work for up to 32 GPUs. No matter how many are reported by the client.

13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 0: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 1: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 2: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 3: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 4: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 5: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 6: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 7: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 8: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 9: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 10: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 11: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 12: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 13: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 14: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 15: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 16: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 17: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 18: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 19: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 20: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 21: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 22: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 23: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 24: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 25: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 26: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 27: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 28: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 29: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 30: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)
13-Oct-2017 19:26:58 [---] OpenCL: ATI GPU 31: ATI Radeon HD 6870 (Barts XT) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 4032 GFLOPS peak)

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

. . Tease! :)
Stephen
:)

Even if many users tried to go nuts I seem to recall there is a hard limit in the scheduler code where it will only assign work for up to 32 GPUs. No matter how many are reported by the client.

. . Hi Hal,

. . I'm guessing that begging and grovelling wouldn't help either ??

Stephen

:)

Bleh. Wish I knew more about linux to get it running on my two 1080's.

Bleh. Wish I knew more about linux to get it running on my two 1080's.

Setting up a Linux machine to crunch CUDA80 for Windows users.

---

Grant
Darwin NT

Nothing against Linux or defending M$ WIndows but what we realy need is some code expert who transport the highly optimized code from linux to windows.

We all know Windows $uck$!!! but for old guy´s like me it´s hard to learn a new OS.

---

. . Hi Hal,

. . I'm guessing that begging and grovelling wouldn't help either ??

Stephen

:)

If it helps, I'll take part in the begging and grovelling ;)

Yeah I've been trying to get different flavors of linux running in a dual boot configuration. So far none of them like this computer. Grub problems (ubuntu) so I had to manually select which OS to boot from the bios, no video because it doesn't like SLI(mint), didn't wanna partition an NVME SSD(red hat), couldn't get the cuda support package running right if I installed it on a regular HDD so it would only CPU crunch.. just a general pain in the ass all around. I was fooling with it for close to a week - the only marginal success I had was putting them into a virtual machine, but hey, no gpu passthrough because windows sucks so there's no point there.

Nothing against Linux or defending M$ WIndows but what we realy need is some code expert who transport the highly optimized code from linux to windows.

We all know Windows $uck$!!! but for old guy´s like me it´s hard to learn a new OS.

. . This has been discussed many times and while some say it is easy to do it does not get done. Others say the reason is because it is still not ready for general release. So for the time being it will require biting the bullet and coming to terms with Linux if you want to try it.

Stephen

:(

Yeah I've been trying to get different flavors of linux running in a dual boot configuration. So far none of them like this computer. Grub problems (ubuntu) so I had to manually select which OS to boot from the bios, no video because it doesn't like SLI(mint), didn't wanna partition an NVME SSD(red hat), couldn't get the cuda support package running right if I installed it on a regular HDD so it would only CPU crunch.. just a general pain in the ass all around. I was fooling with it for close to a week - the only marginal success I had was putting them into a virtual machine, but hey, no gpu passthrough because windows sucks so there's no point there.

. . Hi,

. . You could read the thread that Grant pointed to a little earlier. But basically what I did to avoid interaction between the two OS's was to invest in a 32GB flashdrive (many are fairly inexpensive) and used one of my existing 8GB drives and used Rufus to create a Linux LIVE install drive on the 8GB unit ( makes it very fast) and installed to the 32GB unit as a stand alone drive. I have learned since then that Linux is a nice dual boot launcher in itself and while running alone and not touching the Windows drive it recognises that the Windows OS is available and will allow you to select to boot from it.

. . Go with the disk format EXT4 and most things seems to work from there. There are still some pitfalls, mainly to do with ownership and permissions for files and folders, but people have posted lots of useful info in that thread. The big thing to make it easier for you is to stick with TBar's advice and go with Ubuntu 14.04 and the SETI version of BOINC not the Repository one. That will avoid many headaches.

Stephen

:)

Yeah I've been trying to get different flavors of linux running in a dual boot configuration. So far none of them like this computer. Grub problems (ubuntu) so I had to manually select which OS to boot from the bios, no video because it doesn't like SLI(mint), didn't wanna partition an NVME SSD(red hat), couldn't get the cuda support package running right if I installed it on a regular HDD so it would only CPU crunch.. just a general pain in the ass all around. I was fooling with it for close to a week - the only marginal success I had was putting them into a virtual machine, but hey, no gpu passthrough because windows sucks so there's no point there.

. . Hi,

. . You could read the thread that Grant pointed to a little earlier. But basically what I did to avoid interaction between the two OS's was to invest in a 32GB flashdrive (many are fairly inexpensive) and used one of my existing 8GB drives and used Rufus to create a Linux LIVE install drive on the 8GB unit ( makes it very fast) and installed to the 32GB unit as a stand alone drive. I have learned since then that Linux is a nice dual boot launcher in itself and while running alone and not touching the Windows drive it recognises that the Windows OS is available and will allow you to select to boot from it.

. . Go with the disk format EXT4 and most things seems to work from there. There are still some pitfalls, mainly to do with ownership and permissions for files and folders, but people have posted lots of useful info in that thread. The big thing to make it easier for you is to stick with TBar's advice and go with Ubuntu 14.04 and the SETI version of BOINC not the Repository one. That will avoid many headaches.

Stephen

:)

Perhaps you should try reading *my* post. Specifically the part that mentioned that ubuntu and grub weren't getting along on my computer with windows 10. There was literally no solution that I could find that would work in my instance. I tried over 15 different distros in various configurations and the best I could do to get it running at all was on a virtual machine. It just doesn't like my hardware configuration, period.

Perhaps you should try reading *my* post. Specifically the part that mentioned that ubuntu and grub weren't getting along on my computer with windows 10. There was literally no solution that I could find that would work in my instance. I tried over 15 different distros in various configurations and the best I could do to get it running at all was on a virtual machine. It just doesn't like my hardware configuration, period.

. . Sorry that was of no help to you ....

Stephen

??