Hi, Gilles Filippini a écrit , Le 16/12/2009 23:16: > A few days ago I started to play both with Qi, the frameworkd config, > and using gpsd instead of fso-gpsd. I can't remember when I noticed it > first, but the date isn't persistent anymore on my FR: > * it is set at 01/01/1970 01:00 at boot time > * it is stalled on suspend > > I'm now back with my old configuration (u-boot + frameworkd.conf) and > the problem is still there.
This evening I took some time to dig around this bug, and found out the problem was that /sbin/hwclock failed to read/set the hardware clock: debian-gta02:~# LANG=C hwclock -D -r hwclock from util-linux-ng 2.16.2 Using /dev interface to clock. Last drift adjustment done at 1260715062 seconds after 1969 Last calibration done at 1260715062 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick RTC_RD_TIME: Invalid argument ioctl() to /dev/rtc0 to read the time failed. Then, searching the friendly web with "RTC_RD_TIME: Invalid argument" led me to this page[1] from which I tried successfully the command: # hwclock --systohc -D --noadjfile --utc And I've got my hardware clock back \o/ Still I don't understand what could have set it in an undetermined state :/ Thanks, _Gilles.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
