These errors indicate that the GPU doesn't have a video decoder in it. I filed internal bug 1808799 to try to get VDPAU to provide a better error message when this happens.
These errors indicate that the GPU doesn't have a video decoder in it. I filed internal bug 1808799 to try to get VDPAU to provide a better error message when this happens.
@neti: Why would you need a decoder on a secondary dedicated GPU? Just firing up the GPU will raise the resource usage far more than you could ever save by doing hardware instead of software decoding. Well, maybe not for 4K decoding and/or HEVC video, but still. That's why there's no Nvidia decoder, it's a waste of silicon. Just use the Intel decoder with VAAPI.
@neti: Why would you need a decoder on a secondary dedicated GPU? Just firing up the GPU will raise the resource usage far more than you could ever save by doing hardware instead of software decoding. Well, maybe not for 4K decoding and/or HEVC video, but still. That's why there's no Nvidia decoder, it's a waste of silicon. Just use the Intel decoder with VAAPI.
@aplattner, @neti, @Gusar,
According to this [url=http://us.download.nvidia.com/XFree86/Linux-x86_64/375.26/README/supportedchips.html]page[/url] 940MX has "E" VDPAU feature set.
According to [url=http://us.download.nvidia.com/XFree86/Linux-x86_64/375.26/README/vdpausupport.html#vdpau-implementation-limits-decoder]docs[/url] this future set does have hw video decoding. Am I wrong?
@aplattner, @neti, @Gusar,
According to this page 940MX has "E" VDPAU feature set.
According to docs this future set does have hw video decoding. Am I wrong?
Just for positive input: vdpau is working here and always has. Gentoo, 740M Optimus. So maybe something wrong with driver packaging in some distros?
vdpauinfo:
display: :1 screen: 0
API version: 1
Information string: NVIDIA VDPAU Driver Shared Library 375.26 Thu Dec 8 18:03:32 PST 2016
feature name sup
------------------------------------
DEINTERLACE_TEMPORAL y
DEINTERLACE_TEMPORAL_SPATIAL y
INVERSE_TELECINE y
NOISE_REDUCTION y
SHARPNESS y
LUMA_KEY y
HIGH QUALITY SCALING - L1 y
HIGH QUALITY SCALING - L2 -
HIGH QUALITY SCALING - L3 -
HIGH QUALITY SCALING - L4 -
HIGH QUALITY SCALING - L5 -
HIGH QUALITY SCALING - L6 -
HIGH QUALITY SCALING - L7 -
HIGH QUALITY SCALING - L8 -
HIGH QUALITY SCALING - L9 -
parameter name sup min max
-----------------------------------------------------
VIDEO_SURFACE_WIDTH y 1 4096
VIDEO_SURFACE_HEIGHT y 1 4096
CHROMA_TYPE y
LAYERS y 0 4
attribute name sup min max
-----------------------------------------------------
BACKGROUND_COLOR y
CSC_MATRIX y
NOISE_REDUCTION_LEVEL y 0.00 1.00
SHARPNESS_LEVEL y -1.00 1.00
LUMA_KEY_MIN_LUMA y
LUMA_KEY_MAX_LUMA y
[quote=""]@neti: Why would you need a decoder on a secondary dedicated GPU? Just firing up the GPU will raise the resource usage far more than you could ever save by doing hardware instead of software decoding. Well, maybe not for 4K decoding and/or HEVC video, but still. That's why there's no Nvidia decoder, it's a waste of silicon. Just use the Intel decoder with VAAPI.[/quote]
1) there are enough cases when you have CPU fully loaded and you need to hw decode video at the same time
2) feature sets of Intel's decoder are not equal to NVIDIA one.
3) using Intel's VAAPI while you have switched to NVIDIA GPU is somewhat tricky
4) it is not waste of silicon and video decoder/encoder is certainly there, NVIDIA GPUs have standardized feature sets. Spreading feature sets by disabling features only makes hw support harder. If NVIDIA really did cripple mobile GPUs by limiting the firmware/drivers capabilities, then they need to document this properly.
said:@neti: Why would you need a decoder on a secondary dedicated GPU? Just firing up the GPU will raise the resource usage far more than you could ever save by doing hardware instead of software decoding. Well, maybe not for 4K decoding and/or HEVC video, but still. That's why there's no Nvidia decoder, it's a waste of silicon. Just use the Intel decoder with VAAPI.
1) there are enough cases when you have CPU fully loaded and you need to hw decode video at the same time
2) feature sets of Intel's decoder are not equal to NVIDIA one.
3) using Intel's VAAPI while you have switched to NVIDIA GPU is somewhat tricky
4) it is not waste of silicon and video decoder/encoder is certainly there, NVIDIA GPUs have standardized feature sets. Spreading feature sets by disabling features only makes hw support harder. If NVIDIA really did cripple mobile GPUs by limiting the firmware/drivers capabilities, then they need to document this properly.
Same problem here : 17.10 and 384 on 840M:
[code]
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: User requested driver 'nvidia'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_0_39
GPU at BusId 0x3 doesn't have a supported video decoder
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library 387.34 Tue Nov 21 02:08:49 PST 2017
VDPAU nvidia: Error detected 9 319 3
VDPAU nvidia: Backtrace:
--: /usr/lib/vdpau/libvdpau_nvidia.so.1 [0x7f2d2bf5c000] DSO load base
00: /usr/lib/vdpau/libvdpau_nvidia.so.1 [0x7f2d2bf929f9]
01: /usr/lib/vdpau/libvdpau_nvidia.so.1 [0x7f2d2bf82673]
02: /usr/lib/vdpau/libvdpau_nvidia.so.1 [0x7f2d2bf66951] vdp_imp_device_create_x11
libva error: /usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
[/code]
This seems like on old menace ... anyone found a solution/workaround?
any news to this issue?
Still the same Ubuntu 15.10 + 352.63
i'm not the only one here
370.23 driver 4.7.0 kernel ubuntu xenial gf940mx thinkpad t460
kinda relieved
vdpauinfo
glxinfo|grep OpenGL
Aaron Plattner
NVIDIA Linux Graphics
WTF? 2016 and you are selling chips for laptops without video decoding?! LOL!
According to this page 940MX has "E" VDPAU feature set.
According to docs this future set does have hw video decoding. Am I wrong?
vdpauinfo:
1) there are enough cases when you have CPU fully loaded and you need to hw decode video at the same time
2) feature sets of Intel's decoder are not equal to NVIDIA one.
3) using Intel's VAAPI while you have switched to NVIDIA GPU is somewhat tricky
4) it is not waste of silicon and video decoder/encoder is certainly there, NVIDIA GPUs have standardized feature sets. Spreading feature sets by disabling features only makes hw support harder. If NVIDIA really did cripple mobile GPUs by limiting the firmware/drivers capabilities, then they need to document this properly.
This problem is still there.
This seems like on old menace ... anyone found a solution/workaround?