Hello,
When I installed SuSE, YaST suggested that my hardware-clock was set to
use GMT. But this seems to have the effect, that the time is two hours
ahead every time I start my PC. I adjust it - and the next time I start,
it's two hours ahead again. I have told YaST that I live in Europe
(Denmark), so I really don't understand why this is happening. Anyone?
--
Jannik Lindquist
Jannik Lindquist wrote:
Hello,
When I installed SuSE, YaST suggested that my hardware-clock was set to use GMT. But this seems to have the effect, that the time is two hours ahead every time I start my PC. I adjust it - and the next time I start, it's two hours ahead again. I have told YaST that I live in Europe (Denmark), so I really don't understand why this is happening. Anyone?
When you were installing SuSE 8 you were given the choice of using local time or GMT time and, I think, there is a bit of information about this in the dialogue box where it is suggested that if you are only installing Linux as your only OS then use GMT time; but if you dual booting and have Windows installed then not to use GMT but to use local time (because Windows is braindead and can only properly handle local time). You can change which time mode you are using from the Control Centre. Cheers.
On Saturday 22 June 2002 03:38, Basil Chupin wrote:
Jannik Lindquist wrote:
Hello,
When I installed SuSE, YaST suggested that my hardware-clock was set to use GMT. But this seems to have the effect, that the time is two hours ahead every time I start my PC. I adjust it - and the next time I start, it's two hours ahead again. I have told YaST that I live in Europe (Denmark), so I really don't understand why this is happening. Anyone?
When you were installing SuSE 8 you were given the choice of using local time or GMT time and, I think, there is a bit of information about this in the dialogue box where it is suggested that if you are only installing Linux as your only OS then use GMT time; but if you dual booting and have Windows installed then not to use GMT but to use local time (because Windows is braindead and can only properly handle local time). If you have multiple boot with local hardware clock time, your clock will be set forward or back by each OS the first time you start it after what it considers to be time change date. This is one of the aspects of dual boot being "unsupported" in Windows.
You can change which time mode you are using from the Control Centre.
Cheers.
-- Tim Prince
Hej Basil and Tim, Thank you to you both. I do *not* have Windows installed and I chose the "GMT"-option in YaST when I installed. Nonetheless, the problem persists - and it doesn't help to change the YaST-setting to "local". Sat, 22 Jun 2002 20:38:01 +1000 skrev du:
Jannik Lindquist wrote:
Hello,
When I installed SuSE, YaST suggested that my hardware-clock was set to use GMT. But this seems to have the effect, that the time is two hours ahead every time I start my PC. I adjust it - and the next time I start, it's two hours ahead again. I have told YaST that I live in Europe(Denmark), so I really don't understand why this is happening. Anyone?
When you were installing SuSE 8 you were given the choice of using local time or GMT time and, I think, there is a bit of information about this in the dialogue box where it is suggested that if you are only installing Linux as your only OS then use GMT time; but if you dual booting and have Windows installed then not to use GMT but to use local time (because Windows is braindead and can only properly handle local time).
You can change which time mode you are using from the Control Centre.
Cheers.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
I'm in exactly the same situation as you. The only solution that I found was to set the RTC through the BIOS to be two hours earlier than it is, Linux then sets it to the right time. Whenever I go online I also do a ntp check. jalal Jannik Lindquist wrote:
Hej Basil and Tim,
Thank you to you both. I do *not* have Windows installed and I chose the "GMT"-option in YaST when I installed. Nonetheless, the problem persists - and it doesn't help to change the YaST-setting to "local".
Sat, 22 Jun 2002 20:38:01 +1000 skrev du:
Jannik Lindquist wrote:
Hello,
When I installed SuSE, YaST suggested that my hardware-clock was set to use GMT. But this seems to have the effect, that the time is two hours ahead every time I start my PC. I adjust it - and the next time I start, it's two hours ahead again. I have told YaST that I live in Europe(Denmark), so I really don't understand why this is happening. Anyone?
When you were installing SuSE 8 you were given the choice of using local time or GMT time and, I think, there is a bit of information about this in the dialogue box where it is suggested that if you are only installing Linux as your only OS then use GMT time; but if you dual booting and have Windows installed then not to use GMT but to use local time (because Windows is braindead and can only properly handle local time).
You can change which time mode you are using from the Control Centre.
Cheers.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
See man hwclock. hwclock gives you a lot of control over the CPU and system clocks. Also pay attention to /etc/adjtime. This is where the system is told that the CPU clock is or is not set to UTC. I believe that once long ago I had clock problems that were solved by deleting /etc/adjtime and then setting things up fresh with hwclock. -- Robert C. Paulsen, Jr. robert@paulsenonline.net
if (windows installed){ I know (but I don't remember exactly) that when you have both and boot in windows it will adjust the clock, etc. (some stuff with BIOS, GMT, UTC) } else{ it's another problem... } If you evaluate the expresion "windows installed" for us, returning TRUE or FALSE maybe we will be able to help you. Cheers, Dan On Saturday 22 June 2002 06:02, Jannik Lindquist wrote:
Hello,
When I installed SuSE, YaST suggested that my hardware-clock was set to use GMT. But this seems to have the effect, that the time is two hours ahead every time I start my PC. I adjust it - and the next time I start, it's two hours ahead again. I have told YaST that I live in Europe (Denmark), so I really don't understand why this is happening. Anyone?
Hej Dan,
If you evaluate the expresion "windows installed" for us, returning TRUE or FALSE maybe we will be able to help you.
No, I do not have Windows installed :-)
--
Jannik Lindquist
On Sat, Jun 22, 2002 at 01:27:18PM +0200, Jannik Lindquist wrote:
Hej Dan,
If you evaluate the expresion "windows installed" for us, returning TRUE or FALSE maybe we will be able to help you.
No, I do not have Windows installed :-)
If you have a permanent net connection, I'd suggest installing xntp. I had trouble with time since I got my new pc, which coincided with 7.3 and my finally ditching W$... xntp's been taking care of time ever since. No trouble at all... Just a thought :) hth Jon Clausen
On Saturday 22 June 2002 08:02, Jannik Lindquist wrote:
Hello,
When I installed SuSE, YaST suggested that my hardware-clock was set to use GMT. But this seems to have the effect, that the time is two hours ahead every time I start my PC. I adjust it - and the next time I start, it's two hours ahead again. I have told YaST that I live in Europe (Denmark), so I really don't understand why this is happening. Anyone?
Just guessing, but here's a possibilty what might happen: during startup, in /etc/init.d/boot.clock a call is made to `hwclock --adjust'. Because of the --adjust, hwclock takes the contents of /etc/adjtime into consideration. It uses this info to detect and compensate systematic drift of the HW clock. Now, if you adjust your clock yourself, next time during boot up hwclock detects a huge drift and puts the clock on a time that you wouldn't expect. IIRC, the solution is either the delete the /etc/adjtime (it will be recreated automatically), or put "0.0 0 0.0" in this file. I've been fooled by this behaviour more than once. But that doesn't say your problem is the same. Paul. P.S.: see `man hwclock'
participants (8)
-
Basil Chupin -
Dan Laba -
jalal -
Jannik Lindquist -
Jon Clausen -
Paul Uiterlinden -
Robert C. Paulsen Jr. -
Tim Prince