Mailinglist Archive: opensuse (2324 mails)
| < Previous | Next > |
Re: [opensuse] Time & Date
- From: Anton Aylward <anton.aylward@xxxxxxxxxx>
- Date: Fri, 06 Nov 2009 12:51:27 -0500
- Message-id: <4AF4621F.406@xxxxxxxxxx>
Istvan Gabor said the following on 11/06/2009 12:13 PM:
That was my first thought.
However the statement of the problem hasn't said anything about the
motherboard clock. Yes, if it has failed, be it a hardware failure or a
dead battery, that would require resetting the Linux time on every boot.
How to check?
I'd say go into the BIOS on hardware boot. Most BIOS's let yo adjust
the clock there. It it keeps resetting to the same value (chip
dependent 'all zeros' then I'd replace the battery.
Of course it _could_ be a hardware failure.
How old did you say this was?
--
If you keep your mind sufficiently open, people will throw a lot of
rubbish into it. ---William Orton
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
I don't know about laptops but on desktops this can occur if the battery on
the motherboard has run out.
That was my first thought.
However the statement of the problem hasn't said anything about the
motherboard clock. Yes, if it has failed, be it a hardware failure or a
dead battery, that would require resetting the Linux time on every boot.
How to check?
I'd say go into the BIOS on hardware boot. Most BIOS's let yo adjust
the clock there. It it keeps resetting to the same value (chip
dependent 'all zeros' then I'd replace the battery.
Of course it _could_ be a hardware failure.
How old did you say this was?
--
If you keep your mind sufficiently open, people will throw a lot of
rubbish into it. ---William Orton
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |