Set CPU clock speed to 2GHz

Banana Pi SBCs design BPI-M3(A83T/R18)
1

Hello,

i am not able to set the cpu frequency to 2GHZ: root@bananapi:~# echo 2016000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq root@bananapi:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1800000

And here is the output from /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq: 1800000

Any suggenstions?

2

Unless you use an annoying fan you won’t be able to do this anyway. If you want to try it:

But I doubt that 1080mV are enough when exceeding 1.8 GHz. If you increase these values then you’ll have to ensure stability afterwards as outlined here: http://linux-sunxi.org/Hardware_Reliability_Tests#CPU

But again: Unless you use a fan you won’t succeed anyway since throttling will jump in. Installing RPi-Monitor with my A83T template you’ll find out easily why :slight_smile:

3

Hi i just edited the vf_table and set it up to 2016000000. Now i get the following output:

cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq 
2016000

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
performance

echo 2016000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
1800000

Now the CPU supports the higher CPU frequency but i can’t activate it. Temperature throttling can’t be the reason. Also i have got a heat sink and a fan installed.

cat /sys/class/thermal/thermal_zone1/temp 
36

Am I doing something wrong? Any suggestions?

4

Has anyone an idea what i am doing wrong? How do I activate the higher frequency?

5

Could you explain the difference between vf_table0 and vf_table1? Or anyone here know the differencies? At the vf_table0 L_max_freq = 2016 but at vf_table1 L_max_freq = 1800

6

Last post from Dec 22th: http://forum.banana-pi.org/users/tkaiser/activity

Seems he got too annoyed here (quite understandably). Seems you should join another community instead: http://forum.armbian.com/index.php/topic/474-quick-review-of-banana-pi-m3/#entry4022

7

Does anyone have a Suggestion?

8 
cpupower frequency-info
...
  hardware limits: 480 MHz - 1.80 GHz
....

Somebody locking 2GHz frequency… CPU Budget cooling, or what ever. More Investigation required. I spend the whole weekends and didn’t find anything related to this problem…

9

I want to know the same thing. I have heat-sink and cooling fan installed. ready for 2Ghz, but no way to set it.

10

Why don’t you ask for a refund? The board has been advertised as being capable of 2 GHz cpufreq but the vendor neither provides software settings nor support for this.

11

Hi, Here is my vf_table. You see, it works. Regards

[quote]

[dxfs_table] vf_table_count = 3

[vf_table0] L_max_freq = 2016000000 L_boot_freq = 1800000000 L_min_freq = 480000000 L_LV_count = 8 L_LV1_freq = 2016000000 L_LV1_volt = 1080 L_LV2_freq = 1800000000 L_LV2_volt = 1000 L_LV3_freq = 1608000000 L_LV3_volt = 920 L_LV4_freq = 1200000000 L_LV4_volt = 840 L_LV5_freq = 0 L_LV5_volt = 840 L_LV6_freq = 0 L_LV6_volt = 840 L_LV7_freq = 0 L_LV7_volt = 840 L_LV8_freq = 0 L_LV8_volt = 840 B_max_freq = 2016000000 B_boot_freq = 1800000000 B_min_freq = 480000000 B_LV_count = 8 B_LV1_freq = 2016000000 B_LV1_volt = 1080 B_LV2_freq = 1800000000 B_LV2_volt = 1000 B_LV3_freq = 1608000000 B_LV3_volt = 920 B_LV4_freq = 1200000000 B_LV4_volt = 840 B_LV5_freq = 0 B_LV5_volt = 840 B_LV6_freq = 0 B_LV6_volt = 840 B_LV7_freq = 0 B_LV7_volt = 840 B_LV8_freq = 0 B_LV8_volt = 840

[vf_table1] L_max_freq = 2016000000 L_min_freq = 480000000 L_LV_count = 8 L_LV1_freq = 2016000000 L_LV1_volt = 1080 L_LV2_freq = 1800000000 L_LV2_volt = 1000 L_LV3_freq = 1608000000 L_LV3_volt = 920 L_LV4_freq = 1200000000 L_LV4_volt = 840 L_LV5_freq = 0 L_LV5_volt = 840 L_LV6_freq = 0 L_LV6_volt = 840 L_LV7_freq = 0 L_LV7_volt = 840 L_LV8_freq = 0 L_LV8_volt = 840 B_max_freq = 2016000000 B_min_freq = 480000000 B_LV_count = 8 B_LV1_freq = 2016000000 B_LV1_volt = 1080 B_LV2_freq = 1800000000 B_LV2_volt = 1000 B_LV3_freq = 1608000000 B_LV3_volt = 920 B_LV4_freq = 1412000000 B_LV4_volt = 840 B_LV5_freq = 0 B_LV5_volt = 840 B_LV6_freq = 0 B_LV6_volt = 840 B_LV7_freq = 0 B_LV7_volt = 840 B_LV8_freq = 0 B_LV8_volt = 840

[vf_table2] L_max_freq = -2086967296 L_min_freq = 480000000 L_LV_count = 8 L_LV1_freq = -2086967296 L_LV1_volt = 1080 L_LV2_freq = 2016000000 L_LV2_volt = 1000 L_LV3_freq = 1800000000 L_LV3_volt = 920 L_LV4_freq = 1368000000 L_LV4_volt = 840 L_LV5_freq = 0 L_LV5_volt = 840 L_LV6_freq = 0 L_LV6_volt = 840 L_LV7_freq = 0 L_LV7_volt = 840 L_LV8_freq = 0 L_LV8_volt = 840 B_max_freq = -2086967296 B_min_freq = 480000000 B_LV_count = 8 B_LV1_freq = -2086967296 B_LV1_volt = 1080 B_LV2_freq = 2016000000 B_LV2_volt = 1000 B_LV3_freq = 1800000000 B_LV3_volt = 920 B_LV4_freq = 1368000000 B_LV4_volt = 840 B_LV5_freq = 0 B_LV5_volt = 840 B_LV6_freq = 0 B_LV6_volt = 840 B_LV7_freq = 0 B_LV7_volt = 840 B_LV8_freq = 0 B_LV8_volt = 840

[/quote]

12

Nope, idling at 2.016 GHz is one thing, working reliably under full load another (1080mV might be not enough for this clockspeed, due to overheating I haven’t been able to test this out when I unlocked the 2 GHz back in Dec 2015 so my simple conclusion was: allow 1.8 GHz max and accept that this clockspeed can’t be reached anyway since DC-IN/temperatures prevent that).

13

Ich schreibe dir mal auf Deutsch zurĂźck.

Ich habe einen 5v Lßfter montiert und steuere den ßber ein bash Script. Er geht bei einer Temperatur von ßber 55grad Celsius an und läuft bis die Temperatur bei 45 liegt. Mit 2ghz läuft der m3 stabil. Zumindest fßr meine Anforderungen. Habe ihn einen Stresstest unterzogen:

root@bananapi:~# sysbench --test=cpu --cpu-max-prime=100000 run --num-threads=8

Bei diesem steigt die Temperatur auf 73 ( allerdings schaltet er dann bei 61grad auf 1,8ghz) und bleibt dort stabil bis zum Ende. Ich denke also, dass es ok ist und stabil läuft. Ich bin mir bewusst, dass es nicht das beste Board ist, aber habe es leider erst zu spät bemerkt. Bei mir läuft FHEM mit tabletUi, ein Cups printserver und der Rygel Mediastreamer. Hätte gerne noch eine Digital-Out ßber HDMI, aber da muss ich wohl noch lange warten. Deine Infos wären bisher ßbrigens immer recht hilfreich.

Ps: habe meine SATA Festplatte angeschlossen und bin auch mit der Geschwindigkeit zufrieden. Es reicht allemal wenn man keine riesigen Datenmengen transferieren muss.

Danke fĂźr deinen Kommentar.

14

This is not a heavy workload enough and the results are worthless anyway since throttling already occurs. In other words: You did not test whether A83T with just 1080mV will work reliable at above 2.0GHz :slight_smile:

If you love bit flips, data corruption and the like then this is an option. If you want to stay save better refrain from using potentially unreliable and untested settings. It’s possible to test such stuff but I doubt with BPi M3 since overheating is too much of an issue:

15

Sorry, but my english isn’t good enough to understand completely what you say. I have tested one oft the things you show me.

Here is the result.

[quote] [/quote]

The cup temp is stable around 53degrees

16

Which means you just ran the check script but not cpuburn-a7 in parallel (which is a requirement since the whole idea of reliability testing is to heat up the SoC as much as possible and then start to check for bit flips). You will have problems doing this right even with 1.8GHz and 2.0 might need liquid cooling.

And while I don’t care that much about overclocking fans who are happy to fool themselves it should be noted to anyone else who stumbles accross this thread: Don’t try to use 2.0GHz with A83T especially with potentially undervolted VDD_CPUX settings. Test it before. And you won’t be able to test since A83T overheats too much.

It’s as with the H3 SoC. In the beginning everyone (even the vendor of H3 boards) said we’re talking about a Soc ‘capable of running up to 1.6 GHz’. Now everyone accepted that it’s 1.2/1.3 GHz in reality.

With A83T it will just take some time and responsible vendors already speak about ‘octa-core @ 1.6 GHz’: https://www.indiegogo.com/projects/a02-remix-os-octa-core-computer-stick-by-meegopad#/

17

I have run parallel sysbench and cpu-burn

Here is the result

For me it is ok. It’s possible that for a professional is not enough or the board is a big fail. For my requirements it is ok.

18

Nice. But…

  • this has nothing to do with reliability testing (since you have to run cpuburn-a7 together with the test tool to detect undervoltage. Or Linpack since this alone is heavy enough). So all you did was demonstrating how badly A83T is overheating even with fan since your graphs show that clockspeed even decreased 500MHz
  • And this shows how absurd the attempt to overclock BPi M3 is. Since you might be able to run the SoC at 2.0GHz when it’s doing nothing. But as soon as something’s to do the clockspeed decreases dramatically due to throttling

Combine both and you get the idea that unlocking the 2.0GHz has no real benefit (except of wasting a little more energy and heating the SoC up for no reason when you use performance governor) but instead might affect reliability and increases the chance of stability issues and/or data corruption (since with your settings you clearly undervolt the SoC at 2.0 GHz). Combine this with all the real existing stability issues BPi M3 already has (Micro USB for DC-IN) and it just looks like a bad idea (limiting max cpufreq to something lower would be the better idea)

19

Well, if the only reason to unlock 2 GHz is to gain some street credibility (“my board clocks higher than yours!”) then this is totally ok :wink:

But in case you want to benefit in any real world situations from the 2GHz the only situations would be short load peaks where you gain not even 5 percent. If this would be accompanied by save/tested VDD_CPUX voltage settings, everything would be ok. But it’s not (and I write this mainly for others who have the same idea to just increase some values here and there and then think they would be fine – they’re NOT without testing)

And regarding any normal real world performance scenarios it simply doesn’t matter if you unlocked the 2GHz or not since you won’t be able to benefit from anyway. Since throttling is the issue and no real workload will be able to run at 2GHz clockspeed (unless you apply liquid cooling). To give you an idea (did this testing a while ago): https://www.phoronix.com/forums/forum/hardware/general-hardware/856212-raspberry-pi-3-benchmarks-vs-eight-other-arm-linux-boards?p=857160#post857160

20

that was not what I intended, but certainly good to know for other user.