the merge finished without an error but vdpau isnt installed .... i modified the ebuild to get vdpau back :) please look at it an apply :) Reproducible: Always Steps to Reproduce: 1.emerge nvidia-drivers
Created attachment 213251 [details, diff] patch to fix the ebuild
Tha patch works fine here for vdpau. However, I don't have video playback when using xvmc, could this be related?
*** Bug 297271 has been marked as a duplicate of this bug. ***
Created attachment 213405 [details, diff] modified patch - i think the other paths can stay as they are
The patch don't apply here, I added /usr/lib64/vdpau into /etc/ld.conf (temporary solution) which seems to work for me.
Created attachment 213812 [details, diff] updated patch to fix "new" ebuild
(In reply to comment #5) > The patch don't apply here, I added /usr/lib64/vdpau into /etc/ld.conf > (temporary solution) which seems to work for me. > same here.
The bug http://bugs.gentoo.org/show_bug.cgi?id=298142 contains an ebuild for nvidia-drivers-195.30, which is newer.The ebuild in bug 298142 installs vdpau, at least on my system. If you want to install the old 190.53 driver, renaming the ebuild in bug 298142 to 190.53 should suffice.
it should work do cd /usr/portage/x11-drivers/nvidia-drivers patch -p5 < nvidia.patch ebuild nvidia-drivers-190.53.ebuild digest emerge nvidia-drivers and it should work
(In reply to comment #6) > Created an attachment (id=213812) [details] > updated patch to fix "new" ebuild > The VDPAU libraries belong in /usr/lib[32,64]/vdpau. Read the release notes by NVIDIA for 190.53. Applications should never link directly against libvdpau_nvidia.so but it appears some applications are incorrectly doing this. The ABI has changed to libvdpau_nvidia.so so applications will experience problems. Applications should always use libvdpau.so, which provides a proper abstraction for the specific implementation. x11-libs/libvdpau-0.3 has been updated by NVIDIA to use the new paths and as such its properly listed as a PDEPEND in the 190.53 ebuilds. Rather than incorrectly changing the paths back, please say which apps you are having a problem with so they may be fixed. The big issue that apps will have is the fact that VDPAU is no longer a mutually exclusive operation and can be multiplexed with other operations such as OpenGL and even other VDPAU instances. This requires apps to use proper locks, which none of them do because the locking mechanism is abstracted away inside libvdpau. So using VDPAU and OpenGL at the same time for an app that uses libvdpau_nvidia.so directly will result in screen corruption.
with this driver, i cannot watch videos in mplayer....
(In reply to comment #11) > with this driver, i cannot watch videos in mplayer.... > Yes. Its been reported to the mplayer guys that they are linking directly against libvdpau_nvidia.so and it needs to be corrected. It's an upstream bug. mplayer + nvidia-drivers 190.53 + compiz = crashes & screen corruption because mplayer isn't using the libvdpau API properly which is resulting in issues.
(In reply to comment #12) > (In reply to comment #11) > > with this driver, i cannot watch videos in mplayer.... > > > > Yes. Its been reported to the mplayer guys that they are linking directly > against libvdpau_nvidia.so and it needs to be corrected. It's an upstream bug. > mplayer + nvidia-drivers 190.53 + compiz = crashes & screen corruption because > mplayer isn't using the libvdpau API properly which is resulting in issues. > I have the same problem, seems I have to spend a vdpau-free Christmas day:(
vdpau is used by ffmpeg, mythtv,xmbc. Do they use vdpau correctly? Can someone check this?
(In reply to comment #14) > vdpau is used by ffmpeg, mythtv,xmbc. > > Do they use vdpau correctly? Can someone check this? > I can confirm that it's broken in mythtv as well. I had to downgrade to the previous nvidia driver just so I could play videos through mythtv.
(In reply to comment #15) > (In reply to comment #14) > > vdpau is used by ffmpeg, mythtv,xmbc. > > > > Do they use vdpau correctly? Can someone check this? > > > > I can confirm that it's broken in mythtv as well. I had to downgrade to the > previous nvidia driver just so I could play videos through mythtv. > What version of MythTV? emerge -pv mythtv ldd /usr/bin/mythfrontend | grep vdpau Because it works just fine for me with MythTV.
(In reply to comment #13) > (In reply to comment #12) > > (In reply to comment #11) > > > with this driver, i cannot watch videos in mplayer.... > > > > > > > Yes. Its been reported to the mplayer guys that they are linking directly > > against libvdpau_nvidia.so and it needs to be corrected. It's an upstream bug. > > mplayer + nvidia-drivers 190.53 + compiz = crashes & screen corruption because > > mplayer isn't using the libvdpau API properly which is resulting in issues. > > > > I have the same problem, seems I have to spend a vdpau-free Christmas day:( > For mplayer support, downgrade to an older version of nvidia-drivers. emerge =x11-drivers/nvidia-drivers-190.42-r3
(In reply to comment #17) > (In reply to comment #13) > > (In reply to comment #12) > > > (In reply to comment #11) > > > > with this driver, i cannot watch videos in mplayer.... > > > > > > > > > > Yes. Its been reported to the mplayer guys that they are linking directly > > > against libvdpau_nvidia.so and it needs to be corrected. It's an upstream bug. > > > mplayer + nvidia-drivers 190.53 + compiz = crashes & screen corruption because > > > mplayer isn't using the libvdpau API properly which is resulting in issues. > > > > > > > I have the same problem, seems I have to spend a vdpau-free Christmas day:( > > > > For mplayer support, downgrade to an older version of nvidia-drivers. > > emerge =x11-drivers/nvidia-drivers-190.42-r3 > It's okay.. I don't have to use vdpau..... Thanks :)
I can confirm it fails on mythtv-0.22_p22860 as well. mythtv is only loading libvdpau.so.1 - it looks like libvdpau.so.1 cannot load libvdpau_nvidia.so unless I symlink it from lib64/vdpau to lib64. I'm using manuel@legend ~ $ emerge -pv libvdpau These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] x11-libs/libvdpau-0.3 USE="-doc" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB manuel@legend ~ $ emerge -pv mythtv These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] media-tv/mythtv-0.22_p22860 USE="alsa autostart css dvb fftw lcd lirc mmx perl python vdpau (-altivec) -debug -directv -faad -ieee1394 -jack -pulseaudio -tiff -xvmc" VIDEO_CARDS="-nvidia -via" 0 kB manuel@legend ~ $ ldd `which mythfrontend` | grep vdpau libvdpau.so.1 => /usr/lib/libvdpau.so.1 (0x00007fd3b4e06000) manuel@legend ~ $ ldd /usr/lib/libvdpau.so.1 linux-vdso.so.1 => (0x00007fff5d8d0000) libdl.so.2 => /lib/libdl.so.2 (0x00007f287c85d000) libc.so.6 => /lib/libc.so.6 (0x00007f287c50b000) /lib64/ld-linux-x86-64.so.2 (0x00007f287cc78000) I remerged libvdpau after installing the new driver just in case that fixed it but it had no effect on the problem. I'm currently using the workaround of symlinking the library into lib64.
@ comment #12 Doug Goldstein wrote "Yes. Its been reported to the mplayer guys that they are linking directly against libvdpau_nvidia.so" 1) What was their reaction? What did the mplayer people say? Did they say "sorry, wontfix" or did they really considering it? 2) You are writing about possible screen corruption. Is this only a possible scenario or has it really been observed? That mplayer leads to screen corruption because it links to libvdpai_nvidia.so? I do not see any threads on an issue like that in nvnews forum. 3) And what is about ffmpeg? does it work with this driver in the main three? Can someone test this?
I'm using the same version of mythtv as Manuel stated: mythtv-0.22_p22860.
I've run ldd on all executables in /usr/bin, as well as all shared libraries in /usr/lib64 and grepped for vdpau - in all cases I only found libvdpau.so.1 being requested. In no case did I find libvdpau_nvidia.so. However, unless I either symlink libvdpau_nvidia.so to /usr/lib64 or I add /usr/lib64/vdpau to ld.so.conf (through LDPATH in /etc/env.d/*) MythTV fails with "Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory." I think there may be a bug in how libvdpau-0.3 is looking for the library and it can't find it unless it's in the ld.so.conf library path.
Wouldn't simply installing a 99nvidia file in /etc/env.d/ with LDPATH="/usr/lib/vdpau" be a 'cleaner' fix? Works fine here.
(In reply to comment #23) > Wouldn't simply installing a 99nvidia file in /etc/env.d/ with > LDPATH="/usr/lib/vdpau" be a 'cleaner' fix? Works fine here. That's what I'm doing now and it seems to work fine (except my file is named 99libvdpau). The ebuild should add a file like that or should determine why it's not working without said file.
Doug Goldstein wrote: Vdpau+Mplayer+Compiz=screen-corruption... And that is nonsense. Here is the official statement by nvidia, or the developers of this nvidia driver: http://www.nvnews.net/vbulletin/showthread.php?p=2156911#post2156911 Correct, applications should not be linking directly against libvdpau_nvidia. However, doing so shouldn't be able to cause any corruption problems, it should be harmless.
And further: As for finding the correct library, there have been problems in the past on some distributions where a stale copy of libvdpau 0.2 is left lying around and getting picked up by applications, which doesn't look in /usr/lib/vdpau for libvdpau_nvidia. Are you sure the correct version of libvdpau is being used by your applications? If so, please try running mplayer or mythtv with "strace -eopen" to see where it's looking. Even if the old version were being used, it should look at /usr/lib/libvdpau_nvidia.so which the .run installer creates as a symlink to /usr/lib/vdpau/libvdpau_nvidia.so.<version>.
There's a bug in libvdpau, but I haven't been able to work with nvidia to fix the issue. However this issue is fixed in Gentoo for a few releases.
