Tested finaly:

Houdini DSO error on 'libnvidia-ml.so'
libnvidia-ml.so: cannot open shared object file: No such file or directory
Houdini DSO error on '/usr/lib64/libnvidia-ml.so'
/usr/lib64/libnvidia-ml.so: cannot open shared object file: No such file or directory
KarmaXPU: Failed to load CUDA DSO
KarmaXPU: Found 1 total devices
KarmaXPU: Device 0 Info: Embree CPU device

I've tested on latest priduction build 20.0.688
Nvidia 550.67


I seems to have it fixed.. I just copied libnvidia-ml.so.1 to libnvidia-ml.so in that /usr/lib64 folder...

Mirko, it seems to me that Fedora uses different paths to store NVIDIA libraries than Debian does. But it's the same path problem, where libnvidia-ml.soisn't in the same place as libcuda.so.

You can ping the support using my bug report #151421. Because manually creating a symlink or copying a file is just an improvised solution, which may hit you back on the nearest system or nvidia-driver upgrade. Unless you remember to remove the symlink/file before initiating the process.

I've put some code in 20.0.699 to look for both libnvidia-ml.soand libnvidia-ml.so.1Please let me know if that sorts out all issues
thanks guys

Getting a little late to the discussion but I start to have issues to render on viewport or render gallery, it is crashing.

It is not everything but things that was working on previews versions are making Houdini crash now, not sure if it is a driver thing.

I am using Fedora 40, Houdini 20 build 688 NVIDIA driver 550.78

Render on Mplay is working fine.

brians
I've put some code in 20.0.699 to look for both libnvidia-ml.soand libnvidia-ml.so.1Please let me know if that sorts out all issues
thanks guys

Still working fine on Debian. No regressions. Hopefully it also resolves the issue on Fedora.
Thanks again for the fix, Brians.

mzigaib
Getting a little late to the discussion but I start to have issues to render on viewport or render gallery, it is crashing.
It is not everything but things that was working on previews versions are making Houdini crash now, not sure if it is a driver thing.
I am using Fedora 40, Houdini 20 build 688 NVIDIA driver 550.78

No idea what this is sorry.
Please put together a repro scene + clear steps, and file a bug report.
thanks very much

I've just tested 20.0.702 daily build and it finally works fine without any manual fixes on my side. both GPUs detected properly and working.

One more update on this issue.
I've run into problems with maya on same machine as well, now tested rocky linux and everything seems to work fine including Houdini 20.0.653 that had problems detecting GPUs on Nobara 39 (fedora 39), so seems like fedora hade some changes implemented or something. If it makes any sense. In any case. Rocky Linux 9.4 here at the moment and everything seems to work just fine

I am having a issue on Fedora rendering ocean procedural on Solaris on viewport, rendering on Mplay works fine and it is both XPU and GPU I think this some OS update issue because on Windows is working fine.

mzigaib
Getting a little late to the discussion but I start to have issues to render on viewport or render gallery, it is crashing.

It is not everything but things that was working on previews versions are making Houdini crash now, not sure if it is a driver thing.

I am using Fedora 40, Houdini 20 build 688 NVIDIA driver 550.78

Render on Mplay is working fine.

This is likely unrelated, but I came here looking for "550.78" and this was the only reference I could find.

Having all sorts of crash drama here since I've upgraded to this driver, and Rocky9.4.

G

keyframe
Having all sorts of crash drama here since I've upgraded to this driver, and Rocky9.4.

when you say "crash", what do you mean?
- all of houdini crashes?
- or just the optix device fails?

any crashlogs or error messages?

I was working fine on a ocean project until this driver update só I am betting it is driver related.

Both, currently.

If I attempt to load an HDR map into an environment map, I get an instacrash.

When I attempt to render into a redshift renderview, I get an instacrash.

commandline renders run as intended.

mzigaib
I was working fine on a ocean project until this driver update só I am betting it is driver related.

FWIW, I tried rolling back to an older driver, and got no love either.