Igor

I used to run complex services, including this forum, for at least half a year without a single issue (on probably the same image - Jessie 5.20). We haven't done much changes on the top of Hardkernel kernel either. Crashes can be caused by some hardware defects, insufficient power supply, bad media, bad 3rd party wireless chip, ... If you plan to do upgrade, skip u-boot package, kernel upgrade should be fine. And if you plan to used it as a server, consider using modern kernel. It should be good, bud it doesn't have HDMI console ... serial or SSH access only.

It works fine for me on HDMI display and also on HDMI recorder. ARMBIAN 5.26 stable Ubuntu 16.04.1 LTS 4.9.9-cubox (built one hour ago from sources) http://sprunge.us/HiPO

This means you have some troubles with your network. Wrote on mobile phone

On desktop you go into screen settings and rotate or change screen resolution.

5.20 should be o.k., no need to go for older. .raw rename to .img if you don't see it under your image writer. We recommend Etcher for writing.

We need to fix this or revert back to dual partition. Current temporally solution is that you start with older image -> 5.20, where we had dual partition scheme. Just write image directly to eMMC and it should work.

If you have DHCP server, your wired connection should work out of the box. You don't need to do anything. On all boards this is the same. OPi PC2 is under development and network could be temporally broken. Check today's (automated) build.

If your SD card is set that it boots from somewhere else, you need to mount that SD card on some Linux and set parameter in armbianEnv.txt rootdev="/dev/mmcblk0p1" When you boot from SD, nuke eMMC with standard tool: nand-sata-install

I would say it is, but you will need to play around u-boot scripts.

Currently this is still considered a bug.

(Allwinner) Legacy kernels have different type of storing HW configuration. It's stored in /boot/script.bin and we pack it to "board support package". Make sure that this /boot/script.bin is linked to your board. /boot/bin/cubietruck.bin ... after you install this package.

Yes, that's it ... you have very old build. You need to remove kernel image and install new one: linux-image-sun7i Check the rest of package names here: https://www.armbian.com/kernel/

MiQi (which is very similar) is under research and development. We got two boards two weeks ago. Support for ASUS board is unknown - we don't have any contacts yet.

Running wireless AP on developing kernel (no end user support by default) and 3rd party wireless hardware (also unsupported by us since it's mission impossible) is a hard nut even for experienced users. If you are newbie go the other way and search for & buy a working combination, Orange board with supported on-board WiFi(s) or just prepare yourself for many trial and errors. And we use NetworkManager, since it's more user friendly for newbies. The manual above is wrong in first place. Try this.

Type: armbianmonitor -u since we need to see some logs. Most likely you are using some very old image and since we change package naming once, this could be the problem.

Off yes, while On is not possible to have on those boards without additional hardware. You need to have some sort of PMU - Banana Pi, Cubietruck, ... And fact that you are using Retrorange Pi is also a problem. It's not Armbian but based on Armbian, different enough that is harder to catch a problem.

OK, thank you. Will try to recreate and fix.

That's theory and in most cases it works just fine. In general, not just with Armbian, but with any operating system I would rather do complex distribution upgrades with access to console. There are simply too many things which could go wrong. After all you are upgrading most if not all packages.

https://www.armbian.com/kernel/ https://forum.armbian.com/index.php/topic/2422-more-proper-testing-better-armbian-experience/ We provide even daily builds of this(all) kernel(s), but we won't hear any of pleads for help, because such service is stupid, costly, inefficient, ... supporting stable kernel is already way over for a free amateur service. Developing kernels are built daily for developers and for testing, that we are able to improve them ... and one day, when we are satisfied with quality, put them out. That's the point.

There were some related changes in u-boot and kernel and you will need to dig in there if you want to understand this now. Just install some older u-boot for example ... From our perspective it's another issue with low priority since it doesn't break anything, so we will pay attention on it on a long run.

dpkg -l This way you check what's installed. More info.

Try one more thing. Boot from fresh, switch to developing repository and issue update: https://forum.armbian.com/index.php/topic/2422-more-proper-testing-better-armbian-experience/ To rule out few things ...

Regarding Octoprint details I can't help much since I never ever install it. Have no idea what kind of troubles you can expect. But I saw few install howtos or mentioning of success install on top of Armbian ... which is, if you take Debian Jessie version, not much / almost no different than Raspbian. The biggest / main difference is lower level, hardware support, which is mostly in kernel and other RPi dedicated libraries. I would say unrelated to this install. Since this software looks hardware independent, it should be no problem to install it on Armbian. And when you succeed, the best thing is that you sum commands into one script, that you can recreate build at any time and that you can share your success story / how-to install Octoprint with others.

Docker port for ARM is unofficial and it doesn't need 4G RAM. This is not Windows / Intel world Check this thread for more info. But there is a problem since Docker needs at least kernel 3.10 and for this board (Orange Pi 2e) we don't have stable kernel higher than 3.4.113. Image with kernel 4.9.x can be built, it might even work fine, but we don't provide any support under any condition. You are on your own in case of troubles and they will pop out since this kernel is still under development.

https://www.olimex.com/forum/index.php?topic=1779.0