bschwehn

  • Content Count

    5
  • Joined

  • Last visited

About bschwehn

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. In case anyone missed it, Mikaey posted a workaround that does not require a new armbian image / kernel. Perhaps a viable workaround? I am not sure what the best fix is for armbian itself (so that it will be fixed in some upcoming release), so I don't feel confident submitting a pull request, but time permitting I will have another look this weekend.
  2. Haha, that's great, thanks! Silly me has been rebuilding full kernels for a workaround
  3. There is already some discussion about this topic at the other topic However, if this is causing you issues that need fixing now, it shouldn't be too hard to work around it manually until a better solution is available Simplest solution might be to have a script / service running (as root) that does - read temp from /sys/devices/virtual/thermal/thermal_zone0/temp - if temp is too high for you, throttle max frequency, e.g. using cpufreq-set -u 700000 then up the limit again once temp is reduced. Not ideal of course, but should work in
  4. FWIW, these messages seem to go away when building the dev branch without patch /patch/kernel/sunxi-dev/ths-29-sun4i-gpadc-iio-add-h5-thermal-zone.patch Not sure if this patch is compatible with the changes already done in the megous branch (like this patch) Still, throttling is done only down to 1104 MHz (not an issue for me personally, for me this throttle is enough for mine to not go above 81C @100% CPU usage for 10 minutes). Edit: Looks like I have it working now. I have basically added the patch ths-29-sun4i-gpadc-iio-add-h5-thermal-zone.patch directly