Are you sure it really affects the FSB ? It can easily be a display problem. Many tools related to C-n-Q assume the FSB is at 200, and will display a wrong (lower in your case) frequency, but this does not affect the CPU.

Widan: you're right on this point. /proc/cpuinfo display a bad CPU speed but actually the CPU speed is really higher as some benchmarks could confirm it and there is something to see it easily: the bogomips !

So for my AMD64 3800+ @2Ghz , i have 4000 bogomips and with a FSB overclocked at 250, i get 5000 bogomips and the indication of bogomips is acurate when the CPU speed is not. So it's an easy way to check really the CPU frequency when you use C-n-Q and overclocked CPU.

So now I'm really amazed about my cpu that run overclocked, undervolted with cool'n'quiet ...

I get an easy 2.50Ghz @1.35v for the high step
and an 1.25Ghz @1.10v for low step.

I need just to determine the minimum voltage for the intermediate step at 2.25Ghz.

That's great to have an ~4800+ for the price and voltage of a 3800+ using even the C-n-Q now

And remember that is not real frequency, but stock ones, check your bogomips to be sure !

Think to check you voltages and tempeartures with lm-sensors or mbmon.
Think to check your logs for MCE (Machine Check Exception for undervolt problems).
And burn with two separate process of mprime -t (launched from differents copys of prime directory to not have temp data corruption) to check the overclock.

Are you guys able to use undervolting with latest kernels .21 for e.g.? I can't access the sysfs interface, everytime it hangs.

What kernel config do you use? There were some changes about the tables in it right?_________________Workstation: 5.1 SurroundSound, LIRC remote control; Laptop [IBM-T43]: patched sources, s2disk/ram, fingerprint sensor

It may be a stupid question, but does anyone have an ebuild for this patches?
I really don't think I'd like to learn play with kernel source on my "production" machine.

By the way - is there a simple way to add more steps? Now I have 1000 1800 2000, I'd like (for example) stepping by 200 MHz from 400~600 up to 2000. 400MHz is truly all I need and more whilst my machine is in idle state, waiting in case I'll need it remotely.

I've unmerged and emerged sources, applied the patch again, and that time it worked. It had to be a stupid mistake on some point..._________________"I just have to run faster than the slowest party member"

I don't exactly know, for which version I made the patch, so I named it "-git", but it does apply with some fuzz to current 2.6.24 versions.
I changed the -v2 to -v3, just to make clear (for me and others), that this patch won't apply for earlier versions.
I didn't change the patch itself.

If you need support, post at least the kernel version, cpu & motherboard versions and warnings from patching process.
For now, all I can tell is "works for me, you have problem" - but you know that already ;D_________________"I just have to run faster than the slowest party member"