You are not logged in.
This seems to be a recent issue as I did not notice it prior to a week back. vainfo seems to choosing the wrong render device. In my laptop, the Intel iGPU is /dev/dri/render129 but, for some reason it is choosing /dev/dri/render128 which is the headless discrete AMD GPU.
vainfo returns
vaInitialize failed with error code -1 (unknown libva error),exit
LIBVA_DRIVER_NAME=iHD vainfo
returns
DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [13]
param: 4, val: 0
libva error: /usr/lib/dri/iHD_drv_video.so init failed
vaInitialize failed with error code 18 (invalid parameter),exit
However,
LIBVA_DRIVER_NAME=iHD vainfo --display drm --device /dev/dri/renderD129
returns
vainfo: VA-API version: 1.6 (libva 2.6.0)
vainfo: Driver version: Intel iHD driver - 19.4.0
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointFEI
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointFEI
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointFEI
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointFEI
which is the expected output.
Anyone knows what's the issue? Is there anyway i can point libva to the correct output?
Offline
Have you tried setting the LIBVA_DRIVERS_PATH?:
For iHD_drv_video.so please export related LIBVA environment variables.
export LIBVA_DRIVERS_PATH=<path-contains-iHD_drv_video.so> export LIBVA_DRIVER_NAME=iHD
Last edited by CarbonChauvinist (2020-01-07 14:15:32)
"the wind-blown way, wanna win? don't play"
Offline
Yes. The result is the same.
Offline
I managed to get it to work momentarily by removing and reinstalling the intel-media-driver package. But, it broke again after a couple of hours. Could it be an issue due to xorg? I presume that vaapi applications obtain their DRI info from xorg. So, it could be pointing to the wrong device.
Offline
libva tries to guess the device and often fails.
post outputs of
$ unset -v LIBVA_DRIVER_NAME
$ vainfo
$ vainfo --display drm --device /dev/dri/renderD128
$ vainfo --display drm --device /dev/dri/renderD129
If libva-mesa-driver package is installed , remove it and repeat those commands.
Last edited by Lone_Wolf (2020-01-08 11:09:44)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
all good
Last edited by archuser_9999 (2020-04-28 07:46:13)
Offline