NVIDIA / NVIDIA/nvidia-settings

nvidia-settings only allows setting GPUMemoryTransferOffset and GPUGraphicsClockOffset for [gpu:0]

Open
#75 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
345
Forks
92
PR merge metrics
No merged PRs in 30d

Description

nvidia-settings: version 470.57.01
with Option "Coolbits" "28" and Option "AllowEmptyInitialConfiguration" "True" on both X screens.

Even the GUI shows the "Editable Performance Levels" section for GPU 0 only as shown in this stackexchange question:
https://unix.stackexchange.com/questions/354958/how-to-overclock-multiple-nvidia-gpus-in-ubuntu?newreg=f0cf58cf990d4c16beed86feaed3340d

From the CLI:

# nvidia-settings -v -q [gpu:0]/GPUMemoryTransferRateOffset

ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


  Attribute 'GPUMemoryTransferRateOffset' (mpc:0[gpu:0]): 2000.
    The valid values for 'GPUMemoryTransferRateOffset' are in the range -2000 - 6000
    (inclusive).
    'GPUMemoryTransferRateOffset' can use the following target types: X Screen, GPU.

Using -a isntead of -q works and does set a value.

However, for GPU 1:

# nvidia-settings -v -q [gpu:1]/GPUMemoryTransferRateOffset

ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


WARNING: Attribute 'GPUMemoryTransferRateOffset' specified in query '[gpu:1]/GPUMemoryTransferRateOffset' is not available on mpc:0[gpu:1].

It fails to show the current value when querying, and using -a instead of -q does not work and does not set a value.

Here, assignment yields:

# nvidia-settings -V -a [gpu:1]/GPUMemoryTransferRateOffset=2000

...

WARNING: Attribute 'GPUMemoryTransferRateOffset' specified in assignment '[gpu:1]/GPUMemoryTransferRateOffset=2000' is not available on mpc:0[gpu:1].

Querying perfmodes works on both GPUs, for GPU 1 it yields:

# nvidia-settings -q [gpu:1]/GPUPerfModes

ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


ERROR: An internal driver error occurred


  Attribute 'GPUPerfModes' (mpc:0[gpu:1]): perf=0, nvclock=300, nvclockmin=300,
  nvclockmax=645, nvclockeditable=1, memclock=405, memclockmin=405, memclockmax=405,
  memclockeditable=1, memTransferRate=810, memTransferRatemin=810, memTransferRatemax=810,
  memTransferRateeditable=1 ; perf=1, nvclock=300, nvclockmin=300, nvclockmax=2100,
  nvclockeditable=1, memclock=810, memclockmin=810, memclockmax=810, memclockeditable=1,
  memTransferRate=1620, memTransferRatemin=1620, memTransferRatemax=1620,
  memTransferRateeditable=1 ; perf=2, nvclock=300, nvclockmin=300, nvclockmax=2130,
  nvclockeditable=1, memclock=5001, memclockmin=5001, memclockmax=5001,
  memclockeditable=1, memTransferRate=10002, memTransferRatemin=10002,
  memTransferRatemax=10002, memTransferRateeditable=1 ; perf=3, nvclock=300,
  nvclockmin=300, nvclockmax=2130, nvclockeditable=1, memclock=7501, memclockmin=7501,
  memclockmax=7501, memclockeditable=1, memTransferRate=15002, memTransferRatemin=15002,
  memTransferRatemax=15002, memTransferRateeditable=1 ; perf=4, nvclock=300,
  nvclockmin=300, nvclockmax=2130, nvclockeditable=1, memclock=7751, memclockmin=7751,
  memclockmax=7751, memclockeditable=1, memTransferRate=15502, memTransferRatemin=15502,
  memTransferRatemax=15502, memTransferRateeditable=1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the nvidia-settings query and assignment commands on GPU 0 and GPU 1, using the reported Coolbits and X-screen configuration. Trace the CLI handling for GPUMemoryTransferRateOffset and related attributes; done means querying and assigning the offset works consistently for GPU 1 as it does for GPU 0.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
cli, computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.