Re: Year 2078 problem!

[mann eecg toronto edu]

i had a similar problem.

the time was wrong, so i set it using the date command, and
then after using the date command, i used the
/sbin/clock
command so that it would persist after rebooting (e.g. this should
set it so the time is correct even if computer shut off and restarted).

when i turned it on again, after shutting down, instead of being the
correct time, it showed 2078, and would not boot until i fixed it.

thus it seems that the /sbin/clock
command does not work.

CLOCK(8)            Linux Programmer's Manual            CLOCK(8)

NAME
       clock - manipulate the CMOS clock

SYNOPSIS
       /sbin/clock [ -u ] -r
       /sbin/clock [ -u ] -w
       /sbin/clock [ -u ] -s
       /sbin/clock [ -u ] -a

DESCRIPTION
       clock  manipulates the CMOS clock in variaous ways, allow-
       ing it to be read or written, and allowing synchronization
       between  the  CMOS  clock  and the kernel's version of the
       system time.


> On an new LX system, I had to reset the hardware clock from the setup menu
> to get the century/time correct. A second time, the clock lost a few hours
> in a day and I set the hardware clock a second time. I have not touched
> anything for two weeks with no further difficulty. 
> 
> I don't understand it, but it worked.
> 
> BTW, if you use an editor, like emacs, that won't write to a file modified
> after you begin your edit (ie, one with a 'future' date) don't forget to
> "touch" any files that inherited the wrong century that you will need to
> modify. 
> 
> On Sun, 23 Aug 1998, Morten Nielsen wrote:
> 
> > 
> > Hi!
> > 
> > I got a little problem that I hope someone can help me 
> > with ...
> > I was in linux when I suddenly realized that the year in my Alpha 
> > was set to year 2000-sumthing ... i corrected this with the control
> > panel in RH5.1 ... but when I rebooted the machine, it said the system
> > time was now set to year 2078! .. and the firmware cant handle this!
> > so now it wont let me boot linux! .. its bugging me to set a new system
> > time in the firmware, but it wont allow me! ... anyone had the same kind
> > of problem? or do anyone have any suggestions on how to solve this?
> > I have tried to take off the "Clear CMOS" jumper, but it didnt help! ...
> > neither did the "reset to factory settings!" option in the firmware.
> > 
> > --Morten
> 
> Mark Hansel (218-236-2039)
> hansel@mhd1.moorhead.msus.edu