cat /proc/cpuinfo on AMD3000+
 

I get back that my cpu is running at 1000mhz - it should be 1800! Any idea's?

sounds like your clock rate is not set correctly in your bios...

Ah yes but windows correctly identifies it as 1800mhz....so it's not a BIOS thing. Any other idea's?

Is this in a desktop or laptop? Could be some kind of scaling in place to save power. It's not like a CPU runs of drivers from an operating system so not much could have changed between Windows and linux. Unless linux actually isn't reporting the correct figures but that would just be weird. It gets everything right on my AMD processor.

It's a desktop. By the way I really like your adesklet stuff. Do you know if it would be possible to convert mac dashboard widgets to adesklets?

Thanks

Well since it's in a desktop then I'm out. Might help to check to see if cpufreqd or powernowd are running but I don't think they would be.

Not without rewriting them, no. To make a long story short, Dashboard widgets are drawn using Safari and the <canvas> tag. You can Google that to get more info. Firefox supports the <canvas> tag as well and Sylvain (adesklets developer) put together a little test which worked in almost the same way as Dashboard a while ago but hasn't done any more with it.

The good news, KDE4 will have support for Dashboard widgets with no modifications. See here for a little more info. It seems that he had to reimplement <canvas> himself in the KHTML engine which is a shame because last time I checked Safari used KHTML as well so the work was already done, just not available :(

how do you know that windows thinkgs it's 1800 mhz? just curious...

as windows will report that without really knowing it.....

both windows (system properties) and dxdiag report it at 1800

I guess the final question is do you notice a slow down between operating systems? 800MHz is a lot and would be noticable I'd think, if linux isn't obviously slower then perhaps it's reporting the wrong figure and you don't need to worry about it. Maybe you could try a live CD or something to see if they both report 1000MHz or just your install, could be a buggy kernel version or something in the distros own patchset that some apply.