Comments on: Clock tick timed out http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/ www.thinkhole.org Tue, 02 Feb 2010 16:30:08 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Skulakos http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/comment-page-1/#comment-161721 Skulakos Thu, 15 May 2008 18:34:01 +0000 http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/#comment-161721 In my Gentoo , it worked! Thanks anyway In my Gentoo , it worked!

Thanks anyway

]]> By: Arnab http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/comment-page-1/#comment-161328 Arnab Wed, 14 May 2008 11:22:16 +0000 http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/#comment-161328 Worked out great! I was not able to sync the local clock with the HW clock using hwclock --hctosys You fixed it for me Thanks a lot for the help Worked out great! I was not able to sync the local clock with the HW clock using
hwclock –hctosys

You fixed it for me

Thanks a lot for the help

]]> By: Koba http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/comment-page-1/#comment-101542 Koba Wed, 26 Sep 2007 00:51:29 +0000 http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/#comment-101542 Awesome! That was the last elusive boot-up error I was seeing. I was working around it with NTP, but only after the system was running. The other persistent problem I had was a "/System.map" file not being found. "modules-update" took care of that too. Awesome! That was the last elusive boot-up error I was seeing. I was working around it with NTP, but only after the system was running.

The other persistent problem I had was a “/System.map” file not being found. “modules-update” took care of that too.

]]> By: Drake http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/comment-page-1/#comment-1463 Drake Thu, 11 May 2006 01:44:48 +0000 http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/#comment-1463 or you can try hwclock --show --directisa or you can try

hwclock –show –directisa

]]> By: mantonson http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/comment-page-1/#comment-1336 mantonson Fri, 28 Apr 2006 05:15:07 +0000 http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/#comment-1336 I'm about to install Gentoo on an SC430, and I was wondering what kernel and guide you used. Did you go genetic x86? or 64-bit? I’m about to install Gentoo on an SC430, and I was wondering what kernel and guide you used. Did you go genetic x86? or 64-bit?

]]> By: aardvark http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/comment-page-1/#comment-501 aardvark Wed, 19 Apr 2006 13:46:17 +0000 http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/#comment-501 Still no worky! :( It turns out that the time displayed by the BIOS was incorrect (i.e. it matched the time reported by Gentoo.) However, adjusting the time in the BIOS makes a rather interesting difference; an external LED clock on the computer's front panel immediately reflects the update. Nevertheless, Gentoo fails to acknowledge the updated information in the BIOS. The man page for hwclock seems to suggest what is going on: "It is important that the System Time not have any discontinuities, such as would happen if you used the date(1L) program to set it while the system is running. (Since I did use the date command before I was aware of this, it seems that the "System Time" has elected to avoid any "discontinuities"; ergo, the apparent time lag.) "You can, however, do whatever you want to the Hardware Clock while the system is running, and the next time Linux starts up, it will do so with the adjusted time from the Hardware Clock (Huh? That doesn't seem to be the case here!). You can also use the program adjtimex(8) to smoothly adjust the System Time while the system runs." Well, I installed adjtimex, ran adjtimexconfig, and issued "rc-update add adjtimex boot" for good measure. Still no dice. The system is a Sager NP9860, and is used in a multi-boot configuration that includes Gentoo, Debian and another OS on an NTFS partition. The other two systems seem to be paying attention; then again, I did unintentionally muck with the 'date' command on Gentoo. Any suggestions? Still no worky! :(

It turns out that the time displayed by the BIOS was incorrect (i.e. it matched the time reported by Gentoo.) However, adjusting the time in the BIOS makes a rather interesting difference; an external LED clock on the computer’s front panel immediately reflects the update.

Nevertheless, Gentoo fails to acknowledge the updated information in the BIOS. The man page for hwclock seems to suggest what is going on:

“It is important that the System Time not have any discontinuities, such as would happen if you used the date(1L) program to set it while the system is running. (Since I did use the date command before I was aware of this, it seems that the “System Time” has elected to avoid any “discontinuities”; ergo, the apparent time lag.)

“You can, however, do whatever you want to the Hardware Clock while the system is running, and the next time Linux starts up, it will do so with the adjusted time from the Hardware Clock (Huh? That doesn’t seem to be the case here!). You can also use the program adjtimex(8) to smoothly adjust the System Time while the system runs.”

Well, I installed adjtimex, ran adjtimexconfig, and issued “rc-update add adjtimex boot” for good measure. Still no dice.

The system is a Sager NP9860, and is used in a multi-boot configuration that includes Gentoo, Debian and another OS on an NTFS partition. The other two systems seem to be paying attention; then again, I did unintentionally muck with the ‘date’ command on Gentoo.

Any suggestions?

]]> By: John http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/comment-page-1/#comment-498 John Tue, 18 Apr 2006 23:52:03 +0000 http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/#comment-498 Did you confirm that the hardware clock is set to the correct time in the BIOS? Check that first and make sure it is correct. Did you confirm that the hardware clock is set to the correct time in the BIOS? Check that first and make sure it is correct.

]]> By: aardvark http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/comment-page-1/#comment-495 aardvark Tue, 18 Apr 2006 15:42:51 +0000 http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/#comment-495 It seems your timing (no pun intended) is impeccable! For whatever reason, I am unable to use NTP at my job (perhaps the administrator is blocking it as a security measure?) Anyway, I tried using the 'date' command to set my clock a few weeks back, and my gentoo system time has been out to lunch ever since. In an attempt to resolve this issue, I have used a variety of options available to hctosys. However, it seems that 'hwclock --adjust', 'hwclock --hctosys' and 'hwclock --directisa' all yield the same result -- reverting to the system time which happens to be incorrect. Using the configuration script you mentioned fails to resolve the matter. I have even recompiled the kernel on several occations to no avail. :( Is there any other way I can get the system time back on track without NTP? It seems that everytime I boot up the system, the time resumes from when ever it was last shut down -- a day, a week, etc. Please help. It seems your timing (no pun intended) is impeccable!

For whatever reason, I am unable to use NTP at my job (perhaps the administrator is blocking it as a security measure?) Anyway, I tried using the ‘date’ command to set my clock a few weeks back, and my gentoo system time has been out to lunch ever since.

In an attempt to resolve this issue, I have used a variety of options available to hctosys. However, it seems that ‘hwclock –adjust’, ‘hwclock –hctosys’ and ‘hwclock –directisa’ all yield the same result — reverting to the system time which happens to be incorrect. Using the configuration script you mentioned fails to resolve the matter. I have even recompiled the kernel on several occations to no avail. :(

Is there any other way I can get the system time back on track without NTP? It seems that everytime I boot up the system, the time resumes from when ever it was last shut down — a day, a week, etc.

Please help.

]]> By: John http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/comment-page-1/#comment-474 John Sat, 15 Apr 2006 14:11:15 +0000 http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/#comment-474 Heh. This is just for use at home, so it's not like I'm running a multi-billion dollar corporation with it. So I'm not too concerned. That said, I would consider Gentoo to be quite stable in experienced hands. Heh. This is just for use at home, so it’s not like I’m running a multi-billion dollar corporation with it. So I’m not too concerned.

That said, I would consider Gentoo to be quite stable in experienced hands.

]]> By: Lon http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/comment-page-1/#comment-473 Lon Sat, 15 Apr 2006 02:58:28 +0000 http://thinkhole.org/wp/2006/04/13/clock-tick-timed-out/#comment-473 Gentoo on a server... better you than me! I've already been through that hell... Gentoo on a server… better you than me! I’ve already been through that hell…

]]>