Bug 99515 – nvidia-settings 1.0-7667 ebuild required

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Guy Ratcliffe 2005-07-19 05:19:35 UTC]

When using attributes from the commandline, nvidia-settings only works with
attributes that are part of earlier releases.  Newer attributes (such as
GPUOverclockingState) do not function.  Attributes work correctly from the GUI.

Reproducible: Always
Steps to Reproduce:
1.emerge nvidia-settings with ~x86 flag
2.nvidia-settings -a GPUOverclockingState=1
3.

Actual Results:  
nvidia-settings -a GPUOverclockingState=1

ERROR: Error parsing assignment 'GPUOverclockingState=1' (Unrecognized
attribute name).

Expected Results:  
nvidia-settings -a GPUOverclockingState=1
Attribute 'GPUOverclockingState' (machinename:0.0) assigned value 1.


I removed the Gentoo ebuilds from the machine and ran the direct build from
Nvidia.  This builds both the kernel module and the nvidia-settings utility and
works correctly.

[Comment 1 Guy Ratcliffe 2005-07-19 09:37:46 UTC]

Just tried something else, copied the binary out of the
NVIDIA-Linux-x86-1.0-7667-pkg0.run (NVIDIA-Linux-x86-1.0-7667-pkg0.run
--extract) and into /usr/bin and it works fine so definatly something wrong with
the ebuild and / or compile.

[Comment 2 Joshua Baergen (RETIRED) 2005-07-19 20:18:32 UTC]

My tree doesn't have nvidia-settings-1.0.7667 ebuild...am I just crazy?

[Comment 3 Guy Ratcliffe 2005-07-20 02:29:37 UTC]

It has changed name to nvidia-settings-1.0.20050525.ebuild, why I don't know as
these should relate to the display driver.  Also, after your comment Joshua, I
realised that this ebuild is for "1.0.7664" so should relate to the 7664 build
of the drivers BUT this functionality was available in those drivers as well.  I
have tried the 7664 driver from Nvidia and that works fine, so we still have an
issue with the build.

[Comment 4 Joshua Baergen (RETIRED) 2005-07-20 18:25:05 UTC]

So it would appear the problem is that there is no ebuild for nvidia-settings
7667. It would be appreciated if you tried modifying the 7664 ebuild to work
with 7667 and post it here.  It's probably a driver mis-match causing the problem.

[Comment 5 Xake 2006-10-15 12:56:56 UTC]

So is this still a problem?

[Comment 6 Jakub Moc (RETIRED) 2006-10-15 13:12:58 UTC]

Irrelevant bug, closing.