I'm using the wakeupshutdown.py plugin with nvram, which works "fine" except:
My system is running UTC, so if I select a program to record that starts at 22:00, and shutdown the system the wake up time is set correctly in the BIOS to 22:00. But the clock in the BIOS is one hour behind my "system" clock, so when it's time to start recording, the computer will first start an hour to later, when the BIOS's clock has reached 22:00, but in reality the clock is 23:00 A simple solution would be to modify line 315 in the wakeupshutdown.py plugin to subtract 1 hour from wakeup_time like this: wakeup_time = start_time - config.TV_RECORD_PADDING - config.BOOTTIME_PADDING - 1 But there should be a solution that works for everybody, but I don't know where to start. I'm running Gentoo with Freevo 1.5.4 and some of the files that might be relevant for a solution are: /etc/conf.d/clock # contains CLOCK="UTC" /etc/localtime # points to /usr/share/zoneinfo/Europe/Copenhagen the "date" command says that I'm in the CET timezone output of: /sbin/hwclock --debug --test hwclock from util-linux-2.12r Using /dev/rtc interface to clock. Last drift adjustment done at 1131830004 seconds after 1969 Last calibration done at 1131830004 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2005/11/12 21:53:22 Hw clock time : 2005/11/12 21:53:22 = 1131832402 seconds since 1969 Sat Nov 12 22:53:22 2005 -0.455735 seconds Note that Hw clock is one hour behind system clock. -- Mvh. / Kind regards Henrik Farre - http://www.rockhopper.dk
signature.asc
Description: Dette er en digitalt underskrevet brevdel
