On Wed, 05 Jun 2013 19:51:37 +0200 [email protected] (Michał Masłowski) wrote:
> I know two reasons for hardware time being inaccurate: > - bad battery > - NTP running and system time not being synced to the realtime clock > > Run "hwclock --systohc" as root to fix the second issue. I ran "sudo hwclock -systohc", and didn't notice any immediate change. I then restarted the computer, and the date and time were completely accurate. (Both in BIOS and in Trisquel). However, this does not necessarily mean the issue has been solved, as this usually happens. I'll have to see if the date and time remains accurate after an extended shutdown, which will probably take a few days. > /proc/driver/rtc has a batt_status line that might show if the first > issue occurs. I checked the /proc/driver/rtc file, and saw this: "batt_status : okay" So I'm pretty sure it's not a bad battery, although it certainly could be. > I think BIOSes have no UTC time setting, the time specified is in UTC > and operating systems have settings for UTC or local time. UTC is > probably default here, Windows (at least old versions) used local time. Okay, wasn't sure of that. I should note that this computer originally had a Windows XP installation, but I've since overwritten it with a Trisquel installation. Not sure if XP uses local time or UTC, and if that would have any effect on this problem. > If you use NTP and always have network access, the real time clock isn't > needed. That's what I assumed, but I'm not actually sure if I have NTP set up properly. Any way to make sure in Trisquel Mini? Thanks for your help! -- Michael Mehrazar <[email protected]>
