2024-10-03, 06:43 PM
(This post was last modified: 2024-10-04, 06:23 PM by caius. Edited 1 time in total.)
I have a jellyfin server which used to do opencl tonemapping OK. I've noticed now that it gives an error when trying to transcode a file which requires tone mapping and playback does not start.
The server is a Celeron J4105 with UHD 600 graphics. Quicksync hardware acceleration works OK, as does VPP tone mapping. It's running on Ubuntu 24.04 LTS directly (ie not in docker).
Jellyfin version is 10.9.11.
It looks like some problem with the opencl driver but I'm not sure how to troubleshoot it. If I run clinfo that also crashes with the same error message. I'm not sure if this is a configuration error somewhere or if there's an issue with the driver itself. I'd be grateful if anyone has any ideas.
The server is a Celeron J4105 with UHD 600 graphics. Quicksync hardware acceleration works OK, as does VPP tone mapping. It's running on Ubuntu 24.04 LTS directly (ie not in docker).
Jellyfin version is 10.9.11.
Code:
uname -a:
Linux odyssey 6.8.0-44-generic #44-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 13 13:35:26 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Code:
/usr/lib/jellyfin-ffmpeg/vainfo
Trying display: drm
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.2.5 (12561f6)
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
etc.
Code:
apt policy intel-opencl-icd
intel-opencl-icd:
Installed: 23.43.27642.40-1ubuntu3
Candidate: 23.43.27642.40-1ubuntu3
Code:
sudo /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device vaapi=va:/dev/dri/renderD128 -init_hw_device opencl@va
ffmpeg version 6.0.1-Jellyfin Copyright (c) 2000-2023 the FFmpeg developers
built with gcc 13 (Ubuntu 13.2.0-23ubuntu4)
configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-ptx-compression --disable-static --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto --enable-gpl --enable-version3 --enable-shared --enable-gmp --enable-gnutls --enable-chromaprint --enable-opencl --enable-libdrm --enable-libxml2 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libsvtav1 --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=amd64 --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-vaapi --enable-amf --enable-libvpl --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc
libavutil 58. 2.100 / 58. 2.100
libavcodec 60. 3.100 / 60. 3.100
libavformat 60. 3.100 / 60. 3.100
libavdevice 60. 1.100 / 60. 1.100
libavfilter 9. 3.100 / 9. 3.100
libswscale 7. 1.100 / 7. 1.100
libswresample 4. 10.100 / 4. 10.100
libpostproc 57. 1.100 / 57. 1.100
[AVHWDeviceContext @ 0x5607007e6300] libva: VA-API version 1.22.0
[AVHWDeviceContext @ 0x5607007e6300] libva: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
[AVHWDeviceContext @ 0x5607007e6300] libva: Found init function __vaDriverInit_1_22
[AVHWDeviceContext @ 0x5607007e6300] libva: va_openDriver() returns 0
[AVHWDeviceContext @ 0x5607007e6300] Initialised VAAPI connection: version 1.22
[AVHWDeviceContext @ 0x5607007e6300] VAAPI driver: Intel iHD driver for Intel(R) Gen Graphics - 24.2.5 (12561f6).
[AVHWDeviceContext @ 0x5607007e6300] Driver not found in known nonstandard list, using standard behaviour.
Abort was called at 40 line in file:
./shared/source/built_ins/built_ins.cpp
Aborted
It looks like some problem with the opencl driver but I'm not sure how to troubleshoot it. If I run clinfo that also crashes with the same error message. I'm not sure if this is a configuration error somewhere or if there's an issue with the driver itself. I'd be grateful if anyone has any ideas.