2014-02-11, 07:08
Do you need a GUI for the Crashplan Software?
(2014-02-10, 23:04)bustamelon Wrote:(2014-02-10, 22:54)OllieB Wrote: When I try to change the value in the Wake on LAN dropdown box to stay off the Visual BIOS screen freezes and I cannot make any further changes. I have to manually use the power button to switch the NUC off and on to try again. Tried about five times now, without success.That sucks. Do you have a regular keyboard and mouse connected? I found that with one of those battery powered wireless deals, I had the same issue for some reason, but once I hooked up a real keyboard/mouse, all was fine.
(2014-02-10, 22:54)OllieB Wrote: Un-checking Deep S4/S5 does not make a difference in so far that I am still not able to wake up the NUC with the remote.
Bummer. In that case, disabling all WOL features is your only option until they fix it. But of course your freezing csreen issue will prevent that.
(2014-02-10, 22:54)OllieB Wrote: The funny thing is that in the process I have now also lost the NUC starting screen with the message F2, F7 etc and have to guess when to press the F2 keyThere is an option for that somewhere as well.
* Edit - under Boot->Boot Configuration->Boot Display Config
Also, uncheck "Fast Boot" in the left hand side [UEFI BOOT].
(2014-02-10, 22:07)OllieB Wrote:(2014-02-10, 19:29)Crssi Wrote: I would be more accurate at first... but I am not at home to take a look.
-----
I have got home now.
BIOS, Power, Secondary power settings
Uncheck "Deep S4/S5"
BIOS, Devices, Onboard devices, Legacy device configuration
Check "Enhanced consumer IR"
Thanks again.
The "Enhanced consumer IR" checkbox is checked.
At present I also have Deep S4/S5 checked because I thought this was the solution to prevent the NUC from continuously restarting when it was shutdown? Is this what is preventing the NUC from waking up with the remote?
How do I prevent the NUC from automatically restarting when I uncheck Deep S4/S5?
(2014-02-10, 23:10)Jorgensen Wrote: And that HD audio also works in XBMCBUNTU? Basically, if you have any experience with XBMCBUNTU and the Hasweel NUCs to share, I would be glad.
Cheers,
Jorgensen
(2014-02-11, 07:08)-DDD- Wrote: Do you need a GUI for the Crashplan Software?
(2014-02-11, 14:30)tutu Wrote:(2014-02-10, 23:10)Jorgensen Wrote: And that HD audio also works in XBMCBUNTU? Basically, if you have any experience with XBMCBUNTU and the Hasweel NUCs to share, I would be glad.
Cheers,
Jorgensen
Follow this guide to set it all up manually - http://forum.xbmc.org/showthread.php?tid=165707
You can then do as you please adding emulators etc. You also get HEVC decoding.
(2014-02-11, 09:07)OllieB Wrote:(2014-02-10, 23:04)bustamelon Wrote:(2014-02-10, 22:54)OllieB Wrote: When I try to change the value in the Wake on LAN dropdown box to stay off the Visual BIOS screen freezes and I cannot make any further changes. I have to manually use the power button to switch the NUC off and on to try again. Tried about five times now, without success.That sucks. Do you have a regular keyboard and mouse connected? I found that with one of those battery powered wireless deals, I had the same issue for some reason, but once I hooked up a real keyboard/mouse, all was fine.
(2014-02-10, 22:54)OllieB Wrote: Un-checking Deep S4/S5 does not make a difference in so far that I am still not able to wake up the NUC with the remote.
Bummer. In that case, disabling all WOL features is your only option until they fix it. But of course your freezing csreen issue will prevent that.
(2014-02-10, 22:54)OllieB Wrote: The funny thing is that in the process I have now also lost the NUC starting screen with the message F2, F7 etc and have to guess when to press the F2 keyThere is an option for that somewhere as well.
* Edit - under Boot->Boot Configuration->Boot Display Config
Also, uncheck "Fast Boot" in the left hand side [UEFI BOOT].
I currently only have a WIRED keyboard attached, but no mouse. I will try attaching and using a mouse this evening to see whether that makes a change. I will also disable the UEFI boot option and check the display option mentioned. Thanks for the suggestions.
(2014-02-11, 20:09)OllieB Wrote: YES! Using a mouse solves the freeze problem as already confirmed by others as well.
However,
- with Deep S4/S5 disabled,
- wake on Lan disabled,
- Enhance IR enabled,
- UEFI boot disabled
I am still NOT able to wake up the NUC with my remote. Powering off works with the remote so I am fairly sure that the remote functions (I am using the Xbox 360 media remote). I have also not been able to restore displaying the NUC logo screen which means I have to guess when to press F2
Any further ideas
(2014-02-11, 20:08)Jorgensen Wrote: No, not necessarily on the NUC. I can always connect like this: http://support.code42.com/CrashPlan/Late...ess_Client But I still need to install the Crashplan SW on the NUC in the first place. And I am still not convinced that this is possible using OPENElec. And therefore, I was hoping that the black/gray fix was already implemented in XBMCbuntu.
Sorry for going OT.
Thanks. But as long as the black/washed out gray fix is not implemented in XBMCbuntu, I won't install XBMCbuntu.
(2014-02-11, 20:42)bustamelon Wrote:(2014-02-11, 20:09)OllieB Wrote: YES! Using a mouse solves the freeze problem as already confirmed by others as well.
However,
- with Deep S4/S5 disabled,
- wake on Lan disabled,
- Enhance IR enabled,
- UEFI boot disabled
I am still NOT able to wake up the NUC with my remote. Powering off works with the remote so I am fairly sure that the remote functions (I am using the Xbox 360 media remote). I have also not been able to restore displaying the NUC logo screen which means I have to guess when to press F2
Any further ideas
Did you CHECK "wake system from S5" ? (I assume so, probably not applicable anyway if you have deep sleep disabled).
Have you tried running irw to make sure the power on command is being sent from the remote?
http://wiki.xbmc.org/index.php?title=LIRC
(2014-02-11, 21:14)OllieB Wrote:(2014-02-11, 20:42)bustamelon Wrote:(2014-02-11, 20:09)OllieB Wrote: YES! Using a mouse solves the freeze problem as already confirmed by others as well.
However,
- with Deep S4/S5 disabled,
- wake on Lan disabled,
- Enhance IR enabled,
- UEFI boot disabled
I am still NOT able to wake up the NUC with my remote. Powering off works with the remote so I am fairly sure that the remote functions (I am using the Xbox 360 media remote). I have also not been able to restore displaying the NUC logo screen which means I have to guess when to press F2
Any further ideas
Did you CHECK "wake system from S5" ? (I assume so, probably not applicable anyway if you have deep sleep disabled).
Have you tried running irw to make sure the power on command is being sent from the remote?
http://wiki.xbmc.org/index.php?title=LIRC
Checking Wake system from S5 is NOT checked but as I am not using deep sleep S4/S5 I do not think that this would be related.
Yes I have used irw to check that the power button sends a command and yes it does (also demonstrated by the fact that I can power off the NUC using the remote). The information returned by irw is:
74 0 KEY_POWER devinput
74 0 KEY_POWER_UP devinput
I have noticed that the remote device is not listed in /proc/acpi/wakeup as a device that is enabled for S3, this is something I was reading on the internet but I am not sure this file is still used under openelec