Igor

It used to work a year ago ... if it breaks, you will need to dive into the u-boot source code to see why it breaks. Perhaps this can be solved in a minute, perhaps you need hours. For Armbian, this patch is not relevant, so it is not maintained.

Armbian logo should be displayed in uboot by default. At lest on most recent assembly. Image is read from /boot by another patch. Wrote on mobile

Full at power on, going low when systems boot up and going up while stressing the board is expected ... and wanted behavior. If it works this way all is fine.

It seems that you have fake SD cards. Throw them away/send back. There are no other ways.

Not sure if its drop-in compatible with current bootloader but you get an idea: https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-sunxi/remove-boot-messages-from-hdmi.patch.disabled

This feature is not enabled by default. You need to use armbian-config -> system -> hardware settings Regarding mono/stereo I don't know from my head. If you need some quality, an external I2S sound card is recommended.

I noticed and briefly checked. Perhaps here is the problem: https://github.com/armbian/build/pull/1069

Probably not. Check here: https://github.com/armbian/build/tree/master/packages/extras-buildpkgs/hostapd/debian

It was not meant that way. We have certain minimum requirements to support a board and those are not met. We need more than one board and somebody accountable. And someone as a backup. I know. We do our own, much more detail, inspection: https://github.com/ThomasKaiser/sbc-bench/blob/master/Results.md Well, Allwinner is ... common. Those boards have some shortcomings which makes them less interesting than siblings - lack of a power regulator (impact on heating, power consumption and performance) and micro USB powering (stability).

I hope I didn't miss anything. https://github.com/armbian/build/commit/735a3679e2de12db555e17b0485f99f86a1d106a

Yes, that is planned, but we still have weeks - we also don't need to jump on v4.19.0 ... It's DEV kernel and the idea is that DEV becomes NEXT when the time is right. Which is even more distant. Since 4.19.y is the next LTS it will be worth to prepare it and port support from more recent versions. 4.19.y is for 2019

You must have some very old installation. Have you changed anything by hand? Try this - make and boot from SD card, mount eMMC and copy /boot/boot.* to your eMMC /boot section.

It should also be in a stable build. Since this feature is not really essential, I will not investigate at this moment why it is not there. We provide nightly builds and build tools. Use that first.

No, I haven't got back to this problem yet. Not sure when I will be able.

I had weeks of long shifts due to the last major upgrade and I will do my best to do nothing for some time Then I have a pile of non-technical tasks to cope with.

Peek into: /etc/network/interfaces.d

That's an old build ... fan control works properly on current stable 4.14.70-mvebu build (NEXT kernel branch) ... which is recommended build in any case. OLED display must also work on this kernel. Debian Stretch based OMV is also a better choice now.

Check the whole log. It's NEXT upgraded to DEV. The one that is in a stable repository.

Our build on my board works without issues: http://ix.io/1nb6

Can't reproduce with our 4.18.y kernel hostapd combo (upgraded from 4.14.y) ... I tried with onboard Broadcom wireless (Bananapi M2+) and Alfa AC via USB. In both cases, I didn't have any troubles. Logs can be observed here: http://ix.io/1naG

It might work on H3 with the legacy kernel but never tried such a scenario. Mainline kernel support is WIP at the moment.

No. It would be implemented.

4.14.y is more or less maintaining only while 4.18.y is WIP and will remain in that stage for months. Next LTS is 4.19.y anyway. Probably there is no regulator support?

If you develop this feature.

Configuration not, but there were changes on the lower level which could provoke such weird problems. I would try to boot the system with the previous version of u-boot, than leaving u-boot and change kernel ...