Eee PC ACPI Utilities / Eeebuntu model support thread

platojones · **Joined:** Wed Mar 25, 2009 1:52 am **Posts:** 27

fewt wrote:

platojones wrote:

Hey fewt,

A bug report for ya...using the latest acpi utils...

I've noticed that the cpu mode doesn't go to on-demand (though I have it set in the acpi config file) when I boot up on battery power. It does work if I boot up on AC then remove the power plug. But whenever I start up on batter, it's always in high-performance mode unless I use the tray app to manually set it to on-demand.

Thanks.

I'll look into this.

I just updated to the lastest version and this is fixed! Great work.

alacast · **Joined:** Sun Mar 01, 2009 3:36 pm **Posts:** 10

Just installed the ACPI utilities and the tray icon onto my 1000HE. I frequently switch between my netbook screen and external monitors, and consequently use the FN key monitor switching functionality all the time. Unfortunately Linux doesn't do this effectively at all right now, which is why I've been exclusively on my Windows partition. I had hoped this program would help me get out, but no dice. Here's a suite of bugs for you:

First, as a GUI design issue, right clicking on the tray icon leaves my pointer right on top of the "Exit EEE PC Tray" option, which accidentally gets clicked about 70% of the time unless I'm very careful. This is sad.

"Screen Resolution Cycle" goes to the lowest resolution, but then I can't cycle out of it. I have to manually get to a higher resolution.

"Rotate Screen" does nothing other than displaying the message saying the screen is inverted, even though it's not.

FN+F8 basically doesn't work. I would expect it to toggle between external monitor, netbook monitor, and maybe extend and clone options. Right now it just turns off and on the external, without turning on the netbook screen. Additionally, when it turns back on the external monitor it's on a different resolution than when it left, which is higher resolution (possibly higher than the monitor is capable of displaying correctly) and shifted up past the top of the screen.

FN+F8 frequently deactivates sound as well. I think might come from the functionality in the baseline Eeebuntu, since this combination is mismapped to volume on/off.

Turning touchpad on/off doesn't work. "Unenable to enable touchpad; Ensure xorg.conf is properly configured." Additionally, error message screens like this display for a little too little time.

Cannot turn on "Super High Performance" because the asus_eee module isn't found. What is this module? I have no idea.

Alright. Guess I need to run back to Windows now until this all gets sorted. I really miss my Amarok and Yuake :cry:

fewt · **Posted:** Mon Apr 06, 2009 7:02 pm

alacast wrote:

Just installed the ACPI utilities and the tray icon onto my 1000HE. I frequently switch between my netbook screen and external monitors, and consequently use the FN key monitor switching functionality all the time. Unfortunately Linux doesn't do this effectively at all right now, which is why I've been exclusively on my Windows partition. I had hoped this program would help me get out, but no dice. Here's a suite of bugs for you:

First, as a GUI design issue, right clicking on the tray icon leaves my pointer right on top of the "Exit EEE PC Tray" option, which accidentally gets clicked about 70% of the time unless I'm very careful. This is sad.

I don't see this behavior, when I right click the tray icon the mouse is over the Webcam enable (see image). If you would like to assist with the GUI design, I accept patches. :-D

"Screen Resolution Cycle" goes to the lowest resolution, but then I can't cycle out of it. I have to manually get to a higher resolution.

This is managed by xrandr. I build an array of available resolutions and cycle through them. If you want to get back to the normal resolution, keep cycling.

Quote:

"Rotate Screen" does nothing other than displaying the message saying the screen is inverted, even though it's not.

Again, this is a call to xrandr, if it isn't working check that xrandr is working correctly.

Quote:

FN+F8 basically doesn't work. I would expect it to toggle between external monitor, netbook monitor, and maybe extend and clone options. Right now it just turns off and on the external, without turning on the netbook screen. Additionally, when it turns back on the external monitor it's on a different resolution than when it left, which is higher resolution (possibly higher than the monitor is capable of displaying correctly) and shifted up past the top of the screen.

It turns your external monitor on and off, so it is working. If you would like added functionality I'll gladly look into it, but this isn't a bug.

Quote:

FN+F8 frequently deactivates sound as well. I think might come from the functionality in the baseline Eeebuntu, since this combination is mismapped to volume on/off.

This is a scan code issue, enable the optoin to display key codes, and resolve the conflict in /etc/default/eeepc-acpi.

Quote:

Turning touchpad on/off doesn't work. "Unenable to enable touchpad; Ensure xorg.conf is properly configured." Additionally, error message screens like this display for a little too little time.

This is an xorg misconfiguration, there is tons of documentation on how to set this up properly in the forum. Updating the notification code to add delays to error messages is on my list of features to add.

Quote:

Cannot turn on "Super High Performance" because the asus_eee module isn't found. What is this module? I have no idea.

When you install eeepc-acpi-utilities it suggests installing asus-eee-dkms.

Quote:

Alright. Guess I need to run back to Windows now until this all gets sorted. I really miss my Amarok and Yuake :cry:

Alternately, I accept patches. :-D

t0psy · **Joined:** Fri Dec 26, 2008 2:45 pm **Posts:** 5

Model Eeepc 1000H, Jaunty.
Very high success rate on the ACPI Utilities.

Problems are :-

1.Bluetooth does not toggle the notification says enabled regarless of state. The bluetooth state is determined by the bios selection.

2. Wifi Toggle, turns off ok but toggle on lights the radio led but there is no connection.
Adding "pciehp.pciehp_force=1 pciehp.pciehp_poll_mode=1" to the kernel fixes the toggle but gives a text error on bootup "cant hot add device etc."

3. No graphical display on sound mute, and sound up and down although adjusts ok.

4. No graphical display on brightness adjust.

Disable touchpad worked after I enabled SHMConfig.

I followed this guide.
Warning it has security issues on muli user systems. (How many EeePCs are multiuser?)
https://help.ubuntu.com/community/Synap ... #shmconfig
I have pasted the guide below.

Open a terminal

gksudo gedit /etc/hal/fdi/policy/shmconfig.

Add the following, save and reboot

<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="input.x11_driver" string="synaptics">
<merge key="input.x11_options.SHMConfig" type="string">True</merge>
</match>
</device>
</deviceinfo>

BTW the tray icon loads briefly then dissapears when using the Tray Icon Utility Program.

fewt · **Posted:** Mon Apr 06, 2009 9:47 pm

t0psy wrote:

Model Eeepc 1000H, Jaunty.
Very high success rate on the ACPI Utilities.

Problems are :-

Disable touchpad whilst typing, no disable.

Bluetooth does not enable although the notification says enabled.

Wifi Toggle, turns off ok but toggle on lights the radio led but there is no connection.
Adding "pciehp.pciehp_force=1 pciehp.pciehp_poll_mode=1" to the kernel fixes the toggle but gives a text error on bootup "cant hot add device etc."

No graphical display on sound mute, and sound up and down although adjusts ok.

No graphical display on brightness adjust.

The tray icon loads briefly then dissapears.

Thanks for the feedback. I've been working on Jaunty support for a while now. Touchpad is managed outside of the tools for now, there are a few threads on it.

Bluetooth is a bug in the Ubuntu kernel. I'm building 2.6.29 and packaging it to see if it resolves the issue.

I don't have OSDs for brightness, or volume. I wanted it to be more seemless, didn't see the value in writing a lot of code to present something on the screen that is already fed back in other ways (screen brightens or darkens, volume raises and lowers). I can revisit this though if enough people need it.

There is a eeepc-tray in SVN compiled for Jaunty. There appears to be a bug in mono (I need to report it) that causes the applet to sig 11 whenever the timer or thread wakes up and updates the tooltip. It seems to only occur on the tooltip update, though I haven't proven that out 100% yet. Try replacing the EeePC Tray in /usr/bin with this one (renaming it): http://eeepc-acpi-util.svn.sourceforge. ... ynamic.exe

jazzeee · **Posted:** Mon Apr 06, 2009 10:39 pm

Hi - I was advised to post my problem in this thread.

I installed eeepc-acpi-utilities, however, some things don't work. The touchpad toggle complains it can't do it's job (blames xorg config which I have never touched since I installed eeebuntu - unless one of the eee configure scripts changed it).

The main problem however, the Wifi toggle, locks up the machine SOLID as soon as the wifi light goes out. Had to force power off to get the machine working. I tried it twice, same both times.

Also, boot time is greatly increased and the boot graphic falls back to text mode (because of the crash?).

My machine is a 701SD.

platojones · **Joined:** Wed Mar 25, 2009 1:52 am **Posts:** 27

Quote:

I don't have OSDs for brightness, or volume. I wanted it to be more seemless, didn't see the value in writing a lot of code to present something on the screen that is already fed back in other ways (screen brightens or darkens, volume raises and lowers). I can revisit this though if enough people need it.

Interesting....I have a 1000 HE and the OSD shows up for volume, just not for brightness. I wonder if this could be a hardware difference between the 1000 H and 1000 HE.

TRiPgod · **Posted:** Mon Apr 06, 2009 11:05 pm

platojones wrote:

Interesting....I have a 1000 HE and the OSD shows up for volume, just not for brightness. I wonder if this could be a hardware difference between the 1000 H and 1000 HE.

I think this is an ubuntu 8.10 thing. Ever since I installed intrepid, I lost the OSD for brightness. Other people claim this same thing on forums. I just don't care enough to research why. But it's not an H - HE hardware issue.

fewt · **Posted:** Mon Apr 06, 2009 11:39 pm

jazzeee wrote:

Hi - I was advised to post my problem in this thread.

I installed eeepc-acpi-utilities, however, some things don't work. The touchpad toggle complains it can't do it's job (blames xorg config which I have never touched since I installed eeebuntu - unless one of the eee configure scripts changed it).

The main problem however, the Wifi toggle, locks up the machine SOLID as soon as the wifi light goes out. Had to force power off to get the machine working. I tried it twice, same both times.

Also, boot time is greatly increased and the boot graphic falls back to text mode (because of the crash?).

My machine is a 701SD.

Touchpad toggle is an xorg or hal configuration issue, search the forum here for a fix.

For WIFI and the CPU lockup, can you send me debug outputs? The debug tools are in /etc/acpi/eeepc/debug, they need to be run under the context of sudo.

The WIFI issue is most likely a kernel driver problem. NDiswrapper may fix it, or switching to different drivers.

Also, are you running 1.0.31 from statux.org?

fewt · **Posted:** Mon Apr 06, 2009 11:40 pm

platojones wrote:

Quote:

I don't have OSDs for brightness, or volume. I wanted it to be more seemless, didn't see the value in writing a lot of code to present something on the screen that is already fed back in other ways (screen brightens or darkens, volume raises and lowers). I can revisit this though if enough people need it.

Interesting....I have a 1000 HE and the OSD shows up for volume, just not for brightness. I wonder if this could be a hardware difference between the 1000 H and 1000 HE.

In 8.10 the gnome shortcuts will intercept the mute, and vol up / down for the PCM mixer. This will give you the OSD and EeePC ACPI Utilities will still intercept the keys in the background.

jazzeee · **Posted:** Tue Apr 07, 2009 1:22 am

fewt wrote:

Touchpad toggle is an xorg or hal configuration issue, search the forum here for a fix.

I have been, but it's very confusing. Is there one definitive thread where the steps to fix it are explained?

fewt wrote:

For WIFI and the CPU lockup, can you send me debug outputs? The debug tools are in /etc/acpi/eeepc/debug, they need to be run under the context of sudo.

The WIFI issue is most likely a kernel driver problem. NDiswrapper may fix it, or switching to different drivers.

Also, are you running 1.0.31 from statux.org?

Yes I will send debug outputs. How do I use these tools? Do I run something before the crash or after?

About ndiswrapper, I thought that was for hardware that doesn't have native linux drivers. As I am running the kernel that came with eeebuntu (downloaded only a week ago) I would have thought the driver was a tried and tested one.

