[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: clock troubles under Debian/PowerPC

> Renaud,
> I had that problem, too.  (*Exactly* that problem.)  It turned out
> that my housemate had written a script (in /etc/rc.boot) to set
> the clock properly back when we first installed the system (when
> hwclock was completely broken on the PowerPC), and that script was
> no longer working properly.  I disabled the script and things got
> better.  (I have some vague memory of having to create new links
> to /etc/init.d/hwclock.sh in some of the /etc/rc*.d directories,
> but I may be thinking of something else.)
> I did notice an eight hour clock skew the last time I spent any
> significant time in MacOS before coming back to Linux
> (``coincidentally'', I'm in the Pacific Time Zone, eight hours
> behind GMT).  I can't recall now if I made a permanent fix to that
> problem or if I decided to wait until the next time I do some work
> in MacOS and come back to Linux to find a major clock skew.  ;-)

I think I'm starting to understand what is going on. I've set Debian
to consider the hardware clock to be local time, since I'm
dual-booting with Mac OS too. When booting, /etc/rcS.d/S20modutils
runs *before* /etc/rcS.d/S50hwclock.sh and therefore before the clock
is set properly. My guess is that then the system is confused because
time has suddenly gone back in the past (because it thinks local time,
which is also 8 hours before UTC is my case, is UTC time), and so it
decides we're on December 31st, 1969 and assigns that time to
/lib/modules/2.2.14/modules.dep when that file is generated, making
/etc/modules.conf "more recent". I'm not sure why it doesn't just
assign it a time 8 hours in the past, *that* might be Y2K or PowerPC

I think I have a fix: I moved S50hwclock.sh to S20hwclock.sh to make
sure it runs *before* S20modutils. Hopefully this won't break

As for your 8 hours drift, it might be because you set up Debian to think
the hardware clock was UTC, not local time. What does /etc/default/rcS
say? If you're going to double-boot with Mac OS, you need to tell
Debian the hardware clock is set to local time. Unless that is, one
knows of a way to make Mac OS think of the hardware clock as UTC...



Reply to: