NanoPI NEO / AIR

Christos · October 1, 2016

Ok,

A new build has been done Ubuntu 16.04 with 4.7.6, it looks working.

I answered the default answer to all the build (NEW) questions.

C:\Documents and Settings\Christos>ssh christos@192.168.1.9
christos@192.168.1.9's password:
setsockopt IP_TOS 16: Invalid argument:
 _   _                   ____  _   _   _
| \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___
|  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \
| |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
|_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/


Welcome to ARMBIAN Ubuntu 16.04.1 LTS 4.7.6-sun8i
System load:   0.46             Up time:       3 min
Memory usage:  4 % of 495Mb     IP:            192.168.1.9
CPU temp:      31Î’Â°C
Usage of /:    8% of 15G

Last login: Sat Oct  1 08:41:38 2016 from 192.168.1.6

christos@nanopineo:~$

As tk said, the USB obviously needs modification as the connector in NEO is not enabled in this build.

Lets see now what can be done with dtc..

Christos · October 1, 2016

Ok,

Did some 'cheating' here and instead of going into device tree and change the USB1 to USB3

(I admit I got quite a few gaps still in the dtc/btb/bts thing..)

I just connected the USB1 from the pinheader expansion on NEO and now the wifi device is visible

C:\Christos>ssh christos@192.168.1.9
christos@192.168.1.9's password:
setsockopt IP_TOS 16: Invalid argument:
 _   _                   ____  _   _   _
| \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___
|  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \
| |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
|_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/


Welcome to ARMBIAN Ubuntu 16.04.1 LTS 4.7.6-sun8i
System load:   0.32             Up time:       27 sec
Memory usage:  4 % of 495Mb     IP:            192.168.1.9
CPU temp:      23Î’Â°C
Usage of /:    8% of 15G

Last login: Sat Oct  1 12:38:33 2016 from 192.168.1.6

christos@nanopineo:~$ lsmod      (Before plug-in of WiFi donlge)
Module                  Size  Used by
sun8i_ths               3668  0
cpufreq_dt              3887  0
uio_pdrv_genirq         3591  0
uio                     8953  1 uio_pdrv_genirq
thermal_sys            48267  2 sun8i_ths,cpufreq_dt
christos@nanopineo:~$ lsmod      (After plug-in of WiFi donlge)
Module                  Size  Used by
rtl8192cu              60341  0
rtl_usb                 9530  1 rtl8192cu
rtl8192c_common        40018  1 rtl8192cu
rtlwifi                58627  3 rtl_usb,rtl8192c_common,rtl8192cu
mac80211              396612  3 rtl_usb,rtlwifi,rtl8192cu
cfg80211              237274  2 mac80211,rtlwifi
rfkill                 12189  2 cfg80211
sun8i_ths               3668  0
cpufreq_dt              3887  0
uio_pdrv_genirq         3591  0
uio                     8953  1 uio_pdrv_genirq
thermal_sys            48267  2 sun8i_ths,cpufreq_dt
christos@nanopineo:~$ sudo ifconfig -a
[sudo] password for christos:
eth0      Link encap:Ethernet  HWaddr 02:20:d2:9c:0b:2b
          inet addr:192.168.1.9  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: 2a02:582:d2e:1100:20:d2ff:fe9c:b2b/64 Scope:Global
          inet6 addr: fe80::20:d2ff:fe9c:b2b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:254 errors:0 dropped:0 overruns:0 frame:0
          TX packets:220 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:28086 (28.0 KB)  TX bytes:28700 (28.7 KB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:49 (49.0   TX bytes:49 (49.0 

wlxe84e0626ba70 Link encap:Ethernet  HWaddr e8:4e:06:26:ba:70
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0   TX bytes:0 (0.0 

christos@nanopineo:~$

There is a "wlxe84e0626ba70" wifi device now, but I could get some help here since I know how to set it up in Debian but I'm not so good in Ubuntu, so any hint on how to enable the wifi in this situation is welcome!

so, how can I set this up? is there any how-to to read?

Christos

P.S.

Here is attached the little patchwork

Christos · October 2, 2016

Ok,

Finally I did a Debian latest kernel build and now it works just fine with WiFi

C:\Christos>ssh christos@192.168.1.131
christos@192.168.1.131's password:
setsockopt IP_TOS 16: Invalid argument:
 _   _                   ____  _   _   _
| \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___
|  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \
| |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
|_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/


Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 4.7.6-sun8i
System load:   0.94             Up time:       30 sec
Memory usage:  9 % of 495Mb     IP:            192.168.1.131
CPU temp:      33Î’Â°C
Usage of /:    8% of 15G

Last login: Sun Oct  2 09:24:13 2016 from 192.168.1.6

christos@nanopineo:~$ su root
Password:
root@nanopineo:/home/christos# iwconfig
wlan0     IEEE 802.11  ESSID:"OTEf0b338"
          Mode:Managed  Frequency:2.442 GHz  Access Point: A4:7E:39:F0:B3:38
          Bit Rate=150 Mb/s   Tx-Power=20 dBm
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=64/70  Signal level=-46 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:7   Missed beacon:0

lo        no wireless extensions.

eth0      no wireless extensions.

root@nanopineo:/home/christos# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 02:20:d2:9c:0b:2b
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0   TX bytes:0 (0.0 

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:1104 (1.0 KiB)  TX bytes:1104 (1.0 KiB)

wlan0     Link encap:Ethernet  HWaddr e8:4e:06:26:ba:70
          inet addr:192.168.1.131  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::ea4e:6ff:fe26:ba70/64 Scope:Link
          inet6 addr: 2a02:582:d2e:1100:ea4e:6ff:fe26:ba70/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:150 errors:0 dropped:0 overruns:0 frame:0
          TX packets:151 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15920 (15.5 KiB)  TX bytes:26776 (26.1 KiB)

root@nanopineo:/home/christos#
root@nanopineo:/home/christos# ping www.ubuntu.com -c 3
PING www.ubuntu.com (91.189.90.59) 56(84) bytes of data.
64 bytes from www-ubuntu-com.jujube.canonical.com (91.189.90.59): icmp_seq=1 ttl
=52 time=71.5 ms
64 bytes from www-ubuntu-com.jujube.canonical.com (91.189.90.59): icmp_seq=2 ttl
=52 time=74.7 ms
64 bytes from www-ubuntu-com.jujube.canonical.com (91.189.90.59): icmp_seq=3 ttl
=52 time=72.7 ms

--- www.ubuntu.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 71.594/73.046/74.773/1.312 ms
root@nanopineo:/home/christos#

This build, Armbian 5.21, Debian jessie, kernel 4.7.6, has been build with armbian's build system choosing

choose an option -> "Full OS image for writing to SD card"

choose a board -> "nanopineo"

choose a kernel -> "dev"

choose a release -> "jessie"

choose image type -> "Image with console interface"

and all (NEW) prompts were answered as per their default value

Used with the USB1 exported pins via the DIY board and connector shown above (until of course a proper USB3 image comes)

Modifications to wifi related files are as described here -> http://forum.armbian.com/index.php/topic/1237-tutorial-opi-one-wireless-success/.

Hope that will be useful to anyone interested.

Christos

Christos · October 2, 2016

A question to the Armbian gurus here for the new armbian builds with 4.x kernel.

Do these builds take into consideration the DDR frequency for the NanoPi-NEO RAM? or is that too from the OPi board and thus poses a risk factor for us with NEOs?

Should we avoid making armbian builds with kernel 4.x on NEO?

tkaiser · October 2, 2016

Do these builds take into consideration the DDR frequency for the NanoPi-NEO RAM?

They do. This is done entirely in u-boot and mainline/vanilla kernel doesn't touch these settings. So unlike legacy kernel where you can control DRAM clockspeed from userspace (h3consumption tool) with vanilla kernel you stay with the fixed value set in u-boot.

BTW: I'm currently testing 'add_usb_ports_to_small_h3-boards.patch', if this succeeds I will commit it within the next hour. As a result all USB ports on the small H3 boards should be useable without further tweaks.

Edit: Tested, works and commited: https://github.com/igorpecovnik/lib/commit/14fa719934d38f579eb0ded346f448b6b0fda6bc

Christos · October 2, 2016

Good!

Thanks Thomas,

Fresh build, Armbian 5.21, Ubuntu 16.04.1 LTS, kernel 4.7.6

C:\Christos>ssh christos@192.168.1.131
christos@192.168.1.131's password:
setsockopt IP_TOS 16: Invalid argument:
 _   _                   ____  _   _   _
| \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___
|  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \
| |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
|_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/


Welcome to ARMBIAN Ubuntu 16.04.1 LTS 4.7.6-sun8i
System load:   0.36             Up time:       1 min
Memory usage:  5 % of 495Mb     IP:            192.168.1.131
CPU temp:      35Î’Â°C
Usage of /:    8% of 15G

Last login: Sun Oct  2 20:08:54 2016 from 192.168.1.6

christos@nanopineo:~$ sudo ifconfig -a
[sudo] password for christos:
eth0      Link encap:Ethernet  HWaddr 02:20:d2:9c:0b:2b
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0   TX bytes:0 (0.0 

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:49 (49.0   TX bytes:49 (49.0 

wlxe84e0626ba70 Link encap:Ethernet  HWaddr e8:4e:06:26:ba:70
          inet addr:192.168.1.131  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::ea4e:6ff:fe26:ba70/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:139 errors:0 dropped:0 overruns:0 frame:0
          TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16333 (16.3 KB)  TX bytes:20986 (20.9 KB)

christos@nanopineo:~$ ping www.ubuntu.com -c 3
PING www.ubuntu.com (91.189.89.118) 56(84) bytes of data.
64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.118): icmp_seq=1 ttl=
52 time=70.2 ms
64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.118): icmp_seq=2 ttl=
52 time=69.0 ms
64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.118): icmp_seq=3 ttl=
52 time=67.9 ms

--- www.ubuntu.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 67.914/69.075/70.291/1.017 ms
christos@nanopineo:~$

works like a charm, board USB connector enabled, WiFi up and running.

Thanks again

Christos

P.S.

The only strange thing is the wifi device with weird name wlxe84e0626ba70..

martinayotte · October 3, 2016

The only strange thing is the wifi device with weird name wlxe84e0626ba70

You can force older naming scheme by adding rule in /etc/udev/rules.d

Christos · October 3, 2016

You can force older naming scheme by adding rule in /etc/udev/rules.d

..if I only knew :lol: how to do that.

And as they say, if its not broken, dont try to fix it, I'll live with it.

It works just fine as it is, it just has a ..strong character of its own!!

Thanks for the hint though, appreciated and I might dive into udev rules someday to see how it can be done.

Christos

martinayotte · October 3, 2016

There are some explanations there :

http://forum.armbian.com/index.php/topic/2173-can-not-build-wireless-driver/#entry16630

In fact, this new naming behaviour isn't new, it is the new naming convention that Systemd had introduced awhile ago :

https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

http://askubuntu.com/questions/689070/network-interface-name-changes-after-update-to-15-10-udev-changes

http://askubuntu.com/questions/628217/use-of-predictable-network-interface-names-with-alternate-kernels

Adam Anderson · October 7, 2016

Hi All,

I have a Nanopi Neo:

Welcome to ARMBIAN Ubuntu 16.04.1 LTS 3.4.112-sun8i
System load:   0.24               Up time:       2 days
Memory usage: 5 % of 494Mb     IP:            192.168.0.241
CPU temp:      42Â°C
Usage of /:    28% of 7.2G

I've installed Linphone on it but it's complaining:

adam@nanopineo:~$ linphone
linphone: error while loading shared libraries: libavcodec-ffmpeg.so.56: cannot open shared object file: No such file or directory

I've got this installed
/usr/lib/arm-linux-gnueabihf/libavcodec-ffmpeg.so.57.48.101
/usr/lib/arm-linux-gnueabihf/libavcodec-ffmpeg.so.57

I've tried adding an alternative linphone ppa and updating and installing linphone, but the problem persists. Google isn't helping me much unfortunately. Any tips or pointers?

zador.blood.stained · October 7, 2016

I've got this installed

/usr/lib/arm-linux-gnueabihf/libavcodec-ffmpeg.so.57.48.101

/usr/lib/arm-linux-gnueabihf/libavcodec-ffmpeg.so.57

I've tried adding an alternative linphone ppa and updating and installing linphone, but the problem persists. Google isn't helping me much unfortunately. Any tips or pointers?

This is an issue with 5.20 images, this will be fixed with new release.

Pieter · October 7, 2016

linphone: error while loading shared libraries: libavcodec-ffmpeg.so.56: cannot open shared object file: No such file or directory

I've got this installed

/usr/lib/arm-linux-gnueabihf/libavcodec-ffmpeg.so.57.48.101

/usr/lib/arm-linux-gnueabihf/libavcodec-ffmpeg.so.57

You are probably better of waiting for the fix zador.blood.stained is talking about but...

What you could try in the mean time is by creating a symbolic link as libavcodec-ffmpeg.so.56 to libavcodec-ffmpeg.so.57, sometimes that works :-)

cd /usr/lib/arm-linux-gnueabihf/
ln -s libavcodec-ffmpeg.so.57 libavcodec-ffmpeg.so.56

No guaranties, that it will work :-)

Carlos · October 10, 2016

Hi

Linux imbecile here.

Do any of the Armbian distros have the USB port operational?

I want to use my Neo as a NAA device for HQPlayer. I don't know if I have not installed HQPlayer NAA correctly onto my Neo or if the NAA is not seeing my DAC because the USB port is disabled.

I am currently using ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.112-sun8i.

Any help greatly appreciated.

Regards

Carl

Christos · October 10, 2016

Hi

Linux imbecile here.

Do any of the Armbian distros have the USB port operational?

I want to use my Neo as a NAA device for HQPlayer. I don't know if I have not installed HQPlayer NAA correctly onto my Neo or if the NAA is not seeing my DAC because the USB port is disabled.

I am currently using ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.112-sun8i.

Any help greatly appreciated.

Regards

Carl

Hi Carl,

Yes, if you build yourself a new image now, either legacy or vanilla, it will have USB working ok.

See above posts 213 & 216

Christos

tkaiser · October 10, 2016

I am currently using ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.112-sun8i.

In this image all 3 USB host ports are defined as active: https://github.com/igorpecovnik/lib/blob/master/config/fex/nanopineo.fex#L523-L551

Check output of lsusb (-v) and dmesg after connecting USB devices and if that does not help get back to us with the output from 'sudo armbianmonitor -u'.

Carlos · October 10, 2016

Thanks Christos and Thomas

Up and running with my USB Dac

The problem was that HQPlayer NAA would not install with the Jessie build because it requires libstdc++6 greater than 5.1

The Xenial build allowed HQPlayer NAA to be installed properly

Thanks for your help.

XTL · October 12, 2016

I finally got one of these as well. I'll see how long it takes for me to find time to get a card, a console, and bootup.

Slawek · October 13, 2016

Hi,

I just started my quest with NanoPi NEO (rev 1.1). I'm quite old guy ;-) with my roots in Pleistocene Delphi time so I would like to program it using Lazarus/Pascal.

On Raspberry Pi 2/3 I can install and access Lazarus without any problem using Putty/Xming team (on standard Rasbian).

I'm using the popular guide from here: http://otapi.com/2015/02/10/raspberry-pi-2-freepascal-lazarus-and-delphi/

but I have small problems with my NanoPi NEO.

with FriendlyARM default image I can access NanoPi with Putty/Xming (after installing some g??? application for example gedit) But I can't compile Lazarus IDE.
with Armbian (every version dedicated to NanoPi NEO) I can install Lazarus without any problems, but I cant access it via X11 forwarding Putty/Xming. I get error: Unable to init server: Could not connect: Connection refused (galculator:2743): Gtk-WARNING **: cannot open display"

probably the problem is with the X11 authorisation but I have little experience.

Could you please give me some idea what I should reconfigure to gain X11 access.

Tanks in advance.

Christos · October 13, 2016

Hi Slawek,

There are no old guys, just some others are too young!! (I myself am a '65 model..)

Not sure if that applies to you, but the two images in the armbian nanopineo specific download page are headless (no GUI) so they might lack some of the X11 features you require.

Take a shot and try to build one for yourself via the https://github.com/igorpecovnik/lib in the page there are instructions for a custom build so you might have luck building a desktop build instead of a console/terminal only.

Christos

tkaiser · October 13, 2016

I just started my quest with NanoPi NEO (rev 1.1).

Christos is right, NEO images are headless (no HDMI, no X11 -- maybe too shortsighted). You could either install X11 on an existing image or choose the Desktop image for Orange Pi One and then execute there just 'h3consumption -g off -d 408' (on PCB rev 1.1 it should be save to allow 1200 MHz cpufreq -- on our NEO images this is limited to 912 MHz currently)

Slawek · October 13, 2016

Thanks,

I will try both, but on Monday, an will let you know the results. Now I'm preparing myself and my crew for last sailing trip this season :D

Have nice weekend.

Slawek

bzfrp · 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

trewq · October 15, 2016

Ok, so, I went a little overboard with this but here is my current NanoPi Neo setup. They are all running the latest Ubuntu build, if anyone wants the output of anything let me know. 20 units in total.

webbbn · October 15, 2016

Got a couple of NanoPi NEO Airs today. Anyone tried Armbian on them yet? I imagine the standard NEO image will work, but how hard will it be to install it onto the internal flash?

tkaiser · October 15, 2016

Anyone tried Armbian on them yet?

Nope, but we added support for AIR based on available information recently and already built test images (more or less by accident):

Unless you are able to attach a serial console to the 4-pin header it's useless to even try them out. Two questions from our side:

is the 4-pin header to provide power and attach a serial console populated or not?
if the eMMC pre-flashed?

Please get back to us with this information first, we will then update the NanoPi Air thread and might ask potential Air users a few questions. Thanks!

tkaiser · October 15, 2016

kernel 4.6.7, with schedutil cpufreq governor:

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

Ok, so you modified /etc/defaults/cpufrequtils to 'activate' all available dvfs operating points. In fact your use case implies 'almost idle all the time' so it doesn't make that much of a difference at all.

It only gets interesting when throttling starts to jump in since then I observed that the new ths settings are not optimal (eg. constantly jumping between 816 MHz and 1200 MHz and not using the 1008 MHz in between which leads to lower performance under full load with vanilla kernel compared to legacy currently).

With @trewq's 20 node cluster I would've already started to tweak settings. 20 NEO running in identical conditions would be great to test through a bunch of different DT settings in less time. BTW: I believe I adopted installation of RPi-Monitor also for vanilla images already. Do you get reasonable output after installation (sudo armbianmonitor -r)?

scargill · October 15, 2016

This is a rather interesting board isn't it? H3, GPIO, 0.5GB memory.

http://www.cnx-software.com/2016/07/07/smaller-than-raspberry-pi-zero-meet-nanopi-neo-arm-linux-development-board/

Would it be possible to run this on Armbian?

Already have two of them not only running Armbian - but also a host of other stuff using my script. ... details here - script here. However, very little joy with WIFI - it works with a fairly standard WIFI USB plug but range is AWFUL which I can only put down to the driver or similar.... on wired ethernet however - works a treat. http://tech.scargill.net/the-friendlyarm-nanopi-neo/

tkaiser · October 15, 2016

However, very little joy with WIFI - it works with a fairly standard WIFI USB plug but range is AWFUL which

is the wrong approach anyway. First choose the distro, then choose the device -- that's how Armbian is supposed to work. This is a NEO with a TP-Link TL-WN823N 2.4GHz dongle in an area where 2.4 GHz band is simply dead (+60 networks in the meantime):

root@nanopineo:~# lsusb 
Bus 001 Device 004: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter

And this is what this thingie 'sees':

root@nanopineo:~# nmcli dev wifi list

* SSID MODE CHAN RATE SIGNAL BARS SECURITY

EasyBox-116D28 Infra 9 16 Mbit/s 75 â–‚â–„â–†_ WPA1 WPA2

Snort-Honeynet Infra 13 2 Mbit/s 60 â–‚â–„â–†_ WPA2

-- Infra 6 16 Mbit/s 57 â–‚â–„â–†_ WPA2

FRITZ!Box Fon WLAN 7360 Infra 1 44 Mbit/s 49 â–‚â–„__ WPA1 WPA2

DISTORTEDPEOPLE Infra 9 44 Mbit/s 47 â–‚â–„__ WPA1 WPA2

Wolf 7360 Infra 1 16 Mbit/s 45 â–‚â–„__ WPA1 WPA2

UBNT2 Infra 3 54 Mbit/s 45 â–‚â–„__

EasyBox-290502 Infra 1 44 Mbit/s 44 â–‚â–„__ WPA1 WPA2

FRITZ!Box 7490 Infra 1 44 Mbit/s 44 â–‚â–„__ WPA2

EasyBox-188632 Infra 10 44 Mbit/s 44 â–‚â–„__ WPA1 WPA2

DISTORTEDPEOPLE_EXT Infra 9 16 Mbit/s 39 â–‚â–„__ WPA1 WPA2

Wonder Woman Infra 1 44 Mbit/s 30 â–‚___ WPA1 WPA2

WLAN-341381 Infra 1 16 Mbit/s 30 â–‚___ WPA2

Karen_Range Extender Infra 5 44 Mbit/s 30 â–‚___ WPA1 WPA2

Eichkatzenkind Infra 5 44 Mbit/s 30 â–‚___ WPA2

WLAN-ABD446 Infra 10 16 Mbit/s 30 â–‚___ WPA2

WLAN-A29657 Infra 1 16 Mbit/s 29 â–‚___ WPA2

Brain Exit = Brexit Infra 7 44 Mbit/s 29 â–‚___ WPA1 WPA2

See the signal strength? Now switching over to Orange Pi Lite with onboard 8189FTV (also RealTek, also cheap crap but... different). Same position, crappy mini antenna connected, device being at exactly the same position.

root@orangepilite:~# nmcli dev wifi list

* SSID MODE CHAN RATE SIGNAL BARS SECURITY

5c618d Infra 6 16 Mbit/s 100 â–‚â–„â–†â–ˆ WPA1 WPA2

FRITZ!Box 7490 Infra 6 16 Mbit/s 100 â–‚â–„â–†â–ˆ WPA2

EasyBox-116D28 Infra 9 16 Mbit/s 100 â–‚â–„â–†â–ˆ WPA1 WPA2

Snort-Honeynet Infra 13 2 Mbit/s 100 â–‚â–„â–†â–ˆ WPA2

DISTORTEDPEOPLE Infra 9 44 Mbit/s 72 â–‚â–„â–†_ WPA1 WPA2

WLAN-3C3379 Infra 11 16 Mbit/s 68 â–‚â–„â–†_ WPA2

WLAN-341381 Infra 1 16 Mbit/s 64 â–‚â–„â–†_ WPA2

Wonder Woman Infra 1 44 Mbit/s 62 â–‚â–„â–†_ WPA1 WPA2

-- Infra 6 16 Mbit/s 62 â–‚â–„â–†_ WPA2

FRITZ!Box 6490 Cable Infra 11 16 Mbit/s 62 â–‚â–„â–†_ WPA2

FRITZ!Box Fon WLAN 7360 Infra 1 44 Mbit/s 60 â–‚â–„â–†_ WPA1 WPA2

UBNT2 Infra 3 54 Mbit/s 60 â–‚â–„â–†_

EasyBox-290502 Infra 1 44 Mbit/s 58 â–‚â–„â–†_ WPA1 WPA2

WLAN-A29657 Infra 1 16 Mbit/s 58 â–‚â–„â–†_ WPA2

Horst Infra 3 16 Mbit/s 58 â–‚â–„â–†_ WPA1 WPA2

Karen_Range Extender Infra 5 44 Mbit/s 58 â–‚â–„â–†_ WPA1 WPA2

VC-WLAN Gastzugang Infra 6 16 Mbit/s 58 â–‚â–„â–†_ WPA1 WPA2

EasyBox-188632 Infra 10 44 Mbit/s 58 â–‚â–„â–†_ WPA1 WPA2

Hasenhirn01 Infra 11 16 Mbit/s 58 â–‚â–„â–†_ WPA2

FRITZ!Box 7490 Infra 1 44 Mbit/s 56 â–‚â–„â–†_ WPA2

FRITZ!Box Fon WLAN 7360 Infra 1 44 Mbit/s 56 â–‚â–„â–†_ WPA1 WPA2

Eichkatzenkind Infra 5 44 Mbit/s 56 â–‚â–„â–†_ WPA2

FRITZ!Box Fon WLAN 7113 Infra 6 54 Mbit/s 56 â–‚â–„â–†_ WPA1 WPA2

VC on Air Infra 6 16 Mbit/s 56 â–‚â–„â–†_ WPA1 WPA2

11-Dominik Infra 11 44 Mbit/s 56 â–‚â–„â–†_ WPA1 WPA2

FRITZ!Box Fon WLAN 7360 Infra 1 44 Mbit/s 48 â–‚â–„__ WPA1 WPA2

UnserInternet4.0 Infra 1 16 Mbit/s 48 â–‚â–„__ WPA2

Wireless1 Infra 4 16 Mbit/s 48 â–‚â–„__ WPA1 WPA2

DISTORTEDPEOPLE_EXT Infra 9 16 Mbit/s 48 â–‚â–„__ WPA1 WPA2

FRITZ!Box 7362 SL Infra 1 44 Mbit/s 47 â–‚â–„__ WPA2

Wolf 7360 Infra 1 16 Mbit/s 47 â–‚â–„__ WPA1 WPA2

walterfranz Infra 4 16 Mbit/s 47 â–‚â–„__ WPA2

Piratensender Infra 7 2 Mbit/s 47 â–‚â–„__ WPA1 WPA2

David Infra 11 54 Mbit/s 47 â–‚â–„__ WPA1

FRITZ!Box 7490 Infra 3 44 Mbit/s 46 â–‚â–„__ WPA2

ffg_02 Infra 4 44 Mbit/s 46 â–‚â–„__ WPA2

Brain Exit = Brexit Infra 7 44 Mbit/s 46 â–‚â–„__ WPA1 WPA2

MASSIMO Infra 11 44 Mbit/s 44 â–‚â–„__ WPA1 WPA2

devolo-bcf2afb1d5ce Infra 6 44 Mbit/s 43 â–‚â–„__ WPA2

Antigonus Infra 11 16 Mbit/s 43 â–‚â–„__ WPA1 WPA2

lotta Infra 11 54 Mbit/s 42 â–‚â–„__ WEP

if you need Wi-Fi stop buying devices that lack Wi-Fi. An OrangePi Lite behaves almost the same as a NEO since from an Armbian point of view it's 'just another H3 device', it's just faster under full load (better throttling behaviour), consumes less energy and regarding GPIO everything that applies for Orange Pi PC applies here too.

Armbian supports ~10 boards with onboard Wi-Fi and Armbian feels (and more or less acts) identical on all of them. We don't have the ressources to fiddle around with every random Wi-Fi stick available. Or lets better say with the count of team members we have it's an insane waste of ressources to try to support this cheap and unreliable crap instead of doing important things.

We try at least to give best out of the box support for the various onboard Wi-Fis, as far as I can tell situation with 8189CU and 8188CUS is quite fine so the best idea is to choose the appropriate device for the specific use case (and to be honest: If I have to choose between a NEO with Wi-Fi dongle and an Orange Pi Lite it's pretty easy to choose the latter. And if I would use both reliable Wi-Fi and Ethernet then it's an Orange Pi PC Plus that gets ordered).

scargill · October 15, 2016

Does the Orange Pi lite have audio? Review says no.... (Neo does) ??

tkaiser · October 15, 2016

Does the Orange Pi lite have audio? Review says no.... (Neo does) ??

Orange Pi Lite has Audio through HDMI and analog stuff on solder points (accessing them can be considered PITA ). For Audio + Wi-Fi clearly NanoPi Air will be the board of choice (different Audio stuff on the pin headers just as they did when switching from NEO PCB rev. 1.0 to 1.1)

Sign In

NanoPI NEO / AIR

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Similar Content

Important Information