NVIDIA / NVIDIA/nvidia-settings
NVML 11.8 API bugs
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 345
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
The new 11.8 functions to change VF offset for GPU/Memory clock are bugged in 520 in different ways.
On my GTX 1080 the graphics clock function returns "Not Found":
and the min value returned by nvmlDeviceGetMemClkMinMaxVfOffset isn't correct. It should be -2000 for my card but instead, it returns 8587934. It works correctly otherwise although I wish it was like Windows.
ping @aaronp24
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the NVML 11.8 functions named in the report: the graphics clock VF-offset function and nvmlDeviceGetMemClkMinMaxVfOffset. Reproduce both results on a GTX 1080 using the linked screenshot and reported values, then trace the corresponding NVIDIA driver/API behavior. Done means identifying and correcting both incorrect results, with a regression check for the expected -2000 minimum.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100