MichaIng

Many thanks for your question. The GPU governor has no effect on the maximum frequency, it only decides if/when to change it in the set min/max borders. I remember for...

Please try the following: ```sh if grep -q '^overlays=' /boot/armbianEnv.txt then sed -i '/^overlays=/s/$/ rk3399-opp-2ghz/' /boot/armbianEnv.txt else echo 'overlays=rk3399-opp-2ghz' >> /boot/armbianEnv.txt fi reboot ``` This adds the RK3399 2 GHz...

Great 🙂, I'll mark the issue as closed then. Feel free to reopen if required.

Oh, that is nasty, I'll try to replicate on NanoPi R4S.

I verified that overclocking doesn't work on NanoPi R4S either, so it seems to affect all RK3399 SBCs with recent kernel v5.15 😞. Basically reported here: https://forum.armbian.com/topic/20584-armbian-config-it-does-not-work/ And: https://forum.armbian.com/topic/18153-rk3399-ram-overclocking-rockpro64/

Ah nice, many thanks for compiling it. So the bootloader picked it automatically, right?

Ah okay. I'll have a look, probably it works when changing the U-Boot environment.

That is strange, Linux 5.15 supports cgroupsv2 / unified cgroup hierarchy, so that shouldn't be required 🤔. Ah, now I read again the missing `BPF_CGROUP_DEVICE`. We need to report this...

Many thanks for your report. Did this work with the version we provided before DietPi v8.5? Are there probably some related error logs, either: ```sh journalctl -u amiberry ``` or...

Hmm, on DietPi, Amiberry (still) runs as root, though I actually want to change this when I find time. So at least there shouldn't be permission issues.