You are not logged in.
Hi,
And Thank YOU ! all is working perfectly with your deb file.
++
Offline
Has anyone tried this on a 701 4G ?
TIA
Offline
Or 1101ha?
Offline
works great on my 1000he! long live eee-control!
Offline
what command would bring up eee contol's sensors sub-app? id like to put in startup applications and/or make a shortcut.
Offline
It pulls its info from lm-sensors. Install it and type in console 'sensors' (without quotes). I currently trying to figure out how to pull that from sensors with other app (being dumb is not easy, you know
)
Offline
oh, i see. i tried xsensors (lm sensors + gui) with no detect when i used sudo sensors-detect. ill try it again... if thats the case, then i already know what to do.
Offline
It doesn't work with 1101ha model.
after /etc/init.d/eee-control start:
"You are not using a supported Eee PC model. Continuing anyway with autodetection."
and eee-control-tray says:
"Error communicating with eee-control-daemon: The name org.eee.Eee was not provided by any .service files"
Offline
Not sure if this is a problem with the modified version for 9.10 or just me being new to this app, but I had set fan to smart control last night and everything seemed fine. I booted up this morning and the fan didn't spin up, which was fine, it wasn't hot yet, but after continued use, temp was up about 60C and still no fan. I disabled smart control and it spun up and cooled the cpu, reenabling smart control and the fan still spins. So would it have kicked on at a little higher temp, like 65C or is this a possible problem between eee-control and 9.10?
Offline
danamlund wrote:
I repackaging the deb file to work with karmic.
http://danamlund.dk/eee-control/eee-control.html
As mentioned, this was done by adding and removing stuff i didn't quite understand until it seemed to work.
thank you so much danamlund, i installed your package on a 900 with kubuntu 9.10, its working perfectly.
Offline
yup, lm sensors works! thanks!
Offline
goomba wrote:
Not sure if this is a problem with the modified version for 9.10 or just me being new to this app, but I had set fan to smart control last night and everything seemed fine. I booted up this morning and the fan didn't spin up, which was fine, it wasn't hot yet, but after continued use, temp was up about 60C and still no fan. I disabled smart control and it spun up and cooled the cpu, reenabling smart control and the fan still spins. So would it have kicked on at a little higher temp, like 65C or is this a possible problem between eee-control and 9.10?
Doesn't matter now, updated my 1005HA to the latest bios and it killed eee-control. Tried a clean install of eee-control and no luck. Here is the debug output from eee-control-daemon. If anyone has any ideas, I'd appreciate it.
rfkill: testing /sys/class/rfkill/rfkill0
rfkill: found bluetooth
rfkill: testing /sys/class/rfkill/rfkill1
rfkill: found wifi
rfkill: testing /sys/class/rfkill/rfkill2
rfkill: found bluetooth
rfkill: testing /sys/class/rfkill/rfkill3
rfkill: found wifi
Traceback (most recent call last):
File "/usr/bin/eee-control-daemon", line 124, in <module>
eee_model = EeeControl.actions.EeeActions(bus, manu, model, acpi_base, brn_path, bt_path, wlan_path, hwkey_control)
File "/usr/lib/python2.6/dist-packages/EeeControl/actions.py", line 169, in __init__
self.brn_state = self.get_brightness() + 0x20
File "/usr/lib/python2.6/dist-packages/EeeControl/actions.py", line 251, in get_brightness
brn = int(l.strip()) + 0x20
ValueError: invalid literal for int() with base 10: ''
Offline
I installed the deb posted by danamlund on my 701 with regular 9.10. It won't let me adjust the cpu speed, and when I tried to un-install it, dpkg gave an error and couldn't remove it. I had to re-install the OS so I could run at full speed from my bios again.
Offline
@creelingmee your error was probably due to the eee-control settings using SHE by default, a simple fix that didnt involve reinstalling the OS would have been to simply go into the eee-control.conf file and change the default scaling mode from SHE to direct-io, i couldnt change the cpu speed on my 900, and when i changed it to direct-io, i could adjust the cpu speed.
if you wish to try eee-control again, and adjust the eee-control.conf file, simply reinstall it and go to the terminal and type in:
sudo gedit /etc/eee-control.conf
then look for the part that says:
fsb method: she
and change it to say
fsb method: direct-io
then you should be able to scale the cpu.
Offline
I've updated my repackaged eee-control so removing works.
to remove the package if you downloaded it before today you have to comment out line 16 of /var/lib/dpkg/info/eee-control.prerm
http://danamlund.dk/eee-control/eee-control.html
Offline
goomba wrote:
Doesn't matter now, updated my 1005HA to the latest bios and it killed eee-control. Tried a clean install of eee-control and no luck. Here is the debug output from eee-control-daemon. If anyone has any ideas, I'd appreciate it.
rfkill: testing /sys/class/rfkill/rfkill0
rfkill: found bluetooth
rfkill: testing /sys/class/rfkill/rfkill1
rfkill: found wifi
rfkill: testing /sys/class/rfkill/rfkill2
rfkill: found bluetooth
rfkill: testing /sys/class/rfkill/rfkill3
rfkill: found wifi
Traceback (most recent call last):
File "/usr/bin/eee-control-daemon", line 124, in <module>
eee_model = EeeControl.actions.EeeActions(bus, manu, model, acpi_base, brn_path, bt_path, wlan_path, hwkey_control)
File "/usr/lib/python2.6/dist-packages/EeeControl/actions.py", line 169, in __init__
self.brn_state = self.get_brightness() + 0x20
File "/usr/lib/python2.6/dist-packages/EeeControl/actions.py", line 251, in get_brightness
brn = int(l.strip()) + 0x20
ValueError: invalid literal for int() with base 10: ''
*edit*
Scratch what I wrote 10 minutes ago, it seems that the latest 1005 bios has changed the acpi settings... /proc/acpi/asus doesn't appear to exist anymore, and /sys/devices/platform/eeepc/ seems to be missing some things, like the brightness info. Looks like I might have to try rolling back to an earlier bios, if I can. If anyone has an other ideas, thanks in advance.
Last edited by goomba (2009-11-02 9:00:24 pm)
Offline
eee-contol doesn't work with bioses 0801, 0905 and 1102
I had exactly the same problem. I appears with later bioses 0801, 0905 and 1102. Going back to 0601 made it work again. Saw same problem also in http://aur.archlinux.org/packages.php?ID=22076
any hope for fixing?
Offline
Yeah, a bit disappointing. I rolled back to the 1005HA 0703 bios and its working again.
Offline
goomba & mkonline
Check the brightness location:
find /sys/ | grep brightness
If the result is /sys/devices/virtual/backlight/acpi_video0/brightness, then edit /usr/bin/eee-control-daemon line 85 and 86 from:
elif os.path.exists("/sys/class/backlight/eeepc/brightness"):
brn_path = "/sys/class/backlight/eeepc/brightness"to:
elif os.path.exists("/sys/class/backlight/acpi_video0/brightness"):
brn_path = "/sys/class/backlight/acpi_video0/brightness"Good luck ![]()
Offline
gajm, thank you. I'll try that later this afternoon and see if I can't get it working.
*edit*
Thank you! That did it. Glad to be back on a newer bios that supposed to have better battery life.
Last edited by goomba (2009-11-03 4:17:05 pm)
Offline
Thank you :-)
it works fine with Bios 1102.
@goomba: Battery life is not better than with 0601 (powertop even show 0.1 watt more)
Offline
I had a terrible crash on my 701, just when I tried to set the scaling on performance.
My bios version is 1302.
Offline
@mkonline Interesting, I'm just going by the comments on the bios download page.
Offline
This newly packaged version works brilliantly with my 901 on Karmic using Bios 2103.
Many thanks danamlund!
It works so much more smoothly for me than eee-acpi-utilities and the accompanying tray applet. This would (even on Jaunty) mess up and re-suspend my machine after waking from sleep after it set the performance mode, which was a bit of an annoyance - plus the performance mode switching was always buggy and also delayed displaying the notifications for anything for a long time sometimes - then kept them on the screen for much too long.
Now everything is snappy again.
However, there is one thing I wish eee-control could do that Fewt's ACPI utilities did (which it probably could fairly simply but I'm no programmer) - this is to switch the CPU frequency as well as set the voltages (or whatever it does when changing performance). I find that even if I set it to "high" performance, that the CPU freq. is still set to "On Demand" which means that some flash-heavy websites and playing high-bitrate video files stutter unless I manually force the CPU freq. to "Performance" or 1.60Ghz using the "CPU Frequency Scaling Monitor" applet.
Fewt's app used to do this (although not all the time - but mostly it would get it right on my 901).
Is there an easy way to make eee-control do this too?
Last edited by Rod Hull (2009-11-04 11:28:57 am)
Offline
Rod Hull wrote:
This would (even on Jaunty) mess up and re-suspend my machine after waking from sleep after it set the performance mode, which was a bit of an annoyance - plus the performance mode switching was always buggy and also delayed displaying the notifications for anything for a long time sometimes - then kept them on the screen for much too long.
!!LOL!! Well enjoy eee-control, because users like you with no concept of why they have problems like you claim are why I no longer give a ****. For the record, my utils had never and would never have caused a suspend action, and the notifications were set to time out after 1.5 seconds which karmic and jaunty both ignored but hey what the hell do I know, I only wrote them.![]()
Offline