1

I just got Wake on Lan working but I have a problem: If I wake on lan and try to shutdown or suspend it just starts up again. This only happens once after using WOL and then it successfully shuts down and also suspends. What could be causing this? How should I troubleshoot?

Thanks

luvgirl
  • 11
  • 2

3 Answers3

2

I had this behaviour and fixed it by replacing the driver for my Realtek RTL111/8168B NIC. Instead of using the r8169 driver included in the kernel I used the realtek r8168 driver from realtek (inspired by this post).

Note, I'd tried to upgrade my way out of the problem by installing a 3.10 kernel which unfortunately prevents the realtek driver from building until I applied the patch from (I don't have enough reputation for a third link so google 'r8168 NETIF_F_HW_VLAN_RX undeclared' and click first link). Unfortunately the patch had white space issues that I ended up manually fixing before it would apply.

finn
  • 21
  • 2
  • Is this the link that you are referring to: http://code.google.com/p/r8168/issues/detail?id=13 ? If,so, I can add it to your answer. – Kevin Bowen Aug 19 '13 at 01:55
1

Had the same problem on Ubuntu 16.04 running on GIGABYTE GA-Z97X-UD7 motherboard. BIOS update didn't help, driver update didn't help.

What I did was created a script that would restart the computer after WOL boot. Restart would, unlike shutdown, work just fine. And after that I was able to shut down without problems.

user588579
  • 11
0

I had this same problem with 100% reproducibility, the first power off after a wake-on-lan power on would result in an immediate and undesired re-power on. But only one.

I tried lots of suggestions, even using Realtek's own kernel driver, but nothing worked. Finally I upgraded my motherboard's bios and the problem was fixed.

I have a P8Z77-V-LK ASUS motherboard. The working bios I updated to is P8Z77-V-LK-ASUS-1402. The old dysfunctional bios was 1301.

Dave
  • 1