Search the Community

Hi, I want to expand my NanoPi-NEO2 more uart ports through I2C, so I make a choice to use a sc16is750 module( just like sparkfun sc16is750 ). Below is all of my system information: pi@nanopineo2:~$ uname -a Linux nanopineo2 5.4.20-sunxi64 #20.02.1 SMP Mon Feb 17 02:37:37 CET 2020 aarch64 aarch64 aarch64 GNU/Linux First step ,I edit a device tree overlay for the sc16is750 named sc16is750-i2c.dts as below: pi@nanopineo2:/boot/overlay-user$ sudo nano sc16is750-i2c.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { /* This fragment is required only if using interrupts */ target = <&pio>; __overlay__ { sc16is750_pin_irq: sc16is750_pin_irq { pins = "PA17"; function = "irq"; bias-pull-up; }; }; }; fragment@1 { target = <&i2c1>; __overlay__ { #address-cells = <1>; #size-cells = <0>; sc16is750: sc16is750@4d { compatible = "nxp,sc16is750"; reg = <0x4d>; status = "okay"; clocks = <&sc16is750_clk>; gpio-controller; #gpio-cells = <3>; /* Below are optional properties for supporting interrupts */ interrupt-controller; #interrupt-cells = <3>; interrupt-parent = <&pio>; interrupts = <0 17 2>; /* PG11 IRQ_TYPE_EDGE_FALLING */ pinctrl-names = "default"; pinctrl-0 = <&sc16is750_pin_irq>; sc16is750_clk: sc16is750_clk { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <14745600>; }; }; }; }; __overrides__ { int_pin = <&sc16is750>,"interrupts:0"; addr = <&sc16is750>,"reg:0"; }; }; Second step, I add the sc16is750-i2c.dts to my /boot/overlay-usr as below: pi@nanopineo2:/boot/overlay-user$ sudo armbian-add-overlay sc16is750-i2c.dts Compiling the overlay Copying the compiled overlay file to /boot/overlay-user/ Reboot is required to apply the changes Afterthen, I checked sc16is750-i2c.dtbo as below: pi@nanopineo2:/boot/overlay-user$ fdtdump sc16is750-i2c.dtbo **** fdtdump is a low-level debugging tool, not meant for general use. **** If you want to decompile a dtb, you probably want **** dtc -I dtb -O dts <filename> /dts-v1/; // magic: 0xd00dfeed // totalsize: 0x5f8 (1528) // off_dt_struct: 0x38 // off_dt_strings: 0x4d0 // off_mem_rsvmap: 0x28 // version: 17 // last_comp_version: 16 // boot_cpuid_phys: 0x0 // size_dt_strings: 0x128 // size_dt_struct: 0x498 / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { target = <0xffffffff>; __overlay__ { sc16is750_pin_irq { pins = "PA17"; function = "irq"; bias-pull-up; phandle = <0x00000002>; }; }; }; fragment@1 { target = <0xffffffff>; __overlay__ { #address-cells = <0x00000001>; #size-cells = <0x00000000>; sc16is750@4d { compatible = "nxp,sc16is750"; reg = <0x0000004d>; status = "okay"; clocks = <0x00000001>; gpio-controller; #gpio-cells = <0x00000003>; interrupt-controller; #interrupt-cells = <0x00000003>; interrupt-parent = <0xffffffff>; interrupts = <0x00000000 0x00000011 0x00000002>; pinctrl-names = "default"; pinctrl-0 = <0x00000002>; phandle = <0x00000003>; sc16is750_clk { compatible = "fixed-clock"; #clock-cells = <0x00000000>; clock-frequency = <0x00e10000>; phandle = <0x00000001>; }; }; }; }; __symbols__ { sc16is750_pin_irq = "/fragment@0/__overlay__/sc16is750_pin_irq"; sc16is750 = "/fragment@1/__overlay__/sc16is750@4d"; sc16is750_clk = "/fragment@1/__overlay__/sc16is750@4d/sc16is750_clk"; }; __fixups__ { pio = "/fragment@0:target:0", "/fragment@1/__overlay__/sc16is750@4d:interrupt-parent:0"; i2c1 = "/fragment@1:target:0"; }; __local_fixups__ { fragment@1 { __overlay__ { sc16is750@4d { clocks = <0x00000000>; pinctrl-0 = <0x00000000>; }; }; }; }; }; After reboot, I check the tty devices: pi@nanopineo2:~$ dmesg | grep tty [ 2.056137] printk: console [ttyS0] disabled [ 2.076722] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 26, base_baud = 1500000) is a U6_16550A [ 2.076773] printk: console [ttyS0] enabled [ 2.098045] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 27, base_baud = 1500000) is a U6_16550A [ 2.119044] 1c28800.serial: ttyS2 at MMIO 0x1c28800 (irq = 28, base_baud = 1500000) is a U6_16550A [ 2.142198] 1c28c00.serial: ttyS3 at MMIO 0x1c28c00 (irq = 29, base_baud = 1500000) is a U6_16550A [ 5.873610] serial serial0: tty port ttySC0 registered Also, I have check the i2c: pi@nanopineo2:~$ sudo i2cdetect -y 1 [sudo] password for pi: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- my sc16is750 address:0x4d Finally, I check the tty devices: pi@nanopineo2:~$ ls -l /dev/ttyS* crw------- 1 pi tty 4, 64 Mar 23 03:21 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 Mar 23 03:16 /dev/ttyS1 crw-rw---- 1 root dialout 4, 66 Mar 23 03:16 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 Mar 23 03:16 /dev/ttyS3 pi@nanopineo2:~$ cat /proc/tty/drivers /dev/tty /dev/tty 5 0 system:/dev/tty /dev/console /dev/console 5 1 system:console /dev/ptmx /dev/ptmx 5 2 system /dev/vc/0 /dev/vc/0 4 0 system:vtmaster unknown /dev/ttySC 242 0-7 serial g_serial /dev/ttyGS 245 0-3 serial serial /dev/ttyS 4 64-67 serial pty_slave /dev/pts 136 0-1048575 pty:slave pty_master /dev/ptm 128 0-1048575 pty:master unknown /dev/tty 4 1-63 console So, My question is why I cannot find the /dev/ttySC0? Anyone can give me some advice to resolve the problem. Thanks.

Using Armbian_20.02.1 with 5.4 kernel on NEO2 board, I'm running into an issue trying to get the USB OTG working with the g_ether module. When I run modprobe g_ether I see the following in dmesg: [ 490.490582] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I've also tried compiling my own img using the Armbian builder but it looks like all the correct OTG options are already selected by default. Any ideas what I'm doing wrong?

Just wanted to note this - target NanoPi NEO2 - task at hand is Byte-UnixBench.... https://github.com/sfx2000/byte-unixbench more to follow...

Dears, We have 4 boards Nanopi Neo2, but when we connect to energy, they don't boot, leds of net port (green and yellow ones) and internal led (red) are on all time. We tried to access via serial port (using an usb-serial adapter), but they not show any boot process. We tried some different boot images on sd card. Nothing works. All four devices are in this situation (and they are new!). There is any thing we can do?

Hello I having some issues with the Armbian Buster image for Nano Pi Neo 2. https://www.armbian.com/nanopi-neo-2/ When I launch the command sudo apt update, I'm getting the following error: The package cache file is corrupted, it has the wrong hash I already downloaded the image several times, I still getting the same error. My SD card is ok, I have tried with 2 different ones. I can remember having the same issue with a preview version. What's wrong??? Thank you

I'm wondering if anyone has had any luck using spi-gpio to bitbang SPI on the H5... @martinayotte, I found a forum thread from a few years ago where you seemed to be looking at this area - perhaps you have an idea? Doing a typical spi-gpio DT overlay for this properly loads the spi-gpio and spi-bitbang drivers, creates /dev/spidev0.0, and allocates the gpios (verified via gpiod)...but the first problem I see is that the CS line is simply not working (cs-gpios below)...? /dts-v1/; /plugin/; / { fragment@0 { target-path = "/"; __overlay__ { spi { compatible = "spi-gpio"; #address-cells = <1>; #size-cells = <0>; ranges; mosi-gpios = <&pio 0 64 0>; /* PC0 */ miso-gpios = <&pio 0 65 0>; /* PC1 */ sck-gpios = <&pio 0 66 0>; /* PC2 */ cs-gpios = <&pio 0 67 1>; /* PC3 */ num-chipselects = <1>; status = "ok"; spidev { compatible = "spidev"; reg = <0>; spi-max-frequency = <500000>; }; }; }; }; }; I'm testing this on a NEO2 using dev kernel 5.3.8, and in this case I am re-using the same standard SPI lines for the HW SPI - this way I can switch between the two easily for testing. Standard HW SPI works great, of course, but the spi-gpio version doesn't. (I tested on other GPIO lines as well and the result is the same.) I hooked the CS, CLK, MOSI, and MISO lines to my scope, and did a test write spi_test through /dev/spidev0.0, and it appears that CLK is properly working, as is the test data transferred via MOSI (at least I'm seeing data bits coming across). But CS simply seems to not be working - I can't trigger properly on it (either high or low). Right off, measuring it shows it as low, when by default it should be high... I am not an expert by any means in this area, so any help/pointers/advice/thoughts would be greatly appreciated! Thanks!

