How do I set the scale to 10?

I also ran the diagnostic from the wiki in your link. I have emailed the results to you, When I ran the scaletest.sh script it started off ok then crashed.

Put FSB_SCALE="10" in /etc/default/eeepc-acpi.local.

Problem definately in the kernel.. if i update and boot the .12-netbook kernel, it crashes when i select anything in CPU settings, if i then use grub menu to boot the .11-generic kernel, every setting works fine, no crashing..

try testing our the 29 netbook kernel in the array repo if you can and see if that fixes the issue.... we are probably going to be switching to this kernel once we have finished testing afew more things

Yeah done that, seems to have done the trick, does setting the scale to 10 mean I am getting less effect from scaling back the CPU? Also, will the tray applet now remember the last setting used when I switch off the unit?

Where do i find this kernel?

open synaptic and go to the "origin" section on the left side..... just select the array.org kernel and install the 29 numbered version

Im not so savvy in linux yet, still work in process on the learning.. hehe.. but i selected the linux-image-2.9.29-1, linux-headers 2.6.29-1-netbook and linux-image-2.6.29-1-netbook, there was a -rt real time version there aswell, but i left that alone. It installed fine, and the rebooting went well with no issues.. now, how do i remove the 2.6.28-12-netbook kernel? i guess its just wasting space now.. Which packages are safe to remove on that?

As for the ACPI, its still crashing same as the 2.6.28-12-netbook kernel.... Could it be the netbook kernel? where can i find a 2.6.29-1-generic kernel to test? Might it be that CPU scaling is not available in the -generic kernel? or that it was not implemented in the 2.6.28-11 kernel? just shooting some ideas here.. As for me, the 2.6.28-11-generic kernel works fine in cpu scaling, either that is because its a generic kernel, and the generic kernel either does not contain cpu scaling or it contains support for the 901 cpu scaling, or it is cause its older and something change from 2.6.28-11 to 2.6.28-12 that messed up the cpu scaling, or simply that it was not implemented until 2.6.28-12..

I installed a tray applet to show the cpu freq, and tried changing settings on the eeepc tray, and guess what, it does nothing.. cpu freq is the same on all settings when i run the 2.6.28.11-generic kernel.. So, it seems cpu scaling isnt implemented at all, or atleast not working at all in the 2.6.28-11-generic, but it does work in the other kernels, only that it crashes the computer..

It's probably still working, it changes your bus speed by altering the clock generator controls so the kernel doesn't see it.

If you have an Atom though it should also change your CPU speeds.

yeah, its an atom.. I see the icon jumping between 800mhz, to 1,6ghz as normal, but i doesnt make any difference of which setting i put on the eeepc tray... setting fsb_scale to 10 didnt work for me either, as for now, to be able to run the 12-netbook kernel, i set disable_cpu_scaling to 1.

Ill be helpful to gather any type of data on this if you need, i got multiboot into windows xp, windows 7 and eeebuntu, so i can gather info from all of those operating systems.. I even have a license on Mac OS X, from my mac mini, so ill be installing mac os on this also.. shhhhhh, dont tell apple.. hehe.. Allthough, in norway, this isnt illegal, even if it does violate EULA..

I've also been having the crash on suspend problem and setting FSB_SCALE to 10 seems to have solved it. Question: should I just leave it at 10? I don't mind sacrificing performance, but don't want to hurt the little eee 1000.



[I just installed eebuntu NBR this weekend and I must say it has been a real chore to get it going, even though I've used unix/linux for many many years. I still can't find eeeconfigure on my system...But I will persevere as so much nicer than xandros.]

There is no eeeconfigure.

I must be going mad then. What about viewforum.php?f=32 ?

eeeconfigure was present in version 2.0 and we have removed it from 3.0 while it undergoes a major functionality and use overhaul.... it will be appearing in the next few weeks possibly under a new name too