Quote:
Originally Posted by Suwat
I believed I found what's wrong with the clock. It's a script called "94cpufreq" inside this directory, '/usr/lib/pm-utils/sleep.d". When q7 goes into suspension, the pm-suspend command script will call this routine and it changes the frequency of the cpu hence the clock speed. The rtc will keep the correct value until q7 goes into suspension again. Then a script "90clock" in the same dir will update the realtime clock (rtc).
I don't know about python script and how the system clock utilizes the cpu frequency. So, this is the most I can do. Anyone with the knowledge should take a look at the script to verify and find way to correct the clock. Please.
|
I wish I could help but I'm just a Linux newbie.
The same script appears in the same place on the Q5.
The Q5 does an even worse job of keeping time.
After a reboot/shutdown, it always reports a date of January 2, 1904 under the latest firmware.
I can reset the date and time with Sync but it's still irritating.
Any suggestions for this Q5 clock issue?