-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[bug]: Launching web-gui with CUDA #5863
Comments
I had the same issue last week upon updating to 3.7 from 3.4 with the latest install.bat (I'd put off updating for a while for fear of just such a thing happening after I ran into some of the now-known issues when updating to 3.4!), and saw some older issues posted for it as well (such as #5734 , which was closed with a suggested fix, but no confirmation). I tried doing an update to force dependency reinstallation, tried running the repair installation option, tried reinstalling again from the 3.7 install script, but didn't have any luck. I tried manually uninstalling and re-installing the controlnet_aux module, and still got that error. The module showed up in a "pip list" in the VENV, so I was about ready to pull my hair out in flabbergastery. Finally, I noticed that in the relevant site-packages directory, that regardless of whether I installed it individually or by the script, controlnet_aux was only ever creating the dist-info folder, and not the actual module contents (which explains why it could show up as installed without actually being there). So at that point I just manually downloaded the package (you can grab the current version here: https://pypi.org/project/controlnet-aux/0.0.7/ ) and extracted the module contents folder straight over into the site-packages directory, and that took care of the problem. I'm not versed enough in Python to figure out exactly what was going on here, but it seems like there's some flakiness to this package that might warrant a little extra guarding against. |
@the-space-fish Thanks a bunch for the fix, that's exactly what the problem was! I just wanted to add a few details, as some might still struggle with this information. What I did was download the Sorry if this is simple stuff, I thought it might still be helpful. |
@adriantiron - yes, thanks for adding in the details! I'd have been more explicit, but was writing from memory on a different computer without the installation handy. |
Downloaded and put the controlnet_aux folder from src now the error is a little different.
|
That error seems to be implying it can't access your CUDA device (GPU), so I wonder if this section from the release notes would help you out?
|
You can also try something to see how many CUDA capable devices are seen:
Please post a screenshot here. |
About that. I tried reinstalling torch and got an error. Then I installed fsspec and started the torch installation again - I got the same errors. |
Try installing controlnet-aux, I'm guessing it doesn't find the dist-info: P.S.: Don't start the torch installation again after dealing with the dependencies. That error does not invalidate the torch installation. |
I'm not sure if it can see the video card. During installation it suggested Cuda, and at the time of reinstallation via invoke.bat it couldn't detect the video card. |
If I may, if you don't have a strong reason for choosing InvokeAI, can I suggest Automatic1111? I switched to that and had 0 problems installing and using it. |
Just like in this reply, do the same but for 2 more lines:
|
|
Everything seems to be fine here. I'm stumped, the only other thing I would try doing is start from scratch... Sorry, maybe someone else has better ideas. |
Is there an existing issue for this problem?
Operating system
Windows
GPU vendor
Nvidia (CUDA)
GPU model
2060
GPU VRAM
8Gb
Version number
3.7.0
Browser
Opera: 107.0.5045.37
Python dependencies
No response
What happened
After completing the installation, I proceeded to execute invoke.bat, selected option 1, confirmed it, and encountered an error.
I attempted reinstall through the invoke.bat, then retried launching the GUI and encountered the same errors.
What you expected to happen
I expected to launch web GUI
How to reproduce the problem
No response
Additional context
No response
Discord username
No response
The text was updated successfully, but these errors were encountered: