NIC 'loses' WOL paramater/setting/value after reboot = No WOL possible
by Superblond from LinuxQuestions.org on (#5CANG)
Hallo experts!
After installing the correct Linux driver for my 10GBE Marvell AQN-107 Network card (Marvell AQtion Linux driver) WOL is available and settings can be changed.
Problem: After the 1st reboot the WOL parameter ist gone and cant be changed anymore!
### Installation of the driver ###
Code:root@NAS:~/Downloads/Marvell2$ modprobe ptp
root@NAS:~/Downloads/Marvell2$ modprobe crc_itu_t
root@NAS:~/Downloads/Marvell2$ ./dkms.sh install
Creating symlink /var/lib/dkms/atlantic/2.4.3.0/source ->
/usr/src/atlantic-2.4.3.0
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j4 KERNELRELEASE=4.19.0-13-amd64 -C /lib/modules/4.19.0-13-amd64/build M=/var/lib/dkms/atlantic/2.4.3.0/build......
cleaning build area...
DKMS: build completed.
atlantic.ko:
Running module version sanity check.
- Original module
- This kernel never originally had a module by this name
- Installation
- Installing to /lib/modules/4.19.0-13-amd64/updates/dkms/
depmod...
DKMS: install completed.### Checking if driver ok and NIC working ###
Code:nexus6@NAS:~/Downloads/Marvell2$ sudo /usr/sbin/ethtool enp2s0
Settings for enp2s0:
Supported ports: [ TP ]
Supported link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
5000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
5000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: pg
Wake-on: d
Current message level: 0x00000005 (5)
Current message level: 0x00000005 (5)
drv link
Link detected: yes### Setting WOL from "d" to "g" with ethtool + check ###
Code:root@NAS:~/Downloads/Marvell2$ sudo /usr/sbin/ethtool -s enp2s0 wol g
root@NAS:~/Downloads/Marvell2$ sudo /usr/sbin/ethtool enp2s0
...snip
Supports Wake-on: pg
Wake-on: g
...snip### Until now all good, then reboot and check ###
### now: after reboot & login the WOL parameter is gone ###
Code:root@NAS:~# /usr/sbin/ethtool enp2s0
Settings for enp2s0:
Supported ports: [ TP ]
Supported link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
5000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
5000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Link detected: yes### Try to set mode "g" ###
Code:root@NAS:~# /usr/sbin/ethtool -s enp2s0 wol g
Cannot get current wake-on-lan settings: Operation not supported
not setting wol
root@NAS:~#### Configures a WOL service in /etc/systemd/system/wol@.service ###
Code:[Unit]
Description=Wake-on-LAN
Requires=network.target
After=network.target
[Service]
ExecStart=/sbin/ethtool -s enp2s0 wol g
Type=oneshot
[Install]
WantedBy=multi-user.target### and enable service ###
Code:root@NAS:~# systemctl enable wol@enp2s0.But nothing changed...
NIC is working perfectly at 10GBit, with no problems...execpt: I cant use WOL to wake up my designated NAS!?
### Some basic info about my System ###
Code:
root@NAS:~# cat /etc/issue
openmediavault 5.5.20-1 (Usul) \n \l
Copyright (C) 2009-2020 by Volker Theile. All rights reserved.
To manage the system visit the openmediavault web control panel:
enp2s0: 192.168.178.7
enp2s0: fe80::95a9:4eb8:5aee:c2fc
root@NAS:~# cat /proc/version
Linux version 4.19.0-13-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.160-2 (2020-11-28)
root@NAS:~# uname -a
Linux NAS.fritz.box 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 GNU/Linux
root@NAS:~# lspci -nnk | grep -i net -A2
02:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:d107] (rev 02)
Subsystem: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:0001]
Kernel driver in use: atlantic
Kernel modules: atlantic
root@NAS:~# ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:2c:80:9a:b0 txqueuelen 0 (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
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.178.7 netmask 255.255.255.0 broadcast 192.168.178.255
inet6 2003:f8:5738:cb00:ab5e:eea6:bdaa:dc17 prefixlen 64 scopeid 0x0<global>
inet6 fe80::95a9:4eb8:5aee:c2fc prefixlen 64 scopeid 0x20<link>
ether 00:17:b6:00:52:ce txqueuelen 1000 (Ethernet)
RX packets 8980 bytes 1398418 (1.3 MiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 4631 bytes 1395048 (1.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 (Lokale Schleife)
RX packets 588 bytes 234619 (229.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 588 bytes 234619 (229.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0?> Is it possible that the already installed OpenMediaVault NAS-Software interfere with the Debian-Core?
?> Can it be that the istalled Xfce Desktop and the Network manager in this GUI causing problems?
I appreciate any help you may provide!
Thanks
SB
After installing the correct Linux driver for my 10GBE Marvell AQN-107 Network card (Marvell AQtion Linux driver) WOL is available and settings can be changed.
Problem: After the 1st reboot the WOL parameter ist gone and cant be changed anymore!
### Installation of the driver ###
Code:root@NAS:~/Downloads/Marvell2$ modprobe ptp
root@NAS:~/Downloads/Marvell2$ modprobe crc_itu_t
root@NAS:~/Downloads/Marvell2$ ./dkms.sh install
Creating symlink /var/lib/dkms/atlantic/2.4.3.0/source ->
/usr/src/atlantic-2.4.3.0
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j4 KERNELRELEASE=4.19.0-13-amd64 -C /lib/modules/4.19.0-13-amd64/build M=/var/lib/dkms/atlantic/2.4.3.0/build......
cleaning build area...
DKMS: build completed.
atlantic.ko:
Running module version sanity check.
- Original module
- This kernel never originally had a module by this name
- Installation
- Installing to /lib/modules/4.19.0-13-amd64/updates/dkms/
depmod...
DKMS: install completed.### Checking if driver ok and NIC working ###
Code:nexus6@NAS:~/Downloads/Marvell2$ sudo /usr/sbin/ethtool enp2s0
Settings for enp2s0:
Supported ports: [ TP ]
Supported link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
5000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
5000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: pg
Wake-on: d
Current message level: 0x00000005 (5)
Current message level: 0x00000005 (5)
drv link
Link detected: yes### Setting WOL from "d" to "g" with ethtool + check ###
Code:root@NAS:~/Downloads/Marvell2$ sudo /usr/sbin/ethtool -s enp2s0 wol g
root@NAS:~/Downloads/Marvell2$ sudo /usr/sbin/ethtool enp2s0
...snip
Supports Wake-on: pg
Wake-on: g
...snip### Until now all good, then reboot and check ###
### now: after reboot & login the WOL parameter is gone ###
Code:root@NAS:~# /usr/sbin/ethtool enp2s0
Settings for enp2s0:
Supported ports: [ TP ]
Supported link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
5000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
5000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Link detected: yes### Try to set mode "g" ###
Code:root@NAS:~# /usr/sbin/ethtool -s enp2s0 wol g
Cannot get current wake-on-lan settings: Operation not supported
not setting wol
root@NAS:~#### Configures a WOL service in /etc/systemd/system/wol@.service ###
Code:[Unit]
Description=Wake-on-LAN
Requires=network.target
After=network.target
[Service]
ExecStart=/sbin/ethtool -s enp2s0 wol g
Type=oneshot
[Install]
WantedBy=multi-user.target### and enable service ###
Code:root@NAS:~# systemctl enable wol@enp2s0.But nothing changed...
NIC is working perfectly at 10GBit, with no problems...execpt: I cant use WOL to wake up my designated NAS!?
### Some basic info about my System ###
Code:
root@NAS:~# cat /etc/issue
openmediavault 5.5.20-1 (Usul) \n \l
Copyright (C) 2009-2020 by Volker Theile. All rights reserved.
To manage the system visit the openmediavault web control panel:
enp2s0: 192.168.178.7
enp2s0: fe80::95a9:4eb8:5aee:c2fc
root@NAS:~# cat /proc/version
Linux version 4.19.0-13-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.160-2 (2020-11-28)
root@NAS:~# uname -a
Linux NAS.fritz.box 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 GNU/Linux
root@NAS:~# lspci -nnk | grep -i net -A2
02:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:d107] (rev 02)
Subsystem: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:0001]
Kernel driver in use: atlantic
Kernel modules: atlantic
root@NAS:~# ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:2c:80:9a:b0 txqueuelen 0 (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
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.178.7 netmask 255.255.255.0 broadcast 192.168.178.255
inet6 2003:f8:5738:cb00:ab5e:eea6:bdaa:dc17 prefixlen 64 scopeid 0x0<global>
inet6 fe80::95a9:4eb8:5aee:c2fc prefixlen 64 scopeid 0x20<link>
ether 00:17:b6:00:52:ce txqueuelen 1000 (Ethernet)
RX packets 8980 bytes 1398418 (1.3 MiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 4631 bytes 1395048 (1.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 (Lokale Schleife)
RX packets 588 bytes 234619 (229.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 588 bytes 234619 (229.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0?> Is it possible that the already installed OpenMediaVault NAS-Software interfere with the Debian-Core?
?> Can it be that the istalled Xfce Desktop and the Network manager in this GUI causing problems?
I appreciate any help you may provide!
Thanks
SB