From: Luca Capello <luca-wlebWZzHoyE@public.gmane.org>
To: ML ACPI-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: 2.6.9 S4: clock not updated after resume
Date: Tue, 26 Oct 2004 22:01:17 +0200 [thread overview]
Message-ID: <417EAD0D.1000200@pca.it> (raw)
In-Reply-To: <417A99B4.40707-wlebWZzHoyE@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
on 10/23/04 19:49, Luca Capello wrote:
> on 10/23/04 17:03, Jon Valvatne wrote:
>> Maybe I'm missing something here, but if the problem is that the
>> kernel doesn't update the system clock from the hardware clock on
>> resume, why bother with NTP? Can't you just do a hwclock --hctosys?
> well, I never did it because I didn't know this command, I'll try
> tomorrow and report :-)
'hwclock --hctosys' indeed did the trick :-)
Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFBfq0MVAp7Xm10JmkRAiYMAJ0YpRiDDvFCWusH29es4Y9QLl7tUwCfTme8
Vm9H2pjZ4Oj9CiBZMPsyRoc=
=Kbni
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
prev parent reply other threads:[~2004-10-26 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 12:21 2.6.9 S4: clock not updated after resume Luca Capello
[not found] ` <4177A9DC.7060503-wlebWZzHoyE@public.gmane.org>
2004-10-21 20:20 ` Pavel Machek
[not found] ` <20041021202051.GA21624-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-22 8:10 ` Luca Capello
2004-10-23 15:03 ` Jon Valvatne
[not found] ` <loom.20041023T170041-953-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2004-10-23 17:49 ` Luca Capello
[not found] ` <417A99B4.40707-wlebWZzHoyE@public.gmane.org>
2004-10-26 20:01 ` Luca Capello [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=417EAD0D.1000200@pca.it \
--to=luca-wlebwzzhoye@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.