-
Notifications
You must be signed in to change notification settings - Fork 174
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
Extreme (as in, this is extremely frustrating) dependency conflict: CUDA 12.4, torch 2.5.1
, onnxruntime-gpu==1.20.1
#495
Comments
Try to downgrade Cuda to 12.1 |
Thanks for the info, but downgrading is really a problematic option, both for the risk of even more conflicts with other libraries and the fact that the cloud provider I'm invested only has 12.4 images, which means I'd have to run docker on top of the installation. After running several updates, I got to this point (notice slightly different error message)… Can you make anything else out of it?
Thanks! |
First, confirm
What happened?
Hi,
AFAIK the main issue with CUDA 12.x is older versions of
onnxruntime-[gpu]
, so when I got one of those error messages, I went around searching and found that the latest stable version available for my system (Ubuntu Linux on AMD CPU, Nvidia A6000 GPU) is 1.20.1. According to Microsoft, it should work with any 12.x CUDA version that they know of sinceonnxruntime-gpu 1.19.0
, and I'm on1.20.1
… and yet…… and so on, and so forth…
My status is:
DWPose nodes (can't recall the package name) for Comfy , which are usually super-picky about the
onnxruntime-gpu
version, report GPU acceleration is detected just fine.Can anyone help please?
Steps to reproduce the problem
torch 2.5.1 CUDA 12.4 cuDNN 9.2.1
comfyui-reactor-node
package and run itsinstall.py
onnxruntime-gpu
installed first, currently version1.20.1
(installer sees correct versions oftorch
& CUDA).Appreciate any help you guys can give!
Sysinfo
Relevant console log
System Information
Devices
Logs
Attached Workflow
Please make sure that workflow does not contain any sensitive information such as API keys or passwords.
Additional Context
(Please add any additional context or steps to reproduce the error here)
The text was updated successfully, but these errors were encountered: