bzfrp

April 9, 2018

Thanks for the tip.

I noticed the same kind of problem for the audio with NanoPi NEO/NEO2. The cpu frequency scaling causes noise.

I have to use the same MIN_SPEED et MAX_SPEED in /etc/default/cpufrequtils. And it works with any governor.

October 9, 2017

Thanks for the review.

An important point: https://forum.odroid.com/viewtopic.php?f=97&t=28535
I also have the same experience. This is not a problem for me. But can be one for others.

January 24, 2017

Fast Ethernet means 8 MB/s at least. With current cpufreq settings in Armbian images actual values might be lower since cpufreq might remain at the lower 240 MHz most of the time. Switching to performance governor might help: http://linux-sunxi.org/Cpufreq#The_.22performance.22_governor

Sorry for my stupid question. Instead of switching to performance governor to fix the frequency, can we disable cpufreq in the kernel and set the desired frequency in uboot?

Is there a difference between these two methods?

Thanks.

Advanced users - Development · January 20, 2017

Got it, so the neo is a exact copy of orange one? I assume it is. Any idea on when will the ethernet be re-enabled?

Not a exact copy. Il seems usb are not the same, you don't have a working usb on nanopi neo if using orange pi one.

Ethernet driver status : http://linux-sunxi.org/Sun8i_emac#Statushttp://linux-sunxi.org/Sun8i_emac#Status

The driver is not in mainline yet. It exists two driver for the moment.

The first, sun8i-emac, is a standalone driver You can find the latest sun8i-emac driver version on https://github.com/montjoie/linux/tree/sun8i-emac-wip This driver will never reach mainline and development is discontinued. But this is still the more stable driver for use.

The second is sun8i-stmmac, still in development, is a glue to the stmmac driver. You can find the current version at https://github.com/montjoie/linux/tree/stmmac-sun8i-wip

January 18, 2017

Hi,

I learn a lot from Armbian and I use its sources and patches. Thanks.

But for my very special purpose, I don't use the Armbian build tool. I use a patch (see attached file) for my NanoPi NEO, not tested for Armbian build tool. If someone wants to try it, maybe put it in lib/patch/kernel/sun8i-dev (after remove the .txt in the name) ?

sun8i-emac-thermal-cpufreq.patch.txt

January 17, 2017

Hello,

Not speculations.

sun8i-emac is not enabled in https://github.com/megous/linux/blob/orange-pi-4.9/arch/arm/boot/dts/sun8i-h3-nanopi-neo.dts

and there is no patch to enable it for NanoPi NEO here: https://github.com/igorpecovnik/lib/tree/master/patch/kernel/sun8i-dev/

January 17, 2017

Maybe emac is not enabled in armbian kernel for NanoPi NEO.

January 13, 2017

I have an opi zero (not using armbian image) and the same problem.

Edit. The wifi works (but unstable) if compile sun8i-emac as module and unload it to disable Ethernet.

January 11, 2017

Anyway: Don't exceed 1008 MHz in u-boot on these boards (and please don't encourage others to do so)

Thanks for your reply. That's just a test, not my final objectif.

I use a NEO for audio streaming, so I want it use 480Mhz and 1.1v all the time, even without cpu-freq in kernel.

January 11, 2017

Hi,

Do you mean that the voltage is 1.1v (default) in the u-boot stage, and the 1.3v can only be obtained after booting using the software?

Thanks.

Using CONFIG_SYS_CLK_FREQ=1200000000 in https://github.com/igorpecovnik/lib/blob/master/patch/u-boot/u-boot-sunxi/add-nanopi-neo.patch and the userspace governor in kernel, my NEO can boot.

Does uboot switch to 1.3v ? or the default voltage is 1.3v ? or 1200Mhz can boot with 1.1v which is the default ?

# cat /sys/devices/system/cpu/cpufreq/policy0/scaling_governor 
userspace
# cat /sys/devices/system/cpu/cpufreq/policy0/stats/time_in_state 
120000 0
240000 0
312000 0
480000 0
624000 0
816000 0
1008000 0
1200000 161322

January 10, 2017

I am trying to use the userspace governor and fix the cpu frequency at 480Mhz.

January 8, 2017

To sum it up (I use NEO as example since there it's more obvious)

NEO is supposed to start with just 480 MHz clockspeed (that setting got lost before 5.20 update but will be re-applied later). Reason: Limit max consumption while booting to 2W. Since default cpufreq governor in sun8i kernel is userspace this means that NEO will run with only 480 MHz until the init system starts cpufrequtils.

Armbian's default u-boot settings are meant for users that have to solve problems from time to time, so we activate some stuff there to interact with u-boot and also have a short delay to stop auto-boot

Armbian normally starts a whole init system that mike some time to finish until the distro's own mechanism to autostart things kicks in (be it a startup item or a call from /etc/rc.local)

To address 1) it's just setting a higher clockspeed. ATM I'm just too lazy to look whether it's ok to set 'CONFIG_SYS_CLK_FREQ=1200000000' there since this would also require u-boot to switch to the higher VDD_CPUX voltage on NanoPis (if the voltage remains at 1.1V then freezes/crashes might occur while booting -- we had that back with OPi One in February when I f*cked up settings for some time). In case no voltage switching happens in u-boot relying on the default 1008 MHz as we do now on all other H3 devices might already be wrong (@Zador?)

Hi,

Do you mean that the voltage is 1.1v (default) in the u-boot stage, and the 1.3v can only be obtained after booting using the software?

Thanks.

December 22, 2016

I do have CPU cooler that i ordered with NanoPI NEO ... the ONLY change i made was put CPU in performance mode running at 1.2 GHz. ....

On my NanoPi NEO UPnP player using upmpdcli/mpd, I tested schedutil. It is not suitable for 24/96 hd files.

I have disabled cpu-freq in the kernel config, and now I am testing ondemand. It seems to work better than schedutil, but I think I'll back to cpu-freq disabled.

Advanced users - Development · December 6, 2016

Hi,

I use buildroot https://buildroot.org

November 17, 2016

Hi,

What is your project ? An audio streamer ?

I have a NanoPi NEO. I tried kernel 4.7.6 and 4.8.3 (using armbian build tools), all worked very well.

November 14, 2016

Thank you. Armbian (kernel 4.7 or 4.8) works well on my NanoPi NEO.

Now just for fun, I want to try to build kernel + busybox + some network and audio applications. But I have a problem with cpufreq. The /sys/devices/system/cpu/cpu0/cpufreq is empty. If I load cpufreq_dt module, the system crashes. If I disable cpufreq scaling power management in kernel config, what will be the cpu frequency ? minimal or maximal ?

November 14, 2016

Hello,

I would like to know the cpu frequency without using cpufreq. The /proc/cpuinfo gives BogoMIPS 48.00.

Thanks.

October 29, 2016

Hi

I am looking for an image that runs on NanoPi Neo with a kernel above 4.4.x (I want to run docker) and enabled USB support.

You can build your own image to have USB support. You choose dev branch : https://github.com/igorpecovnik/lib/blob/master/README.md

October 25, 2016

A little off topic, sorry. I would like your opinion on what I did with Builroot. If what I have done is correct. Thanks.

Buildroot supports orangepi pc (without ethernet ?).

See https://git.busybox.net/buildroot/tree/board/orangepi/orangepipcand https://git.busybox.net/buildroot/tree/configs/orangepipc_defconfig

In Buildroot, I compiled orangepi-pc with dhcpcd and openssh, and then I copied the image on a SD card.

On the small partition on the sd card, there were three files boot.src, sun8i-h3-orangepi-pc.dtb and zImage. I replaced two of them by those of armbian-dev (sun8i-h3-orange-pi-one.dtb and zImage). This seems to work.

dmesg : dmesg.txt

/var/log/message : message.txt

October 13, 2016

Hello,

Thanks for your excellent distribution!

I have NanoPi NEO + heatsink + box (all official from friendlyarm). I installed Jessie legacy because I need the USB audio output. I installed the mpd package + upmpdcli ( http://www.lesbonscomptes.com/upmpdcli/) + shairport -sync. This SBC is perfect for creating a UPnP audio player and airplay audio player. Here the load during playback of FLAC files

root@nanopineo:~/shairport-sync# armbianmonitor -m
Stop monitoring using [ctrl]-[c]
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU
15:32:27:  912MHz  0.01   2%   0%   1%   0%   0%   0%   49Â°C
15:32:32:  240MHz  0.00   2%   0%   1%   0%   0%   0%   49Â°C
15:32:38:  240MHz  0.00   2%   0%   1%   0%   0%   0%   49Â°C
15:32:43:  240MHz  0.00   2%   0%   1%   0%   0%   0%   49Â°C
15:32:48:  240MHz  0.00   2%   0%   1%   0%   0%   0%   49Â°C
15:32:53:  240MHz  0.00   2%   0%   1%   0%   0%   0%   50Â°C
15:32:59:  240MHz  0.00   2%   0%   1%   0%   0%   0%   49Â°C
15:33:04:  240MHz  0.08   2%   0%   1%   0%   0%   0%   49Â°C
15:33:09:  240MHz  0.08   2%   0%   1%   0%   0%   0%   49Â°C
15:33:14:  240MHz  0.07   2%   0%   1%   0%   0%   0%   49Â°C
15:33:20:  240MHz  0.06   2%   0%   1%   0%   0%   0%   49Â°C
15:33:25:  240MHz  0.06   2%   0%   1%   0%   0%   0%   49Â°C
15:33:30:  240MHz  0.05   2%   0%   1%   0%   0%   0%   49Â°C
15:33:36:  240MHz  0.05   2%   0%   1%   0%   0%   0%   49Â°C
15:33:41:  240MHz  0.05   2%   0%   1%   0%   0%   0%   49Â°C
15:33:46:  912MHz  0.04   2%   0%   1%   0%   0%   0%   49Â°C
15:33:51:  240MHz  0.04   2%   0%   1%   0%   0%   0%   49Â°C
15:33:56:  240MHz  0.04   2%   0%   1%   0%   0%   0%   49Â°C
15:34:02:  240MHz  0.03   2%   0%   1%   0%   0%   0%   49Â°C
15:34:07:  240MHz  0.10   2%   0%   1%   0%   0%   0%   50Â°C
15:34:12:  240MHz  0.09   2%   0%   1%   0%   0%   0%   49Â°C
15:34:18:  240MHz  0.09   2%   0%   1%   0%   0%   0%   49Â°C
15:34:23:  240MHz  0.08   2%   0%   1%   0%   0%   0%   49Â°C
15:34:28:  240MHz  0.07   2%   0%   1%   0%   0%   0%   49Â°C
15:34:33:  240MHz  0.07   2%   0%   1%   0%   0%   0%   49Â°C
15:34:39:  240MHz  0.06   2%   0%   1%   0%   0%   0%   49Â°C
15:34:44:  240MHz  0.06   2%   0%   1%   0%   0%   0%   49Â°C
15:34:49:  240MHz  0.05   2%   0%   1%   0%   0%   0%   49Â°C
15:34:54:  912MHz  0.05   2%   0%   1%   0%   0%   0%   49Â°C
15:35:00:  240MHz  0.04   2%   0%   1%   0%   0%   0%   49Â°C
15:35:05:  240MHz  0.04   2%   0%   1%   0%   0%   0%   50Â°C
15:35:10:  240MHz  0.04   2%   0%   1%   0%   0%   0%   49Â°C
15:35:15:  240MHz  0.03   2%   0%   1%   0%   0%   0%   49Â°C
15:35:21:  240MHz  0.03   2%   0%   1%   0%   0%   0%   49Â°C
15:35:26:  240MHz  0.03   2%   0%   1%   0%   0%   0%   49Â°C
15:35:31:  240MHz  0.03   2%   0%   1%   0%   0%   0%   50Â°C
15:35:37:  240MHz  0.02   2%   0%   1%   0%   0%   0%   49Â°C
15:35:42:  240MHz  0.02   2%   0%   1%   0%   0%   0%   49Â°C
15:35:47:  912MHz  0.09   2%   0%   1%   0%   0%   0%   49Â°C
15:35:52:  240MHz  0.09   2%   0%   1%   0%   0%   0%   49Â°C
15:35:58:  240MHz  0.08   2%   0%   1%   0%   0%   0%   49Â°C
15:36:03:  240MHz  0.07   2%   0%   1%   0%   0%   0%   49Â°C
15:36:08:  240MHz  0.23   2%   0%   1%   0%   0%   0%   49Â°C
15:36:13:  240MHz  0.21   2%   0%   1%   0%   0%   0%   49Â°C
...

kernel 4.6.7, with schedutil cpufreq governor:

root@nanopineo:~# armbianmonitor -m
Stop monitoring using [ctrl]-[c]
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU
20:59:30:  240MHz  0.13   0%   0%   0%   0%   0%   0% 36.7Â°C
20:59:36:  120MHz  0.12   0%   0%   0%   0%   0%   0% 36.8Â°C
20:59:41:  120MHz  0.11   0%   0%   0%   0%   0%   0% 36.9Â°C
20:59:47:  120MHz  0.10   0%   0%   0%   0%   0%   0% 37.1Â°C
20:59:52:  120MHz  0.09   0%   0%   0%   0%   0%   0% 36.7Â°C
20:59:58:  120MHz  0.09   0%   0%   0%   0%   0%   0% 37.1Â°C
21:00:04:  120MHz  0.08   0%   0%   0%   0%   0%   0% 36.8Â°C
21:00:09:  120MHz  0.07   0%   0%   0%   0%   0%   0% 36.9Â°C
21:00:15:  240MHz  0.07   0%   0%   0%   0%   0%   0% 37.1Â°C
21:00:20: 1200MHz  0.06   0%   0%   0%   0%   0%   0% 37.8Â°C
21:00:25: 1200MHz  0.06   0%   0%   0%   0%   0%   0% 37.8Â°C
21:00:30: 1200MHz  0.05   0%   0%   0%   0%   0%   0% 38.5Â°C
21:00:35: 1200MHz  0.13   0%   0%   0%   0%   0%   0% 38.5Â°C
21:00:40: 1200MHz  0.20   0%   0%   0%   0%   0%   0% 38.5Â°C
21:00:45: 1200MHz  0.18   0%   0%   0%   0%   0%   0% 38.5Â°C
21:00:50: 1200MHz  0.15   0%   0%   0%   0%   0%   0% 38.8Â°C
21:00:56: 1200MHz  0.14   0%   0%   0%   0%   0%   0% 39.1Â°C
21:01:01:  120MHz  0.13   0%   0%   0%   0%   0%   0% 38.6Â°C
21:01:06: 1200MHz  0.12   0%   0%   0%   0%   0%   0% 38.6Â°C
21:01:11: 1200MHz  0.11   0%   0%   0%   0%   0%   0% 38.8Â°C
21:01:16: 1200MHz  0.18   0%   0%   0%   0%   0%   0% 38.9Â°C
21:01:21: 1200MHz  0.17   0%   0%   0%   0%   0%   0% 38.9Â°C
21:01:27: 1200MHz  0.15   0%   0%   0%   0%   0%   0% 38.3Â°C
21:01:32: 1200MHz  0.14   0%   0%   0%   0%   0%   0% 38.9Â°C
21:01:37: 1200MHz  0.13   0%   0%   0%   0%   0%   0% 38.8Â°C
21:01:42:  240MHz  0.12   0%   0%   0%   0%   0%   0% 38.8Â°C
21:01:47: 1200MHz  0.11   0%   0%   0%   0%   0%   0% 38.8Â°C
21:01:52: 1200MHz  0.10   0%   0%   0%   0%   0%   0% 38.6Â°C
21:01:57:  120MHz  0.09   0%   0%   0%   0%   0%   0% 39.0Â°C
21:02:03: 1200MHz  0.08   0%   0%   0%   0%   0%   0% 38.9Â°C
21:02:08: 1200MHz  0.08   0%   0%   0%   0%   0%   0% 39.2Â°C
21:02:13: 1200MHz  0.07   0%   0%   0%   0%   0%   0% 39.1Â°C
21:02:18: 1200MHz  0.06   0%   0%   0%   0%   0%   0% 38.8Â°C
21:02:23: 1200MHz  0.06   0%   0%   0%   0%   0%   0% 38.8Â°C
21:02:28: 1200MHz  0.05   0%   0%   0%   0%   0%   0% 39.1Â°C
21:02:33: 1200MHz  0.05   0%   0%   0%   0%   0%   0% 39.4Â°C
21:02:38: 1200MHz  0.05   0%   0%   0%   0%   0%   0% 39.4Â°C
21:02:43: 1200MHz  0.04   0%   0%   0%   0%   0%   0% 39.5Â°C
21:02:49: 1200MHz  0.04   0%   0%   0%   0%   0%   0% 39.2Â°C
21:02:54: 1200MHz  0.03   0%   0%   0%   0%   0%   0% 39.1Â°C
21:02:59: 1200MHz  0.03   0%   0%   0%   0%   0%   0% 39.2Â°C
21:03:04: 1200MHz  0.03   0%   0%   0%   0%   0%   0% 39.5Â°C
21:03:09: 1200MHz  0.03   0%   0%   0%   0%   0%   0% 39.2Â°C
21:03:14: 1200MHz  0.02   0%   0%   0%   0%   0%   0% 39.4Â°C
21:03:19:  120MHz  0.02   0%   0%   0%   0%   0%   0% 39.1Â°C
21:03:25: 1200MHz  0.02   0%   0%   0%   0%   0%   0% 38.6Â°C
21:03:30: 1200MHz  0.02   0%   0%   0%   0%   0%   0% 39.4Â°C
21:03:35:  816MHz  0.02   0%   0%   0%   0%   0%   0% 39.2Â°C
21:03:40: 1200MHz  0.02   0%   0%   0%   0%   0%   0% 39.1Â°C
21:03:45: 1200MHz  0.01   0%   0%   0%   0%   0%   0% 39.4Â°C
21:03:50: 1200MHz  0.01   0%   0%   0%   0%   0%   0% 39.6Â°C
21:03:55: 1200MHz  0.01   0%   0%   0%   0%   0%   0% 39.6Â°C
21:04:00: 1200MHz  0.01   0%   0%   0%   0%   0%   0% 39.5Â°C
21:04:05: 1200MHz  0.01   0%   0%   0%   0%   0%   0% 39.5Â°C
21:04:10: 1200MHz  0.01   0%   0%   0%   0%   0%   0% 39.5Â°C
21:04:15: 1200MHz  0.01   0%   0%   0%   0%   0%   0% 39.1Â°C
21:04:21: 1200MHz  0.01   0%   0%   0%   0%   0%   0% 39.7Â°C
21:04:26: 1200MHz  0.01   0%   0%   0%   0%   0%   0% 39.7Â°C
21:04:31: 1200MHz  0.00   0%   0%   0%   0%   0%   0% 39.7Â°C
21:04:36:  816MHz  0.00   0%   0%   0%   0%   0%   0% 39.9Â°C
21:04:41: 1200MHz  0.08   0%   0%   0%   0%   0%   0% 39.9Â°C
21:04:46: 1200MHz  0.07   0%   0%   0%   0%   0%   0% 39.5Â°C
21:04:51:  120MHz  0.07   0%   0%   0%   0%   0%   0% 39.5Â°C
21:04:57: 1200MHz  0.06   0%   0%   0%   0%   0%   0% 39.5Â°C
21:05:02: 1200MHz  0.06   0%   0%   0%   0%   0%   0% 40.0Â°C
21:05:07: 1200MHz  0.05   0%   0%   0%   0%   0%   0% 39.4Â°C
21:05:12: 1200MHz  0.05   0%   0%   0%   0%   0%   0% 39.7Â°C

root@nanopineo:~# cat  /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
120000 8016033
240000 12243
312000 2445
480000 6209
624000 1322
816000 1738
1008000 432
1200000 978525


root@nanopineo:~# cpufreq-info 
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 244 us.
  hardware limits: 120 MHz - 1.20 GHz
  available frequency steps: 120 MHz, 240 MHz, 312 MHz, 480 MHz, 624 MHz, 816 MHz, 1.01 GHz, 1.20 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 120 MHz and 1.20 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 1.20 GHz (asserted by call to hardware).
  cpufreq stats: 120 MHz:88.88%, 240 MHz:0.14%, 312 MHz:0.03%, 480 MHz:0.07%, 624 MHz:0.01%, 816 MHz:0.02%, 1.01 GHz:0.00%, 1.20 GHz:10.85%  (31937)
analyzing CPU 1:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 244 us.
  hardware limits: 120 MHz - 1.20 GHz
  available frequency steps: 120 MHz, 240 MHz, 312 MHz, 480 MHz, 624 MHz, 816 MHz, 1.01 GHz, 1.20 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 120 MHz and 1.20 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 1.20 GHz (asserted by call to hardware).
  cpufreq stats: 120 MHz:88.88%, 240 MHz:0.14%, 312 MHz:0.03%, 480 MHz:0.07%, 624 MHz:0.01%, 816 MHz:0.02%, 1.01 GHz:0.00%, 1.20 GHz:10.85%  (31937)
analyzing CPU 2:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 244 us.
  hardware limits: 120 MHz - 1.20 GHz
  available frequency steps: 120 MHz, 240 MHz, 312 MHz, 480 MHz, 624 MHz, 816 MHz, 1.01 GHz, 1.20 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 120 MHz and 1.20 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 1.20 GHz (asserted by call to hardware).
  cpufreq stats: 120 MHz:88.88%, 240 MHz:0.14%, 312 MHz:0.03%, 480 MHz:0.07%, 624 MHz:0.01%, 816 MHz:0.02%, 1.01 GHz:0.00%, 1.20 GHz:10.85%  (31937)
analyzing CPU 3:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 244 us.
  hardware limits: 120 MHz - 1.20 GHz
  available frequency steps: 120 MHz, 240 MHz, 312 MHz, 480 MHz, 624 MHz, 816 MHz, 1.01 GHz, 1.20 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 120 MHz and 1.20 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 1.20 GHz (asserted by call to hardware).
  cpufreq stats: 120 MHz:88.88%, 240 MHz:0.14%, 312 MHz:0.03%, 480 MHz:0.07%, 624 MHz:0.01%, 816 MHz:0.02%, 1.01 GHz:0.00%, 1.20 GHz:10.85%  (31937)
root@nanopineo:~# cat  /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

September 17, 2016

The V1 (CPU G3088BA 63R3)

Before

5.12v

.26A

During

5.12V

.45A - .48A

After

5.13V

.31A

How did you get these informations ? CPU G3088BA 63R3 ....

September 4, 2016

Hi,

Is there an application to measure power consumption ?

Thanks.

September 1, 2016

Hello,
Thanks for your excellent distribution!
I have NanoPi NEO + heatsink + box (all official from friendlyarm). I installed Jessie legacy because I need the USB audio output. I installed the mpd package + upmpdcli ( http://www.lesbonscomptes.com/upmpdcli/) + shairport -sync. This SBC is perfect for creating a UPnP audio player and airplay audio player. Here the load during playback of FLAC files

root@nanopineo:~/shairport-sync# armbianmonitor -m
Stop monitoring using [ctrl]-[c]
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU
15:32:27:  912MHz  0.01   2%   0%   1%   0%   0%   0%   49Â°C
15:32:32:  240MHz  0.00   2%   0%   1%   0%   0%   0%   49Â°C
15:32:38:  240MHz  0.00   2%   0%   1%   0%   0%   0%   49Â°C
15:32:43:  240MHz  0.00   2%   0%   1%   0%   0%   0%   49Â°C
15:32:48:  240MHz  0.00   2%   0%   1%   0%   0%   0%   49Â°C
15:32:53:  240MHz  0.00   2%   0%   1%   0%   0%   0%   50Â°C
15:32:59:  240MHz  0.00   2%   0%   1%   0%   0%   0%   49Â°C
15:33:04:  240MHz  0.08   2%   0%   1%   0%   0%   0%   49Â°C
15:33:09:  240MHz  0.08   2%   0%   1%   0%   0%   0%   49Â°C
15:33:14:  240MHz  0.07   2%   0%   1%   0%   0%   0%   49Â°C
15:33:20:  240MHz  0.06   2%   0%   1%   0%   0%   0%   49Â°C
15:33:25:  240MHz  0.06   2%   0%   1%   0%   0%   0%   49Â°C
15:33:30:  240MHz  0.05   2%   0%   1%   0%   0%   0%   49Â°C
15:33:36:  240MHz  0.05   2%   0%   1%   0%   0%   0%   49Â°C
15:33:41:  240MHz  0.05   2%   0%   1%   0%   0%   0%   49Â°C
15:33:46:  912MHz  0.04   2%   0%   1%   0%   0%   0%   49Â°C
15:33:51:  240MHz  0.04   2%   0%   1%   0%   0%   0%   49Â°C
15:33:56:  240MHz  0.04   2%   0%   1%   0%   0%   0%   49Â°C
15:34:02:  240MHz  0.03   2%   0%   1%   0%   0%   0%   49Â°C
15:34:07:  240MHz  0.10   2%   0%   1%   0%   0%   0%   50Â°C
15:34:12:  240MHz  0.09   2%   0%   1%   0%   0%   0%   49Â°C
15:34:18:  240MHz  0.09   2%   0%   1%   0%   0%   0%   49Â°C
15:34:23:  240MHz  0.08   2%   0%   1%   0%   0%   0%   49Â°C
15:34:28:  240MHz  0.07   2%   0%   1%   0%   0%   0%   49Â°C
15:34:33:  240MHz  0.07   2%   0%   1%   0%   0%   0%   49Â°C
15:34:39:  240MHz  0.06   2%   0%   1%   0%   0%   0%   49Â°C
15:34:44:  240MHz  0.06   2%   0%   1%   0%   0%   0%   49Â°C
15:34:49:  240MHz  0.05   2%   0%   1%   0%   0%   0%   49Â°C
15:34:54:  912MHz  0.05   2%   0%   1%   0%   0%   0%   49Â°C
15:35:00:  240MHz  0.04   2%   0%   1%   0%   0%   0%   49Â°C
15:35:05:  240MHz  0.04   2%   0%   1%   0%   0%   0%   50Â°C
15:35:10:  240MHz  0.04   2%   0%   1%   0%   0%   0%   49Â°C
15:35:15:  240MHz  0.03   2%   0%   1%   0%   0%   0%   49Â°C
15:35:21:  240MHz  0.03   2%   0%   1%   0%   0%   0%   49Â°C
15:35:26:  240MHz  0.03   2%   0%   1%   0%   0%   0%   49Â°C
15:35:31:  240MHz  0.03   2%   0%   1%   0%   0%   0%   50Â°C
15:35:37:  240MHz  0.02   2%   0%   1%   0%   0%   0%   49Â°C
15:35:42:  240MHz  0.02   2%   0%   1%   0%   0%   0%   49Â°C
15:35:47:  912MHz  0.09   2%   0%   1%   0%   0%   0%   49Â°C
15:35:52:  240MHz  0.09   2%   0%   1%   0%   0%   0%   49Â°C
15:35:58:  240MHz  0.08   2%   0%   1%   0%   0%   0%   49Â°C
15:36:03:  240MHz  0.07   2%   0%   1%   0%   0%   0%   49Â°C
15:36:08:  240MHz  0.23   2%   0%   1%   0%   0%   0%   49Â°C
15:36:13:  240MHz  0.21   2%   0%   1%   0%   0%   0%   49Â°C
...

Sign In

Forums

Store

Crowdfunding

Applications

Events

Raffles

Community Map

Posts posted by bzfrp

Important Information