Stanislav Sinyagin

haha, mine too. I just didn't bother to look at the chip

almost forgot: there's onboard 8GB eMMC chip (actually preloaded with Ubuntu image), and it's also not visible if I boot the Nanopineo2 Armbian image. It will be great to have a way to push Armbian onto that chip too.

thank goodness they decided for a better chip I just checked, the Ubuntu image that FriendlyARM is providing sees all those components correctly.

FriendlyARM has recently launched a new board in its NEO family: NanoPi NEO Plus2 As of Armbian_5.32.170704_Nanopineo2_Ubuntu_xenial_dev_4.11.8.img, few things aren't working: out of 1GB RAM, only 512MB is visible the USB socket closer to the edge (USBN1) is not visible, even with overlays Wifi and Bluetooth are not visible (AP6212A) (it's not a complaint, but just a statement

well, easier said than done. I'm still digging out of a backlog of my current projects

I can help with Perl or shell scripting, if needed

I'm fine with experimental status, but just wondering, how did 4.10.3-sun8i memorize the MAC address, and why 4.11.3-sun8i does not? Also, why is today's nightly build of Nanopi Neo2 not having this issue? Is the network hardware completely different on it?

also after poweroff command, the board starts up again by itself

I'm not complaining, just eager to help identifying the problems

with 4.11, there's still an issue that an attached WiFi dongle is not visible after reboot, and it needs to be re-plugged (or the whole board needs a power-cycle). It looks like the USB device initialization is broken at soft reboot.

Now 4.11 kernel update is missing for nanopineo2. The link returns 404: https://beta.armbian.com/pool/main/l/linux-u-boot-nanopineo2-dev/

Here's my small improvement on their acrylic enclosure: https://txlab.wordpress.com/2017/06/02/acrylic-enclosure-for-friendlyelec-nanopi-neo2/

the serial console shows that it comes up, but the USB devices are not visible. I'll try more troubleshooting when I get the time.

Got my Neo2, playing some early tests. The plastic enclosure is unfortunately useless: it's 3D printed, and it doesn't fixate the heatsink. Also I broke the enclosure while trying to insert the board. Fresh Armbian booted fine, and with a WiFi dongle, it's much more stable than OPI0 (OPI0 hanging up after less than an hour). What I noticed, is that it doesn't come up after a reboot, and needs a power cycle. here I wrote a short summary: https://txlab.wordpress.com/2017/04/16/friendlyelec-nanopi-neo2-a-better-sub-20-linux-computer/

As now /boot/armbianEnv.txt contains the line "overlay_prefix=sun8i-h3", the string above does not work, and it needs to look like follows: overlays=usbhost2 usbhost3

I have an old Nokia USB cable that ends with 3 wires for the UART interface. I thought to solder a plug on them, but then I found a nice console cable for less than $2 on Aliexpress I'll try playing with the power, thanks

and there's another bug: after "poweroff" command, the power consumption grows from normal 1.5 to 3.5W slowly within few minutes. The device stops responding on network requests, but it heats up quite significantly. Looks like I need to solder a console adapter

by the way, is there a way to have an overlay that disables the WiFi chip completely, to save power?

Zador, tkaiser, thanks a lot, it helped adding overlays=sun8i-h3-usbhost2 sun8i-h3-usbhost3 into /boot/armbianEnv.txt and rebooting. DISCLAIMER: the overlay names may change as the development goes on. Of course I realize it's a development kernel, and I'm not going to use it for any production installations. But as I'm evaluating the platform in general, I prefer using the latest development software. Do you feel comfortable if I report any issues in the same format on this forum? It's in my habit to report bugs or thought-to-be-bugs

I was referring to the fact that the vendor delivered a poorly documented piece of hardware with a binary module for Linux kernel. I thought it's the same issue here. actually these expansion USB ports are kind of "on the board", if you look at this set. So far, it's the only enclosure available for OPI0, so people will assume that those expansion USB ports are in by default. I am actually a software developer, and also contributed to a Linux driver with a patch back in 1997. Currently I'm evaluating OPI0 if it can fit into my projects as a low-cost network agent. For example, connect to OpenVPN and provide remote console access via USB-to-Serial. I already discovered that WiFi hardware is quite poor, and the connection is too shaky for an interactive session. But if I disable Wifi interface, it's quite a useful piece of hardware for its price. But of course, it would be nice to have all USB ports active :-)

Orange Pi Zero with the small expansion board (2x USB, audio out, mic, IR). Legacy 3.4.113-sun8i kernel sees all USB hubs, and the USB ports on the expansion board work fine: root@orangepizero:~# 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 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 With the nightly build, the number of root hubs is less, and also the expansion board USB ports give only power, but no USB signaling: root@orangepizero:~# lsusb Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I guess it's the same story as with wifi driver...

installing a nightly image helped, thanks. So, it looks like the upgrade process from legacy to nightly is broken?

Just did it on Orange Pi Zero, followed by mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr and it did not help: root@orangepizero:~# lscpu Architecture: armv7l Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0 Off-line CPU(s) list: 1-3 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 Model name: ARMv7 Processor rev 5 (v7l) CPU max MHz: 1008.0000 CPU min MHz: 120.0000