From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from <gentoo-user+bounces-134624-garchives=archives.gentoo.org@lists.gentoo.org>) id 1RuTin-00079c-Ld for garchives@archives.gentoo.org; Mon, 06 Feb 2012 18:55:25 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5A0D2E07DB; Mon, 6 Feb 2012 18:54:57 +0000 (UTC) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by pigeon.gentoo.org (Postfix) with ESMTP id 9B309E0843 for <gentoo-user@lists.gentoo.org>; Mon, 6 Feb 2012 18:52:33 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 5598320D46 for <gentoo-user@lists.gentoo.org>; Mon, 6 Feb 2012 13:52:33 -0500 (EST) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute6.internal (MEProxy); Mon, 06 Feb 2012 13:52:33 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=binarywings.net; h=message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type; s=mesmtp; bh=CwBZKnYECRL9SQnc3Gcf4o7K HWU=; b=TK5SrWV0KCZ5bwMjNL8oIN7OM3IdGzVczPjISd0i1wdGCDTutlyaHciZ fDyQTujeQ6socVy32dVIEoR+QZTFlOHsnv6uRaahqWqH4B2e1Dk3yFnTjcqTQar8 tG2ECTZSTvwnwUA5vj+atALY5abqRiFuie0n+Hlm3Oxw2sktxGM= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type; s=smtpout; bh=CwBZ KnYECRL9SQnc3Gcf4o7KHWU=; b=SwqxGkoCMNoONj0pJWF1d7gK6AWzAQtTStXq ZuQJO3EEC0N9olQghYmhLBK0xICQCKnIy7CjmaFEM9vJ/VOuFfFhT95JywzLTikZ uNohJ/33hyUTLUoFH5ibHuhw+Wmz4+7qHSAPmeQ67BDZHOoQaCVe8D4uHIBul+c6 azw0ASg= X-Sasl-enc: w8V4xFwIzxbq0wIb+IFkmStvcov+KMEwDW7KfZXfI3yt 1328554352 Received: from [192.168.5.18] (serv.binarywings.net [83.169.5.6]) by mail.messagingengine.com (Postfix) with ESMTPSA id A1FBC8E0153 for <gentoo-user@lists.gentoo.org>; Mon, 6 Feb 2012 13:52:32 -0500 (EST) Message-ID: <4F302166.1080905@binarywings.net> Date: Mon, 06 Feb 2012 19:52:22 +0100 From: Florian Philipp <lists@binarywings.net> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20120114 Thunderbird/9.0 Precedence: bulk List-Post: <mailto:gentoo-user@lists.gentoo.org> List-Help: <mailto:gentoo-user+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-user.gentoo.org> X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] hwclock <--> sysclock and the ntp-client References: <20120206175130.GA3145@solfire> <CA+czFiCsc+8WxWMUoTVCe=MMuqPsJzCPUBCh36XkaFsMy3cvsQ@mail.gmail.com> <20120206183916.GB3145@solfire> In-Reply-To: <20120206183916.GB3145@solfire> X-Enigmail-Version: 1.3.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFA2B55EEE2EA9E979EEA1A1B" X-Archives-Salt: 5d50bc0a-c84d-47f0-b2c2-b90b41ccf82f X-Archives-Hash: c5c25f87439ef4cf943ae980442166fd This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFA2B55EEE2EA9E979EEA1A1B Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Am 06.02.2012 19:39, schrieb meino.cramer@gmx.de: > Michael Mol <mikemol@gmail.com> [12-02-06 19:20]: >> On Mon, Feb 6, 2012 at 12:51 PM, <meino.cramer@gmx.de> wrote: >>> Hi, >>> >>> to get the correct system time I use ntp-client in the boot process. >>> Furthermore in /etc/conf.d/hwclock I set: >>> >>> # Set CLOCK to "UTC" if your Hardware Clock is set to UTC (also kn= own as >>> # Greenwich Mean Time). If that clock is set to the local time, t= hen >>> # set CLOCK to "local". Note that if you dual boot with Windows, = then >>> # you should set it to "local". >>> clock=3D"UTC" >>> >>> # If you want to set the Hardware Clock to the current System Time= >>> # (software clock) during shutdown, then say "YES" here. >>> # You normally don't need to do this if you run a ntp daemon. >>> clock_systohc=3D"YES" >>> >>> # If you want to set the system time to the current hardware clock= >>> # during bootup, then say "YES" here. You do not need this if you = are >>> # running a modern kernel with CONFIG_RTC_HCTOSYS set to y. >>> # Also, be aware that if you set this to "NO", the system time wil= l >>> # never be saved to the hardware clock unless you set >>> # clock_systohc=3D"YES" above. >>> clock_hctosys=3D"NO" >>> >>> # If you wish to pass any other arguments to hwclock during bootup= , >>> # you may do so here. Alpha users may wish to use --arc or --srm h= ere. >>> clock_args=3D"" >>> >>> In the kernel config file I had set: >>> >>> CONFIG_RTC_HCTOSYS=3Dy >>> CONFIG_RTC_HCTOSYS_DEVICE=3D"rtc0" >>> >>> I would exspect that after a reboot of the system which system time i= s >>> correctly set via ntp-client that the hwclock and system time only >>> differ in a small amount of time. >>> >>> But: >>> solfire:/home/mccramer>hwclock >>> Mon Feb 6 19:05:11 2012 -0.172569 seconds >>> solfire:/home/mccramer>date >>> Mon Feb 6 18:49:37 CET 2012 >>> solfire:/home/mccramer> >> >> I don't know the CET tz, but I can see that the minutes don't match >> up. I assume you rand the two commands within seconds of each other. >> Is this true immediately after bootup, or does it take a while to get >> that far off? It could be that your hardware clock is drifting, and >> the system won't reset it until it goes to shutdown. >> >> --=20 >> :wq >> >=20 > Hi Michael, > thank you for your reply. > I set the configuration as mentioned above and booted twice with about > five minutes wait. > The commands were executed within seconds, yes. > All hardware clocks drifts, but this is not the problem. > The problem is that the hardware clock is not set to the system time > in contradiction to what I think the comments in the config are=20 > saying. >=20 > How can I fix that? >=20 > Thank you very much in advance for any help! > Best regards, > mcc >=20 >=20 >=20 Is your RTC driver compiled into the kernel? The "httosys" function of the kernel takes place before any modules can be loaded and will fail if your CMOS clock driver is a module. Activating clock_hctosys in /etc/conf.d/hwclock should solve this as it takes place later in the boot process. Regards, Florian Philipp --------------enigFA2B55EEE2EA9E979EEA1A1B 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.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8wIWsACgkQqs4uOUlOuU9gfwCfdWEJcIuehdPAP2CiLCRHiC0l z3IAnjqjoOAj/z86y4L2ZjK8cKlC6eJK =GZ12 -----END PGP SIGNATURE----- --------------enigFA2B55EEE2EA9E979EEA1A1B--