@Gael et al.

I’m post a more descriptive post to summarize what the issue is. I don’t know how to fix (so I’ll start there.)

TL;DR;

Linux Kernel is putting a volatile Firmware on the NIC. This happens when FOS loads and the kernel begins associating the drivers. On restart, the firmware is still existing on the NIC from the Kernel. When Windows Boots, it re-flashes the volatile firmware so subsequent elements will work. Or a full power pull will do too (completely cold boot.)

Basis:

This particular issue, is due to Linux Kernel having a firmware defined for the NIC. This is volatile. This means when power is pulled, the firmware will no longer be present and normal actions will work properly.

While the machine is in FOS, the linux kernel hands it a temporary Firmware File and this is what’s causing the strangeness with the NIC.

Pulling the power cord causes the firmware to wipe. Similarly, if booting to Windows immediately after, and then powering off the machine, it should WOL. This is because Windows has a FW being applied when it loads, overwriting whatever the Linux Kernel pushed.

@emryz @ragnurenson From my point of view it’s all working fine. See the screenshot below. You are right that the power management task is not in the scheduledTasks table. I was on the wrong track with that when I had a brief look at this last time. As mentioned by @emryz the power management tasks show up in the same view where you schedule those for the host. See my screenshot below.

@emryz I can imagine that some kind of AdBlock add-on in the browser could make this view disappear. We had a very strange case where one single text field was missing just because of an AdBlock add-on. Please disable these and see if it works for you.

Note: I corrected my other post so when people come along and find this, they don’t get confused.

laa.jpg

@fdrouard wol/wol.php path no longer exists.