Author |
Message |
|
Yes, this was only testing the current plan_class with Cuda111 while there are some different things in config. It looks like the app was not compiled with cc7 but cc6. For cc10 we will have a separate app of course.
your current cuda120 app seems to support 5.0 (maybe, dont have any to test), 6.0, 6.1, 7.5, 8.6, 8.9, neglecting 7.0.
it seems clear that the project is only looking at the driver version or embedded cuda version for deciding which app to send. using an app_config WILL NOT WORK.
could you recompile the cuda120 app to include ALL CCs and add in 7.0? |
|
|
rebirtherVolunteer moderator Project administrator Project developer Project tester Project scientist
![Avatar](http://www.gravatar.com/avatar/7466455f8af25f39a89640c7f6e36c01?s=100&d=identicon) Send message
Joined: 2 Jan 13 Posts: 7346 Credit: 42,730,867 RAC: 5
|
Yes, this was only testing the current plan_class with Cuda111 while there are some different things in config. It looks like the app was not compiled with cc7 but cc6. For cc10 we will have a separate app of course.
your current cuda120 app seems to support 5.0 (maybe, dont have any to test), 6.0, 6.1, 7.5, 8.6, 8.9, neglecting 7.0.
it seems clear that the project is only looking at the driver version or embedded cuda version for deciding which app to send. using an app_config WILL NOT WORK.
could you recompile the cuda120 app to include ALL CCs and add in 7.0?
Need to ask, windows and linux can be different. |
|
|
|
ok I was able to force it to send me the cuda11 app by manually editing the coproc_info.xml and making it say i only had CUDA 11 support. then I marked the file immutable.
This app seems to work with CC 7.0, but the project never naturally sends this. not many folks know how to exploit BOINC in this way and doing so has rammifications for other projects that will want higher CUDA support from the client.
please recompile the CUDA 12 app or reconfigure the server to check the CC version of the GPUs from the client (it's transmitted in the coproc info) |
|
|
|
Yes, this was only testing the current plan_class with Cuda111 while there are some different things in config. It looks like the app was not compiled with cc7 but cc6. For cc10 we will have a separate app of course.
your current cuda120 app seems to support 5.0 (maybe, dont have any to test), 6.0, 6.1, 7.5, 8.6, 8.9, neglecting 7.0.
it seems clear that the project is only looking at the driver version or embedded cuda version for deciding which app to send. using an app_config WILL NOT WORK.
could you recompile the cuda120 app to include ALL CCs and add in 7.0?
Need to ask, windows and linux can be different.
I'm talking about the Linux cuda120 app |
|
|
rebirtherVolunteer moderator Project administrator Project developer Project tester Project scientist
![Avatar](http://www.gravatar.com/avatar/7466455f8af25f39a89640c7f6e36c01?s=100&d=identicon) Send message
Joined: 2 Jan 13 Posts: 7346 Credit: 42,730,867 RAC: 5
|
Yes, this was only testing the current plan_class with Cuda111 while there are some different things in config. It looks like the app was not compiled with cc7 but cc6. For cc10 we will have a separate app of course.
your current cuda120 app seems to support 5.0 (maybe, dont have any to test), 6.0, 6.1, 7.5, 8.6, 8.9, neglecting 7.0.
it seems clear that the project is only looking at the driver version or embedded cuda version for deciding which app to send. using an app_config WILL NOT WORK.
could you recompile the cuda120 app to include ALL CCs and add in 7.0?
Need to ask, windows and linux can be different.
I'm talking about the Linux cuda120 app
yes, compiling is in progress. |
|
|
rebirtherVolunteer moderator Project administrator Project developer Project tester Project scientist
![Avatar](http://www.gravatar.com/avatar/7466455f8af25f39a89640c7f6e36c01?s=100&d=identicon) Send message
Joined: 2 Jan 13 Posts: 7346 Credit: 42,730,867 RAC: 5
|
v39 with cc7 is up for linux |
|
|
|
will try. thanks! |
|
|
|
it seems to be working. |
|
|