Difference between revisions of "Postponed: CUDA device initialisation failed"
From BOINC Wiki
(adding new FAQ) |
(adding break) |
||
| Line 2: | Line 2: | ||
Seen in combination with [[Couldn%27t_get_cuda_device_count_in_file_%27/PATH/cudaAcceleration.cu%27_in_line_N:_no_CUDA-capable_device_is_detected.|Couldn't get cuda device count in file '/PATH/cudaAcceleration.cu' in line N: no CUDA-capable device is detected.]]<br> | Seen in combination with [[Couldn%27t_get_cuda_device_count_in_file_%27/PATH/cudaAcceleration.cu%27_in_line_N:_no_CUDA-capable_device_is_detected.|Couldn't get cuda device count in file '/PATH/cudaAcceleration.cu' in line N: no CUDA-capable device is detected.]]<br> | ||
This happens when you do have an Nvidia GPU, but it isn't CUDA capable, its driver hasn't loaded correctly or the user running the GPU driver does not have the correct permission to do so. <br> | This happens when you do have an Nvidia GPU, but it isn't CUDA capable, its driver hasn't loaded correctly or the user running the GPU driver does not have the correct permission to do so. <br> | ||
| + | <br> | ||
BOINC suspends the CUDA device initialisation until this is fixed.<br> | BOINC suspends the CUDA device initialisation until this is fixed.<br> | ||
</div> | </div> | ||
Revision as of 16:00, 12 September 2016
Seen in combination with Couldn't get cuda device count in file '/PATH/cudaAcceleration.cu' in line N: no CUDA-capable device is detected.
This happens when you do have an Nvidia GPU, but it isn't CUDA capable, its driver hasn't loaded correctly or the user running the GPU driver does not have the correct permission to do so.
BOINC suspends the CUDA device initialisation until this is fixed.
