Processor Speed 6.0 Beta 3
I have a problem with 6.0 and I hope that someone can help. I have a new desktop system using a Nvidia Geforce 6150 motherboard and an Athlon64 3000.
Both 6.0 Beta2 and Beta3 install and work fine with this hardware. I am currently using Beta-3. Initially the processor is detected and works fine per KInfocenter and is detected as:
Athlon 64 Processor 3000+
CPU MHZ = 1808.749
Bogomips = 3620.38
After a couple of days the system is slower and KInfocenter reports:
Athlon 64 Processor 3000+
CPU MHZ = 1004.841
Bogomips = 2011.30
I have not updated from the repositories except for a few applications I have installed.
I tried installing again and it worked fine for a few days and then the same thing happened.
Any ideas? I could have saved money and bought a slower processor! 
Processor Speed 6.0 Beta
I did a little more googling and concluded that this is the processor throttling back. I installed powernowd and the processor speed came back. Don't know it that was because of the installation or the cpu load reached a certain level. It held the higher speed through the night, so I'll see what happens.

Processor Speed 6.0 Beta
Yep thats what its for , generally needed for laptops i think , dont see mutch need on desktops . Interesting i didnt know it worked on amd64 chips...
jim
Processor Speed 6.0 Beta
It works and it is aggravating if you need the power but I suppose it saves energy.

KPowersave replaces Powernow
I think you will find that KPowersave has superceeded Powenow (read the info in Synaptic for Kpowersave)- and will be on the default setting of throttle down when idle - it may also be installed and enabled by default in Mepis 6 beta3 - which is good - you wouldn't sit in your car while parked with the engine revving hard would you?? (well i know some people do - but thats another story!!)




Any ideas?
Try running the live cd as root and moving the /etc/rc.local file into your root dir. for safe keeping . Worked for a little problem i had BUT my rig isnt a athlon64 , ergo move it. might have a look at the bios messages when booting too.
jim