This is so weird. Something is messing up the wol settings at the end of the boot process and most likely also during shutdown.
Directly after boot I see that the wol@enp39s0 service was excecuted successfully:
4# systemctl status wol@enp39s0
● wol@enp39s0.service - Wake-on-LAN for enp39s0
Loaded: loaded (/usr/lib/systemd/system/wol@.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Sun 2020-10-25 15:33:22 CET; 44s ago
Process: 4100 ExecStart=/usr/bin/ethtool -s enp39s0 wol g (code=exited, status=0/SUCCESS)
Main PID: 4100 (code=exited, status=0/SUCCESS)
Okt 25 15:33:22 rakete systemd[1]: Starting Wake-on-LAN for enp39s0...
Okt 25 15:33:22 rakete systemd[1]: wol@enp39s0.service: Succeeded.
Okt 25 15:33:22 rakete systemd[1]: Finished Wake-on-LAN for enp39s0.
But the status of the network device is not reflecting this.
9# ethtool enp39s0 | grep Wake
Supports Wake-on: pumbg
Wake-on: d
When I now start the wol@enp39s0 service again:
systemctl start wol@enp39s0
The settings are correct:
11# ethtool enp39s0 | grep Wake
Supports Wake-on: pumbg
Wake-on: g
Something is reverting what wol@enp39s0` is doing during boot. And I am afraid that something similar happens during shutdown so that the results of the manual wol@enp39s0 run are not surviving.
Any idea how I can find out which sersvice or script is messing with the network device? NetworkManager is deinstalled.