Hi, I am trying to interface I/O expander MCP23017 to Nano Pi Neo2(Hardware specs:1 GB RAM, Gigabit Ethernet . Software specs: Debian Buster with Armbian Linux 4.19.59-sunxi64 ) . The issue I am having is I am not able to see the device when I run sudo i2cdetect -y 0 . I have enabled i2c overlays in /boot/armbian.txt . I am using 10 K Ohm pull-ups on SDA and SCK . I get no activity while running i2cdetect on the oscilloscope on SCK and SDA lines . Is this an issue with the kernel ?

I flashed the latest Armbian image on my NanoPi Neo 2 Plus's emmc. According to https://linux-sunxi.org/Linux_mainlining_effort I2S is not part of the mailinke kernel for H5. I can use I2S with Friendlyelec's images. However, I prefer Armbian. Is it somehow possible to use I2S with an Armbian image on this board?

I have read other thread regarding v4l2loopback kernel module installation. I got same problem like this message below ========================================= ------------------------------ Deleting module version: 0.10.0 completely from the DKMS tree. ------------------------------ Done. Unpacking v4l2loopback-dkms (0.10.0-1) over (0.10.0-1) ... Setting up v4l2loopback-dkms (0.10.0-1) ... Loading new v4l2loopback-0.10.0 DKMS files... dpkg: warning: version '3.4.113-sun8i 4.19.25' has bad syntax: invalid character in revision number Building for 4.19.20-sunxi64 Module build for kernel 4.19.20-sunxi64 was skipped since the kernel headers for this kernel does not seem to be installed. =================================== I am usng Nano PI neo2 with armbian 4.19.20. When I install the kernel-headers using armbian-config, the version of kernel-headers installed is 4.19.25. Either the kernel source I have installed using armbian-config is 4.19.25. I just guess the version mistach doesn't make me succeed build of v4l2loopback. But I can't figure out what to do with this error. Please give me some comment.

Hi, I am new here and searched the forums for an answer to my questions regarding the NanoPi NEO2 and NEO Plus2. Most answers I could find, but a few were left open. The NEO Plus2 is marked as WIP. Why? What do I have to expect not to work? Both boards are similarly old, from what I could find. Will the Plus2 move up to "supported" eventually or does it currently more look like the route is going towards CSC? Do common features like GPIO access, SPI, I2C ... work with current images? Do specific features where the Plus2 differs from the NEO2 like WiFi, Bluetooth, ... work? I already found out, that the second USB port should work fine. If someone could answer one ore all of those questions that would be much appreciated. Also if you have any other input towards rather buying one or the other SBC, that would be great. Thank you! Frank

