You are not logged in.
- Topics: Active | Unanswered
#1 2021-04-12 16:11:01
- Cuissedemouche
- Member
- Registered: 2021-04-12
- Posts: 4
[SOLVED] Can't find a correlation between fans and pwm - DesktopComput
Hi guys,
Since a bit more than a week, I'm trying to configure the fans speed for my new config but I can't find a correlation between my PWM and fans.
My fans are PWM, and I can set the speed easily under my Windows partition.
I tried to follow the wiki:
https://wiki.archlinux.org/index.php/fan_speed_control
I already attempted this on another machine (my Unraid server) with success.
After the sensors-detect, I first have a problem en permission running pwmconfig:
sudo pwmconfig
# pwmconfig version 3.6.0+git
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.
Found the following devices:
hwmon0 is nvme
hwmon1 is k10temp
hwmon2 is nct6687
hwmon3 is iwlwifi_1
hwmon4 is hidpp_battery_0
Found the following PWM controls:
hwmon2/pwm1 current value: 98
/usr/bin/pwmconfig: line 180: hwmon2/pwm1: Permission denied
hwmon2/pwm2 current value: 255
/usr/bin/pwmconfig: line 180: hwmon2/pwm2: Permission denied
hwmon2/pwm3 current value: 153
/usr/bin/pwmconfig: line 180: hwmon2/pwm3: Permission denied
hwmon2/pwm4 current value: 0
/usr/bin/pwmconfig: line 180: hwmon2/pwm4: Permission denied
hwmon2/pwm5 current value: 255
/usr/bin/pwmconfig: line 180: hwmon2/pwm5: Permission denied
hwmon2/pwm6 current value: 255
/usr/bin/pwmconfig: line 180: hwmon2/pwm6: Permission denied
hwmon2/pwm7 current value: 255
/usr/bin/pwmconfig: line 180: hwmon2/pwm7: Permission denied
hwmon2/pwm8 current value: 128
/usr/bin/pwmconfig: line 180: hwmon2/pwm8: Permission denied
Giving the fans some time to reach full speed...
Found the following fan sensors:
hwmon2/fan1_input current speed: 4743 RPM
hwmon2/fan2_input current speed: 2065 RPM
hwmon2/fan3_input current speed: 1528 RPM
hwmon2/fan4_input current speed: 731 RPM
hwmon2/fan5_input current speed: 0 ... skipping!
hwmon2/fan6_input current speed: 0 ... skipping!
hwmon2/fan7_input current speed: 0 ... skipping!
hwmon2/fan8_input current speed: 0 ... skipping!
hwmon2/fan9_input current speed: 0 ... skipping!
Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue:
Testing pwm control hwmon2/pwm1 ...
/usr/bin/pwmconfig: line 225: hwmon2/pwm1: Permission denied
Manual control mode not supported, skipping.
Testing pwm control hwmon2/pwm2 ...
/usr/bin/pwmconfig: line 225: hwmon2/pwm2: Permission denied
Manual control mode not supported, skipping.
Testing pwm control hwmon2/pwm3 ...
/usr/bin/pwmconfig: line 225: hwmon2/pwm3: Permission denied
Manual control mode not supported, skipping.
Testing pwm control hwmon2/pwm4 ...
/usr/bin/pwmconfig: line 225: hwmon2/pwm4: Permission denied
Manual control mode not supported, skipping.
Testing pwm control hwmon2/pwm5 ...
/usr/bin/pwmconfig: line 225: hwmon2/pwm5: Permission denied
Manual control mode not supported, skipping.
Testing pwm control hwmon2/pwm6 ...
/usr/bin/pwmconfig: line 225: hwmon2/pwm6: Permission denied
Manual control mode not supported, skipping.
Testing pwm control hwmon2/pwm7 ...
/usr/bin/pwmconfig: line 225: hwmon2/pwm7: Permission denied
Manual control mode not supported, skipping.
Testing pwm control hwmon2/pwm8 ...
/usr/bin/pwmconfig: line 225: hwmon2/pwm8: Permission denied
Manual control mode not supported, skipping.
Testing is complete.
Please verify that all fans have returned to their normal speed.So I just run a
sudo chmod +w /sys/devices/platform/nct6683.2592/hwmon/hwmon2/pwm*After this, I don't have the permission error anymore, but pwmconfig can't find a correlation with my fans:
sudo pwmconfig
# pwmconfig version 3.6.0+git
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.
Found the following devices:
hwmon0 is nvme
hwmon1 is k10temp
hwmon2 is nct6687
hwmon3 is iwlwifi_1
hwmon4 is hidpp_battery_0
Found the following PWM controls:
hwmon2/pwm1 current value: 104
hwmon2/pwm2 current value: 255
hwmon2/pwm3 current value: 153
hwmon2/pwm4 current value: 0
hwmon2/pwm5 current value: 255
hwmon2/pwm6 current value: 255
hwmon2/pwm7 current value: 255
hwmon2/pwm8 current value: 128
Giving the fans some time to reach full speed...
Found the following fan sensors:
hwmon2/fan1_input current speed: 4761 RPM
hwmon2/fan2_input current speed: 2044 RPM
hwmon2/fan3_input current speed: 1534 RPM
hwmon2/fan4_input current speed: 0 ... skipping!
hwmon2/fan5_input current speed: 0 ... skipping!
hwmon2/fan6_input current speed: 0 ... skipping!
hwmon2/fan7_input current speed: 0 ... skipping!
hwmon2/fan8_input current speed: 0 ... skipping!
hwmon2/fan9_input current speed: 0 ... skipping!
Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue:
Testing pwm control hwmon2/pwm1 ...
hwmon2/fan1_input ... speed was 4761 now 4724
no correlation
hwmon2/fan2_input ... speed was 2044 now 2097
no correlation
hwmon2/fan3_input ... speed was 1534 now 1532
no correlation
No correlations were detected.
There is either no fan connected to the output of hwmon2/pwm1,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)?
Testing pwm control hwmon2/pwm2 ...
hwmon2/fan1_input ... speed was 4761 now 4724
no correlation
hwmon2/fan2_input ... speed was 2044 now 2044
no correlation
hwmon2/fan3_input ... speed was 1534 now 1528
no correlation
No correlations were detected.
There is either no fan connected to the output of hwmon2/pwm2,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)?
Testing pwm control hwmon2/pwm3 ...
hwmon2/fan1_input ... speed was 4761 now 4724
no correlation
hwmon2/fan2_input ... speed was 2044 now 2097
no correlation
hwmon2/fan3_input ... speed was 1534 now 1536
no correlation
No correlations were detected.
There is either no fan connected to the output of hwmon2/pwm3,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)?
Testing pwm control hwmon2/pwm4 ...
hwmon2/fan1_input ... speed was 4761 now 4743
no correlation
hwmon2/fan2_input ... speed was 2044 now 2094
no correlation
hwmon2/fan3_input ... speed was 1534 now 1530
no correlation
No correlations were detected.
There is either no fan connected to the output of hwmon2/pwm4,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)?
Testing pwm control hwmon2/pwm5 ...
hwmon2/fan1_input ... speed was 4761 now 4761
no correlation
hwmon2/fan2_input ... speed was 2044 now 2094
no correlation
hwmon2/fan3_input ... speed was 1534 now 1544
no correlation
No correlations were detected.
There is either no fan connected to the output of hwmon2/pwm5,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)?
Testing pwm control hwmon2/pwm6 ...
hwmon2/fan1_input ... speed was 4761 now 4761
no correlation
hwmon2/fan2_input ... speed was 2044 now 2094
no correlation
hwmon2/fan3_input ... speed was 1534 now 1534
no correlation
No correlations were detected.
There is either no fan connected to the output of hwmon2/pwm6,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)?
Testing pwm control hwmon2/pwm7 ...
hwmon2/fan1_input ... speed was 4761 now 4705
no correlation
hwmon2/fan2_input ... speed was 2044 now 2068
no correlation
hwmon2/fan3_input ... speed was 1534 now 1538
no correlation
No correlations were detected.
There is either no fan connected to the output of hwmon2/pwm7,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)?
Testing pwm control hwmon2/pwm8 ...
hwmon2/fan1_input ... speed was 4761 now 4761
no correlation
hwmon2/fan2_input ... speed was 2044 now 2097
no correlation
hwmon2/fan3_input ... speed was 1534 now 1542
no correlation
No correlations were detected.
There is either no fan connected to the output of hwmon2/pwm8,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)?
Testing is complete.
Please verify that all fans have returned to their normal speed.I also modify manually every pwm* files to 0 and to 255 to see if it would do something without any success.
Here what could be relevant for the config:
MB: MSI MPG B550i
CPU: AMD Ryzen 9 5950X
AIO: Corsair Hydro iCUE H100i
GPU: RTX 3090 (deshroud, that mean I removed the fans)
FAN1: Noctua A9x14 connected to a fan case header
FAN2: 2x Noctua A12x25 + 2x Noctua A12x15 connected to the AIO
FAN3: 2x Noctua A12x25 connected to a fan case header (under my deshroud GPU)
FAN4: NVMe fan (included with MB and different connection)
Last edited by Cuissedemouche (2021-04-14 17:48:48)
Offline
#2 2021-04-13 12:08:07
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,008
Re: [SOLVED] Can't find a correlation between fans and pwm - DesktopComput
hwmon2 is nct6687That chipset should be supported by the ntc6683D kernel module .
Is that module loaded ?
You could also try using https://aur.archlinux.org/packages/nct6687d-dkms-git/ .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#3 2021-04-13 12:27:42
- Cuissedemouche
- Member
- Registered: 2021-04-12
- Posts: 4
Re: [SOLVED] Can't find a correlation between fans and pwm - DesktopComput
Oh yes you saved my life !
I read online that the NCT6687D was managed by the nct6683, that was already installed and I was using, so I didn't think there were other packages.
Installing the package nct6687d-dkms-git that you suggest solved the problem.
You're my hero thank you.
EDIT:
Problem maybe not completely solved, I have to do few test before returning them.
EDIT 2:
While booting the computer, I have nct6687 loaded to hwmon2, but while running pwmconfig it still not working.
So to make my pwm work, I have to do:
sudo modprobe nct6687The problem is that it will load a new instance of nct6687 but under hwmon5
Found the following devices:
hwmon0 is nvme
hwmon1 is k10temp
hwmon2 is nct6687
hwmon3 is iwlwifi_1
hwmon4 is hidpp_battery_0
hwmon5 is nct6687Now, while editing the hwmon2/pwm* or hwmon5/pwm* it change the fan speed, but why do I have to reload a new time under root privileges the module to even make work hwmon2?
Also it creates a mess with my sensors command doing that:
sensors
nct6687-isa-0a20
Adapter: ISA adapter
VIN0: 1.01 V (min = +0.00 V, max = +0.00 V)
VIN1: 1.01 V (min = +0.00 V, max = +0.00 V)
VIN2: 1.01 V (min = +0.00 V, max = +0.00 V)
VIN3: 672.00 mV (min = +0.00 V, max = +0.00 V)
VIN4: 320.00 mV (min = +0.00 V, max = +0.00 V)
VIN5: 800.00 mV (min = +0.00 V, max = +0.00 V)
VIN6: 720.00 mV (min = +0.00 V, max = +0.00 V)
VIN7: 1.50 V (min = +0.00 V, max = +0.00 V)
VCC: 3.38 V (min = +0.00 V, max = +0.00 V)
VTT: 1.82 V (min = +0.00 V, max = +0.00 V)
VSB: 3.33 V (min = +0.00 V, max = +0.00 V)
AVSB: 3.33 V (min = +0.00 V, max = +0.00 V)
VTT: 1.82 V (min = +0.00 V, max = +0.00 V)
VBAT: 3.28 V (min = +0.00 V, max = +0.00 V)
fan1: 4743 RPM (min = 0 RPM)
fan2: 1011 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
fan6: 0 RPM (min = 0 RPM)
fan7: 0 RPM (min = 0 RPM)
fan8: 0 RPM (min = 0 RPM)
fan9: 0 RPM (min = 0 RPM)
fan10: 0 RPM (min = 0 RPM)
AMD TSI Addr 98h: +41.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = AMD AMDSI
Diode 0 (curr): +42.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermal diode
Thermistor 15: +35.5°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 1: +41.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 16: +34.5°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 0: +36.5°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 15: +0.0°C (low = +0.0°C)
(high = +110.0°C, hyst = +23.0°C)
(crit = +0.0°C) sensor = thermistor
intrusion0: ALARM
beep_enable: disabled
nvme-pci-0100
Adapter: PCI adapter
Composite: +36.9°C (low = -273.1°C, high = +84.8°C)
(crit = +84.8°C)
Sensor 1: +36.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +42.9°C (low = -273.1°C, high = +65261.8°C)
nct6687-isa-0a20
Adapter: ISA adapter
+12V: 12.22 V (min = +12.22 V, max = +12.22 V)
+5V: 5.07 V (min = +5.06 V, max = +5.07 V)
+3.3V: 3.33 V (min = +3.33 V, max = +3.33 V)
CPU Soc: 1.01 V (min = +1.01 V, max = +1.01 V)
CPU Vcore: 320.00 mV (min = +0.26 V, max = +0.51 V)
CPU 1P8: 1.84 V (min = +1.84 V, max = +1.84 V)
CPU VDDP: 0.00 V (min = +0.00 V, max = +0.00 V)
DRAM: 1.35 V (min = +1.35 V, max = +1.35 V)
Chipset: 808.00 mV (min = +0.81 V, max = +0.81 V)
ERROR: Can't get value of subfeature in9_input: Kernel interface error
ERROR: Can't get value of subfeature in9_min: Kernel interface error
ERROR: Can't get value of subfeature in9_max: Kernel interface error
in9: N/A (min = +0.00 V, max = +0.00 V)
ERROR: Can't get value of subfeature in10_input: Kernel interface error
ERROR: Can't get value of subfeature in10_min: Kernel interface error
ERROR: Can't get value of subfeature in10_max: Kernel interface error
in10: N/A (min = +0.00 V, max = +0.00 V)
ERROR: Can't get value of subfeature in11_input: Kernel interface error
ERROR: Can't get value of subfeature in11_min: Kernel interface error
ERROR: Can't get value of subfeature in11_max: Kernel interface error
in11: N/A (min = +0.00 V, max = +0.00 V)
ERROR: Can't get value of subfeature in12_input: Kernel interface error
ERROR: Can't get value of subfeature in12_min: Kernel interface error
ERROR: Can't get value of subfeature in12_max: Kernel interface error
in12: N/A (min = +0.00 V, max = +0.00 V)
ERROR: Can't get value of subfeature in13_input: Kernel interface error
ERROR: Can't get value of subfeature in13_min: Kernel interface error
ERROR: Can't get value of subfeature in13_max: Kernel interface error
in13: N/A (min = +0.00 V, max = +0.00 V)
CPU Fan: 4743 RPM (min = 4562 RPM)
Pump Fan: 1011 RPM (min = 1010 RPM)
System Fan #1: 0 RPM (min = 0 RPM)
System Fan #2: 0 RPM (min = 0 RPM)
System Fan #3: 0 RPM (min = 0 RPM)
System Fan #4: 0 RPM (min = 0 RPM)
System Fan #5: 0 RPM (min = 0 RPM)
System Fan #6: 0 RPM (min = 0 RPM)
ERROR: Can't get value of subfeature fan9_input: Kernel interface error
ERROR: Can't get value of subfeature fan9_min: Kernel interface error
fan9: N/A (min = 0 RPM)
ERROR: Can't get value of subfeature fan10_input: Kernel interface error
ERROR: Can't get value of subfeature fan10_min: Kernel interface error
fan10: N/A (min = 0 RPM)
ERROR: Can't get value of subfeature temp1_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp1_crit: Kernel interface error
CPU: +41.0°C (low = +38.0°C)
(high = +41.0°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp1_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
ERROR: Can't get value of subfeature temp2_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp2_crit: Kernel interface error
System: +42.0°C (low = +42.0°C)
(high = +42.0°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp2_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
ERROR: Can't get value of subfeature temp3_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp3_crit: Kernel interface error
VRM MOS: +35.0°C (low = +35.0°C)
(high = +35.0°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp3_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
ERROR: Can't get value of subfeature temp4_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp4_crit: Kernel interface error
PCH: +41.0°C (low = +41.0°C)
(high = +41.0°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp4_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
ERROR: Can't get value of subfeature temp5_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp5_crit: Kernel interface error
CPU Socket: +34.0°C (low = +34.0°C)
(high = +34.0°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp5_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
ERROR: Can't get value of subfeature temp6_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp6_crit: Kernel interface error
PCIe x1: +36.0°C (low = +36.0°C)
(high = +36.0°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp6_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
ERROR: Can't get value of subfeature temp7_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp7_crit: Kernel interface error
M2_1: +0.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp7_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: N/A
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +40.8°C
Tdie: +40.8°C Last edited by Cuissedemouche (2021-04-13 13:07:06)
Offline
#4 2021-04-14 14:13:54
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,008
Re: [SOLVED] Can't find a correlation between fans and pwm - DesktopComput
Please stop editing those permissions / using sudo to do things as root .
Either login to a text -console (tty) as root, or start a X / wayland terminal and use su - to get a clean login shell as root .
create as root /etc/modprobe.d/no_nct6683.conf
# Do not load the nct6683 module on boot.
blacklist nct6683
# uncomment the line below if blacklisting is not sufficient
# install nct6683 /bin/truereboot , login as root
Use lsmod | grep nct to check if nct6683 is still present.
Incase it is present :
edit /etc/modprobe.d/no_nct6683.conf
uncomment the install line
reboot
still logged in as root
Once nct6683 is not loaded anymore
modprobe nct6687
post pwmconfig output, it should no longer list nct6683 and just one hwmon* entry with nct6687
Test changing fans and report back.
Get everything working as root first, then look at making settings permanent / allowing non-root to change things.
Edit: corrected module names
Last edited by Lone_Wolf (2021-04-14 15:30:09)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#5 2021-04-14 15:08:28
- Cuissedemouche
- Member
- Registered: 2021-04-12
- Posts: 4
Re: [SOLVED] Can't find a correlation between fans and pwm - DesktopComput
Ok, I never understood when using sudo or when using su.
So I did what you asked, I just replace nct6833 by nct6683 in your file (probably a small typo problem) and it unload successfully the nct6683:
lsmod | grep nct
pinctrl_amd 32768 1After loading nct6687, I run a pwmconfig and yes, everything is corrected. I forgot that the first nct6687 was actually the nct6683 module.
# pwmconfig version 3.6.0+git
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.
Found the following devices:
hwmon0 is nvme
hwmon1 is k10temp
hwmon2 is iwlwifi_1
hwmon3 is hidpp_battery_0
hwmon4 is nct6687
Found the following PWM controls:
hwmon4/pwm1 current value: 255
hwmon4/pwm2 current value: 255
hwmon4/pwm3 current value: 255
hwmon4/pwm4 current value: 255
hwmon4/pwm5 current value: 255
hwmon4/pwm6 current value: 255
hwmon4/pwm7 current value: 255
hwmon4/pwm8 current value: 128
Giving the fans some time to reach full speed...
Found the following fan sensors:
hwmon4/fan1_input current speed: 4780 RPM
hwmon4/fan2_input current speed: 2105 RPM
hwmon4/fan3_input current speed: 2116 RPM
hwmon4/fan4_input current speed: 13186 RPM
hwmon4/fan5_input current speed: 0 ... skipping!
hwmon4/fan6_input current speed: 0 ... skipping!
hwmon4/fan7_input current speed: 0 ... skipping!
hwmon4/fan8_input current speed: 0 ... skipping!
Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue:
Testing pwm control hwmon4/pwm1 ...So now I suppose the goal is to load the module during the boot?
I created as root /etc/modules-load.d/nct6687.conf with just nct6687 in it.
It seems working but I would like to know if I again did a mess or if it is correct.
Offline
#6 2021-04-14 16:02:46
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,008
Re: [SOLVED] Can't find a correlation between fans and pwm - DesktopComput
I did indeed have typos in the module names .
The cause of the extra hwmon and weird errors from sensors was that both nct6683 and nct6687 were accessing the same hardware .
Since the functionality you want is not yet available from the in-kernel nct6683 module, preventing it from getting loaded itfp aka blacklisting it is the simplest way to ensure only the nct6687 module has access to the hardware.
You correctly automated the loading of nct6687 .
Next steps are on the fan speed control wiki page https://wiki.archlinux.org/index.php/fa … figuration
as for sudo / su :
I often have trouble with them and use following scenarios to distinguish between them :
- family member asks you to open the trunk of their car and gives you the keys .
- your boss can't make it to an important meeting and asks you to take over his part in the meeting.
You will have exactly the same powers & authority as your boss for the duration of the meeting.
In the first scenario you use sudo rights, while in the second scenario you acquire su rights.
Last edited by Lone_Wolf (2021-04-14 16:03:50)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#7 2021-04-14 17:48:06
- Cuissedemouche
- Member
- Registered: 2021-04-12
- Posts: 4
Re: [SOLVED] Can't find a correlation between fans and pwm - DesktopComput
Ahah I like your analogy for sudo/su
Otherwise I set the next part already, almost completely at least, right now I'm trying to check if how to change a case fan speed depending of the temperature of my graphic card (and it's quite a requirement since I have a deshrouded GPU).
Thanks a lot for you help.
Offline