Today nvidia released a new beta driver, introducing the VDPAU API for video acceleration on newer nvidia chipsets. For this the ebuild has to be adapted a bit, bad example follows: if [[ -f usr/include/vdpau/vdpau.h ]]; then dodir /usr/include/vdpau insinto /usr/include/vdpau doins usr/include/vdpau/*.h if [[ -f usr/${pkglibdir}/libvdpau_nvidia.so.${PV} ]]; then dolib.so usr/${pkglibdir}/libvdpau_nvidia.so.${PV} dosym libvdpau_nvidia.so.${PV} /usr/${inslibdir}/libvdpau_nvidia.so.1 dosym libvdpau_nvidia.so.1 /usr/${inslibdir}/libvdpau_nvidia.so fi and same thing for libvdpau.so and libvdpau_trace.so. Otherwhise the older (177) ebuilds work so far. Probably having a USE-Flag for vdpau would be the good way, and maybe a warning that it is a) beta b) able to crash your system c) only available on some chipsets (point to http://www.nvnews.net/vbulletin/showthread.php?t=123091) As I have no big experience in writing ebuilds, I better don't even try. You know what you have to change, a workaround as the one above is working fine here so far. Looking forward to see this driver in official portage tree. Reproducible: Always Steps to Reproduce: 1. look at nvidia drivers available in portage 2. see that today released driver is not available yet 3. sit down and cry because you don't have vdpau Actual Results: beta driver not available yet Expected Results: beta driver with vdpau available (useflag)
(just before somebody mentions it: yes, there is a fi missing, as it goes on a bit but I cut it off. Thanks.)
Reassigning...
Works just fine here with git-sources-2.6.28_rc4-git5 and xorg-server-1.5.2 - I used the old 177.80 ebuild without modifications.
one more thing about these drivers... they give MASSIVE improvements comparing to latest stable in portage, and by MASSIVE I mean MASSIVE. It's the _first_ nvidia driver I can use without bitching about performance (at least on Geforce 8600M GT). KDE4 4.1.73 works over twice as fast comparing to 177.80 Worth adding to the tree - even keyworded/hardmasked for testing (as it's a BETA driver).
(In reply to comment #4) > one more thing about these drivers... > > they give MASSIVE improvements comparing to latest stable in portage, and by > MASSIVE I mean MASSIVE. > > It's the _first_ nvidia driver I can use without bitching about performance (at > least on Geforce 8600M GT). KDE4 4.1.73 works over twice as fast comparing to > 177.80 > > Worth adding to the tree - even keyworded/hardmasked for testing (as it's a > BETA driver). Hooray! Can't wait to try them out :)
Can confirm that this works for me just renaming the 177.80 ebuild.
@ Ian and Andreas: Keep in mind that by renaming the old ebuild not all libraries will be installed, as an example the new video acceleration support (which is experimental) won't be available. @ Robert Most of these improvements are available in stable drivers, which are in portage, as well. Just read http://www.nvnews.net/vbulletin/showthread.php?t=118088 The main difference of this new beta driver is the fact that these "fixes" are enabled by default. Kind regards Fuchs
I'll wait for the portage inclusion for the big fixes, but I needed this to build against the 2.6.28 kernel, which it does. That is all that I needed for the time being.
All you need for vdpau: if [[ -f usr/include/vdpau/vdpau.h ]]; then dodir /usr/include/vdpau insinto /usr/include/vdpau doins usr/include/vdpau/*.h if [[ -f usr/${pkglibdir}/libvdpau_nvidia.so.${PV} ]]; then dolib.so usr/${pkglibdir}/libvdpau_nvidia.so.${PV} dosym libvdpau_nvidia.so.${PV} /usr/${inslibdir}/libvdpau_nvidia.so.1 dosym libvdpau_nvidia.so.1 /usr/${inslibdir}/libvdpau_nvidia.so fi if [[ -f usr/${pkglibdir}/libvdpau.so.${PV} ]]; then dolib.so usr/${pkglibdir}/libvdpau.so.${PV} dosym libvdpau.so.${PV} /usr/${inslibdir}/libvdpau.so.1 dosym libvdpau.so.1 /usr/${inslibdir}/libvdpau.so fi if [[ -f usr/${pkglibdir}/libvdpau.so.${PV} ]]; then dolib.so usr/${pkglibdir}/libvdpau_trace.so.${PV} dosym libvdpau_trace.so.${PV} /usr/${inslibdir}/libvdpau_trace.so.1 dosym libvdpau_trace.so.1 /usr/${inslibdir}/libvdpau_trace.so fi fi (Yes it's a quickish cut'n'paste but it works =))
Yes, I have the almost the same lines in my tweaked ebuild (available in my overlay), although I prefer a for loop ;) #vdpau if [[ -f usr/include/vdpau/vdpau.h ]]; then dodir /usr/include/vdpau insinto /usr/include/vdpau doins usr/include/vdpau/*.h for vdpau_lib in libvdpau_nvidia.so libvdpau.so libvdpau_trace.so; do if [[ -f usr/${pkglibdir}/${vdpau_lib}.${PV} ]]; then dolib.so usr/${pkglibdir}/${vdpau_lib}.${PV} dosym ${vdpau_lib}.${PV} /usr/${inslibdir}/${vdpau_lib}.1 dosym ${vdpau_lib}.1 /usr/${inslibdir}/${vdpau_lib} fi done fi Works fine with mplayer-vdpau (sorry, no ebuild for that one yet, I just installed it manually)
How are you guys renaming this? I've tried nvidia-drivers-180.06.ebuild and nvidia-drivers-180.08.ebuild but portage can't find the download.
I just named it nvidia-drivers-180.06.ebuild and it worked.
Can anyone tell me what I did wrong? All I did was rename 177.80. I'm on amd64. # ebuild nvidia-drivers-180.08.ebuild manifest >>> Downloading 'http://distfiles.gentoo.org/distfiles/NVIDIA-FreeBSD-x86-180.08.tar.gz' --2008-11-20 18:29:26-- http://distfiles.gentoo.org/distfiles/NVIDIA-FreeBSD-x86-180.08.tar.gz Resolving distfiles.gentoo.org... 64.50.236.52, 64.50.238.52, 140.211.166.134, ... Connecting to distfiles.gentoo.org|64.50.236.52|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2008-11-20 18:29:27 ERROR 404: Not Found. >>> Downloading 'http://distro.ibiblio.org/pub/linux/distributions/gentoo/distfiles/NVIDIA-FreeBSD-x86-180.08.tar.gz' --2008-11-20 18:29:27-- http://distro.ibiblio.org/pub/linux/distributions/gentoo/distfiles/NVIDIA-FreeBSD-x86-180.08.tar.gz Resolving distro.ibiblio.org... 152.46.7.109 Connecting to distro.ibiblio.org|152.46.7.109|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2008-11-20 18:29:31 ERROR 404: Not Found. >>> Downloading 'http://us.download.nvidia.com/freebsd/180.08/NVIDIA-FreeBSD-x86-180.08.tar.gz' --2008-11-20 18:29:31-- http://us.download.nvidia.com/freebsd/180.08/NVIDIA-FreeBSD-x86-180.08.tar.gz Resolving us.download.nvidia.com... 96.7.41.8, 96.7.41.9 Connecting to us.download.nvidia.com|96.7.41.8|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2008-11-20 18:29:32 ERROR 404: Not Found. !!! Couldn't download 'NVIDIA-FreeBSD-x86-180.08.tar.gz'. Aborting. !!! File NVIDIA-FreeBSD-x86-180.08.tar.gz doesn't exist, can't update Manifest
Just to cover the bases, you did the manifest and digest ebuild options?
(In reply to comment #13) > Can anyone tell me what I did wrong? All I did was rename 177.80. I'm on > amd64. > [...] > >>> Downloading 'http://us.download.nvidia.com/freebsd/180.08/NVIDIA-FreeBSD-x86-180.08.tar.gz' > --2008-11-20 18:29:31-- > http://us.download.nvidia.com/freebsd/180.08/NVIDIA-FreeBSD-x86-180.08.tar.gz > Resolving us.download.nvidia.com... 96.7.41.8, 96.7.41.9 > Connecting to us.download.nvidia.com|96.7.41.8|:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 2008-11-20 18:29:32 ERROR 404: Not Found. > > !!! Couldn't download 'NVIDIA-FreeBSD-x86-180.08.tar.gz'. Aborting. > !!! File NVIDIA-FreeBSD-x86-180.08.tar.gz doesn't exist, can't update Manifest > change http://us.download.nvidia.com to ftp://download.nvidia.com
(In reply to comment #13) FreeBSD?
I just tried copying again from 177.80 and renaming with the same result. I hardcoded the correct path for amd64, but it wants to download the x86-fbsd version. I've never had a problem like this before. I'm trying both of these: # ebuild nvidia-drivers-180.08.ebuild manifest # ebuild nvidia-drivers-180.08.ebuild digest All you guys did was rename 177.80 and it worked? The path isn't even right.
Well, I used 180.06, but that is all that I did.
is there still anyone working on this? #10 adds support for vdpau, so why not update the ebuild on portage and add support for the new beta drivers (180.16 by now)?
I'm all for adding these drivers to portage, they make for a huge improvement in KDE 4 performance, let alone VDPAU. I'm using them using the ebuild in the Berkano overlay. Note though, some people have been having problems with these drivers and Songbird. See http://getsatisfaction.com/songbird/topics/glibc_2_8_detects_invalid_free_pointer?utm_content=topic_link&utm_medium=email&utm_source=reply_notification I also had problems with other XULRunner based apps like Firefox 3.1B2. Disabling Glitz support for Cairo seems to work.
Version 180.22 is now out of beta and is stable according to nvidia. http://www.nvidia.com/object/linux_display_amd64_180.22.html
180.22 are available in the tree. Please use those.
