johnneylee.rollins at gmail.com
Thu Dec 10 20:49:52 PST 2009
> I am use to old hardware (i486DX) having problems keeping time on the
> hardware clock. But isn't the system clock a separate thing? I am losing
> about 4 min on the system clock for every 10 minutes of real time. I've
> googled around for clock drift information. What I found suggests that
> a system under heavy load with the 2.6.x kernel on certain hardware
> might show this symptom. I've yet to try it, but I've read that adding
> "clock=pit noapic nolapic" to the boot parameters should fix it.
> Is this something that will affect an LFS build? I don't like the idea
> of finding out towards the end that it will. That is my main concern.
> Should I ignore the clock issue? Is this something I should concern
> myself about? Any advice would be welcome.
> Thanks in Advance,
> Mykal Funk
I'm not sure about a permanent fix, but a script to update the time with a
ntp server might help. I'm not sure of the best method for offline use
unless someone can absolve this issue with a more permanent solution.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lfs-support