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

Re: Y2K



Hi again,

It was me that asked for some hint about this hwclock problem. I got a lot 
of hint from Christian, so now can I add some myself. Or is it waist of 
time maybe every Linux-running Amiga owner have already solved the problem?
Anyway this is what I have found out. 
This is if you are running Slink.

Set the date to before 2000 with Time Prefs or via Date in a shell, 
start Linux, login, change the date with hwclock to present date like: 
hwclock --set --date="01/09/00 14:10:15"
then do hwclock --hctosys (I am using local time as systime). 
Now is hwclock working every time I start Linux.
 
**** AFTER THIS DO NOT CHANGE THE TIME WITH ANY AMIGA PROGRAM ****
Because then will battclock be corrupt again. 

I down loaded util-linux-2.10d and compiled the hwclock and this was the
message I got when I run it with --debug.

** First with the date before 2000

Using KDGHWCLK interface to m68k clock.
Assuming hardware clock is kept in local time.
Waiting for clock tick...
Waiting in loop for time from KDGHWCLK to change
...got clock tick
Time read from Hardware Clock: 11:20:27
Hw clock time : 11:20:27 = 946599627 seconds since 1969
Fri Dec 31 11:20:27 1999  -1.317940 seconds

** Then when the date is after 2000

Using KDGHWCLK interface to m68k clock.
Assuming hardware clock is kept in local time.
Waiting for clock tick...
Waiting in loop for time from KDGHWCLK to change
...got clock tick
Time read from Hardware Clock: 11:53:27
Invalid values in hardware clock:  0/01/08 11:53:27

This is saying me that it must be something with Amiga-DOS "setclock" that 
only put in one digit in the year. Because hwclock will run OK if I set the 
ate and time with hwclock and not with Amiga WB-Prefs or AmigaShell Date.
I also changed to year 2010 with Amiga WB-Prefs and the problem was gone.

Now is my question: Is this really a problem with hwclock? 
I do not think so, but I am not any specialist of any sort so I can not say. 
Is it not mktime() that will be confused to only see one digit in the year?
I leave this to you who knows better than me.

All this is done on a A4000T and Debian 2.1 (Slink) 

Thank You for Your time.
 
-->>> Aller <<<--



Reply to: