[elrepo] Intel video on CentOS 6.4 - elrepo libdrm/libva/mesa vs updates

Matt Garman matthew.garman at gmail.com
Mon Oct 7 15:55:42 EDT 2013


(I originally replied to Andrey off-list, but after thinking about it some
more, believe it's relevant to the elrepo list in general.)

One of the biggest differences between my install (vaapi not working) and
Andrey's (vaapi working) is the source of some key packages, particularly
libdrm, libva, and mesa.  (See below for his package list versus mine.)

In short, I'm using the libdrm and mesa packages from CentOS's "updates"
repository, which are newer than that of elrepo.  I know this wasn't
originally the case, as when I first started messing with all this, elrepo
was way ahead of the upstream release.  But at some point it seems upstream
leap-frogged elrepo.

With libva, it's a little trickier: elrepo has a newer version, but it
conflicts with upstream's "libva1" package.  (Side note: I'm also using the
ATrpms repo, which includes even more libva packages, making things still
more muddy.)

Given this, does it make any sense to do away with elrepo's libdrm and mesa
packages, and simply defer to upstream?  And maybe rename the "libva"
package to "libva1" to be compatible with upstream?  Or would these changes
cause breakages that aren't obvious to me?

Thanks,
Matt


His package list:
On Sat, Oct 5, 2013 at 3:52 PM, Andrey Zhunev <a-j at a-j.ru> wrote:

> # rpm -qa |grep elrepo |sort
> clang-3.0-5.el6.elrepo.x86_64
> clang-devel-3.0-5.el6.elrepo.x86_64
> elrepo-release-6-5.el6.elrepo.noarch
> intel-gpu-tools-2.21.2-1.el6.elrepo.x86_64
> khrplatform-devel-8.0.5-1.el6.elrepo.noarch
> libdrm-2.4.31-3.el6.elrepo.x86_64
> libdrm-devel-2.4.31-3.el6.elrepo.x86_64
> libva-1.1.0-1.el6.elrepo.x86_64
> libva-devel-1.1.0-1.el6.elrepo.x86_64
> libva-utils-1.1.0-1.el6.elrepo.x86_64
> llvm-3.0-5.el6.elrepo.x86_64
> llvm-devel-3.0-5.el6.elrepo.x86_64
> llvm-libs-3.0-5.el6.elrepo.x86_64
> llvm-ocaml-3.0-5.el6.elrepo.x86_64
> llvm-ocaml-devel-3.0-5.el6.elrepo.x86_64
> mesa-dri-drivers-8.0.5-1.el6.elrepo.x86_64
> mesa-dri-filesystem-8.0.5-1.el6.elrepo.x86_64
> mesa-libGL-8.0.5-1.el6.elrepo.x86_64
> mesa-libGL-devel-8.0.5-1.el6.elrepo.x86_64
> mesa-libGLU-8.0.5-1.el6.elrepo.x86_64
> mesa-libGLU-devel-8.0.5-1.el6.elrepo.x86_64
> mesa-libOSMesa-8.0.5-1.el6.elrepo.x86_64
> mesa-libOSMesa-devel-8.0.5-1.el6.elrepo.x86_64
> vaapi-driver-intel-1.0.17-1.el6.elrepo.x86_64
> xorg-x11-drv-intel-2.21.2-1.el6.elrepo.x86_64
> xorg-x11-drv-intel-devel-2.21.2-1.el6.elrepo.x86_64



And here's what I have:
# rpm -qa  | egrep "(mesa|libva|libdrm)" | sort
libdrm-2.4.39-1.el6.x86_64
libdrm-devel-2.4.39-1.el6.x86_64
libva-0.31.1.1_1-0.31.1-2_sds5.el6.x86_64
libva-0.32.0.2_1-0.32.0-4_sds2.el6.x86_64
libva-1.0.15-7.el6.x86_64
libva1-1.0.15-7.el6.x86_64
libva-compat0-0.32.0-4_sds2.el6.x86_64
libva-devel-1.0.15-7.el6.x86_64
libva-egl-0.32.0.2_1-0.32.0-4_sds2.el6.x86_64
libva-egl1-1.0.15-7.el6.x86_64
libva-glx-0.31.1.1_1-0.31.1-2_sds5.el6.x86_64
libva-glx-0.32.0.2_1-0.32.0-4_sds2.el6.x86_64
libva-glx1-1.0.15-7.el6.x86_64
libva-tpi-0.31.1.1_1-0.31.1-2_sds5.el6.x86_64
libva-tpi-0.32.0.2_1-0.32.0-4_sds2.el6.x86_64
libva-tpi1-1.0.15-7.el6.x86_64
libva-vdpau-driver-0.7.4-3.el6.1.x86_64
libva-x11-0.31.1.1_1-0.31.1-2_sds5.el6.x86_64
libva-x11-0.32.0.2_1-0.32.0-4_sds2.el6.x86_64
libva-x11_1-1.0.15-7.el6.x86_64
mesa-demos-9.0-0.8.el6_4.3.x86_64
mesa-dri1-drivers-7.11-8.el6.x86_64
mesa-dri-drivers-9.0-0.8.el6_4.3.x86_64
mesa-dri-filesystem-9.0-0.8.el6_4.3.x86_64
mesa-libGL-9.0-0.8.el6_4.3.x86_64
mesa-libGL-devel-9.0-0.8.el6_4.3.x86_64
mesa-libGLU-9.0-0.8.el6_4.3.x86_64
mesa-libGLU-devel-9.0-0.8.el6_4.3.x86_64
mesa-libGLw-6.5.1-10.el6.x86_64
mesa-libGLw-devel-6.5.1-10.el6.x86_64
mesa-libOSMesa-9.0-0.8.el6_4.3.x86_64
mesa-libOSMesa-devel-9.0-0.8.el6_4.3.x86_64
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo/attachments/20131007/d113f3d9/attachment.html>


More information about the elrepo mailing list