-
Notifications
You must be signed in to change notification settings - Fork 255
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
No CUDA device found; using CPU as fallback. #609
Comments
Hello @Fedomer, Sionna uses Mitsuba for its ray tracing capabilities, which itself uses OptiX under the hood. |
Hello @merlinND , NB: podman use the flags of docker and works fine for rapids images. |
Glad it worked! |
Hello @merlinND , the "No CUDA device found; " appears when I do : import sionna |
could you please run this inside the docker container and give us the result?
|
Hi @gmarcusm thanks, also with import sionna:
it seems that Tensorflow is not GPU enabled! but it's the official build with the dockerfile provided. |
Upgraded news Docker container seems load fine sionna package (with cuda) in a computer with Ubuntu 20.04LTS and Nvidia A5000 card with driver: Other container with more recent tensorflow, Rapids works fine. Still investigating...... ** ... after some investigating** |
Hi @Fedomer did you solve this issue? Were you able to get it to work on Redhat Linux? I am facing the same problem. TF by itself is able to find a GPU but once I pip install sionna it is not able to find a GPU anymore. Not sure if Sionna downgrades the TF version and messes up things in the process. |
Hello @csankar69 , for the moment I'm using Docker because I Think it's a problem about GPU podman management or a bad configuration for Sionna. I'm waiting a new Server wit redHat and I will try again. RedHat can't solve the problem. |
First use and just at the first line [1]:
GPU Configuration and Imports in the tutorial Sionna_Ray_Tracing_Introduction was not found.
No CUDA device found; using CPU as fallback.
but !nvidia-smi print:
I use a container with the docker image.
Other Rapids docker images works fine.
drivers pb????
The text was updated successfully, but these errors were encountered: