TDCroPower

  • Posts

    29
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

TDCroPower's Achievements

  1. My upgrade is done. Before... root@192.168.180.5'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: 172.18.0.1 192.168.180.5 CPU temp: 47°C Usage of /: 60% of 15G [ General system configuration (beta): armbian-config ] Last login: Fri Nov 27 02:53:45 2020 from 192.168.180.83 root@helios64:~# After... root@192.168.180.5's password: _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 20.11 Buster with Linux 5.9.10-rockchip64 No end-user support: work in progress System load: 53% Up time: 0 min Memory usage: 8% of 3.71G IP: 192.168.180.5 CPU temp: 43°C Usage of /: 60% of 15G [ General system configuration (beta): armbian-config ] Last login: Fri Nov 27 03:42:24 2020 from 192.168.180.83 root@helios64:~#
  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 [upgradable from: 1.17-3] libkrb5support0/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libldap-2.4-2/stable,stable 2.4.47+dfsg-3+deb10u4 arm64 [upgradable from: 2.4.47+dfsg-3+deb10u3] libldap-common/stable,stable,stable,stable 2.4.47+dfsg-3+deb10u4 all [upgradable from: 2.4.47+dfsg-3+deb10u3] linux-buster-root-current-helios64/buster 20.11 arm64 [upgradable from: 20.08.21] linux-dtb-current-rockchip64/buster 20.11 arm64 [upgradable from: 20.08.21] linux-image-current-rockchip64/buster 20.11 arm64 [upgradable from: 20.08.21] linux-u-boot-helios64-current/buster 20.11 arm64 [upgradable from: 20.08.21] openmediavault/usul,usul,usul,usul 5.5.17-3 all [upgradable from: 5.5.16-1] The changelog is here... https://www.armbian.com/newsflash/armbian-20-11-tamandua/
  3. you can use the boot mode jumper to switch between eMMC (P10) and microSD (P11) boot, see the Helios wiki... https://wiki.kobol.io/helios64/jumper/ @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+dfsg-3+deb10u3 arm64 [upgradable from: 2.4.47+dfsg-3+deb10u2] libldap-common/stable,stable,stable,stable 2.4.47+dfsg-3+deb10u3 all [upgradable from: 2.4.47+dfsg-3+deb10u2] linux-buster-root-current-helios64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-dtb-current-rockchip64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-image-current-rockchip64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-libc-dev/stable,stable 4.19.152-1 arm64 [upgradable from: 4.19.146-1] linux-u-boot-helios64-current/buster 20.08.21 arm64 [upgradable from: 20.08.10] openmediavault-omvextrasorg/buster,buster 5.4.2 all [upgradable from: 5.4.1] openmediavault/usul,usul,usul,usul 5.5.16-1 all [upgradable from: 5.5.12-1] salt-common/usul,usul,usul,usul 3002.1+ds-1 all [upgradable from: 3001.1+ds-1] salt-minion/usul,usul,usul,usul 3002.1+ds-1 all [upgradable from: 3001.1+ds-1] tzdata/stable-updates,stable-updates 2020d-0+deb10u1 all [upgradable from: 2020a-0+deb10u1]
  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 0% /sys/fs/cgroup tmpfs 1.9G 4.0K 1.9G 1% /tmp
  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% 938.7MiB / 3.711GiB 24.70% 0B / 0B 6.22GB / 8.44GB 124 711e02b8f517 iobroker 15.94% 977.9MiB / 3.711GiB 25.73% 0B / 0B 4.79GB / 59.5GB 144 ae4aba42dce4 embyserver 2.94% 928MiB / 3.711GiB 24.42% 0B / 0B 13.2GB / 423MB 39 0150a9f8edfb portainer-ce 0.66% 14.87MiB / 3.711GiB 0.39% 5.95MB / 9.88MB 741MB / 136MB 15
  7. @aprayoga was once again very active, so we can look forward to further optimizations in the next armbian releases ... https://github.com/armbian/build/commit/079b467342fffa7678f903793c589e9fe9fb8b69 https://github.com/armbian/build/commit/5e62c071f0c4bafd1d25ef5f5259bb485935a77e
  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: 172.18.0.1 192.168.180.5 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 192.168.180.83 root@helios64:~# note that the change to eMMC is not necessarily only about speed, mainly about the stability an eMMC has compared to a microSD. A microSD will most likely die faster than an eMMC. Especially if you want to run your system in the background in continuous operation at some point, a microSD in continuous operation is not pleasant.
  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 plastic so that the connector looks like this... The black plastic of the USB-C cable must NOT touch the backside of the Helios64, this ensures that the Cable is 100% plugged in.
  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 of the nand-sata-install script. I think you can do this via their Jira ticket system? edit: unfortunately I did not manage to boot from the microSD again. Does anyone know how to switch from eMMC boot to microSD boot? Solution: with this mount command... mount /dev/mmcblk0p1 /mnt ... you can have access to the microsd files under /mnt... root@helios64:~# ll /mnt/ total 96 lrwxrwxrwx 1 root root 7 Aug 30 20:55 bin -> usr/bin drwxr-xr-x 3 root root 4096 Oct 15 16:47 boot drwxr-xr-x 2 root root 4096 Oct 5 16:04 dev drwxr-xr-x 108 root root 12288 Oct 15 16:49 etc drwxr-xr-x 2 root root 4096 Sep 22 02:38 export drwxr-xr-x 3 root root 4096 Oct 6 02:24 home lrwxrwxrwx 1 root root 7 Aug 30 20:55 lib -> usr/lib drwx------ 2 root root 16384 Oct 5 16:17 lost+found drwxr-xr-x 2 root root 4096 Aug 30 20:55 media drwxr-xr-x 4 root root 4096 Oct 15 16:48 mnt drwxr-xr-x 4 root root 4096 Oct 14 01:18 opt drwxr-xr-x 2 root root 4096 Jul 10 23:04 proc drwx------ 5 root root 4096 Oct 14 01:39 root drwxr-xr-x 2 root root 4096 Oct 5 16:13 run lrwxrwxrwx 1 root root 8 Aug 30 20:55 sbin -> usr/sbin drwxrwxr-x 2 root root 4096 Oct 5 16:05 selinux drwxr-xr-x 2 root root 4096 Sep 22 02:38 sharedfolders drwxr-xr-x 6 root root 4096 Oct 15 16:39 srv drwxr-xr-x 2 root root 4096 Jul 10 23:04 sys drwxrwxrwt 2 root root 4096 Oct 5 16:17 tmp drwxr-xr-x 11 root root 4096 Oct 6 03:22 usr drwxr-xr-x 14 root root 4096 Oct 6 03:12 var root@helios64:~# and to copy the two directories back into the /srv directory just use the following two commands... cp -r /mnt/srv/pillar /srv cp -r /mnt/srv/salt /srv ... and after an reboot its back... root@helios64:~# ll /srv/ total 16 drwxr-xr-x 10 root root 4096 Oct 15 16:40 dev-disk-by-label-nas drwxr-xr-x 2 ftp nogroup 4096 Oct 6 03:06 ftp drwxr-xr-x 3 root root 4096 Oct 6 03:05 pillar drwxr-xr-x 5 root root 4096 Oct 6 03:05 salt root@helios64:~#
  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-omvextrasorg/buster,buster 5.4.1 all [upgradable from: 5.4] root@helios64:~# As soon as my copy of my backup to my new RAID5 is finished I will update and test the part with the eMMC right away! edit: Perfect, the update went through cleanly and installing/booting from eMMC now works without problems. _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 20.08.10 Buster with Linux 5.8.14-rockchip64 No end-user support: work in progress System load: 28% Up time: 1 min Memory usage: 8% of 3.71G IP: 192.168.180.5 CPU temp: 41°C Usage of /: 45% of 15G Last login: Thu Oct 15 16:47:49 2020 from 192.168.180.83 root@helios64:~# df -h Filesystem Size Used Avail Use% Mounted on udev 1.8G 0 1.8G 0% /dev tmpfs 381M 11M 370M 3% /run /dev/mmcblk1p1 15G 6.1G 7.4G 45% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup tmpfs 1.9G 4.0K 1.9G 1% /tmp folder2ram 1.9G 11M 1.9G 1% /var/log folder2ram 1.9G 0 1.9G 0% /var/tmp folder2ram 1.9G 268K 1.9G 1% /var/lib/openmediavault/rrd folder2ram 1.9G 724K 1.9G 1% /var/spool folder2ram 1.9G 14M 1.9G 1% /var/lib/rrdcached folder2ram 1.9G 12K 1.9G 1% /var/lib/monit folder2ram 1.9G 1.3M 1.9G 1% /var/cache/samba tmpfs 381M 0 381M 0% /run/user/0 root@helios64:~#
  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 ... https://wiki.kobol.io/helios64/install/emmc/
  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 one should be seen as fix for the eMMC problem, right? https://github.com/armbian/build/commit/d909a4ea723f5e3e1d1b3e7bb07a2215793725b1 (Verified) https://github.com/armbian/build/commit/bc66f9d835cb8303eb65ea55ac02da69920284f7 (???) edit2: Unfortunately there is nothing to find in the changelog about 20.08.9 yet. Is it perhaps still so fresh? https://docs.armbian.com/Release_Changelog/
  15. I had the same problem on my Mac. But with Windows and PuTTY it works perfectly.