Good day! I've had the Nanopi Neo2 v1.0 for sometime now, used for mostly for NAS solution. the v1.0 is the one being carried by my supplier here. No v1.1 yet Lately I installed armbian monitor to monitor system resources. Then I stumbled upon the min and max frequency when I checked using # cpufreq-info -p 408000 816000 ondemand I've read on some internet writeups that one can set the max frequency to 1008000 tried editing the cpufrequtils scaling_max_freq scaling_available_frequencies scaling_setspeed I was able to lower the minimum frequency to 120000 using the following entry at cpufrequtils # WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true #MIN_SPEED=408000 #MAX_SPEED=816000 MIN_SPEED=0 MAX_SPEED=1008000 GOVERNOR=ondemand but the output of cpufreq-info -p remains as # cpufreq-info -p 120000 816000 ondemand I'd really like to be able to set the max frequency higher than it is now. Any info, pointers, procedures (much better) will be much appreciated Thanks in advance!

I'm not sure I even want BakeBit. I'm trying to use the GPIO in my NanoPi Neo2. Specifically I want to read a digital I/O pin on/off state. And if possible I'd like to read an analog voltage from the H5's built in ADC. Now that I've looked deeper into BakeBit, it seems like the entire purpose of BakeBit is to do GPIO with an Arduino, and read the information remotely on a RbPi/NanoPi or whatever ON the Arduino's GPIO pins. If that is really what BakeBit is, then BakeBit doesn't interest me. The H5 already has GPIO and an ADC. We just need to get that working. For interest's sake, here is the progress I made with BakeBit. ADC Python example in Bakebit http://wiki.friendlyarm.com/wiki/index.php/BakeBit_-_Light_Sensor i had to `apt-get install libjpeg-dev zlib1g-dev` to get pillow to install properly, which is a dependency of BakeBit. Bakebit installed without errors, but it tries to compile WiringNP which complained with a lot of warnings. In the following thread I got WiringNP to run. This was semi useful BTW https://www.cnx-software.com/2017/05/21/using-gpios-on-nanopi-neo-2-board-with-bakebit-starter-kit/ Now when I `rm -rf the bakebit dir` then do a fresh clone and `/scripts/BakeBit/Script/install.sh` it installs without errors except warnings for WiringNP. (which I don't actually get when I build it myself) With the hax I did to get WiringNP to work on my Neo2. I deleted Bakebit/Scripts/WiringNP and replaced it with the version that I modified and built successfully.

Hi all, Running Armbian Ubuntu 18.04 with stock neo2 4.19.20 kernel I tried installing https://github.com/friendlyarm/WiringNP but after installation `gpio readall` says : "This NanoPi model is currently not supported." However all the wiki's and the Github page says it's supported.......? I can see GPIO in the sys fs at /sys/class/gpio/ but I was hoping to have an easier time with it than manually exporting each pin and calculating offsets for pins with scraps of info online etc. Objective 1: Read a high/low 3.3v/0v status from a GPIO Objective 2: Read an analog voltage, using an ADC. Does the H5 include an ADC? When I look in http://wiki.friendlyarm.com/wiki/images/d/de/Allwinner_H5_Datasheet_V1.0.pdf Page 13 says 2.1.4.9.KEYADC * Analog to digital converter with 6-bit resolution for key application * Maximum sampling frequency up to 250 Hz * Supports general key, hold key and already hold key * Supports single , normal and continuous work mode I don't need high speed sampling, don't need interrupts, the simpler and easier the implementation the better. Any help will be much appreciated PS: How to fix friendlyarm/WiringNP friendlyarm/WiringNP is not accepting issues on their github repo, but it seems to be the best fork out there. How can we get them to accept issues and how can we fix the issue? http://forked.yannick.io/friendlyarm/WiringNP

(Edit: it's a red herring for me to worry about swap. Please see a few posts down...) Hello. My NanoPi Neo 2 only has 512MB RAM. I'm using it for OpenMediaVault. It starts swapping very badly (totally paralysing it) when I FTP 60GB worth of tiny files into an attached 500GB SSD SATA drive (attached with the NAS kit). Yes, ProFTPd is RAM-hungry! I know how to create and work with traditional linux swap files. I'm a noob to this whole zram thing, which I suspect is more trouble than it's worth. I would prefer to not use zram, and use a traditional swap file on an attached 6TB 3.5" SATA drive (attached over USB 2.0 with UAS). It's a backup drive that sits there all day long doing nothing, in fact it goes to sleep all day (and only wakes up in the middle of the night to do a backup). zramctl shows: NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lzo 60.3M 4K 78B 12K 4 [SWAP] /dev/zram1 lzo 60.3M 4K 78B 12K 4 [SWAP] /dev/zram2 lzo 60.3M 4K 78B 12K 4 [SWAP] /dev/zram3 lzo 60.3M 4K 78B 12K 4 [SWAP] Those zram device files are on my Sandisk Ultra MicroSD card (which is "A1"), where Armbian runs from. My lightly-used SATA drive would be better for me, for running a traditional swap file from (due to its just sleeping all day otherwise). Is there some way to tell my Armbian "quit with zram, and just use a traditional swap file, as per my /etc/fstab"? BTW: I've set my "vm.swappiness" to 5 in /etc/sysctl.conf

Hi, I am trying to install the aircrack-ng driver via dkms from over here: https://github.com/aircrack-ng/rtl8812au When I change the Makefile to match my processor arm-sun50iw1p1 , I receive these compilation errors and do not know how to fix them. cat /var/lib/dkms/rtl8812au/5.2.20.2/build/make.log DKMS make.log for rtl8812au-5.2.20.2 for kernel 4.19.20-sunxi64 (aarch64) Tue Feb 12 21:53:55 UTC 2019 make ARCH=arm64 CROSS_COMPILE=/home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu- -C /lib/modules/4.19.20-sunxi64/build M=/var/lib/dkms/rtl8812au/5.2.20.2/build modules make[1]: Entering directory '/usr/src/linux-headers-4.19.20-sunxi64' arch/arm64/Makefile:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum arch/arm64/Makefile:48: Detected assembler with broken .inst; disassembly will be unreliable ./scripts/gcc-version.sh: line 26: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: No such file or directory ./scripts/gcc-version.sh: line 27: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: No such file or directory make[1]: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: Command not found make[1]: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: Command not found make[1]: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: Command not found make[1]: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: Command not found /bin/sh: 1: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: not found (standard_in) 1: syntax error CC [M] /var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_cmd.o /bin/sh: 1: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: not found scripts/Makefile.build:303: recipe for target '/var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_cmd.o' failed make[2]: *** [/var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_cmd.o] Error 127 make[2]: *** Waiting for unfinished jobs.... CC [M] /var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_security.o /bin/sh: 1: /home/android_sdk/Allwinner/a64/android-51/lichee/out/sun50iw1p1/android/common/buildroot/external-toolchain/bin/aarch64-linux-gnu-gcc: not found scripts/Makefile.build:303: recipe for target '/var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_security.o' failed make[2]: *** [/var/lib/dkms/rtl8812au/5.2.20.2/build/core/rtw_security.o] Error 127 Makefile:1520: recipe for target '_module_/var/lib/dkms/rtl8812au/5.2.20.2/build' failed make[1]: *** [_module_/var/lib/dkms/rtl8812au/5.2.20.2/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-4.19.20-sunxi64' Makefile:1551: recipe for target 'modules' failed make: *** [modules] Error 2 Any ideas? kind regards, rhagu

Hi, I'm running a NEO2 with Ubuntu at a remote location, so watchdog would be very important to have. Didn't use it before, but afaik H5 SoC supports hardware watchdog. How should I turn it on and do I need to install and configure anything? I read about H3, but not sure about H5. Thanks!

I'm trying to figure out what happened in my device this morning. the process that i'm monitoring was interrupted and restarted and i'm want to know that reason, is it internal code reasone or system failure that caused to my process to crash. i'm attaching the /var/log/message piece of logs when my process crashed. can you tell me what happened? I'm using NanoPi2 NEO with latest armbian version for this specific board, Thanks alot

HI, I have the following NanoPi Neo 2 boards, hardware v 1.1, model 1711 with 1Gb RAM Linux 4.19.13-sunxi64 #5.70 SMP Sat Jan 12 17:41:57 CET 2019 aarch64 GNU/Linux I have noticed that various network related tasks fail at boot apparently at eth0 is not yet ready This includes network mounts via /etc/fstab and disabling IPv6 via /etc/sysctl.conf My current solution (which I feel is a complete bodge) is to have extra commands in /etc/rc.local that after a 5 second sleep issue a 'mount -a' and 'sysclt -p' I have tried solutions for 'wait for network' on boot but neither work. systemctl enable NetworkManager-wait-online.service systemctl enable systemd-networkd-wait-online.service Looking at the armbianmonitor output I see this. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet XXX.XXX.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 02:01:43:0c:2e:f7 brd ff:ff:ff:ff:ff:ff I have not edited the network config and /etc/network/interfaces is the standard # Network is managed by Network manager auto lo iface lo inet loopback IP address allocation is via DHCP, however these have pihole installed which I believe change this to static, albeit to match whatever they were getting via DHCP. Is anyone else seeing this, have any thoughts or have a 'better' solution ? edit: just spotted this at the bottom of the log [ 9.905128] RTL8211E Gigabit Ethernet 0.2:07: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=0.2:07, irq=POLL) [ 9.907509] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found [ 9.907527] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 9.907535] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 9.907998] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 15.011046] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 15.011101] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 15.107488] FS-Cache: Loaded [ 15.176939] FS-Cache: Netfs 'cifs' registered for caching [ 15.177411] Key type cifs.spnego registered [ 15.177427] Key type cifs.idmap registered [ 15.178533] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [ 15.611651] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 15.648915] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 15.655164] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 15.655183] cfg80211: failed to load regulatory.db [ 20.150078] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. It would be interesting to know what is happening between 9.907 and 15.01 where the network finally comes up. I would guess that the CIFS mount at 15.17 is the OS reading fstab, which appears to fail, then the second mount at 20.15 is rc.local running mount -a but I'm not 100% sure. I can't tell / don't know enough to see where in the boot sequence /etc/sysctl or /etc/fstab are invoked.

Board NEO2 with Armbian Stretch mainline kernel 4.19.y many errors: info:xxxxx[3087]::2019-01-30T10:19:10.607956+00:00: /usr/sbin/xxxxx: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory info:xxxxx[3093]::2019-01-30T10:19:20.857869+00:00: /usr/sbin/xxxxx: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory info:xxxxx[3097]::2019-01-30T10:19:31.114980+00:00: /usr/sbin/xxxxx: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory info:xxxxx[3106]::2019-01-30T10:19:41.357962+00:00: /usr/sbin/xxxxx: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory info:xxxxx[3108]::2019-01-30T10:19:51.607633+00:00: /usr/sbin/xxxxx: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory please help

Hi, I have just received some shiny new NanoPi Neo 2 boards, hardware v 1.1, model 1711 with 1Gb RAM. I have installed Armbian Stretch mainline kernel 4.19.y with no issues at all however I have noticed that the green LED is pretty well ignoring anything I ask of it. ls -la /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Jan 25 16:14 . drwxr-xr-x 52 root root 0 Jan 1 1970 .. lrwxrwxrwx 1 root root 0 Jan 1 1970 nanopi:green:status -> ../../devices/platform/leds/leds/nanopi:green:status lrwxrwxrwx 1 root root 0 Jan 1 1970 nanopi:red:pwr -> ../../devices/platform/leds/leds/nanopi:red:pwr cat /sys/class/leds/nanopi:green:status/trigger none kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport usb-gadget usb-host disk-activity disk-read disk-write ide-disk mtd nand-disk [heartbeat] cpu cpu0 cpu1 cpu2 cpu3 default-on panic mmc0 0.2:07:link 0.2:07:1Gbps 0.2:07:100Mbps 0.2:07:10Mbps rfkill-any rfkill-none Of the above only 'none' heartbeat' and 'default-on' seem to work, all others are just off / no activity. I didn't try the kbd / usb related ones etc. as I don't have one attached. There was a comment in Nanopi NEO 2 dated May 2017 that this was seen and may get looked at so was just wondering if this is still as expected ? From the date and the colours mentioned I am also assuming that the original thread and comments covered the v1.0 hardware. All that aside, gotta say - Love your work.

I just got a Nanopi NEO2 512MB, installed Armbian Ubuntu Bionic. It works fine, except for the DVB-T/C stick. It is affected by Kernel 4.10+ problems. I wonder if I can downgrade to an older kernel, like 4.4.0 for example, where everything works perfectly? If yes, how? There is a patch that perhaps would resolve the problem, how could I apply this patch to an of the available releases of Armbian? This patch Please, help me with this. Many thanks!

Hello guys, at first I want to says thanks for the great OS that you deliver. I use it since 8 months on a bunch of nano-pi neo2's and it runs rock solid. However i rebuild from time to time the image I use from scratch in order to see that the installation is reproducable and repeatable. Today it has encountered that the installation of 'apt-get install python:armhf python-dev:armhf' failed with: # dpkg --add-architecture armhf # sudo apt-get update .... Reading package lists... Done # sudo apt-get install -y python-pip python:armhf python-dev:armhf Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python-dev:armhf : Depends: libpython-dev:armhf (= 2.7.12-1~16.04) but it is not going to be installed Depends: python2.7-dev:armhf (>= 2.7.12-1~) but it is not going to be installed E: Unable to correct problems, you have held broken packages. I use armbian_5.38_Nanopineo2_Ubuntu_xenial_next_4.14.14.img. The reason I do this, is that I want to use Segger Debugger on the platform, but Segger only provides armhf-libs (used by Pylink-square). Asking Segger to release arm64 libraries already failed. Thanks in advance, Axel.

These boards are well suited to routing/network traffic control functionality. Currently the kernel has been compiled with Traffic Control stuff disabled, which makes it impossible to perform traffic shaping on stock Armbian kernel. I'm busy recompiling the kernel as a temporary solution, but I will really appreciate it if the kernel build maintainer can please change the traffic control options from DISABLED to MODULE (at least)? I have a bunch of Armbian boards but I'm testing with NanoPi Neo 2 right now. --- I'll let you know the size of the modules once I've finished compiling.

I use a NEO2 (H5), with armbian linux 4.19.13-sunxi64, and have a StarTech usb2.0 to Gigabit-ethernet adapter, which I plug in the usb slot of the NEO2 and which gives me a new additional ethernet interface. iperf3 on this interface (against another NEO2 with its generic gigabit interface) gives maximum 111 MBit/sec, even with the tips in https://forum.armbian.com/topic/7001-slow-usb-speed-on-h5-devices-orangepi-prime-probably-cpu-governor-related/ (which actually dont change much) Using a raspberry pi (2B) with the same adapter and cable I get 170 MBit/sec, which is significantly more (although still not what one should hope for, which is up to 300, but maybe the StarTech is not perfect) So the usb adapter is not the problem, and I observe similar speeds (around 100 MBit/sec) with other devices too. Why is the usb in the H5 so slow? I need at least 150MBit/sec (ok not really for this adapter, actually for another one, but never mind)

I'm running some stress test on the NanoPi neo2 512mb, CPU heating reached 75-76 degrees, and it's stable, the problem that I faced is that the computer changed it's IP suddenly (after 55 minutes of test running), I guess it's because of a network card reset. Did anyone face the following issue? Is it related to the stress test? Or it's another networking problem? The test I'm running is with the "stress" tool, running long time stress on 4 CPUs. In addition, does anyone have any insights regarding this device? good or bad?