[QUOTE=Suwat;576883]Did you check "syslog" under "/var/log"? QUOTE]
@Suwat
Thanks for being willing to make some suggestions.
rogue_ronin is right about there being two clocks in Linux: the RTC/Hardware Clock and the System Clock/Software Clock. See the discussion here under 2.1 Basic Strategies (
http://www.linux.org/docs/ldp/howto/Clock-2.html#ss2.1).
My Q5 hardware clock (RTC) is way off and won't reset.
My script for "now" appears to reset the software clock, not the hardware clock.
At your suggestion, I checked the "syslog" file in "/var/log" and found this line:
Jan 2 19:40:04 mojo kernel: s3c2410-rtc s3c2410-rtc: setting system clock to 2040-02-08 08:08:00 UTC (2212301280)
However, the Q5 doesn't reset the date/time to 2040-02-08 08:08:00.
It stays at Jan 2 19:40:04 as evidenced by the remaining lines in the syslog file and the clock on the desktop after the boot process is complete.
The hardware clock always shows this date and time after a reboot/shutdown.
It's almost as if when the Q5 is turned off, the RTC is not getting any power and defaults to this basic date/time.
Other possible explanations include a bad kernel, bios, or hardware clock.
When the Q5 is put into suspend mode (not plugged in) and and then woken up, the clock shows the time when it was suspended, not the current time.
This makes me wonder whether the hardware clock itself is bad.
The Q7 acts normally--it shows the correct time when rebooted and updates it when it comes back from hibernation.
I'd like to see what happens when the Q5 hardware clock is reset to the correct system date/time and the system rebooted.
I found out how to change the RTC to the system clock settings but it doesn't work on the Q5 and I get a weird message.
The command and argument is "sudo hwclock --systohc" and it's followed by this message, "Timed out waiting for time change".
This is consistent with a diagnosis of a bad hardware clock and not a kernel or bios issue.
Issuing the same command and argument on the Q7 executes it without the "Timed out" message.
Any further help you can provide would be appreciated.
Otherwise, I think I'm going to work on my "now" script to automatically update itself (say hourly) and just assume I'll never be able to reset the hardware clock. Of course, I could return the Q5 to eletroworld for a warranty repair/replacement but shipping is costly.