This is a two-part request: 1) NVIDIA-drivers 177.78 are out at the following URLs -- please add them to Portage at your earliest convenience: ftp://download.nvidia.com/XFree86/Linux-x86_64/177.78/NVIDIA-Linux-x86_64-177.78-pkg2.run ftp://download.nvidia.com/XFree86/Linux-x86/177.78/NVIDIA-Linux-x86-177.78-pkg1.run Here's the changelog: http://www.nvnews.net/vbulletin/showthread.php?t=120052 2) Once upon a time, I discovered that all NVIDIA-drivers >173.08 wouldn't work for my ~amd64 system. Upstream solved my problem: I needed to run "sh NVIDIA-Linux-x86-177.78-pkg2.run --force-tls=new" to get it to work. Is there a way to modify the nvidia-drivers ebuild to allow passing this flag? Perhaps a USE flag? Here's the upstream thread: http://www.nvnews.net/vbulletin/showthread.php?p=1790995 Let me know if I can assist you further. Reproducible: Didn't try Actual Results: Need to install NVIDIA driver from outside Portage with --force-tls=new Expected Results: Want to emerge nvidia-drivers and have the flag passed automagically emerge --info is irrelevant here.
While I wouldn't mind seeing the latest beta in the tree, I have had no problems merging or installing all the versions from 173.14.05 to 177.70.0 on my ~amd64 system. The "Improved compatibility with recent Linux 2.6 kernels" alone probably makes it worth adding.
I doubt many, if any, had my bug. I don't even seem to have it anymore, after using the nptl USE flag and emerging mesa and xorg-x11-7.4. So, I withdraw my request for that there --force-tls=new flag. My system seems to have got the message.
Ebuild shall be in tree shortly, just bear with me, I'm in the process of moving.
*** Bug 239453 has been marked as a duplicate of this bug. ***
Created attachment 167107 [details] ebuild for nvidia-drivers-177.78
Created attachment 167108 [details] nvidia-settings ebuild
Using the attached ebuilds, this installs and runs fine on my system (GTX 280). I don't see any differences in performance or any glitches since 177.70.0. Portage 2.2_rc11 (default/linux/amd64/2008.0/desktop, gcc-4.3.1, glibc-2.8_p20080602-r0, 2.6.26-gentoo-r1 x86_64) ================================================================= System uname: Linux-2.6.26-gentoo-r1-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q9650_@_3.00GHz-with-glibc2.2.5 Timestamp of tree: Sat, 04 Oct 2008 13:45:04 +0000 ccache version 2.4 [enabled] app-shells/bash: 3.2_p39 dev-java/java-config: 1.3.7, 2.1.6-r1 dev-lang/python: 2.5.2-r8 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r8 sys-apps/baselayout: 2.0.0 sys-apps/openrc: 0.2.5 sys-apps/sandbox: 1.2.18.1-r3 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 2.2.6a virtual/os-headers: 2.6.26 ACCEPT_KEYWORDS="amd64 ~amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=core2 -O2 -pipe -ggdb" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=core2 -O2 -pipe -ggdb" DISTDIR="/usr/portage/distfiles" FEATURES="ccache distlocks fixpackages parallel-fetch preserve-libs protect-owned sandbox sfperms splitdebug strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://distro.ibiblio.org/pub/linux/distributions/gentoo/" LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="en" MAKEOPTS="-j8" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/overlays/zugaina /usr/local/overlays/paludis-extras /usr/local/overlays/sunrise /usr/local/overlays/gnome /usr/local/overlays/desktop-effects /usr/local/overlays/vmware /usr/local/overlays/ikelos /usr/local/overlays/berkano /usr/local/overlays/myoverlay" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="X a52 aac acl acpi alsa amd64 amr bash-completion berkdb bluetooth branding bzip2 cairo cdda cdr cli cracklib crypt css cups dbus dri dts dvd dvdr dvdread eds emboss encode esd evo fam ffmpeg flac fortran gdbm gif glitz gnome gpm gstreamer gtk hal iconv ipv6 isdnlog java jpeg kde kdehiddenvisibility kerberos ldap libnotify mad midi mikmod mmx mono mp3 mpeg mudflap multilib ncurses nls nptl nptlonly ogg opengl openmp pam pcre pdf perl pic png ppds pppd python qt3support qt4 quicktime readline reflection ruby samba sdl session spell spl sqlite sse sse2 ssl startup-notification svg sysfs tcpd theora tiff truetype unicode usb userlocales vcd vorbis x264 xml xorg xulrunner xv xvid zlib" ALSA_CARDS="cmipci hdaintel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
there are improvements. With 177.70, my ut2004 would crash, if I had kde4 desktop rendering effects enabled. Now I can enjoy both the KDE effects and the UT2004 first person shooter
This version of nvidia-settings is missing the .desktop file: $ qlist nvidia-settings /usr/bin/nvidia-settings /usr/lib64/libXNVCtrl.a /usr/lib64/debug/usr/bin/nvidia-settings.debug /usr/include/NVCtrl/NVCtrl.h /usr/include/NVCtrl/NVCtrlLib.h /usr/share/man/man1/nvidia-settings.1 /usr/share/doc/nvidia-settings-177.78/FRAMELOCK.txt /usr/share/doc/nvidia-settings-177.78/NV-CONTROL-API.txt /usr/share/doc/nvidia-settings-177.78/nvidia-settings-user-guide.txt So no menu icon...
nVidia has released 177.80 which is stable (not a beta). I have not tried it yet but it should be the next version in the tree since it is a "stable" release.
Created attachment 167568 [details] nvidia release driver 177.80.ebuild I attached an 177.80 ebuild for the release driver, which worked for me.
*** Bug 240508 has been marked as a duplicate of this bug. ***
on a side note, nvidia-drivers ebuilds should now warn that backingstore should be set to false or not specified in xorg.conf at all now. kde4 will bail out with backingstore enabled.
The ebuild worked for me. However, removing the backingstore option did nothing for stability, kde4 worked even when I had the option (I'm using twinview, so that might have had something to do with it). Anyway, I vote this going into the tree ASAP. It's stable. (But, kde is still crashing like mad every now and again.) Cheers.
(In reply to comment #14) > The ebuild worked for me. However, removing the backingstore option did nothing > for stability, kde4 worked even when I had the option (I'm using twinview, so > that might have had something to do with it). > > Anyway, I vote this going into the tree ASAP. It's stable. (But, kde is still > crashing like mad every now and again.) > > Cheers. > I'm having a problem with the attached ebuild. Getting this: ebuild nvidia-drivers-177.80.ebuild digest Appending /usr/local to PORTDIR_OVERLAY... !!! /usr/local/portage/x11-drivers/nvidia-drivers-177.80.ebuild does not seem to have a valid PORTDIR structure.
(In reply to comment #15) > (In reply to comment #14) > > The ebuild worked for me. However, removing the backingstore option did nothing > > for stability, kde4 worked even when I had the option (I'm using twinview, so > > that might have had something to do with it). > > > > Anyway, I vote this going into the tree ASAP. It's stable. (But, kde is still > > crashing like mad every now and again.) > > > > Cheers. > > > I'm having a problem with the attached ebuild. Getting this: > > ebuild nvidia-drivers-177.80.ebuild digest > Appending /usr/local to PORTDIR_OVERLAY... > !!! /usr/local/portage/x11-drivers/nvidia-drivers-177.80.ebuild does not seem > to have a valid PORTDIR structure. > Disregard this comment please...I should have known it was something stupid I did. It's not an issue.
Is 177.80 compatible with recently released kernel 2.6.27 ?? 173.14.12 is not :-(
hello. I'm using ~amd64 here, and testing the 177.80 ebuild. It did download the files for x86, amd64, bsd, and all... is that expected ? i really do not understand why it is so. Moreover, even though I'm not sure i understand the ebuild perfectly, I would say the ebuild is supposed to download only the relevant file for the architecture. >>> Downloading 'http://us.download.nvidia.com/freebsd/177.80/NVIDIA-FreeBSD-x86-177.80.tar.gz'
Yes, I think comment 18 has a point. The ebuild should check the architecture and download only the relevant files. The ebuild which I've attached was only a slightly modified version of the beta ebuild which was already in the three (name and download path changed in the final release). Maybe someone who understands more about ebuilds can write a better one. Also, I didn't succeed to write one for nvidia-settings of the release driver....
Hey guys, think twice about the fetching of all different arch packages. When you run "ebuild ... digest" on some ebuild without Manifest file (like with any new ebuild in an overlay), portage fetches EVERY file which is contained in the SRC_URI variable to calculate the checksums for those files and to store those checksums in the Manifest file.
(answering comment #20) Yes, sorry, this was indeed my problem. actual emerging did only use the correct one, and there is not problem (so far). sorry again!
All in boys, sorry for the delay. Transcontinental moves can cause that.
Can some einfo lines be put into the ebuild, warning folks that this ebuild only works on Geforce 6xxx and above GPU's? Looks like the days of the 5 series are over.
I think better action here would be to adjust nvidia-driver.eclass properly. Seems like the 173.xx.xx series of drivers became another legacy series *sigh*...
FWIW, works for me (amd64).
This ebuild didnt work on 2.6.28-rc2-git6 so I searched this problem and I resolved. Please follow; * Download nvidia driver which architecture do you have and use with patch command sh NVIDIA-Linux-x86_64-177.80-pkg2.run --apply-patch NVIDIA_kernel-177.80-2990799.diff.txt diff file: http://www.nvnews.net/vbulletin/attachment.php?attachmentid=33772&d=1225130342
(In reply to comment #26) > This ebuild didnt work on 2.6.28-rc2-git6 so I searched this problem and I > resolved. Please follow; confirmed with epatch "${FILESDIR}"/NVIDIA_kernel-177.80-2990799.patch it compiles successfully with 2.6.28-rc4-00246-g3edac25
Trying to compile nvidia-drivers-177.80 but get error. I use gentoo-sources-2.6.27-r4. With gentoo-sources-2.6.27 compilation without errors. I browse nvidia's ftp and find version 177.82.
Created attachment 174222 [details] nvidia-drivers-177.80 for about linux kernel 2.6.27.x or above issue I added epatch section for linux kernel 2.6.27.x or above (mostly 2.6.28.x) Tested = am64 and x86 Result = Worked fine both of them. Regards, Behzat.
Created attachment 174224 [details, diff] nvidia-drivers-177.80 for about linux kernel 2.6.27.x or above issue patch This epatch for linux kernel 2.6.27.x or above (mostly 2.6.28.x) Tested = am64 and x86 Result = Worked fine both of them. Regards, Behzat.
Use nvidia-drivers-177.82 for 2.6.27 kernel support. wrt to the original question about forcetls. That support exists in the ebuild already. You would need to provide additional details about your system to see why it's failing. Seeing as this is a multi-request bug report. Please open another one for the specific issue of having your tls support not detected and used properly.
