Date: Sat, 11 Oct 2008 08:49:16 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Richard Smith <geseeker@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: dmesg: Invalid time in clock: check and reset the date Message-ID: <48F05A7C.7030404@infracaninophile.co.uk> In-Reply-To: <111038.12337.qm@web45011.mail.sp1.yahoo.com> References: <111038.12337.qm@web45011.mail.sp1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6CB20C5D69B775E8E7E6D1F7
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Richard Smith wrote:
> Hi, I've just installed FreeBSD 7.0 Release along with Windows XP on my=
PC. I found that when I set the clock to the correct time&date, next tim=
e I boot into FreeBSD it changes and reports the wrong time&date. Both BI=
OS and Windows reports the time correctly.
>=20
> dmesg shows the following message:
> Invalid time in clock: check and reset the date!
>=20
> Can't figure out what's wrong... any help will be appreciated.
Is the time out by an exact number of hours?[*] Does the offset
correspond to your localities' timezone offset from UTC?
If so, then what is happening is this: Windows will only deal with
one timezone at a time, and it expects the system clock (and
consequently the CMOS clock on the motherboard) to be set to the
local wall-clock time.
Unix in comparison allows each process to be run in an arbitrary
timezone, simply by setting the TZ environment variable. It
expects the system clock and the CMOS clock to be set to UTC, and
it calculates the local offset as required.
When you reboot the machine, the internal system clock is set from
the cmos clock, so one or the other OS will end up thinking local
wall-clock time is UTC or vice-versa. Unless you have the happy=20
fortune to be living in this Sceptered Isle (but only during the winterti=
me), or in certain parts of West Africa that's going to
cause problems.
If you need to dual-boot, FreeBSD provides a mechanism for allowing
the CMOS clock to be set to wallclock time. You can toggle the
setting using /usr/sbin/tzsetup -- if there is a zero length file /etc/wa=
ll_cmos_clock then your system is running in compatability
mode. Note: this file should not appear on a box that is dedicated
to running FreeBSD[+] -- the tzsetup default is the /wrong/ choice
in this case.
Cheers,
Matthew
[*] Assuming you don't live in Newfoundland or one of the other odd
places with timezones that have a 30 minute offset.
[+] or that only dual boots to *BSD or Linux or MacOS X or Solaris
etc.
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
--------------enig6CB20C5D69B775E8E7E6D1F7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkjwWoMACgkQ8Mjk52CukIyIVACeJxpNhutab5xgHvtTCIy63/Y3
iXsAn1sQseMxLryflMXTg0DqnC1h7ap3
=cTR1
-----END PGP SIGNATURE-----
--------------enig6CB20C5D69B775E8E7E6D1F7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48F05A7C.7030404>