You are not logged in.
Pages: 1
Hii, I know its a stregnth problem, but my clock in linux is very wired, sometimes after reset the time is +2 and then when going to windows is -2 or +2 and so on, even after I set it up to be right it does problems,How can set it up please?
Offline
CMOS battery ok?
Time setting in linux - # date MMDDhhmmYYYY
Offline
CMOS battery ok?
Time setting in linux - # date MMDDhhmmYYYY
Yes,its ok, what else?
Offline
lol, that remembers me of a problem I have still, too
I changed the Hardware-Clock to CEST and put TIMEZONE=
Then I deleted the symlink /etc/localtime ->/ushr/share/zoneinfo/Europe/Berlin and now I have the correct time shown...
Offline
A simple BIOS check did it for me.
Offline
lol, that remembers me of a problem I have still, too
I changed the Hardware-Clock to CEST and put TIMEZONE=
Then I deleted the symlink /etc/localtime ->/ushr/share/zoneinfo/Europe/Berlin and now I have the correct time shown...
What did you do?
explain me better please.
Offline
After checking my BIOS-clock (which showed the correct time)
I really was out of ideas, where the problem may be, and played a bit with the settings in /etc/rc.conf
I live in Germany, so GMT+2 is my timezone, I think....
I opened rc.conf and changed the following lines as you can see:
HARDWARECLOCK="localtime"
TIMEZONE=
Then I deleted the symlink /etc/localtime
When I issue date now, I get:
Di Apr 4 22:05:19 UTC 2006
Which means, that Linux "thinks" that I'm in UTC, but thats not true, I'm CET so this can't be the optimal solution. However, I got a correct time now which is more importatnt *g*
Offline
I have same problem since installed arch - have no idea why...
Me too, but i have installed ntp and solve it
Offline
Berlin is on GMT + 1 , like most of western europe.
I had some problems with time also, but solved it like this :
HARDWARECLOCK="UTC"
TIMEZONE=Europe/Amsterdam
Amsterdam, like berlin is GMT + 1, so i changed the bios clock to 1 hour before my normal clock time.
Everything now shows the correct time, and the clock was corrected to summertime automatically.
NOTE : don't use this on a dual-boot system with M$.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Berlin is on GMT + 1 , like most of western europe.
I had some problems with time also, but solved it like this :
HARDWARECLOCK="UTC"
TIMEZONE=Europe/AmsterdamAmsterdam, like berlin is GMT + 1, so i changed the bios clock to 1 hour before my normal clock time.
Everything now shows the correct time, and the clock was corrected to summertime automatically.
For the record after you set your system time using date or ntpdate or whatever, hwclock --utc --systohc will automatically set your bios clock without having to reboot or mess around in BIOS.
Offline
Haha, how complicated... but why did it work with my first install of Arch?
I don't understand it...
Isn't GMT now UTC? and UTC+1=CET (Central European Time) and in Summertime, CET=UTC+2?
So if i tell my rc.conf: "HARDWARECLOCK=CET" and set "TIMEZONE=CET" everything should be fine, but no, when I issue "date", I get 2 hours later than it actually is... args
Offline
Haha, how complicated... but why did it work with my first install of Arch?
I don't understand it...Isn't GMT now UTC? and UTC+1=CET (Central European Time) and in Summertime, CET=UTC+2?
So if i tell my rc.conf: "HARDWARECLOCK=CET" and set "TIMEZONE=CET" everything should be fine, but no, when I issue "date", I get 2 hours later than it actually is... args
NO. HARDWARECLOCK has to be localtime or UTC, for you set it to UTC. TIMEZONE should represent your specific timezone. Its this setting that will automatically adjust daylight savings for you, as each location of the world will be at different times when it occurs. For me TIMEZONE=America/New_York
Look in /usr/share/zoneinfo for available timezones
Offline
This is all to weird for me. Why can't my BIOS have the clock set up in the timezone where I am? I don't put my wrist watch to UTC neither...
But thx for the explanation
Offline
This is all to weird for me. Why can't my BIOS have the clock set up in the timezone where I am? I don't put my wrist watch to UTC neither...
But thx for the explanation
Because your computer would have a difficult time communicating with another on the other side of the world.
Consider both our computers are set to localtime. Say I post a document on my webserver 5 minutes ago at 1:00AM localtime (my time), you, on the side of the world, read this document now and note the time -1:00AM. But there's a problem your timezone hasn't even hit 1:00AM yet, so how can this be?
Thats where UTC comes in. If your computer reads the time of my document posted in UTC, it will automatically know to adjust that time to -4 or whatever your timezone adjustment would be to reflect the proper time to you.
Hope that clears things up.
Offline
Hm I'm not too good in this complex thinking but I guess it makes sense
Thanks for your patience
Offline
Try this
Install ntp (pacman -S ntp)
If you get an error re: /etc/ntp.conf it is OK to delete (or re-name) this file and install ntp.
As root, run these 2 commands:
ntpdate ntp.nasa.gov
hwclock -w
Should do the trick
If is not broken ... tweak it
Offline
Pages: 1