Re: NTP / RTC problem driving me absolutely INSANE! - cause of problem found
Sorry to Rick and the other members of the mailing list. The problem is nothing to with Debian. Debian is setting and adjusting the clock fine. OSX is what's causing the problem. Here's how I ascertained this if anyone's interested:
1. In Debian type: hwclock --systohc so system and hwclock were synced.
2. Rebooted from Debian -> Debian and then powered off from Debian and booted Debian. The system and hwclocks were still in sync on both occassions.
3. Booted into OSX (10.4.8). The problem arose again.
Obviously OSX is messing about somewhere and support for OSX problems is also obviously not to be expected on this mailing list. I suppose it's another example of proprietary = bad, free / oss = good. As if I needed reminding. Well at least OSX is not as bad Windows. I'm probably going to blitz OSX anyway as I only use it for DVDs and flash websites, and I should be getting an X86-64 desktop soon (running Debian of course) which will be able to provide me with the functionality that the iBook lacks on Linux. This iBook was only meant to be for doing work and basic tasks on the go, that was until my previous desktop blew up. Oh well.......
thanks,
Ananda
On Sat, 10 Feb 2007 08:23:00 +0000
Ananda Samaddar <a.k.samaddar@googlemail.com> wrote:
> I've just found this website where a guy has a similar problem to me using an almost identical notebook (he has an iBook2 600 MHz, mine is 700 MHz).
>
> http://gecius.de/linux/IBook2.html
>
> I don't know if this sheds any light on a possible solutuion. I may try e-mailing the author if his e-mail address is still valid.
>
> regards,
>
> Ananda
>
>
> On Sat, 10 Feb 2007 08:02:57 +0000
> Ananda Samaddar <a.k.samaddar@googlemail.com> wrote:
>
> > Thanks for the help this is what the command you suggested gave:
> >
> > Sat Feb 10 07:50:29 UTC 2007
> > time in rtc is Sat Feb 10 08:50:30 2007
> > Sat Feb 10 08:50:30 2007
> >
> > So I'm guessing that it's down to Debian making a mess of things and not OSX. OSX must read the RTC see that it's an hour too fast and correct it. To be honest I really don't know where to go from here and do require a bit of hand holding. To think I used Debian for 5 and Ubuntu for 2 years on X86! So the RTC is one hour two fast according to the command output. Why doesn't Debian adjust the value of the RTC? I'm sorry but I'm a bit baffled and need a hand. Tzconfig tells me I'm set to Europe/London which is right. Why doesn't Debian just set up time by checking the RTC at boot up. It's obviously not changinging the RTC on reboot / shutdown because if I was to boot into OSX now with the RTC one hour two fast OSX would recognise it. I've just checked and all the scripts for hwclock are symlinked correctly too. I also have rtc support in the kernel, which is custom compiled. But the kernel does say that if fails to access rtc0.
> >
> > Sorry this has been a bit of a rambling message that I hope makes some sense. Any further advice much appreciated.
> >
> > regards,
> >
> > Ananda
> >
> >
> > On Sat, 10 Feb 2007 02:39:20 -0500
> > Rick Thomas <rbthomas55@pobox.com> wrote:
> >
> > > It sounds like a timezone problem. It could be one or both of two
> > > things:
> > >
> > > 1) Your hardware CMOS clock is set to something other than UTC or
> > > local time. For Linux, it must be one or the other -- UTC is
> > > preferable.
> > >
> > > In Linux as super-user, at the bash prompt type "(export TZ=UTC ;
> > > date ; clock)" (without the quotes, but with the parens).
> > > The three times it prints should be identical and equal to the
> > > present time in UTC. If, as seems likely, you're in GB and "Summer
> > > Time" is not in effect, then it should also be the same as your local
> > > time.
> > >
> > > 2) Either MacOS or Linux has the wrong timezone. My guess (assuming
> > > you're in GB) is that one or the other is set to BST, even though it
> > > is manifestly *not* summer in the Northern Hemisphere right now.
> > >
> > > Hope that helps!
> > >
> > >
> > > Rick
> > >
> > >
> > >
> > > On Feb 9, 2007, at 7:56 PM, Ananda Samaddar wrote:
> > >
> > > > Hello everyone,
> > > >
> > > > by now you're probably mostly familiar with the trials and
> > > > tribulations I faced moving to a new architecture but there is one
> > > > thing that is really annoying me!
> > > >
> > > > I have NTPD running synced to four servers here in the UK and one
> > > > in France which works fine. The correct time is shown and
> > > > everything's ok. The problem is when I boot to OSX it always shows
> > > > the time as being one hour behind and corrects it. Fair enough.
> > > > If I then reboot into Debian it shows the time to be one hour
> > > > ahead. You'd think that NTP would just correct the time
> > > > accordingly. It does but if I'm logged into GNOME which I use as
> > > > the desktop it blanks the screen and no matter what I try I cannot
> > > > get back to GNOME or a console terminal. If I reboot after OSX and
> > > > log into a terminal while I'm using the terminal GDM informs me
> > > > that the greeter (the default Etch one) is crashing and changes it
> > > > to the old school one from Potato! The only solution is a hard reset.
> > >
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-powerpc-REQUEST@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> >
>
>
> --
> To UNSUBSCRIBE, email to debian-powerpc-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: