Hi All,
My PC wakes up one hour too late. In everything.log I see the PC wants to wake up 03:15, but wakes up 4:15 instead.
" Nov 2 00:37:03 TV vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.acpiwakeup Nov 2 00:37:03 TV vdr-addon-acpiwakeup: Setting ACPI alarm time to: 2012-11-02 03:15:00 .. Nov 2 04:15:40 TV kernel: [ 0.000000] Initializing cgroup subsys cpuset " $ cat /proc/driver/rtc rtc_time : 18:26:10 rtc_date : 2012-11-02 alrm_time : 03:15:00 alrm_date : 2012-11-03 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
$ date Fri Nov 2 18:26:34 CET 2012
$ uname -a Linux TV 3.6.2-1-ARCH #1 SMP PREEMPT Fri Oct 12 23:58:58 CEST 2012 x86_64 GNU/Linux
The following does not wake up my PC within 5 minutes: # echo 0 > /sys/class/rtc/rtc0/wakealarm # echo `date '+%s' -d '+ 5 minutes'` > /sys/class/rtc/rtc0/wakealarm # cat /proc/driver/rtc rtc_time : 18:31:01 rtc_date : 2012-11-02 alrm_time : 18:35:34 alrm_date : 2012-11-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
[cedric@TV cedric]$ hwclock Fri Nov 2 21:14:26 2012 -0.610421 seconds [cedric@TV cedric]$ date Fri Nov 2 20:14:37 CET 2012
I use ntpd, si i guess /etc/ntp.conf is of interest :-) [cedric@TV cedric]$ cat /etc/ntp.conf # With the default settings below, ntpd will only synchronize your clock. # # For details, see: # - the ntp.conf man page # - http://support.ntp.org/bin/view/Support/GettingStarted # - https://wiki.archlinux.org/index.php/Network_Time_Protocol_daemon
# Associate to public NTP pool servers; see http://www.pool.ntp.org/ server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org
# Only allow read-only access from localhost restrict default noquery nopeer restrict 127.0.0.1 restrict ::1
# Location of drift and log files driftfile /var/lib/ntp/ntp.drift logfile /var/log/ntp.log
# NOTE: If you run dhcpcd and have lines like 'restrict' and 'fudge' appearing # here, be sure to add '-Y -N' to the dhcpcd_ethX variables in /etc/conf.d/net
Cedric,
yes of course, you do use ntp, the clock runs correctly, good.
But that wasn't the issue I did ask for. Using "acpiwakeup", does need to set the hardware clock to UTC timezone.
So, if you don't live in Greenwich next to London or within this timezone at all, there should most probably be a difference between the hardware clock of your VDR and it's system time.
If your hw clock doesn't run at UTC time, you may see wakeup shifts like you did describe it. Some hours before or ahead, where ever you're living.
You can check RTC's time with the command "sudo hwclock" and check if it does run on UTC time, comparing to your systems time, according to "/etc/timezone".
=== Regards fnu
PS.: IIRC it is possible to configure "acpiwakeup" not to need RTC in UTC, pls. check documentation for that ...
Hi,
based on your last topics I'm assuming you are using ArchVDR. If you have already moved to systemd and your RTC is set to UTC, chances are you're experiencing this bug: http://sourceforge.net/apps/trac/archvdr/ticket/160 Just apply the patch and check if your PC wakes up correctly.
Best Regards
Am 02.11.2012 18:57, schrieb cedric.dewijs@telfort.nl:
On Sun, Nov 4, 2012 at 11:09 AM, cedric.dewijs@telfort.nl wrote:
I have applied the patch, disabled ntpd, and set the BIOS clock correctly.
You don't have to disable ntpd. You just have to make sure your BIOS clock is set correctly.
-
cedric.dewijs＠telfort.nl -
fnu -
Ole Ernst -
VDR User