Wake On Lan Is Not Waking

[m00tpoint]

Well, my pcie NIC arrived, I've installed it, and WOL does not work with this NIC either. I see the same symptoms as with the onboard Intel NIC's.

I did discover that I had not enabled the "Boot up after power outage" option in the BIOS, and I did that, so the wifi controlled power plug is now a reliable way to wake up the machine. That will be what I do going forward.

Thanks again for all the reads, suggestions, etc. Linux Mint has a great community!

[rene]

Thanks for reporting. That's really stupidly unexpected though. Oh well...

[powerwagon75]

...

One more question (for doing the original method)...did you ever run ethtool -s eth0 wol g on the remote machine? [ where you'd substitute eth0 for your remote machines connection name]

running the request below with your connection name should yield similar results if so:

Code: Select all

[user3@UseR3 ~]$ sudo ethtool enp0s12
[sudo] password for user: 
Settings for enp0s12:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Supported pause frame use: No
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Speed: 1000Mb/s
	Duplex: Full
	Auto-negotiation: on
	Port: Twisted Pair
	PHYAD: 2
	Transceiver: internal
	MDI-X: on (auto)
	Supports Wake-on: pumbg
	Wake-on: g  <--------------------------------(I believe this needs to be there for your original method to work)
        Current message level: 0x00000007 (7)
                               drv probe link
	Link detected: yes

[m00tpoint]

Code: Select all

dennis@apollo:~$ sudo ethtool eno1
Settings for eno1:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: No
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Speed: 100Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: off (auto)
	Supports Wake-on: pumbg
	Wake-on: g   <---------------------------------------------- It's lying, I tell you, lying!!!!!
	Current message level: 0x00000007 (7)
			       drv probe link
	Link detected: yes
dennis@apollo:~$ 

It's .... frustrating.

[rene]

The most interesting thing is trouble not occuring from a really-full shutdown, i.e., after removing power. This would seem to say that it's not the NIC as such but the board somehow powering down the interconnect to the NIC when shutting down, with the power-cycling resetting that state. It's the sense in which I expected that onboard vs. PCIe could likely make a difference. It's in any case very weird that your machine would do anything like that given that it has explicit WoL settings in its BIOS. One would expect that someone once tested things.

[m00tpoint]

I agree completely. I have to wonder if it's some strange hardware failure .... this machine is not new by any means.