Hi,
First off, thank you for fantastic product. We are using Raspberry Pi 3 as thin-client with WTware as OS.
I have problems specifically related to Raspberry Pi's absent of a power button/switch. Here is the scenario:
User connects to a remote virtual machine via WTware. Once work is done, user log off remote virtual machine. A few things happen here:
- If parameter "turnoffmenu" is poweroff, then the Raspberry Pi will power off
- If parameter "turnoffmenu" is anything else, then user can either power off the Raspberry Pi, or leave it on
If user decided to turn off Raspberry Pi. There is no way to turn it back up, except for unplug & replug USB power cord. This is quite inconvenient & will shorten longevity of USB power port on Raspberry Pi.
My question/suggestion is:
- Is there a "sleep" mode on WTware? Let's say user log off remote virtual machine, WTware put Raspberry Pi in a sleep mode that can be awaken by touch of any keyboard, mouse event. If yes, how do we invoke it?
- I do see a "sleep" parameter, but my understanding tells me that is for the monitor.
- Ideally, this is what I would like to see:
1. User log off remote virtual machine, WTware puts Raspberry Pi in low-power state, sleep state if you will
2. Raspberry Pi can be awaken either via keyboard/mouse event (preferably just keyboard) or via network from a server
Is this possible, hard to implement?
Once again, thank you very much for such a great package.
WTware & Raspberry Pi power on
Re: WTware & Raspberry Pi power on
There is no sleep mode or low-power state on Pi. I don't know about this in hardware, so we can not do it in software.
Re: WTware & Raspberry Pi power on
We have decided to just leave the RPi itself to run forever; it's consumption at 1W idle is about the same as a PC in sleep anyway. It can be made to put the monitors to sleep via config.txt,
And, adding to the profile,
Should you need to reboot the Pi for some reason, it can be done from the management console or via http, eg wget http://[ip-address]/reboot
Another option, if your screens have a powered USB hub in them, is to power the RPi from a screen USB port, so it will die when the monitor is turned off. But that requires manual intervention and time to reboot of course, if running network boot over high latency lines it does take a while (compared to on LAN) due to lack of windowing in TFTP protocol.
Hope that helps.
Code: Select all
# Enable HDMI Power Management
hdmi_blanking=1
Code: Select all
sleep=10,poweroff
Another option, if your screens have a powered USB hub in them, is to power the RPi from a screen USB port, so it will die when the monitor is turned off. But that requires manual intervention and time to reboot of course, if running network boot over high latency lines it does take a while (compared to on LAN) due to lack of windowing in TFTP protocol.
Hope that helps.