I were warned but ... now really need your advice

Vu Pham vu
Tue May 29 08:50:19 PDT 2007


On Tue, 2007-05-29 at 10:35 -0500, Net Llama! wrote:
> On Tue, 29 May 2007, Vu Pham wrote:
> > On Tue, 2007-05-29 at 09:58 -0500, Net Llama! wrote:
> >> On Tue, 29 May 2007, Vu Pham wrote:
> >>> On Mon, 2007-05-28 at 20:45 -0500, Net Llama! wrote:
> >>>> Maybe the CMOS battery died?  How old is this mobo?
> >>>>
> >>>
> >>> One is 9-month old, the other is 3-day old :)
> >>>
> >>> I also did the following tests:
> >>> - set the motherboard time correctly and turn it off.
> >>> - several hours later turn it on and check the time. It is correct.
> >>> - without turning off the power, just let it boot to the hard drive, now
> >>> it shows the incorrect time, both the OS and the motherboard.
> >>>
> >>> I think some process(es) on the motherboard change the system time.
> >>
> >> Perhaps it has the wrong timezone set?
> >
> > I checked that already. It shows CDT in both the "date" command line as
> > well as in the Yast interface.
> >
> > The strange thing is it changes the minutes also. Like from 7:30PM to
> > 4:16AM.
> 
> And this box was working fine up until recently?

The 9-month old board has worked fine recently. I just found the time
problem about two days ago and I thought its battery is dead. Then I got
the new board and just want to compare the performance of the two boards
and found even the new one has the time problem.

Vu






More information about the Linux-users mailing list