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.

im also having this issue, im wondering if updating to the latest build of redshift caused it? trying without the redshift package to see if it makes a difference.

yep, that did it. latest redshift is breaking karma somehow...

Probably a path thing.
Is redshift adding itself to your path before the Houdini stuff?
if so, try moving it to the back.

if using packages, how would that work?

Are you on windows?
If so, you can see what's in your path (ie directory search list) via the "System Properties" dialog.

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...

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)

I'm Having this same issue, Redshift is bricked right now.

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!

I tried but it just said "KarmaXPU: Unable to initialize NVRTC" after I set the variable.
I disabled Redshift for Solaris as well but no such luck.

I am also seeing this, is the option to rollback to the older version of redshift?

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!

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.

Ah! a smoking gun!
We're somehow picking up this DLL from the Redshifts install, instead of hfs/bin.
I'll let you know when we have a fix in place
thanks!

I've made a change to 19.5.421 that should make the loading of the NVRTC dll more robust for when the system search path is modified by other plugins.

Please let me know if 19.5.421 fixes this Redshift issue
thanks!

Thank you Brians!!
I will check when a windows daily build will be out, for now is just 19.5.420 version.

Hi guys

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!

Hi Brians,
I didn't get the message for now, seeams to be good for me

Thank you

Great! thanks!