You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Known issues
There is a known incompatibility between this release and i915 kernel mode driver in kernel 6.7.5 or later.
Symptom: GPU device is not detected
The workaround untill next release is to add these 2 debug variables to the docker container
This makes clinfo able to see the gpu again.
But i'm still unable to play content that is using opencl :(, it just seems to get stuck while trying to play.
Guess I will downgrade the kernel and wait for the next release of opencl.
This post is more of a shared info for anyone having the same issues right now or might get
Expected Behavior
No response
Steps To Reproduce
install a kernel newer than 6.7.x
opencl and clinfo no work
apply above workaround
clinfo now detects gpu
But playback that uses opencl still does not work
Environment
- OS: Unraid 6.12.10 with custom kernel 6.9.0-rc3-thor-Unraid+
- How docker service was installed: Comes built-in with the OS, so I got no idea how they install the service
Is there an existing issue for this?
Name of mod
jellyfin-opencl-intel
Name of base container
lscr.io/linuxserver/jellyfin:10.8.13
Current Behavior
There is currently a known issue with opencl, that it is unable to detect gpu's on systems running with linux kernels newer than 6.7.x.
See https://github.com/intel/compute-runtime/releases for more in and https://github.com/intel/compute-runtime/releases/tag/24.09.28717.12 for more info
The workaround untill next release is to add these 2 debug variables to the docker container
Or directly through console
This makes clinfo able to see the gpu again.
But i'm still unable to play content that is using opencl :(, it just seems to get stuck while trying to play.
Guess I will downgrade the kernel and wait for the next release of opencl.
This post is more of a shared info for anyone having the same issues right now or might get
Expected Behavior
No response
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs
without the workaround
With the workaround
The text was updated successfully, but these errors were encountered: