Clock resets itself everytime on boot

  • myrddinemrys
Posted: Sun, 10/21/2007 - 03:46
I try to set the time right, but the clock likes to show that it is 5 hours earlier than what it is. I have checked the timezone, which is appropriately at EST.
‹ how to add another player as a default music player? Root access ›

patch

  • Quentin Harley
  • 05/24/07
  • Tue, 11/20/2007 - 17:06
  • Copy comment link
The patches are already installed in 64studio... You should not patch it twice! Why do you need a kernel you compiled yourself? Cheers

why I'm compiling a custom kernel

  • myrddinemrys
  • 09/25/07
  • Tue, 11/27/2007 - 16:10
  • Copy comment link
I should have prefaced that I have a Sempron processor. Being that my system has experienced some oddities running the 486 kernel provided by 64studio, I thought it best to just compile a custom kernel for k7 arch. Now I think I've found the ultimate root of the problem . . . I believe that my motherboard went "poop". Gives me a better reason to get an AMD64 system :D. My thanks to all who have assisted.

I had a similar

  • distort
  • 10/21/07
  • Sun, 10/21/2007 - 11:23
  • Copy comment link
I had a similar problem. This helped: http://ubuntuguide.org/wiki/Ubuntu:Feisty/Troubleshooting#How_to_disable_system_time.2Fdate_from_being_reset_to_UTC_.28GMT.29

It's still a problem

  • myrddinemrys
  • 09/25/07
  • Sun, 11/18/2007 - 23:08
  • Copy comment link
Thanks for your response. UTC is set to "no", timezone is EST. I discovered a unique twist to this: anytime I use a stock kernel from Debian or 64studio, the clock is fine. If I use a kernel I compiled, I have the above problem.

a little closer to the issue

  • myrddinemrys
  • 09/25/07
  • Mon, 11/19/2007 - 04:34
  • Copy comment link
compiled a vanilla kernel tonight. No clock problem. Apparently 64studio doesn't like Ingo Molnar's preemption patches. Is there a reason for this that anyone can think of?