As for the version, I installed the utilities from your repo yesterday, so it's the latest.

fewt · **Posted:** Tue Apr 07, 2009 2:40 am

jazzeee wrote:

fewt wrote:

Touchpad toggle is an xorg or hal configuration issue, search the forum here for a fix.

I have been, but it's very confusing. Is there one definitive thread where the steps to fix it are explained?

fewt wrote:

For WIFI and the CPU lockup, can you send me debug outputs? The debug tools are in /etc/acpi/eeepc/debug, they need to be run under the context of sudo.

The WIFI issue is most likely a kernel driver problem. NDiswrapper may fix it, or switching to different drivers.

Also, are you running 1.0.31 from statux.org?

Yes I will send debug outputs. How do I use these tools? Do I run something before the crash or after?

About ndiswrapper, I thought that was for hardware that doesn't have native linux drivers. As I am running the kernel that came with eeebuntu (downloaded only a week ago) I would have thought the driver was a tried and tested one.

As for the version, I installed the utilities from your repo yesterday, so it's the latest.

The how-to is here: http://forum.eeeuser.com/viewtopic.php?id=54742&p=1

Run them before the crash, it will toggle them. Do the CPU debug first.

vortmax · **Joined:** Mon Apr 06, 2009 4:33 am **Posts:** 4

fewt wrote:

vortmax wrote:

Reposted from other thread...

I'm using a 1000HE and loving it so far! I installed the ACPI utilities to get the goodies working...most things are, except that Bluetooth is always ON and the webcam is always OFF. Attempting to toggle using the silver keys or the acpi tray utility will always report "Bluetooth Enabled" and "Webcam Disabled," and I cannot switch their states. Any ideas?

Try updating to 1.0.31. I unfortunately created a pair of bugs in 1.0.27 or 28.

This fixed the issue...all is well now. Thanks for the help!

jazzeee · **Posted:** Tue Apr 07, 2009 10:33 am

fewt wrote:

The how-to is here: http://forum.eeeuser.com/viewtopic.php?id=54742&p=1

Run them before the crash, it will toggle them. Do the CPU debug first.

Well, first I had to reinstall and I got a new version 1.0.32. Then I ran the cpu debug -didn't work very well

Code:

/etc/acpi/eeepc/debug/cpu.sh: line 43: ((: > 70 : syntax error: operand expected (error token is "> 70 ")
/etc/acpi/eeepc/debug/cpu.sh: line 45: ((: <= 70 : syntax error: operand expected (error token is "<= 70 ")
Outputting to: [/tmp/cpu_debug.txt]
Please generate and sent this file to the maintainer whenever reporting CPU issues.

So I tried the wifi one, and, of course the eeepc locked up. After I rebooted, there is no debug file in tmp, so I can't post it here.

fewt · **Posted:** Tue Apr 07, 2009 12:28 pm

jazzeee wrote:

fewt wrote:

The how-to is here: http://forum.eeeuser.com/viewtopic.php?id=54742&p=1

Run them before the crash, it will toggle them. Do the CPU debug first.

Well, first I had to reinstall and I got a new version 1.0.32. Then I ran the cpu debug -didn't work very well

Code:

/etc/acpi/eeepc/debug/cpu.sh: line 43: ((: > 70 : syntax error: operand expected (error token is "> 70 ")
/etc/acpi/eeepc/debug/cpu.sh: line 45: ((: <= 70 : syntax error: operand expected (error token is "<= 70 ")
Outputting to: [/tmp/cpu_debug.txt]
Please generate and sent this file to the maintainer whenever reporting CPU issues.

So I tried the wifi one, and, of course the eeepc locked up. After I rebooted, there is no debug file in tmp, so I can't post it here.

Run the cpu debug again, and send that file to me. Forget the WIFI one for now, for that, send me the output of 'sudo lspci -v'.

The CPU debug will have a few errors, because I need to update it, but the output is still ok.

Eee PC ACPI Utilities / Eeebuntu model support thread

Who is online