• Content Count

  • Joined

  • Last visited

Everything posted by TDCroPower

  1. My upgrade is done. Before... root@'s password: _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 20.08.21 Buster with Linux 5.8.17-rockchip64 No end-user support: work in progress System load: 8% Up time: 16 days 6:46 Memory usage: 77% of 3.71G IP: CPU temp: 47°C Usage of /: 60% of 15G [ General system configuration (beta): armbian-c
  2. After the official release of Armbian 20.11 today I would like to collect feedback if and how the firmware runs on the Helios64. Is it possible to upgrade already or should we Helios64 owners wait? apt-get lists these already... armbian-config/buster,buster 20.11 all [upgradable from: 20.08.22] armbian-firmware/buster,buster 20.11 all [upgradable from: 20.08.22] libgssapi-krb5-2/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libk5crypto3/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libkrb5-3/stable,stable 1.17-3+deb10u1 arm64 [upgradabl
  3. you can use the boot mode jumper to switch between eMMC (P10) and microSD (P11) boot, see the Helios wiki... @Helios Team... what is the current image status? Is it now possible to upgrade from 20.08.10 to the current version? By now we are already at 20.08.22... armbian-config/buster,buster 20.08.22 all [upgradable from: 20.08.10] armbian-firmware/buster,buster 20.08.22 all [upgradable from: 20.08.10] libfreetype6/stable,stable 2.9.1-3+deb10u2 arm64 [upgradable from: 2.9.1-3+deb10u1] libldap-2.4-2/stable,stable 2.4.47
  4. use the command df -h to show from which storage the system was loaded. If it says /dev/mmcblk1p1 it is the eMMC and if it says /dev/mmcblk0p1 it is still your microSD. You can also tell from the memory size whether it is the eMMC (has 15GB) or your microSD. root@helios64:~# df -h Filesystem Size Used Avail Use% Mounted on udev 1.8G 0 1.8G 0% /dev tmpfs 381M 37M 344M 10% /run /dev/mmcblk1p1 15G 7.8G 5.7G 59% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 1.9G 0 1.9G
  5. Soldering? No problem here ! I can help users from Germany to fix their helios board once the solution is released.
  6. how did you display this ingenious output? I currently have a consumption of 88-90% on my Helios64 and suspect that a container is at fault. edit: ok with docker stats I got a similar output, but yours is even more "neat". CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 7b42ac796d6f pihole 0.13% 18.92MiB / 3.711GiB 0.50% 0B / 0B 2.87GB / 621MB 21 3d3d14ccf50d unifi-controller 3.85% 93
  7. @aprayoga was once again very active, so we can look forward to further optimizations in the next armbian releases ...
  8. @Bethlehem my Helios64 installation with 3x WD Red 4TB, OMV und Docker nativ -> Containers: Portainer, pihole, iobroker, emby, unifi controller, netdata... runs at 45°C Welcome to Armbian 20.08.10 Buster with Linux 5.8.14-rockchip64 No end-user support: work in progress System load: 20% Up time: 1 day 9:02 Memory usage: 61% of 3.71G IP: CPU temp: 45°C Usage of /: 59% of 15G [ General system configuration (beta): armbian-config ] Last login: Sun Oct 18 03:35:55 2020 from root@helios64:~#
  9. After several weeks of testing and trying I finally put my Helios64 into production. With the 20.08.10 and the possibility to run the firmware over the eMMC I can finally sleep more calmly again. The front view mounted: The back view connected: And to prevent my wife from killing me because there is a lighting party going on in the hallway I taped the front LEDs with insulating tape... And for all who have problems with the included USB-C cable at the USB-C port of the Helios64. You have to remove the pla
  10. yes I have. I started it via armbian-config >>> System >>> Install >>> "2 Boot from eMMC - system on eMMC", but it is the same script that is behind it. Before that I installed OMV and Docker natively on the system and pihole, unifi controller, iobroker and emby server as container. @antsu you are probably right, because under /srv I cant't find my OMV -> SMB Shared Folders... root@helios64:~# ll /srv/ total 0 root@helios64:~# i try to boot from the microSD again to save the 2 directories. You should tell the armbian team or the dev
  11. The new firmware 20.08.10 is finally available via apt-get... root@helios64:~# apt list --upgradable Listing... Done armbian-config/buster,buster 20.08.10 all [upgradable from: 20.08.8] armbian-firmware/buster,buster 20.08.10 all [upgradable from: 20.08.8] linux-buster-root-current-helios64/buster 20.08.10 arm64 [upgradable from: 20.08.8] linux-dtb-current-rockchip64/buster 20.08.10 arm64 [upgradable from: 20.08.8] linux-image-current-rockchip64/buster 20.08.10 arm64 [upgradable from: 20.08.8] linux-u-boot-helios64-current/buster 20.08.10 arm64 [upgradable from: 20.08.8] openmediavault-omv
  12. thanks for the feedback. Will be available again after about 24h via apt-get. Currently the 20.08.9 is still offered... root@helios64:~# apt list --upgradable Listing... Done armbian-config/buster,buster 20.08.9 all [upgradable from: 20.08.8] armbian-firmware/buster,buster 20.08.9 all [upgradable from: 20.08.8] linux-buster-root-current-helios64/buster 20.08.9 arm64 [upgradable from: 20.08.8] root@helios64:~# edit: the new wikis are even already online ...
  13. Cool, very good news! Is a fresh install from "20.08.8" also urgently necessary or can we also upgrade to "20.08.10" with an apt-get upgrade?
  14. i checked today and saw a new 20.08.9 in the updates. Has anything new been implemented or fixed in the new 20.08.9 that might interest us as Helios64 owners? root@helios64:~# apt list --upgradable Listing... Done armbian-config/buster,buster 20.08.9 all [upgradable from: 20.08.8] armbian-firmware/buster,buster 20.08.9 all [upgradable from: 20.08.8] linux-buster-root-current-helios64/buster 20.08.9 arm64 [upgradable from: 20.08.8] root@helios64:~# edit1: I have found 2 commits from aprayoga, have they perhaps already been implemented in 20.08.9? If so, the first o
  15. I had the same problem on my Mac. But with Windows and PuTTY it works perfectly.
  16. very good, just these 2 features are for many probably the most important to be able to set it up quickly and neatly.
  17. because my first microSD has a satisfying image i got a second microSD today to test it. I will try to reproduce my steps to copy + boot from the eMMC. I have here still the 20.08.4 image for reference. Tomorrow I have to set up my test setup to test more effective/faster and give feedback again. @aprayoga is it true what @gprovost has written here that you have already fixed the eMMC problem and are working on a suitable Wiki? If that's true then theoretically I can save myself the test run and just wait for your update. Unless you would like to get further feedback o
  18. @aprayoga Oh sorry I think there is an understanding problem. The system can always boot from the microSD! When i install everything on the eMMC with nand-sata-install and reboot it has booted from the eMMC... the microSD stays plugged in! If I shut down the system, removed the microSD and rebooted it did not boot anymore. When I plugged in the microSD and booted it again it showed me that it has mounted from the eMMC. See my post early Topic 2
  19. Thanks for the answer. As shown in my previous posts I somehow managed to get the eMMC partition loaded and in some places this was displayed correctly. The only problem was that the microSD had to stay connected, which surprised me a bit. I'm happy to share my feedback with everyone so that we can all benefit from it. If I annoy you with this I am sorry.
  20. Right and there the option "2 Boot from eMMC - system on eMMC". The only thing I haven't done this time is to set the jumper P11. Is it possible to do something with the file /boot/armbianEnv.txt and changing the variable "rootdev"? Because in the /boot/boot.scr the default value for "rootdev" -> "/dev/mmcblk0p1" is used and this is the partition of the microSD.
  21. Did the team change anything about the boot variant with the 20.08.8? With the previous version I was able to boot from the eMMC with a detour and now I can't boot anymore, although the image was transferred via nand-sata-install!
  22. Such short feedback on the new 20.08.8... Runs much better/stable so far. Installing OMV and Docker via armbian-config worked fine... perfect! Writing the image from microSD to eMMC with "nand-sata-install" or "armbian-config" >> System >> Install also worked, but I couldn't boot from eMMC anymore.
  23. i will flash later the new fresh image, the image file is ready from armbian download site but not via apt-get. I have updated with „apt-get update && apt-get upgrade“ + „reboot“
  24. I'm looking forward to see how far I notice the changes, I'm already on the "20.08.7". Is it normal that under "uname -a" the used version is not shown? Welcome to Armbian 20.08.7 Buster with Linux 5.8.11-rockchip64 No end-user support: work in progress System load: 2% Up time: 54 min Memory usage: 5% of 3.71G IP: CPU temp: 65°C Usage of /: 16% of 15G [ General system configuration (beta): armbian-config ] Last login: Mon Oct 5 20:21:08 2020 from root@helios64:~# uname -r 5.8.11-rockchi
  25. And unfortunately already the next problem. I couldn't start Docker successfully so far, so far all attempts to find a solution have failed. Here is the error message when I try to start Docker or the message as not successfully installed... root@helios64:~# apt-get install docker-ce docker-ce-cli Reading package lists... Done Building dependency tree Reading state information... Done Recommended packages: cgroupfs-mount | cgroup-lite pigz libltdl7 The following NEW packages will be installed: docker-ce docker-ce-cli 0 upgraded, 3 newly install