Igor

Perhaps in 2019/2020? Updates (development, testing, development, testing, ...) are already a luxury which you don't pay for. And you want optimizations of this luxury? Don't waste time. Do it: https://docs.armbian.com/Process_Contribute/ BTW. We have only one download server + backup.

Works somehow on mainline kernels ... while on legacy it can be a bit challenging.

@WarHawk_AVG He probably means this: http://linux-sunxi.org/USB_Gadget/Ethernet

OK. BTW. 2 is overkill

Is it O.K. now?

armbianmonitor -u is the first step if you expect some help/attention. Well, prior to this is reading and this should be a result https://en.wikipedia.org/wiki/Nvidia Revenue US$9.714 billion (2017) We are amateurs backed by good will and donations.

Good! Last known state with A64 and particular with this board are (IIRC): working legacy kernel and partially working modern u-boot/kernel combo. Wifi works on both, eMMC is up while there are problems with a network on the mainline kernel. HDMI is also not enabled yet. Things are moving. When building, just use NEXT branch, 2018.05 + 4.17.y/4.18.y kernel. We have to bring it up here. Debian Stretch is the best target in any case. Bionic is packed with bugs, while Xenial is older than Stretch now. Our Ubuntu is free of corporate junk and AFAIK we only use those non-free packages: iozone3, firmware.

Retry now.

Are you adding/changing anything?

I see. It looks like I failed to merge LUKS encrypting function to the master branch and it is normal that is not yet mentioned in a documentation. I also haven't tried it yet. @zador.blood.stained I didn't pay much attention to its development ... Is it ready to merge and since I already dump the "development" branch ... do I need to restore it to merge it properly with commits and comments? @tyrion Wait that we sort this out first.

In theory, if you manage to install those packages ... it should work this way, yes. But it's better to start with a latest native image.

My lab keyboard is this: ultra cheap RF keyboard. It is clumsy, impractical, battery dies quickly ... It is really hard to type anything, but I don't recall a situation that it didn't work. Sometimes I use it via HUB, sometimes directly.

Change back to the main server. apt.armbian.com

The kernel, which is ours in any case, will be getting upgrades while Jessie userspace is(was) covered by debian.org. They stopped providing public security updates. Debian Stretch upgrade should go standard Debian way ... but be ready to start from a clean Debian Stretch build in case of failure.

We don't deal with LXD but XFCE. Both are just about the same light, while IMO XFCE looks nicer (which is pretty irrelevant I guess). Jessie is EOL, so rather go for Ubuntu Xenial or Debian Stretch ... and install desktop within armbian-config. There is an option "desktop only" which is pure desktop without any apps, no browser, nothing. If you prefer/insist on LXDE it's possible with some general install on top of CLI. (Armbian is Debian/Ubuntu ) ... but if you don't tweak by hand, you will end up with much more stuff than our well-tuned XFCE based desktop.

Hmm, now we need to find why it doesn't work apt update & upgrade before starting this and upgrade to latest then do it again. and logs: armbianmonitor -u

https://docs.armbian.com/User-Guide_Armbian-Config/ armbian-config -> system -> switch to NEXT

... which uses new u-boot 2018.06 where boot environment is/must be saved to a file system. I think the location of env file is hard encoded ... well, you find a bug. If you have time, check if https://github.com/armbian/build/blob/master/lib/compilation.sh#L157 changing to CONFIG_ENV_EXT4_DEVICE_AND_PART="auto:auto" helps.

First bugfix release https://lists.ubuntu.com/archives/ubuntu-announce/2018-July/000234.html Our images should follow from today on.

@Antony Abi Rached Try https://dl.armbian.com/nanopineo/Debian_stretch_next_nightly.7z or just update if you still run previous version.

Quite normal. Upstream u-boot and kernel changes are severe and things break all the time at boards which are under development. IMO they are at least half a year away from the end user stage. Automated builds made for developers and testers are never tested. Manual testing is expensive and nobody covers that. This build might work: https://dl.armbian.com/orangepilite2/Debian_stretch_dev_nightly.7z A modern kernel is still far away from stock functionality. Video driver does not exist yet, so you need to use a serial console.

There are only two versions of this driver as you already discovered. One is stock, from Allwinner and the other is a result of a desperate attempt to make it work on a modern kernel. I don't recall any other wireless driver that would waste community that much time. Do some search on the forum to get a picture: xradio, xr819, zero wireless, ... Rather pick 8811AU (or better), plug it into USB and forget that Opi Zero has a wireless chip.

Source packages are quite big and considering the number different kernels ... this needs some adjustments in packaging logic. Keeping only the most recent source packages or don't care about anything ... but the current download server is at 95% of capacity and is scheduled to move to a new location within two weeks. The main build server is also running low on space and needs some (fast and expensive) space upgrade. It would also be possible to rent out some of our main server capacities. A virtual machine with ready to build Armbian. If there is an interest? This could be possible after space upgrade.

Documentation is always behind/at minimum since we are low on resources. It is stated: "For a comprehensive list of available variables, look through lib/configuration.sh" https://github.com/armbian/documentation/blob/master/docs/Developer-Guide_User-Configurations.md#user-provided-configuration Feel free to make a pull request if you want to extend this part of the documentation.

Wait until tomorrows update. Do apt-update & upgrade - make sure new kernel version is installed, reboot and try again.