-
Notifications
You must be signed in to change notification settings - Fork 349
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
CUDA error (again ! :-)) #554
Comments
Issue with Prebuilt CUDA SD Binary Size Discrepancy I've noticed a potential issue with the prebuilt CUDA version of stable-diffusion.cpp: Current release after Nov 30: Previous release (Nov 23): This significant size reduction (approximately 85% smaller) suggests that the latest prebuilt binary might be missing essential components or was incorrectly packaged. The properly functioning version should be closer to the 137MB size of the November 23rd release. Recommendation: |
In fact, the release of 23 Nov is much bigger than the releases of december.
And moreover, it doesn't explain, why the version of december works well on my other computer (with RTX 4070) (In fact, it is Flux1Dev that works on this other computer, and the error I mentioned here on the other computer, coincerns SD1.4 (since I've not enough VRAM to Run FluxDev), so my comparison is not perfect) |
RTX A1000 is Ampere GPU architecture source,Maybe you need to change it from 89 to 87. https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/index.html#virtual-architecture-feature-list |
It seems to be caused by ggml upstream:ggml-org/ggml@77d37f5 |
so how should we solve this issue? |
Hi,
I've tried SD 1.4 and CUDA backend on 2 configurations :
On my personal computer with RTX 4070, everything works well, thanks to ag2s20150909 and the build https://github.com/ag2s20150909/stable-diffusion.cpp/releases/tag/master-74a21a7
On my working computer, a laptop with RTX A1000, I still get errors that I don't understand :
Here is the full log :
Does anybody have an idea ?
Thanks a lot in advance
Olivier
The text was updated successfully, but these errors were encountered: