Mailinglist Archive: opensuse (4634 mails)

[John Andersen <jsa@xxxxxxxxxxxxxx>]

On Sunday 17 December 2006 03:42, Mark Hounschell wrote:
> Mark Hounschell wrote:
> > Darryl Gregorash wrote:
> >> On 2006-12-17 04:48, Mark Hounschell wrote:
> >>> A dmesg output from the OP might shed some light.
> >>
> >> That won't help at all, since nothing related to the clocks is logged to
> >> the system log (the default xntp configuration is logging to
> >> /var/log/ntp).
> >>
> >> The only clues available are from reading the kernel time variables
> >> directly (adjtimex, or ntpdc if ntpd is running), and from comparing the
> >> hardware of systems that are having the problem.
> >
> > dmesg | grep clock
> > Time: acpi_pm clocksource has been installed.
> >
> > All the clock source stuff is in kernel not ntp
> >
> > Duh...
>
> Remember the original problem IS NOT an NTP problem. The guys clock runs
> to fast.

No it doesn't run too fast.

Byte specifically stated his clock was just find on prior releases
and in other OSs.  Its only the latest version of Suse that
is giving him fits.

-- 
_____________________________________
John Andersen