-v va-api-glx, there are errors?

softhdvaapi, libplacebo et al
-
-
Nothing changed here:
CodeApr 06 14:56:32 client vdr[3364]: video/glx: glx version 1.4 Apr 06 14:56:32 client vdr[3364]: [3374] epg data reader thread ended (pid=3364, tid=3374) Apr 06 14:56:32 client vdr[3364]: video/vaapi: Can't inititialize VA-API on ':0.0' Apr 06 14:56:32 client vdr[3364]: video: 'va-api-glx' output module isn't supported Apr 06 14:56:32 client vdr[3364]: [softhddev] ready
-
-v va-api
Looks like no vaapi libs.
-
-v va-api
Looks like no vaapi libs.
libva-devel-2.17.0-1.3
libva-drm2-2.17.0-1.3
libva-gl-devel-2.17.0-1.3
libva-glx2-2.17.0-1.3
libva-utils-2.17.1-1.2
libva-wayland2-2.17.0-1.3
libva-x11-2-2.17.0-1.3
libva2-2.17.0-1.3
Mesa-libva-23.0.1-1599.348.pm.5
-
Do
make
in plugin's dir
and post compilation messages.
Ex:
Spoiler anzeigen
CXX softhddevice.o
g++ -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/src/media_build/linux -I/usr/local/src/vdr-2.6.4-mod/include -I/usr/include/ffmpeg -I/usr/include/ffmpeg -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-4 -pthread -I/usr/include/ffmpeg -DPLUGIN_NAME_I18N='"softhddevice"' -D_GNU_SOURCE -DDEBUG -DOSD_DEBUG -DAV_INFO -DAV_INFO_TIME=3000 -DUSE_PIP -DHAVE_PTHREAD_NAME -DUSE_TS -DUSE_MPEG_COMPLETE -DH264_EOS_TRICKSPEED -DUSE_VDR_SPU -DUSE_ALSA -DUSE_OSS -DUSE_VDPAU -DUSE_VAAPI -DUSE_GLX -DUSE_EGL -DUSE_SCREENSAVER -DUSE_SWSCALE -DUSE_SWRESAMPLE -DUSE_CUVID -DUSE_OPENGLOSD -DGIT_REV='"5c85231"' -g -W -Wall -Wextra -Winit-self -Werror=overloaded-virtual -Wno-unused-parameter -c -DPLUGIN_NAME_I18N='"softhddevice"' -D_GNU_SOURCE -DDEBUG -DOSD_DEBUG -DAV_INFO -DAV_INFO_TIME=3000 -DUSE_PIP -DHAVE_PTHREAD_NAME -DUSE_TS -DUSE_MPEG_COMPLETE -DH264_EOS_TRICKSPEED -DUSE_VDR_SPU -DUSE_ALSA -DUSE_OSS -DUSE_VDPAU -DUSE_VAAPI -DUSE_GLX -DUSE_EGL -DUSE_SCREENSAVER -DUSE_SWSCALE -DUSE_SWRESAMPLE -DUSE_CUVID -DUSE_OPENGLOSD -DGIT_REV='"5c85231"' -o softhddevice.o softhddevice.cpp
CC softhddev.o
-
See attachement.
-
-DUSE_VAAPI -DUSE_GLX -DUSE_EGL
All fine.
Why....
Apr 06 14:56:32 client vdr[3364]: video/vaapi: Can't inititialize VA-API on ':0.0'
Apr 06 14:56:32 client vdr[3364]: video: 'va-api-glx' output module isn't supportedEnable debug in Makefile, line 50:
CONFIG += -DDEBUG
Recompile and post all starting log with va-api-egl ang cpu-egl, let's try to understand the reason.
-
I attached the complete vdr startup journal entries up to "[softhddev] ready" for va-api-egl and cpu-egl - perhaps there is something else wrong or missing.
-
Try -d :0 or -d :1
-
Try -d :0 or -d :1
I have to use :0.0, because :0.1 and :0.2 are already used for other X displays.
Using :0 only would make this impossible.
-
dann kommen beim ninja Build die Fehlermeldungen:
Code
Alles anzeigenFAILED: src/libplacebo.so.247.p/meson-generated_.._vulkan_utils_gen.c.o cc -Isrc/libplacebo.so.247.p -Isrc -I../src -Isrc/include -I../src/include -Isrc/opengl/include -I../src/opengl/include -Isrc/vulkan -Isrc/opengl/include/glad -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c11 -O2 -g -Wundef -Wshadow -Wparentheses -Wpointer-arith -D_ISOC99_SOURCE -D_ISOC11_SOURCE -D_GNU_SOURCE -D_XOPEN_SOURCE=700 -U__STRICT_ANSI__ -fvisibility=hidden -Wmissing-prototypes -Wno-sign-compare -Wno-unused-parameter -Wno-missing-field-initializers -Wno-type-limits -Werror=implicit-function-declaration -Werror=incompatible-pointer-types -fPIC -pthread -MD -MQ src/libplacebo.so.247.p/meson-generated_.._vulkan_utils_gen.c.o -MF src/libplacebo.so.247.p/meson-generated_.._vulkan_utils_gen.c.o.d -o src/libplacebo.so.247.p/meson-generated_.._vulkan_utils_gen.c.o -c src/vulkan/utils_gen.c src/vulkan/utils_gen.c: In function ‘vk_res_str’: src/vulkan/utils_gen.c:32:10: error: ‘VK_ERROR_VALIDATION_FAILED’ undeclared (first use in this function); did you mean ‘VK_ERROR_VALIDATION_FAILED_EXT’? 32 | case VK_ERROR_VALIDATION_FAILED: return "VK_ERROR_VALIDATION_FAILED"; | ^~~~~~~~~~~~~~~~~~~~~~~~~~ | VK_ERROR_VALIDATION_FAILED_EXT src/vulkan/utils_gen.c:32:10: note: each undeclared identifier is reported only once for each function it appears in src/vulkan/utils_gen.c:33:10: error: ‘VK_ERROR_INVALID_PIPELINE_CACHE_DATA’ undeclared (first use in this function) 33 | case VK_ERROR_INVALID_PIPELINE_CACHE_DATA: return "VK_ERROR_INVALID_PIPELINE_CACHE_DATA"; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/vulkan/utils_gen.c:34:10: error: ‘VK_ERROR_NO_PIPELINE_MATCH’ undeclared (first use in this function) 34 | case VK_ERROR_NO_PIPELINE_MATCH: return "VK_ERROR_NO_PIPELINE_MATCH"; ...
Bei mir auch so. Es liegt tatsächlich am Wechsel von vulkan 1.3.239 auf 1.3.243.
Ich habe erstmal die alte Vulkan-Version von einem anderen Repository geholt. Denn wenn Vulkan-devel und vulkan-headers deinstalliert werden, dann wird libplacebo ohne vulkan gebaut. Ich will aber die Vulkan-Unterstützung.
Codezypper addrepo https://download.opensuse.org/repositories/home:dirkmueller:branches:openSUSE:Factory:Rings:1-MinimalX/standard_v3/home:dirkmueller:branches:openSUSE:Factory:Rings:1-MinimalX.repo zypper ref
Stefan
-
Bei mir auch so. Es liegt tatsächlich am Wechsel von vulkan 1.3.239 auf 1.3.243.
Ich habe erstmal die alte Vulkan-Version von einem anderen Repository geholt. Denn wenn Vulkan-devel und vulkan-headers deinstalliert werden, dann wird libplacebo ohne vulkan gebaut. Ich will aber die Vulkan-Unterstützung.
Stefan
Ne, wenn du die submodules mit geholt hast aus dem GIT, hast du wieder alles, was zum Bauern der Vulkan-Unterstützung notwendig ist.
-
I have to use :0.0, because :0.1 and :0.2 are already used for other X displays.
Using :0 only would make this impossible.
Nevertheless I tried to use -d :0, but to no avail. See attached journal snippet.
Again I get video/vaapi: Can't inititialize VA-API on ':0'
Just an idea: Do I have to use the xf86-video-intel driver instead of the modesetting driver for this to work?
On the other hand, the modeseeting driver also supports glx:
-
If cpu-elg works with :d0.0, then all ok.
You can test
DISPLAY=:0.0 vainfo
-
Again I get video/vaapi: Can't inititialize VA-API on ':0'
Evtl. hat dein FFMPEG kein vaapi support eincompiliert. Beim Suse FFMPEG ist das wohl so und du must es selber compilieren.
-
Ich hab den ffmpeg-5 aus packman Tumbleweed Repo installiert - der sollte das AFAIK haben.
-
If cpu-elg works with :d0.0, then all ok.
You can test
DISPLAY=:0.0 vainfo
Oops, this is the first time, I get an error:
Code
Alles anzeigenDISPLAY=:0.0 vainfo Trying display: wayland Trying display: x11 libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_17 libva error: /usr/lib64/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit
-
I am really stupid 8-<
At one point I had uninstalled intel-media-driver, i.e. the iHD_drv_video module., because I compiled a newer version from Intel. After uninstalling this self compiled version, I forgot to reinstall the package from the Tumbleweed repo.
After reinistalling it, softhddevice can initialize vaapi as expected.
lnj: Thx for your help and your patience!
Just to be sure: va-api-egl is the preferred driver? Or should I use a different one for my Intel(R) Core(TM) i5-10400T CPU @ 2.00GHz?
Code
Alles anzeigenApr 10 10:54:07 client vdr[19785]: video/egl: egl apis: OpenGL OpenGL_ES Apr 10 10:54:07 client vdr[19785]: video/egl: EglSetupWindow 200004 1920x1080 context: 0x172d6b0 Apr 10 10:54:07 client vdr[19785]: video/vaapi: libva 1.17 (Intel iHD driver for Intel(R) Gen Graphics - 23.1.3 ()) initialized Apr 10 10:54:07 client vdr[19785]: video/vaapi: background-color is supported Apr 10 10:54:07 client vdr[19785]: video/vaapi: supports video processing Apr 10 10:54:07 client vdr[19785]: video: screen saver extension present Apr 10 10:54:07 client vdr[19785]: video: dpms extension present Apr 10 10:54:07 client vdr[19785]: video: dpms was enabled Apr 10 10:54:07 client vdr[19785]: Selected deinterlacer for resolution 0 is not supported by HW Apr 10 10:54:07 client vdr[19785]: Selected deinterlacer for resolution 1 is not supported by HW Apr 10 10:54:07 client vdr[19785]: Selected deinterlacer for resolution 2 is not supported by HW Apr 10 10:54:07 client vdr[19785]: Selected deinterlacer for resolution 3 is not supported by HW Apr 10 10:54:07 client vdr[19785]: Selected deinterlacer for resolution 4 is not supported by HW Apr 10 10:54:07 client vdr[19785]: video/egl: osd init context (nil) <-> 0x17fbc30 Apr 10 10:54:07 client vdr[19785]: video/egl: osd context 0x17fbc30 <-> 0x17fbc30 Apr 10 10:54:07 client vdr[19785]: [softhddev] ready
-
For UHD use va-api-egl, also for new Intel driver too.
For old Intel va-api and va-api-glx.
-
For UHD use va-api-egl, also for new Intel driver too.
For old Intel va-api and va-api-glx.
Is Intel(R) Core(TM) i5-10400T CPU @ 2.00GHz a new one for this case?
-
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!