[expert] Gigabyte GA-7ZX-1 Bad System Clock (was Re: [newbie] gigabyte GA-7ZXH)

2001-10-26 Thread Sevatio

Jose,

I rebooted my GA-7ZX-1 to Windoze98 and have had it there for more than a 
day.  The time remained accurate to the second.  As far as I know, Windoze98 
uses only the hardware clock for its timekeeping.

OTOH, LM8.0  LM8.1 uses a combination of the PC's hardware clock  its 
system clock.  The system clock's time can drift away from the hardware 
clock's time by over an hour per day.  The problem is further exacerbated 
when the shutdown process instructs the hardware clock to set its time to the 
screwed-up systemclock.

Normally adjtimex can be used to adjust the drift rate of the system clock, 
LM8.0  LM8.1's drift rate fluctuates wildly rendering adjtimex useless.

Since Wind98 and LM7.2 (pre 2.4 era) did not have this problem, I must say 
that this timer issue is not OS independent and is related to LM8.0  LM8.1 
and perhaps any distro out there that uses the 2.4 kernel.

I hope that they resolve this sometime in the near future.  In the meantime, 
I'll abstain from purchasing suspect hardware.


Sevatio



On Wednesday 24 October 2001 10:25am, you wrote:
 The timer issue is OS independent, and is not related to Linux.

 7.2 did not have the routines which attempted to fix the problem AFAIK,
 whereas 8.x does.

 -JMS



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] Gigabyte GA-7ZX-1 Bad System Clock (was Re: [newbie]gigabyte GA-7ZXH)

2001-10-26 Thread Bill Kenworthy

Or use ntp!

BillK

On Sat, 2001-10-27 at 04:47, Sevatio wrote:
 Jose,
 
 I rebooted my GA-7ZX-1 to Windoze98 and have had it there for more than a 
 day.  The time remained accurate to the second.  As far as I know, Windoze98 
 uses only the hardware clock for its timekeeping.
 
 OTOH, LM8.0  LM8.1 uses a combination of the PC's hardware clock  its 
 system clock.  The system clock's time can drift away from the hardware 
 clock's time by over an hour per day.  The problem is further exacerbated 
 when the shutdown process instructs the hardware clock to set its time to the 
 screwed-up systemclock.
 
 Normally adjtimex can be used to adjust the drift rate of the system clock, 
 LM8.0  LM8.1's drift rate fluctuates wildly rendering adjtimex useless.
 
 Since Wind98 and LM7.2 (pre 2.4 era) did not have this problem, I must say 
 that this timer issue is not OS independent and is related to LM8.0  LM8.1 
 and perhaps any distro out there that uses the 2.4 kernel.
 
 I hope that they resolve this sometime in the near future.  In the meantime, 
 I'll abstain from purchasing suspect hardware.
 
 
 Sevatio
 
 
 
 On Wednesday 24 October 2001 10:25am, you wrote:
  The timer issue is OS independent, and is not related to Linux.
 
  7.2 did not have the routines which attempted to fix the problem AFAIK,
  whereas 8.x does.
 
  -JMS
 
 
 

 Want to buy your Pack or Services from MandrakeSoft? 
 Go to http://www.mandrakestore.com





Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com