Evening all,

I am wanting to get nvram-wakeup feature fully functioning. After playing with guess-helper and getting the config right for the wake up to record feature working I ran into a problem.

Using this code I tested the pc's wake up on alarm: sudo nvram-wakeup -s $((`date +%s` + 900)) and the wakeup time is set in the BIOS with no warnings , and the pc shut down. Then it doesn't wake up.

This is a porblem caused by British Summer Time. My BIOS clock is correct on GMT - it does not have BST applied to it, so at 9pm, the BIOS clock says 8pm.

Unfortunately the decrepancy between the BIOS clock and the system clock the 15 mins into the future is 23 hours and 15 minutes away or if you look at it another way it is 45 mins ago.

Neither is particularly helpful.

Now, BST doesn't last for too much longer and that means my the BIOS and the system clock will agree, but this will mean in six months time I have a problem again.

Any ideas?

Thanks

BTW- I've followed the wiki for this so far - with and without MythWelcome.

_________________
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)

Very strange. I'm on WEDT (UTC+2) and I don't have this problem (BIOS is on UTC). It sounds like a timezone issue, even though you seem to have checked it.

I would recommend checking:

"date" (should print correct BST)

"date -u" (should print correct UTC)

Also check all your BIOS settings for the clock. I believe some BIOSes may have a local vs. UTC config setting.

Finally, run tzconfig and make sure all is correct.

Good luck!

Allen

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

Hi alien, Thanks for the reply.
I ran date then date -u.
For the former I got: Thur 14 Sept 21:14:27 BST
For the latter I get: Thur 14 Sept 20:14:29 UTC
Could this be a descrepancy between these? i,e, Myth is aware of BST?
Perhaps I should try and get iit onto UTC, but I think that's what really messed up my on screen display before...

_________________
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)

Hmmm... that's strange... Yes, myth takes timezone into account. Anyway, you are seeing the problem with nvram-wakeup -s $((`date +%s` + 900)), so myth isn't involved. Only nvram-wakeup and date.

Run tzconfig just to be sure. Maybe you have set the zone with TZ instead of configuring a default. This might mess up nvram-wakeup.

If that doesn't work, a few other things to see what is really being set:

"hwclock" will read the BIOS clock. Should display in UTC.

Running nvram-wakeup with no parameters after setting the wakeup time displays what was actually set. Should be the wakeup time in UTC (i.e. "hwclock" output plus 15 minutes).

There should be a discrepency in one these.

Allen

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