* libvdpau: cannot open shared object
@ 2017-12-10 14:14 Marco van Hulten
2017-12-10 14:30 ` ng0
2017-12-10 20:08 ` Efraim Flashner
0 siblings, 2 replies; 15+ messages in thread
From: Marco van Hulten @ 2017-12-10 14:14 UTC (permalink / raw)
To: help-guix
Hi,
I am having a problem with kodi, which I installed on a clean
install of GuixSD 0.14.0 on amd64. It was looking for libvdpau, so I
installed it. Hereafter I get this:
kodi@watson ~$ vdpauinfo
display: :0.0 screen: 0
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared
object Error creating VDPAU device: 1
Running `kodi` gives the same error. The VDPAU problem seems like
something that I should solve first, before continuing with kodi.
Thanks,
—Marco
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-10 14:14 libvdpau: cannot open shared object Marco van Hulten
@ 2017-12-10 14:30 ` ng0
2017-12-10 15:04 ` Marco van Hulten
2017-12-10 20:08 ` Efraim Flashner
1 sibling, 1 reply; 15+ messages in thread
From: ng0 @ 2017-12-10 14:30 UTC (permalink / raw)
To: Marco van Hulten; +Cc: help-guix
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
For what it's worth: I've been having crashes with Kodi
for months now. Now back on a new system (installed from
my dev branch that is a couple of commits ahead of guix master)
I get a Kodi that has no visible font characters (even with
fonts installed in my profile, and rebooting + fc-cache -vf run)
and an vdpau / nouveau error message on startup.
Were you able to start Kodi before without issues?
Marco van Hulten transcribed 0.5K bytes:
> Hi,
>
> I am having a problem with kodi, which I installed on a clean
> install of GuixSD 0.14.0 on amd64. It was looking for libvdpau, so I
> installed it. Hereafter I get this:
>
> kodi@watson ~$ vdpauinfo
> display: :0.0 screen: 0
> Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared
> object Error creating VDPAU device: 1
>
> Running `kodi` gives the same error. The VDPAU problem seems like
> something that I should solve first, before continuing with kodi.
>
> Thanks,
>
> —Marco
>
>
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
WWW: https://n0.is
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-10 14:30 ` ng0
@ 2017-12-10 15:04 ` Marco van Hulten
0 siblings, 0 replies; 15+ messages in thread
From: Marco van Hulten @ 2017-12-10 15:04 UTC (permalink / raw)
To: ng0; +Cc: help-guix
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
ng0—
Je 10 dec 14:30 skribis ng0:
> For what it's worth: I've been having crashes with Kodi
> for months now.
This is worth something: we can now share the pain :-)
> Now back on a new system (installed from
> my dev branch that is a couple of commits ahead of guix master)
> I get a Kodi that has no visible font characters (even with
> fonts installed in my profile, and rebooting + fc-cache -vf run)
> and an vdpau / nouveau error message on startup.
I am using the "intel" X11 module, so it does not appear to be related
to which video card one uses.
> Were you able to start Kodi before without issues?
About a month ago, I could start Kodi without issues, on the same
hardware on GuixSD 0.13.0. When I then rolled back to the working
version, I could run kodi again. After some more testing, rolling back
did not help anymore: kodi kept crashing. I documented it in a thread
on this mailinglist about two weeks ago.
Yesterday I did a clean install of GuixSD 0.14.0. Ludo' had pointed out
that reinstalling the system is not useful, but I tried anyway when
0.14.0 came out (partly because of the inconsistent roll-back
behaviour). I think I still have the same problems (at least for the
VDPAU error).
—Marco
[-- Attachment #2: OpenPGP digitale handtekening --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-10 14:14 libvdpau: cannot open shared object Marco van Hulten
2017-12-10 14:30 ` ng0
@ 2017-12-10 20:08 ` Efraim Flashner
2017-12-12 16:44 ` Ludovic Courtès
1 sibling, 1 reply; 15+ messages in thread
From: Efraim Flashner @ 2017-12-10 20:08 UTC (permalink / raw)
To: Marco van Hulten; +Cc: help-guix
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On Sun, Dec 10, 2017 at 03:14:53PM +0100, Marco van Hulten wrote:
> Hi,
>
> I am having a problem with kodi, which I installed on a clean
> install of GuixSD 0.14.0 on amd64. It was looking for libvdpau, so I
> installed it. Hereafter I get this:
>
> kodi@watson ~$ vdpauinfo
> display: :0.0 screen: 0
> Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared
> object Error creating VDPAU device: 1
>
> Running `kodi` gives the same error. The VDPAU problem seems like
> something that I should solve first, before continuing with kodi.
>
> Thanks,
>
> —Marco
>
I just want to add that I ran:
'guix environment --ad-hoc vdpauinfo -- vdpauinfo'
on my x86_64 GuixSD machine and I got the following:
display: :0.0 screen: 0
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory
Error creating VDPAU device: 1
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-10 20:08 ` Efraim Flashner
@ 2017-12-12 16:44 ` Ludovic Courtès
2017-12-12 19:58 ` Efraim Flashner
0 siblings, 1 reply; 15+ messages in thread
From: Ludovic Courtès @ 2017-12-12 16:44 UTC (permalink / raw)
To: Efraim Flashner; +Cc: help-guix
Hi!
Efraim Flashner <efraim@flashner.co.il> skribis:
> I just want to add that I ran:
> 'guix environment --ad-hoc vdpauinfo -- vdpauinfo'
> on my x86_64 GuixSD machine and I got the following:
>
> display: :0.0 screen: 0
> Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory
> Error creating VDPAU device: 1
Same here.
I searched for “libvdpau_i965.so” on the intertubes and it seems to be a
problem “everyone has.” For instance:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869815
So it seems that we lack a driver package.
Ludo’.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-12 16:44 ` Ludovic Courtès
@ 2017-12-12 19:58 ` Efraim Flashner
2017-12-14 9:07 ` Ludovic Courtès
0 siblings, 1 reply; 15+ messages in thread
From: Efraim Flashner @ 2017-12-12 19:58 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: help-guix
[-- Attachment #1.1: Type: text/plain, Size: 1319 bytes --]
On Tue, Dec 12, 2017 at 05:44:43PM +0100, Ludovic Courtès wrote:
> Hi!
>
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
> > I just want to add that I ran:
> > 'guix environment --ad-hoc vdpauinfo -- vdpauinfo'
> > on my x86_64 GuixSD machine and I got the following:
> >
> > display: :0.0 screen: 0
> > Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory
> > Error creating VDPAU device: 1
>
> Same here.
>
> I searched for “libvdpau_i965.so” on the intertubes and it seems to be a
> problem “everyone has.” For instance:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869815
>
> So it seems that we lack a driver package.
>
> Ludo’.
here's a patch for libvdpau-va-gl. after setting 'VDPAU_DRIVER=va_gl'
and running 'guix environment --ad-hoc libvdpau-va-gl vdpauinfo -- vdpauinfo'
I get:
display: :0.0 screen: 0
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
Error creating VDPAU device: 1
so it still needs some more work
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #1.2: 0001-gnu-Add-libvdpau-va-gl.patch --]
[-- Type: text/plain, Size: 4571 bytes --]
From da659401a0116d0810f003769c933253f5b18f4c Mon Sep 17 00:00:00 2001
From: Efraim Flashner <efraim@flashner.co.il>
Date: Tue, 12 Dec 2017 21:44:49 +0200
Subject: [PATCH] gnu: Add libvdpau-va-gl.
* gnu/packages/video.scm (libvdpau-va-gl): New variable.
* gnu/packages/patches/libvdpau-va-gl-unbundle.patch: New file.
* gnu/local.mk (dist_patch_DATA): Register it.
---
gnu/local.mk | 1 +
gnu/packages/patches/libvdpau-va-gl-unbundle.patch | 35 ++++++++++++++++++++++
gnu/packages/video.scm | 35 ++++++++++++++++++++++
3 files changed, 71 insertions(+)
create mode 100644 gnu/packages/patches/libvdpau-va-gl-unbundle.patch
diff --git a/gnu/local.mk b/gnu/local.mk
index 46829756b..2cfd35cd8 100644
--- a/gnu/local.mk
+++ b/gnu/local.mk
@@ -834,6 +834,7 @@ dist_patch_DATA = \
%D%/packages/patches/libunistring-gnulib-multi-core.patch \
%D%/packages/patches/libusb-0.1-disable-tests.patch \
%D%/packages/patches/libusb-for-axoloti.patch \
+ %D%/packages/patches/libvdpau-va-gl-unbundle.patch \
%D%/packages/patches/libvpx-CVE-2016-2818.patch \
%D%/packages/patches/libxcb-python-3.5-compat.patch \
%D%/packages/patches/libxml2-CVE-2016-4658.patch \
diff --git a/gnu/packages/patches/libvdpau-va-gl-unbundle.patch b/gnu/packages/patches/libvdpau-va-gl-unbundle.patch
new file mode 100644
index 000000000..b15e15c2a
--- /dev/null
+++ b/gnu/packages/patches/libvdpau-va-gl-unbundle.patch
@@ -0,0 +1,35 @@
+From 18e3ff648356cf06a39372aa4a4bbf2732d9d0f4 Mon Sep 17 00:00:00 2001
+From: Efraim Flashner <efraim@flashner.co.il>
+Date: Tue, 12 Dec 2017 21:36:44 +0200
+Subject: [PATCH] don't use bundled libvdpau headers
+
+---
+ CMakeLists.txt | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index 0484179..e950707 100644
+--- a/CMakeLists.txt
++++ b/CMakeLists.txt
+@@ -9,16 +9,17 @@ find_package(PkgConfig REQUIRED)
+ find_package(X11 REQUIRED)
+ pkg_check_modules(LIBVA libva-x11 REQUIRED)
+ pkg_check_modules(LIBGL gl REQUIRED)
++pkg_check_modules(LIBVDPAU vdpau REQUIRED)
+
+ set(DRIVER_NAME "vdpau_va_gl" CACHE STRING "driver name")
+ set(LIB_SUFFIX "" CACHE STRING "library path suffix (if needed)")
+ set(LIB_INSTALL_DIR "${CMAKE_INSTALL_PREFIX}/lib${LIB_SUFFIX}/vdpau" CACHE PATH "library installation path")
+
+ include_directories (
+- 3rdparty
+ ${X11_INCLUDE_DIRS}
+ ${LIBVA_INCLUDE_DIRS}
+ ${LIBGL_INCLUDE_DIRS}
++ ${LIBVDPAU_INCLUDE_DIRS}
+ ${GENERATED_INCLUDE_DIRS}
+ ${CMAKE_BINARY_DIR}
+ )
+--
+2.15.1
+
diff --git a/gnu/packages/video.scm b/gnu/packages/video.scm
index 0bd1be6e6..d8f8081fe 100644
--- a/gnu/packages/video.scm
+++ b/gnu/packages/video.scm
@@ -1864,6 +1864,41 @@ present in modern GPUs.")
implementation.")
(license (license:x11-style "file://COPYING"))))
+(define-public libvdpau-va-gl
+ (package
+ (name "libvdpau-va-gl")
+ (version "0.4.2")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (string-append "https://github.com/i-rinat/libvdpau-va-gl/"
+ "releases/download/v" version "/libvdpau-va-gl-"
+ version ".tar.gz"))
+ (sha256
+ (base32
+ "1x2ag1f2fwa4yh1g5spv99w9x1m33hbxlqwyhm205ssq0ra234bx"))
+ (patches (search-patches "libvdpau-va-gl-unbundle.patch"))
+ (modules '((guix build utils)))
+ (snippet '(delete-file-recursively "3rdparty"))))
+ (build-system cmake-build-system)
+ (arguments
+ '(#:tests? #f)) ; Tests require a running X11 server, with VA-API support.
+ (native-inputs
+ `(("libvdpau" ,libvdpau)
+ ("pkg-config" ,pkg-config)))
+ (inputs
+ `(("libva" ,libva)
+ ("mesa" ,mesa)))
+ (home-page "https://github.com/i-rinat/libvdpau-va-gl")
+ (synopsis "VDPAU driver with VA-API/OpenGL backend")
+ (description
+ "Many applications can use VDPAU to accelerate portions of the video
+decoding process and video post-processing to the GPU video hardware. Since
+there is no VDPAU available on Intel chips, they fall back to different drawing
+techniques. This driver uses OpenGL under the hood to accelerate drawing and
+scaling and VA-API (if available) to accelerate video decoding.")
+ (license license:expat)))
+
(define-public recordmydesktop
(package
(name "recordmydesktop")
--
2.15.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply related [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-12 19:58 ` Efraim Flashner
@ 2017-12-14 9:07 ` Ludovic Courtès
2017-12-15 6:38 ` Efraim Flashner
0 siblings, 1 reply; 15+ messages in thread
From: Ludovic Courtès @ 2017-12-14 9:07 UTC (permalink / raw)
To: Efraim Flashner; +Cc: help-guix
Hi!
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Tue, Dec 12, 2017 at 05:44:43PM +0100, Ludovic Courtès wrote:
[...]
>> I searched for “libvdpau_i965.so” on the intertubes and it seems to be a
>> problem “everyone has.” For instance:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869815
>>
>> So it seems that we lack a driver package.
>>
>> Ludo’.
>
> here's a patch for libvdpau-va-gl. after setting 'VDPAU_DRIVER=va_gl'
> and running 'guix environment --ad-hoc libvdpau-va-gl vdpauinfo -- vdpauinfo'
> I get:
> display: :0.0 screen: 0
> Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
> Error creating VDPAU device: 1
> so it still needs some more work
What if you point LD_LIBRARY_PATH to libvdpau-va-gl?
> From da659401a0116d0810f003769c933253f5b18f4c Mon Sep 17 00:00:00 2001
> From: Efraim Flashner <efraim@flashner.co.il>
> Date: Tue, 12 Dec 2017 21:44:49 +0200
> Subject: [PATCH] gnu: Add libvdpau-va-gl.
>
> * gnu/packages/video.scm (libvdpau-va-gl): New variable.
> * gnu/packages/patches/libvdpau-va-gl-unbundle.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Register it.
[...]
> + (native-inputs
> + `(("libvdpau" ,libvdpau)
Should move to ‘inputs’ I guess?
Otherwise LGTM, thanks for acting this fast!
When we have that, we can at least arrange for things to work
out-of-the-box on GuixSD. It’s better if we can do that without setting
LD_LIBRARY_PATH, we’ll have to investigate how this can be done. At
least, we’ll have to set VDPAU_DRIVER=va_gl I presume?
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-14 9:07 ` Ludovic Courtès
@ 2017-12-15 6:38 ` Efraim Flashner
2017-12-15 11:02 ` Ludovic Courtès
0 siblings, 1 reply; 15+ messages in thread
From: Efraim Flashner @ 2017-12-15 6:38 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: help-guix
[-- Attachment #1: Type: text/plain, Size: 3494 bytes --]
On Thu, Dec 14, 2017 at 10:07:20AM +0100, Ludovic Courtès wrote:
> Hi!
>
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
> > On Tue, Dec 12, 2017 at 05:44:43PM +0100, Ludovic Courtès wrote:
>
> [...]
>
> >> I searched for “libvdpau_i965.so” on the intertubes and it seems to be a
> >> problem “everyone has.” For instance:
> >>
> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869815
> >>
> >> So it seems that we lack a driver package.
> >>
> >> Ludo’.
> >
> > here's a patch for libvdpau-va-gl. after setting 'VDPAU_DRIVER=va_gl'
> > and running 'guix environment --ad-hoc libvdpau-va-gl vdpauinfo -- vdpauinfo'
> > I get:
> > display: :0.0 screen: 0
> > Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
> > Error creating VDPAU device: 1
> > so it still needs some more work
>
> What if you point LD_LIBRARY_PATH to libvdpau-va-gl?
>
> > From da659401a0116d0810f003769c933253f5b18f4c Mon Sep 17 00:00:00 2001
> > From: Efraim Flashner <efraim@flashner.co.il>
> > Date: Tue, 12 Dec 2017 21:44:49 +0200
> > Subject: [PATCH] gnu: Add libvdpau-va-gl.
> >
> > * gnu/packages/video.scm (libvdpau-va-gl): New variable.
> > * gnu/packages/patches/libvdpau-va-gl-unbundle.patch: New file.
> > * gnu/local.mk (dist_patch_DATA): Register it.
>
> [...]
>
> > + (native-inputs
> > + `(("libvdpau" ,libvdpau)
>
> Should move to ‘inputs’ I guess?
>
> Otherwise LGTM, thanks for acting this fast!
$ guix gc --references $(guix build libvdpau-va-gl)
/gnu/store/1zfmi6bixxz3fljr4kfy37xpjial90p1-libva-1.8.3
/gnu/store/3h31zsqxjjg52da5gp3qmhkh4x8klhah-glibc-2.25
/gnu/store/6wyjls0q2c9gjskkplsr1ad09p3d8gzg-gcc-5.4.0-lib
/gnu/store/7mdyg1vigcxqb1ra16mdqnhz8aa00xc7-libxext-1.3.3
/gnu/store/8z7130mb33a3jqliqs6bq2d46mar5gqy-mesa-17.2.1
/gnu/store/d3pbj6vynkig0v0lnwp9nh04sijxin2w-libvdpau-va-gl-0.4.2
/gnu/store/p37m873k9k69m944njar80i6bsmqrcvj-libx11-1.6.5
libvdpau is actually a propagated input of mesa
>
> When we have that, we can at least arrange for things to work
> out-of-the-box on GuixSD. It’s better if we can do that without setting
> LD_LIBRARY_PATH, we’ll have to investigate how this can be done. At
> least, we’ll have to set VDPAU_DRIVER=va_gl I presume?
>
> Thanks,
> Ludo’.
From the upstream documentation VDPAU_DRIVER=va_gl is the minimum needed
to get it working, and then there are a couple of other environmental
variables that can be set to change its behavior.
$ VDPAU_DRIVER=va_gl LD_LIBRARY_PRELOAD=$(guix build libvdpau-va-gl) env | grep VDPAU
VDPAU_DRIVER=va_gl
$ VDPAU_DRIVER=va_gl LD_LIBRARY_PRELOAD=$(guix build libvdpau-va-gl) vdpauinfo
display: :0.0 screen: 0
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
Error creating VDPAU device: 1
Not so helpful to us, but upstream wants us to install it in the same
directory as the other vdpau*so files. I suppose we could add a
mesa-headers package and use that to build it and then just copy it into
mesa-out/lib/vdpau, but I really don't like that idea. I'm inclined to
push it as is and then we'll work out exactly how to make it work for
us.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-15 6:38 ` Efraim Flashner
@ 2017-12-15 11:02 ` Ludovic Courtès
2017-12-15 12:18 ` Efraim Flashner
0 siblings, 1 reply; 15+ messages in thread
From: Ludovic Courtès @ 2017-12-15 11:02 UTC (permalink / raw)
To: Efraim Flashner; +Cc: help-guix
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Thu, Dec 14, 2017 at 10:07:20AM +0100, Ludovic Courtès wrote:
[...]
>> > From da659401a0116d0810f003769c933253f5b18f4c Mon Sep 17 00:00:00 2001
>> > From: Efraim Flashner <efraim@flashner.co.il>
>> > Date: Tue, 12 Dec 2017 21:44:49 +0200
>> > Subject: [PATCH] gnu: Add libvdpau-va-gl.
>> >
>> > * gnu/packages/video.scm (libvdpau-va-gl): New variable.
>> > * gnu/packages/patches/libvdpau-va-gl-unbundle.patch: New file.
>> > * gnu/local.mk (dist_patch_DATA): Register it.
>>
>> [...]
>>
>> > + (native-inputs
>> > + `(("libvdpau" ,libvdpau)
>>
>> Should move to ‘inputs’ I guess?
>>
>> Otherwise LGTM, thanks for acting this fast!
>
> $ guix gc --references $(guix build libvdpau-va-gl)
> /gnu/store/1zfmi6bixxz3fljr4kfy37xpjial90p1-libva-1.8.3
> /gnu/store/3h31zsqxjjg52da5gp3qmhkh4x8klhah-glibc-2.25
> /gnu/store/6wyjls0q2c9gjskkplsr1ad09p3d8gzg-gcc-5.4.0-lib
> /gnu/store/7mdyg1vigcxqb1ra16mdqnhz8aa00xc7-libxext-1.3.3
> /gnu/store/8z7130mb33a3jqliqs6bq2d46mar5gqy-mesa-17.2.1
> /gnu/store/d3pbj6vynkig0v0lnwp9nh04sijxin2w-libvdpau-va-gl-0.4.2
> /gnu/store/p37m873k9k69m944njar80i6bsmqrcvj-libx11-1.6.5
>
> libvdpau is actually a propagated input of mesa
OK.
>> When we have that, we can at least arrange for things to work
>> out-of-the-box on GuixSD. It’s better if we can do that without setting
>> LD_LIBRARY_PATH, we’ll have to investigate how this can be done. At
>> least, we’ll have to set VDPAU_DRIVER=va_gl I presume?
>>
>> Thanks,
>> Ludo’.
>
> From the upstream documentation VDPAU_DRIVER=va_gl is the minimum needed
> to get it working, and then there are a couple of other environmental
> variables that can be set to change its behavior.
>
> $ VDPAU_DRIVER=va_gl LD_LIBRARY_PRELOAD=$(guix build libvdpau-va-gl) env | grep VDPAU
> VDPAU_DRIVER=va_gl
>
> $ VDPAU_DRIVER=va_gl LD_LIBRARY_PRELOAD=$(guix build libvdpau-va-gl) vdpauinfo
> display: :0.0 screen: 0
> Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
> Error creating VDPAU device: 1
It should be:
LD_LIBRARY_PATH=$(guix build libvdpau-va-gl)/lib
or:
LD_PRELOAD=$(guix build libvdpau-va-gl)/lib/libwhatever-its-called.so
HTH!
Ludo’.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-15 11:02 ` Ludovic Courtès
@ 2017-12-15 12:18 ` Efraim Flashner
2017-12-15 14:31 ` Ludovic Courtès
0 siblings, 1 reply; 15+ messages in thread
From: Efraim Flashner @ 2017-12-15 12:18 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: help-guix
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
On Fri, Dec 15, 2017 at 12:02:14PM +0100, Ludovic Courtès wrote:
>
> It should be:
>
> LD_LIBRARY_PATH=$(guix build libvdpau-va-gl)/lib
$ VDPAU_DRIVER=va_gl LD_LIBRARY_PATH=$(guix build libvdpau-va-gl)/lib vdpauinfo
display: :0.0 screen: 0
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
Error creating VDPAU device: 1
>
> or:
>
> LD_PRELOAD=$(guix build libvdpau-va-gl)/lib/libwhatever-its-called.so
$ VDPAU_DRIVER=va_gl LD_PRELOAD=$(guix build libvdpau-va-gl)/lib/vdpau/libvdpau_va_gl.so vdpauinfo
display: :0.0 screen: 0
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
Error creating VDPAU device: 1
>
> HTH!
>
> Ludo’.
Not sure what's going on with this one :/
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-15 12:18 ` Efraim Flashner
@ 2017-12-15 14:31 ` Ludovic Courtès
2017-12-16 8:08 ` Marco van Hulten
2017-12-16 17:05 ` Efraim Flashner
0 siblings, 2 replies; 15+ messages in thread
From: Ludovic Courtès @ 2017-12-15 14:31 UTC (permalink / raw)
To: Efraim Flashner; +Cc: help-guix
Efraim Flashner <efraim@flashner.co.il> skribis:
> $ VDPAU_DRIVER=va_gl LD_LIBRARY_PATH=$(guix build libvdpau-va-gl)/lib vdpauinfo
> display: :0.0 screen: 0
> Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
> Error creating VDPAU device: 1
Well the exact line is this:
VDPAU_DRIVER=va_gl \
LD_LIBRARY_PATH=$(./pre-inst-env guix build libvdpau-va-gl)/lib/vdpau \
$(guix build vdpauinfo)/bin/vdpauinfo
Works for me! It displays lots of things. :-)
So I think you can push the package, and then we need to figure out what
to do on GuixSD with ‘VDPAU_DRIVER’ (set it unconditionally to ‘va_gl’?)
and how to avoid LD_LIBRARY_PATH.
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-15 14:31 ` Ludovic Courtès
@ 2017-12-16 8:08 ` Marco van Hulten
2017-12-16 19:00 ` Ricardo Wurmus
2017-12-16 17:05 ` Efraim Flashner
1 sibling, 1 reply; 15+ messages in thread
From: Marco van Hulten @ 2017-12-16 8:08 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: help-guix
Ludovic—
Je 15 dec 15:31 skribis Ludovic:
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
> > $ VDPAU_DRIVER=va_gl LD_LIBRARY_PATH=$(guix build libvdpau-va-gl)/lib vdpauinfo
> > display: :0.0 screen: 0
> > Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
> > Error creating VDPAU device: 1
>
> Well the exact line is this:
>
> VDPAU_DRIVER=va_gl \
> LD_LIBRARY_PATH=$(./pre-inst-env guix build libvdpau-va-gl)/lib/vdpau \
> $(guix build vdpauinfo)/bin/vdpauinfo
>
> Works for me! It displays lots of things. :-)
> [...]
It does not work for me, still cannot find 'libvdpau_va_gl.so'.
I am trying to understand the commands that you use to define
LD_LIBRARY_PATH:
kodi@watson ~$ guix build libvdpau-va-gl
guix build: error: libvdpau-va-gl: unknown package
kodi@watson ~$ guix build vdpauinfo
/gnu/store/46x8ba3q11zgq8qygqpgkv41ws9km9b1-vdpauinfo-1.0
Where can I find 'pre-inst-env'? Does this make guix aware of the
libvdpau-va-gl package?
I'm running GuixSD 0.14.0 on real hardware, and did a pull and upgrade
just yesterday.
—Marco
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-15 14:31 ` Ludovic Courtès
2017-12-16 8:08 ` Marco van Hulten
@ 2017-12-16 17:05 ` Efraim Flashner
2017-12-18 20:40 ` Ludovic Courtès
1 sibling, 1 reply; 15+ messages in thread
From: Efraim Flashner @ 2017-12-16 17:05 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: help-guix
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
On Fri, Dec 15, 2017 at 03:31:29PM +0100, Ludovic Courtès wrote:
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
> > $ VDPAU_DRIVER=va_gl LD_LIBRARY_PATH=$(guix build libvdpau-va-gl)/lib vdpauinfo
> > display: :0.0 screen: 0
> > Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
> > Error creating VDPAU device: 1
>
> Well the exact line is this:
>
> VDPAU_DRIVER=va_gl \
> LD_LIBRARY_PATH=$(./pre-inst-env guix build libvdpau-va-gl)/lib/vdpau \
> $(guix build vdpauinfo)/bin/vdpauinfo
>
> Works for me! It displays lots of things. :-)
>
It seems I forgot the '/vdpau'
> So I think you can push the package, and then we need to figure out what
> to do on GuixSD with ‘VDPAU_DRIVER’ (set it unconditionally to ‘va_gl’?)
> and how to avoid LD_LIBRARY_PATH.
The VDPAU_DRIVER is actually a mesa environmental variable IIRC, so
setting it unconditionally would negatively affect others.
>
> Thanks,
> Ludo’.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-16 8:08 ` Marco van Hulten
@ 2017-12-16 19:00 ` Ricardo Wurmus
0 siblings, 0 replies; 15+ messages in thread
From: Ricardo Wurmus @ 2017-12-16 19:00 UTC (permalink / raw)
To: Marco van Hulten; +Cc: help-guix
Hi Marco,
> Ludovic—
>
> Je 15 dec 15:31 skribis Ludovic:
>> Efraim Flashner <efraim@flashner.co.il> skribis:
>>
>> > $ VDPAU_DRIVER=va_gl LD_LIBRARY_PATH=$(guix build libvdpau-va-gl)/lib vdpauinfo
>> > display: :0.0 screen: 0
>> > Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
>> > Error creating VDPAU device: 1
>>
>> Well the exact line is this:
>>
>> VDPAU_DRIVER=va_gl \
>> LD_LIBRARY_PATH=$(./pre-inst-env guix build libvdpau-va-gl)/lib/vdpau \
>> $(guix build vdpauinfo)/bin/vdpauinfo
>>
>> Works for me! It displays lots of things. :-)
>> [...]
>
> It does not work for me, still cannot find 'libvdpau_va_gl.so'.
> I am trying to understand the commands that you use to define
> LD_LIBRARY_PATH:
>
> kodi@watson ~$ guix build libvdpau-va-gl
> guix build: error: libvdpau-va-gl: unknown package
> kodi@watson ~$ guix build vdpauinfo
> /gnu/store/46x8ba3q11zgq8qygqpgkv41ws9km9b1-vdpauinfo-1.0p
>
> Where can I find 'pre-inst-env'? Does this make guix aware of the
> libvdpau-va-gl package?
“pre-inst-env” is a wrapper script that will be created when building
Guix from a git checkout. It ensures that the (possibly modified)
source directory is used for all operations.
If you don’t have a source checkout then you won’t have that script as
you don’t have a need for it.
This discussion is about a change that is not yet part of Guix.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: libvdpau: cannot open shared object
2017-12-16 17:05 ` Efraim Flashner
@ 2017-12-18 20:40 ` Ludovic Courtès
0 siblings, 0 replies; 15+ messages in thread
From: Ludovic Courtès @ 2017-12-18 20:40 UTC (permalink / raw)
To: Efraim Flashner; +Cc: help-guix
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Fri, Dec 15, 2017 at 03:31:29PM +0100, Ludovic Courtès wrote:
[...]
>> So I think you can push the package, and then we need to figure out what
>> to do on GuixSD with ‘VDPAU_DRIVER’ (set it unconditionally to ‘va_gl’?)
>> and how to avoid LD_LIBRARY_PATH.
>
> The VDPAU_DRIVER is actually a mesa environmental variable IIRC, so
> setting it unconditionally would negatively affect others.
How should it be handled?
I’m under the impression that ‘va_gl’ is the generic driver that works
for everyone, but that there might be optimized drivers for specific
pieces of hardware, is that correct?
If it is, we could always use ‘va_gl’ as the default.
As for LD_LIBRARY_PATH, perhaps we need a central location for these
drivers on GuixSD, like /run/current-system/vdpau?
Ludo’.
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2017-12-18 20:40 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-12-10 14:14 libvdpau: cannot open shared object Marco van Hulten
2017-12-10 14:30 ` ng0
2017-12-10 15:04 ` Marco van Hulten
2017-12-10 20:08 ` Efraim Flashner
2017-12-12 16:44 ` Ludovic Courtès
2017-12-12 19:58 ` Efraim Flashner
2017-12-14 9:07 ` Ludovic Courtès
2017-12-15 6:38 ` Efraim Flashner
2017-12-15 11:02 ` Ludovic Courtès
2017-12-15 12:18 ` Efraim Flashner
2017-12-15 14:31 ` Ludovic Courtès
2017-12-16 8:08 ` Marco van Hulten
2017-12-16 19:00 ` Ricardo Wurmus
2017-12-16 17:05 ` Efraim Flashner
2017-12-18 20:40 ` Ludovic Courtès
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).