ah, i have nov 20th currently....$ vcgencmd bootloader_version
2023/12/14 16:43:25
version 0f8812243344aec92965cda3943fd6d7e2c6170a (release)
checking git history, i can see signs that maybe the firmware was lying a bit
linux claimed the clock was 1ghz, vcgencmd claimed the clock was 1.5ghz
and this comment, implies that before that version, 1.5ghz was the minimum clock* Add support for C(arm_min_freq) < 1500 MHz (must be at >= 200 MHz)
rpi-eeprom-update gaveme december 6th, and the problem is still present
but on closer inspection, it bottoms out at 1.5ghz, but works fine for higher clocks
and i notice, trejan never got a clock under 1.5ghz from vcgencmd, so it might be broken for him as well?
edit:
Code:
root@raspberrypi:~# cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies 1500000 1600000 1700000 1800000 1900000 2000000 2100000 2200000 2300000 2400000 - Image may be NSFW.
Clik here to view.
the min freq that cpufreq can select from has changed after updating the firmware
so with default configs, the "bug" is gone, because you just cant go below 1.5ghz now, which is likely what the commit i found fixes?
i'll need to dig more when it isnt 2am
edit2:
@dom, i can see signs of the same voltage curve bug on the pi5
before updating the firmware, 1.5ghz was 836mv and 1.6ghz was 846mv
after updating the firmware, 1.5ghz is 721mv and 1.6ghz is 821mv
because the 1ghz-1.4ghz options got deleted, the freq and voltage lists shifted out of alignment, and its now using lower voltages at higher clocks
and in this case, it is entirely due to default clocks being changed
Statistics: Posted by cleverca22 — Sat Dec 23, 2023 5:46 am
