Igor

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.

Yes. I sent him this thread.

Failed SD card?

I am also running out of ideas I assume you see all four cores when booting from a clean build?

If you are referring to "file not found /boot/dtb/overlay/-fixup.scr" ... this safe to ignore. This worries me more. I booted this kernel a few days ago on Cubietruck and it seems to work fine. Next step would be to build an image from scratch and see if it helps. We notice some troubles with a certain A20 board on 4.14.y kernel and this might be the issue. I hope this is solved on 4.16.y ... even there is still a lot of work to get there. In a matter of hours, there will be a beta image in here: https://dl.armbian.com/bananapipro/nightly/ Try it.

Try to replace (and recompile) a boot script as well. Get it from here https://github.com/armbian/build/blob/master/config/bootscripts/boot-sunxi.cmd and add rootdev=UUID=xxxx to /boot/armbianEnv.txt if you don't have rootfs on your SD card (logs are also partially broken and can't see that) ... and remove packages which you don't need: linux-dtb-dev-sun8i linux-image-dev-sun8i linux-image-sun8i linux-xenial-root-orangepipc

Try this - go to armbian-config, switch to beta, reboot and move to alternative kernel "dev". Then report, if that makes any change.

U-boot package is critical. Provide output from armbianmonitor -u

But we already did something to fix issues on eMMC cards on a mainline kernel? I can't reproduce this problem so it's irrelevant if I have the board If this could help and if SD card runs on "Rpi level" I don't mind. Push a patch.

Both are ok but before the file was missing ... I don't know if it is related, but we had a short blackout on the main internet connection right around the time of the initial post.