-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
InvokeAI doesn't work (AMD) #83
Comments
I do not own an AMD GPU, and do not have adequate funding to resolve that issue. So testing is not possible. Are you running NixOS? If so, show me your configuration for your AMD driver. |
Yes, I'm running NixOS (unstable with use of flakes). services.xserver.videoDrivers = [ "amdgpu" ];
hardware.opengl.extraPackages = [ pkgs.amdvlk ]; I also use: environment.variables = {
HSA_OVERRIDE_GFX_VERSION = "10.3.0";
AMD_VULKAN_ICD = "RADV";
}; to use mesa by default instead of amdvlk and |
HSA_OVERRIDE_GFX_VERSION is already set by the wrapper here flake/projects/invokeai/package.nix Line 100 in 63339e4
|
It's understandable. Thanks for trying to help. |
Related Problem:
System Information:
Nix Config (system wide installed):
|
I have this exact same error (the missing file is the same one as well). Running NixOS on AMD 7900XTX GPU, Ryzen 9 3900 CPU, 32GB RAM. |
Related problem:I have this same issue, except with an additional deprecation notice for Here's the result of running it for the first time:
And the second time:
No selection menu ever appears, and I don't really know what more to do about that. System informationOS: NixOS 24.11 (Vicuna) x86_64 |
I tried installing InvokeAI according to README with
nix run github:nixified-ai/flake#invokeai-amd
. During installation (after InvokeAI configuration screen) I got error:If I try to run
nix run github:nixified-ai/flake#invokeai-amd
once more, webui will launch but when trying to generate image it spits out error message in terminal:Launching with
HIP_LAUNCH_BLOCKING=1
doesn't change the error message.System information:
The text was updated successfully, but these errors were encountered: