Search the Community

I am trying to enable USB on Nanopi-neo-air in mainline kernel. Followed these links to do that. But any device on USB port is not recognized at all. http://linux-sunxi.org/USB_Gadget/Ethernet http://linux-sunxi.org/USB_Gadget/Mass_storage Any clue, what's missing? Thank you.

Hi, I have a nanopi neo based on allwinner h3 chipset. I am trying to use an SPIDEV based driver for RF2401L (2.4 Ghz wireless module). I have used npi-config to enable the /dev/spidev0.0 device. However, when I try to use it to read status register of my module, I get wrong values. My SPI settings are Speed: 10kHz Bits: 8 Mode: 0 (CPOL=0, CPHA=0) To debug the issue I used a logic analyzer and found the clock signal rising up just before the MISO/MOSI activity. It shouldn't do that. When CPOL = 0, clock should be idle at 0. I am setting the SPI mode to 0. Here is the code void SPI::init() { uint8_t bits = RF24_SPIDEV_BITS; uint32_t speed = RF24_SPIDEV_SPEED; uint8_t mode = 0; int ret; /* * spi mode */ ret = ioctl(this->fd, SPI_IOC_WR_MODE, &mode); if (ret == -1) { perror("can't set spi mode"); abort(); } ret = ioctl(this->fd, SPI_IOC_RD_MODE, &mode); if (ret == -1) { perror("can't set spi mode"); abort(); } /* * bits per word */ ret = ioctl(this->fd, SPI_IOC_WR_BITS_PER_WORD, &bits); if (ret == -1) { perror("can't set bits per word"); abort(); } ret = ioctl(this->fd, SPI_IOC_RD_BITS_PER_WORD, &bits); if (ret == -1) { perror("can't set bits per word"); abort(); } /* * max speed hz */ ret = ioctl(this->fd, SPI_IOC_WR_MAX_SPEED_HZ, &speed); if (ret == -1) { perror("can't set max speed hz"); abort(); } ret = ioctl(this->fd, SPI_IOC_RD_MAX_SPEED_HZ, &speed); if (ret == -1) { perror("can't set max speed hz"); abort(); } } Please someone help!

