Werner

Members
  • Content Count

    196
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Everything posted by Werner

  1. Welcome to Debian Buster with Armbian Linux 5.3.0-sunxi64 System load: 0.00 0.00 0.00 Up time: 22:28 hours Memory usage: 9 % of 988MB IP: CPU temp: 54°C No heat sink, about 22°C environment.
  2. From Armbians point of view it is still the dev branch. Though the linux source repository has been updated to 5.3.0 stable release.
  3. I have two OPi1+ and both running fine on 5.3.0 and earlier ran fine on 5.2.x as well... Just updated one of those SBCs to the 5.3.0-sunxi64 kernel image I built earlier today (and is available to the public, see link below) and is booting fine.
  4. Nice. New builds, including freshly released Linux 5.3.0, are ready.
  5. You can give "usbmount" a try.
  6. I do not own this board so no idea.
  7. I found some information about bluetooth here regarding firmware for a certain chip. https://linux-sunxi.org/Xunlong_Orange_Pi_3
  8. 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/
  9. Feel free to create a PR to https://github.com/armbian/build including the changes you wish.
  10. 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
  11. 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.
  12. I always freeze firmware updates when using custom build kernel images on my boards to avoid issues like this.
  13. 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.
  14. Awesome. Starting a new build round right now
  15. 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....
  16. 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.
  17. 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.
  18. 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.
  19. Usually you should have one kernel image only installed on your SBC. armbian-config should handle this for you. Some things looking strange indeed. Any chance to start over with a fresh Armbian?
  20. This hint is quite old, though I do not know about its current status. On the bottomline H6 is still under development and not come with any official support.
  21. You can give 5.3.0-rc3 a shot if you want. You can find precompiled packages for various OrangePi boards following the link below (in my signature). Offtopic: For better encryption performance you should grab a ARM64 board, like something based on the Allwinner H5 or H6 SoC. root@orangepioneplus:~# cryptsetup benchmark --cipher xchacha20,aes-adiantum-plain64 # Tests are approximate using memory only (no storage IO). # Algorithm | Key | Encryption | Decryption xchacha20,aes-adiantum 256b 136.5 MiB/s 152.3 MiB/s Linux honeypot3 5.3.0-rc3-sunxi64 #5.94 SMP Sat Aug 17 14:21:45 UTC 2019 aarch64 GNU/Linux
  22. /bin/sh: 1: scripts/basic/fixdep: Exec format error I am actually not that deep in this, though I guess armhf and armeb are incompatible architectures...