[blfs-support] wake-on-lan fails since kernel 4.19

[Thomas Seeling via blfs-support]

Hallo,


I had WOL successfully configured on my machine, and out of the blue it stopped working. I can't remember changing anything in that regard except switching to kernel 4.19.
My mainboard is Asrock B75GL-M with Realtek Gigabit chip.
ethtool says it supports "pumbg" flags, and I had it configured as mode "g" (magic packet).

Is my suspicion correct that it might be some behaviour change in the kernel?
A colleague suggested that the WOL state had to be repeated after each boot, but I didn't do that before, so my only idea is the kernel update I did.

I went to the network initialization scripts (ifconfig.$if, /sbin/ifup etc.) but so far I'm not sure where exactly to put the additional ethtool command. Any suggestions please?

Tschau...Thomas

[Bruce Dubbs via blfs-support]

Post by Thomas Seeling via blfs-support
Hallo,
I had WOL successfully configured on my machine, and out of the blue it stopped working. I can't remember changing anything in that regard except switching to kernel 4.19.
My mainboard is Asrock B75GL-M with Realtek Gigabit chip.
ethtool says it supports "pumbg" flags, and I had it configured as mode "g" (magic packet).
Is my suspicion correct that it might be some behaviour change in the kernel?
A colleague suggested that the WOL state had to be repeated after each boot, but I didn't do that before, so my only idea is the kernel update I did.
I went to the network initialization scripts (ifconfig.$if, /sbin/ifup etc.) but so far I'm not sure where exactly to put the additional ethtool command. Any suggestions please?

You don't say whether you are running sysV or systemd. The comments
below are for sysV.

You can put extra commands wherever you think best. Your disto, your
rules. That said, /etc/sysconfig/ifconfig* would not work directly as
it is just a set of variables. You might want to add something there
like WAKEONLAN=1 and use that in /etc/lsb/ipv4-static with an if
statement in the up) case.

if [ [ -n "$WAKEONLAN" ]; then
ethtool ...
fi

Of course other methods are possible.

-- Bruce

[Thomas Seeling via blfs-support]

Hallo,

You don't say whether you are running sysV or systemd.  The comments
below are for sysV.

I don't like systemd at all, I'm using sysv and I'm really fond of the
concept.

like WAKEONLAN=1 and use that in /etc/lsb/ipv4-static with an if
statement in the up) case.
if [ -n "$WAKEONLAN" ]; then
  ethtool ...
fi

sounds like the most reasonable place. I wasn't quite sur ewhether to
add my code to "factory" scripts or have something separate for my
customizations.

I'd like to see something like "local plugins" in the LFS basic scripts
so that there's a generic hook for local modifications, something like

test -f /etc/rc.sys/${script}.local && . /etc/rc.sys/${script}.local

Ok, thanks for the general idea, I think I'm going that direction.

Apart from that: any idea why WOL suddenly stopped working?

Tschau...Thomas

[Ken Moffat via blfs-support]

Post by Thomas Seeling via blfs-support
Apart from that: any idea why WOL suddenly stopped working?
Tschau...Thomas

You said it stopped working with 4.19, but you did not specify which
point release.

If your network chip uses the r8169 driver, there was a revert in
4.19.1 to fix broken WOL from S5 (poweroff).

And if you happen to use the BLK-MQ i/o scheduler, 4.19.8 contains
the fix for filesystem corruption.

Beyond that, I know nothing about the changes in the 4.19 releases,
except that the -rc kernels (and .0, .3) worked for me on the
machines where I tried them - but WOL is not something I use.

ĸen