I've done some testing over the previous months regarding getting the IceBox to wake using the RCU. So far, I have had no success. However, here is what I tried and what I found. Perhaps someone else may have some other ideas.
Lets start with a positive - Timed Waking
The IceBox supports Linux rtcwake capabilities. This means that the unit can be woken from a powered-off state in order to perform recordings. I had to write directly to the RTC device in order for this to happen, but at least it is possible. Perhaps Kodi can already utilise this feature, more investigation is required.
And now for the rest - Sleeping / waking, etc.
I have tested the IceTV remote with its USB dongle in a Windows 10 PC and a PC running Ubuntu. On both systems, the ICE RCU was able to generate arrow keys, etc, and the power key was able to put those systems to sleep/hibernate.
Unfortunately, the IceTV RCU was unable to wake either system. Both systems would wake on USB keyboard input and I even tried plugging the ICE dongle into the exact same port that a known good waking USB keyboard was in plugged into, however, the systems could not be woken with the ICE RCU.
Given that the IceBox can not be woken with the ICE RCU, perhaps a real USB keyboard can wake it. Unfortunately not. I have been unable to make a USB keyboard wake the IceBox.
Perhaps the IceBox can't be woken because it can't get to sleep in the first place.
Most modern computers can 'sleep' where memory is kept active but the rest of the computer is shut down and 'hibernate' where the memory is saved to disk before the unit is powered off.
I could get neither of these modes to work.
During my tests, I discovered that LibreELEC (the OS that the IceBox is based on) has 'swapping' disabled by default. This feature is required for systems to be able to hibernate.
I followed the instruction and got a swapfile working, however, I was still unable to get the unit to hibernate. Kodi would sort of freeze in a dimmed state and a full power reset was required to return the unit to operation.
Quote from: DeltaMikeCharlie on July 19, 2023, 10:12:30 AMPerhaps someone else may have some other ideas.
My box is a BYOB Intel/Lenovo so what I have observed may not be related in any way to the stock IceBox, per-se.
This is how it is for me:
The box suspends to a low power state from the shutdown/suspend menu. The tuners also shut down... they're plugged into USB3 ports.
The system will not suspend or shutdown via the Idle Timer. But will wakeup for a timed recording or the wakeup timer.
The system will not wake-up using the RCU but will wake up with a USB keyboard (space-bar, for example). And it will wake up when using a Rii mini wireless keyboard with its dongle plugged into any USB2 port. Either the space bar or the home button (at least) will wake up the system.
My RCU also seems to exhibit contact bounce on occasion, in any Kodi page or any menu. Particularly irksome when you want to skip 3 minutes and get 10...
I have ordered a Flirc dongle so will see what that can do for me when it arrives. I don't have any serious Linux know how so time will tell. I may need help with keymapping.
Quote from: srto2 on July 19, 2023, 10:39:22 AMThe box suspends to a low power state from the shutdown/suspend menu. The tuners also shut down... they're plugged into USB3 ports.
The system will not suspend or shutdown via the Idle Timer. But will wakeup for a timed recording or the wakeup timer.
The system will not wake-up using the RCU but will wake up with a USB keyboard (space-bar, for example). And it will wake up when using a Rii mini wireless keyboard with its dongle plugged into any USB2 port. Either the space bar or the home button (at least) will wake up the system.
Thanks. This is good information to have.
From your data, it would appear that the underlying LibreELEC OS has no fundamental problems with the whole hibernate/wake process. This points towards the capability of the IceBox hardware. There is a minor possibility that the hardware does support this but that the BIOS does not and that a BIOS update could add support.
I know that IceTV have said that the IceBox is intended to be run 24x7, however, this does not suit my needs. I am not 100% sure if the IceBox is suitable for my production environment.
Quote from: srto2 on July 19, 2023, 10:39:22 AMI may need help with keymapping.
Post your questions to the forum. I had already done some work mapping buttons for skipping:
https://oztoppy.forumchitchat.com/post/remote-control-testing-12529503?highlight=kodi&pid=1334309292 (https://oztoppy.forumchitchat.com/post/remote-control-testing-12529503?highlight=kodi&pid=1334309292)
Quote from: srto2 on July 19, 2023, 10:39:22 AMI don't have any serious Linux know how so time will tell.
You can copy keymaps to the IceBox via the Windows Explorer on a Windows PC. No Linux knowledge required.
Delta Mike Charlie, I checked the BIOS/UEFI of my beta IceTV IceBox and it does not seem to have settings for wake on keyboard/mouse/network. This is physically different from the production model, and while apparently have the same BIOS it has a different date. My BYOB IceBox has Intel BIOS/UEFI. It seems to support wake on LAN and Wake on System (whatever that means). Will investigate further.
I have looked at the IceBox BIOS many times and I have been unable to find anything relating to this. I'm not saying that it's not there, I'm just saying that I can't recognise it if it is.
What I meant about my previous BIOS statement was that perhaps the physical USB controllers soldered to the motherboard are capable of waking on USB. In spite of this, if the BIOS is not recognising this capability or advertising it to the OS, then we can't take advantage of it.
I have also searched for the manufacturer online in search for a BIOS update with no success thus far.
On my test Ubuntu PC, I actually had to enable 'Wake on LAN' in the BIOS to enable waking from USB keyboard. However, on my main PC, I have a special 'Wake on USB' setting that I needed to enable. Every BIOS is slightly different.
On further investigation it appears that my BYOB Intel NUC only supports wake on LAN (from S4/S5 and wake system from S5), not wake on Keyboard/Mouse.
Ian
Quote from: IanL-S on July 19, 2023, 03:08:38 PMOn further investigation it appears that my BYOB Intel NUC only supports wake on LAN (from S4/S5 and wake system from S5), not wake on Keyboard/Mouse.
Try enabling the 'Wake on LAN' option and see if that enables waking via keyboard as well.
This Microsoft article seems to suggest that S4 also covers USB.
https://learn.microsoft.com/en-us/windows/win32/power/system-power-states (https://learn.microsoft.com/en-us/windows/win32/power/system-power-states)
Quote from: IanL-S on July 19, 2023, 03:08:38 PMOn further investigation it appears that my BYOB Intel NUC only supports wake on LAN (from S4/S5 and wake system from S5), not wake on Keyboard/Mouse.
That looks more like a problem with the LibreELEC installation that with the NUC. A Pentium Silver NUC I just configured for WOL will wake from S5, but only from a S3 sleep state if configured to do so from the Windows device manager. Without a similar setting in LibreELEC I suspect it would also fail there.
I suspect that the same scenario might apply to the 8th generation NUC that I run IceBox BYO, but without changing the boot order to load Windows I cannot check.
All subsequent NUCs that I have are cursed with Modern Standby that triggers wake on the slightest movement of input peripherals, so no comparison possible.
I an definitely no expert on NUCs, but I am wondering if this could be an electrical issue rather than a software issue.
Is power supplied to the USB ports when the Icebox is shut down?
i.e. if not, the dongle wouldn't be powered and therefore couldn't be able to receive the RF from the Remote.