Github messages for voidlinux
 help / color / mirror / Atom feed
From: xAlpharax <xAlpharax@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] nvidia-powerd service is not working on nvidia driver versions newer than 535.154.05
Date: Sat, 27 Apr 2024 13:30:17 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50054@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]

New issue by xAlpharax on void-packages repository

https://github.com/void-linux/void-packages/issues/50054

Description:
### Is this a new report?

Yes

### System Info

Void 6.8.7_1 x86_64

### Package(s) Affected

nvidia-*

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

The NVIDIA driver ships with a service for dynamically changing the power cap the GPU has based on load (crucial for MAX Q GPUs). This service is called nvidia-powerd, and it should be up when the system boots.

### Actual behaviour

In driver versions newer than 535.154.05 (see https://github.com/void-linux/void-packages/commits/master/srcpkgs/nvidia for the versions that I am talking about) the nvidia-powerd service is down and refuses to start, or better said, it starts and immediately crashes/stops (what I believe happens)

### Steps to reproduce

1. Make sure to have a version of nvidia newer than 535.154.05
2. Enable the nvidia-powerd service (on GPUs other than MAX Q variants it won't change the power cap, so there isn't supposed to be an effect of it being up or down but you can still see in the following step whether it is working correctly or not)
3. Run `sudo sv status nvidia-powerd` and see that the service is down

             reply	other threads:[~2024-04-27 11:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-27 11:30 xAlpharax [this message]
2024-04-27 11:32 ` classabbyamp
2024-04-27 13:04 ` xAlpharax
2024-04-27 20:34 ` abenson
2024-04-27 20:36 ` abenson
2024-04-27 22:46 ` abenson
2024-04-27 22:47 ` abenson
2024-04-27 22:49 ` abenson
2024-04-28  5:50 ` xAlpharax
2024-04-28  5:54 ` xAlpharax
2024-04-28  5:58 ` xAlpharax
2024-04-28  6:17 ` xAlpharax
2024-04-28  6:30 ` xAlpharax
2024-04-28 15:27 ` abenson
2024-04-28 18:38 ` xAlpharax
2024-04-28 21:29 ` abenson
2024-04-29  9:08 ` xAlpharax

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50054@inbox.vuxu.org \
    --to=xalpharax@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).