Search the Community

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?

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.

Because today I did get my Black-Friday NanoPi Neo2 LTS 1GB I swapped my old Neo2 against this new 1Gb LTS-version. After assembling the new LTS to the fresh heatsink I did a testdrive and all went fine (network etc). So I did try to put the faceplate back on the case but it doenst fit. At the time when I did buy the case there was also a faceplate for the normal H3 Neo delivered. So for the new LTS Neo2 I had to use the faceplate for the H3-Neo, because the new LTS Neo2 has the USB-Port aligned like the H3-Neo . The old Neo2 has his USB-Port (on the main Neo2-PCB) a bit shifted against the Network-port. Also the new LTS Neo2 has the Ethernet LEDs upside down against the old Neo2 AND the MicroSD-Slot is now click-inserted (which the old Neo2 didnt had). At the attached picture you could the the old Neo2 (IP22) with the shifted USB-Port in the NAS-case (like the old Neo2 in the black Aluminium case - but PCB upside-down) and the new LTS Neo2 (IP23) in the NAS-case with the aligned USB-Port beside the Ethernet-Port.

Hi, I tried to enable the i2c in u-boot by using the config flags shown in the Readme. But I had no success. What do I miss?

Hi, I compiled the newest version of u-boot. Then I updated it at my sd card via: dd if=/dev/zero of=/dev/mmcblk0 bs=1k count=1023 seek=1 dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8 dd if=u-boot.bin of=/dev/mmcblk0 bs=1024 seek=40 Now u-boot starts and I'll get to the message "Starting kernel ..." and nothing happens. Do I have to recompile the Kernel or did I something wrong? Edit: I did it on my NanoPi Neo2

Hello, The NanoPi Neo 2 has an H5 SoC. When I look at the Linux mainlining effort chart at Sunxi, I see that Ethernet support for the H5 only came in the 4.15 kernel. But the kernel in the Armbian downloads for the NanoPi Neo 2 only have the 4.14.y kernel. So can one expect the GbE to work, on a NanoPi Neo 2, with the current Armbian (Bionic or Stretch)? Maybe you already backport the 4.15 Ethernet-related code (for the H5) into that 4.14.y kernel?

Armbian_5.59_Nanopineo2_Ubuntu_bionic_next_4.14.65.img does not see the sound codec at all. The status matrix here: http://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix tells that Audio Codec should be supported since kernel 4.12 on H3 (H2+ is the same, as far as I know). But Armbian does not see the audio codec nor on NanoPi Neo2 (H5), nor even on on NanoPi Duo (H2+), although all the img files I used have 4.14 in their name. However, even with FriendlyElec's own image nanopi-neo2_ubuntu-oled_4.14.52_20180628.img there is a different issue - the sound is mono instead of stereo! I tried speaker-test: speaker-test -Dsysdefault:Codec -c 2 -t wav speaker-test 1.1.0 Playback device is sysdefault:Codec Stream parameters are 48000Hz, S16_LE, 2 channels The test plays back the voice that says: Front Right / Front Left but the sound comes form both channels simultaneously. Tried also other devices reported by aplay -L: hw, hwplug. The same result - the sound is monophonic. I tested for short circuit by attaching another audio player right in parallel to my wires - the sound is stereo from the player, so there is no short circuit. Also, if I run the same test on a cheap external USB sound adapter connected to the NanoPi, it works correctly and plays stereo. I also tried the same speaker test on a NanoPi Duo with its Mini shield and connected headphones to 3.5 jack. The same result - no stereo sound even on the official 3.5 minijack. Has FriendlyElec missed the fact that their boards do not have stereo sound? Or is everyone using external USB soundcards (which seems redundant considering the in-built audio) or I2S? At the same time, my old CHIP with R8 (which essentially is A13) passes the same speaker-test without any issues - the sound is stereo. I posted a question on FriendlyElec forums about the issue, but at the end, I would like to use Armbian anyway. So, what are my options to get stereo sound out of H5 (and H2+) in-built audio codec using Armbian?

