Nvidia GPU Tool Issue with Fan setting

Bradford1040 · 2015-04-28 15:55:23

Linux archlinux 4.0.0-2-ARCH #1 SMP PREEMPT Tue Apr 14 07:14:46 CEST 2015 x86_64 GNU/Linux

GTX680 Classified on an X58 asus board and a Xeon X5660

Nvidia 349.16-2 & NV-Control version 1.29 installed and was working fine, well is working fine other than I can't manually set the fan speed anymore, I used to be able to hit apply on "Enable GPU Fan Settings" but now it is a little weird!

I open nvidia tool menu, got to "Thermal Settings" the fan speed and slider is there for a split second and then it disappears, no slider nothing but the apply check box but no way to set the speed? I played around with Xorg settings and coolbits settings with no luck. Removed & Reinstalled Nvidia Driver! I just don't get it and normally I can figure things like this out but brain not working today it seems, please help if you can

Last edited by Bradford1040 (2015-04-28 15:56:27)

Bradford1040 · 2015-04-28 18:50:24

I starting to think I didn't screw something up, well yeah I did lol, I am thinking I upgraded to quickly, just went to play "Metro last light" and the frames where real choppy, so I am thinking I need to downgrade my driver, but

I did do that a bit ago and the gpu fan settings were still doing this! Anyone got an Idea??? Some reason? anything at all? I was running perfect about a week ago with Metro so wondering if there is some way to get my system back to that point? What do I need to do wipe out Nvidia Fully? Reinstall it that way? Or just wait a few days and see if they fix the driver issue?

I know a lot of questions sorry, I just was going to play today. Kinda jonesing now

smirky · 2015-04-29 04:57:54

Provide some info.

$ pacman -Q | grep nvidia

Some logs would be good too.

Bradford1040 · 2015-04-29 12:38:18

smirky wrote:

Provide some info.
$ pacman -Q | grep nvidia
Some logs would be good too.

lib32-nvidia-cg-toolkit 3.1-4
lib32-nvidia-libgl 349.16-1
lib32-nvidia-utils 349.16-1
lib32-opencl-nvidia 349.16-1
nvidia 349.16-2
nvidia-cg-toolkit 3.1-3
nvidia-libgl 349.16-1
nvidia-utils 349.16-1
opencl-nvidia 349.16-1

Buddlespit · 2015-04-29 12:48:27

Also, do you have coolbits enabled? What setting, if so?

Bradford1040 · 2015-04-29 12:55:15

Buddlespit wrote:

Also, do you have coolbits enabled? What setting, if so?

I had coolbit at 4 but now 28, tried a few different ones. Like I said it is weird, I open the tool see the slider for a split second and it disappears, if I close the tool and open it again same thing, not restart of the OS needed to repeat this.

https://www.dropbox.com/sc/b7018n4pzlon … iqms--jZXa

Last edited by Bradford1040 (2015-04-29 13:08:52)

Bradford1040 · 2015-04-29 13:05:39

bump, that is what I end up seeing after it disappears, no slider so no adjustment, had to edit again, wrong link at first

Last edited by Bradford1040 (2015-04-29 13:09:36)

Buddlespit · 2015-04-29 13:13:53

