Arch fancontrol12/3/2023 ![]() Unikum ( talk) 06:50, (UTC)įancon is great when your fans make noise at specific RPM, as you can set the ranges that it should use. It would be nice to add the instructions to this page. I found the interesting utility to control a fan speed: Regid ( talk) 19:06, 19 November 2022 (UTC) fancon utility The alternative solution below is (section 9.2.2) fan speed control#Alternative solution: absolute paths. If you cannot find any, then you could try using the alternative solution below. If this does not work, I highly recommend finding another program to control your fans. Does anybody know if that solution works well, or if there is another way to reliably keep the hwmon paths persistent instead of using a workaround? Jmarmstrong1207 ( talk) 17:44, 1 August 2019 (UTC)Īt the time of this writing, (section 9.2.1) fan speed control#Solution non definitive answer is: There is the solution to manually load the modules using /etc/modules-load.d/nf, however I do not know if this is guaranteed to fix the issue. Googling the issue brings up a multitude of forum threads of the same issue, however many of them work around the problem and use the absolute paths instead. Linking a permanent solution for the problem of inconsistent hwmon device paths. Also, the following command sets fan speed:Įcho "100" > /sys/class/hwmon/hwmon1/pwm1 Yet it should be the way to control it, since I was able to do it on windows using very specific laptops fan control app. I always give following message using sensors -s: Error: File /etc/sensors.d/nf, line 2: Unknown feature name coretemp-isa-0000: No such subfeature known Not quite sure if it's related, but I am unable to set anything using fan_div instructions. Ziusudra ( talk) 06:06, 26 February 2016 (UTC) The real problem is that the only thing that should be in the #Sensor driver section is a link to the Lm_sensors page saying to get the fan and temp readings working and the explanation of the module loading order. Herodotus ( talk) 19:23, 2 January 2016 (UTC)Īlso editing nf is wrong and there are many chips not in there. I wonder if these kind of hints should be incorporated into the instructions. how do I know when I should give up on these instructions? For instance my MSI Wind has a directory /sys/devices/platform/msi-laptop-pf/, since I don't see anything related to fan control there, perhaps that means I'm out of luck? Whereas my Thinkpad has /sys/devices/platform/thinkpad_hwmon/fan1_input, etc. What is the fan divisor, why would I need to increase it? "Edit /etc/nf and look up the exact chipset." How do I find the chipset that I'm supposed to be looking up?īy the way, how many motherboards simply don't have the capability for software fan control? E.g. Darxus ( talk) 05:57, 15 November 2020 (UTC) Increasing fan_div? KubaF ( talk) 12:19, 22 March 2020 (UTC) That's the same as /sys/class/hwmon/hwmon?/pwm? because device is a link to the absolute path. Perfect for testing fans at specific speeds for buzzing/clicking sounds. For me it is /sys/class/hwmon/hwmon?/device/hwmon/hwmon?/pwm?. Thanks for the link, finally found the path to where fan speeds can be set manually. Maybe something like this should be in the main article? - Unhammer 02:45, 1 October 2009 (EDT) Read it if you're interested in the details (esp. There are many grammar mistakes and might be more logic mistakes, so I am calling everyone willing to help - contribute to this page. What do you think? I've also created AUR script for "NBFC" tool, which I will update in the near future. I've updated this page + moved "ThinkPad Fan Control" to this page too. Of course it could also be placed in the amdgpu article, if you want mostly CPU related fan control around here.Īufkrawall ( talk) 19:55, 22 April 2018 (UTC) It can also be more flexible to adjust to one's own needs. If you argue that the solution via script is redundant to fancontrol: Relying entirely on sysfs and bash doesn't require any additional binary, which might help avoiding additional bugs and other troubles. Also, most users these days use amdgpu and not ati/radeon anymore. However, it seems we want all the fan information at one central place, so we might just want to link from there to here, and perhaps also on the amdgpu page. I'm aware that there is already an entry about it in the ATI driver section.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |