I'm about to do a clean install (problems with my drive) and this time I want to remove fewt's stuff and just go back to what Jaunty comes with.
My processor doesn't support scaling and the current set up strangles my processor at boot. Switching wireless on/off etc. doesn't get used so I won't miss them.

Is it a case of removing eeepc-acpi-utilities and eeepc-tray and then adding eeepc-acpi-scripts?

This will remove a lot of background stuff though that you may really miss like setting laptop mode, changing your kernel options on battery, etc.

I wouldn't recommend removing it.

In that case, how do I disable cpu scaling/strangling altogether?

Set on battery, and on power modes to "performance" in /etc/default/eeepc-acpi.local.

MODE_AC="performance"
MODE_BAT="performance"

If you want to stop scaling completely and you have the Celeron, just stop loading p4-clockmod in /etc/modules.

There is no performance gain from removing it though (I've tested all possible combinations with geekbench).

You can force scale modes and minimum thresholds using /etc/sysfs.conf, '/etc/acpi/eeepc-cpu-control.sh debug' will tell you what scale modes are available.

When I return from vacation I'll write a how-to.

But that doesn't exist.

So, I uninstalled eeepc-acpi-utilities and eeepc-tray.
However, when I rebooted, the machine was running very slow.
Then I put the cpu frequency applet into the panel which enables me to choose my processor speed and have it report correctly. Set it to 900 and I'm away.

The advantage for me here is that the EeePC Tray utility wasn't being entirely truthful with me when it came to my processor speed. It told me that I was running on Performance when I wasn't and then it wouldn't remember my settings.

As I said previously, my Celeron cpu doesn't support scaling, but it can be throttled. However, from what I have read, throttling does not save power in the same way scaling does. Therefore, I don't need scaling. I don't need throttling either.
Eeebuntu 2.0 didn't have these scripts built in and I never installed any of them. This was due to seeing endless posts on forums from users having niggling little issues with them. So I didn't bother, thinking, I'll give it some time and then decide whether or not to use them.
And in the meantime, my machine worked just as I like it.
I really have no need of switching my wireless or webcam on and off at will, resolution cycling and the like. My machine sits next to the sofa, plugged in and occasionally I take it out to the pub. Bit like the missus, really...

Apologies if this all sounds a bit negative. I'm just getting a bit hacked off with looking through wikis and forum posts and trying to solve this. I'm not an expert, just a regular user. I've learned a lot in the five years since abandoning Microsoft products and I get a thrill out of piecing stuff together in an effort to find an answer. But this, after loving Base 2.0 is irritating the hell out of me. I'll leave it as it is for now and I'll keep an eye on the forums for any progress and/or success stories.

I know that these scripts are very, very useful for some users and I appreciate and applaud the hard work that has gone into them.

Thank you.

You set the throttling on full.



This is from your FSB misreporting, I can fix the bug in a future release. It only occurs when the clock generator isn't read properly by the kernel module.



What you've read was wrong, I've proven with a kill-a-watt device (it measures power output from the wall socket) that you can save 3-5 watts or even more using it. I've managed to get my Celeron Eee down to 8.9 Watts. It runs at 22 Watts full throttle, that's a difference of several hours on battery.