You are not logged in.
Pages: 1
I recently purchased a new laptop with Windows 7 Home Premium, and I've got a dual-boot set up and running perfectly between Win7 and Arch. The only issue is that the date and time in GNOME shell is messed up.
I've checked the all-knowing ArchWiki, and it says that UTC is generally preferred, unless using a Windows operating system or something, in which case using localtime would be preferred. I've done that. the time in GNOME shell still shows up as inaccurate. I've reset the time in GNOME shell to fix it, but seeing as how /etc/rc.conf is sourced upon boot, my efforts were in vain.
Has this occurred with anyone else who has a dual-boot with Windows 7 where the time shows up as inaccurate? If so, what's the method of fixing it?
Last edited by shaunsingh14 (2012-03-17 16:07:44)
I made this account 10 years ago when I was an ignorant and insufferable teenager.
I apologise to all the people I annoyed with my cringe in the past.
Offline
What's the exact timedifference you're seeing? Also, what's the current setting of your hardwareclock (UTC or localtime)?
Burninate!
Offline
I've had the same problem.
I've fixed it by setting HARDWARECLOCK="UTC" in rc.conf and applied this registry key in windows 7
Offline
I've checked the all-knowing ArchWiki, and it says that UTC is generally preferred, unless using a Windows operating system or something, in which case using localtime would be preferred.t?
The wiki does mention UTC in Windows: https://wiki.archlinux.org/index.php/Ti … in_Windows
Please post the output of 'hwclock --debug'.
Offline
shaunsingh14 wrote:I've checked the all-knowing ArchWiki, and it says that UTC is generally preferred, unless using a Windows operating system or something, in which case using localtime would be preferred.t?
The wiki does mention UTC in Windows: https://wiki.archlinux.org/index.php/Ti … in_Windows
Please post the output of 'hwclock --debug'.
Output of
hwclock --debug
is as follows:
[root@the-enforcer shaun]# hwclock --debug
hwclock from util-linux 2.20.1
Using /dev interface to clock.
Last drift adjustment done at 1331440368 seconds after 1969
Last calibration done at 1331440368 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2012/03/11 15:23:59
Hw clock time : 2012/03/11 15:23:59 = 1331479439 seconds since 1969
Sun 11 Mar 2012 11:23:59 AM EDT -0.549004 seconds
[root@the-enforcer shaun]#
I made this account 10 years ago when I was an ignorant and insufferable teenager.
I apologise to all the people I annoyed with my cringe in the past.
Offline
EDT = UTC - 4 hours and your UTC readout seems correct.
Have you manually fixed the time before issuing this command?
Offline
EDT = UTC - 4 hours and your UTC readout seems correct.
Have you manually fixed the time before issuing this command?
In GNOME shell, I've fiddled around with the date and time when I saw that it was incorrect. But when I reboot, the settings aren't kept, seeing as how /etc/rc.conf is sourced upon boot.
I made this account 10 years ago when I was an ignorant and insufferable teenager.
I apologise to all the people I annoyed with my cringe in the past.
Offline
Can you post the output of 'hwclock --debug' right after reboot, when the time is wrong?
Have you switched Windows to UTC?
Offline
No, I don't believe I have switched Windows to UTC.
I made this account 10 years ago when I was an ignorant and insufferable teenager.
I apologise to all the people I annoyed with my cringe in the past.
Offline
That's your problem. Windows overwrites the system clock upon shutdown iirc.
Offline
Okay, I've fixed it in Windows. Switching to UTC in Windows helped solve this issue. Sorry for the long response time.
I made this account 10 years ago when I was an ignorant and insufferable teenager.
I apologise to all the people I annoyed with my cringe in the past.
Offline
Pages: 1