Igor

Unknown or too complex to explain. If there is USB support and since there is, all of those will and they do work out of the box. Just remember to use USB2 port. USB3 is also not working yet.

Thomas told you how things are. (I missed the part that you want to boot this backup copy) Nothing to add.

It depends. If you start with a nightly image, you don't need, otherwise you need.

According to Hardkernel folks, it's stable. Last time I want to make a switch (again) I made a few tests and sometimes I could not boot. If you know what you are doing is easy. Everything is packed (kernel, dtb, u-boot, root, headers, firmware) and it was explained how to do it manually in case armbian-config way of switching kernels and repositories fails. You can try, but if you fail you are on your own to do some forum searching and fix the problem.

Boot from SD and install to eMMC. This will nuke your eMMC so you don't need to do nothing.

Start with a clean image.

Remove all our packages that gives you problem and install those: apt install linux-image-next-sunxi linux-dtb-next-sunxi linux-headers-next-sunxi linux-stretch-root-next-orangepiplus linux-u-boot-orangepiplus-next

It's getting ready. You can install it from a nightly repository, kernel name DEV.

Please switch to nightly (armbian-config), update and repeat the tests. You should be running 4.17.4

We always seek for scientific explanation. You will need to add a lot more to support such heretical claims You can run into a kernel panic even SD card was written properly and some boards are picky about SD card brand/speed. That's nothing unusual. Inadequate powering, on the other hand, can and do cause weird troubles ... which are sometimes hard to explain.

@Rami Can you check if this image works for you as expected: https://dl.armbian.com/nanopineo/Ubuntu_bionic_dev_nightly.7z

Nope, don't worry.

Our Debian and our Ubuntu always use the exact same kernel. There is no difference. But each userspace release (Debian Jessie, Debian Stretch, Ubuntu Xenial or Ubuntu Bionic) can have different kernels: default = usually old legacy one (3.4.y), next = modern 4.14.y (atm), dev = modern 4.17.y ... I assume you are not planning to use a generic "Debian" kernel from www.debian.org? It might work but it would be a step back. Can Neo, regardless of the operating system, boot from SSD disk? No, it can't. You always need an SD card, but you can run it from SSD. https://docs.armbian.com/User-Guide_Getting-Started/#how-to-install-to-emmc-nand-sata-usb

There is no special procedure. But why you don't rather install some RDP/VNC and connect to the boards desktop remotely ... when you need that.

Our nanopi core image has disabled ethernet since board does not have it. Try to use image for a normal Neo if you use ethernet. Wrote on mobile

Hmm.Strange. then uboot or whole image from a normal Neo? Afaik there are no other diffs. Wrote on mobile

Remove spaces between = The rest I cant help since you forget to provide diagnostic logs. armbianmonitor -u

Add fdtfile=sun8i-h3-nanopi-neo.dtb to /boot/armbianEnv.txt and reboot. Wifi is not connected automagically. https://docs.armbian.com/User-Guide_Getting-Started/#how-to-connect-to-wireless Also, a possible problem with ssh daemon if there was not a finished first boot. In that case, you need to recreate ssh keys manually.

Try adding --keep-dirlinks parameter.

Sure why not. Bionic provides the same experience with possible problems since it's a new assembly.

Yes. Small H3 boards are prone to higher temperatures due to a primitive voltage regulator and small size. H3 can go up to 90-100 by the specs so don't worry. If you can touch it and it doesn't hurt, it's ok. A small heatsink can't do any damage

We deal with board hardware issues and OS. I rarely use Python and I am sure those libraries can be easily installed but this I don't know. You can also do some search or wait for someone that plays with this. For setting GPIO on and off you don't need any libs http://linux-sunxi.org/GPIO

I2C protocol, which is needed for this device, is supported but disabled by default. Use armbian-config to enable the appropriate I2C port or edit .fex file (decompile-edit-compile) /boot/script.bin if you are using old legacy 3.4.y kernel. RPi GPIO is on Raspberry Pi. I am not aware of Python libraries, but officially is this what you get: https://github.com/friendlyarm/WiringNP

Considering the time wasted on breaking & fixing we just froze legacy kernel (fork it when MS allows us as is and forget about. There are a lot of 3399 related patches getting in and that's is anyway irrelevant here.

Yeah. I noticed just before my bedtime. Damn. Can we afford to drop default? What NEXT doesn't have?