does it really work for you ? Yes, the variables are displayed, but they do no alter the cpu clock freq., at least for me.only direct-io works for FSB tweaking, 3 setups are available high/normal/powersave.
The cpu frequency read by acpitools wouldn't change, that's a known issue. It seems FSB changes, it saves power, reduces cpu performance, but the frequency is not read differently, that's stated here by Greg, the dev:gringo wrote:does it really work for you ? Yes, the variables are displayed, but they do no alter the cpu clock freq., at least for me.only direct-io works for FSB tweaking, 3 setups are available high/normal/powersave.
SHE is supposed to work out of the box with kernel >=2.6.30 but it doesn´t here, i tried contacting upstream but got no response till now.
Here i've set up my eeepc to use the conservative governor, it works with eee-control in parallel i suppose, it's built in the kernel with performance too, it's somehow automagically chosen by the kernel and is the recommended governor for laptops. It scales my acpi-shown frequency from 800 to 1600 mhz. I've kind of tested it by letting conky do the math and estimate my battery remaning life: when idle, running at 800mhz and with eee-control powesave setup it is supposed to last about 7 hours, which is that battery life stated as maximum by Asus.I switched to high performance/powersave mode, but the CPU frequency scaling applet still shows the same frequencies and governor. Why?
While eee-control adjusts the FSB, the CPU frequency scaling applet is a frontend for cpufreq. FSB and cpufreq are two separate things. Furthermore, cpufreq cannot detect the FSB change and therefore still will display the original frequencies, even with the FSB underclocked/overclocked.
Known Issues
Under some circumstances, I2C/SMBus is not available because the BIOS "hides" the controller. In this case "i2c-dev" performance control cannot be used.
sure, i know, im not talking about cpufreq : if i set powersave mode in eee-control the cpu should run in powersave mode, IOW, reducing FSB which will bring down cpu clock. If thats the case it doesnt work here, or at least /proc/cpuinfo always shows the same cpu clock speed.The cpu frequency read by acpitools wouldn't change, that's a known issue. It seems FSB changes, it saves power, reduces cpu performance, but the frequency is not read differently, that's stated here by Greg, the dev:
sure, but for me that goes against for what i understand for "powersave mode"However, you can reduce fsb and raise the multiplier

Code: Select all
cp /opt/portage/app-misc/eee-control/eee-control-0.9.3.ebuild /opt/portage/app-misc/eee-control/eee-control-0.9.4.ebuild
ebuild /opt/portage/app-misc/eee-control/eee-control-0.9.4.ebuild digestI guess you're not trying that hard? It's nice that you've put up the website, but please do an Update. The patches are here in this thread. Thank You!lxg wrote:I have created an ebuild for this software, and I'm trying to keep up with the rapid development by trying new versions and creating up-to-date ebuilds.

Code: Select all
eee-control-query set_fsb string:powersave
eee-control-query set_fsb string:full
eee-control-query get_fsbDo you know what apps you are currently running?npc wrote:Again i was missing stuff. I messed around with cpufreqd and other apps but none of them really impressed me. Besides that, xorg would not see some of the extra hotkeys that the eeepc has. So i tried eee-control one last time and to my surprise it works!
I was prolly missing acpi-freqd and fan kernel modules and maybe something else.
Anyways, only direct-io works for FSB tweaking, 3 setups are available high/normal/powersave. My wifi card is well seen because i overrid the default modules and device in eee-control.conf. All hotkeys work flawlessly, also the fan controlling feature is okay too.
Any ideas how to solve this?ERROR:dbus.proxies:Introspect error on :1.10:/org/eee/Eee/EeePc: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.DBus.Introspectable" member "Introspect" error name "(unset)" destination ":1.10")
Fehler bei er Kommunikation mit eee-control-daemon: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.eee.Eee" member "set_fan_control" error name "(unset)" destination ":1.10")

I think you are missing the part about direct-io.npc wrote:Anyways, only direct-io works for FSB tweaking, 3 setups are available high/normal/powersave
Code: Select all
fsb-method: direct-ioCode: Select all
/usr/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:40: RuntimeWarning: tp_compare didn't return -1 or -2 for exception
from gtk import _gtk
ImportError: could not import gio
ImportError: could not import gio
ImportError: cannot import name Widget from gtk
Traceback (most recent call last):
File "/usr/bin/eee-control-tray", line 20, in <module>
import EeeControl.tray
File "/usr/lib/python2.6/site-packages/EeeControl/tray.py", line 522, in <module>
class EeeControlSensors(gtk.Dialog):
AttributeError: 'module' object has no attribute 'Dialog'Just posting here to confirm that the staging driver from 2.6.31-r5 is working for me. I had been trying to get the 2.2.0.0 version of the driver from Ralink's web site to work, but it wouldn't get an IP address from my router.gringo wrote:just FYI : there is a driver in the kernel that supports the ralink 2860 chip under "staging drivers".
i´ve been using this one since i have my eeepc and it works just fine afaict.
cheers
just as a side note : the driver in the staging tree actually is the driver from ralink but somewhat refactored and reworked, mainly to fit more nicely into the kernel coding style rules.Just posting here to confirm that the staging driver from 2.6.31-r5 is working for me. I had been trying to get the 2.2.0.0 version of the driver from Ralink's web site to work, but it wouldn't get an IP address from my router.