Clock Not right time.

[Malachai]

Hello all,

I was wondering if someone could help me out. Every time I log out of FC6 and don't turn it on for a few days.. My time does not update. Like right now it said 5:39, but it was 1:39. Can someone tell me how to fix this problem. I did the adjust time a few time, but is there other way of keeping the right time?

Malachai.

[bob]

When in 'system-config-date', set it to the right time, then exit, go back and 'Network Time Protocol'. Grab one of those. It will sync during boot which adds a second or two.

[Malachai]

Thank you very much for you help. i will try it out

[Dan]

In FC 6, my system clock gains several hours over one day.

So, I let the NTP handle it most of the time now, but when I go off-line, the first thing I do when I log back on the web, is run the time updater.

Dan

[marko]

Originally Posted by Malachai

Hello all,

I was wondering if someone could help me out. Every time I log out of FC6 and don't turn it on for a few days.. My time does not update. Like right now it said 5:39, but it was 1:39. Can someone tell me how to fix this problem. I did the adjust time a few time, but is there other way of keeping the right time?

Malachai.

Note how your time is exactly 4 hours "off"? The problem likely isnt' the clock,
it's that the time zone offset is wrong. You need to set the time zone. If you're
running KDE, put the mouse over the clock in the lower right, does it show
the correct timezone for you? I'm in the Eastern Time zone, so when I do that I see
as an example:

Eastern 5:11pm
New York

You can set the time zone in KDE's menu with Administration-> Date & Time via
the "Time Zone" tab (the toggle "System Clock uses UTC" is also important)

PS about NTP, it will not update your time beyond a certain error threshold, if your
clock is hours off, ntp will refuse to set it. Manually get your clock in the
ballpark with "date" as root user, then ntp will keep it set ok.

Mark

[Seve]

Hello:
The clock is always correct .... what's wrong is where you are located

Seve

[jcliburn]

Originally Posted by TangledWeb

In FC 6, my system clock gains several hours over one day.

So, I let the NTP handle it most of the time now, but when I go off-line, the first thing I do when I log back on the web, is run the time updater.

Dan

Dan, is this clock problem by chance on an Intel chipset? Does time ever seem to run backwards on this machine? Does the machine ever hang? I had similar problems and it turned out to be a hardware issue that you can workaround by booting with the noapic option.

Here's a little program that tests whether your system is afflicted by the pm timer bug. I can't remember where I found it, so I can't provide proper attribution.

Run "grep PM_TMR /proc/ioports" to get the ioport number (it's the first number of the two), then run this little program (that I call timercheck), substituting your PM_TMR ioport where I've shown 0x1008.

sudo ./timercheck 0x1008

#include <stdio.h>
#include <stdlib.h>
#include <errno.h>
#include <error.h>
#include <sys/io.h>

typedef unsigned int    u32;
static unsigned short pmtmr_ioport;
static int cnt;

#define ACPI_PM_MASK 0xFFFFFF /* limit it to 24 bits */

static u32 read_pmtmr(void)
{
        u32 v1=0,v2=0,v3=0;
        /* It has been reported that because of various broken
         * chipsets (ICH4, PIIX4 and PIIX4E) where the ACPI PM time
         * source is not latched, so you must read it multiple
         * times to insure a safe value is read.
         */
        cnt = 0;
        do {
                v1 = inl(pmtmr_ioport);
                v2 = inl(pmtmr_ioport);
                v3 = inl(pmtmr_ioport);
                cnt++;
        } while ((v1 > v2 && v1 < v3) || (v2 > v3 && v2 < v1)
                        || (v3 > v1 && v3 < v2));

        /* mask the output to 24 bits */
        return v2 & ACPI_PM_MASK;
}

int main(int argc, char *argv[])
{
        int i;

        if (argc < 2)
                error(1, 0, "Usage: %s pmtmr_port\n", argv[0]);

        pmtmr_ioport = strtoul(argv[1], NULL, 0);
        if ((pmtmr_ioport & 0xff) != 0x08)
                error(1, 0, "Invalid port address: 0x%x\n", pmtmr_ioport);

        if (iopl(3) < 0)
                error(1, errno, "iopl");

        for (i = 0; i < 10000000; i++) {
                read_pmtmr();
                if (cnt > 1)
                        error(1, 0, "Detect PM-Timer Bug\n");
                if ((i % 100000) == 0)
                        printf("%d\n", i);
        }
        return 0;
}

[Dan]

Hi JC

Nope. It's an AMD Athlon XP 3000+ on an MSI nVIDIA chipset.

However, I've got some suspicions about the motherboard. I've had to throttle the chip down to 1700 to keep it stable. It's a replacement board from the factory. (after a warrantied failure) I've bought a new one, just haven't installed it yet.

I'll blow that past it though. Thanks!

Dan