I've just finished the setup of my Helios4 Batch 3 device and I'm having trouble with the Wake-on-LAN (WoL) feature.
I've followed the instructions on the Wiki, despite the note saying WoL should enable by default as of Armbian 5.77 my 5.91 Debian Stretch installation's eth0 device did not have WoL enabled (sudo ethtool eth0 | grep Wake).
While following the steps to manually enable WoL (sudo ethtool -s eth0 wol g) did change the flag the systemd service didn't persist it across reboots, the service didn't seem to run/apply post reboot and produced errors:
Sep 01 17:18:51 helios4 systemd[1]: Starting Wake-on-LAN for eth0...
Sep 01 17:18:51 helios4 ethtool[1491]: Cannot set new wake-on-lan settings: Operation not supported
Sep 01 17:18:51 helios4 ethtool[1491]: not setting wol
Sep 01 17:18:51 helios4 systemd[1]: Started Wake-on-LAN for eth0.
I ended up following these NetworkManager steps and was able to get the WoL 'g' flag to persist across reboots.
My issue is that after executing the "sudo systemctl suspend" command the Helios4 does appear to suspend (fans go to low speed, network connection drops) but after 1-2 min the device seems to reboot itself automatically and come back online.
I even unplugged the Ethernet cable post suspend to ensure no magic packets were received and the issue persists. Has anyone else encountered this issue or can confirm WoL is working for them?
Everything else about the device seems to function correctly, I did notice some odd behavior with the power supply such that after plugging it into an outlet there is a slight delay before the green light comes on and powers on the Helios4, seems stable once running though.
Thanks.
