-
Notifications
You must be signed in to change notification settings - Fork 209
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
Raspberry pi 5 active cooler fan full speed all time #660
Comments
Using that EEPROMversion the cooling fan is working as expected for me, with or without your dtparams, and without explicitly loading the cooling-fan overlay.
During reboot, do you see the fan twitch at all before it starts running at full speed? The firmware is supposed to let the fan spin a bit so that activity on the FAN_TACH line indicates the presence of a fan. Newer versions of the EEPROM then turn off the fan until the kernel starts, whereas it used to be left on. |
Ad.1 i'm using "vcgencmd measure_temp" to get temperature without dtparam cooling_fan when rebooting fan was at full speed, stopped for a while and again went full speed. also when powering on it was stopped at the beginning and after a while went full speed and stayed like that. now with "dtparam cooling_fan on" fan is not running during boot and after. it only starts when cpu goes in my case over 45 degress. i believe /boot/overlays/README should be updated: cooling_fan Enables the Pi 5 cooling fan (enabled automatically by the firmware) |
When the fan is spinning, what does |
And no, the README doesn't need updating - that is how it works for me, and it is how it should also work for you. |
!. fan runs at full speed. grep fan /boot/firmware/config.txt cat /sys/class/hwmon//fan1_input
root@pineberry:~# grep cooling /boot/firmware/config.txt root@pineberry:~# vcgencmd measure_temp ; cat /sys/class/hwmon/*/fan1_input running |
unfortunately it doesn't for me. BTW mine is fresh install with "Raspberry Pi Imager" and "Raspberry Pi OS Lite 64bit" |
Describe the bug
I updated my raspberry pi 5 eeprom to:
root@pineberry:/boot/firmware/overlays# rpi-eeprom-update -a
BOOTLOADER: up to date
CURRENT: Wed 22 Jan 00:16:51 UTC 2025 (1737505011)
LATEST: Wed 22 Jan 00:16:51 UTC 2025 (1737505011)
RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2712/default)
Use raspi-config to change the release.
and after update fan connected to built-in 4-pin JST-SH PWM fan connector. started working on full speed despite low temperature:
vcgencmd measure_temp
temp=26.8'C
and is not obeying settings in /boot/firmware/config.txt
dtparam=fan_temp0=45000
dtparam=fan_temp0_hyst=5000
dtparam=fan_temp0_speed=75
dtparam=fan_temp1=50000
dtparam=fan_temp1_hyst=5000
dtparam=fan_temp1_speed=128
dtparam=fan_temp2=55000
dtparam=fan_temp2_hyst=9000
dtparam=fan_temp2_speed=192
dtparam=fan_temp3=60000
dtparam=fan_temp3_hyst=9000
dtparam=fan_temp3_speed=255
found solution this need to be added to config.txt
dtparam=cooling_fan=on
so behavior changed with a new firmware when you compare what is in README.
less /boot/overlays/README
cooling_fan Enables the Pi 5 cooling fan (enabled automatically by the firmware)
so looks like that not enabled automatically now.
Steps to reproduce the behaviour
Device (s)
Raspberry Pi 5
Bootloader configuration.
rpi-eeprom-update
BOOTLOADER: up to date
CURRENT: Wed 22 Jan 00:16:51 UTC 2025 (1737505011)
LATEST: Wed 22 Jan 00:16:51 UTC 2025 (1737505011)
RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2712/default)
Use raspi-config to change the release.
System
cat /etc/rpi-issue
Raspberry Pi reference 2024-11-19
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 891df1e21ed2b6099a2e6a13e26c91dea44b34d4, stage2
vcgencmd bootloader_version
2025/01/22 00:16:51
version a77530632346c8ac1d579fa3c369f9980401e821 (release)
timestamp 1737505011
update-time 1738681359
capabilities 0x0000007f
vcgencmd version
2025/01/22 00:16:51
Copyright (c) 2012 Broadcom
version a7753063 (release) (embedded)
uname -a
Linux pineberry 6.6.74+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025-01-27) aarch64 GNU/Linux
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: