time always changes on reboot

English Applications
#1

i set the clock and done every setting i can think of, the time get sets correctly and at reboot goes back to a differnt time.?

#2

diablo1 wrote:
>
> i set the clock and done every setting i can think of, the time get sets
> correctly and at reboot goes back to a differnt time.?
>
>

You might want to tell which openSUSE version you are running?

Vahis

http://waxborg.servepics.com
openSUSE 11.4 (x86_64) 2.6.37.6-0.9-default main host
openSUSE 12.1 (x86_64) 3.1.1-48-desktop Tumbleweed in VirtualBox
openSUSE 12.1 (i586) 3.1.0-1.2-desktop in EeePC 900

#3

opensuse 12.1(x86_64)3.1.0-1.2 kde 4.7.2 release 5

#4

When you reboot, is the time off by minutes or by hours?

Are you running other operating systems (such as Windows)? If so, perhaps they have incompatible settings for the hardware clock.

What’s the output from


grep HWCLOCK /etc/sysconfig/clock
#5

[CODEsuse@linux-bv9r:~> grep HWCLOCK /etc/sysconfig/clock
HWCLOCK="-u"
]



off by hours 4 hours.  just windows networked with opensuse
#6

diablo1 wrote:
>
> opensuse 12.1(x86_64)3.1.0-1.2 kde 4.7.2 release 5
>
>

Do you have NTP running?

Vahis

http://waxborg.servepics.com
openSUSE 11.4 (x86_64) 2.6.37.6-0.9-default main host
openSUSE 12.1 (x86_64) 3.1.1-48-desktop Tumbleweed in VirtualBox
openSUSE 12.1 (i586) 3.1.0-1.2-desktop in EeePC 900

#7

in system services no.
ill turn it on

#8

turned NTP on but time is still 4 hours off after I set it then reboot

#9

When you are multi boot with a Windows system, you should use “set hardware clock to local time” (not to UTC), because Windows does not understand a good time system and sets the clock to local time (you are apperently 4 hours off from UTC).

YaST > System > Date and time. Uncheck the box lower left.

And settinf the NTP service ON in services (runlevel) is not enough. You must configure a server. use
YaST > Network services > NTP configuration. Add > Server > Public server.

#10

As root, run the following command:


# hwclock -w

The system clock is supposed to be written back to the hardware clock on shutdown. However, it is possible that systemd is skipping that step (in which case it is a bug that needs reporting).

I did notice that my system clock was 22 seconds off today. I had set it correctly yesteday. But I rebooted this morning. It normally does not drift that much. However, if when setting it yesterday, that never got written back to the hardware clock on rebooting, then the 22 seconds error makes sense.

I’m going to do some testing, to see if the hardware clock is being written back.

#11

its not a dual boot system. one hard drive one opensuse 12.1 operating system on laptop only one partition. the windows is on another computer only networked. ill try some of the thing above

thanks

#12

It appears that the system clock is not being written back to the hardware clock. Presumably, it will be if I boot using sysvinit. I’ll test that, and then report back.

#13

It did not update the hardware clock with sysvinit either.

Here’s what I did. I checked my laptop. The time was off by 4 seconds. So I set from an ntp time server (with a manual command). That indicated an approx 4 second change.

I rebooted. It was again off by 4 seconds.

I rebooted with sysvinit. I reset the clock to the correct time again. Then I rebooted. Since the shutdown was being managed by sysvinit, I expected the hardware clock to update. But no, on reboot, it was 4 seconds out.

As a final check, I ran


hwclock -w

and then rebooted. This time, the clock was correct after the reboot.

Addendum: It looks as if I have to setup “boot.clock” as a run level service for this to work. I don’t recall having to do that in prior versions.

#14

i did all those thing about and hwclock -w and my clock keeps resetting to something after i reboot, so whatever im doing isnt getting saves when i shutdown, its 2 hours ahead one reboot 2 hours behind after reboot, a mess. ready to shut clock down its usless

#15

On 2011-12-18 23:56, diablo1 wrote:
>
> i did all those thing about and hwclock -w and my clock keeps resetting
> to something after i reboot, so whatever im doing isnt getting saves
> when i shutdown, its 2 hours ahead one reboot 2 hours behind after
> reboot, a mess. ready to shut clock down its usless

Adjust clock, as root in a terminal, update cmos clock, then delete the
/etc/adjtime file.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#16

Am Sun, 18 Dec 2011 18:46:02 +0000 schrieb diablo1:

> i set the clock and done every setting i can think of, the time get sets
> correctly and at reboot goes back to a differnt time.?

Did you set it to hardware clock upon installation? If so, uncheck it. I
had a similar problem once and by unchecking it went to normal.

#17

do i do it this way from Linux Set Date and Time From a Command Prompt

Use %p locale’s equivalent of either AM or PM, enter:
# date +%T%p -s "6:10:30AM"
# date +%T%p -s "12:10:30PM"

as for cmos- no clue there

#18

I missed a step. when i went into time and date from yast i was told try unchecking hardware clock set to UTC. Then i hit ok What i should have done after that was hit the change button in time and date and change the time there as well:O. I tried that and the time seems to be staying now…

thanks:good:

#19

You should only uncheck that box when you are multibooting with Windows because it adapts toi the Windows way of time keeping. When you do not multiboot, it should be on UTC (like every true Unix/Linux system).

#20

multiboot? my laptop has one drive, one operating system opensuse for now but later ill throw in a drive with windows on it? maybe back and forth, is that considered a multiboot?

on my desktop, i have three hardrives in my tower each with its own system, one HD with windows, one HD with opensuse 12.1 and one hd with old xp pro. ill boot up into the HD i want at the time thru my asus bios boot. thats considered multiboot right?

thanks