Wake on LAN setting of eth1 to Xavier NX is reset to "d" after reboot

Robotics & Edge Computing Jetson Systems Jetson Xavier NX
1

Hello All,

I tried enabling Wake on LAN for ‘eth1’ port of Xavier Nx board. Using ethtool, i found that the supported mode is ‘g’.

Enabled it using ‘sudo ethtool -s eth1 wol g’ command.
Default value is : ‘d’ has changed to ‘g’
Command “sudo systemctl suspend” kept the board in Deep Sleep State.
Command "sudo etherwake -i <mac_Address_jetson_eth1> woke up the system.

Second method i tried is added netplan.yaml file and added the following:
eth1:
match:
macaddress: <mac_Address_of_eth1>
wakeonlan: true
This is part of netplan file i created. Then i need to call “sudo netplan apply” command.
This commands enables Wake-On-LAN for eth1.

In both cases, after suspend systems wakes up normally.

But if i restart/shutdown the jetson, then wake on LAN value is set to ‘d’ only for eth1.

Do i need add service during every boot up to enable the WOL?

is there any way to enable the WOL once using netplan.yaml file? I am using networkd as the renderer

is this possible to enable WOL using Device Tree file ?

Details: Jetpack 5

3

Hi,

Could you confirm what is “eth1” here?
“eth1” sounds more like your extra ethernet NIC but not the on board ethernet port.

4

Hi,

This board is from Advantech vendor. Probably, it is extra ethernet port added by vendor.

5

Then I think you may need to ask the vendor if this is supported.

I am not able to answer such question as we don’t even know what kind of NIC is instatlled.

is this possible to enable WOL using Device Tree file ?

6

what about eth0? Can we enable WOL permanently for eth0? I guess this is the ethernet from NVIDIA.

7

Which release are you using here? I remember eth0 WoL is already enabled by default.

8

R35 (release), REVISION: 4.1, GCID: 33958178, BOARD: t186ref, EABI: aarch64, DATE: Tue Aug 1 19:57:35 UTC 2023.

Can you pls share the procedure to enable or disable the WOL on eth0?

9

Hi WayneWWW,

I changed the port to eth0.
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
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: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes

Then i entered into suspend state using :
sudo systemctl suspend.

After that wake up is not happening. Wake-up is possible manually by moving keyboard or mouse.
Command for wake from host:
sudo etherwake -i interface-name mac_Address_of_Eth0
Board: Xavier NX
Jetpack: 5

10

Hi Purusothaman_K,

Please try below steps to WOL:
Xavier-NX:

$ sudo ethtool -s eth0 wol g
$ sudo systemctl suspend

Host:

$ sudo apt-get install wakeonlan
$ wakeonlan -i <DUT-IP-Address> <DUT-HW-Address>
11

Hi Carolyuu,

Just to confirm: - is this broadcast address from the ifconfig?

DUT-HW-Address: is this ether address from the ifconfig?

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet XX.XX.XX.11 netmask XX.XX.XX.0 broadcast XX.XX.XX.255
inet6 XXXX::XXXX:XXXX:XXXX:XXXX prefixlen 64 scopeid 0x20
ether XX:XX:XX:XX:XX:XX txqueuelen 1000 (Ethernet)
RX packets 5844 bytes 446270 (446.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1203 bytes 117328 (117.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xxxx40000000-xxxx007ffff

12

Hi Purusothaman_K,

please check bold words:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet XX.XX.XX.11 netmask XX.XX.XX.0 broadcast XX.XX.XX.255 → IP address
inet6 XXXX::XXXX:XXXX:XXXX:XXXX prefixlen 64 scopeid 0x20
ether XX:XX:XX:XX:XX:XX txqueuelen 1000 (Ethernet) → HW address

13

Hi Carolyuu,

I tried the command given above. it is not working.

eth0 is configured to dhcp. Host and Jetson board is connected via Network switch. if i wake up the Jetson manually, I could able to access the host PC from jetson box. Both host and Jetson is in the same network.

Broadcast address and Gateway is same for both host and Jetson.

16

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

Is this still an issue to support? Any result can be shared?