I have a time problem that has me stumped. In our community lab we have dual boot Win7 & Mepis PC's. Our MOBO's are Asus F1A75-V Pro with the new UEFI bios and we are running Mepis11. When we log out of Mepis the BIOS time gets set 5 hours later. Mepis doesn't have a problem with that and I didn't notice that as it gets the correct time from the internet as soon as we logon. But Windows doesn't change the time and shows the wrong time. When we reset the time correctly it stays OK until the next time we run Mepis. When I installed Mepis I am pretty sure I picked the Chicago, central time zone. And when I checked, the correct time zone is shown, Chicago (central time), but upon shutdown the time in the BIOS is reset 5 hours ahead. That five hour difference is the difference between US Central time zone and GMT. Is there some other setting I should look at? Or is there some setting in the BIOS that I seem to be overlooking? The only thing I can remember seeing in the BIOS is the time itself. TIA

I was going to respond by saying that I run dual boot WinXP and Mepis, and have not had a problem with the time since I started. I know I had to set things up on Mepis installation, but I can't remember the critical step.

Then I noticed that my system clock and Mepis time were way out - I expect an hour, because my time setting on the forum is UTC and we have summer time at present. But the forum is running 10 mins behind that. Just to check, I will post this at 18:17 BST (17:17 UTC) precisely.

There is a question about it while running the installer, I forget what it defaults to if you just press 'Enter' .

Btw, the UTC setting has been removed from the /etc/default/rcS file in sid {and probably wheezy as well}.

Quote:

snippet from man:rcS

... The UTC setting is replaced by the UTC or LOCAL setting in /etc/adjtime, and should have been migrated automatically.See hwclock(5) and hwclock(8) for further details on configuring the system clock.

fine print: this doesn't apply to Mepis 11.0 but will when Mepis 12 comes out

I believe the key is to have the bios set to local time. I've never had that issue when the bios is set to local time, then re-setting the time and time zone settings in both Win and Lin. In MEPIS, you'll need to do it through the System Settings dialog as root, and the first time you change it it might not stick. I've had to fight it on occasion.

The problem seems to be that Win assumes that the machine bios is set to local time, while unless told otherwise, Lin thinks it's set to UTC.

... The UTC setting is replaced by the UTC or LOCAL setting in /etc/adjtime, and should have been migrated automatically.See hwclock(5) and hwclock(8) for further details on configuring the system clock.

From Wheezy's /etc/default/rcS:

Quote:

# assume that the BIOS clock is set to UTC time (recommended)#UTC=no # OBSOLETE; see /etc/adjtime and hwclock(8).

... The UTC setting is replaced by the UTC or LOCAL setting in /etc/adjtime, and should have been migrated automatically.See hwclock(5) and hwclock(8) for further details on configuring the system clock.

From Wheezy's /etc/default/rcS:

Quote:

# assume that the BIOS clock is set to UTC time (recommended)#UTC=no # OBSOLETE; see /etc/adjtime and hwclock(8).

Those comment lines mentioning 'BIOS clock' and 'UTC' have been removed from sid's /etc/default/rcS file. It just changed yesterday, it hasn't made it to Wheezy yet. You'll probably see it in the next week or so in Wheezy.

It's an update of the initscripts package 2.88dsf-22.1 --> 2.88dsf-26.

Last edited by kmathern on Fri Jun 08, 2012 3:42 pm, edited 1 time in total.

All times are UTC - 5 hours [ DST ] | It is currently Tue Mar 31, 2015 4:50 pm

Who is online

Users browsing this forum: Yahoo [Bot] and 0 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum