search for: libva

...722316 ... 0.7.4-13 - Revert symlinks - should be handled by mesa rhbz#1271842 https://bugzilla.redhat.com/show_bug.cgi?id=1271842 ... 0.7.4-12 - Add symlinks for radeonsi,r600,nouveau - rhbz#1264499 https://bugzilla.redhat.com/show_bug.cgi?id=1264499 $ rpm -q libva libva-vdpau-driver mesa-dri-drivers libva-1.7.1-1.fc24.x86_64 libva-vdpau-driver-0.7.4-14.fc24.x86_64 mesa-dri-drivers-11.2.2-2.20160614.fc24.x86_64 $ rpm -ql libva-vdpau-driver /usr/lib64/dri/nvidia_drv_video.so /usr/lib64/dri/s3g_drv_video.so /usr/lib64/dri/vdpau_drv_video.so /usr/share/doc/......

On 30.06.2016 08:27, Xiang, Haihao wrote: > > > Are you using VA-API on X11? libva gets the driver name from Xserver, > it is nouveau for you. so libva tries to load nouveau_drv_video.so. > You can create a symlink for nouveau pointing to a available driver or > just ignore the message because you have gallium_drv_video.so now. > > Thanks > Haihao > In p...

Are you using VA-API on X11? libva gets the driver name from Xserver, it is nouveau for you. so libva tries to load nouveau_drv_video.so.  You can create a symlink for nouveau pointing to a available driver or just ignore the message because you have gallium_drv_video.so now. Thanks Haihao > nouveau_drv_video.so - what should...

...so. The one that used to work shows this in Tools/Messages: vdpau_avcodec error: decoder profile not supported: 7 The new one that doesn't work shows this in Tools/Messages: vdpau_avcodec error: decoder profile not supported: 8 I think it might be related to the noveau video driver: $ vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit

..., Seems like you're missed your question. "nouveau_drv_video.so ?" does not mean much I'm afraid :-( On 30 June 2016 at 11:03, poma <pomidorabelisima at gmail.com> wrote: > On 30.06.2016 08:27, Xiang, Haihao wrote: >> >> >> Are you using VA-API on X11? libva gets the driver name from Xserver, >> it is nouveau for you. so libva tries to load nouveau_drv_video.so. >> You can create a symlink for nouveau pointing to a available driver or >> just ignore the message because you have gallium_drv_video.so now. >> Indeed. The tricky par...

...vdpau_avcodec error: decoder profile not supported: 7 >> >> The new one that doesn't work shows this in Tools/Messages: >> vdpau_avcodec error: decoder profile not supported: 8 >> >> I think it might be related to the noveau video driver: >> $ vainfo >> libva info: VA-API version 0.40.0 >> libva info: va_getDriverName() returns 0 >> libva info: Trying to open >> /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so >> libva info: va_openDriver() returns -1 >> vaInitialize failed with error code -1 (unknown libva error),exit I...

Hello my hardware has: 03:00.0 VGA compatible controller: NVIDIA Corporation GT218 [ION] (rev a2) rpm -qa | grep nvidia nvidia-detect-410.78-1.el7.elrepo.x86_64 kmod-nvidia-340xx-340.107-2.el7_6.elrepo.x86_64 nvidia-x11-drv-340xx-340.107-1.el7.elrepo.x86_64 rpm -qa | grep libva libva-vdpau-driver-0.7.4-19.el7.x86_64 libva-utils-1.8.3-4.el7.x86_64 libva-devel-1.8.3-1.el7.x86_64 libva-1.8.3-1.el7.x86_64 rpm -qa | grep vdpau libva-vdpau-driver-0.7.4-19.el7.x86_64 libvdpau-1.1.1-3.el7.x86_64 vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 l...

...his in Tools/Messages: > vdpau_avcodec error: decoder profile not supported: 7 > > The new one that doesn't work shows this in Tools/Messages: > vdpau_avcodec error: decoder profile not supported: 8 > > I think it might be related to the noveau video driver: > $ vainfo > libva info: VA-API version 0.40.0 > libva info: va_getDriverName() returns 0 > libva info: Trying to open > /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so > libva info: va_openDriver() returns -1 > vaInitialize failed with error code -1 (unknown libva error),exit > > ____________...

...profile not supported: 7 >>> >>> The new one that doesn't work shows this in Tools/Messages: >>> vdpau_avcodec error: decoder profile not supported: 8 >>> >>> I think it might be related to the noveau video driver: >>> $ vainfo >>> libva info: VA-API version 0.40.0 >>> libva info: va_getDriverName() returns 0 >>> libva info: Trying to open >>> /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so >>> libva info: va_openDriver() returns -1 >>> vaInitialize failed with error code -1 (unknown...

...ote: >> >> What hardware are you using? > > > 0000:18:00.0 VGA compatible controller: NVIDIA Corporation GP104GL [Quadro P4000] (rev a1) There's no acceleration support for video decoding past Kepler. FWIW I don't get a crash with a GP108 when running vainfo: $ vainfo libva info: VA-API version 1.8.0 libva info: Trying to open /usr/lib64/va/drivers/nouveau_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit with Mesa 20.2.0-rc2. Not sure if your issue has been fixed (and now it errors), or if you'r...

...at barrel SPECS]$ coredumpctl gdb 3926866 PID: 3926866 (test_va_api) UID: 1000 (tkloczko) GID: 1000 (tkloczko) Signal: 11 (SEGV) Timestamp: Sun 2020-09-13 18:57:06 BST (32s ago) Command Line: ./test_va_api Executable: /home/tkloczko/rpmbuild/BUILD/libva-utils-2.9.0/test/test_va_api Control Group: /user.slice/user-1000.slice/session-297.scope Unit: session-297.scope Slice: user-1000.slice Session: 297 Owner UID: 1000 (tkloczko) Boot ID: ab9d350c623e4313bacb892de46b85f9 Machine ID: d033f66b249a4ec09acfa81ac...

...3.30 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.2.0-devel (git-4fd8161773) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: vainfo: vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/X11R7/lib/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Mesa Galliu...

...(II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event11) [ 18.440] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event8) [ 18.441] (II) config/udev: Adding input device HDA Intel PCH Headphone Front (/dev/input/event9) Vainfo fails: vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit [root at nuc5cdev2 tmp]# ls /usr/lib64/dri/ i915_dri.so i965_d...

...e > loader. > > > https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/frontends/va/context.c#n111 > > For the DRM/rendernodes "platform", it will just take whatever fd it > is given. vainfo appears to give it a fixed device: > > > https://github.com/intel/libva-utils/blob/master/common/va_display_drm.c#L39 > > However it looks like you can pass in --device /dev/dri/renderD129 or > whatever the right one is, which should pass in the right render node, > as seen here: > > https://github.com/intel/libva-utils/blob/master/common/va_display.c...

https://bugs.freedesktop.org/show_bug.cgi?id=77102 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mesa-dev at lists.freedesktop. |nouveau at lists.freedesktop.o |org |rg Component|Other

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #7 from Stefan Ringel <mail at stefanringel.de> --- Created attachment 96999 --> https://bugs.freedesktop.org/attachment.cgi?id=96999&action=edit ls -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #8 from Ilia Mirkin <imirkin at alum.mit.edu> --- OK, so it seems like the firmware is correctly in place, and there are no errors coming from dmesg, which means it's getting loaded (or at least isn't failing to load). What version of Mesa are you using? I recently added a feature which auto-detects if firmware is

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #9 from Stefan Ringel <mail at stefanringel.de> --- (In reply to comment #8) > OK, so it seems like the firmware is correctly in place, and there are no > errors coming from dmesg, which means it's getting loaded (or at least isn't > failing to load). > > What version of Mesa are you using? I recently

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #10 from Ilia Mirkin <imirkin at alum.mit.edu> --- Would you mind booting with nouveau.debug=PBSP=trace and putting up a dmesg from that (after the vdpauinfo, that is). BTW, silly question -- do you have a libvdpau_nouveau.so? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #11 from Stefan Ringel <mail at stefanringel.de> --- (In reply to comment #10) > Would you mind booting with > > nouveau.debug=PBSP=trace > > and putting up a dmesg from that (after the vdpauinfo, that is). BTW, silly > question -- do you have a libvdpau_nouveau.so? yes I have libvdpau_nouveau.so. It is