Bios Time problem

Hardware MikroTik hardware general
1

On my PC (x86 Intel Atom 330) with RouteroS 3.28 I’ve problem with Bios Time settings.

On RoS I’ve set up ntp client and time is correct.
But BIOS time, which is set by ROS (i think so) is one hour late than current time. So BIOS time is set to GMT, while my time is GMT + 01:00.

Of course i try to change time in BIOS, but with no effect. ROS change time to GMT after boot.

It’s really annoying

Any suggestion?

My config:

/system clock
set time-zone-name=Europe/Warsaw
/system clock manual
set dst-delta=+01:00 dst-end="oct/31/2010 03:00:00" dst-start=\
    "mar/27/2010 03:00:00" time-zone=+00:00

system->ntp->client->print

enabled: yes
mode: unicast
primary-ntp: 212.244.36.227
secondary-ntp: 212.244.36.228
status: synchronized
2

I’m not sure MikroTik RouterOS is able to configure clock of your BIOS. Make sure your BIOS is able to store the configuration (upgrade BIOS to the latest version).

3

Ok, I’ll try to do this at weekend and let you know if it works.

Regards

4

Ok, I’ve upgraded BIOS, set Time in BIOS correct, and save it. Then I’ve boot ROS and immediately check clock time in Mikrotik - it’s been one our fast, than my correct time. After few seconds(when Mikrotik synchronized time with NTP server) time in Mikrotik was correct, but in BIOS was one hour late.

So it’s seems like BIOS take only GMT +00 time, but where it could be changed?

5

After a quick google search, GMT+1 timezone should not be using daylight saving time. If dst was enabled it could result in a 1 hour difference. This is only a guess.

6

Hi,

Some Linux distros (Ubuntu, Fedora) set BIOS clock to GMT+0, and set system clock according to selected Time Zone and DST.
Probably RouterOS do the same.

Regards, Grzegorz.

7

@bburley

My settings says, that DST is now off:


 
sys clock print 
time: 11:34:55
date: nov/22/2010
time-zone-name: Europe/Warsaw
gmt-offset: +01:00
dst-active: no

@ditonet

That is possible, but can someone form staff confirm this information.

The main issue is that The Dude Syslog Server didn’t create new log file, although I have set to create new file every hour/every day etc.
I think it might be because of incorrect time settings.

But so far, no one could help me with this issue.

Regards

8

Hello every1,

Even I am facing the same issue from last 2 week where suddenly Dude 3.6 stop creating a new file. Initially I have tried to change language setting to English & then check date time setting too. when I execute Dude.exe or restart the server new file gets created but it work till next 24hrs only after that it again gets stopped.

Please suggest or help me what could be the issue or how we can scheduled daily .log from this.