AndrewDB

There are many possible reasons for that.

I have also experienced that, it's the kernel random generator that requires a source of entropy to initialize the driver. There are a number of workarounds , google for it.

Try a different kernel version (earlier/later).

Your box is bricked. See how to unbrick on Freaktab website. or google "how to unbrick my Amlogic tv box". Also, please don't post off-topic anymore in this thread, since at this point this has nothing to do with Armbian.

Try to flash the Android firmware to a different (preferably earlier) version.

Then just copy the kernel, initrd and modules from any of Oleg's images that fits your needs.

That is completely unrelated to Armbian. In your case, I would suggest trying an Ubuntu desktop image, it shouldn't take more than 5 minutes to get a VNC server working on it. Firefox should be working out of the box and Chrom(ium) is an extra 3-minutes install.

So you want to update the kernel? The way I do that is that I compile and install a kernel I download from Oleg's (balbes150) repository on GitHub. This has the advantage that I can configure the kernel to fit exactly my needs. Depending on your hardware you can also download, configure, compile and install an unpatched mainline kernel from kernel.org. Either way, you get exactly the kernel version you want with exactly the options you need. BUT If the kernel you already have installed and booting from eMMC is working fine, there is no reason to update.

@klimbo I don't have any Km8P box with Android 8.0, and as far as I know Mecool does not have an Android image for Android 8.0. So I am not sure your question makes any sense.

Are you trying to upgrade to a new Armbian release, a new Debian/Ubuntu release, or to a new kernel? Because these are three different things. And obviously there is a way to upgrade each of these.

I checked pihole, since it's the main difference between your setup and mine (I assume you are using Armbian Ubuntu 18.04 in server mode). Pihole by default is setup to do both IPV4 and IPV6 blocking, but if you are running your internal net on IPV4 I suggest you completely disable IPV6 in the kernel of your km8p box, and disable IPV6 blocking in pihole, that will eliminate one possible source of crashes. Pi hole should continue to work just fine. To disable IPV6 in the Linux kernel, just type the following commands: sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1 sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1

Are you using the WiFi or ethernet to connect to the net? Also try a different power brick if you have one, you could have received a bad one. andrew@km8p1:~$ uptime 22:12:51 up 23 days andrew@km8p2:~$ uptime 22:13:38 up 47 days andrew@km8p3:~/Development/Armbian-NG$ uptime 22:14:01 up 47 days

@NicoD I noticed you have benchmarked it against other SBC's using blender, but how long does your PC take to render the same file and what kind of CPU does it have?

Just a weekly update on the progress on Armbian-NG, as of April 10 2019: I pushed version 0.05 yesterday. The public repository now holds a total of 482 lines of Python code and 102 lines of documentation (in markdown format). Almost all the new code is the TUI (terminal user interface), which tries to copycat as much as possible Armbian's ncurses-based dialogues using a Python library called npyscreen. This took me longer to program than I expected because I was held back by a bug "undocumented feature" in npyscreen... I estimate the TUI code is 80% completed now. I also wrote some "internal documentation" (notes) for my personal reference, which I have not uploaded to the repository. But if anybody wants to contribute, this is available, just PM me. After the past week's effort into programming the TUI for Armbian-NG, I have renewed respect and appreciation for the amazing programming work done by Igor in writing Armbian. It truly is a wonder! If I am able to do 10% of what Igor did I will be proud already! Over the next week I intend to let the TUI code settle down a little bit and work mainly on the kernel downloading and compilation steps.

NEXT uses 5.1 mainline kernel which does not have dtb for any TV box, I believe. You'll have to write your own dts (device tree source) file, and compile it to a dtb. Or you can send a MagicSee N6 Max to Oleg and ask him to write one!