Werner

Oddly high temperature anyways. @5kft you have some H5 boards?

Of course. And they are already

Does this happen as well when building on Ubuntu Focal native or in a virtual environment (Virtualbox or similar)?

Duplicate

Aight. Since I now had a chance to get kind a overview I suggest to do the following with the tags/prefixes Disallow the use of tags in the bug tracker forums since there is no real use for them. Information like mainline and so on is included in the armbianmonitor output which is mandatory anyways. Allow "help" and "solved" as possible prefixes for topics only where "help" is the default and enforced prefix for new topics. Moderators and the users themselves are allowed to change that if appropriate. This has been implemented in the Allwinner A20 forums only for now for testing purpose. (Note to myself: Add saved action to flip prefix to solved if possible)

Tested with Windows 10 version 1909 (Build 18363.1049) and Ubuntu 20.04 and default 4.9.109 kernel shipped directly from Microsoft. Could run through my autobuild I usually do on remote machine flawless. Needs NO_HOST_RELEASE_CHECK=yes

So the issues has been fixed upstream?

That is quite a temperature. Did you try to add a heatsink (which is recommended for any SBC that is running a load anyways)?

armbianmonitor -u

If you have already experience with Debian/Ubuntu you should not notice much of a difference. Armbian trying to provide as much as "vanilla" experience as possible while adding some tweaks for the individual hardware under the hood. For moving the operating system you can use the sata-nand-install script which is included in any Armbian image. Take note that the sd card might still need to be present since the bootloader will be store there that points to the ssd.

Aight, looking good so far. Now do partitioning or LVM or whatever you want. The SSD is empty.

What's the full output of fdisk -l? I assume it is incomplete.

Do another fdisk -l and check if the partition table is empty.

I wasn't sure about that because it looked to me that nvme0 is the device itself and n1 is the first partition but maybe there was not partition on it beforehand...

You could do something like dd if=/dev/zero of=/dev/nvme0 bs=512 count=1 where nvme0 should be the device itself and not the first partition. You can verify this beforehand with fdisk -l. After that you may have to restart the board to make the "new" partition table recognized.

If you want to start from scratch and have no important data on the device you could simply kill the partition table with dd and start over.

So since the release is out we should catch up here. Open topics are what I found so far: - Merge common issues and peer to peer technical support - Merge H5/A64 and H6 to complete sunxi64 family (?) - creating / updating tags? Per each forum. Done for bugtracker. Other forums need individual attention - ping moderators, remove unresponsive ones?

Sure that would be nice. But stuff is changing frequently and there are simply not enough ressources to keep track and test each and every feature of each and every board over and over....

No worries 30685 BOARD=z28pro 30686 BOARD_NAME="Z28 PRO" 30687 BOARDFAMILY=rockchip64 30688 BUILD_REPOSITORY_URL=https://github.com/armbian/build 30689 BUILD_REPOSITORY_COMMIT=31b56af4-dirty 30690 VERSION=5.90 Anyway, this is quite some output, will take a bit more to dig through... Edit: At line 12625 this Z28 thing occuring the first time. Edit2: Any chance that you could dig your dpkg.log for stuff that happened before Sat 15 Aug 2020 07:49:32 PM CEST?

It has not been announed, more a best guess since the past showed that every fifth new version became LTS. (5.9) 5.4 4.19 4.14 4.9 4.4 ....

Since 5.9 is ahead I'd suggest to focus on that since this will become next LTS kernel.

armbianmonitor -u You can also try the following: increase boot verbosity (see documentation) and connect a serial console. Open it and log its output. Maybe leave it over night if needed. Also try messing with the bluetooth while serial console is connected and collect any output it may throw when crashing.

Log might be incomplete. Please increase the buffer sice of your terminal application and retry. You could also redirect the output into a file.

Try setting a random MAC via armbianEnv.txt in /boot