2024-07-17, 09:12 PM
(This post was last modified: 2024-07-17, 09:26 PM by TheDreadPirate. Edited 1 time in total.)
(2024-07-17, 05:25 PM)TheDreadPirate Wrote:(2024-07-17, 05:07 PM)draxer Wrote: I seem to have the same issue hardware transcoding stopped working and ffmpeg logs tell me
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
[AVHWDeviceContext @ 0x59efeceea440] Failed to get number of OpenCL platforms: -1001.
Device creation failed: -19.
Failed to set value 'opencl=ocl@va' for option 'init_hw_device': No such device
Error parsing global options: No such device
I am running jellyfin through a docker container on Ubuntu noble 24.04 x86_64 with kernel 6.8.0-38-generic.
Hardware is:
CPU: AMD Ryzen 5 3600X (12) @ 4,41 GHz
GPU: Intel Arc A380 @ 2,45 GHz
@draxer - roll back the kernel to 6.8.0-36. 6.8.0-38 inherited an upstream kernel bug that breaks transcoding. One of the jellyfin devs and I submitted a report to the Ubuntu kernel team to backport a pair of patches.
https://bugs.launchpad.net/ubuntu/+sourc...ug/2072755
Nyanmisaka and I validated the backport worked on a test kernel. So it should appear in a later Ubuntu kernel release. For now stay on 6.8.0-36. Reboot your system, press Esc after the BIOS screen if your system doesn't show the boot loader by default, select Advanced and the -36 kernel should be an option.
thanks for the help!