[mythtv-users] Carbon Footprint

Daryl McDonald darylangela at gmail.com
Sun Sep 1 18:28:31 UTC 2013


On Sun, Sep 1, 2013 at 11:51 AM, Stefan Pappalardo <sjuk at gmx.de> wrote:

>  Hi Daryl, here you are.
>
> Operating System: Ubuntu 12.04.3 LTS
> Motherboard: Gigabyte GA-MA785GM-US2H
> BIOS RTC (real time clock) is set to UTC (not set to localtime)
>
> The machine is backend and frontend.
> Mythshutdown is controlled by mythwelcome.
>
> Power Management Setup
> ---------------------------------------
> ACPI Suspend Type: S3 (STR)
> HPET-Support: Disabled
> Power-On by Alarm: Disabled
> ErP Support: Disabled
>
> Hints
> -------
> 1: With HPET-Support and ErP Support enabled all seemed to work fine, but
> the system never waked up.
> 2: Setting a fixed Power-On by Alarm time can get into conflict with the
> time mythtv sets. In my case it only works when I disable it in BIOS.
> 3: I can only choose between S1 (Power on Suspend) and S3 (Suspend to RAM)
> in BIOS. But I always use S5 (Soft Off).
>
> Kernel
> ---------
> sjuk at obelix:~$ uname -r
> 3.2.0-52-generic
>
> sjuk at obelix:~$ sudo grep -i rtc /var/log/dmesg
> [    0.157612] RTC time: 14:28:52, date: 09/01/13
> [    1.592355] rtc_cmos 00:04: RTC can wake from S4
> [    1.592440] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
> [    1.592466] rtc0: alarms up to one month, 242 bytes nvram
> [    1.598070] rtc_cmos 00:04: setting system clock to 2013-09-01 14:28:54
> UTC (1378045734)
>
> sjuk at obelix:~$ cat /proc/driver/rtc
> rtc_time    : 14:50:45
> rtc_date    : 2013-09-01
> alrm_time    : 06:10:00
> alrm_date    : 2013-09-02
>
> alarm_IRQ    : no
> alrm_pending    : no
> update IRQ enabled    : no
> periodic IRQ enabled    : no
> periodic IRQ frequency    : 1024
> max user IRQ frequency    : 64
> 24hr        : yes
> periodic_IRQ    : no
> update_IRQ    : no
> HPET_emulated    : no
>
> BCD        : yes
> DST_enable    : no
> periodic_freq    : 1024
> batt_status    : okay
>
> Disable hwclock updates
> ---------------------------------
> On my system there is no need to disable the hwclock updates
>
> Setwakeuptime (don't forget to make it executable)
> -----------------------------------------------------------------
> sjuk at obelix:~$ cat /usr/bin/setwakeup.sh
> #!/bin/sh
> #
> # set ACPI Wakeup time
> # usage: setwakeup.sh seconds
> #    seconds - number of seconds from epoch to UTC time (time_t time
> format)
> #
> # set UTCBIOS to true if bios is using UTC time
> # set UTCBIOS to false if bios is using local time
>
> UTCBIOS=true
>
> if $UTCBIOS
> then
>     #utc bios - use supplied seconds
>     SECS=$1
> else
>     #non utc bios - convert supplied seconds to seconds from
>     #epoch to local time
>     SECS=`date -u --date "\`date --date @$1 +%F" "%T\`" +%s`
> fi
>
> echo 0 > /sys/class/rtc/rtc0/wakealarm       # clear alarm
> echo $SECS > /sys/class/rtc/rtc0/wakealarm   # write the waketime
>
> Sudo
> -------
> sjuk at obelix:~$ sudo cat /etc/sudoers.d/mythwelcome
> Defaults:mythtv !requiretty
> %mythtv ALL = NOPASSWD: /bin/sh, /usr/bin/setwakeup.sh, /sbin/shutdown,
> /usr/bin/mythshutdown
>
> Backend (General > Shutdown/Wakeup Options)
> --------------------------------------------------------------
> Block shutdown before client connected: unchecked
> Idle shutdown timeout (secs): 180
> Max. wait for recording (min): 15
> Startup before rec. (secs): 600
> Wakeup time format: time_t
> Command to set Wakeup Time:  sudo sh -c "/usr/bin/setwakeup.sh $time"
> Server halt command: sudo shutdown -h now
>
>
> When you have a question please post your settings corresponding to the
> question.
>
> Good Luck ;-)
>
> Stefan
>
> Am 31.08.2013 22:44, schrieb Daryl McDonald:
>
>
>
>
> On Thu, Aug 29, 2013 at 11:56 AM, Stefan Pappalardo <sjuk at gmx.de> wrote:
>
>>  Hello Daryl,
>>
>> I did not read the hole thread but I think Michael is right when pointing
>> to permissions and sudo will be the solution.
>> I'm using mythbuntu 12.04 and had to use sudo: search for sudoers in
>> http://www.mythtv.org/wiki/ACPI_Wakeup
>>
>> I'm using the mythwelcome-mythshutdown-solution, and had to do several
>> configurations.
>> (Bios, mythtv-setup, mythwelcome, setwakeup.sh, sudoers, ...)
>>
>> When you are interested I can give you more details of my setup. Only ask
>> what you need.
>>
>> Stefan Pappalardo
>>
>> Am 29.08.2013 17:36, schrieb Daryl McDonald:
>>
>
>  Hey Stefan, I would appreciate it if you would share your Mythtv
>  configuration with me, specifically: backend>general>Shutdown/Wakeup
> Options & Backend Wakeup Settings. The wiki unclear, for me, on some of
> those values. Also, does your BIOS use RTC or UTC?
>
>  Daryl
>
>>
>>
>>
>> On Thu, Aug 29, 2013 at 11:29 AM, Michael <mythtv at blandford.net> wrote:
>>
>>>   On 08/29/2013 08:27 AM, Daryl McDonald wrote:
>>>
>>>
>>>
>>>
>>> On Thu, Aug 29, 2013 at 11:11 AM, Michael <mythtv at blandford.net> wrote:
>>>
>>>> On 08/29/2013 07:59 AM, Daryl McDonald wrote:
>>>>
>>>>>
>>>>> Of the three commands the first one gets no complaint, with the second
>>>>> attempt I did add the "sudo" preface and still I'm denied:
>>>>>
>>>>> daryl at daryl-A780L3C:~$ SECS=`date -u --date "2013-08-29 10:50:00" +%s`
>>>>> daryl at daryl-A780L3C:~$ sudo echo 0 > /sys/class/rtc/rtc0/wakealarm
>>>>> bash: /sys/class/rtc/rtc0/wakealarm: Permission denied
>>>>> daryl at daryl-A780L3C:~$ sudo echo $SECS > /sys/class/rtc/rtc0/wakealarm
>>>>> bash: /sys/class/rtc/rtc0/wakealarm: Permission denied
>>>>>
>>>>> See! I remain open to suggestions.
>>>>>
>>>>>
>>>>
>>>>  This is because the echo is running as root, but the redirect is not,
>>>> hence the permission denied.  If you want to use sudo you would need to do
>>>> something like:
>>>>
>>>> sudo sh -c 'echo 0 > /sys/class/rtc/rtc0/wakealarm'
>>>>
>>>> Or just become root and run the command.
>>>>
>>>> Michael
>>>>
>>>>
>>>> _______________________________________________
>>>> mythtv-users mailing list
>>>> mythtv-users at mythtv.org
>>>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>>>
>>>
>>  Thanks Michael, It looks like I'm good now:
>>
>>   daryl at daryl-A780L3C:~$ cat /proc/driver/rtc
>> rtc_time : 11:33:21
>> rtc_date : 2013-08-29
>> alrm_time : 11:37:32
>> alrm_date : 2013-08-29
>> alarm_IRQ : no
>> alrm_pending : no
>> update IRQ enabled : no
>> periodic IRQ enabled : no
>> periodic IRQ frequency : 1024
>> max user IRQ frequency : 64
>> 24hr : yes
>> periodic_IRQ : no
>> update_IRQ : no
>> HPET_emulated : yes
>> BCD : yes
>> DST_enable : no
>> periodic_freq : 1024
>>  batt_status : okay
>> daryl at daryl-A780L3C:~$
>>
>>>
>>>  My son warned me about becoming root, I am still quite a newbie, and
>>> it shows, below is what happened when I tried the first option:
>>>
>>>   daryl at daryl-A780L3C:~$ SECS=`date -u --date "2013-08-29 11:45:00" +%s`
>>> daryl at daryl-A780L3C:~$ sudo sh -c echo 0 > /sys/class/rtc/rtc0/wakealarm
>>> bash: /sys/class/rtc/rtc0/wakealarm: Permission denied
>>> daryl at daryl-A780L3C:~$ sudo sh -c echo $SECS >
>>> /sys/class/rtc/rtc0/wakealarm
>>> bash: /sys/class/rtc/rtc0/wakealarm: Permission denied
>>> daryl at daryl-A780L3C:~$
>>>
>>>  I'm still looking at bricks, this shouldn't be that complicated,
>>> should it?
>>>
>>>  Daryl
>>>
>>>
>>>
>>>  You seem to be missing the ' marks before the echo and at the end of
>>> the line.
>>>
>>> Michael
>>>
>>>
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
>>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>
>>
>>  Shutting down now to test
>>
>>  Thanks to all Daryl
>>
>>
>>
>> _______________________________________________
>> mythtv-users mailing listmythtv-users at mythtv.orghttp://www.mythtv.org/mailman/listinfo/mythtv-users
>>
>>
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>
>>
>
>
> _______________________________________________
> mythtv-users mailing listmythtv-users at mythtv.orghttp://www.mythtv.org/mailman/listinfo/mythtv-users
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users


