pdieguez

Thank you very much Ojay. By the way, are your kernel upgrades still frozen? Haven't you updated any since you installed Wireguard?

Which exact options did you choose on armbian-config after installing wireguard? I can see "Headers_install" under system. Is that it? What else? Thanks,

I used armbian-config. Way easier than I expected. Thank you. I did not try that before because it says "deprecated" But anyway, thanks.

Hello all, I have noticed that whenever I reboot my Orange Pi 5 board, all the 8 cpus slow down to 408 Mhz with no range, as stated by cpufreq-info: I have created a cronjob script in order to bring the frequency back to acceptable range. I don't even know if this is the correct way to solve this, but I am running the following: echo performance | sudo tee /sys/devices/platform/dmc/devfreq/dmc/governor cpufreq-set -c 0 -u 1800000 cpufreq-set -c 4 -u 2260000 cpufreq-set -c 6 -u 2300000 cpufreq-set -c 0 -g schedutil cpufreq-set -c 4 -g schedutil cpufreq-set -c 6 -g schedutil However, even though I set the frequency for processors 6 and 7 for 2.30 Ghz using this method, they never go that high, as stated by cpufreq-info: analyzing CPU 6: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.26 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:80.22%, 600 MHz:1.90%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:3.98%, 1.42 GHz:2.08%, 1.61 GHz:1.47%, 1.80 GHz:1.01%, 2.02 GHz:1.17%, 2.21 GHz:0.86%, 2.26 GHz:7.30% (2110) analyzing CPU 7: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.26 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:80.22%, 600 MHz:1.90%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:3.98%, 1.42 GHz:2.08%, 1.61 GHz:1.47%, 1.80 GHz:1.01%, 2.02 GHz:1.17%, 2.21 GHz:0.86%, 2.26 GHz:7.30% (2110) Those last two processors only go that high if I run sbc-bench one time, than I get the desired speeds: analyzing CPU 6: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.30 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.30 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.30 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 2.30 GHz (asserted by call to hardware). cpufreq stats: 408 MHz:0.00%, 600 MHz:0.00%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:3.63%, 2.21 GHz:5.86%, 2.30 GHz:90.50% (1538) analyzing CPU 7: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.30 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.30 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.30 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 2.30 GHz (asserted by call to hardware). cpufreq stats: 408 MHz:0.00%, 600 MHz:0.00%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:3.63%, 2.21 GHz:5.86%, 2.30 GHz:90.50% (1538) What is the correct way to solve this? What is sbc-bench doing in order to achieve these frenquencies?? Best regards,

Hello all, I am running an Orange Pi 5 board with Armbian on a SD Card and I realized that my /var/log path is constantly full, with it being at /dev/zram1 It gets full at 50Mb with the file /var/log/samba/cores/smbd/core taking up all the space I have not managed to read this file, so I can't tell what kinds of errors are showing up. My OpenMediaVault and samba setup are running perfectly fine, and even though I delete this core file, it shows up again during reboot. I have tried to set enable core files = no in smb.conf With no sucess. The file continues to show up during reboot. Any ideas how to solve this? Best regards