-
-
Notifications
You must be signed in to change notification settings - Fork 501
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
DietPi- Config | Set ARM Temp Limit for RPI3 and RPI4 to 75c. Currently set at 65c #3151
Comments
@Trunkzeh |
Hey MichaIng/DietPi ; this was pushed for 6.26.1 or later? It didn’t apply
on my RPI2 on 6.26.1; this was a fresh reinstall.
…On Fri, 11 Oct 2019 at 21:59, MichaIng ***@***.***> wrote:
@Trunkzeh <https://github.com/Trunkzeh>
Many thanks for your request. Indeed this has already been done for v6.26:
https://github.com/MichaIng/DietPi/blob/dev/rootfs/var/lib/dietpi/services/dietpi-firstboot.bash#L79
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3151?email_source=notifications&email_token=AMQYLYB5NSBEDJVG3V2A32DQODSJLA5CNFSM4I7I3FL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBBGINQ#issuecomment-541221942>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMQYLYGNZJJO72GVSXRUNZDQODSJLANCNFSM4I7I3FLQ>
.
|
@Trunkzeh Do you think we should apply the change with v6.26 for all RPi4 models (where currently 65°C is set)? |
@MichaIng Both would be favourable; but certainly RPI4 as these units run considerably hotter than previous generations of raspberrypis. I've kept mine on a fan shim and currently am running it as a testbed for dietpi so its not even running production environment software yet and it will still reach 65c regularly. |
Hey @MichaIng ;
Following on from the previous conversation within the RPI4 temperature bug report; this could probably be done via board ID or HW ID of some description so that the ARM throttling limit is increased to 75c instead of the 65c thats currently being set.
Thoughts on the matter?
The text was updated successfully, but these errors were encountered: