Quote:
Originally Posted by dir194
thx for the tip 
just have a go:
Code:
[root@[192_168_15_244] root]# hwclock -systohc
hwclock: invalid option -- 'y'
BusyBox v1.17.1 (2011-11-03 11:08:48 PDT) multi-call binary.
Usage: hwclock [-r] [-s] [-w] [-l] [-u] [-f FILE]
Query and set hardware clock (RTC)
Options:
-r Show hardware clock time
-s Set system time from hardware clock
-w Set hardware clock to system time
-u Hardware clock is in UTC
-l Hardware clock is in local time
-f FILE Use specified device (e.g. /dev/rtc2)
[root@[192_168_15_244] root]# date -s 2012.05.05-2:01
Sat May 5 02:01:00 UTC 2012
[root@[192_168_15_244] root]# hwclock -w
[root@[192_168_15_244] root]# date
Sat May 5 02:01:11 UTC 2012
[root@[192_168_15_244] root]#
Not sure if I'm doing right,still not working. |
My bad - I wasn't referencing the busybox version of hwclock,
but I see you figured out my mistake.
Now the hardware clock (whatever that is in a Kindle SoC) should keep the time between restarts.
May not fix the event recognition but at least fsck should no longer complain about the file system being out of date.
I was working off the observation that the problem only developed after hours or even days of use.
(Clock drift or other clock problems came first to mind.)
Hmm...
What else can change over "normal" operation of hours or days?
Some part of the filesystem "filling up"?
Check the filesystem usage with:
df
You may want to cut&paste the result, some areas will probably report 100% as their "normal" use, making the problem area hard to spot.