One difference though is that NAS1 has got an 1.40 UEFI version while NAS2 is on a 1.60 UEFI version.īoth have the following UEFI setup that, to my understanding, should enable WoL:Ĭode: System: Host: NAS2 Kernel: 4.15.0-96-generic x86_64 bits: 64 gcc: 7.5.0 Desktop: MATE NAS1 and NAS2 components are very similar, and both are based on the very same motherboard, an Asrock J3455-ITX. I showed this to a friend and it ended up with him wanting the same solution, so I made him one similar Ubuntu Server 18.04 build, let's call it NAS2.Īs you may guess, NAS2 is not responding to WoL, no way to power it on remotely. When NAS1 has been shut down (with sudo shutdown - h now), I can turn it on from PC1 by sending wake-on-lan (WoL) magic packets to it either with the powerwake or wakeonlan command.
#WAKEONLAN UBUNTU 16 MAC#
I am successfully powering on my home made Ubuntu Server 18.04 NAS1 from my PC1 Linux Mint 19.2 Build (Ubuntu 18.04 based).īoth have their IP addresses reserved in my router according to their MAC Addresses and are on the same subnet. Notice the “Info” which says “Info: don’t support pm_turn_off yet.First post, long time reader of the forum to help solving my problems, needing your support this time. PM: noirq suspend of devices complete after 7.256 msecsĮven though the CPUs are up, the system remains in frozen state and the tasks are not restarted. PM: late suspend of devices complete after 0.699 msecs PM: suspend of devices complete after 83.021 msecs Wake on UART worked perfectly.įor wake on lan, please see the terminal output below (after sending the magic packet): ethtool -s eth0 wol echo enabled > echo mem>/sys/power/state ata1: SATA link down (SStatus 0 SControl 300) PM: resume of devices complete after 179.727 msecs PM: early resume of devices complete after 0.547 msecs PM: noirq resume of devices complete after 0.494 msecs
The target station address is 0:14:2d:4b:16:3. Sending magic-packet using ‘etherwake’: $ sudo etherwake -i enp12s0 -D 00:14:2D:4B:16:03 PM: noirq suspend of devices complete after 0.838 msecs PM: late suspend of devices complete after 0.638 msecs PM: suspend of devices complete after 158.399 msecs To enable the eth0 as wakeup source: # echo enabled > /sys/class/net/eth0/power/wakeup
a/arch/arm/boot/dts/im圆qdl-apalis.dtsiĪlso by default in userspace the wake-on-lan is disabled, to enable the wake-on-lan run: # ethtool -s eth0 wol g
You can try enabling wake-on-lan support, changes required to enable wake-on-lan: diff -git a/arch/arm/boot/dts/im圆qdl-apalis.dtsi b/arch/arm/boot/dts/im圆qdl-apalis.dtsi Have a look at the device tree bindings documentation here. I am using the wakeonlan utility from Ubuntu host to send the magic packet to the eval board.īy default wake-on-lan is not enabled, one will need to enable it in device tree.
#WAKEONLAN UBUNTU 16 HOW TO#
To enable wakeup via UART port: # echo enabled > /sys/class/tty/ttymxc0/power/wakeupĪlso, I was not able to find any info on how to configure the ethernet to detect a wake-on-lan (magic packet) signal. Have a look at this article for information on available tty ports on Apalis iMX6. Please note that the article you are refering to is not applicable for Apalis iMX6. However, I was not able to configure the UART for wake up as the following path does not exist in the rootfs.
0 kommentar(er)