Hi all, I am trying get wifi working on Nanopi neo air with the Mainline kernel v4.12.12. I enabled brcmfmac driver in the kernel. Downloaded the corresponding firmware(brcmfmac43430-sdio.bin) for AP6212 from : https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/brcm. I have applied patch to the device tree to enable wifi (https://www.spinics.net/lists/arm-kernel/msg563666.html) I couldn't get the firmware loaded properly. Here's the log. [ 85.922929] brcmfmac: brcmf_attach Enter [ 85.922967] brcmfmac: brcmf_proto_attach Enter [ 85.922990] brcmfmac: brcmf_fweh_register event handler registered for PSM_WATCHDOG [ 85.923078] brcmfmac: brcmf_sdio_probe completed!! [ 85.923088] brcmfmac: brcmf_fw_get_firmwares_pcie enter: dev=mmc1:0001:1 [ 85.923292] usbcore: registered new interface driver brcmfmac [ 85.930368] brcmfmac: brcmf_fw_request_code_done enter: dev=mmc1:0001:1 [ 85.930520] brcmfmac: brcmf_fw_request_nvram_done enter: dev=mmc1:0001:1 [ 85.930591] brcmfmac: brcmf_sdio_firmware_callback Enter: dev=mmc1:0001:1, err=0 [ 85.930715] brcmfmac: brcmf_sdio_download_code_file Enter [ 85.952077] brcmfmac: brcmf_sdio_verifymemory Compare RAM dl & ul at 0x00000000; size=369577 [ 85.988168] brcmfmac: brcmf_sdio_download_nvram Enter [ 85.988333] brcmfmac: brcmf_sdio_verifymemory Compare RAM dl & ul at 0x0007fd78; size=648 [ 85.988478] brcmfmac: brcmf_chip_set_active Enter [ 86.999164] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 87.006519] brcmfmac: brcmf_sdio_firmware_callback failed: dev=mmc1:0001:1, err=0 [ 87.006563] brcmfmac: brcmf_sdio_remove Enter [ 87.006568] brcmfmac: brcmf_detach Enter [ 87.006582] brcmfmac: brcmf_bus_change_state 0 -> 0 [ 87.006589] brcmfmac: brcmf_sdio_bus_stop Enter [ 88.018990] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 88.026469] brcmfmac: brcmf_proto_detach Enter [ 88.026483] brcmfmac: brcmf_fweh_unregister event handler cleared for PSM_WATCHDOG [ 89.039090] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 89.086342] brcmfmac: brcmf_chip_set_passive Enter [ 89.087211] brcmfmac: brcmf_sdio_remove Disconnected Should I be trying some different firmware? Any input is much appreciated. Thank you.

Hi, Noobee here. I'm using a NanoPi NEO with the latest legacy image updated. Using ssh to access device. Linux Lap 3.4.113-sun8i #4 SMP PREEMPT Wed Nov 22 13:45:28 CET 2017 armv7l armv7l armv7l GNU/Linux In the journalctrl log I'm getting repeated failures for ntpd and cron about every minute. 1) The router that I'm connected to is IPv4 only. In nmtui I'v set the connection to ignore IPv6, but it seems that IPv6 has not been disabled. A IPv6 IP address has been assigned to the wireless interface. Should I be doing something else? 2) Cron is constantly doing something with armbian-updates. Is this normal?? diagnosis information will now be uploaded to http://sprunge.us/VfcK Regards, Gord_W Dec 12 08:04:22 Lap ntpd[902]: bind(22) AF_INET6 fe80::42a5:efff:fed2:ee52%4#123 flags 0x11 failed: Cannot assign req Dec 12 08:04:22 Lap ntpd[902]: unable to create socket on wlx40a5efd2ee52 (400) for fe80::42a5:efff:fed2:ee52%4#123 Dec 12 08:04:22 Lap ntpd[902]: failed to init interface for address fe80::42a5:efff:fed2:ee52%4 Dec 12 08:05:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:05:01 Lap CRON[9046]: pam_unix(cron:session): session opened for user root by (uid=0) Dec 12 08:05:01 Lap CRON[9047]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 12 08:05:01 Lap CRON[9046]: pam_unix(cron:session): session closed for user root Dec 12 08:06:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:06:22 Lap ntpd[902]: bind(22) AF_INET6 fe80::42a5:efff:fed2:ee52%4#123 flags 0x11 failed: Cannot assign req Dec 12 08:06:22 Lap ntpd[902]: unable to create socket on wlx40a5efd2ee52 (401) for fe80::42a5:efff:fed2:ee52%4#123 Dec 12 08:06:22 Lap ntpd[902]: failed to init interface for address fe80::42a5:efff:fed2:ee52%4 Dec 12 08:07:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:08:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:08:22 Lap ntpd[902]: bind(22) AF_INET6 fe80::42a5:efff:fed2:ee52%4#123 flags 0x11 failed: Cannot assign req Dec 12 08:08:22 Lap ntpd[902]: unable to create socket on wlx40a5efd2ee52 (402) for fe80::42a5:efff:fed2:ee52%4#123 Dec 12 08:08:22 Lap ntpd[902]: failed to init interface for address fe80::42a5:efff:fed2:ee52%4 Dec 12 08:09:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:10:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:10:22 Lap ntpd[902]: bind(22) AF_INET6 fe80::42a5:efff:fed2:ee52%4#123 flags 0x11 failed: Cannot assign req Dec 12 08:10:22 Lap ntpd[902]: unable to create socket on wlx40a5efd2ee52 (403) for fe80::42a5:efff:fed2:ee52%4#123 Dec 12 08:10:22 Lap ntpd[902]: failed to init interface for address fe80::42a5:efff:fed2:ee52%4 Dec 12 08:11:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:12:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:12:22 Lap ntpd[902]: bind(22) AF_INET6 fe80::42a5:efff:fed2:ee52%4#123 flags 0x11 failed: Cannot assign req Dec 12 08:12:22 Lap ntpd[902]: unable to create socket on wlx40a5efd2ee52 (404) for fe80::42a5:efff:fed2:ee52%4#123 Dec 12 08:12:22 Lap ntpd[902]: failed to init interface for address fe80::42a5:efff:fed2:ee52%4 Dec 12 08:13:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:14:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:14:22 Lap ntpd[902]: bind(22) AF_INET6 fe80::42a5:efff:fed2:ee52%4#123 flags 0x11 failed: Cannot assign req Dec 12 08:14:22 Lap ntpd[902]: unable to create socket on wlx40a5efd2ee52 (405) for fe80::42a5:efff:fed2:ee52%4#123 Dec 12 08:14:22 Lap ntpd[902]: failed to init interface for address fe80::42a5:efff:fed2:ee52%4 Dec 12 08:15:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:15:01 Lap CRON[9100]: pam_unix(cron:session): session opened for user root by (uid=0) Dec 12 08:15:01 Lap CRON[9101]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 12 08:15:01 Lap CRON[9100]: pam_unix(cron:session): session closed for user root Dec 12 08:16:01 Lap cron[455]: (*system*armbian-updates) INSECURE MODE (group/other writable) (/etc/cron.d/armbian-up Dec 12 08:16:22 Lap ntpd[902]: bind(22) AF_INET6 fe80::42a5:efff:fed2:ee52%4#123 flags 0x11 failed: Cannot assign req Dec 12 08:16:22 Lap ntpd[902]: unable to create socket on wlx40a5efd2ee52 (406) for fe80::42a5:efff:fed2:ee52%4#123 D

I recently received my kit, which consists of the Neo, heatsink, and acrylic shell. Installed Debian_jessie_default.7z with Etcher onto a Kingston SDCIT/8GBSP. PCB 1.3+ uses a more sophisticated voltage regulator than earlier revisions... The temperature is excellent so far (only 40c). I can run some more tests if someone provides instructions. So these boards do not in fact require a heavy copper plane for heat dissipation. I did use a superior heat pad rather than the one that is provided with the heatsink kit. Ideally, you would want something like a 4mm or so copper shim with good quality thermal paste applied to both sides. I also considered thermally coupling the RAM to the heatsink but decided not to. I am running Webmin with Apache and PHP for some very basic web server functionality (media relaying server). All-in-all, I'd highly recommend the Neo if you need a simple headless server. This was my first experience with a development board, and it was a good one. Cheers

Hi, I'm looking for a working OS Image for Nano Pi Neo Air for using I2S, SPI and Bluetooth (AP6212). Is there a release I can use "out of the box" for this? Regards Bernhard

Hello, I'm trying to make MB1242 sonar working with my nanopi but every time I run i2cdetect, I got "i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0". Sonar works fine on RPI after changing i2c_baudrate to 50000. Is there any way to do the same at nanopi?

Hi, I try without success to attach the a.m. adapter to my NanoPi Neo. OS is Armbian_5.25_Nanopineo_Ubuntu_xenial_default_3.4.113 I did two trials in order to install the driver: 1. Download the Edimax driver und run the install.sh script. Result: Error in the processing of the make file. 2. Followed an comprehensive advice from the net. Result: Error in kernel generation. Question: Has somebody got this device running on the Neo? And how you have performed this? Please consider, I am just a Linux user, but (unfortenately) no expert. Any hints are very welcome. Thanks, Walter

Hi. I am hoping to connect this type of IR receiver to my NanoPi Neo. https://www.jaycar.com.au/arduino-compatible-infrared-receiver-module/p/XC4427 I am hoping that all I need to do is connect 5v, ground and signal to the IR receiver pin to pin 6 on the header. Can anyone help me with the software and what I need to do to install lirc so the IR receiver is recognised? TIA V.

Hi all ! I try to turn off ethernet leds on Nano Pi Neo. I don't use network-manager (which disables leds when ethernet cable is disconnected) because I need to use ifup and ifdown... I tried to see (without success) : cd /sys/class/leds cd /sys/class/net/eth0/ h3consumption -e off I know that it's possible on banapi (with a github library), is it possible on nano pi neo ? Best Regards

Hello everyone, I am using Nanopi air and I wish to have ethernet and mass storage simultaneously. I went through numerous problems but now I have OTG working. If i try modprobe with g_serial, g_ether, or g_mass_storage, each works individually. Even g_cdc ( ethernet + serial ) and g_acm_ms ( mass storage + ethernet ) work. when I try to run : modprobe g_multi file=/sdcard.img I get the following: [ 290.720691] g_multi gadget: unable to autoconfigure all endpoints [ 290.880936] g_multi musb-hdrc.1.auto: failed to start g_multi: -524 Please help

I'm trying to use the kernel-driver (1) for a DHT11 (or DHT22) humidity sensor with my NanoPi NEO. I'm already got this sensors working with some little C example-programs in userspace. I figured out that I need to apply a Device Tree overlay because the driver (dht11.c) needs to know the gpio-pin where the sensor is connected to. So - I don't know how to write such a file from scratch - I customised a existing overlay file - "sun8i-h3-pps-gpio.dts" (2) - only the lines "pins" (PG6) & "compatible with" (dht11) & "gpios" (&pio 6 6 1) /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { pps_pins: pps_pins { pins = "PG6"; function = "gpio_in"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { pps@0 { compatible = "dht11"; pinctrl-names = "default"; pinctrl-0 = <&pps_pins>; gpios = <&pio 6 6 1>; /* PG6 */ status = "okay"; }; }; }; }; With this overlay file applied ("armbian-add-overlay ...") the driver module is loading on boot and the directories and files in the iio-subsystem are created (eg. /sys/bus/iio/devices/iio\:device0/in_humidityrelative_input) When I try to read from the sensor I got the following error in my terminal cat: '/sys/bus/iio/devices/iio:device0/in_humidityrelative_input': Connection timed out and this on the serial console dht11 pps@0: Only 25 signal edges detected According to the source of the driver there should be 84 edges to detect - something seems to be to slow ... When it is possible to read from the sensor with userspace programs so it should be also possible to do the same thing with a kernel driver - right? So I'm thinking, that the error should be in my overlay file ... but I am at my wit's end. Maybe somebody can help me? (1) https://github.com/torvalds/linux/blob/master/drivers/iio/humidity/dht11.c (2) https://github.com/armbian/sunxi-DT-overlays/blob/master/sun8i-h3/sun8i-h3-pps-gpio.dts (my English lessons in school are 15 years ago, so please excuse)

Don't quite know what to expect here. The download page implies that there should be a gadget serial connection but there is nothing. I don't even see the USB DRC getting registered. Is this a known issue and is there a solution? TAIA. # nanopineo:~$ uname -a Linux nanopineo 4.11.3-sun8i #3 SMP Wed Jun 7 13:28:34 CEST 2017 armv7l armv7l armv7l GNU/Linux # nanopineo:~$ lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M # nanopineo:~$ lsmod Module Size Used by evdev 20480 1 brcmfmac 172032 0 brcmutil 16384 1 brcmfmac cfg80211 204800 1 brcmfmac rfkill 24576 4 cfg80211 sun8i_codec_analog 24576 0 snd_soc_core 122880 1 sun8i_codec_analog snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 77824 2 snd_pcm_dmaengine,snd_soc_core sun8i_ths 16384 0 gpio_keys 16384 0 uio_pdrv_genirq 16384 0 cpufreq_dt 16384 0 uio 16384 1 uio_pdrv_genirq thermal_sys 57344 2 cpufreq_dt,sun8i_ths g_serial 16384 0 libcomposite 40960 1 g_serial

Hello people, I'm using Armbian 5.30 - kernel 3.4.113 on a Nanopi NEO. and I'm relatively new to this stuff, so please bear with me. I successfully managed to install an LCD screen on SPI (ILI9341) using this command: sudo modprobe fbtft_device custom name=fb_ili9341 gpios=reset:1,dc:201,led:6 speed=16000000 rotate=90 bgr=1 So far so good, but the resolution of the screen is too little and can't load anything - for example Dosbox. I would want to replicate the trick that already exists on Raspberry/Raspbian, and that is to framebuffer a higher res screen (at least 640x480) on the tiny LCD's resolution of 320x240. This is the program that is used for Raspberry, for reference: https://github.com/tasanakorn/rpi-fbcp Can someone please tell me if is possible? Thank you

Hello Everyone , Can anyone please guide me . I need to use nano pi neo's USB pins(2.54mm x 2 header pins) and looking for resources related to it. I am using armbian OS on it. I am struggling with it , I read many resources on the web but none of them provide detailed information. Any help will really be appreciated !! Thanks so much!!

HI.. I have an opi zero and I want to copy the card and use it in a NanoPi Neo I plugged it in and it works but displays Orange Pi Zero on the login screen. What steps should I take to make it work best in the NanoPi Neo? Thanks. V.

