Posts: 21
Joined: Feb 2014
Reputation:
0
Thanks. It ended up working for me. Seems to be a lot smoother and my on/off with harmony remote issues seem to have been resolved.
So anyone reading this. Make sure you update to newest BIOS.
Cheers
Posts: 224
Joined: Jan 2010
Reputation:
1
Reset BIOS/UEFI settings.
Posts: 67
Joined: Oct 2010
Reputation:
4
Ok, thx, will give it a try.
--
multiple Kodi clients + vdr backend + mysql db
Posts: 67
Joined: Oct 2010
Reputation:
4
2018-01-14, 14:52
(This post was last modified: 2018-01-15, 15:32 by lazyman.)
Well, that did not work. Reset the settings at 11 am. Compared vs. old. Looked good and ok ish. Just changed back to _not_ to WoL. At 1pm NUC boots by itself - again. Urgh! Any other hints? Maybe something with autostart.sh or NIC settings or something wthin LE itsellf? I'm not very familiar with ethtool and don't know what to look at. Thx! Tomorrow I will disconnect the LAN cable ...
edit: pheww, LAN cable disconnected. NUC starts at 12:45 - again. So no magic packets for somewhere within my LAN. Besides, I found something with regard to BIOS CMOS wipe and also that a downgrade is not recommended. So a downgrade is possible but ... at least I got the CMMS procedure. What a mess.
edit2: CMOS wipe is the same as "F9 to restore BIOS factory default values" what I did - umpf - downgrade it is.
--
multiple Kodi clients + vdr backend + mysql db
Posts: 67
Joined: Oct 2010
Reputation:
4
2018-01-17, 14:02
(This post was last modified: 2018-01-17, 16:50 by lazyman.)
NUC is back on BIOS 027 and for me the best thing is: No more wapeups at 12:45 (11:45 UTC).
The downgrade process involved a few *shock* moments when error messages showed up - like 'fwUpdate FullBuffer' or something. A plain downgrade or recovery was not possible for me - afaik. I than used the HW based `yellow jumper` process with 027 as the only .bio file on an attached USB stick. The recovery process is well documented on intels support site.
edit: fsck - LOL - well, now it wakes at 13:45. I think that was around the time I did the recovery. awesome. I'm nearly out of options ...
--
multiple Kodi clients + vdr backend + mysql db
Posts: 58
Joined: Apr 2014
Reputation:
3
Under the Power tab in the BIOS be sure to uncheck "Wake system from S5" which "Enable or disable system wake on alarm event. When enabled, system will wake on the day/hour/minute/second specified."
Otherwise why not cut power from your NUC while not using it? I have been doing it on my D34010WYK ever since I got it a few years ago without noticing any adverse effect.
Posts: 67
Joined: Oct 2010
Reputation:
4
2018-01-20, 00:11
(This post was last modified: 2018-01-20, 00:13 by lazyman.)
thx ulibuck. I did that S5 stuff. Though I still want to use the remote to power on/off. Andnit worked for years. Meanwhile I got it sorted - mostly by accident I think. This is what I did:
1. I disconnected the PSU for ~ 3h
2. Is set and unset the timer function the BIOS offers. I activated the function and let it start the NUC for exactly one time. After that I disabled it again.
3. I checked with ethtool the NIC settings. eth0 WOL flag was set to 'g'. This did not change after a reboot. So I added a 'ethtool -s eth0 wol d' into a startup shellscript - made me feel better :\
Well I'm now without recurring daily power-on situations.
btw, 046 bios is not available any more. the mitigations did not mitigate ...
--
multiple Kodi clients + vdr backend + mysql db