-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gpu-burn compiled using nvidia-toolkit 12.3 fails, had to recompile using nvidia-cuda-toolkit 11.5 #94
Comments
So basically the difference seems (for now, maybe I'm missing something?) to be the first time it compiled and failed to run it was using cuda-toolkit 12.3, and the second time, cuda-toolkit 11.5. The hosted version in the Ubuntu repos lags behind the upstream NVIDIA repos, but all the cuda packages are 12.3 otherwise. Any idea where to start here? I'm happy to do whatever necessary to figure this out and resolve it. |
Have you had a chance to look at this any @wilicc ? the version I used won't hang around forever, and NVIDIA keeps moving cuda toolkit onwards. The compilation seems to pass just fine, but the execution has the errors mentioned... if I'm doing something wrong, I'm happy to help with providing log info or whatever. |
I just tried this with 12.3 and it seems to be working fine. Typically the problems I have when moving to newer version is that older compute capabilities are deprecated, which is not the error you are getting. |
Hrmmmm ok, I'll look at that. The toolchain should be fine as the whole
thing was installed initially from the CUDA repos. I wasn't aware that
there was also an issue if hte driver itself wasn't compiled with the same
toolchain. I'll refer back to the person who maintains the driver (and
probably need to also retry this using the upstream driver as well to
confirm that the problem is there. Thanks for that pointer.
…On Wed, Dec 13, 2023 at 3:55 AM Ville Timonen ***@***.***> wrote:
I just tried this with 12.3 and it seems to be working fine. Typically the
problems I have when moving to newer version is that older compute
capabilities are deprecated, which is not the error you are getting.
To me it looks like your CUDA toolchain does not match the NVidia driver
you have installed. Or some other mismatch between nvcc compiler version
and runtime.
—
Reply to this email directly, view it on GitHub
<#94 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAYWSEC3JU2S265WKGB64DYJFUQPAVCNFSM6AAAAABAGNQP62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJTGUYDMMBZGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Jeff Lane - Engineering Manager, Tools Developer, Warrior Poet, Lover of Pie
Ubuntu Ham: W4KDH
Freenode IRC: bladernr or bladernr_
gpg: 1024D/3A14B2DD 8C88 B076 0DD7 B404 1417 C466 4ABD 3635 3A14 B2DD
|
I had the same problem on Debian testing; upgrading nvidia-cuda-toolkit to match the driver version fixed the problem. (I installed cuda from the run files some time ago, which appears to have been the culprit). |
and now gpu-burn is packaged in debian officially, well non-free of it... |
I also encountered this problem. After my testing, just recompile it. I guess your CUDA or driver has been updated, so you need to recompile GPU-burn. |
I installed gpu-burn on an machine and as part of the setup installed cuda-toolkit which got me this:
but when I ran gpu-burn to sniff test everything was read, it errored out:
i then installed nvidia-cuda-toolkit (packaged in the ubuntu repos):
and recompiled gpu-burn
$ sudo make clean
and that finally succeeded
The text was updated successfully, but these errors were encountered: