New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPi5 active cooler fan starts full-throttle #501
Comments
I kind of like this behaviour - it lets you know that the fan is working. It also blows any dust out of the systemas in the rack-mount servers you refer to. |
There's another benefit of doing this - the RP1 firmware maintains a max recorded RPM value, which is useful for determining if your fan motor is on the way out. |
Having some side-benefits for a bug doesn't make it a feature. This should be fixed; another thing is if there should be some kind of configuration for it. |
The fact that you don't like it doesn't make it a bug. |
When there are tons of reports on forums by regular users asking why the fan seems a rocket at init, without any real reason for the final user, with low temps... that looks to me a bug or an unwanted behavior. Your argument can be used with your own answer, you like it, that doesn't make it "right". And most regular users DON'T use raspi for rack servers. They just want a silent thing on their room. Closing this issue is totally arbitrary. |
Describe the bug
When powering up the RPi5 with an active cooler the fan runs full-throttle, being annoyingly noisy like 19" rack servers, until the kernel pwm-fan driver is finally loaded which puts it to silent/off mode.
Especially when netbooting (and having CONFIG_SENSORS_PWM_FAN set to "m" in kernel config) the fan is noisy for a very long time.
IMHO it would be better to initialize the fan PWM output to "off" (or at most a very low level) as early-stage boot shouldn't be too challenging for the CPU/VPU and having the fan running shouldn't be necessary.
Steps to reproduce the behaviour
Power-up an RPi5 with official active cooler installed and fan connected
Device (s)
Other
Bootloader configuration.
[all]
BOOT_UART=1
POWER_OFF_ON_HALT=1
BOOT_ORDER=0xf421
System
Bootloader logs
No response
USB boot
No response
NVMe boot
No response
Network (TFTP boot)
No response
The text was updated successfully, but these errors were encountered: