Using the nvidia-drivers-1.0.7185 pulls in the latest version of nvidia-settings, which requires a newer version of the NV-CONTROL X Extension than is in this driver. Reproducible: Always Steps to Reproduce: 1. emerge nvidia-drivers (>=nvidia-drivers-1.0.7200 masked as per instructions, gtk USE flag set) 2. nvidia-settings 3. Actual Results: nvidia-settings runs, but has no device controls. The following is output at console: ERROR: NV-CONTROL extension version 1.6 is too old; the minimimum required version is 1.11. ERROR: Unable to determine number of NVIDIA GPUs on ':0.0'. ERROR: Unable to determine number of NVIDIA Frame Lock Devices on ':0.0'. ERROR: Unable to determine number of NVIDIA VCSCs on ':0.0'. Expected Results: nvidia-settings has correct device controls, and no error output.
see http://forums.gentoo.org/viewtopic-t-574426.html
So which version(s) work(s) for you? We really have better things to do that solving this nVidia incompatibility crap.
The version of nvidia-settings that driver 1.0.7185 requires is the one that is contained in that very driver package from nvidia. The packages should be merged back into one ebuild, especially since the nvidia-drivers ebuild now directly depends on the nvidia-settings package, and the version dependency is resolved already when nvidia made the package. Simply use the 'gtk' useflag, already used by the ebuild, to choose whether or not to install the included nvidia-settings. If the nvidia package were not intentionally split by the ebuilds into nvidia-settings and nvidia-drivers, this need to keep track of dependencies would not arise.
Created attachment 127328 [details, diff] A patch to the ebuild to install the packaged nvidia-settings This is how I'd fix it. I can't verify it's correct: it's the first time I've patched an ebuild.
Multiple places ( ftp://download.nvidia.com/XFree86/Linux-x86/100.14.19/README/chapter-24.html ftp://download.nvidia.com/XFree86/Linux-x86/nvidia-settings-user-guide.txt ) refer to ftp://download.nvidia.com/XFree86/nvidia-settings/ as the location for nvidia-settings source. nvidia-settings-1.0.20070621 in portage is actually (ie. identical to) nvidia-settings-1.0-100.14.11 from the above url. Perhaps nvidia-settings ebuilds should use the version number indicated by nvidia (ie. source tarball) while nvidia-drivers ebuilds rely on the matching nvidia-settings-${PV}.
As discussed in this (http://www.nvnews.net/vbulletin/showthread.php?t=96562) thread at nvnews forums, the nvidia chaps kindly packaged up the nvidia-settings code that was used for each driver release, by release version. See: http://people.freedesktop.org/~aplattner/nvidia-settings/ So nvidia-drivers can now pull down the relevant nvidia-settings package.
well, 1.0.7185 is gone from the tree. Additionally, NVIDIA claims the same tarball should work for all.
