Werner

You can give "usbmount" a try.

I do not own this board so no idea.

I found some information about bluetooth here regarding firmware for a certain chip. https://linux-sunxi.org/Xunlong_Orange_Pi_3

There should not be any need to change anything. Armbian comes with optimization to extend sd cards life. Check the section performance tweaks for more information: https://docs.armbian.com/

Feel free to create a PR to https://github.com/armbian/build including the changes you wish.

Yeah....kind of root@honeypot:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 13:47:48: 1008MHz 0.21 3% 0% 3% 0% 0% 0% 33.5°C 0/6^C root@honeypot:~# uname -a Linux honeypot 5.3.0-rc3-sunxi #5.94 SMP Sat Aug 17 13:17:44 UTC 2019 armv7l GNU/Linux Interesting. RC3 seems to be okay

The barrel plug is not flawless either. I run my OPi1+ with those from a 5V 3A. Though when I connect an external hard drive to the USB the voltage drops far enough to prevent the spin-up. As we know Xulong mostly passes the input voltage unfiltered through I connected the microUSB with a second cable to the same power source as well and the hard drive could start without issues.

I always freeze firmware updates when using custom build kernel images on my boards to avoid issues like this.

https://github.com/armbian/build/pull/1541

You can always give 5.3-rcX kernel a shot if you haven't already. You can find some prebuild debs and images following the link below.

Awesome. Starting a new build round right now

Megous 5.3 branch has been pushed from rc3 to rc6 and it seems like we have a regression somewhere. Did not have a chance to look further yet. == kernel == arch/arm64/Makefile:56: CROSS_COMPILE_COMPAT not defined or empty, the compat vDSO will not be built arch/arm64/Makefile:56: CROSS_COMPILE_COMPAT not defined or empty, the compat vDSO will not be built arch/arm64/boot/dts/allwinner/overlay/sun50i-a64-spi-spidev.dts:20.11-25.6: Warning (spi_bus_reg): /fragment@1/__overlay__/spidev: SPI bus unit address f ormat error, expected "0" arch/arm64/boot/dts/allwinner/overlay/sun50i-a64-spi-spidev.dts:34.11-39.6: Warning (spi_bus_reg): /fragment@2/__overlay__/spidev: SPI bus unit address f ormat error, expected "0" arch/arm64/boot/dts/allwinner/overlay/sun50i-h5-spi-spidev.dts:20.11-25.6: Warning (spi_bus_reg): /fragment@1/__overlay__/spidev: SPI bus unit address fo rmat error, expected "0" arch/arm64/boot/dts/allwinner/overlay/sun50i-h5-spi-spidev.dts:34.11-39.6: Warning (spi_bus_reg): /fragment@2/__overlay__/spidev: SPI bus unit address fo rmat error, expected "0" arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi:200.20-210.5: ERROR (duplicate_label): /soc/ths@1c25000: Duplicate label 'ths' on /soc/ths@1c25000 and /soc/ thermal-sensor@1c25000 ERROR: Input tree has errors, aborting (use -f to force output) make[2]: *** [arch/arm64/boot/dts/allwinner/sun50i-h5-bananapi-m2-plus.dtb] Error 2 make[2]: *** Waiting for unfinished jobs.... arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi:200.20-210.5: ERROR (duplicate_label): /soc/ths@1c25000: Duplicate label 'ths' on /soc/ths@1c25000 and /soc/ thermal-sensor@1c25000 ERROR: Input tree has errors, aborting (use -f to force output) make[2]: *** [arch/arm64/boot/dts/allwinner/sun50i-h5-bananapi-m2-plus-v1.2.dtb] Error 2 arch/arm64/boot/dts/allwinner/overlay/sun50i-h6-spi-spidev.dts:20.11-25.6: Warning (spi_bus_reg): /fragment@1/__overlay__/spidev: SPI bus unit address fo rmat error, expected "0" arch/arm64/boot/dts/allwinner/overlay/sun50i-h6-spi-spidev.dts:34.11-39.6: Warning (spi_bus_reg): /fragment@2/__overlay__/spidev: SPI bus unit address fo rmat error, expected "0" make[1]: *** [arch/arm64/boot/dts/allwinner] Error 2 make: *** [dtbs] Error 2 make: *** Waiting for unfinished jobs....

In first place I wanted to store the debs I created on Github as well, though dropped the plan as the file size limitations is quite annoying. That is why I utilized owncloud to store and share them.

Xulung states that the hardware is basically identical. They just rearranged stuff to reduce wire length and various other optimizations like that. So yes, the software is the same in every aspect.

No. If the serial console is working perfectly fine on one SBC it should work on the alleged broken one the same way. Anyway you can do the test with Win7 just to content the company. On the bottomline it is to mention that these boards are dirt cheap and you basically make a tradeoff. For the difference you may pay for an equivalent board from another company you get proper software AND customer support.