Hello,
Since upgrading to R5 I've been using mythwelcome, now on my R6 .22 system it's suddenly stopped working.

Here's what I'vebeen doing:
On Sunday I upgraded my Mythbox to the svn packages so I'm now running .22 (which is fantastic btw). I added a new hard drive, then upgraded, after making a good backup. I tested mythwelcome once I'd successfully completed the upgrade and it worked.

On Monday I spent half an hour getting the new Mythvideo features working by adding all the extra storage groups in Mythtv-setup (not managed to get the extra graphics working for recorded tv yet) however, I realised by Wednesday the Mythbox was not turning itself on for record.

So far i've run mythwelcome-test-alarm.sh and the the system shuts down and reboots 4 mins later. I have had a look at Mythwelcome --setup and the relevant page in Mythtv-setup and the details seem correct.

Can anyone point me in the right direction to solve this?

Many thanks

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

The location of the scripts has changed in 6. If you used the full path name in the mythwelcome and mythtv setups, they will have to be changed. The command which <scriptName> at the command line will tell you the new location.

Hope this helps,

Allen

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

Thanks alien,

I believe the location of files and subsequent paths should be unaffected as MythWelcome it was working fine in my R6 install (after initial fix-ups).

The problem appears to be linked to my subsequent upgrade to .22. Mythwelcome seemed to work correctly when I tested afterwards. However certainly after I set up the additional storage groups for the new MythVideo features Mythwelcome is not waking the machine to record.

This would suggest I did something during that fix up, though I can't be 100% sure when Mythwelcome stopped working.

I checked the paths prior to my initial post, but I will do so again as I may have inadvertently mangled something.

Thanks

(edited to make sense - I really shouldn't post after a couple of drinks in the pub)

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

Right, checked and double checked the settings as described in the /usr/LH/bin/mythwelcome-set-alarm.sh file and they are correct. Unless I've gone blind. I even deleted and re-copied some of the longer lines and made sure there were not any lurking spaces at the beginning/end of a command.

Then I checked my /var/log/wake_alarm



If I'm reading this correctly it suggests the time for the alarm is being set to 00:00:00 which is earlier today than now. My current theory i that myth thinks the rtc time is 22:02:51 yesterday instead of the 11 o'clock on November 7th that it actually is.

If this is correct, then I must assume that in upgrading to myth .22 reset my time zone so I am no longer on GMT-0 but somewhere else.

Can someone confirm my diagnosis before I start poking things and making it worse?

Many thanks

Chris

Oh, I almost forgot... checked the BIOS that has the correct time, program guide is correct and displayed time on screen is correct.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

I've been doing some reading. More specifically this document: http://www.mythtv.org/wiki/ACPI_Wakeup#Using_.2Fsys.2Fclass.2Frtc.2Frtc0.2Fwakealarm

After I manually ran sudo mythwelcome-set-wakeup.sh, /var/log/wake_alarm gave me:

rtc_time : 12:44:17
alrm_time : 12:49:17
alrm_date :****-**-08
alarm_IRQ : no
alrm_pending : no
24hr : yes
periodic_IRQ : no
update_IRQ : no
HPET_emulated : yes
DST_enable : no
periodic_freq : 1024
batt_status : okay

However, it didn't seem to wake the computer up. Though that does report alrm_pending as: 'No'.

After reboot, I checked cat /proc/driver/rtc shows the alarm time (alrm_time)
is correct.


According to the ACPI Wakeup - Mythtv the ***** indicates a date in the past. So why is this not working? I've tried to follow the ACPI guide, so I can identify where it's falling down. But i am not getting anywhere.

I'm completely stuck. Any help greatly recieved.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

No one else having this problem?

It's a bit of a show stopper.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

I'm a little confused. Is mythwelcome-test-alarm.sh working? Your first post indicated it is, but reading the others, I'm not so sure.

If I understand correctly, everything worked fine until you upgraded to 0.22 svn. That shouldn't affect mythwelcome-test-alarm.sh or the basic RTC functionality, so I would expect the test to work if it worked before the upgrade.

I would suspect that mythwelcome has changed it's parameters in 0.22. In particular, time format in mythwelcome --setup needs to be seconds since 1970. If that changed, then it won't work correctly.

If you are really stuck, I would suggest adding the following to the bottom of mythwelcome-set-alarm.sh

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

Hi,
You are correct - mythwelcome-test-wakeup.sh does work. But mythwelcome-set-alarm.sh does not wake up my mythbox.

I'll append the line you suggest to the mythwelcome-set-wakeup.sh and see what pops out.

Thank you.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

Hello alien,

I added that line you suggested, but it didn't produce any visible difference in the behaviour of mythwelcome or the information detailed in /var/log/wake_alarm. Do you recommend I remove the original line?

Having re-read the wiki guide again (link above), I think you must be right about the way myth counting of time. The BIOS seems to be using rtc, while I suppose myth is using UTC. I have no idea how to get myth to make the conversion.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

I've not done anything to follow up this thread for a week or so however there have been some developments.

The week before last I was turning the mythbox off after using and turinging it back on when I got home so I would record what I wanted. But, then mythwelcome's behaviour appeared to deteriorate. Mythwelcome would not switch the machine off after a recording had finished. The mythwelcome screen would report idle and do no more.

Last Tuesday everything went crazy, and has been since then (hopefully the craziness will stop tomorrow). So we went away for the weekend and I came back to discover the Mythbox was on and then it turned itself off five minutes after we got back. I was too tired to do anything about it then. Last night this behaviour repeated itself.

Today when I checked if things had been recorded. Guess what - it now appears to be working again. Mythwelcome seems to be working correctly again!!!!!!??????!!!!!!!!!

I'm very glad about this... but I want to know why.

Can anyone suggest reasons or what to look at to find out what was causing this problem?

Many thanks,

Chris

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

Sorry, I've been unavailable the last little while.

If is working, great. If it happens again, it is acting as if the time passed to the set-alarm is incorrect. No need to delete the line above. However, the added line must go at the end.

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

I'm having this this problem again after a rebuild. Unfortunately I'm no nearer to fixing it or understanding why it's not working.

Hopefully it will start to majically work again.

I've checked all the setings as described above, however this time, when I run mythwelocme-test-alarm.sh as user, I get a permission error relating to setting the alarm, but the box wakes up after 4 mins. Perplexing.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

The test script uses sudo to write the wakealarm, so I doubt the permissions problem is there... especially since it woke up correctly (to be sure, make sure root has write access to /sys/class/rtc/rtc0/wakealarm).

I suspect the error message came when the test script reads /proc/driver/rtc. Can you check that user, group and other all have read access to this file. I.e.:
Also, what was in the logfile afterwords?

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

Hi Alien,

Looks like the permissions are fine:



I had a chance to look at logfiles. I can see the mythwelcome shutdown process being called in mythbackend.log



That section came from lastnight setting the wakeup time for later today.

What I see in /var/sys/log/wake_alarm shows me:



While the cat /proc/driver/rtc gives me:


In both, it does not appear the time is set for wakeup.

Odd behaviour.

Any further thoughts?

Chris

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

I can't believe I've missed this flyspray ticket. Anyway, fixed me right up. Who'd have thought they'd change the time format?

Anyway, for those who can't be bothered to read the link here's what alien said:


I suppose (though not checked) this new version of the instructions has been added to the R6.02 release.
As I was running under 'testing' I missed it.
Anyway, I'm glad that's all sorted out now and mythwelcome is doing it's thing.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)