-
Notifications
You must be signed in to change notification settings - Fork 27.4k
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]: Launch Prevention after recent update #12223
Comments
I was JUST about to post this... I saw an update last night but this morning i couldn't restart Auto1111 Did an entire reinstall to no avail.
|
I have the same issue on a previously working install, it was working like 12 hours ago. I guess something got wrong in the most recent update. |
had to be, I generated one image this morning before work to test that I could run a batch... and something happened and it suddenly failed. hope for a fix in the next 2 hours :D lol (off work) |
can't seem to find anything related to a change between now and ~12hours, no commit here, windows update or anything really. Guess we have to wait for someone |
I have this too. I don't know enough to fix it myself. Seems like attempting to fix it might break any fixes forthcoming. "from modules.shared import opts, cmd_opts, log |
afaik you can mess with your own cloned repo and it won't impact the main one at all (not that you can anyway). |
I have this exact issue. Started about 12 hours ago. Waiting on fix, |
I figured out the temp fix to roll back to the previous. You can switch back to the main repo later when an update hits. Temp fix for Auto 1111 on AMD use Auto1111 again. It might work on others, not sure though since I use the fork for AMD and directml, I assume nvidia would just go to the main repo and go to the last commit that was good (if they are even having issues? |
OH MY GOSH THAT FIXED IT FOR NOW! THANK YOU |
This is due to shoddy support of RDNA1 (and lower) cards (like RX5700XT) - torch>=2.0.0 won't run on these from my experience, at least on ROCm. This was apparently fixed in #11048 but someone forgot about it and forced torch version to be >=2.0.0 in
Though, I am a bit worried, since RDNA2 cards aren't working apparently too #12228 and they did before (no workaround present in shell script, so assuming that it's true) with torch>=2.0.0 so it could be due to newest torch version? |
I'm on RDNA3. Same problem. |
Or downgrade to nightly versions before 2023-07-31, unless I'm mistaken and other requirements (or something else out of my scope) like |
You know you're not using A1111 right? That's a forks so please don't open issues on the A1111 repository. |
in fact I did not know. so unless you read each step super extra careful you won't notice edit: |
Is there an existing issue for this?
What happened?
git pulled as always, launch failed afterwards.
Proceeded to try a clean-install, didn't work.
=> Unable to launch sd-webui at the moment as I don't know how to roll-back
Steps to reproduce the problem
What should have happened?
It should have launched.
Version or Commit where the problem happens
Version: 1.5.1
What Python version are you running on ?
Python 3.10.x
What platforms do you use to access the UI ?
Windows
What device are you running WebUI on?
AMD GPUs (RX 5000 below)
Cross attention optimization
Automatic
What browsers do you use to access the UI ?
Mozilla Firefox, Google Chrome
Command Line Arguments
List of extensions
clean install
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: