Is it possible to overclock the Rock Pi 4?

If you look at the arm docs

says 650mhz there so guessing 800 for the t860 is reasonably high.
800 is what Google chromebooks went for a max and expecting there might not be a whole load more to be had as they where also fairly aggressive with the 2.0/1.5Ghz

Just edit the dtsi and try but that is up to you

1 Like

The 2.0/1.5Ghz overclock seems really stable with my silicon.
Keep running benches as stability tests.

@stuartiannaylor , I downloaded your ‘rk3399-rock-pi-4.dtb’, running Radxa’s Ubtunu Server instance, are you saying that the dtb can just be swapped out on a live instance, and reboot with overclock settings?

Its the mainline dtb mv old dtb to .bak copy new and yeah.
Definately works with manjaro that way or what you can do is compile your own kernel.

Or git clone current radxa master kernel
zcat /proc/config.gz > .config clone current config to .config in kernel root directory

go to mainline grab /arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi
place in your radxa kernel git clone @ /arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi
Change the line in /arch/arm64/boot/dts/rockchip/rockpi-4b-linux.dts #include "rk3399-opp.dtsi" to #include "rk3399-op1-opp.dtsi"
You don’t need the kernel and a long way but it will make a dts for you that you can do the same with if there is any difference as the above.
Or convert both to dts and just make the cpu table changes then convert back

1 Like

For some reason I can’t get Manjaro to boot on my RockPi 4A.

I’ll give Armbian a shot, Ubuntu Server works, but there is no ‘rk3399-rock-pi-4.dtb’ to swap in their dtbs folder.

Using Rock Pi 4 Minimal (Manjaro) -

Simply doesn’t boot up.

Dunno about Pi4A but that is just the bt/wifi but there is a long boot delay when upgraded to 5.2.
The is no printk console and you have to wait but yeah that is the right link.

Yeah only thing removed in 4A is bt/wifi, otherwise it’s the same (1gb ram). I can get Armbian working, Ubuntu Server as well. Manjaro just doesn’t boot up. How long was the boot delay on first install for you?

Its not that bad 5.1 30secs+, 5.2 there are errors and its bad 3mins+

1 Like

@stuartiannaylor, in Manjaro what’s the pathway for ‘rk3399-rock-pi-4.dtb’? I couldn’t get it to work on the 4A but want to see what it maps to on Ubuntu.

The overlays and everthing with the 4.4 kernel is different.
Use as stretch check overlays as 2.0ghz in there

1 Like

Just in case someone will need that. You need to do

sudo apt-get install rockpi4-dtbo

to get /boot/hw_intfc.conf file in Ubuntu Server


to “overclock” the gpu to 800 mhz just

echo performance | sudo tee /sys/class/drm/card1/device/devfreq/devfreq0/governor

if its presente on the dbt it should work
mine was at 200 mhz on powersave, clocked to just 200 mhz and then ive get it to 800 so easily.

1 Like

Not sure if that is an OC you are just turning scaling off so that its running at max all time even when no workload.
Its very easy to use the op1 dts inclusion and compile and get a big/little OC but have not seen an increase with the GPU on the default.

I messure the gpu freq. and setting it to ondemand or performance it could reach to 800 mhz…permanent if you set performance. anything of this iits not really overclock, its on the dtb as you said… it has the 800 mhz setting there, you just need to enable it, and powersave lock the gpu to 200 mhz ON MY SETUP (armbian). I dont know the others . cheers

What i mean if even when running opengl test or emulators, the gpu keeps on 200 mhz on powersave, the scaler doesnt work properly.

Governor Description
performance Run the CPU at the maximum frequency.
powersave Run the CPU at the minimum frequency.
userspace Run the CPU at user specified frequencies.
ondemand Scales the frequency dynamically according to current load. Jumps to the highest frequency and then possibly back off as the idle time increases.
conservative Scales the frequency dynamically according to current load. Scales the frequency more gradually than ondemand.
schedutil Scheduler-driven CPU frequency selection [1], [2].

Same with GPU the scaling works fine as that is what its supposed to do.
The ‘powersave’ scaler does what it is implemented to do but its an awful power save method as it just renders your cpu/gpu at lowest performance.
Ondemand/conservative is prob the best “powersave” unless some form of intelligent userspace control is used control is used.


Is there any way to overclock 4C+, which runs RK3399-T?
Playing with the cpufreq did not help, despite the latest packages (Ubuntu 20.04).

As above use dtc to convert the dtb to a rexr dts edit the opp table convert back to a dtb in /boot and see if changes are applied or its somehow its fixed freq.
Likely you will need to up the current entries in Freq & Volt

Hi, thank you for suggestion, however I have a silly question. I converted and opened rk3399-rock-pi-4c-plus.dts and see that it contains frequencies higher than opp-1512000000: up to 1800000000.
Given the entries are already there, why it does not work?

Dunno as actually don’t know what the difference with the RK3399-T is as don’t have one, I had one of the early rk3399 that where quite hot and you OC to 2Ghz and maybe the T runs cooler or is in some way fixed.
Someone else will prob have to tell you an answer.