Search Criteria
Package Details: nvfancontrol 0.5.1-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/nvfancontrol.git (read-only, click to copy) |
---|---|
Package Base: | nvfancontrol |
Description: | NVidia dynamic fan control |
Upstream URL: | https://github.com/foucault/nvfancontrol |
Keywords: | nvidia system |
Licenses: | GPL3 |
Submitter: | Foucault |
Maintainer: | Foucault |
Last Packager: | Foucault |
Votes: | 8 |
Popularity: | 0.185188 |
First Submitted: | 2017-07-01 19:11 (UTC) |
Last Updated: | 2021-06-22 21:27 (UTC) |
Dependencies (5)
- libxext (libxext-git)
- cargo (cargo-git, rust-nightly-bin, rustup-git, rust, rustup) (make)
- libxnvctrl (libxnvctrl-beta-gtk2, libxnvctrl-430xx, libxnvctrl-340xx, libxnvctrl-470xx, libxnvctrl-510xx, libxnvctrl-390xx) (make)
- nvidia (nvidia-vulkan, nvidia-vulkan-dkms, nvidia-beta, nvidia-beta-dkms, nvidia-dkms) (optional) – For GTX 4xx or newer cards
- nvidia-340xx (nvidia-340xx-lts-dkms, nvidia-340xx-dkms) (optional) – For G8x, G9x and GTX 2xx cards
Latest Comments
Foucault commented on 2021-06-22 21:28 (UTC)
My bad, sorry! Should be fixed now.
smitropoulos commented on 2021-06-22 21:09 (UTC) (edited on 2021-06-22 21:10 (UTC) by smitropoulos)
Getting the following error on install:
project0 commented on 2021-04-25 09:18 (UTC)
The service file mentioned by @Foucault was not working for me. This is the working version (at least for me :-) )
Foucault commented on 2020-01-21 09:30 (UTC) (edited on 2020-01-21 09:31 (UTC) by Foucault)
This is the stable version of the package. New fixes are only present in git as I haven't made a new release yet- sorry!
EnSER commented on 2020-01-21 09:27 (UTC)
Sorry for the question, but I can't get "fanflicker prevention" working as described on github. Switch '-r' or '--fanflicker' gives me "UnrecognizedOption".
hottea commented on 2019-06-25 02:45 (UTC)
@Cavsfan systemd is not suitable for starting a service that needs X (nvidia-settings needs X to work properly). If you're not using headless system, you could use the DE's startup settings. For headless system, you might consider starting X, setting the
DISPLAY
environment, and then start nvfancontrol.Cavsfan commented on 2018-07-05 18:52 (UTC) (edited on 2018-07-05 18:53 (UTC) by Cavsfan)
@Foucault, no I did not but, now I have and along with a conf file it's working!
I just could not get the systemd unit to startup at boot.
I could start it, enable it but, it still did not start when I booted up.
So, I just added it to Xfce Applications > Settings > Session and Startup and it's working fantastic!Cheers and thank you! :-)
Foucault commented on 2018-07-05 01:51 (UTC)
Have you enabled Coolbits ?
Cavsfan commented on 2018-07-04 18:58 (UTC) (edited on 2018-07-04 21:55 (UTC) by Cavsfan)
I got it, just didn't save it as ~/.config/systemd/user/nvfancontrol.service
Then it started just fine but, I am getting this error:
Jul 04 17:47:11 ArchLinux nvfancontrol[32423]: INFO - NVIDIA driver version: 396.24
Jul 04 17:47:11 ArchLinux nvfancontrol[32423]: INFO - NVIDIA graphics adapter #1: GeForce GTX 980 Ti
Jul 04 17:47:11 ArchLinux nvfancontrol[32423]: ERROR - Could not update fan speed: XNVCtrl QueryAttr(COOLER_MANUAL_CONTROL) failed; error 0
Jul 04 17:47:13 ArchLinux nvfancontrol[32423]: ERROR - Could not update fan speed: XNVCtrl QueryAttr(COOLER_MANUAL_CONTROL) failed; error 0
Jul 04 17:47:15 ArchLinux nvfancontrol[32423]: ERROR - Could not update fan speed: XNVCtrl QueryAttr(COOLER_MANUAL_CONTROL) failed; error 0
I probably do not have a driver component installed?
Foucault commented on 2018-07-04 02:04 (UTC) (edited on 2018-07-04 02:05 (UTC) by Foucault)
Add it to your
~/.config/systemd/user
and check if it's working withand
If the service is running properly you can permanently enable it upon login with
More details on systemd user units here
Cavsfan commented on 2018-07-03 23:24 (UTC)
Sorry for posting here but, is there a wiki for installing this? I've installed it and have a Nvidia Geforce 980 ti and need the fans of course. I just do not how to get it to work. I copied the systemd file into /.config/systemd/user but do not know how to enable it. Thank you in advance!
Foucault commented on 2018-02-11 21:25 (UTC) (edited on 2018-07-04 02:03 (UTC) by Foucault)
You made it start upon login not upon boot. You could have similarly created a systemd user unit and place it in
/home/YOURUSERNAME/.config/systemd/user
. Then you could enable it withsystemctl --user enable nvfancontrol.service
. Here is a minimal systemd unit to do soStillrotten commented on 2018-02-07 03:32 (UTC)
No concerns here, just wanted to say thanks a ton for making a simple, easy to use, and effective program. Using this with my Gigabyte GTX 1060 and it's working absolutely flawlessly. Cheers and thanks again.
Foucault commented on 2018-02-02 01:13 (UTC)
This is more complicated than it sounds. It is impossible to use xnvctrl (the library that controls the GPU) without an X server. So at the very least the program must be run after the graphics environment has been brought up. So graphical.target should be a better candidate instead of multi-user.target. If you run nvfancontrol as root after graphical.target it might work. However once you log in your desktop the display will probably re-initialised or a new one will be set up (for example GDM does that; if you check $DISPLAY you'll see that is :1 rather than :0). In any case nvfancontrol will be killed once this happen and you will have to start it again. This is an inherent limitation of the way the NVIDIA driver works. There is a hacky way [0] to fake a GPU context however it still involves spinning up an X server so again similar limitations apply. I'm wondering if it is possible to have a different X server always running (etc. in :50) and bind nvfancontrol there but I haven't tested that yet. It might or it might not work.
[0] https://sites.google.com/site/akohlmey/random-hacks/nvidia-gpu-coolness#TOC-Faking-a-Head-for-a-Headless-X-Server
Foucault commented on 2017-12-29 19:32 (UTC)
You're right; wrong installation permissions
Nordlicht commented on 2017-12-29 19:27 (UTC)
Ok, it works now. Small bug: The executable bit isn't set, so I had to do it via 'chmod +x' after installing.
Foucault commented on 2017-12-28 12:44 (UTC)
It should work now!
Nordlicht commented on 2017-12-28 07:34 (UTC)
Build fails:
error[E0432]: unresolved import
log::LogRecord
--> src/main.rs:6:16 | 6 | use log::{Log, LogRecord, LogLevelFilter, LogMetadata, SetLoggerError}; | ^^^^^^^^^ noLogRecord
in the root. Did you mean to useRecord
?error[E0432]: unresolved import
log::LogLevelFilter
--> src/main.rs:6:27 | 6 | use log::{Log, LogRecord, LogLevelFilter, LogMetadata, SetLoggerError}; | ^^^^^^^^^^^^^^ noLogLevelFilter
in the root. Did you mean to useLevelFilter
?error[E0432]: unresolved import
log::LogMetadata
--> src/main.rs:6:43 | 6 | use log::{Log, LogRecord, LogLevelFilter, LogMetadata, SetLoggerError}; | ^^^^^^^^^^^ noLogMetadata
in the root. Did you mean to useMetadata
?error[E0423]: expected function, found macro
log::max_log_level
--> src/main.rs:58:29 | 58 | metadata.level() <= log::max_log_level() | ^^^^^------------- | | | | | did you meanmax_level
? | did you meanlog::max_log_level!(...)
?error[E0046]: not all trait items implemented, missing:
flush
--> src/main.rs:56:1 | 56 | / impl Log for Logger { 57 | | fn enabled(&self, metadata: &LogMetadata) -> bool { 58 | | metadata.level() <= log::max_log_level() 59 | | } ... | 65 | | } 66 | | } | |_^ missingflush
in implementation | = note:flush
from trait:fn(&Self)
error: aborting due to 5 previous errors
error: Could not compile
nvfancontrol
.To learn more, run the command again with --verbose.