Also worth mentioning: osu!lazer has a native Linux build, whereas osu!stable still requires WINE to run on Linux. That’s something I was very glad to see.
Also worth mentioning: osu!lazer has a native Linux build, whereas osu!stable still requires WINE to run on Linux. That’s something I was very glad to see.
YaCy, Mwmbl, Alexandria, Stract, Marginalia to name a few.
I would try what the other commenter here said first. If that doesn’t fix your issue, I would try using the Forge version of WebUI (a fork of that WebUI with various memory optimizations, native extensions and other features): https://github.com/lllyasviel/stable-diffusion-webui-forge. This is what I personally use.
I use a 6000-series GPU instead of a 7000-series one, so the setup may be slightly different for you, but I’ll walk you through what I did for my Arch setup.
Me personally, I skipped that Wiki section on AMD GPUs entirely and it seems the WebUI still respects and utilizes my GPU just fine. Simply running the webui.sh
file will do most of the heavy lifting for you (you can see in the webui.sh
file that it uses specific configurations and ROCm versions for different AMD GPU series like Navi 2 and 3)
git clone https://github.com/lllyasviel/stable-diffusion-webui-forge stable-diffusion-webui
(the stable-diffusion-webui
directory name is important, webui.sh
’s script seems to reference that directory name specifically)webui.sh
and webui-user.sh
are in the wrong spot, make symlinks to them so the symlinks are at the same level as the stable-diffusion-webui
directory you created: ln stable-diffusion-webui/webui.sh webui.sh
(ditto for webui-user.sh
)webui-user.sh
file. You don’t really have to change much in here, but I would recommend export COMMANDLINE_ARGS="--theme dark"
if you want to save your eyes from burning.yay -S python310
or paru -S python310
or whatever method you use to install packages from the AUR. Once you do that, edit webui-user.sh
so that python_cmd
looks like this: python_cmd="python3.10"
webui.sh
file: chmod u+x webui.sh
, then ./webui.sh
venv
directory from within the stable-diffusion-webui
directory and running the script again. This actually worked in my case, not really sure what went wrong…http://127.0.0.1:7860
. Select the proper checkpoint in the top left, write down a test prompt and hopefully it should be pretty speedy, considering your GPU.Yes, I torrent on the same machine where all my personal stuff is. The biggest reason for this is that I don’t have a dedicated machine to torrent 24/7, though I’d definitely like to set that up at some point. I like being able to seed niche torrents to those who need them, and a machine seeding 24/7 would definitely help with that. Also having easy simple access to the downloaded files is always a plus, but there’s a myriad of ways to do this over a local network (pretty sure some torrenting clients even have an option to torrent over LAN).
My torrent client is bound to my VPN’s network interface, and my VPN has a killswitch as well, so I’m not paranoid that things will suddenly leak. Been running this setup for months now without issues.
zellij attach --create-background
Nice; this was the only thing preventing me from making a full switch from tmux to zellij.
I think that is completely normal. I run Arch on my main desktop, OpenSUSE Tumbleweed on my laptop and Debian on any and all servers I host. And I think they all work wonderfully. Even outside of these distros, I can still see the use case for many other distros. I think many popular distros each have a specific goal in mind and they execute it well.
In other news, the sky is blue…
Sorry for the late response, but yes, I believe you can. There is an option in the config called
allow_public_upload
which can be changed to true or false.