I have a NanoPi Neo that's been up about 4 months and I am using it for DHCP and DNS caching (using dnsmasq). This has been working fine over SSH until after the update. Previously, I could log in, edit the dnsmasq settings, and restart the service without issue. Now, when I attempt to restart a service (not just dnsmasq, I tested a couple others), it hangs and looks like it's waiting for a password entry on the TTY. (I'm logged in over SSH and I do not have a TTY connected). ... in first SSH session, this just hangs forever until I ctrl-C: root@nanopineo:/etc# systemctl restart dnsmasq ... in second SSH session, PS shows: root 1825 783 0 11:18 pts/0 00:00:00 systemctl restart dnsmasq root 1826 1825 0 11:18 pts/0 00:00:00 /bin/systemd-tty-ask-password-agent --watch root 1827 1624 0 11:18 pts/1 00:00:00 ps -ef Much reading online and I still cannot figure out if this is intentional, nor can I find how I can disable this behavior. Why would it ask for a prompt when running as root user? I think perhaps this might be a bug - you cannot remotely manage a server if it's going to hang waiting for a password every time you restart a service! That's pretty bad. Possibly this one which does not seem resolved. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789 Any ideas? Has anyone seen this? Thanks

Hi, I got one of those cheap 300Mbps wifi dongles with 8192EU chip with USB Vid/Pid 0bda:818b. How can we enable this in Armbian? lsmod does not show any detected h/w driver and wan0 is not showing up in ifconfig. Only lsusb has the following root@nanopineo:~# lsusb Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0bda:818b Realtek Semiconductor Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@nanopineo:~# Any hint or pointer welcome. Christos

Hello guys, I've been trying for the past month to get USB OTG and I2C to work on a NanoPI NEO AIR running Armbian, without any success. For OTG what I've tried was adding the following to "sun8i-h3-nanopi-neo-air.dts": &usb_otg { dr_mode = "otg"; status = "okay"; }; I have also enabled OTG and I2C in the kernel config menu, but for I2C I couldn't find what to put inside the DTS file. Can someone give me pointers on how to solve this, please? Yes, I am a very inexperienced developer when it comes to embedded systems and have very poor understanding of how to properly configure a device tree source file. Any help would be deeply appreciated. Thank you.

Nano Pi Neo, Armbian (Armbian_5.27.170422_Nanopineo_Ubuntu_xenial_dev_4.10.11) External USB device works fine when connected via USB-A jack, but doesn't work when connected to 2.54 pin header (2,3). Is there some additional steps to activate internal (usb1, usb2) ports, or it's hardware problem?

Hello I have an issue with my wifi, it's not reliable. There is no problem with my laptop, or any other devices on my network, but my NanoPi Neo is disconneted after a few hours. It can stay alive for an half a day, and after it become unreachable. As I have no other connection to my NanoPi it's a bit hard to establish what appens. But if I unplug the USB Wifi dungle, and replugged it the link come back. Doing a ping to the NanoPi, I see regular "Request timeout for icmp_seq" - every 20, 50 or 100 request, it depends - and sometime the request time is abnormally huge: serveral seconds. The config has bee done with nmtui, the name has been left as proposed (wlx00b819aa5f7). It's a static IP, Gateway is y router, and the DNS server has been input manually based on my router data. iwconfig output: wlx000b819aa5f7 IEEE 802.11bgn ESSID:"MyESSID" Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency:2.437 GHz Access Point: 14:CC:20:97:FE:64 Bit Rate:150 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:****-****-****-****-****-****-****-**** Security mode:open Power Management:off Link Quality=80/100 Signal level=49/100 Noise level=0/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ifconfig: wlx000b819aa5f7 Link encap:Ethernet HWaddr 00:0b:81:9a:a5:f7 inet addr:192.168.1.202 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::d443:6a18:32da:e5d7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:51728 errors:0 dropped:8476 overruns:0 frame:0 TX packets:35786 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7144585 (7.1 MB) TX bytes:4917495 (4.9 MB) ping output: 64 bytes from 192.168.1.202: icmp_seq=22055 ttl=64 time=56.726 ms 64 bytes from 192.168.1.202: icmp_seq=22056 ttl=64 time=3.295 ms 64 bytes from 192.168.1.202: icmp_seq=22058 ttl=64 time=6.217 ms 64 bytes from 192.168.1.202: icmp_seq=22059 ttl=64 time=6.551 ms 64 bytes from 192.168.1.202: icmp_seq=22060 ttl=64 time=6.095 ms 64 bytes from 192.168.1.202: icmp_seq=22061 ttl=64 time=8.796 ms Request timeout for icmp_seq 22062 64 bytes from 192.168.1.202: icmp_seq=22063 ttl=64 time=5.058 ms 64 bytes from 192.168.1.202: icmp_seq=22064 ttl=64 time=6.975 ms 64 bytes from 192.168.1.202: icmp_seq=22065 ttl=64 time=6.486 ms 64 bytes from 192.168.1.202: icmp_seq=22066 ttl=64 time=3.707 ms 64 bytes from 192.168.1.202: icmp_seq=22067 ttl=64 time=9.997 ms 64 bytes from 192.168.1.202: icmp_seq=22068 ttl=64 time=6.415 ms 64 bytes from 192.168.1.202: icmp_seq=22069 ttl=64 time=6.248 ms 64 bytes from 192.168.1.202: icmp_seq=22070 ttl=64 time=5.540 ms 64 bytes from 192.168.1.202: icmp_seq=22071 ttl=64 time=5.915 ms 64 bytes from 192.168.1.202: icmp_seq=22072 ttl=64 time=12.543 ms I would really appreciate if someone can tell me waht to monitor to prevent that issue Regards

Today I encounter a rather significant packet loss at the wired ethernet connectionmy at my NanoPi NEO. The device is up-to-date running with Armbian 5.25 and Pi-hole. The system is the most of time idle and shouldn't suffer from heavy load or many simultaneous connections. From NanoPi NEO to Windows: --- 192.168.0.204 ping statistics --- 263 packets transmitted, 221 received, 15% packet loss, time 262004ms rtt min/avg/max/mdev = 0.358/0.457/0.729/0.049 ms From Windows to NanoPI NEO: Ping-Statistik für 192.168.0.10: Pakete: Gesendet = 249, Empfangen = 222, Verloren = 27 (10% Verlust), Ca. Zeitangaben in Millisek.: Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms Other clients in my network respond regular without any loss. Is there a solution for this problem? Thank you very much in advance! GR3mGH0n

hi, as of this morning, i tried updating my NanoPi Neo build (kernel=dev, os=ubuntu xenial, type=no graphics/server). Has been building fine for months. I think problem is in U-Boot (header missing ?) LDFLAGS="" python ./lib/libfdt/setup.py \ "-Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -include ./include/libfdt_env.h -idirafterinclude -idirafter./arch/arm/include -I./lib/libfdt -I./tools -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE " lib/libfdt/fdt.c lib/libfdt/fdt_ro.c lib/libfdt/fdt_rw.c lib/libfdt/fdt_strerror.c lib/libfdt/fdt_wip.c lib/libfdt/fdt_region.c lib/libfdt/fdt_sw.c tools/libfdt_wrap.c tools/libfdt_wrap.c:147:21: fatal error: Python.h: No such file or directory compilation terminated. error: command 'x86_64-linux-gnu-gcc' failed with exit status 1 tools/Makefile:123: recipe for target 'tools/_libfdt.so' failed make[1]: *** [tools/_libfdt.so] Error 1 Makefile:1229: recipe for target 'tools' failed make: *** [tools] Error 2 [ error ] ERROR in function compile_uboot [ common.sh:97 ] [ error ] U-boot compilation failed [ o.k. ] Process terminated real 1m23.452s

A board (nanopi neo) collects some information and stores it to SD card. Users than change the SD card and open it on PC (windows). Due windows limitation, there is only one (first) partition (fat/ntfs) can be visible. Current mainline image for nanopi neo contains only one ext4 partition, so I tried to gparted it (moved first partition and made new FAT16 one), but for some reason, the image did not boot. So I'm looking for info, how to make two partitions properly.

Hi there, I've received 4 NanoPi Neo (with heatsinks as suggested by @tkaiser) recently. Here is my my first impression and also I've come across some minor issues. I hope It would be useful. I've installed Armbian_5.27.170403_Nanopineo_Ubuntu_xenial_dev_4.10.3. Also tried dietpi (kernel 3.4) and h3-mainline-ubuntu-core-qte-sd4g-beta-20170228.img (FrendlyArm, kernel 4.10) So far for good. Armbian works like a charm I have been able to install Docker and I've performed some simple tests. Awesome job guys! I've found one issue so far MAC address changes at every reboot. The issue was mentioned in some threads on the forum but seems like there is no solution still. btw FA's h3-mainline-ubuntu-core-qte-sd4g-beta-20170228 has no such an issue. So my workaround for this is `hwaddress ether 02:81:xx:xx:xx:xx` in `/etc/network/interfaces` file. I took MAC address from FA's image. It is not a issue. Installer forces me to change root password and make a user account. I totally understand all the security implications and stuff but it makes a massive bootstrapping difficult. I would like to make an ansible playbook to bootstrap all boards at once but it requires some extra work and jumping over hoops with expect module. If it it possible to disable that (without rebuilding an images) please share. Overall Armbian gives me a very positive impression. Great work. I'm looking forward for some more experiments.