Bug#736944: nvidia-legacy-304xx-driver: vdpau driver missing, causes floating point exception

[Andreas Beckmann]

Control: reassign -1 vdpau-va-driver 0.7.4-dmo1
Control: close -1

On 2014-01-28 18:18, debbug.nvidia.legacy.nospam.plz at sub.noloop.net wrote:
> It seems the VDPAU video acceleration driver files are missing from 
> the nvidia-legacy-304xx-driver package (or related packages).

There is no use in providing vdpau-something for 304xx legacy: all
devices that support vdpau are supprted by the current driver.

> Example output of "vainfo":
> 
> libva info: VA-API version 0.34.0
> libva info: va_getDriverName() returns 0
> libva info: Trying to open /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so
> libva info: Found init function __vaDriverInit_0_34
> Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
> Floating point exception

That only happens with vdpau-va-driver from DMO. Not a package supplied
by Debian. Look for support at DMO.


Andreas

PS: since your device does not support vdpau, you could just remove
vdpau-va-driver

PPS: this is vainfo output using the Debian vdpau-va-driver package:

$ vainfo
libva info: VA-API version 0.34.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_0_32
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared
object file: No such file or directory
libva error: /usr/lib/i386-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