Igor

You are not using our images.

If you are using development branch - we are doing changes on a daily base and caches are dropping. In case you are attached to the main branch, things should be cached. Adjust CLEAN_LEVEL , remove deb from it and kernel will not be rebuilt at next run. https://docs.armbian.com/Developer-Guide_Build-Options/

That image 100% works: http://ix.io/17uH If you have troubles, https://docs.armbian.com/User-Guide_Getting-Started/ Nightly images are not subject of a support. Nobody but developers care if they work or not.

I would certainly prefer if we could bring this into the build script. But there is no rush.

https://github.com/armbian/build/commit/c5a87844f8eb5d89f87d3de4d707ecee4bb7c6b2 Try now.

Which one you can't boot? They (legacy/stable) are tested, nightly builds are automated builds for developers and might not always work.

I know but I haven't dug into how this is done now. HDMI works out of the box which means they are probably deprecated. @jernej ?

Build script has a switch from where to install packages, install prebuild or build and install. By default, its prebuild since building takes some time and it is rarely needed to recompile things. At a release stage or for nightly repository I do build them so packages are getting updates. When they are built, they are installed from a local repository. If you manage to merge/add to the existing way of building, most of the problems are solved. Packages are built in chroot https://github.com/armbian/build/blob/development/lib/chroot-buildpackages.sh This part is not very well documented and was done by @zador.blood.stained ... in case I will be unable to provide proper guidance on this.

We host only our packages in a repository with a few exceptions. So far we only did acceleration methods for Allwinner legacy kernel. For example, those are the packages we build for Ubuntu Xenial: Debian Stretch is almost ready/testing & minor fixing and can be used as a default desktop.

That is deprecated and it was removed from armbian-config ... currently present in a beta repository only. Also, armbian-firmware is present if you switch to the beta building BETA="yes".

Yes, it freezes and I hope this will be fixed upstream, like the previous issue with BASH. We don't plan to release Ubuntu Bionic (support) anytime soon so this remains a known issue with low priority. A workaround is to kill the mandb process. Good enough for testing and development purposes.

https://github.com/armbian/config/commit/2992430d263cad9ca18fb773127fb90d628e5ab8#diff-f31297ad208d45c13b6d3d24c66823cdR35 Ubuntu Bionic can be build ... but you need to kill man-db process which hangs during debootsrap process. I made a test image for Odroid XU4 but the network was not configured and probably other things need to be fixed. Addin Bionic remains a low priority and hidden under the expert switch. armbian-config, network management needs further testing and fixing. power management on wireless devices was enabled on some during my last test. IIRC brcmfmac / mainline / h3

Try switching to nightly DEV kernel (4.16.y) ... or back to some older 4.11.y version. Probably better, since 4.16.y is in an early development stage and many other things can simply be broken. I share the frustration

It builds on Xenial. You only need to get latest debootstrap_1.0.95_all.deb Not really arm o.k. / arm64 hangs, yes. I haven't boot the image yet.

And that is normal. You can't log in. You are forced to change a password and create a normal user. Then you can log in. root 1234 1234 your new password your new password again username password password again https://docs.armbian.com/User-Guide_Getting-Started/#how-to-login

Was this meant for Zador or me? Yes, better there.

Nice! I can go back on

I am almost sure it works but I don't recall doing tests. It works on Clearfog with the mainline kernel.

Solidrun u-boot autodetects hardware (dtb select). Generally, it works but for some model, it doesn't. Check two things: - do you have dtb files in /boot/dtb/ - do you have armbianEnv.txt? if not, create it and put fdt_file=some_most_likely_device_tree_blobk.dtb Boot.

Try to (force) SD card filesystem check on some Linux computer. Then save your work to the safe place if you haven't done that already. That won't help in this case since your SD card (filesystem) is most likely corrupted to some degree.

Steven:

I need a week or two to get my mess into the order. Perhaps we write down changes on the way?

- adjust the rest of the patches/drivers https://github.com/armbian/build/tree/development/patch/kernel/sunxi-dev/unresolved - test many other boards - find and fix problems - test them again - find and fix problems - release an update Month(s) of work for a small team to put out a stable release. I already find out that some boards do not boot at all with this kernel. If this kernel works for you, freeze it with armbian-config to prevent overwriting/upgrading and unfreeze and move to "next" branch, unfreeze and update again until something better / stable build is released. In case it still crashes, please report.

Overlay support might be broken on this build which means you need to edit DTS(B) manually and enable USB ports ... development builds have rough edges.

Yes, this image is not intended for deployment. For testing only so rather install it on another SD card and try to crash the board. If it does, describe what you did and try to get some logs if possible.