安装ArchLinux后无法通过主板BIOS调整风扇转速

CVN B550M GAMING PRO V14

利民AX120RSE

之前用Windows的时候没有问题,用Linux Mint的时候也没有问题。我想让风扇在CPU低于75℃的时候都是停转或者保持低转速。

如果我说的情况不够详细请提醒我,谢谢。

请问各位有没有什么解决方法。

没明白什么是「 无法通过主板BIOS调整风扇转速」。

——是说在BIOS Setup里调整风扇转速的时候风扇的转速不变吗?
——还是说在BIOS Setup里设置好风扇的转速曲线,在Arch Linux运行期间没有遵守?

无论哪种情况,现状是什么样的(请使用肯定句来描述,而不要使用否定句来「下结论」)?

另外,你有安装任何和风扇或者电源管理相关的软件吗?

在BIOS里调整风扇策略后风扇转速不变,进入系统后风扇转速不变。

以前是BIOS里调整风扇策略后风扇转速不变,进入系统后风扇过一段时间变化。

下面是我现在的BIOS设置,我的BIOS好像有2处可以修改风扇策略,我以前只需要修改第1张图的设置就可以有效果了,但现在2处设置都修改后效果仍然没有。

是的,我安装了TLP,在看到你的回复后禁用了TLP,然后重启计算机,但我设置的风扇策略仍然没有生效。

“无论哪种情况,现状是什么样的(请使用肯定句来描述,而不要使用否定句来「下结论」)?”谢谢,我尽量注意。

image

是不是因为现在冬天天冷,CPU的温度一直没达到设定的温度值所以一直没有转?你目前进系统后风扇是会转吗?大约在哪个转速?

使用sensors命令应该可以看到CPU的温度和风扇的转速。可能需要modprobe一个nct多少的模块。

另外,有可能风扇的设置在重启之后并不会重置到BIOS设置的状态。

sensors了一下,但是好像没有风扇转速。

风扇不是没有转,是我认为风扇转速太快了,想要在低温的时候保持静音低转速。

modprobe一个nct多少的模块。谢谢,感觉找到了一些方向,可能确实是这里的问题,我自己去研究一下。

在找到那个模块、能看到风扇转速之后,你可以去/sys/class/hwmon这个目录里看看,有不少信息,也能调节——不过主板的曲线应该有效才是。是不是装TLP的时候安装的软件、设置的参数在它停止之后并没有完全停止工作啊。

哦,那个模块大概是叫nct6775。

去问了下deepseek,尝试加载了nct6775,好像不行。

加载了一些其他的模块,nct7802可以成功加载,但是sensors后仍然不显示风扇转速。

诶?我的B550M-E就可以啊,不过我的是华硕的。

想问下有哪里可以去查每个主版的这个对应模块的表吗。

不知道。我都不记得我当初是在哪里看到的了……

谢谢,我先自己去找一下。

我的经验是先运行一下sudo sensors-detect --auto然后比如在s-tui(或者这里的sensors)里面就能看到更多的设备了,不过桌面PC应该不需要这个就能看到转速了才对

我有个nct6798-isa-0290,下边有很多主板的数据。

[AlmeasqViolet@ArchLinux ~]$ sudo sensors-detect --auto

sensors-detect version 3.6.2

System: Colorful Technology And Development Co.,LTD CVN B550M GAMING FROZEN [Default string]

Kernel: 6.17.9-zen1-1-zen x86_64

Processor: AMD Ryzen 9 3900 12-Core Processor (23/113/0)

Running in automatic mode, default answers to all questions
are assumed.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 16h thermal sensors... No
AMD Family 17h thermal sensors... Success!
(driver `k10temp')
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Hygon Family 18h thermal sensors... No
AMD Family 19h thermal sensors... No
Intel digital thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
Intel 5500/5520/X58 thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus

Next adapter: NVIDIA i2c adapter 2 at b:00.0 (i2c-0)
Do you want to scan it? (yes/NO/selectively):

Next adapter: NVIDIA i2c adapter 3 at b:00.0 (i2c-1)
Do you want to scan it? (yes/NO/selectively):

Next adapter: NVIDIA i2c adapter 4 at b:00.0 (i2c-2)
Do you want to scan it? (yes/NO/selectively):

Next adapter: NVIDIA i2c adapter 5 at b:00.0 (i2c-3)
Do you want to scan it? (yes/NO/selectively):

Next adapter: NVIDIA i2c adapter 6 at b:00.0 (i2c-4)
Do you want to scan it? (yes/NO/selectively):

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-5)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Handled by driver `ee1004' (already loaded), chip type `ee1004'
(note: this is probably NOT a sensor chip!)
Client found at address 0x52
Handled by driver `ee1004' (already loaded), chip type `ee1004'
(note: this is probably NOT a sensor chip!)
Client found at address 0x53
Handled by driver `ee1004' (already loaded), chip type `ee1004'
(note: this is probably NOT a sensor chip!)

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-6)
Do you want to scan it? (YES/no/selectively):

Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-7)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x4f
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... Success!
(confidence 3, driver `lm75')
Probing for `Maxim MAX6642'... No
Probing for `Texas Instruments TMP421'... No
Probing for `Texas Instruments TMP422'... No
Probing for `Texas Instruments TMP435'... No
Probing for `Texas Instruments TMP441'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No

Now follows a summary of the probes I have just done.

Driver `k10temp' (autoloaded):
* Chip `AMD Family 17h thermal sensors' (confidence: 9)

Driver `lm75':
* Bus `SMBus PIIX4 adapter port 1 at 0b20'
Busdriver `i2c_piix4', I2C address 0x4f
Chip `Dallas Semiconductor DS75' (confidence: 3)

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):
[AlmeasqViolet@ArchLinux ~]$

好像没有CPU风扇转速。

modprobe nct6798-isa-0290或者modprobe nct6798吗。

我试了下这样好像不行。

nct6798-isa-0290是一个什么页面的名称吗,然后里面有很多主板的数据?

是一个sensors节的名字,就跟你那些k10temp-pci-00c3什么的类似。你的主板可能和我的不一样。

我的风扇转速可以通过一个GUI软件来控制(机械革命),佬友不妨搜搜类似的软件试试看?

谢谢,今天回家试一试。

:thinking:应该和楼主的问题没有关系,一方面你这个是控制笔记本风扇的,另一方面TUXEDO这个控制中心能用大概率是因为TUXEDO的某款机器用了同样的模具罢了。。