On 12/10/2018 09:13 AM, Thomas Seeling via blfs-support wrote:
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
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
