Both sides previous revisionPrevious revisionNext revision | Previous revision |
howtos:misc:asus_eeepc [2013/04/21 22:54 (UTC)] – [Powersaving and ACPI] Typos sycamorex | howtos:hardware:asus_eeepc [2014/12/18 02:38 (UTC)] (current) – howtos:misc:asus_eeepc renamed to howtos:hardware:asus_eeepc (Moved to hardware section) mfillpot |
---|
<note tip>I recommend to add this parameters using liloconfig logged as root.</note> | <note tip>I recommend to add this parameters using liloconfig logged as root.</note> |
| |
==== EEE PC acpi scrips ==== | ==== EEE PC acpi scripts ==== |
| |
Eric Hameleers,(aka [[wiki:user:alienbob|AlienBOB]]) had created a slackware [[http://taper.alienbase.nl/mirrors/people/alien/slackbuilds/eeepc-acpi-scripts/ | package]] that will enable most of the FN keys functions; however, two FN key functions that I've personally impossible to live without based on my preferences and usage are the FN+F3 (disable touchpad) and FN+Space bar (Super Hybrid Engine) | Eric Hameleers (aka [[wiki:user:alienbob|AlienBOB]]) had created a Slackware [[http://taper.alienbase.nl/mirrors/people/alien/slackbuilds/eeepc-acpi-scripts/ | package]] that will enable most of the FN keys functions; however, two FN key functions that I personally find impossible to live without based on my preferences and usage are the FN+F3 (disable touchpad) and FN+Space bar (Super Hybrid Engine). |
| |
These could be easily enabled by doing the following: | These could be easily enabled by doing the following: |
=== Touchpad toggle function === | === Touchpad toggle function === |
| |
Create a text file on /etc/acpi/events/ as follows | Create a text file in /etc/acpi/events/ containing the following code: |
<code> | <code> |
event=hotkey ATKD 00000037 | event=hotkey ATKD 00000037 |
</code> | </code> |
| |
In my case, the file is named touchpad-toggle. This particular file identify an action once an event triggers. The "00000037" points specifically to the event of pressing FN+F3 keys combination of the model specified.<note> To identify the correct code for your keys use <key>acpi_listen</key> | In my case, the file is named touchpad-toggle. This particular file identifies an action once an event is triggered. The "00000037" points specifically to the event of pressing FN+F3 keys combination of the model specified.<note> To identify the correct code for your keys use <key>acpi_listen</key> |
</note> | </note> |
| |
notify touchpad "$msg" | notify touchpad "$msg" |
</code> | </code> |
<note important>do not forget to give execute permissions to the actions files (as root) | <note important>Do not forget to give execute permissions to the actions files (as root) |
chmod +x /etc/acpi/actions/touchpad-toggle.sh</note> | chmod +x /etc/acpi/actions/touchpad-toggle.sh</note> |
| |
| |
=== Enabling SHE function === | === Enabling SHE function === |
"Super Hybrid Engine" as it's known under windows has a significant effect on powersaving. This underclocks the FSB for powersave/overclocks for performance. This is achieved by laptop-mode-tools. | "Super Hybrid Engine" as it's known under Windows has a significant effect on powersaving. This underclocks the FSB for powersave/overclocks for performance. This is achieved by laptop-mode-tools. |
<note tip> | <note tip> |
| |
I recommend using the slackbuild script available at [[http://slackbuilds.org/repository/14.0/system/laptop-mode-tools/]]</note> | I recommend using the SlackBuild script available at [[http://slackbuilds.org/repository/14.0/system/laptop-mode-tools/]]</note> |
| |
Once laptop-mode-tools is installed we could proceed with enabling the control of the FSB by pressing FN+Space bar combo by creating a file on the /etc/acpi/events folder just as before: | Once laptop-mode-tools is installed we could proceed with enabling the control of the FSB by pressing FN+Space bar combo by creating a file in the /etc/acpi/events directory just as we did before: |
| |
<code> | <code> |
notify cpu "$msg" | notify cpu "$msg" |
</code> | </code> |
<note important>do not forget to give execute permissions to the actions files (as root) | <note important>Do not forget to give execute permissions to the actions files (as root) |
chmod +x /etc/acpi/actions/she.sh</note> | chmod +x /etc/acpi/actions/she.sh</note> |
| |
===== Video card speed tune up ===== | ===== Video card speed tune up ===== |
| |
I've recently learned that this Asus 1005HA Intel chip 945GM/GMS/GME is slightly under clocked in order to provide longer battery life according to the SHE profile. On windows, the default clock-speed is 166MHz in powersaving mode and 200MHz in High/Super mode; however, this chip is able to run at 400MHz. | I've recently learned that this Asus 1005HA Intel chip 945GM/GMS/GME is slightly under clocked in order to provide longer battery life according to the SHE profile. On Windows, the default clock-speed is 166MHz in powersaving mode and 200MHz in High/Super mode. This chip, however, is able to run at 400MHz. |
| |
<note>I've only found necessary to set the clock at high speed when using an external monitor with extended desktop while running kde. I've left the video card clock speed settings separated form the SHE toggle acpi scripts for that specific reason.</note> | <note>I've only found necessary to set the clock at high speed when using an external monitor with extended desktop while running KDE. I've left the video card clock speed settings separated form the SHE toggle acpi scripts for that specific reason.</note> |
| |
The following script will set GMA chipset speeds (run it as root): | The following script will set GMA chipset speeds (run it as root): |
<!-- Please do not modify anything below, except adding new tags.--> | <!-- Please do not modify anything below, except adding new tags.--> |
<!-- You must remove the tag-word "template" below before saving your new page --> | <!-- You must remove the tag-word "template" below before saving your new page --> |
{{tag>howtos template}} | {{tag>howtos asus eee}} |