Problem: clockspeed on 2Ghz Athlon
[email protected] Tue, 25 Mar 2003 14:17:21 -0500 (EST)
| Newsgroups | gmane.comp.lib.libtai |
|---|---|
| Message-ID | <[email protected]> |
Hello, I'm running clockspeed on a system based on Dan's recommendations at <http://cr.yp.to/hardware/advice.html>, except that (1) it has 1GB of RAM, instead of 256MB, and (2) it has a 2Ghz Athlon CPU, instead of 1.667 Ghz. Originally I set up the system without moving the bus-speed dip switch from its factory default, 100Mhz. As a result the CPU was identified by the Linux kernel as running at 1.5 Ghz. Under those conditions, I installed clockspeed and it ran extremely well: time was within 25 ms after a week or two. After discovering my error, I shut down, set the bus-speed dip switch to 133 Mhz, and rebooted, and the kernel began recognizing the CPU as 2Ghz. As soon as I did that, clockspeed stopped working: I restarted it and gave it an adjustment, according to the instructions in the INSTALL file, but after 4-5 hours I noticed that the clock was over 3 seconds off. Since then I've disabled clockspeed and used clockadd to set the time; there was still substantial clock drift: it's been 17 hours, and the clock is now 9.06 seconds off. Is there something elementary I'm doing wrong? Is there some reason that clockspeed would work fine at 1.5Ghz, but would fail for the same system running 33% faster? (I'm positive that clockspeed was working at the slower speed; on one occasion I started clockspeed with over 1 second of error in my clock, and I could see the time quickly converge on the correct time after giving clockspeed an adjustment.) Thanks! Len. -- You're repeating the same old ``forks are bad and execs are disastrous'' litany without _profiling_ where your time is actually going. -- Dan Bernstein