* Andres Salomon: " Re: Bug#1035917: chromium: libva error:
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed" (Thu, 11 May 2023
11:48:48 -0400):
Hi Andres,
thanks for your feedback.
> I'm guessing that the following is also broken for you:
>
> vainfo
Not really broken, but
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.17 (libva 2.12.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Desktop - 2.4.1
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264MultiviewHigh : VAEntrypointVLD
VAProfileH264MultiviewHigh : VAEntrypointEncSlice
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileH264StereoHigh : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
VAProfileJPEGBaseline : VAEntrypointVLD
> You could also try the following to see if the other intel driver isn't
> broken:
>
> LIBVA_DRIVER_NAME=i965 vainfo
>
> Did this used to work for you? If so, you could try downgrading
> intel-media-va-driver using snapshot.debian.org (or upgrading to the
> version that's in unstable, and hasn't migrated to bookworm yet).
Ok, will try that besides evtl. downgrading chromium.
> Either way, chromium uses vaapi by default; so if the vaapi driver for
> your specific hardware is broken, you'll have to figure out which
> combination of flags to disable it work for you (eg,
> https://www.reddit.com/r/archlinux/comments/tc5379/if_you_have_trouble_getting_vaapi_hardware_video/
>
> ) until you get vaapi working with your hardware.
>
> Out of curiosity, what is the GPU and CPU that you're seeing this iHD
> driver failure on?
mathiasb@monsterix:~$ cat /proc/cpuinfo
...
GenuineIntel cpu family : 6 model : 60 model name :
Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz
...
mathiasb@monsterix:~$ glxinfo
...
Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086)
Device: Mesa Intel(R) HD Graphics 4600 (HSW GT2) (0x412) Version: 22.3.6
Accelerated: yes Video memory: 1536MB Unified memory: yes Preferred profile:
core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max
GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor
string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics 4600 (HSW GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.3.6 OpenGL core
profile shading language version string: 4.60
...
--
Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6
