InvokeAI

rfile#... has, in addition to fan and power controls, automatic updates on desktop, supergfxctl, system76-scheduler, and an fsync kernel: rpm-ostree install rocm-hip \ rocm-opencl \ rocm-clinfo But it's not `rpm-ostree install --apply-live` because its a Containerfile. To install a ublue-os distro, you install any of the Fedora ostree distros: {Silverblue, Kinoite, Sway Atomic, or Budgie Atomic} from e.g. a USB stick and then `rpm-ostree rebase <OCI_host_image_url>`: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-nvidia:stable rpm-ostree rebase ostree-image-signed: ublue-os/config//build/ublue-os-just/40-nvidia.just defines the `ujust configure-nvidia` and `ujust toggle-nvk` commands: https://github.com/ublue-os/config/blob/main/build/ublue-os-... There's a default `distrobox` with pytorch in ublue-os/config//build/ublue-os-just/etc-distrobox/apps.ini: https://github.com/ublue-os/config/blob/main/build/ublue-os-... [mlbox] image=nvcr.io/nvidia/pytorch:23.08-py3 additional_packages="nano git htop" init_hooks="pip3 install huggingface_hub tokenizers transformers accelerate datasets wandb peft bitsandbytes fastcore fastprogress watermark torchmetrics deepspeed" pre-init-hooks="/init_script.sh" nvidia=true pull=true root=false replace=false docker.io/rocm/pytorch: https://hub.docker.com/r/rocm/pytorch pytorch/builder//manywheel/Dockerfile: https://github.com/pytorch/builder/blob/main/manywheel/Docke... ROCm/pytorch//Dockerfile: https://github.com/ROCm/pytorch/blob/main/Dockerfile The ublue-os (and so also bazzite) OCI host image Containerfile has Sunshine installed; which is a 4k HDR 120fps remote desktop solution for gaming. There's a `ujust remove-sunshine` command in system_files/desktop/shared/usr/share/ublue-os/just/80-bazzite.just : https://github.com/ublue-os/bazzite/blob/main/system_files/d... and also kernel args for AMD: pstate-force-enable: rpm-ostree kargs --append-if-missing=amd_pstate=active ublue-os/config//Containerfile: https://github.com/ublue-os/config/blob/main/Containerfile LizardByte/Sunshine: https://github.com/LizardByte/Sunshine moonlight-stream https://github.com/moonlight-stream Anyways, hopefully this PR fixes the immediate issue: https://github.com/invoke-ai/InvokeAI/pull/5714/files conda-forge/pytorch-cpu-feedstock > "Add ROCm variant?": https://github.com/conda-forge/pytorch-cpu-feedstock/issues/... And Fedora supports OCI containers as host images and also podman container images with just systemd to respawn one or a pod of containers.

port - We’ve implemented support the impending SDXL model architecture (And the current 0.9 model), and we’ll follow-up with streamlined SDXL support in the core UI interfaces once the 1.0 model is released. - ControlNet - Integrated support for the most popular ControlNet models, directly in the UI, with a simple processor preview and UI/UX. - Boards - Expanded gallery support to better organize and manage large scale images. Multi-select, drag & drop to anywhere in the UI, and backed by a local database to provide performant operations even when you’re thousands of images deep. - Expanded Schedulers - Rather than list all of them here… All the schedulers/samplers you know and love, with the ability to set favorites and disable those you’ll never use. - Model Flexibility - Swap your VAE on demand. Mix and match models as needed. Clip Skip. With the flexibility of the experimental Node Editor, you can even swap models mid-generation. - LoRA Enhancements - Full LoRA support (for all the Lo’s and Ly’s you can name), we’ve also added a mechanism which directly patches the model UNet on loading a LoRA. Test for yourself. - UI/UX Updates - Across the board, we’ve worked to clean up the UI, optimize the options panel for the most commonly used features, and left a number of the tiny little microinteractions across the app that make using Invoke easy for your workflow. It’s our best UI yet, hands down. And more is coming. - Node Editor (Experimental) - The main reason 3.0 took as long as it did (5 months!) is because we disassembled the entire backend of the application, and put it back together one “node” at a time. It’s clean, streamlined, and scalable. This sets us up to drive powerful advanced experiences for power users and gives an easy way for contributors to extend the capabilities of Invoke. The Node Editor that exposes all of the available functionality in the background is in an “experimental” status, for explorers and developers - Mainly because we have a lot of UI/UX polish we want to apply to it, and provide better ways to help less experienced users be successful with it! — *Up Next* More is coming. We have plans to extend on many of the core UI/UX experiences in the application, add more community resources for sharing new plug-ins/nodes, and will release the full version of the Node Editor in 3.1. Stay tuned! –- Whether you're a dev looking to build on or contribute to the project, a professional looking for pro-grade tools to incorporate into your workflow, or just looking for a great open-source SD experience, we're looking forward to you joining our community. You can get the latest version on GitHub https://github.com/invoke-ai/InvokeAI/releases