Ok, I just set my Coolbits to 28 (wasn't set on my system, really don't need it here) and I'm able to adjust my fan speeds and my gpu/mem speeds. At this point, I don't know how to help you, other than drop to console, remove nvidia and the config files in /etc/X11/*, rebuild the kernel (mkinitcpio), reboot and reinstall nvidia and finally rebuild and edit the config file (nvidia-xconfig).

Bradford1040 · 2015-04-29 13:24:52

Buddlespit wrote:

Ok, I just set my Coolbits to 28 (wasn't set on my system, really don't need it here) and I'm able to adjust my fan speeds and my gpu/mem speeds. At this point, I don't know how to help you, other than drop to console, remove nvidia and the config files in /etc/X11/*, rebuild the kernel (mkinitcpio), reboot and reinstall nvidia and finally rebuild and edit the config file (nvidia-xconfig).

Well not the answer I wanted, you make up another one? lol, I will sit on this a few more days before I do that. I have been running 100% perfect up till this for over a year on the same OS. Just been upgrading, first time I have really enjoyed Linux, and in the beginning Nvidia is always the hardest part it seems. So if anyone comes up with a better fix please let me know

xylef · 2015-04-29 15:14:03

It seems to be a bug in the latest nvidia drivers.
I reported it to nvidia a month ago: https://devtalk.nvidia.com/default/topi … er-349-12/
From the reports on nvidia forum, i think it affects pre maxwell hardware.

Bradford1040 · 2015-04-29 17:45:41

xylef wrote:

It seems to be a bug in the latest nvidia drivers.
I reported it to nvidia a month ago: https://devtalk.nvidia.com/default/topi … er-349-12/
From the reports on nvidia forum, i think it affects pre maxwell hardware.

Yeah, I have been diving into it even further, seen your post. Sucks for me as no workarounds yet, I have messed with Xauthority and Xorg and every other darn thing. I even seen if the install package was some how different. Mine was working even a few days ago with 349.16-1 and seemed to mess up on -2 update

Bradford1040 · 2015-04-29 21:24:28

Well it is more than the fan setting! I just said the heck with the temps, I mean I have a classified so it stays cool anyway, I just don't like the fan going up and down noise.

So I clicked play and wow it is running like crap! I was getting 60+ fps in game with slowdowns getting only 22~25 fps before, I mean only a week ago. NOW I am getting 8~12 fps max in game! Talk about a bad driver! Sucks, How do I roll the driver back again? I mean without going through hell, wipe out the current driver and install an older one?? Been a long long time now for me doing it, any hints? Don't say google lol

Bradford1040 · 2015-04-29 21:26:38

pacman -Rdd nvidia-utils nvidia-lts nvidia-libgl nvidia

You think that will wipe them out good enough, and then specify the version on install?

Buddlespit · 2015-04-29 21:30:32

It'll have to match the kernel version too. Might have to download a pkgbuild of the nvidia version and edit it to match the current/running kernel.

Bradford1040 · 2015-04-29 21:37:41

Buddlespit wrote:

It'll have to match the kernel version too. Might have to download a pkgbuild of the nvidia version and edit it to match the current/running kernel.

poop! I forgot that, well waiting for a fix is sounding better lol, man I am really lazy lately! This OS install has been trouble free for a year! I really am almost tempted to dual boot into windows! (ewww!!!) I know

Buddlespit · 2015-04-29 21:44:50

I understand. I'm running KDE Plasma5, with testing, community testing and kde_unstable repos enabled. Along with repo_ck for linux-ck kernel, which is broken. I usually save everything that breaks for the weekend, unless the system doesn't boot. Then I'll load Kubuntu LiveUSB just to check my email or GoogleNews. I'm just too burnt out from my day to deal with a broken system. I can't wait for Plasma5 to stabilize, make my life easier...

Bradford1040 · 2015-04-29 21:58:14

Buddlespit wrote:

I understand. I'm running KDE Plasma5, with testing, community testing and kde_unstable repos enabled. Along with repo_ck for linux-ck kernel, which is broken. I usually save everything that breaks for the weekend, unless the system doesn't boot. Then I'll load Kubuntu LiveUSB just to check my email or GoogleNews. I'm just too burnt out from my day to deal with a broken system. I can't wait for Plasma5 to stabilize, make my life easier...

Tell you the truth I don't even know which KDE I am running lol, wow talk about lazy times 10! LMAO, I am pulling it up now.

Qt: 4.8.6
KDE Development Platform: 4.14.7
kde4-config: 1.0

I guess I am running that to lol, I have Black-arch & Arch-assault repos on top of DEV and Testing. But really I have not had one day my system was not running right till now! Thanks Nvidia!!! I was reading through a few .conf type files man you know the is a file in the repo call unfu**ed nvidia lmao

xylef · 2015-04-29 22:58:09

Bradford1040 wrote:

So I clicked play and wow it is running like crap! I was getting 60+ fps in game with slowdowns getting only 22~25 fps before, I mean only a week ago. NOW I am getting 8~12 fps max in game!l

Maybe you have the fan control thingy checkbox enabled in nvidia-settings? That would make the fan stay at its lower level and the card will gain heat pretty fast making it throttle the speed down to avoid overheat...

Bradford1040 · 2015-04-29 23:36:15

xylef wrote:

Bradford1040 wrote:
So I clicked play and wow it is running like crap! I was getting 60+ fps in game with slowdowns getting only 22~25 fps before, I mean only a week ago. NOW I am getting 8~12 fps max in game!l
Maybe you have the fan control thingy checkbox enabled in nvidia-settings? That would make the fan stay at its lower level and the card will gain heat pretty fast making it throttle the speed down to avoid overheat...

NO, but I am sure someone has done that in time, lol The PCI-E lane is even showing running on only 1 lane instead of 16, there is a major issue with the new driver, reading up on the build of it now. I have mentioned I have not had issues for one year so a bit out of touch remembering a few things but trust me this is not operator error here lol

Bradford1040 · 2015-04-29 23:54:35

One thing I keep thinking it might be, seeing as we get the (Read Only) via the command line. I wonder if they brought back the agreement line in the code, remember it used to have to agree to TOS before it would allow the Fan adjustment! Doesn't fully explain my issue, but might help with yours. I have been looking for the right file to change the attributes. No luck on that yet but will post soon as I find anything

This is the command
# nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a "[fan-0]/GPUCurrentFanSpeed=55"

Attribute 'GPUFanControlState' (archlinux:0[gpu:0]) assigned value 1.

ERROR: The attribute 'GPUCurrentFanSpeed' specified in assignment '[fan-0]/GPUCurrentFanSpeed=55' cannot be assigned (it is a read-only attribute).

# nvidia-smi -q | grep Fan
Fan Speed : 20 %

4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux

# pacman -Q | grep nvidia
lib32-nvidia-cg-toolkit 3.1-4
lib32-nvidia-libgl 349.16-1
lib32-nvidia-utils 349.16-1
lib32-opencl-nvidia 349.16-1
nvidia 349.16-2
nvidia-cg-toolkit 3.1-3
nvidia-libgl 349.16-1
nvidia-lts 349.16-1
nvidia-utils 349.16-1
opencl-nvidia 349.16-1

Last edited by Bradford1040 (2015-04-29 23:59:43)

xylef · 2015-04-30 09:09:05

Well, i guess the best thing you can do for now is revert to 346 and wait for the next driver release. Hopefully they'll fix it...

dubigrasu · 2015-05-10 16:21:57

Bradford1040 wrote:

One thing I keep thinking it might be, seeing as we get the (Read Only) via the command line. I wonder if they brought back the agreement line in the code, remember it used to have to agree to TOS before it would allow the Fan adjustment! Doesn't fully explain my issue, but might help with yours. I have been looking for the right file to change the attributes. No luck on that yet but will post soon as I find anything
This is the command
# nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a "[fan-0]/GPUCurrentFanSpeed=55"
Attribute 'GPUFanControlState' (archlinux:0[gpu:0]) assigned value 1.

ERROR: The attribute 'GPUCurrentFanSpeed' specified in assignment '[fan-0]/GPUCurrentFanSpeed=55' cannot be assigned (it is a read-only attribute).

From the Nvidia changelog:
"Added nvidia-settings commandline support to query the current and targeted GPU fan speed."

From what I see "GPUCurrentFanSpeed" was previously used to both set and get the fan speed.
Now is only for viewing the fan speed (read only) while for setting the speed "GPUTargetFanSpeed" is used.

So:
# nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a "[fan-0]/GPUTargetFanSpeed=55"
would be the correct command.

More info with: nvidia-settings -q all | grep Fan

xylef · 2015-05-10 16:39:05

dubigrasu wrote:

Bradford1040 wrote:
One thing I keep thinking it might be, seeing as we get the (Read Only) via the command line. I wonder if they brought back the agreement line in the code, remember it used to have to agree to TOS before it would allow the Fan adjustment! Doesn't fully explain my issue, but might help with yours. I have been looking for the right file to change the attributes. No luck on that yet but will post soon as I find anything
This is the command
# nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a "[fan-0]/GPUCurrentFanSpeed=55"
Attribute 'GPUFanControlState' (archlinux:0[gpu:0]) assigned value 1.

ERROR: The attribute 'GPUCurrentFanSpeed' specified in assignment '[fan-0]/GPUCurrentFanSpeed=55' cannot be assigned (it is a read-only attribute).
From the Nvidia changelog:
"Added nvidia-settings commandline support to query the current and targeted GPU fan speed."
From what I see "GPUCurrentFanSpeed" was previously used to both set and get the fan speed.
Now is only for viewing the fan speed (read only) while for setting the speed "GPUTargetFanSpeed" is used.
So:
# nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a "[fan-0]/GPUTargetFanSpeed=55"
would be the correct command.
More info with: nvidia-settings -q all | grep Fan

That attribute does not appear for me.
nvidia-settings -q all | grep Fan
Attribute 'GPUFanControlState' (gothmog:1[gpu:0]): 0.
'GPUFanControlState' is a boolean attribute; valid values are: 1 (on/true) and 0 (off/false).
'GPUFanControlState' can use the following target types: GPU.
Attribute 'GPUCurrentFanSpeedRPM' (gothmog:1[fan:0]): 990.
'GPUCurrentFanSpeedRPM' is an integer attribute.
'GPUCurrentFanSpeedRPM' is a read-only attribute.
'GPUCurrentFanSpeedRPM' can use the following target types: Fan.
Attribute 'GPUFanControlType' (gothmog:1[fan:0]): 2.
'GPUFanControlType' is an integer attribute.
'GPUFanControlType' is a read-only attribute.
'GPUFanControlType' can use the following target types: Fan.
Attribute 'GPUFanTarget' (gothmog:1[fan:0]): 0x00000007.
'GPUFanTarget' is a bitmask attribute.
'GPUFanTarget' is a read-only attribute.
'GPUFanTarget' can use the following target types: Fan.

dubigrasu · 2015-05-10 17:04:56

It depends on the driver version used, in this case 349.16:

steam@steamos:~/Desktop$ nvidia-settings -q all | grep Fan
  Attribute 'GPUFanControlState' (steamos:0[gpu:0]): 1.
    'GPUFanControlState' is a boolean attribute; valid values are: 1 (on/true) and 0 (off/false).
    'GPUFanControlState' can use the following target types: GPU.
  Attribute 'GPUTargetFanSpeed' (steamos:0[fan:0]): 35.
    The valid values for 'GPUTargetFanSpeed' are in the range 0 - 100 (inclusive).
    'GPUTargetFanSpeed' can use the following target types: Fan.
  Attribute 'GPUCurrentFanSpeed' (steamos:0[fan:0]): 35.
    The valid values for 'GPUCurrentFanSpeed' are in the range 0 - 100 (inclusive).
    'GPUCurrentFanSpeed' is a read-only attribute.
    'GPUCurrentFanSpeed' can use the following target types: Fan.
  Attribute 'GPUCurrentFanSpeedRPM' (steamos:0[fan:0]): 1472.
    'GPUCurrentFanSpeedRPM' is an integer attribute.
    'GPUCurrentFanSpeedRPM' is a read-only attribute.
    'GPUCurrentFanSpeedRPM' can use the following target types: Fan.
  Attribute 'GPUFanControlType' (steamos:0[fan:0]): 2.
    'GPUFanControlType' is an integer attribute.
    'GPUFanControlType' is a read-only attribute.
    'GPUFanControlType' can use the following target types: Fan.
  Attribute 'GPUFanTarget' (steamos:0[fan:0]): 0x00000007.
    'GPUFanTarget' is a bitmask attribute.
    'GPUFanTarget' is a read-only attribute.
    'GPUFanTarget' can use the following target types: Fan.
steam@steamos:~/Desktop$

xylef · 2015-05-10 17:12:07

dubigrasu wrote:

It depends on the driver version used, in this case 349.16:

Yeah, yeah, i know, I'm on 349.16. But the thing is that it doesn't work for everybody. So far from the reports on the nvidia forum it seems to be working only for people with maxwell hardware.

Arch Linux

#1 2015-04-28 15:55:23

Nvidia GPU Tool Issue with Fan setting

#2 2015-04-28 18:50:24

Re: Nvidia GPU Tool Issue with Fan setting

#3 2015-04-29 04:57:54

Re: Nvidia GPU Tool Issue with Fan setting

#4 2015-04-29 12:38:18

Re: Nvidia GPU Tool Issue with Fan setting

#5 2015-04-29 12:48:27

Re: Nvidia GPU Tool Issue with Fan setting

#6 2015-04-29 12:55:15

Re: Nvidia GPU Tool Issue with Fan setting

#7 2015-04-29 13:05:39

Re: Nvidia GPU Tool Issue with Fan setting

#8 2015-04-29 13:13:53

Re: Nvidia GPU Tool Issue with Fan setting

#9 2015-04-29 13:24:52

Re: Nvidia GPU Tool Issue with Fan setting

#10 2015-04-29 15:14:03

Re: Nvidia GPU Tool Issue with Fan setting

#11 2015-04-29 17:45:41

Re: Nvidia GPU Tool Issue with Fan setting

#12 2015-04-29 21:24:28

Re: Nvidia GPU Tool Issue with Fan setting

#13 2015-04-29 21:26:38

Re: Nvidia GPU Tool Issue with Fan setting

#14 2015-04-29 21:30:32

Re: Nvidia GPU Tool Issue with Fan setting

#15 2015-04-29 21:37:41

Re: Nvidia GPU Tool Issue with Fan setting

#16 2015-04-29 21:44:50

Re: Nvidia GPU Tool Issue with Fan setting

#17 2015-04-29 21:58:14

Re: Nvidia GPU Tool Issue with Fan setting

#18 2015-04-29 22:58:09

Re: Nvidia GPU Tool Issue with Fan setting

#19 2015-04-29 23:36:15

Re: Nvidia GPU Tool Issue with Fan setting

#20 2015-04-29 23:54:35

Re: Nvidia GPU Tool Issue with Fan setting

#21 2015-04-30 09:09:05

Re: Nvidia GPU Tool Issue with Fan setting

#22 2015-05-10 16:21:57

Re: Nvidia GPU Tool Issue with Fan setting

#23 2015-05-10 16:39:05

Re: Nvidia GPU Tool Issue with Fan setting

#24 2015-05-10 17:04:56

Re: Nvidia GPU Tool Issue with Fan setting

#25 2015-05-10 17:12:07

Re: Nvidia GPU Tool Issue with Fan setting

Board footer