[Solved] WOL issue again - I solved it once

Issues related to applications and software problems and general support
Post Reply
lightman47
Posts: 1521
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

[Solved] WOL issue again - I solved it once

Post by lightman47 » 2022/01/05 17:13:06

RHEL 8 fully updated. I recently changed this ancient (AMI BIOS v2.5 042015) machine's HDD to an SSD, then reinstalled dual-boot with Windows 10. I had WOL working on the HDD (and don't remember exactly how I did it - it wasn't very difficult though). The BIOS settings haven't changed yet with the new install there's now no link light and the machine will not wake!

I did "sudo ethtool -s enp2s0 wol g" to get wol turned back on - am at a loss how it got disabled**! Now it shows

Code: Select all

 sudo ethtool enp2s0
Settings for enp2s0:
	Supported ports: [ TP	 MII ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Half 1000baseT/Full
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Half 1000baseT/Full
	Advertised pause frame use: Symmetric Receive-only
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Link partner advertised link modes:  10baseT/Half 10baseT/Full
	                                     100baseT/Half 100baseT/Full
	Link partner advertised pause frame use: Symmetric Receive-only
	Link partner advertised auto-negotiation: Yes
	Link partner advertised FEC modes: Not reported
	Speed: 100Mb/s
	Duplex: Full
	Auto-negotiation: on
	master-slave cfg: preferred slave
	master-slave status: slave
	Port: MII
	PHYAD: 0
	Transceiver: external
	Supports Wake-on: pumbg
	Wake-on: d
	Link detected: yes
so, I should be good to go. Not so much! I then created/enabled/started a service:

Code: Select all

[Unit]
Description=Wake-on-LAN for %i
Requires=network.target
After=network.target

[Service]
ExecStart=/usr/sbin/ethtool enp2s0 -s wol g
Type=oneshot

[Install]
WantedBy=multi-user.target
-still won't wake. I ran wireshark on it - it IS receiving the magic packets (containing its correct MAC address). I don't get it -- what am I missing?

This is no emergency; it's just living in the back of my mind driving me crazy. If you've any ideas or suggestions I'd be grateful. I do have another network card I could throw in it to see if maybe the onboard got zapped I suppose.

Thank you

EDIT:
I should mention that the link light does come on during boot; it just doesn't stay on after shutdown.

** I wonder if the Windows Install is disabling it.
Last edited by lightman47 on 2022/01/11 19:15:30, edited 1 time in total.

lightman47
Posts: 1521
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: WOL issue again - I solved it once

Post by lightman47 » 2022/01/11 15:16:09

I've been working on this from time to time. I did find out that RHEL 8 is turning something off when it runs. If I run Windows 10 and do a shutdown from there, then WOL works the next time. If I run RHEL and do a shutdown, it does not!

Curiouser and curiouser ...

lightman47
Posts: 1521
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

[Solved] Re: WOL issue again - I solved it once

Post by lightman47 » 2022/01/11 19:14:57

BINGO! - and I remember that this is how I solved it the last time (on THIS machines' new motherboard as well as another machine with a brand new MSI motherboard).

https://groupbcl.ca/blog/posts/2020/set ... 0-edition/

then Section:

"Getting Linux to set the network interface for WoL at startup"

Post Reply