Hi All,

I've been running mythwelcome on KM for a few versions now, and generally its been a solid performer. I'm using ACPI according to the KM wiki
http://www.knoppmythwiki.org/index.php?page=MythWelcome and the myth wiki
http://www.mythtv.org/wiki/index.php/ACPI_Wakeup.

In recent weeks ive noticed that a few programs have not recorded, as the machine has not woken up. I'm not sure now if the wakeup has worked since i went to R5.5.

I run the following commends to see if my configuration is correct
and then issue


This sets the alarm time to +4 mins, and shuts the machine down. In 4 minutes the machine wakes up. No problem. The /tmp/alarm.log looks like this



If i schedule a program to record in 30 mins time, then mythwelcome will shutdown the computer, but it doesnt wakeup. When i manually start the machine up, the following is in /tmp/alarm.log



Now, looking at the alarm.log files above, the main difference i can see in what is logged at shutdown time is the "time-since-epoch" value. In the manual test, the correct value was set in /tmp/alarm

In the mythwelcome shutdown, the /tmp/alarm value is ALWAYS the following


It doesnt matter when (or how many times) i let mythwelcome shutdown the machine the "time-since-epoch" value is always


So, i'm thinking that it MUST be an error in how im passing the shutdown $time value from mythbackend/mythwelcome to the mythwelcome-set-alarm.sh script? My settings for both the backend and the mythwelcome are as per the wiki detail (i believe, although it was late).

I must admit that i'm not 100% clear on which settings do what on mythbackend/mythwelcome, there seems to be some duplication of settings?

Any ideas?

Cheers,

Nathan

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector

Did you have a show scheduled to record around October 24th, 2008 11:29:00 AM?

I noticed my box skipped a couple shows. Thinking back, I shutdown the box shortly before in both cases. This might be a bug that shows in the near future are ignored....

Try scheduling a show farther in the future. Two numbers that might prove interesting are:

1. >1 hour in the future (say 1:15)

2. Your timezone difference from UTC + 15mins (ex. if you are UTC+5, try recording something 5:15 in the future).

If that is the problem, you can increase the "Max wait for recording" parameter as a work-around.
Allen

_________________
ASUS AT3N7A-I (Atom 330)
TBS 8922 PCI (DVB-S2)

Thanks for the reply, it seems that i might have been a bit too clever for myself.

I must have changed the setting in mythsetup from

to


The problem being the --settime instead of --setwakeup...

Seems that because of this innapropriate change the "time to wakeup" was never getting passed to the KM set-alarm script, and taking a default/old value (i guess).

I have corrected it (to what the KM wiki says), and set a program to record in 10 minutes time, and it started up... excellent...

Other things is changed, possibly unrelated tonight are
1) Added /tmp/alarm and /tmp/alarm.log to /etc/sudoers

I'll probably remove this from sudoers... thanks for your help.
Hopefully this works all the time now... otherwise, i'm back to pulling hair.

Cheers,

Nathan

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector