(In reply to Benjamin Poirier from comment #22) > Perhaps we can > find out if the setting was changed before shutdown or if it is related to > the initialization of the adapter. > It looks as if it is the initialization of the adaptor at power on... I think :) "journalctl --list-boots" only lists the last boot... I'm rather stuck on rsyslog :) Using: "cat /var/log/messages | grep -i r8169" This is the reboot (without power off) immediately after installing your "r8169-kmp-desktop" 2014-12-01T15:19:01.287565+00:00 Orion-14 kernel: [ 5.678966] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded 2014-12-01T15:19:01.287566+00:00 Orion-14 kernel: [ 5.678980] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control 2014-12-01T15:19:01.287568+00:00 Orion-14 kernel: [ 5.679576] r8169 0000:02:00.0: irq 42 for MSI/MSI-X 2014-12-01T15:19:01.287570+00:00 Orion-14 kernel: [ 5.679770] r8169 0000:02:00.0 eth0: RTL8168b/8111b at 0xffffc90010742000, 00:1f:d0:3e:f6:e9, XID 3b000700 IRQ 42 2014-12-01T15:19:01.287572+00:00 Orion-14 kernel: [ 5.679773] r8169 0000:02:00.0 eth0: jumbo features [frames: 4080 bytes, tx checksumming: ko] 2014-12-01T15:19:01.287578+00:00 Orion-14 kernel: [ 5.679782] r8169 0000:02:00.0 eth0: wol status And this is the boot after the power cycle 2014-12-01T15:21:12.248281+00:00 Orion-14 kernel: [ 5.665904] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded 2014-12-01T15:21:12.248286+00:00 Orion-14 kernel: [ 5.665918] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control 2014-12-01T15:21:12.248289+00:00 Orion-14 kernel: [ 5.666200] r8169 0000:02:00.0: irq 42 for MSI/MSI-X 2014-12-01T15:21:12.248290+00:00 Orion-14 kernel: [ 5.666444] r8169 0000:02:00.0 eth0: RTL8168b/8111b at 0xffffc90010742000, 00:1f:d0:3e:f6:e9, XID 3b000100 IRQ 42 2014-12-01T15:21:12.248293+00:00 Orion-14 kernel: [ 5.666447] r8169 0000:02:00.0 eth0: jumbo features [frames: 4080 bytes, tx checksumming: ko] 2014-12-01T15:21:12.248295+00:00 Orion-14 kernel: [ 5.666455] r8169 0000:02:00.0 eth0: wol status u g (The log times don't exactly agree with those from "journalctl -b -l -o short-iso"?? - however I've double checked, and this *is* the correct section of /var/log/messages.) > If you don't mind, could you also make some tests to see if it is reliably > the > case that if you disable wol and reboot, wol is still disabled at the next > boot, whereas if you disable wol and shutdown, wol is enabled again at the > next boot. With your "r8169-kmp-desktop" uninstalled and the "disable wol script" removed: At initial power on wol status is "ug" Issue "ethtool -s enp2s0 wol d" -- check status: now "d" Reboot using (KDE) Leave -> Restart Computer -- check status: is still "d" Repeat reboot twice more and status remains "d" Try (KDE) Leave -> Turn off computer -- upon restart status is still "d" Power off completely and upon restart status is now "ug" > Finally, testing with the 13.1 kernel would still be interesting. Yes, I'll try that in a few days... (I have some *very* important work that I must complete first, just in case I manage to bork something when messing with the kernel ... I'm all out of my depth here really.)