Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#70515 - [nvidia-dkms] GPUTargetFanSpeed does not work on 465.X.X

Attached to Project: Arch Linux
Opened by Alex Frick (alex313031) - Tuesday, 20 April 2021, 03:48 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 29 April 2021, 21:57 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No


GPUTargetFanSpeed does not work. I use this is a script to tune thermal performance during WebGL sessions.

460.67 and below it works. Yes coolbits is set. LinuxLTS, Linux, and Zen are installed and it does the same thing on all kernels. Downgrading just nvidia, nvidia-dkms, and nvidia-utils solves it, but obviously I downgraded all nvidia packages.

Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
Upgrade to 465.24.02-1, -2, or -3 causes it.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Thursday, 29 April 2021, 21:57 GMT
Reason for closing:  Upstream
Additional comments about closing:  Doesn't seem like anything we can change downstream. If this used to work and now doesn't and considering I didn't change much in how we package things, please get in contact with nvidia upstream and try to get them to fix this.

Re-open if nvidia tells you that something in the package is broken though it seems unlikely to me.
Comment by alex mitchell (alexmitchellmus) - Tuesday, 20 April 2021, 12:41 GMT
I can confirm this issue with Nvidia Driver > 460.67

Nvidia-settings GUI (problematic driver) will show fan and powermizer controls when coolbits is set accordingly.

However- when the sliders/values are changed, the operation will fail with unknown error.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 21 April 2021, 05:31 GMT
I'm pretty sure this is not a packaging bug. However, I do concede that 465.24.02 did have some internal package changes from nvidia so this _might_ potentially be a packaging thing. I'd ask nvidia and post the upstream report here.
Comment by frederick_metzengerstein (metzengerstein) - Thursday, 29 April 2021, 20:22 GMT