[mythtv-users] SBE is "currently not connected instead" of "currently asleep"

Herman Gerritsen lfsmailing at gmail.com
Sat Jan 21 14:23:30 UTC 2012


Sorry for the late reponse. But I was busy on changing my setup to one
without SBE's
So now I always have two systems on when i watch videos :)

My setup now consists of A dedicated master backend (with working
wakeup on lan and bios timer) and a dedicated frontend that can wakeup
my master backend (so I am happy that this works as expected, yet I
would like a working SBE with my tuner cards)

>     I have a similar setup using WOL, that mostly works ok.  Sometimes
> the SBE's status, for reasons unknown will change from asleep to
> disconnected, but mostly it works as expected.
So you're SBE usually reports as "asleep" mine only did that for a few
seconds and changed to "disconnected".
Did you use scripts to shut the SBE down? or just commands as I did,
configured from the mythtv-setup on the SBE itself?

>     I had difficulty setting it up due to sparse documentation on what
> the shutdown, wake, sleep commands actually do.
>     I ended up using a wrapper script for the wake command, mainly to
> diagnose what was actually going on, and once I got it working, I left
> it as is.  So I have:
>
>         wake command:  /usr/bin/wake_tv02.sh
>
>     wake_tv02.sh
>     --------------------
>     #!/bin/bash
>     logger -t "wake_tv02.sh" "Waking TV02"
>     wakeonlan <tv02 mac address>

Okay I just used "wakeonlan <SBE mac address>" without the wrapper I
never tried a script I can not imagine that it would make a difference
(so maybe I should have tried it...)
What is the "logger -t" command?

Greetings,
Herman


More information about the mythtv-users mailing list