Hello, I'm running rsync to backup a VPS to an USB hard drive on the neo2 and sometimes rsync just stops with "read error from input device (I/O error)". I believe this issue happens when rsync is causing high load in the USB disk, writing or removing a large number of files or trying to write a big file. Notes: The hard drive is on a self powered enclosure - so power failure is not really an option here I also have Apache and mariadb storing data on the USB disk and I never had this kind of I/O errors with it OS: Debian GNU/Linux 9.4 (stretch) Drive is ext4 Whenever rysnc stops I get this under /var/log/messages: sd 0:0:0:0: [sda] tag#1 data cmplt err -32 uas-tag 2 inflight: sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 38 80 0a 68 00 00 a0 00 sd 0:0:0:0: [sda] tag#0 data cmplt err -32 uas-tag 1 inflight: CMD sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 57 50 28 78 00 03 00 00 sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 38 80 0a 68 00 00 a0 00 sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x2a 2a 00 19 47 7f 20 00 00 90 00 sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 57 50 28 78 00 03 00 00 scsi host0: uas_eh_device_reset_handler start usb 5-1: reset high-speed USB device number 2 using ehci-platform scsi host0: uas_eh_device_reset_handler success sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 sd 0:0:0:0: [sda] tag#0 Sense Key : 0x2 [current] sd 0:0:0:0: [sda] tag#0 ASC=0x3a ASCQ=0x0 sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 57 50 28 78 00 03 00 00 sd 0:0:0:0: [sda] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 sd 0:0:0:0: [sda] tag#1 Sense Key : 0x2 [current] sd 0:0:0:0: [sda] tag#1 ASC=0x3a ASCQ=0x0 sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x2a 2a 00 19 47 7f 20 00 00 90 00 EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 13001563 (offset 0 size 73728 starting block 53014518) My fstab: LABEL=USBHD /mnt/storage ext4 defaults,nofail 0 0 Why does it happen? Thank you. PS: can someone move this to the Technical support section? Posted on the wrong place!

I'm trying to boot my Nano Pi Neo 2 from the network but I am a bit stuck. I have found out how to add network support to u-boot for the Nano Pi Neo 2, I can set the serverip and perform the dchp command, the Nanopi neo get's an IP address from the DHCP server but then booting halts with the message that it can't find the file. I'm pretty sure the location & access rights are valid. (Is there an easy way to check?) U-Boot 2018.09-rc3-00026-g4cdeda511f-dirty (Sep 10 2018 - 16:37:11 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: FriendlyARM NanoPi NEO 2 DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 => setenv serverip 192.168.188.1 => dhcp BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 DHCP client bound to address 192.168.188.50 (1003 ms) Using ethernet@1c30000 device TFTP from server 192.168.188.1; our IP address is 192.168.188.50 Filename '/nfsshares/tftp/npi/boot/boot.scr'. Load address: 0x42000000 Loading: T TFTP error: 'File not found' (1) Not retrying... => Is there anyone who has experience booting Armbian from the network that can point me in the right direction / perhaps share a working solution?

There appears to be a problem or incompatibility with the new 2018.05 u-boot configuration and/or implementation and the Armbian sunxi-next startup scripts (both in the current master branch). The "fdt" command processing doesn't appear to properly expand local environment variables before trying to execute them (?). Here's an example from a vanilla Armbian boot (u-boot 2018.05) - notice the "libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND" errors when the DT fixup script runs: ... Err: serial Net: No ethernet found. 230454 bytes read in 15 ms (14.7 MiB/s) starting USB... No controllers found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 3100 bytes read in 7 ms (431.6 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 230 bytes read in 5 ms (44.9 KiB/s) 26379 bytes read in 19 ms (1.3 MiB/s) 780 bytes read in 18 ms (42 KiB/s) Applying kernel provided DT overlay sun50i-h5-spi-spidev.dtbo 504 bytes read in 30 ms (15.6 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo 504 bytes read in 32 ms (14.6 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo 4179 bytes read in 26 ms (156.3 KiB/s) Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 44000000 libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND 4534427 bytes read in 230 ms (18.8 MiB/s) 13942792 bytes read in 695 ms (19.1 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... ... These particular "FDT_ERR_NOTFOUND" errors are coming from the processing for the /boot/armbianEnv.txt setting "param_spidev_spibus=". The two "fdt set /soc/${tmp_spi_path} ..." commands are failing because ${tmp_spi_path} is not getting expanded (or is expanded incorrectly, or something}. I've excerpted the necessary commands from the board DT startup scripts to illustrate this. Simply boot into u-boot on a top-of-tree build from master on an H5 device - hit spacebar repeatedly while u-boot is starting up - and enter the following commands in the u-boot command line (in this example I'm using my NanoPi NEO2): ... In: serial Out: serial Err: serial Net: No ethernet found. 230454 bytes read in 15 ms (14.7 MiB/s) starting USB... No controllers found Autoboot in 1 seconds, press <Space> to stop => => => => setenv load_addr "0x44000000" => print fdt_addr_r fdt_addr_r=0x4FA00000 => setenv devtype mmc => setenv devnum 0 => load ${devtype} ${devnum} ${fdt_addr_r} dtb/allwinner/sun50i-h5-nanopi-neo2.dtb 26379 bytes read in 18 ms (1.4 MiB/s) => fdt addr ${fdt_addr_r} => fdt resize 65536 => load ${devtype} ${devnum} ${load_addr} dtb/allwinner/overlay/sun50i-h5-spi-spidev.dtbo 780 bytes read in 18 ms (42 KiB/s) => fdt apply ${load_addr} => => #### now if I set a temporary variable and use that variable (as in "sun50i-h5-fixup.scr"), it fails: => setenv tmp_spi_path "spi@01c68000" => fdt list /soc/${tmp_spi_path} libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND => => #### however if I specify the value directly, it works fine: => fdt list /soc/spi@1c68000 spi@1c68000 { compatible = "allwinner,sun8i-h3-spi"; reg = <0x01c68000 0x00001000>; interrupts = <0x00000000 0x00000041 0x00000004>; clocks = <0x00000003 0x0000001e 0x00000003 0x00000052>; clock-names = "ahb", "mod"; dmas = <0x00000017 0x00000017 0x00000017 0x00000017>; dma-names = "rx", "tx"; pinctrl-names = "default"; pinctrl-0 = <0x00000018>; resets = <0x00000003 0x0000000f>; status = "okay"; #address-cells = <0x00000001>; #size-cells = <0x00000000>; phandle = <0x0000004e>; spidev { }; }; => The effect of this is that the current fixup scripts in the master branch won't process everything properly, and (in my case), SPI fails to be enabled and configured properly. I did some quick comparisons between the prior 2017.11 version and this version (cmdline processing and fdt processing), and there isn't anything obvious that stands out. Any ideas what might be going on here? Perhaps the startup DT scripts need to be updated?

Hi, I recently got a NanoPI NEO2 v1.0. I am able to load the Linux images using SD card and login using debug UART. But I am facing a strange issue where I need to disconnect USB power AND debug UART GND to switch off/on the board. I am using PL2303 UART module and connected the Tx, Rx and GND (verified using board diagram in wiki). Basically to completely reset the board, I also need to disconnect the UART GND. Is this expected? The LED is always on from beginning of boot till UART GND is disconnected (on even with USB power off). I have also verified that the board boots up only using UART 5V and without USB power, but I would to continue using USB power. Thanks, - Arun

Hi - Just checked out latest greatest code from git to compile new stretch image for my NanoPiNeo2 ( Armbian_5.46_Nanopineo2_Debian_stretch_next_4.14.47 ) but seems it won't boot up. Tried two SDcards and two different boards but same result. Tried both Etscher ( 1.4.4 ) and Rufus ( 3 ) but same result, any issue known that I missed ? Please note I am building a standard image ( thus no customised settings ) also came to my attention the board becomes quite warm, this is unusual . Thanks

For a new project with multiple socs, I want to use the NanoPi Neo 2 with the Allwinner H5 soc and boot from DHCP / NFS. I've done the same in the past for a setup with Raspberry Pi's, but the Allwinner socs require a different approach. What would be the best way to achive this? - FEL? - SD or USB with U-Boot? - any other suggestions?

Sometimes it's unclear if my Nanopi NEO2 is still running, or fully locked up / FUBAR. Ping and SSH give no result. As there is no HDMI, I have no way to check if it's still there. So I was thinking: can I let the green LED flash each x seconds as a sign of life? Quote from Igor: "Both are accessible via sysfs, green is configurable while blue is not lit and reacting to anything. ". So a crontab script that writes something to /sys/ <LED> ... ? Feedback appreciated.

Hi guys, I have just installed Armbian on my nanopi neo2 which works in 1-bay NAS Kit v1.2 for NanoPi NEO&NEO2 (http://www.friendlyarm.com/index.php?route=product/product&product_id=192) I have installed Armbian from image (https://dl.armbian.com/nanopineo2/Debian_stretch_next.7z). The only thing that works on it is OMV which was installed via armbian-config My system is: root@openmediavault:/# uname -a Linux openmediavault 4.14.18-sunxi64 #26 SMP Fri Feb 9 17:14:48 CET 2018 aarch64 GNU/Linux root@openmediavault:/# root@openmediavault:/# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.4 (stretch) Release: 9.4 Codename: stretch root@openmediavault:/# Everything seems to be fine except watchdog module. root@openmediavault:~# systemctl status wd_keepalive.service ● wd_keepalive.service - watchdog keepalive daemon Loaded: loaded (/lib/systemd/system/wd_keepalive.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-04-25 17:27:41 CEST; 1min 22s ago Process: 1579 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module (code=exited, sta Apr 25 17:27:41 openmediavault systemd[1]: Starting watchdog keepalive daemon... Apr 25 17:27:41 openmediavault sh[1579]: modprobe: FATAL: Module softdog not found in directory /lib/modules/4.14.18-sunxi64 Apr 25 17:27:41 openmediavault systemd[1]: wd_keepalive.service: Control process exited, code=exited status=1 Apr 25 17:27:41 openmediavault systemd[1]: Failed to start watchdog keepalive daemon. Apr 25 17:27:41 openmediavault systemd[1]: wd_keepalive.service: Unit entered failed state. Apr 25 17:27:41 openmediavault systemd[1]: wd_keepalive.service: Failed with result 'exit-code'. root@openmediavault:~# root@openmediavault:~# root@openmediavault:~# systemctl status watchdog.service ● watchdog.service - watchdog daemon Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-04-25 17:27:41 CEST; 1min 50s ago Process: 1574 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module (code=exited, sta Apr 25 17:27:41 openmediavault systemd[1]: Starting watchdog daemon... Apr 25 17:27:41 openmediavault sh[1574]: modprobe: FATAL: Module softdog not found in directory /lib/modules/4.14.18-sunxi64 Apr 25 17:27:41 openmediavault systemd[1]: watchdog.service: Control process exited, code=exited status=1 Apr 25 17:27:41 openmediavault systemd[1]: Failed to start watchdog daemon. Apr 25 17:27:41 openmediavault systemd[1]: watchdog.service: Unit entered failed state. Apr 25 17:27:41 openmediavault systemd[1]: watchdog.service: Triggering OnFailure= dependencies. Apr 25 17:27:41 openmediavault systemd[1]: watchdog.service: Failed with result 'exit-code'. Maybe someone of you has idea how to fix it or even workaround it?

This seems like a really simple problem, but I can't find any pointers on any forums. I am running a NanoPiNEO2 (Allwinner H5) using the latest Armbian build DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS" I am trying all ways to save power. For most of the time, I do not need to use the Ethernet interface (I am using the USB interfaces for comms). I have tried all the obvious commands such as ifdown, and explored ethtool, but nothing I do makes any difference to the current consumption of the device. I expect i am missing something obvious - any help gratefully accepted.

Hy I tried to play around with the GPIOs and found some nice threads here however I don't get past the modprobe gpio command. I get this error modprobe: FATAL: Module gpio not found in directory /lib/modules/4.14.29-sunxi64 Does my kernel build has no GPIO library inside? Linux 4.14.29-sunxi64 #64 SMP Sat Mar 24 11:13:51 CET 2018 aarch64 GNU/Linux Andy

Hi there! I have been playing around with my NanoPi Neo 2 plus, I managed to get initramfs working thanks to the kernel config of armbian. I have just noticed a problem: only the first of the two USBs works. The second is completely dead. Big disclaimer: I am using an HTC PSU that provides only 1A, not the 2A that should be fed, although I do not know if this could be the cause of the issue. Aside from this problem, I cannot see other issues. Wifi is working and I disabled bluetooth. lsusb without anything plugged in to USB: Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Hello, I have just updated to the latest Debian Server image of NanoPI NEO 2. When connecting via Serial and using vim.basic/tiny I got the following strange behaviour: As soon as I enter the insert mode a newline is inserted automatically. This does not happen when connecting via SSH. So far I haven't experienced this behaviour with my previous image. Any ideas? Kind regards, Markus NB: textwidth is set to 0 (disabled).

Today I did get my NAS-Case "Neo Station NS-120B" for my NanoPi Neo2 (also useable with a normal NanoPi Neo). Because I already did use the Neo2 with armbian (and had soldered all pins on the mainboard - I ordered only the case without a new Neo2 with soldered pins) I didnt want to write the FriendlyARM Image for NAS to my uSD. After completing to built the Neo2 and the 2.5 HDD inside the case (and using the 12V PowerSupply I had) armbian did start up and I could normally SSH into my Neo2 - BUT I cant see the HDD or the HDD-controller (which should be connected via USB). ( @tkaisernow here the Neo2 do get his power over pins and not via the MicroUSB and the Neo2 not only has the "bigger" heat sink - now also the complete case is cooling the Neo2 ) There did come a thread - about the additional USB-Ports showing up at the Neo2 - to my mind. After a little search I did found the article of @Lope and @Igor: So I did add in /boot/armbianEnv.txt before my) last line (usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u) in the file: overlays=usbhost0 usbhost2 usbhost3 After a reboot dmesg did recognize the HDD [ 2.251979] usb 3-1: new high-speed USB device number 2 using ehci-platform [ 2.445211] scsi host0: uas [ 3.098627] scsi 0:0:0:0: Direct-Access JMicron Tech 0227 PQ: 0 ANSI: 6 [ 3.129039] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 3.129904] usbcore: registered new interface driver uas [ 3.130418] sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/233 GiB) [ 3.130432] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 3.130775] sd 0:0:0:0: [sda] Write Protect is off [ 3.130791] sd 0:0:0:0: [sda] Mode Sense: 5f 00 00 08 [ 3.131526] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 3.155212] sda: sda1 [ 3.159285] sd 0:0:0:0: [sda] Attached SCSI disk and lsusb did found the USB-HDD-controller JMicron JMS567 (USB 3.0 SATA-Controller connected to USB 2.0): root@nanoneo2:~# lsusb Bus 003 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. the module for the controller was also loaded already: root@nanoneo2:~# lsmod Module Size Used by uas 24576 0 after that mounting the HDD was business as usual: root@nanoneo2:~# cd /mnt root@nanoneo2:/mnt# mkdir harddisc root@nanoneo2:/mnt# mount /dev/sda1 /mnt/harddisc The disk contains an unclean file system (0, 0). The file system wasn't safely closed on Windows. Fixing. and df did show the free space on the HDD (the HDD was preformat while using it on PC): root@nanoneo2:/mnt/harddisc# df Filesystem 1K-blocks Used Available Use% Mounted on udev 179036 0 179036 0% /dev tmpfs 49460 1684 47776 4% /run /dev/mmcblk0p1 15126944 3487428 11453712 24% / tmpfs 247284 0 247284 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 247284 0 247284 0% /sys/fs/cgroup tmpfs 247284 0 247284 0% /tmp log2ram 51200 1968 49232 4% /var/log tmpfs 49460 0 49460 0% /run/user/0 /dev/sda1 244196348 122948 244073400 1% /mnt/harddisc The case does also include a realtime-clock (with CR2032 battery as buffer) which shows up in dmesg: [ 1.717710] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0 [ 1.717716] sun6i-rtc 1f00000.rtc: RTC enabled Later I will check - hdparm - let the HDD sleep after a while - install SMB and create a share (or more) (FTP is already installed) - create SMB-User

I had a NanoPi NEO2 working well with ARMBIAN 5.34.171121. After apt-get upgrade, ARMBIAN has been changed to ARMBIAN 5.37.171208 with below firmware update: Get:1 http://beta.armbian.com xenial/main arm64 linux-dtb-next-sunxi64 arm64 5.37.171208 [25.0 kB] Get:2 http://beta.armbian.com xenial/main arm64 linux-image-next-sunxi64 arm64 5.37.171208 [14.7 MB] Get:3 http://beta.armbian.com xenial/main arm64 linux-u-boot-nanopineo2-next arm64 5.37.171208 [222 kB] Get:4 http://beta.armbian.com xenial/main arm64 linux-xenial-root-next-nanopineo2 arm64 5.37.171208 [318 kB] Then the Ethernet port is no longer working. Kernel message shows MDIO register failure: root@NEO2-ST0:~# dmesg | grep -i eth [ 0.000000] psci: probing for conduit method from DT. [ 1.661750] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 1.838435] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 1.838566] dwmac-sun8i 1c30000.ethernet: Will use external PHY [ 1.944368] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 1.944381] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 1.944391] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 1.944401] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 1.944412] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 1.944422] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 1.944984] dwmac-sun8i 1c30000.ethernet: Cannot register the MDIO bus [ 1.945003] dwmac-sun8i 1c30000.ethernet: stmmac_dvr_probe: MDIO bus (id: 0) registration failed Any hack do I need on device tree or driver to make it work again? BTW: Is there any way to select specific version of ARMBIAN to build? 5.36 for example. Even if I checkout the specific release tag the build scripts will always switch to master and build the latest version. Thanks & BR, Xiaohai Li

Hi all, I'm currently running Armbian 5.36 Ubuntu 16.04.3 LTS 4.11.1-sun50iw2. This was / is a local armbian build that I performed a few months ago to resolve an issue that I saw at that time in the network stack that prevented ipsec working correctly. I've performed apt update / apt upgrade since however cat /proc/version still reports the version as that which I manually built back in June. Fast forward to today and I'd like to try out some traffic shaping tc rules but I'm running into some difficulty, which is making me doubt if my kernel has the support needed for iproute2. The following works without any issue to list existing rules on eth0: root@nanopineo2:~# tc -s qdisc ls dev eth0 qdisc pfifo_fast 0: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 1109245 bytes 4725 pkt (dropped 0, overlimits 0 requeues 26) backlog 0b 0p requeues 26 ..where pfifo_fast is the default qdisc (queuing discipline) for eth0 If I attempt to remove this rule I see an RTNETLINK error: root@nanopineo2:~# sudo tc qdisc del dev eth0 root RTNETLINK answers: No such file or directory If I attempt to add a new rule I see the same RTNETLINK error: root@nanopineo2:~# tc qdisc add dev eth0 root tbf rate 1000kbit latency 50ms burst 5000 RTNETLINK answers: No such file or directory iproute2 is installed: root@nanopineo2:~# apt list --installed | grep iproute2 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. iproute2/xenial-updates,now 4.3.0-1ubuntu3.16.04.2 arm64 [installed] ..however I read here http://lartc.org/howto/lartc.iproute2.package.html that kernel netlink support is required for iproute2 to work properly and I'm not sure that I have it. I'm almost sure that sch_netem should be present for it to work but this is not installed and as far as I can tell by looking at kernel source that I can find in github, this is not included as part of the sunxi kernel: root@nanopineo2:~# modprobe sch_netem modprobe: FATAL: Module sch_netem not found in directory /lib/modules/4.11.1-sun50iw2 Does anyone have any idea what I need to do to get this working? Thanks for any help Joe

Hello, Just started on the latest Neo2 Ubuntu (Armbian_5.34.171121_Nanopineo2_Ubuntu_xenial_next_4.13.14) as we were tired trying to get around the challenges of the Ubuntu Core provided by FriendlyARM. Have enabled SPI we think (armbian-config->system/hardware/spi-spidev) and rebooted, but even after full power cycle we don't see anything in /dev/spi*. Is there anything special/additional we need to do to get SPI working (which we know does from our Ubuntu Core build). Thanks Rob

Hi,I want to know how to disable serial console /dev/ttyS0 on NanoPi NEO2 with allwinner H5. My Environment: Board:NanoPi NEO2 uname -a: Linux nanopineo2 4.14.4-sunxi64 #11 SMP Thu Dec 7 11:55:12 CET 2017 aarch64 aarch64 aarch64 GNU/Linux dmesg | grep tty: [ 0.000156] console [tty0] enabled [ 1.655315] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 24, base_baud = 1500000) is a U6_16550A [ 1.655383] console [ttyS0] enabled [ 1.678058] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 25, base_baud = 1500000) is a U6_16550A [ 1.700706] 1c28800.serial: ttyS2 at MMIO 0x1c28800 (irq = 26, base_baud = 1500000) is a U6_16550A [ 1.723358] 1c28c00.serial: ttyS3 at MMIO 0x1c28c00 (irq = 27, base_baud = 1500000) is a U6_16550A Why I want to disable serial console /dev/ttyS0,because I want to use 3 uart port to communicate with other board and module. So I'm already using /dev/ttyS1,/dev/ttyS2. I tried some of solution that written on this forum and other web site. remove console=~ from boot.cmd and recompile boot.scr edit console=both to console=ttyGS0 on armbian-config disable some of getty service and serial console service using systemctl But never solved this problem. I ever can login with serial console on ttyS0 with USB-Serial converter. And when I conneted GPS to UART0,I can see recieved data using sudo cat /dev/ttyS0 for few seconds. But after few seconds, this procces was ended. I have faced same problem on RaspberryPi with Officeial Image. But in Raspberry Pi case,I used raspi-config to change disable serial console succesfully. If who know solution of this problem or information,Please teach me it. Sorry my not good English. Thank you for Armbian developers and forum members.

