WOL is not working

dan.h · June 26, 2016 at 7:33 AM

Hello all
I upgraded my OpenELEC 5.0.3 Nvidia Legacy build to LibreELEC 7.0.1 Generic Build, and it went very well

However since the upgrade the WOL (Wake-On-LAN) is not responding, it used to work fine under OpenELEC 5.0.3 Nvidia Legacy build.
And there was no change in the hardware or my network.

I’ll appreciate any suggestions / investigation directions.
Thanks a lot
Dan

Technical details:
I use Yatse remote app --> details?id=org.leetzone.android.yatsewidgetfree
And my hardware is Xtremer Ultra (1) --> Xtreamer Ultra specs
I use the LAN connection (not Wi-Fi)

alessandro.psrt · June 26, 2016 at 7:46 AM

Your hardware support wol?

dan.h · June 26, 2016 at 8:02 AM

Yes it does, and not only theoretically it actually worked until the upgrade

**DaVu** · June 26, 2016 at 8:57 AM Official Post

could you please show use the output of

Code

ethtool eth0 | pastebinit

"eth0" might be different on your system. So please check with

Code

ifconfig

which NIC is in use and change the first command to the matching one.

A first thought might, that your power settings are different now on LibreELEC and therefor it behaves different than OE does. So please check your BIOS and your power settings once again if something is different in there.

dan.h · June 26, 2016 at 3:42 PM

Thanks DaVu
Here is the output NRLZ
can you please guid me what to look for in the BIOS, and where to check the power settings that you mentioned ?

Thanks Dan

**newphreak** · June 26, 2016 at 3:54 PM Official Post

Here I would guess:

External Content youtu.be

Content embedded from external sources will not be displayed without your consent.

Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

dan.h · June 27, 2016 at 7:57 AM

I reviewed the entire BIOS settings but could not find the power options
In any case if I restore to OpenELEC it works and on LibreELEC it doesn’t (I’m not changing anything on the BIOS)

**CvH** · June 27, 2016 at 8:34 AM Official Post

You have to readd the HTPC at yatse, you can't just take the same profile like you used at 5.0

yort · June 27, 2016 at 4:07 PM

I would say CvH has figured out your issue. I had the same problem, my IP address did not change and the host could still be controlled by YATSE but the WOL and power options wouldn't work until I deleted the host and added it as a new host to YATSE. This seem to happen because you upgraded versions of Kodi not because of changing from OE to LE or even upgrading OE or LE.

dan.h · June 27, 2016 at 10:30 PM

Thank you CvH & yort, you are right.
After I removed the host from my Yatse remote and readded it, WOL is working

soest009 · February 20, 2017 at 7:43 PM

Sorry to poke on an old thread, but i have the same issues when changing from kodibuntu to LE.
Trying to activate WOL via SSH or reconfiguring into Yatse sofar is not working for me.

Running the following:
ASrock E350M mainboard
Yatse on Android (Galaxy S5)
EL (latest version with krypton)

Any pointers?
[hr]
I have noticed when accessing with SSH and entering the command: "

Code

ethtool -s eth0 wol g

" the system responds correctly to WOL.
However when putting it back to sleep it stop responding, checking the status then sets setting "Wake-on" to d resulting in no WOL trigger untill i set it again for one time.

Any way to get this permanently on the g setting?

**CvH** · February 21, 2017 at 11:55 AM Official Post

you could put it to the autoexec.sh

soest009 · February 21, 2017 at 1:29 PM

Dear CvH thanks for your reply, i am still a bit of a noob concerning linux.
Can you please explain how this can be done using an SSH session?

Many thanks in advanced.

**DaVu** · February 21, 2017 at 1:42 PM Official Post

Code

cd /storage/.config

Code

nano autostart.sh

with that commands you will change to the /storage/.config folder and the "nano" command will open an editor to enter the needed things to the file "autostart.sh" (which will be created automatically). After you did your changes, save and exit the file.

Not really needed, but it doesn't hurt, make that file executably with:

Code

chmod +x autostart.sh

Then, everytime you boot up LibreELEC, the commands inside that script are executed.

soest009 · February 21, 2017 at 2:22 PM

Dear DaVu thank you for the instruction, i will give it a go later today and report back with the results.

soest009 · February 21, 2017 at 4:40 PM

Dear DaVu, i have added the line to autostart.sh however situation remains unchanged, after one successfull suspend followed with WOL wakeup the system no longer responds to WOL requests.
Also after checking the setting it's back to disabled mode.

soest009 · February 23, 2017 at 6:54 PM

Been looking around some more and found out that the PCI deviced linked to my ethernet adapter shows as S4 state disabled.
when using code cat /proc/acpi/wakeup This shows me that: PCE4 S4 *disabled pci:0000:00:04.0 which resembles my nic.
I figure this has to do with the fact that ethtool keeps switching back to disabled wol, is this true?

Furthermore i doublechecked bios settings and virtually everything that could invoke remote wakeup is on.
Any suggestions?

soest009 · March 15, 2017 at 10:52 PM

Been a while again and discovered (more dumb luck t.b.h.) that WOL from suspend doesn not function, however when powering down WOL does respond to the WOL command from Yaste correctly.
No clue how it is like this but i am happy, so the way i see it: stay away from suspend

WOL is not working

Similar Threads

Sometimes no screen on TV

ALSA support for OMXPlayer

Execute script on shutdown by timer