I have a Foxconn motherboard with Phoenix-Award BIOS and Cedar Mill P4 (Hyperthreading PAE single core) RAID1 system with 11.0 first installed, later 11.2 added, and still later with 11.4 added, now with 3.3.4-1-desktop, giving me three boot choices. 11.4 has been running fine many months, except that /proc/cpuinfo has been reporting my 3.4GHz CPU running at 2400MHz for as long as I can remember, back to when I had a cooling problem and purposely underclocked to keep the temperature down. So today, long after solving the cooling problem, I finally tried to get the CPU speed where it belongs. Eventually I just did a "load optimized defaults" in the BIOS, with a resulting CPU speed within a few MHz of 3400. However, that resulted in the system clock going crazy fast, gaining at least 1.5 minutes every 10 minutes. I Googled and found that Spread Spectrum enabled can cause this, so I went back to the BIOS. I found a way to turn Spread Spectrum off, but that system clock fix brought the CPU speed back down to 2400MHz. The BIOS Spread Spectrum setting has limited access. To reach it, "Fox Intelligent Stepping" needs to be set to "manual", but it is the manual setting that produces 2400MHz CPU speed. I finally figured out that the Spread Spectrum setting appears to remain wherever set while accessible even after restoring to one of the automatic settings that denies access to it. In order to write this, I needed to reboot into the BIOS again to get the right terms. On next boot, I decided to remove CPUFREQ=off from cmdline to see what difference it might make, and the clock error was back. I have no recollection what caused me to include it, but I've had it there at least as long as 11.4 has been installed. Google also said try adding clock=tsc, so next I tried that instead of CPUFREQ=off, also resulting in speedy clock. Google also suggested clock=hpet, which seems to be a fix I'll have to confirm after some sleep. Google said delete /etc/adjtime if the clock runs slightly fast or slow, so I've done that 3-4 times over these boots. I've been using puters for decades, and have never had clock trouble anything like this. I found http://susefaq.sourceforge.net/howto/time.html, but it's 8 years old, not particularly easy to understand, and I have to wonder if kernel evolution has changed things anyway. How common is this kind of clock error? Anyone else here run into this, or know why it ever happens? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org