Overclocking settings
Does the DietPi for OpiPC include bronco's fixes to dvfs from http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=724&extra=page%3D1My main concern is reliable operation, with these changes my compute unit works without heatsink and does not produce much heat.
With original settings OPi was idling at 42-43*C. Using bronco's dvfs settings board is idling at 33-35*C. Worth trying. zgoda replied at 2015-12-12 14:59
With original settings OPi was idling at 42-43*C. Using bronco's dvfs settings board is idling at 33 ...
Intresting. I've never had an issue with stability or high tempratures using the default clocks. As underclocking is a personal choice, I wont be rolling this out with DietPi. As we use Loboris image, if he makes the decision to impliment it, it would then be applied to DietPi installations aswell.
DietPi-Config allows you to limit the maximum CPU frequencies and gets applied automatically during boot.
Although the current kernel doesnt supply us with scaling_available_frequencies to generate a list, you can manually set the value (1200mhz):
nano /DietPi/dietpi.txtChange:
cpu_max_frequency=1200
The above would then be applied after a reboot and during every boot. Use the following to check freqs:
cpu
Edited by bronco at 2015-12-14 15:26
Fourdee replied at 2015-12-14 03:56
Intresting. I've never had an issue with stability or high tempratures using the default clocks. A ...
Unless you want to understand how dvfs settings work, limiting the maximum cpufreq while relying on the limited overvolted dvfs table is just a joke. Since with your settings you fry the H3 at 1.3V constantly instead of using less Vcore voltage.
Again: The main problem is not default overclocking introduced by Xunlong but dumb adjusting of the dvfs table leading to a VCore voltage of either 1.3V (1.2 GHz or below) or 1.5V (above 1.2GHz): http://forum.armbian.com/index.p ... ew-of-orange-pi-pc/
So actually with these settings you're undervolting the H3 at 1.2 GHz which is also bad. I believe the best idea is to adopt the official linux-sunxi dvfs settings:
https://groups.google.com/forum/#!topic/linux-sunxi/20Ir4It3GsA (read Siarhei's explanations carefully)
That's why I changed settings the hard way, bin2fex, edit dvfs table and set voltages, fex2bin. Edited by bronco at 2015-12-14 23:09
zgoda replied at 2015-12-14 22:53
That's why I changed settings the hard way, bin2fex, edit dvfs table and set voltages, fex2bin.
In the meantime I corrected the script that should do this automagically on Debian based distros to adopt the official linux-sunxi settings: http://www.orangepi.org/orangepi ... d=785&fromuid=29411
A backup of the SD card is mandatory before using the script since when exchanging script.bin fails the board might not even boot any more. bronco replied at 2015-12-14 07:11
Unless you want to understand how dvfs settings work, limiting the maximum cpufreq while relying on ...
Any official word from Allwiner confirming max clock speed, and, vcore values per clock step for the H3? Fourdee replied at 2015-12-16 05:28
Any official word from Allwiner confirming max clock speed, and, vcore values per clock step for th ...
Nope, but they never provide such informations with product announcements. There's indeed informations in the H3's user manual (and the settings you currently use are way beyond these values).
It's pretty easy: The H3 is "1.2 GHz max".
Every H3 device on this planet (various OTT boxes) is advertised as being "1.2 Ghz", only the Orange Pi's not. The reason is pure marketing. Overvolting history documented here: http://www.orangepi.org/orangepi ... =7009&fromuid=29411
And you find also relevant informations in the approriate article on linux-sunxi (more or less concentrating on the 'PC' since the other H3 based Orange Pis are pretty uninteresting): http://linux-sunxi.org/Orange_Pi_PC#CPU_clock_speed_limit
page:
[1]