The wiki didn't cover it and your settings don't either, so I'm forced to
assume that the "Startup Command" should be left
blank?(Backend>General>Shutdown/Wakeup options page) My system will shut
the backend down but will not wakeup for recordings, at this point. I can
find no reference of what to put in the "Startup Command" box. Secondly I
am using, to the best of my knowledge, Local time in the RTC, because I
employ a dual boot, and as I compair terminal out put it seems to be off by
a day:
daryl at daryl-A780L3C:~$ sudo grep -i rtc /var/log/dmesg
[sudo] password for daryl:
[    0.200520] RTC time: 14:43:57, date: 08/31/13
[    1.242563] rtc_cmos 00:03: RTC can wake from S4
[    1.242708] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[    1.242731] rtc0: alarms up to one month, y3k, 114 bytes nvram
[    1.250110] rtc_cmos 00:03: setting system clock to 2013-08-31 14:43:58
UTC (1377960238)

I got this reading Sunday Sept 1st just before 2p.m.

Although the time is correct from this probe:

daryl at daryl-A780L3C:~$ cat /proc/driver/rtc
rtc_time : 13:32:16
rtc_date : 2013-09-01
alrm_time : 18:45:00
alrm_date : 2013-08-31
alarm_IRQ : no
alrm_pending : no
update IRQ enabled : no

