Igor

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.

This is low-level problem and most likely related to your SD card. Odroids are sensitive to them and also brand new UHS type cards can have problems. You will run into the same problem in other distributions. Waste of time if you don't get to the bottom of the problem. Instead of distro hopping, invest your time into education: https://magazine.odroid.com/wp-content/uploads/odroid-c2-user-manual.pdf https://docs.armbian.com/ You might find the cause of the problems there.

It will take some time before this kernel gets to the functionality of the previous one ... I hope we will get better stability. What is missing? I noticed that gserial console is not enabled. I'll try to fix that asap.

Great! I also pin sunxi-dev and sunxi64-dev to 4.16.y to have some reference point and possibly new next if it works better. Testing and/or help with leftovers is welcome.

Sorry. Try this build: https://dl.armbian.com/orangepizeroplus2-h5/archive/Armbian_5.42_Orangepizeroplus2-h5_Debian_stretch_dev_4.16.0.7z

Download to your board and install with: dpkg -i *.deb reboot. You can also switch to nightly (armbian-config -> system) and switch to alternative kernels (dev). My board survived the night with this kernel. I'll keep on with testings.

Try with attached kernel. linux-image-dev-sunxi64_5.42_arm64.deb linux-dtb-dev-sunxi64_5.42_arm64.deb

I am doing some more research on this topic ... I'll update images when done.

... until I tried to run apt update & upgrade. It instantly crashed. I switched now to a (trusted) LAB PSU and after severe stressing board remains stable. I am proceeding to upgrade, switching to beta, desktop install ... According to this, the problem can be solved by reading this section and act accordingly. Nope, it crashed again.

My v1.0 board, this image https://dl.armbian.com/orangepizeroplus2-h5/Ubuntu_xenial_next.7z and connected/powered to USB3 hub boots perfectly fine. With monitor attached. Boards might have a difference in memory quality/speed. This would explain why stock images work. Are you able to get some verbose boot logs on a serial console? Before you go for that, change cables, PSU, monitor and don't attach anything else to the board.

When do you get this? Does it also reboot? Can you describe your setup more in details?

Me neither. Images are tested multiple times and they work. Bash scripts are not really an appropriate reference nor help in diagnostic this problem. Procedure at login is as follows: root 1234 1234 yournewpass yournewpass Do this way and you should be fine. Just to make sure I tested those images once again: https://dl.armbian.com/odroidc2/Ubuntu_xenial_default_desktop.7z Boot log: http://ix.io/16qp https://dl.armbian.com/odroidc2/Ubuntu_xenial_default.7z Boot log: http://ix.io/16qx Edit: After this fix, upgrading from legacy to mainline also works fine.

At least we have a working eth, USB ports, SD card: https://github.com/armbian/build/pull/914 (merged into development branch)

Orange Pi Mini 2 was never directly supported and yes, you probably can just use the image from Orange Pi 2. Disappeared boards appear here: https://www.armbian.com/deprecated/

If you don't use our kernel, this function might not be supported.If you do, check this part for reading things: https://github.com/armbian/build/blob/master/packages/bsp/common/etc/update-motd.d/30-sysinfo#L53-L78 Another option is talking to AXP chip via I2C which is a bit more complicated. It was brought up once - do some forum search.

A64 with legacy kernel supports only a few screen sizes. For example on H3, which is most popular, more were added by us/community (example). Do some forum search and you will get info how this was made. The first step is digging into video driver, adding this resolution and then you can start using it.