Hello SuSe people, Really strange. Every time I reboot my computrer it loses 4 hours exactly. (I shut down every night and restart the folowing day) I can set the time exactly using an NTP server Running 10.3 64 bit and KDE3. To test this, tonight wiith the exact time correct. I shut down and rebooted 3 times. Each time I rebooted it lost exactly 4 hours. A total of 12 hours. First time, 4 hours, Second time an additional 4 hours or eight hours total. Third time an additional 4 hours or a total of 12 hours. After every corrrective reset I do an hwclock --systohc Anyone, any ideas on what could be happening here? Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
Hello SuSe people,
Really strange.
Every time I reboot my computrer it loses 4 hours exactly. (I shut down every night and restart the folowing day) I can set the time exactly using an NTP server Running 10.3 64 bit and KDE3.
To test this, tonight wiith the exact time correct. I shut down and rebooted 3 times. Each time I rebooted it lost exactly 4 hours. A total of 12 hours. First time, 4 hours, Second time an additional 4 hours or eight hours total. Third time an additional 4 hours or a total of 12 hours.
After every corrrective reset I do an hwclock --systohc
Anyone, any ideas on what could be happening here?
Bob S
That is strange, I usually just loose about 2 hours when the aliens pick me up. But seriously, do the same experiment but this time only boot into the BIOS. Check if you also loose some time. If you do, its a hardware issue, battery probably dying. Manne ps also check for small needle marks on your body. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 21 October 2008 02:08:22 am Manne Merak wrote:
Bob S wrote:
Hello SuSe people,
Really strange.
Every time I reboot my computrer it loses 4 hours exactly. (I shut down every night and restart the folowing day) I can set the time exactly using an NTP server Running 10.3 64 bit and KDE3.
To test this, tonight wiith the exact time correct. I shut down and rebooted 3 times. Each time I rebooted it lost exactly 4 hours. A total of 12 hours. First time, 4 hours, Second time an additional 4 hours or eight hours total. Third time an additional 4 hours or a total of 12 hours.
After every corrrective reset I do an hwclock --systohc
Anyone, any ideas on what could be happening here?
Bob S
That is strange, I usually just loose about 2 hours when the aliens pick me up.
But seriously, do the same experiment but this time only boot into the BIOS. Check if you also loose some time. If you do, its a hardware issue, battery probably dying.
Hi Manne, No I can continually boot into the bios and it doesn't change. Just changed the battery. Funny, seems to have happened about that time. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2008-10-22 at 00:11 -0400, Bob S wrote:
No I can continually boot into the bios and it doesn't change. Just changed the battery. Funny, seems to have happened about that time.
Makes sense... the clock has to be set and the adjtime gets the wrong offset. That's why the file has to be deleted. Maybe we have now to recreate the file manually with our settings. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkj/qD4ACgkQtTMYHG2NR9VIdwCfQ57vmA4u5mvkOZ6cINSCU5U8 mugAnjA1sFEwdFuacz04639VBrE4Y1Ls =a+zP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
Hello SuSe people,
Really strange.
Every time I reboot my computrer it loses 4 hours exactly. (I shut down every night and restart the folowing day) I can set the time exactly using an NTP server Running 10.3 64 bit and KDE3.
To test this, tonight wiith the exact time correct. I shut down and rebooted 3 times. Each time I rebooted it lost exactly 4 hours. A total of 12 hours. First time, 4 hours, Second time an additional 4 hours or eight hours total. Third time an additional 4 hours or a total of 12 hours.
After every corrrective reset I do an hwclock --systohc
Anyone, any ideas on what could be happening here?
Bob S
Bob, Is the box a dual-boot box with windows installed? Are you GMT+-4 in your timezone? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 21 October 2008 04:40:36 am David C. Rankin wrote:
Bob S wrote:
Hello SuSe people,
Really strange.
Every time I reboot my computrer it loses 4 hours exactly. (I shut down every night and restart the folowing day) I can set the time exactly using an NTP server Running 10.3 64 bit and KDE3.
To test this, tonight wiith the exact time correct. I shut down and rebooted 3 times. Each time I rebooted it lost exactly 4 hours. A total of 12 hours. First time, 4 hours, Second time an additional 4 hours or eight hours total. Third time an additional 4 hours or a total of 12 hours.
After every corrrective reset I do an hwclock --systohc
Anyone, any ideas on what could be happening here?
Bob S
Bob,
Is the box a dual-boot box with windows installed? Are you GMT+-4 in your timezone?
Yes and yes (EDT) but I haven't booted windoze in over a year. See my reply to Ingolf. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
On Tuesday 21 October 2008 04:40:36 am David C. Rankin wrote:
Bob S wrote:
Hello SuSe people,
Really strange.
Every time I reboot my computrer it loses 4 hours exactly. (I shut down every night and restart the folowing day) I can set the time exactly using an NTP server Running 10.3 64 bit and KDE3.
To test this, tonight wiith the exact time correct. I shut down and rebooted 3 times. Each time I rebooted it lost exactly 4 hours. A total of 12 hours. First time, 4 hours, Second time an additional 4 hours or eight hours total. Third time an additional 4 hours or a total of 12 hours.
After every corrrective reset I do an hwclock --systohc
Anyone, any ideas on what could be happening here?
Bob S Bob,
Is the box a dual-boot box with windows installed? Are you GMT+-4 in your timezone?
Yes and yes (EDT) but I haven't booted windoze in over a year. See my reply to Ingolf.
Bob S
Well, Regardless, if you will ever boot windows, then you need to set your hwclock to localtime and not UTC. In Yast -> Date & Time when the map is displayed, look in the lower left corner and there is a check box "Hardware Clock set to UTC". Make sure that the box is not checked --or-- checked if it isn't checked on your system. On my single boot box with hwclock set to UTC, there is no check in that box (rather counterintuitive really) However, my date and date -u show correct time for central zone: 00:53 alchemy~/linux/scripts> date Wed Oct 22 00:55:08 CDT 2008 00:55 alchemy~/linux/scripts> date -u Wed Oct 22 05:55:09 UTC 2008 I noticed that if I did check the box, the time was set 5 hours in the past. In essence, applying the offset twice. A good test is just to set your system clock by hand and make sure it works right. As root, set the time with: date MMDDHHMMCCYY.ss (example # date 102201022008.00) Then look at how your systems is handling time: date date -u Which is right? If you are still 4 hours in the past, then set the time with "date -u" to specify you are setting time in UTC. Do the same test with date and date -u. Post the results and we will investigate further with you. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Quoting David C. Rankin
Regardless, if you will ever boot windows, then you need to set your hwclock to localtime and not UTC. [snip]
If you use Windows very seldom and travel to other timezones frequently, it may be more convenient (or less inconvenient) to set your Windows timezone to UTC (AKA London or GMT) and set your hardware clock to UTC. I am in another timezone more often than I boot into Windows. HTH, Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 22 October 2008 02:04:56 am David C. Rankin wrote:
Bob S wrote:
On Tuesday 21 October 2008 04:40:36 am David C. Rankin wrote:
....<snip original>,,,,,,,,
Bob,
Is the box a dual-boot box with windows installed? Are you GMT+-4 in your timezone?
Yes and yes (EDT) but I haven't booted windoze in over a year. See my reply to Ingolf.
Bob S
Well,
Regardless, if you will ever boot windows, then you need to set your hwclock to localtime and not UTC. In Yast -> Date & Time when the map is displayed, look in the lower left corner and there is a check box "Hardware Clock set to UTC". Make sure that the box is not checked --or-- checked if it isn't checked on your system. On my single boot box with hwclock set to UTC, there is no check in that box (rather counterintuitive really) However, my date and date -u show correct time for central zone:
00:53 alchemy~/linux/scripts> date Wed Oct 22 00:55:08 CDT 2008 00:55 alchemy~/linux/scripts> date -u Wed Oct 22 05:55:09 UTC 2008
I noticed that if I did check the box, the time was set 5 hours in the past. In essence, applying the offset twice. A good test is just to set your system clock by hand and make sure it works right. As root, set the time with:
date MMDDHHMMCCYY.ss (example # date 102201022008.00)
Then look at how your systems is handling time:
date date -u Which is right?
If you are still 4 hours in the past, then set the time with "date -u" to specify you are setting time in UTC. Do the same test with date and date -u.
Hi David, Well, I went into Yast and set 10.3 to UTC. (Checked the lttle box and reset the time after I updated with NTP. That seems like kind of a hack to me though because I have to reset the other OS's also. I run three beside Windoz just to play with them. They were fine, as well as was 10.3 until something happened to 10.3 that kept making it lose 4 hours at every reboot. I've rebooted twice since the change and it appears to be keeping time properly. We will see. This is indeed a strange occurence. If I am not mistaken this seems to have happened about the time of the last kernel update. The update screwed up my nvidia card/driver which I have to investigate next. Think it could have been the kernel? Remembering now, that the other OS's weren't effected. What will happen if I boot Windoz? Will just the time in Windoz be wrong, or will it do something to the system clock? Thanks David, Carlos, and to everybody, and there were many of you, offering advice and tips. Much appreciated. We will see what happens. Bob S. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2008-10-22 at 23:45 -0400, Bob S wrote:
Hi David,
Well, I went into Yast and set 10.3 to UTC. (Checked the lttle box and reset the time after I updated with NTP. That seems like kind of a hack to me though because I have to reset the other OS's also. I run three beside Windoz just to play with them. They were fine, as well as was 10.3 until something happened to 10.3 that kept making it lose 4 hours at every reboot. I've rebooted twice since the change and it appears to be keeping time properly. We will see. This is indeed a strange occurence.
If I am not mistaken this seems to have happened about the time of the last kernel update. The update screwed up my nvidia card/driver which I have to investigate next. Think it could have been the kernel? Remembering now, that the other OS's weren't effected.
I don't think so. It is usually a bad /etc/adjtime file.
What will happen if I boot Windoz? Will just the time in Windoz be wrong, or will it do something to the system clock?
The time will simply be wrong, and nothing will happen unless windows tries to set up the time from internet. This is what I do, by the way. Perhaps you can set your windows system to be either UTC or UTC-4. You may also have problems when windows thinks that the winter/summer hour jump occurs between boots. I mean, you use your computer in summer, when the hour is, say, +2. Then next time you boot windows is winter, the time is +1, and windows sets the clock back one hour. When windows pop up, I just undo the change. I don't remember now, I think I didn't find a way to disable that summer/winter time shift, tell it to keep UTC and stay. Those reasons certainly support the choice of local time for the CMOS clock, but... Linux works better with he other choice :-p No, seriously, openSUSE should work fine with both settings. you could also try: SYSTOHC="no" in /etc/sysconfig/clock, but I don't know when this was introduced. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkA+ysACgkQtTMYHG2NR9X1RQCgj48Vow6/DlYBCXhkgv/gMrDA rR8An2iBxtQjC+xbI7I4V/AXEHBtt+Rs =Dzyh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 21 October 2008 04:40:36 am David C. Rankin wrote:
Bob S wrote:
Hello SuSe people,
Really strange.
Every time I reboot my computrer it loses 4 hours exactly. (I shut down every night and restart the folowing day) I can set the time exactly using an NTP server Running 10.3 64 bit and KDE3.
To test this, tonight wiith the exact time correct. I shut down and rebooted 3 times. Each time I rebooted it lost exactly 4 hours. A total of 12 hours. First time, 4 hours, Second time an additional 4 hours or eight hours total. Third time an additional 4 hours or a total of 12 hours.
After every corrrective reset I do an hwclock --systohc
Anyone, any ideas on what could be happening here?
Bob S
Bob,
Is the box a dual-boot box with windows installed? Are you GMT+-4 in your timezone?
Yes and yes (EDT) but I haven't booted windoze in over a year. See my reply to Ingolf.
Bob S
Do you use openSUSE 11.O and updated ? When I install openSUSE 11.0 the first time from DVD , it is so, time is wrong after every reboot. If I have a network with it, I would update something, it goes OK then. But if I dont update, it would still be that, everytime I reinstall with DVD. : ) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 24 October 2008 11:18:25 am v.s.u wrote:
Do you use openSUSE 11.O and updated ?
When I install openSUSE 11.0 the first time from DVD , it is so, time is wrong after every reboot. If I have a network with it, I would update something, it goes OK then. But if I dont update, it would still be that, everytime I reinstall with DVD. : )
No, I'm sorry. This was on 10.3. I cured the problem by setting the system time to UTC in Yast. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 21 October 2008 07.46:08, Bob S wrote:
Hello SuSe people,
Really strange.
Every time I reboot my computrer it loses 4 hours exactly. (I shut down every night and restart the folowing day) I can set the time exactly using an NTP server Running 10.3 64 bit and KDE3.
To test this, tonight wiith the exact time correct. I shut down and rebooted 3 times. Each time I rebooted it lost exactly 4 hours. A total of 12 hours. First time, 4 hours, Second time an additional 4 hours or eight hours total. Third time an additional 4 hours or a total of 12 hours.
After every corrrective reset I do an hwclock --systohc
Anyone, any ideas on what could be happening here?
Bob S
try if it still happens when you delete /etc/adjtime (correct time as you like, hwclock --systohc, rm /etc/adjtime) the file will be recreated, so don't worry... Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 21 October 2008 05:31:31 am Daniel Bauer wrote:
On Tuesday 21 October 2008 07.46:08, Bob S wrote:
Hello SuSe people,
Really strange.
Every time I reboot my computrer it loses 4 hours exactly. (I shut down every night and restart the folowing day) I can set the time exactly using an NTP server Running 10.3 64 bit and KDE3.
To test this, tonight wiith the exact time correct. I shut down and rebooted 3 times. Each time I rebooted it lost exactly 4 hours. A total of 12 hours. First time, 4 hours, Second time an additional 4 hours or eight hours total. Third time an additional 4 hours or a total of 12 hours.
After every corrrective reset I do an hwclock --systohc
Anyone, any ideas on what could be happening here?
Bob S
try if it still happens when you delete /etc/adjtime (correct time as you like, hwclock --systohc, rm /etc/adjtime)
the file will be recreated, so don't worry...
Daniel
Thanks Daniel. Yes, it still happens. See my reply to Ingolf. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I tried every script mod, deletion, etc I found (including the Sourceforge How-To so many folks like to refer us to) to no avail. I do not know if this will solve everyone's issue, but this is what finally worked for me - you will note that your settings have to be like mine for this fix to probably work (see under the steps for explanation): 1) Ensure the time is set properly in CMOS and software via Yast. 2) In the KDE menu program menu, select "Save Session" Ever since I re-saved my session, the clock has stopped resetting itself. Splanation (long): I have no idea what happened behind the scenes, but the first thing I do upon installation/upgrade is turn off the silly new KDE menu style, and revert to the basic KDE menu. I thereafter set my system thru KDE's Control Panel to "load saved session", because I tend to tweak and experiment a lot and have messed up my KDE configs pretty badly before :D I explicitly remember when I switched to 11.0, NTP had been enabled, and my stupid router was "off" (set to UTC vs. local). When I finally did get around to turning off NTPD, it had already sunc (that's Texan for 'synch'ed') the time AND I had already saved my session and changed KDE to load that saved session every boot. It doesn't seem to me that time zone should be saved in KDE session settings, but I re-saved the session this past Thursday, et violins, it hasn't mysteriously reset my time since then - and I've rebooted to test this theory about 15 times. Good thing, too, because between that odd behavior and the totally unhelpful "what are you guys idiots who cannot read" posts to the listserv, I was going insane. I kinda made it worse, because I typically don't reboot my system for weeks, and would forget about the problem with the time, hehe. BTW - guys, we ARE reading and trying your suggestions - sometimes the cause ain't what you're asserting. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2008-10-21 at 01:46 -0400, Bob S wrote:
Hello SuSe people,
Really strange.
Every time I reboot my computrer it loses 4 hours exactly. (I shut down every night and restart the folowing day) I can set the time exactly using an NTP server Running 10.3 64 bit and KDE3.
To test this, tonight wiith the exact time correct. I shut down and rebooted 3 times. Each time I rebooted it lost exactly 4 hours. A total of 12 hours. First time, 4 hours, Second time an additional 4 hours or eight hours total. Third time an additional 4 hours or a total of 12 hours.
After every corrrective reset I do an hwclock --systohc
Anyone, any ideas on what could be happening here?
Yep. Known thing. Curious that your time zone is -4 hours, eh? ;-) http://susefaq.sourceforge.net/howto/time.html It's old, but the remedy and cause is the same. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkj9uUYACgkQtTMYHG2NR9UwUgCghwjzXOTt4p0P5pZYtKwo4Jd8 0l0AnRVLLFaTcHZgRvyMxpEHttm9pnS+ =ro8I -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 21 October 2008 07:13:08 am Carlos E. R. wrote:
On Tuesday, 2008-10-21 at 01:46 -0400, Bob S wrote:
Hello SuSe people,
Really strange.
Every time I reboot my computrer it loses 4 hours exactly. (I shut down every night and restart the folowing day) I can set the time exactly using an NTP server Running 10.3 64 bit and KDE3.
To test this, tonight wiith the exact time correct. I shut down and rebooted 3 times. Each time I rebooted it lost exactly 4 hours. A total of 12 hours. First time, 4 hours, Second time an additional 4 hours or eight hours total. Third time an additional 4 hours or a total of 12 hours.
After every corrrective reset I do an hwclock --systohc
Anyone, any ideas on what could be happening here?
Yep. Known thing. Curious that your time zone is -4 hours, eh? ;-)
http://susefaq.sourceforge.net/howto/time.html
It's old, but the remedy and cause is the same.
Hi Carlos, Yep, sure is curious. I read that how-to by you at least four times. I must be really thick or something. I think I have done everything you explained there. I have an adsl connection so once I am booted up it is a permanent connection but I shut down every night and reboot every evening. I never had to do a timeset except every couple of months because the PC kept pretty good time. And then I would do a manual correction and continue on my merry way for the next 3 or 4 months. I gave a pretty detailed explanation to Ingolf. Maybe you could check that out and tell me where I am screwing up. Thanks again. Bob S. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2008-10-21 at 17:23 -0400, Bob S wrote:
Yep. Known thing. Curious that your time zone is -4 hours, eh? ;-)
http://susefaq.sourceforge.net/howto/time.html
It's old, but the remedy and cause is the same.
Hi Carlos,
Yep, sure is curious. I read that how-to by you at least four times. I must be really thick or something. I think I have done everything you explained there. I have an adsl connection so once I am booted up it is a permanent connection but I shut down every night and reboot every evening. I never had to do a timeset except every couple of months because the PC kept pretty good time. And then I would do a manual correction and continue on my merry way for the next 3 or 4 months.
I gave a pretty detailed explanation to Ingolf. Maybe you could check that out and tell me where I am screwing up.
Well... I wrote that piece for SuSE 8.2, I think, but I know it works (the clock scripts have changed), at least in console mode. Perhaps what you have found is an strange interaction with KDE. Dunno. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkj/pZ8ACgkQtTMYHG2NR9Vi/ACdFPOX8Yrzn2lkfjWNsPqUvgsD GugAnA5uLvWvHqRJtYN6U4wgzRANGZf1 =iYhJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Bob S -
Carlos E. R. -
Curt Bryson (GMail) -
Daniel Bauer -
David C. Rankin -
Jeffrey L. Taylor -
Manne Merak -
v.s.u