On Thu, 2011-01-27 at 15:30 +1100, James Cameron wrote:
> On Wed, Jan 26, 2011 at 06:09:02PM -0600, Jerry Vonau wrote:
> > That actually makes things worse, try installing ntpdate and run it with
> > the stock /etc/adjtime file, now the real time clock is set to localtime
> > as that is the first t
On Thu, 2011-01-27 at 09:01 -0500, Martin Langhoff wrote:
> Very interesting. Strange. Unexpected.
>
> On Wed, Jan 26, 2011 at 11:30 PM, James Cameron wrote:
> > Until these problems are fixed, please change your build;
>
> Could this be added to http://wiki.laptop.org/go/OS_Builder#Recipes ?
I
Very interesting. Strange. Unexpected.
On Wed, Jan 26, 2011 at 11:30 PM, James Cameron wrote:
> Until these problems are fixed, please change your build;
Could this be added to http://wiki.laptop.org/go/OS_Builder#Recipes ?
cheers,
m
--
martin.langh...@gmail.com
mar...@laptop.org -- Softw
On Thu, 2011-01-27 at 15:30 +1100, James Cameron wrote:
> On Wed, Jan 26, 2011 at 06:09:02PM -0600, Jerry Vonau wrote:
> > That actually makes things worse, try installing ntpdate and run it with
> > the stock /etc/adjtime file, now the real time clock is set to localtime
> > as that is the first t
On Wed, Jan 26, 2011 at 06:09:02PM -0600, Jerry Vonau wrote:
> That actually makes things worse, try installing ntpdate and run it with
> the stock /etc/adjtime file, now the real time clock is set to localtime
> as that is the first time hwclock is run.
>
> http://osdir.com/ml/fedora-olpc-list/20
On Thu, 2011-01-20 at 14:40 -0500, Martin Langhoff wrote:
> On Thu, Jan 20, 2011 at 8:02 AM, Sridhar Dhanapalan
> wrote:
> > We've actually disabled the /sbin/hwclock --systohc in our latest
> > build (probably to be released tomorrow).
>
> If you are spinning your own build, ensure ntpdate is in
On Thu, Jan 20, 2011 at 8:02 AM, Sridhar Dhanapalan
wrote:
> We've actually disabled the /sbin/hwclock --systohc in our latest
> build (probably to be released tomorrow).
If you are spinning your own build, ensure ntpdate is installed. That
should help significantly.
cheers,
m
--
martin.lan
On Thu, 2011-01-20 at 02:15 -0800, Hal Murray wrote:
> > What is the accuracy of the hwclock on XOs? Can we assume that it will keep
> > good time over an XO's five-year lifespan?
>
> The ballpark for the hardware is 1 second per day.
>
> > We have some XO-1.5s that have their hwclocks off by 10-
On 20 January 2011 21:15, Hal Murray wrote:
>
>> What is the accuracy of the hwclock on XOs? Can we assume that it will keep
>> good time over an XO's five-year lifespan?
>
> The ballpark for the hardware is 1 second per day.
>
>> We have some XO-1.5s that have their hwclocks off by 10-20 minutes.
> What is the accuracy of the hwclock on XOs? Can we assume that it will keep
> good time over an XO's five-year lifespan?
The ballpark for the hardware is 1 second per day.
> We have some XO-1.5s that have their hwclocks off by 10-20 minutes. Would
> this likely be due to a fault at the factory
On Thu, Jan 20, 2011 at 06:36:14PM +1100, Sridhar Dhanapalan wrote:
> What is the accuracy of the hwclock on XOs?
By accuracy I presume you mean stability over time, or the amount of
error between the clock and actual time. If you mean something else,
ignore the following explanation.
The XO-1.5
What is the accuracy of the hwclock on XOs? Can we assume that it will
keep good time over an XO's five-year lifespan?
We have some XO-1.5s that have their hwclocks off by 10-20 minutes.
Would this likely be due to a fault at the factory (e.g. not setting
the time before shipping them), or did the
12 matches
Mail list logo
