BOINC encodes the driver number into an integer in a way that assumes the minor
number is < 100.
This is bad, of course - BOINC has no business encoding other peoples' version
numbers -
but fixing it is not easy.
That's because the plan classes used by projects refer to
driver version numbers using these encoded integers.
If we change the representation of version it might break these projects.
Projects: do you in fact have plan classes that use nvidia driver version?
-- David
On 1/13/2018 8:31 PM, TarotApprentice wrote:
The CUDA device driver version number is being truncated.
Background: Nvidia released CUDA driver 384.111 (for Linux) to resolve one of the
Spectre variants. The minor version number of 111 is being truncated to two digits
(ie 11). The OpenCL detection seems to get it right though.
Event log:
14-01-2018 03:04 PM Starting BOINC client version 7.8.4 for x86_64-pc-linux-gnu
14-01-2018 03:04 PM log flags: file_xfer, sched_ops, task
14-01-2018 03:04 PM Libraries: libcurl/7.52.1 OpenSSL/1.0.2l zlib/1.2.8
libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
14-01-2018 03:04 PM Data directory: /var/lib/boinc-client
14-01-2018 03:04 PM CUDA: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version
384.11, CUDA version 9.0, compute capability 6.1, 3014MB, 2918MB available, 3936
GFLOPS peak)
14-01-2018 03:04 PM OpenCL: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version
384.111, device version OpenCL 1.2 CUDA, 3014MB, 2918MB available, 3936 GFLOPS peak)
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
