Thierry CHARLES <thierry@_no_spam_les-charles.net> wrote:
> The first thing to do is to reboot the machine and go in the BIOS.
> Then set the clock correctly, save and shutdown the machine.
> Wait for couple of minutes (15 - 30 minutes) and turn it on againt.
> Go in the BIOS and check the time.

Hey, I may have no idea how to administer a Linux system, but I do know how to
tell a faulty RTC from an OS getting its own timekeeping wrong...

> If time as gone twice as when running linux, shutdown the machine,
> remove your motherboard and send it back to your resealer.
>
> If not, you'll have to tweak kernel options manually.

That was exactly where I was hoping some Linux Guru who might be experienced
enough to google this problem up in no time flat could go out of his way and
help me: HOW to tweak the damn system, and WHAT to tweak.

I was actually hoping for something more substantial than the usual "RTFM" type
of replies - that someone might be willing to invest maybe 15 minutes to save
me from spending half a day trying to dig up the very same information myself.


Well, I *did* dig it up by myself now, and I'm glad it took me "only" 3 and a
half hours spent on nothing but this single problem...

.... or was it 7 hours? I guess it depends on the frame of reference in this
case...

Anyway, sorry for letting off steam on you. I'm just very, very, *very* upset at
the moment, about how really, really, *really* badly open source stuff tends to
be documented, how many promising internet links lead to nowhere, how
distribution producers leave all the documentation and support to "the
community", and a lot more.

The solution? Just add a bloody "no_timer_check" at the right place in the right
file (actually it's the kernel boot options in the Grub boot loader settings, as
I have learned today). Documentation? Well, seems to be one of those occult
secrets circulated in "the community".

So I don't know what exactly that thing might do, and how it could possibly
wreck my system as a side effect - but at least the clock seems to run properly
now...

Post a reply to this message