My tivo's clock is suddenly an hour slow?

[Tony]

Hi all,

Any reason why my Tivo should suddenly have decided its an hour earlier than it actually is?

Not completely sure when it did this... early Sunday morning I think? Something to do with the daylight saving dates having moved?

I'm running the current 1.5 NZ image, and don't think I've tweaked anything relevant.

Cheers,

Tony

[nicb]

I think... Mine has done the same.

[Grant]

roger that me too, oddly only on one of the two tivos..

[Skolink]

Did you guys update to the latest daylightsavings file?
Get Auckland.zip from here http://forums.oztivo.net/showthread.php?t=1743&highlight=Auckland.zip

[KEG]

Hi all, both my Tivo's are an hour out. I updated the daylight saving time file as suggest and rebooted. Redid guide data and the clock is still 1 hour out. I then used settime to correctly set the time. All OK until I did guide data again. You guessed it, clock out by 1 hour. It appears that the clock that the Tivo syncs to during daily call (guide data) is an hour out.
Can someone confirm this?

Thanks

Keith

[Skolink]

Our TiVo is displaying the correct time.

[petestrash]

The clock that your TiVo calls would not be out at it replies in UTC. The timezone calculation is done in the TiVo and it does not appear to be calculating correctly.

What do you get with these commands?
/bin/ntpdate -b -v 132.163.4.103

ls -l /var/hack/zoneinfo/Pacific/Auckland

Can someone who is ok also try them.

Peter.

[Wibble]

From a working configuration



/bin/ntpdate -b -v 132.163.4.103

[TiVo [p0] ~]# /bin/ntpdate -b -v 132.163.4.103
Our postcode is 02113. Found matching timezone Pacific/Auckland
Offset 46800 for timezone NZDT, daylight saving is 1
Connecting to time server 132.163.4.103
Setting the local time to Fri Mar 20 11:01:55 2009
gmtime gives 109/2/20 11:01:55 [5]
sending to clock 09/03/20 11:01:55 [5]



ls -l /var/hack/zoneinfo/Pacific/Auckland

-rw-r--r-- 1 0 0 882 Sep 7 2007 /var/hack/zoneinfo/Pacific/Auckland

[KEG]

From a unit showing an hour out.

[TiVo [p0] ~]# /bin/ntpdate -b -v 132.163.4.103
Our postcode is 02112. Found matching timezone Pacific/Auckland
Offset 0 for timezone GMT, daylight saving is 0
Connecting to time server 132.163.4.103
Setting the local time to Fri Mar 20 00:32:36 2009
gmtime gives 109/2/20 00:32:36 [5]
sending to clock 09/03/20 00:32:36 [5]


[TiVo [p0] ~]# ls -l /var/hack/zoneinfo/Pacific/Auckland
-rwxr-xr-x 1 0 0 885 Mar 17 12:40 /var/hack/zoneinfo/Pacific/Auckland

[petestrash]

Ok, it looks like the timezone file you loaded may be corrupt.

Did you unzip it on your PC first?

If you did, copy it across again and unzip on the TiVo.

Peter.

[Wibble]

Ok, it looks like the timezone file you loaded may be corrupt.


Make sure your are ftp'ing it in binary mode.

It should be 882 bytes, not 885.

[petestrash]

That is the most likely cause.

I suggested transferring the .zip file to the TiVo as zip's should be automatically transferred in binary if the FTP is set to auto.

Peter.

[Islander]

The method used here: http://forums.oztivo.net/showthread.php?t=1638 worked for both of my tivos last year.
I used this remotely from Britain with no problems.

[KEG]

Hi Guys, all sorted. Was not transfer the file in binary mode, silly me:-)

Thanks for all your help.

Keith

[Grant]

All sorted here too. different date stamps on the files btw the machines...

[hh75]

Hi - my tivo is insisting on thinking daylight savings has finished already in New Zealand, and I'm having to manually reset the time every day. Is anyone else having this problem? Would somon mind telling me a fix?

[Skolink]

http://forums.oztivo.net/showthread.php?t=2082

[hh75]

Thanks - I updated the Auckland timezone file - all good now