Hey all!
anybody knows why I would get an " unable to initialize NVRTC" issue
I know it has to do with the graphics card I'm also not able to render with redshift
I'm using Nvidia studio driver 517.40 I rolled it back to an older driver, but no dice.
at the start I used 19.5.303 but now using 19.5.368, not helping me.
also, it has nothing to do with to project that I'm working on.
not sure what's going on.
open for suggestions
thanks
thanks
edit --
well, my redshift maintenance has expired so it and (God knows why) it messes up the GPU, and karma cant uses it.
Karma XPU NVRTC Issue
8248 23 5-
- sachiman
- Member
- 39 posts
- Joined: June 2015
- Offline
-
- ChristopherRutledge
- Member
- 453 posts
- Joined: Feb. 2017
- Online
-
- ChristopherRutledge
- Member
- 453 posts
- Joined: Feb. 2017
- Online
-
- brians
- Staff
- 543 posts
- Joined: May 2019
- Offline
-
- ChristopherRutledge
- Member
- 453 posts
- Joined: Feb. 2017
- Online
-
- brians
- Staff
- 543 posts
- Joined: May 2019
- Offline
-
- ChristopherRutledge
- Member
- 453 posts
- Joined: Feb. 2017
- Online
im confused, i dont think i understand what the houdini specific env var / packages have to do with the windows system level env variables? theres nothing in my windows system enviornment variables under path that seem to pertain to houdini in any way that I can tell, i didnt think these two things were related...
-
- brians
- Staff
- 543 posts
- Joined: May 2019
- Offline
Its all the NVidia stuff.
- first we load CUDA (which in turn loads a bunch of driver stuff from the path)
- we then load NVRTC (which in turn loads a bunch of driver stuff from the path)
my thought was that redshift is somehow affecting the path.
but if the path is not changing, then perhaps its something else... (just a thought really)
- first we load CUDA (which in turn loads a bunch of driver stuff from the path)
- we then load NVRTC (which in turn loads a bunch of driver stuff from the path)
my thought was that redshift is somehow affecting the path.
but if the path is not changing, then perhaps its something else... (just a thought really)
-
- terry_williams
- Member
- 55 posts
- Joined: Sept. 2018
- Offline
-
- brians
- Staff
- 543 posts
- Joined: May 2019
- Offline
Could anyone with this issue try running with the HOUDINI_DSO_ERROR environment variable set please?
eg
export HOUDINI_DSO_ERROR=1
And let us know if they see any errors/info relating to the NVRTC binary.
eg
- what path it's attempting to load it from
- any additional error messages that might get shown.
- etc...
Windows = "nvrtc64_112_0.dll"
Linux = "libnvrtc.so"
thanks!
eg
export HOUDINI_DSO_ERROR=1
And let us know if they see any errors/info relating to the NVRTC binary.
eg
- what path it's attempting to load it from
- any additional error messages that might get shown.
- etc...
Windows = "nvrtc64_112_0.dll"
Linux = "libnvrtc.so"
thanks!
-
- terry_williams
- Member
- 55 posts
- Joined: Sept. 2018
- Offline
-
- jumax
- Member
- 85 posts
- Joined: Jan. 2009
- Offline
-
- brians
- Staff
- 543 posts
- Joined: May 2019
- Offline
19.5.415 now has improved error reporting for when the NVRTC DSO fails to load.
Hopefully you'll get some kind of error message like...
Please let us know what that message says when it pops up.
thanks very much!
Hopefully you'll get some kind of error message like...
NVRTC DynLib failed to load. name=[...] path=[...] reason=[...]
Please let us know what that message says when it pops up.
thanks very much!
Edited by brians - Oct. 25, 2022 22:56:43
-
- wanglifu
- Member
- 196 posts
- Joined: Feb. 2017
- Offline
brians
19.5.415 now has improved error reporting for when the NVRTC DSO fails to load.
Hopefully you'll get some kind of error message like...NVRTC DynLib failed to load. name=[...] path=[...] reason=[...]
Please let us know what that message says when it pops up.
thanks very much!
Here is the info,please check out.
Edited by wanglifu - Oct. 27, 2022 05:21:46
-
- brians
- Staff
- 543 posts
- Joined: May 2019
- Offline
-
- brians
- Staff
- 543 posts
- Joined: May 2019
- Offline
-
- WowNems
- Member
- 45 posts
- Joined: Oct. 2021
- Offline
-
- brians
- Staff
- 543 posts
- Joined: May 2019
- Offline
Hi guys
Any update on this? Has anyone had a chance to try out 19.5.420? (or later)
Another thing, this comment caught my attention.
I thought it was only KarmaXPU that was failing. Are you saying Redshift also failed?
cheers!
Any update on this? Has anyone had a chance to try out 19.5.420? (or later)

terrypxm
I'm Having this same issue, Redshift is bricked right now.
Another thing, this comment caught my attention.
I thought it was only KarmaXPU that was failing. Are you saying Redshift also failed?
cheers!
Edited by brians - Nov. 3, 2022 05:29:59
-
- WowNems
- Member
- 45 posts
- Joined: Oct. 2021
- Offline
-
- brians
- Staff
- 543 posts
- Joined: May 2019
- Offline
-
- Quick Links