I did a apt update & upgrade on my NanoPi Neo2 NAS and it updated to nightly 5.37 but at the beginning of the boot-log it tells me: Net: No ethernet found. I didnt get an eth0 interface from the mainboard ethernet-port (only lo) [ 1.633544] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 1.798411] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 1.798556] dwmac-sun8i 1c30000.ethernet: Will use external PHY [ 1.904820] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 1.904832] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 1.904842] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 1.904853] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 1.904863] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 1.904873] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 1.905433] dwmac-sun8i 1c30000.ethernet: Cannot register the MDIO bus [ 1.905452] dwmac-sun8i 1c30000.ethernet: stmmac_dvr_probe: MDIO bus (id: 0) registration failed Now I can access the Neo2 only via TTL-serial-debug console Lucky me - I have a USB-Ethernet Adapter which I can use: [ 787.473350] MOSCHIP usb-ethernet driver 3-1:1.0 eth0: register 'MOSCHIP usb-ethernet driver' at usb-1c1b000.usb-1, MOSCHIP 7830/7832/7730 usb-NET adapter, 00:12:34:55:56:2b [ 787.473508] usbcore: registered new interface driver MOSCHIP usb-ethernet driver [ 787.503850] MOSCHIP usb-ethernet driver 3-1:1.0 enx00123455562b: renamed from eth0 so here the armbianmontor -u : root@nanopineo23:~# armbianmonitor -u System diagnosis information will now be uploaded to http://sprunge.us/JQdE PS: The NanoPi NAS with only a "normal" Neo has found his Network after update to 5.37 root@nanopi-neo:~# dmesg|grep -i 1c30000 [ 4.313641] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 4.313714] dwmac-sun8i 1c30000.ethernet: No regulator found [ 4.313819] dwmac-sun8i 1c30000.ethernet: Will use internal PHY [ 4.313937] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 148000 (expect 58000) [ 4.314111] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 4.314123] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 4.314134] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 4.314145] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 4.314156] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 4.314167] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 19.124960] dwmac-sun8i 1c30000.ethernet eth0: device MAC address 16:1c:0c:e4:e5:76 [ 19.128797] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 19.128816] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 22.249109] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx ARMBIAN 5.37.171208 nightly Debian GNU/Linux 9 (stretch) Linux nanopineo23 4.14.4-sunxi64 #11 SMP Thu Dec 7 11:55:12 CET 2017 aarch64 GNU/Linux Neo2_Bootlog_537.txt