On Wed, 2012-05-23 at 14:57 +0200, e...@kapitein.org wrote: > Hi Alon, > > > > check if you can use: > > /usr/sbin/rtcwake --verbose --seconds 1 --mode disable > > > > Or if disable is not available in your version of rtcwake: > > > > /usr/sbin/rtcwake --verbose --seconds 1 --mode no > > Using UTC time. > > delta = 1 > > tzone = 0 > > tzname = UTC > > systime = 1337703739, (UTC) Tue May 22 16:22:19 2012 > > rtctime = 1337703738, (UTC) Tue May 22 16:22:18 2012 > > alarm 0, sys_time 1337703739, rtc_time 1337703738, seconds 1 > > rtcwake: wakeup from "no" using /dev/rtc0 at Tue May 22 16:22:20 2012 > > > > And you can check the RTC with: > > cat /proc/driver/rtc > > > > rtc_time : 16:25:13 > > rtc_date : 2012-05-22 > > alrm_time : 16:22:20 > > alrm_date : 2012-05-22 > > alarm_IRQ : yes > > alrm_pending : yes > > 24hr : yes > > > > And see if it has any effect. > > > > Kind regards, > > Ed > > > > _______________________________________________ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community
Unfortunately, modes no and disable aren't recognized. After the device woke itself up again two days ago, I just took out the battery last night and synchronized time using ntpdate-debian without setting hardware clock. The cat command shows the date is 01.01.2000 and "alrm time" and "alrm date" at 23:59:59 and 01.01.2000 respectively. Also, alarm IRQ is yes and "alrm pending" is no. How can no alarm be pending while there is an alarm time? _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
