Now that I have a new rig, I need to figure out what to do with the old one. It’s not stable as it crashes after some time. Maybe a test machine of sorts? Following the official guide. I added the -g -flag. Hopefully it’s enough as the BIOS is really limited. I can only set time there!

Now the “SleepingRig” has: -g -flag. I also took it’s MAC-address and shut it down.
On my “MainRig” I installed etherwake. It uses eth0 by default so I need to modify the command a bit.

$ sudo etherwake -i enp2s0 aa:bb:cc:11:22:33

And boom! It works! Amazing!
Now I can automatically start a LAN-machine. It boots into the login-screen, and the -g -flag has reverted to -d.

The above guide shows how to set the -g -flag, but it’s from 2015 and doesn’t use the new netplan that’s default in Ubuntu nowadays. This might be a problem (upd: editing the /etc/interfaces worked for me).

Setting up TightVNC

Normally SleepingRig is running KDE, but the guide that I’m following needs xfce. While KDE has it’s own ‘krfb’, I can live with the bloat. I also want to know how this’ll work.

Everything went well until the section 3. The command doesn’t work! It does ask for the vnc password, but after that there’s just empty terminal.
I also tried to use kde instead of xfce4, but that failed and vnc showed only x. Section 4 worked fine, it’s about creating a systemd service for vnc.

Final Words

All in all I did good progress. There were few issues that still puzzle me, like why did startkde and secure-vnc fail? Well I can work with xfce4 and this machine wont be accessible online so fine.
However Wake-on-LAN, ssh and vnc works so now I can power my devices with a simple terminal command and control them from a different machine!