Arch Linux

jackdroido

Member

From: Italy

Registered: 2011-07-26

Posts: 8

r8169 wake-on-lan (WOL) works only after a manual suspend/resume cycle

Hi !

I have a weird and long-standing problem with wake-on-lan with my Realtek ethernet.
After turning wake-on-lan flag on (using either ethtool or NetworkManager as shown in https://wiki.archlinux.org/index.php/Wake-on-LAN, doesn't matter which method), to make the PC responsive to wol packets, I have to first suspend and wakeup it once manually (hitting any key or power button).

After this maneuver, I can wakeup via magic packet from all subsequent suspend transitions AND also from the first shutdown. Then I have to repeat the manual suspend/resume cycle to make it work.

I already tried various solutions (including trying the r8168 module mentioned in the wiki) or forcing autonegotiation on (as mentioned in https://forums.centos.org/viewtopic.php?t=71861), without success. Searching online, I see many subtly different issues with wol on Realtek cards exist.

Here's the card details:

$ lspci -k
...
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
	Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
	Kernel driver in use: r8169
	Kernel modules: r8169
$ dmesg | grep XID
[    5.658877] r8169 0000:02:00.0 eth0: RTL8168h/8111h, xx:xx:xx:xx:xx:xx, XID 541, IRQ 126

The PC is a Gigabyte NUC-like barebone: https://www.gigabyte.com/Mini-PcBarebon … 05R-rev-10. BIOS is up-to-date and doesn't show any "obvious" wol settings, and honestly doesn't seems to be the culprit here, since after all, wol is working...

Is there a solution that I miss out-there ? Or at least a workaround to replicate the state the eth is in after the suspend/resume cyle (without actually suspending of course) ? If more info are needed just ask.