wake on lan is not working

Bug #1780872 reported by Ignacio
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I'm dual-booting Ubuntu 18.04 and Windows 10. If I turn off my computer with Windows, I can turn it back on using wol. However, if I turn it off using Ubuntu the computer won't turn back on if I use wol.

These are my network cards:

```
ignacio@ignacio-XPS-8930:~$ ifconfig
docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
        inet6 fe80::42:e4ff:fe0a:9fee prefixlen 64 scopeid 0x20<link>
        ether 02:42:e4:0a:9f:ee txqueuelen 0 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 165 bytes 24102 (24.1 KB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.86.31 netmask 255.255.255.0 broadcast 192.168.86.255
        inet6 fe80::955b:12c8:20b9:7645 prefixlen 64 scopeid 0x20<link>
        ether d8:9e:f3:85:42:8a txqueuelen 1000 (Ethernet)
        RX packets 50484 bytes 52395285 (52.3 MB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 29166 bytes 4575560 (4.5 MB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
        device interrupt 19

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0
        inet6 ::1 prefixlen 128 scopeid 0x10<host>
        loop txqueuelen 1000 (Local Loopback)
        RX packets 1124 bytes 95423 (95.4 KB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 1124 bytes 95423 (95.4 KB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth66fe4e4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet6 fe80::2078:3ff:feb3:2aa1 prefixlen 64 scopeid 0x20<link>
        ether 22:78:03:b3:2a:a1 txqueuelen 0 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 224 bytes 30503 (30.5 KB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vethb50cc6f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet6 fe80::5c0b:47ff:fef1:cfc9 prefixlen 64 scopeid 0x20<link>
        ether 5e:0b:47:f1:cf:c9 txqueuelen 0 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 125 bytes 18006 (18.0 KB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
        ether 5c:ea:1d:4c:61:a7 txqueuelen 1000 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

```

This is what ethtool tells me about my ethernet card:

```
ignacio@ignacio-XPS-8930:~$ sudo ethtool enp4s0
Settings for enp4s0:
 Supported ports: [ TP ]
 Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         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/Full
 Advertised pause frame use: Symmetric
 Advertised auto-negotiation: Yes
 Advertised FEC modes: Not reported
 Speed: 1000Mb/s
 Duplex: Full
 Port: Twisted Pair
 PHYAD: 0
 Transceiver: internal
 Auto-negotiation: on
 MDI-X: Unknown
 Current message level: 0x000060e4 (24804)
          link ifup rx_err tx_err hw wol
 Link detected: yes

```

And this is what happens when I try to activate wake on lan:

```
ignacio@ignacio-XPS-8930:~$ sudo ethtool -s enp4s0 wol g
Cannot get current wake-on-lan settings: Operation not supported
  not setting wol
```

Finally, this is the infor about my distro:

```
ignacio@ignacio-XPS-8930:~$ lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
```

Thanks for the help!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ethtool 1:4.15-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 9 18:58:08 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
InstallationDate: Installed on 2018-07-07 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: ethtool
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: ignacio 4483 F.... pulseaudio
 /dev/snd/controlC0: ignacio 4483 F.... pulseaudio
 /dev/snd/controlC1: ignacio 4483 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-07-07 (5 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. XPS 8930
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-23-generic root=UUID=da1fcc13-cc4b-41d4-a29f-063ccf97684e ro rootflags=subvol=@ quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-23-generic N/A
 linux-backports-modules-4.15.0-23-generic N/A
 linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/31/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.11
dmi.board.name: 0DF42J
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/31/2018:svnDellInc.:pnXPS8930:pvr1.0.11:rvnDellInc.:rn0DF42J:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.version: 1.0.11
dmi.sys.vendor: Dell Inc.

Revision history for this message
Ignacio (ignacio82) wrote :
Revision history for this message
Ben Hutchings (benh-debian) wrote :

This is a bug in the driver, not in ethtool.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Could you please attach the output of dmesg right after you get the error with ethtool? And I believe lspci would also be helpful for the kernel people.

Changed in ethtool (Ubuntu):
status: New → Incomplete
Revision history for this message
Ignacio (ignacio82) wrote :
Revision history for this message
Ignacio (ignacio82) wrote :
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Please run this and attach the ethtool.strace output file:

sudo strace -f -o ethtool.strace -s 500 ethtool -s enp4s0 wol g

I grabbed that command from your post in this bug earlier, please adjust if I got it wrong. We want to see what the tool is doing when it fails.

Revision history for this message
Ignacio (ignacio82) wrote :
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

9771 ioctl(3, SIOCETHTOOL, 0x7fff544879a0) = -1 EOPNOTSUPP (Operation not supported)

Looks like the operation is not supported, so a driver issue. I'm changing the task to the kernel.

affects: ethtool (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1780872

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Ignacio (ignacio82) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Ignacio (ignacio82) wrote : CRDA.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : IwConfig.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : Lspci.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : Lsusb.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : ProcEnviron.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : ProcModules.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : PulseList.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : RfKill.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : UdevDb.txt

apport information

Revision history for this message
Ignacio (ignacio82) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc5

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Ignacio (ignacio82) wrote :

> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

This is a fresh install on a brand new computer, so no clue if a prior kernel has this problem or not.

> Would it be possible for you to test the latest upstream kernel?

Never done this before, but I can try. I downloaded linux-headers-4.18.0-041800rc5-generic_4.18.0-041800rc5.201807152130_amd64.deb . I will give it a try and update this comment soonish.

Revision history for this message
Ignacio (ignacio82) wrote :

I get the following error when i try to install the kernel:

$ sudo dpkg -i linux-headers-4.18.0-041800rc5-generic_4.18.0-041800rc5.201807152130_amd64.deb
[sudo] password for ignacio:
Selecting previously unselected package linux-headers-4.18.0-041800rc5-generic.
(Reading database ... 187153 files and directories currently installed.)
Preparing to unpack linux-headers-4.18.0-041800rc5-generic_4.18.0-041800rc5.201807152130_amd64.deb ...
Unpacking linux-headers-4.18.0-041800rc5-generic (4.18.0-041800rc5.201807152130) ...
dpkg: dependency problems prevent configuration of linux-headers-4.18.0-041800rc5-generic:
 linux-headers-4.18.0-041800rc5-generic depends on linux-headers-4.18.0-041800rc5; however:
  Package linux-headers-4.18.0-041800rc5 is not installed.

dpkg: error processing package linux-headers-4.18.0-041800rc5-generic (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-headers-4.18.0-041800rc5-generic

Revision history for this message
Ignacio (ignacio82) wrote :

> First, if one is using select proprietary or out-of-tree modules (e.g. bcmwl, fglrx, NVIDIA proprietary graphics drivers, VitualBox, etc.) unless there is an extra package available for the version you are testing, you will need to uninstall the module first, in order to test the mainline kernel. If you do not uninstall these modules first, then the upstream kernel may fail to install, or boot.

Given that I'm using the nVidia drivers, I'm guessing this is not going to work. I guess I will have to wait until the next official kernel update

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

alx has wol support starts from 4.15.0-24.26

Revision history for this message
Ignacio (ignacio82) wrote :

I have 4.15.0-29 and it does not work :(

ignacio@ignacio-XPS-8930:/nfs/R/Projects/SlidesSEDS/docker$ uname -a
Linux ignacio-XPS-8930 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ignacio@ignacio-XPS-8930:/nfs/R/Projects/SlidesSEDS/docker$ sudo ethtool -s enp4s0 wol g
[sudo] password for ignacio:
Cannot set new wake-on-lan settings: Operation not supported
  not setting wol

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

It's default off. Use parameter to turn it on: "alx.enable_wol=1"

Revision history for this message
Ignacio (ignacio82) wrote :

Could you be a bit more specific about how to 'Use parameter to turn it on: "alx.enable_wol=1"' ?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Ignacio (ignacio82) wrote :

As suggested in [askubuntu](https://askubuntu.com/questions/1053302/wake-on-lan-not-working-if-i-turn-of-with-ubuntu/1072862#1072862) I tried editing /etc/netplan/01-network-manager-all.yaml

```
# Let NetworkManager manage all devices on this system
network:
  version: 2
  renderer: NetworkManager
  renderer: networkd
  ethernets:
    enp4s0:
      match:
        macaddress: D8:9E:F3:85:42:8A
      dhcp4: true
      wakeonlan: true
```

and running `sudo netplan apply`

This did not help either:

```
ignacio@ignacio-XPS-8930:~$ ethtool enp4s0
Settings for enp4s0:
 Supported ports: [ TP ]
 Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         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/Full
 Advertised pause frame use: Symmetric
 Advertised auto-negotiation: Yes
 Advertised FEC modes: Not reported
 Speed: 1000Mb/s
 Duplex: Full
 Port: Twisted Pair
 PHYAD: 0
 Transceiver: internal
 Auto-negotiation: on
 MDI-X: Unknown
Cannot get wake-on-lan settings: Operation not permitted
 Current message level: 0x000060e4 (24804)
          link ifup rx_err tx_err hw wol
 Link detected: yes

```

Revision history for this message
Bib (bybeu) wrote (last edit ):

@Ignacio, from your post #27, check you have no .deb in your downloads directory before you fetch all 3 latest linux-headers-X.YZ.x-xxxxxxrcN...._all.deb and linux-headers-X.YZ.x-xxxxxxrcN-generic...._amd64.deb and linux-image-unsigned-X.YZ.x-xxxxxxrcN-generic_X.YZ.x-xxxxxxrcN_amd64.deb then run sudo dpkg -i path-to-DLs/*.deb

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.