I installed the AMD64 version of Fedora Core 4-test 1 on my AMD64 computer. The most significant problem that I have encountered so far is the fact that the clock seems to run at double time. I reported this as a bug. Does anyone have any input on this problem?
Cindy Jeness
Hi,
I had to learn the same. only difference: on my AMD64 it is 4 times faster ;-) I have done some investigation up to now:
The prob is definetly a software prob of the FC4. the hwclock is running fine on my AMD.
unfortunately I don't have a solution on that up to now. But I have seen in Bugzilla that some bidy filed it already.
see yo Frank Cynthia Jeness wrote:
I installed the AMD64 version of Fedora Core 4-test 1 on my AMD64 computer. The most significant problem that I have encountered so far is the fact that the clock seems to run at double time. I reported this as a bug. Does anyone have any input on this problem?
Cindy Jeness
Well I have had one heck of a time with the clock on my FC3 box, and it is not AMD 64. It is consistently 5 hours behind no matter what. I can play around with time zones and change the time all I want but it will not stay set to the correct time. I am guessing that there is a bug in the NTP ?
Marc
Hi Marc,
if you are using NTP you should use a local NTP server (same time zone) I have had the same prob on my FC3 Notebook and I only could fix it with changing the NTP server I used. some how the NTP request is overwirting all the other settings.
see you Frank
Marc M wrote:
Well I have had one heck of a time with the clock on my FC3 box, and it is not AMD 64. It is consistently 5 hours behind no matter what. I can play around with time zones and change the time all I want but it will not stay set to the correct time. I am guessing that there is a bug in the NTP ?
Marc
if you are using NTP you should use a local NTP server (same time zone) I have had the same prob on my FC3 Notebook and I only could fix it with changing the NTP server I used. some how the NTP request is overwirting all the other settings.
--Ok, will do, thanks. And yes I am EST.
---In answer to Bret's question, yes, when I run timeconfig, the 'system clock uses UTC' is indeed checked.
--Oh, and this is a dual boot with windblows that I haven't bothered removing, if windblows is the problem I will eradicate that. How do I know for sure that windblows is the problem here?
Marc
Marc M kirjoitti viestissään (lähetysaika perjantai, 1. huhtikuuta 2005 05:37):
---In answer to Bret's question, yes, when I run timeconfig, the 'system clock uses UTC' is indeed checked.
--Oh, and this is a dual boot with windblows that I haven't bothered removing
Windows wants the system clock to be in local time. You must uncheck the "system clock uses UTC" box in a dual-boot machine.
Markku Kolkka wrote:
Marc M kirjoitti viestissään (lähetysaika perjantai, 1. huhtikuuta 2005 05:37):
---In answer to Bret's question, yes, when I run timeconfig, the 'system clock uses UTC' is indeed checked.
--Oh, and this is a dual boot with windblows that I haven't bothered removing
Windows wants the system clock to be in local time. You must uncheck the "system clock uses UTC" box in a dual-boot machine.
Windows can use an ntp server as well :)
Harald Hoyer kirjoitti viestissään (lähetysaika perjantai, 1. huhtikuuta 2005 13:49):
Markku Kolkka wrote:
Windows wants the system clock to be in local time. You must uncheck the "system clock uses UTC" box in a dual-boot machine.
Windows can use an ntp server as well :)
Yes, but that doesn't change the requirement of using local time for the BIOS clock.
Once upon a time, Markku Kolkka markkuk@tuubi.net said:
Yes, but that doesn't change the requirement of using local time for the BIOS clock.
You can also just tell Windows your time zone is GMT.
Hi Marc,
I do not see a reason on a dual boot system that Windows can impact you!? So I don't think you have to remove it
see you Frank Marc M wrote:
if you are using NTP you should use a local NTP server (same time zone) I have had the same prob on my FC3 Notebook and I only could fix it with changing the NTP server I used. some how the NTP request is overwirting all the other settings.
--Ok, will do, thanks. And yes I am EST.
---In answer to Bret's question, yes, when I run timeconfig, the 'system clock uses UTC' is indeed checked.
--Oh, and this is a dual boot with windblows that I haven't bothered removing, if windblows is the problem I will eradicate that. How do I know for sure that windblows is the problem here?
Marc
On Thu, 2005-03-31 at 21:37 -0500, Marc M wrote:
if you are using NTP you should use a local NTP server (same time zone) I have had the same prob on my FC3 Notebook and I only could fix it with changing the NTP server I used. some how the NTP request is overwirting all the other settings.
--Ok, will do, thanks. And yes I am EST.
---In answer to Bret's question, yes, when I run timeconfig, the 'system clock uses UTC' is indeed checked.
--Oh, and this is a dual boot with windblows that I haven't bothered removing, if windblows is the problem I will eradicate that. How do I know for sure that windblows is the problem here?
It is -- well, sortof. If you boot into windows, it reads the hardware clock, which it doesn't know is UTC. So it thinks that's the local time. If the time is corrected (i.e. with something like ntp, or by manual update, or whatever), then it'll write the local time to the hw clock.
So then, when you reboot to Linux, it reads the local time from the hw clock, but it thinks it's reading UTC. So it's off by your timezone offset.
The solution is to either not use UTC, not dual boot, or to make sure Windows never updates the time. Ever. At all.
On Apr 1, 2005 12:10 PM, Peter Jones pjones@redhat.com wrote:
On Thu, 2005-03-31 at 21:37 -0500, Marc M wrote:
if you are using NTP you should use a local NTP server (same time zone) I have had the same prob on my FC3 Notebook and I only could fix it with changing the NTP server I used. some how the NTP request is overwirting all the other settings.
--Ok, will do, thanks. And yes I am EST.
---In answer to Bret's question, yes, when I run timeconfig, the 'system clock uses UTC' is indeed checked.
--Oh, and this is a dual boot with windblows that I haven't bothered removing, if windblows is the problem I will eradicate that. How do I know for sure that windblows is the problem here?
It is -- well, sortof. If you boot into windows, it reads the hardware clock, which it doesn't know is UTC. So it thinks that's the local time. If the time is corrected (i.e. with something like ntp, or by manual update, or whatever), then it'll write the local time to the hw clock.
So then, when you reboot to Linux, it reads the local time from the hw clock, but it thinks it's reading UTC. So it's off by your timezone offset.
The solution is to either not use UTC, not dual boot, or to make sure Windows never updates the time. Ever. At all.
-- Peter
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list
I'm getting some clock problems on my fc3-x86_64 box too. I can loose time pretty fast and here is something from dmesg
warning: many lost ticks. Your time source seems to be instable or some driver is hogging interupts rip 0x2a95716bda