Apparently one of my attempt to wakeup is still showing because it failed
to execute.
I did insert a disable hwclock script as directed by the wiki, how did you
discern that it wasn't needed in your case?

Below is my setwakeup.sh, quite different than yours, is this due to the
local verses UTC difference?:
daryl at daryl-A780L3C:~$ cat /usr/bin/setwakeup.sh
#!/bin/sh
#$1 is the first argument to the script. It is the time in seconds since
1970
#this is defined in mythtv-setup with the time_t argument

echo 0 > /sys/class/rtc/rtc0/wakealarm      #this clears your alarm.
echo $1 > /sys/class/rtc/rtc0/wakealarm     #this writes your alarm
daryl at daryl-A780L3C:~$

I have what has been referred to as the "fussy BIOS" too, and thought I was
getting somewhere, because after shutting down the system, before midnight,
I would find it on the next morning. I had enabled wake from RTC and left
the default setting "every day" and "00:00:00". Below is my kernel:
daryl at daryl-A780L3C:~$ uname -r
3.5.0-39-generic
My values appear after the > symbol
Block shutdown before client connected: unchecked >  checked, maybe I
misinterpreted?
Idle shutdown timeout (secs): 180 > currently at 0 to disable shutting down
Max. wait for recording (min): 15 > can't remember why I set to 120
Startup before rec. (secs): 600 > 600
Wakeup time format: time_t  > time_t
Command to set Wakeup Time:  sudo sh -c "/usr/bin/setwakeup.sh $time" >
sudo /usr/bin/setwakeup.sh $time (wiki didn't cover sh -c or quotation
marks)
Server halt command: sudo shutdown -h now > sudo shutdown -p

Then there is the next page "Backend Wakeup Settings":
Delay between wake attempts (secs)  default 0
Wake attempts  default 5
Wake Command   blank
It continues with slave backend settings, which I don't have, but I need
direction for the first three boxes.

Daryl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130901/1fb4177f/attachment-0001.html>


More information about the mythtv-users mailing list