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/

I haven't done any particular testing of 20.11 but I've been running it since Wednesday 10:30AM (UTC+2) without any issues.

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:~#

 

Yes, you can upgrade to 20.11.

 

I upgraded and it's working fine for me.

I have configures iSCSI and replaced about 6 virtual machines by moving their services into the Helios64.

I have to say that PostgreSQL 13 runs very well with the loads being spread across all cores on the system.

Now I just have figure out how to reconfigure the UniFi controller to run either as a docker image or as another service (leaning towards a container at this point).

Upgraded today with no issues to be seen as of yet. Got plex and jellyfin in docker. It did for some reason change my encrypted device from /dev/md127 to /dev/md0. But that was about it.

Another small upgrade to 20.11.1

 

 

19 hours ago, Igor said:

Another small upgrade to 20.11.1

 

 

 

❯ sudo systemctl status helios64-heartbeat-led.service
● helios64-heartbeat-led.service - Enable heartbeat & network activity led on Helios64
   Loaded: loaded (/etc/systemd/system/helios64-heartbeat-led.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2020-11-28 23:19:56 PST; 13min ago
  Process: 1158 ExecStart=/usr/bin/bash -c echo heartbeat | tee /sys/class/leds/helios64\:\:status/trigger (code=exited, status=0/SUCCESS)
  Process: 1177 ExecStart=/usr/bin/bash -c echo netdev | tee /sys/class/leds/helios64\:blue\:net/trigger (code=exited, status=1/FAILURE)
 Main PID: 1177 (code=exited, status=1/FAILURE)

Nov 28 23:19:56 helios64 systemd[1]: Starting Enable heartbeat & network activity led on Helios64...
Nov 28 23:19:56 helios64 bash[1158]: heartbeat
Nov 28 23:19:56 helios64 bash[1177]: netdev
Nov 28 23:19:56 helios64 bash[1177]: tee: '/sys/class/leds/helios64:blue:net/trigger': Invalid argument
Nov 28 23:19:56 helios64 systemd[1]: helios64-heartbeat-led.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 23:19:56 helios64 systemd[1]: helios64-heartbeat-led.service: Failed with result 'exit-code'.
Nov 28 23:19:56 helios64 systemd[1]: Failed to start Enable heartbeat & network activity led on Helios64.

 

To activate the network activity led load kernel module ledtrig-netdev and restart helios64-heartbeat-led.service.

 

 

7 hours ago, Gammel said:

To activate the network activity led load kernel module ledtrig-netdev and restart helios64-heartbeat-led.service.

 

 

sudo insmod /lib/modules/5.9.11-rockchip64/kernel/drivers/leds/trigger/ledtrig-netdev.ko
sudo systemctl restart helios64-heartbeat-led.service

 

@Zageron run

echo ledtrig-netdev | sudo tee -a /etc/modules

add the modules into auto load list.

 

apparently /etc/modules is not modified during upgrade.

10 minutes ago, aprayoga said:

@Zageron run

echo ledtrig-netdev | sudo tee -a /etc/modules

add the modules into auto load list.

 

apparently /etc/modules is not modified during upgrade.

 

Ah, thank you.