[Bug 217825] multimedia/libva-intel-driver: problem with the driver name
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Mar 16 06:02:00 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217825
Bug ID: 217825
Summary: multimedia/libva-intel-driver: problem with the driver
name
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: madpilot at FreeBSD.org
Reporter: henry.hu.sh at gmail.com
Flags: maintainer-feedback?(madpilot at FreeBSD.org)
Assignee: madpilot at FreeBSD.org
Today, I tried mpv on some mp4 file, and it says
libva info: Trying to open /usr/local/lib/va/i915_drv_video.so
libva info: va_openDriver() returns -1
The same happens for vainfo.
It seems like that only i965_drv_video.so is installed. The reason seems to be
that on Linux, they have i915 and i965 drivers, and only the devices supported
by i965 supports vaapi (some of them).
However, on FreeBSD we only have i915 which supports all the devices.
>From Xorg.0.log we can see
[ 405.175] (II) modeset(0): [DRI2] Setup complete
[ 405.175] (II) modeset(0): [DRI2] DRI driver: i915
[ 405.175] (II) modeset(0): [DRI2] VDPAU driver: i915
while old hardware under linux says
[ 80.051] (II) intel(0): [DRI2] Setup complete
[ 80.051] (II) intel(0): [DRI2] DRI driver: i965
[ 80.051] (II) intel(0): [DRI2] VDPAU driver: va_gl
and libva seems to be loading drivers based on the dri driver name.
The most simple fix seems to be making a symlink to i915_drv_video.so, which is
also somewhere correct, because we do have i915 driver which supports VAAPI.
Another fix may be changing libva's logic and load i965_drv_video.so instead.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list