https://wiki.archlinux.org/api.php?action=feedcontributions&user=Hiperi0n&feedformat=atomArchWiki - User contributions [en]2024-03-29T14:40:34ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Bashrc&diff=52642Bashrc2008-11-03T20:48:24Z<p>Hiperi0n: </p>
<hr />
<div>{{stub}}<br />
<br />
[[Category:Dotfiles (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Bashrc}}<br />
{{i18n_entry|Español|Bashrc (Español)}}<br />
{{i18n_links_end}}<br />
<br />
A place for Arch users' .bashrc file tips and tricks. .bashrc is a configuration file that contains commads to be executed whenever an interactive shell is started.<br />
==PS1==<br />
To colourise the bash prompt:<br />
Comment out the default PS1:<br />
#PS1='[\u@\h \W]\$ '<br />
The following PS1 is useful for a root bash prompt, with red designation and green console text:<br />
PS1='\[\e[0;31m\]\u\[\e[m\] \[\e[1;34m\]\w\[\e[m\] \[\e[0;31m\]\$ \[\e[m\]\[\e[0;32m\] '<br />
See also [[Color Bash Prompt | this wiki page]]<br />
==Aliases==<br />
<br />
===Default command usage===<br />
To make rm prompt for removals<br />
alias rm='rm -i'<br />
To make spelling mistakes not matter<br />
alias unmount='umount'<br />
alias pakman='pacman'<br />
Seen in forums to force someone to learn vim<br />
alias nano='vi'<br />
<br />
===Shortcuts===<br />
<br />
==Useful environment variables==<br />
Set a default text editor<br />
EDITOR=nano<br />
EDITOR=vi<br />
<br />
== HTTP / FTP Proxy ==<br />
You can export your HTTP and FTP proxy settings from .bashrc by adding the following:<br />
export http_proxy="http://172.16.1.6:3128"<br />
export ftp_proxy="ftp://172.16.1.6:3128"</div>Hiperi0nhttps://wiki.archlinux.org/index.php?title=Talk:ASUS_Eee_PC_701&diff=50879Talk:ASUS Eee PC 7012008-10-09T18:04:46Z<p>Hiperi0n: Info about SSD</p>
<hr />
<div>=Please Finish this article=<br />
The EEE has been out for quite some time now. Please finalize this entry and get it up to date. It remains too long and somewhat convoluted. Thanks for your efforts. [[User:Misfit138|Misfit138]] 17:10, 11 September 2008 (EDT)<br />
<br />
== Changes to the article ==<br />
<br />
I have made quite a radical changes to the article. Please provided your feedback and comment. Also, please correct any mistakes, weather it is technical or grammatical, that you have found on the article.<br />
<br />
The article need a lot of input from people who use filoktetes kernel26eee. So if you use filoktetes kernel, please contribute.<br />
<br />
I would like to thanks all people who have contributed on this article, to whom without which I wouldn't have gotten this far. Thanks guys! You guys rock! :)<br />
<br />
<br />
<br />
Isn't the filoktetes kernel26eee removed from all repos? I think the article needs some heavy editing in the kernel / kernel modules installation part.<br />
[[User:Ighea|Ighea]] 14:58, 21 March 2008 (EDT)<br />
<br />
==Journaling FS and Temp FS for logs==<br />
It should be noted that the Eee 901 uses ext3 by default for the /home partition. A lot of the "don't use a journaling FS" FUD relates to the early days of solid state devices before hardware level wear-leveling was introduced. [http://wiki.eeeuser.com/ssd_write_limit this eeeuser.com article] looks into the matter in more detail.<br />
<br />
Also see this article: http://www.storagesearch.com/ssdmyths-endurance.html<br />
<br />
Perhaps there should at least be a footnote to the warning not to use a journaling FS and to create the logs partition as a tempfs, with pointers to these articles and a brief mention that SSD flash cards have improved.<br />
<br />
== madwifi-newhal-svn ==<br />
<br />
WiFi works very well with http://aur.archlinux.org/packages.php?ID=17392 No need to patch anymore!<br />
<br />
== Info about SSD ==<br />
<br />
I have added some info regarding SSD and avoiding pitfalls. I know this document is for the standard eee pc, however as all other eee users also must follow this guide, I thought it would be nice to remark the difference of SSD and standard HD.</div>Hiperi0nhttps://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=50878ASUS Eee PC 7012008-10-09T18:01:15Z<p>Hiperi0n: </p>
<hr />
<div>{{stub}}<br />
[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
'''WARNING: THIS ARTICLE IS INCOMPLETE!''' Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum]. There is also a nice Arch Linux installation guide on the [http://wiki.eeeuser.com/installingarchlinux EeeUser Wiki].<br />
<br />
Note: Users of 901/1000 series eee pcs should follow the work in progress guide [http://wiki.archlinux.org/index.php/Asus_Eee_PC_901 here].<br />
<br />
==Before You Begin==<br />
<br />
===Avoiding Pitfalls===<br />
<br />
The install is pretty normal, except that you'll need to [http://forum.eeeuser.com/viewtopic.php?id=890 avoid the pitfalls] of our alternative Linux install:<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
The rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]] '''(Recommended)'''<br />
<br />
==Installing Arch Linux==<br />
<br />
* '''NOTE:''' Please refer to The [[Beginners_Guide]] for detailed instructions, if needed. Ideally, your CD/USB should boot up just fine on Eee PC without any need for additional options.<br />
<br />
===Booting Arch the installation CD/USB===<br />
<br />
The stock kernel on Arch installation media since 2008.06 and newer support Eee's ethernet network card. So there's no need to install any additional modules before or during the installation process to have a working network connection (unless you want to use wireless network card). <br />
<br />
===Mount the installation media===<br />
<br />
* '''NOTE:''' Non-FTP install only<br />
The installer should mount USB source media automatically. If it fails you can manually mount the source media on the stick to the /src directory with the following command:<br />
<br />
mount /dev/sd[x] /src<br />
<br />
===Start the Installation===<br />
<br />
Just run<br />
<br />
/arch/setup<br />
<br />
To start the installation just like normal.<br />
<br />
===Prepare Hard Drive===<br />
<br />
The default Eee PC drive is split up into four partitions (here is [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* It is easiest to wipe the existing partitions and use one or two partitions for your install. One partition would be just '/', and two partitions would be '/boot' and '/'.<br />
* Choose "NONE" for swap in case your eee has a SSD (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* Select "ext2" as your filesystem in case your eee has a SSD (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]). If your model has a standard HD choose "ext3".<br />
<br />
===Select Packages===<br />
<br />
Choose the proper source of package, this should be done automatically if you are installing from USB.<br />
<br />
In addition to the '''BASE''' category, you also need all of the packages in the '''DEVEL''' category if you are planning on compiling stuffs on your Eee.<br />
<br />
If you intended to use wireless, then you'll also need the ''wireless_tools'' package from '''SUPPORT''' category.<br />
<br />
===Install Customized Kernel and All the Necessary Modules===<br />
<br />
After you have installed all the packages you want from your installation media of choice, the next step is to install the kernel that was customized for Eee and all the necessary modules. <br />
<br />
Since toofishes' kernel-eee is currently the most up to date one and contains all the necessary modules and patches for Eee (while the stock kernel lacks most of them), it is recommended that you use kernel-eee from toofishes' repository.<br />
<br />
====Eee repository from toofishes====<br />
toofishes created a repository for the Eee. You can find some basic packages like Pentium-M-optimized kernel and needed modules. Add<br />
[eee]<br />
Server = http://code.toofishes.net/packages/eee<br />
to your /etc/pacman.conf to use the repository.<br />
<br />
=====Package List=====<br />
<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' <br />
customized kernel for Eee<br />
*'''luvcview''' <br />
webcam program for testing webcam driver<br />
*'''madwifi-eee-svn''' <br />
wifi driver for Eee<br />
*'''eeepc-linux''' <br />
kernel module to change Eee's FSB speed and fan control<br />
<br />
=====Installation Instruction=====<br />
<br />
Simply use pacman to install the package that you need. For a working system, you'll need at least 3 packages: kernel-eee (the kernel), linux-uvc-eee-svn (webcam driver) and madwifi-eee-svn (the wifi driver).<br />
<br />
Install the packages with this command:<br />
<br />
pacman -Sy kernel-eee madwifi-eee-svn<br />
<br />
*'''ATTENTION:''' dkite's eeemodules package conflicts with the madwifi-eee-svn package. You need to remove dkite's eeemodules package before you can install toofishes madfwifi-eee-svn package.<br />
<br />
Then, add the following to /boot/grub/menu.lst; note that no initrd is needed:<br />
# (2) Arch Linux<br />
title Arch Linux EEE kernel<br />
root (hd0,0)<br />
kernel /boot/vmlinuzeee root=/dev/sda1 ro<br />
<br />
Restart and select Arch Linux EEE kernel from the grub boot menu.<br />
<br />
===Add the Final Touch===<br />
<br />
After you have install kernel-eee and all the related packages as noted above, make these edits to /etc/fstab:<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* '''OPTIONAL:''' Add a new line: "tmpfs /var/log tmpfs size=1M 0 0" ('''WARNING:''' this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]. To save your startup/shutdown logs, look at the pitfalls link above).<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. The following is the guide on how to get the rest of your system working.<br />
<br />
===Xorg===<br />
<br />
You have two choices for video on the Eee - the newer <b>xf86-video-intel</b> driver, or the older <b>xf86-video-i810</b> driver paired with 915resolution. The intel driver is the focus upstream and is being actively developed so it is your best choice. <br />
<br />
However, if you wish to use composite extension (for Compiz Fusion, for example), then the old i810 driver might be a better option, mainly because XV video output does not work when composite is enabled on the currently intel driver and thus a lot of applications, such as Skype or UCView, will not function properly.<br />
<br />
You need these packages in addition to the Xorg's packages:<br />
<br />
pacman -Sy synaptics xf86-video-intel<br />
<br />
If you choose to use the older i810 video, you will have to install xf86-video-i810 and 915resolution as well. Note that the i810 driver and the intel driver cannot both be installed at the same time.<br />
<br />
Then, just drop in the following xorg.conf into your /etc/X11/ directory:<br />
<br />
<pre>Section "ServerLayout"<br />
Identifier "ArchLinux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "extmod"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail"<br />
Option "BlankTime" "5"<br />
Option "AIGLX" "false"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "keyboard"<br />
Driver "kbd"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbLayout" "us"<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "IMPS/2"<br />
Option "Emulate3Buttons" "yes"<br />
Option "ZAxisMapping" "4 5"<br />
Option "CorePointer"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "synaptics"<br />
Driver "synaptics"<br />
Option "Device" "/dev/psaux"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1000"<br />
Option "RightEdge" "5400"<br />
Option "TopEdge" "1000"<br />
Option "BottomEdge" "4900"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "HorizScrollDelta" "0" <br />
Option "RBCornerButton" "0"<br />
Option "RTCornerButtom" "0"<br />
Option "MaxSpeed" "0.1"<br />
<br />
# You will also need the following 3 lines if you're using Xorg 1.5RC6 or newer<br />
Option "TapButton1" "1"<br />
Option "TapButton2" "2"<br />
Option "TapButton3" "3"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "ASUS"<br />
ModelName "eeePC P701"<br />
Modeline "800x480" 29.58 800 816 896 992 480 481 484 497 -HSync +Vsync # 60 Hz<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "intel"<br />
VendorName "Intel Corporation"<br />
BoardName "Mobile 915GM/GMS/910GML Express Graphics Controller"<br />
BusID "PCI:0:2:0"<br />
Option "AccelMethod" "EXA"<br />
Option "MigrationHeuristic" "greedy"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</pre><br />
<br />
If you want to set up the i810 driver instead, you will also have to configure 915resolution and add it to your daemons line. This is not needed for the intel driver. Edit the /etc/conf.d/915resolution to look like this:<br />
<br />
<pre># Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
</pre><br />
<br />
Now put the 915resolution daemon into your /etc/rc.conf file:<br />
<br />
<pre>DAEMONS=(... 915resolution ...)</pre><br />
<br />
===Sound, Webcam & Microphone===<br />
<br />
====Sound====<br />
<br />
Some people have reported sound working right out of the box with no troubles. However, others might need to add to /etc/modprobe.conf the following line for the EeePC 701<br />
<pre>options snd-hda-intel model=3stack-dig</pre><br />
or the following one for the EeePC 900 model<br />
<pre>options snd-hda-intel model=auto</pre><br />
<br />
If your internal microphone doesn't work, you probably have to turn the capture feature on. Simply fire up alsamixer, find your Capture control, and press spacebar to enable it.<br />
<br />
====Webcam====<br />
<br />
You can enable your built-in webcam by adding the following line to your /etc/rc.local file.<br />
<br />
echo 1 > /proc/acpi/asus/camera<br />
<br />
If you want the webcam application that the default Xandos installation uses, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14469 ucview from the AUR].<br />
<br />
The webcam also works fine with the latest version of Skype.<br />
<br />
If you already have mplayer installed you can launch :<br />
mplayer -fps 15 tv://<br />
<br />
I have yet to get it working with vlc or any other software such as xawtv. If you know how, please update this.<br />
<br />
*'''NOTE:''' For anyone who has accidentally disabled Auto Exposure for their webcam in luvcview (making the image dark), and can't enable it again, do the following:<br />
<br />
Install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14468 libwebcam from the AUR].<br />
<br />
Issue the following command:<br />
<pre>uvcdynctrl --set "Exposure, Auto" 4</pre><br />
<br />
*'''NOTE:''' Be sure the "OS Installation" option is set to "finished" in the BIOS' "Advanced" tab or your camera may not work in some applications (like Skype).<br />
<br />
====Microphone====<br />
<br />
Solution for problems with the internal microphone.<br />
<br />
1. First of all set in alsamixer "Input Source" to "i-Mic"<br />
<br />
2. Increase "Capture" and "i-Mic Boost" to your needs<br />
<br />
3. Edit /etc/asound.state the following, change the 2 "false" to "true" like showing:<br />
<pre><br />
....snap.....<br />
control.11 {<br />
comment.access 'read write'<br />
comment.type BOOLEAN<br />
comment.count 2<br />
iface MIXER<br />
name 'Capture Switch'<br />
value.0 true<br />
value.1 true<br />
}<br />
....snap....</pre><br />
<br />
4. After editing run following as root<br />
<pre>alsactl restore</pre><br />
<br />
5. Now your internal microphone should be working.<br />
<br />
===Getting Hot Keys, Graphic Indicators and Shutdown with the Power Button Working===<br />
<br />
If you want to have working hot keys for changing brightness and volumes, graphic indicators working as well as shutdown when press the power button (just like in the stock Eee PC), then you should install '''ighea's acpi-eee''' or '''dkite's acpid_eee''' package.<br />
<br />
==== ighea's acpi-eee ====<br />
<br />
Get the latest package from [http://kapsi.fi/ighea/eee/acpi-eee/ here].<br />
<br />
The package can be easily installed with<br />
pacman -U acpi-eee-10.0-1-i686.pkg.tar.gz<br />
<br />
See messages during installation for more details and don't forget to edit /etc/acpi/eee.conf to suit your tastes.<br />
<br />
==== dkite's acpid_eee ====<br />
<br />
Package can also be download from his [http://members.shaw.ca/dkite/ website]<br />
<br />
The package itself can be install with<br />
<br />
pacman -Uf acpid_eee-0.0.3-1-i686.pkg.tar.gz.tar<br />
<br />
With '''both''' packages don't forget to start '''asusosd''' if you want to have the Graphic Indicators from Xandros.<br />
<br />
==Additional Tips & Tweaks==<br />
<br />
===kernel26eee tweaks===<br />
<br />
Toofishes' kernel, also known as kernel26eee, can be recompiled to include custom features. You can download toofishes' kernel PKGBUILD and all the nesseary files from his gitweb by installing the git package and using the following command:<br />
<br />
git clone http://code.toofishes.net/gitprojects/eee.git<br />
<br />
There are two ways to tweak the kernel. The first is simply to edit the <code>kernelconfig</code> file with your favorite editor and the second is to insert a <code>make menuconfig</code> line into the PKGBUILD before the kernel's compilation.<br />
<br />
===Using Wine with toofishes' kernel===<br />
<br />
Normally, Wine won't work with toofishes' kernel because it is compiled with VMSPLIT_2G_OPT option. In order to use Wine with toofishes' kernel, you have to recompile his kernel with VMSPLIT_3G option.<br />
<br />
Download the kernel PKGBUILD and all the necessary files from toofishes' gitweb using the above instructions, then change the following lines in the <code>kernelconfig</code> file<br><br />
from this:<br />
<pre><br />
...<br />
230 CONFIG_NOHIGHMEM=y<br />
231 # CONFIG_HIGHMEM4G is not set<br />
232 # CONFIG_HIGHMEM64G is not set<br />
233 # CONFIG_VMSPLIT_3G is not set<br />
234 # CONFIG_VMSPLIT_3G_OPT is not set<br />
235 # CONFIG_VMSPLIT_2G is not set<br />
236 CONFIG_VMSPLIT_2G_OPT=y<br />
237 # CONFIG_VMSPLIT_1G is not set<br />
...<br />
</pre><br />
<br />
to this:<br />
<pre><br />
...<br />
230 CONFIG_NOHIGHMEM=y<br />
231 # CONFIG_HIGHMEM4G is not set<br />
232 # CONFIG_HIGHMEM64G is not set<br />
233 CONFIG_VMSPLIT_3G=y<br />
234 # CONFIG_VMSPLIT_3G_OPT is not set<br />
235 # CONFIG_VMSPLIT_2G is not set<br />
236 # CONFIG_VMSPLIT_2G_OPT is not set<br />
237 # CONFIG_VMSPLIT_1G is not set<br />
...<br />
</pre><br />
Compile and install the kernel and Wine should now work.<br />
<br />
===Power down with the power button===<br />
<br />
* '''NOTE:''' If you are using ighea's acpi-eee or dkite's acpid_eee package then you should already be able to shutdown by pressing the power button and should not need to do this.<br />
<br />
The two alternatives here are described in [[Allow_users_to_shutdown]].<br />
<br />
If you don't already or don't plan to use sudo, it may be simpler to use the setuid /sbin/halt method, otherwise using sudo is preferred.<br />
<br />
Below are all the steps required for the sudo method. If you want to use the setuid method, read the article linked above and perform the 'power' file step here, while omitting the 'sudo' in it.<br />
<br />
<pre>pacman -S sudo</pre><br />
<br />
As root, do the following:<br />
<br />
<pre>visudo</pre><br />
<br />
Add the following line to the file:<br />
<br />
<pre>USER HOST = NOPASSWD: /sbin/poweroff</pre><br />
<br />
Where USER = the user you want to be able to power down with and HOST = your hostname (from /etc/rc.conf).<br />
<br />
Now, create a file called /etc/acpi/events/power, containing:<br />
<br />
<pre># /etc/acpi/events/power<br />
# This is called when the user presses the power button<br />
<br />
event=button/power (PWR.||PBTN)<br />
action=sudo /sbin/poweroff</pre><br />
<br />
Make sure that you execute<br />
<br />
<pre>/etc/rc.d/acpid start</pre><br />
<br />
And/or add acpid to the daemons list in /etc/rc.conf:<br />
<br />
<pre>DAEMONS=(hal, acpid ...</pre><br />
<br />
===Use cpufreq for power saving===<br />
<br />
* '''NOTE:''' If you are using toofishes's kernel, then processor scaling is already enable and you don't need to do the following steps.<br />
<br />
Install cpufrequtitls.<br />
pacman -S cpufrequtils<br />
<br />
For scaling down the processor you have to load the p4_clockmod module. Insert it into your /etc/rc.conf MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
<br />
Add 'cpufreq' to the DAEMONS array in /etc/rc.conf to have it start on startup.<br />
DAEMONS=(... cpufreq ...)<br />
<br />
Add the following into /etc/conf.d/cpufreq<br />
governor="ondemand"<br />
min_freq="113MHz"<br />
max_freq="900MHz"<br />
<br />
With enabled cpufreq it scales the processor between 113MHz up to max. frequency. That should save a lot on battery power. The stated 900MHz will be never reached by the eeePC, the p4_clockmod reports a wrong frequency here. But scaling works, you can feel it in the performance of eeePC that he slow down the processor.<br />
<br />
===More responsive system with ondemand governor===<br />
The default up_threshold (where it will bump to a faster speed) for the CPU governor is 80, which means it will increase the CPU speed when utilization is above 80%. This can make X applications have a bit of lag. <br />
Try changing this value:<br />
sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
With 40 it still leaves the majority of CPU cycles at the lowest available clock speed but increases responsiveness. You can add this line to one of your startup scripts (such as /etc/rc.local) if you wish to keep it, for example:<br />
<pre><br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
<br />
echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold<br />
</pre><br />
<br />
Also, following line is also reported to help makes system more responsive. You can use it by adding it to your /etc/rc.local:<br />
<pre><br />
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate<br />
</pre><br />
<br />
===Speeding up udev for faster boot===<br />
* [[Speedup udev]]<br />
*http://dev.laptop.org/ticket/4349<br />
*[http://www.eeesale.com/Asus-Eee-PC-overclock-Benchmarks.htm Speed up the Eee PC]<br />
<br />
You can also disable the autoload by editing your ''rc.conf'' :<br />
...<br />
MOD_AUTOLOAD="no"<br />
...<br />
MODULES=(pciehp wlan ath_hal ath_pci)<br />
<br />
===Update your BIOS without Xandros===<br />
* '''Warning : you can break your system, do not update if you are not sure of what you are doing!'''<br />
<br />
First, you need to download the ''.rom'' file.<br />
*[http://update.eeepc.asus.com/bios/ Asus official's BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USBStick formated in fat32.<br />
To format an USBStick, use cfdisk tool :<br />
cfdisk /dev/sdc #could be something else than "c"<br />
Choose [delete], [type] : "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
cp /somewhere/blabla/.../thecurrentnameofthefile.rom /dev/sdc1/701.rom<br />
The name of the copy '''must''' be 701.rom<br />
<br />
Next step, reboot the eeepc with the USBStick pluged-in, and press<br />
Alt + F2<br />
It will launch the built-in tool. Everything should be Ok, you can make a coffee during the update. When it asks you to push the power-button it has finished.<br />
<br />
At the next boot, you'll be invited to configure the BIOS. Check if the everything is enabled (my webcam and wireless were disabled after the update) and if it displays the good version in the main screen. It's done !<br />
<br />
===More usuable font sizes===<br />
<br />
On a default installation with XFCE 4 my font sizes were too big, here is what I did to sort them out.<br />
<br />
First, I set the DPI by adding the following to ~/.Xdefaults:<br />
Xft*dpi: 134<br />
<br />
This then caused the fonts to be even bigger, so I set them all to be font-size 6 by adding the following into ~/.gtkrc-2.0 (note this will be overwritten if you use any tools to change GTK settings):<br />
style "user-font"<br />
{<br />
font_name="Bitstream Vera Sans 6"<br />
}<br />
widget_class "*" style "user-font"<br />
<br />
To do the same with KDE fonts (without KDE installed) you have to add the following to ~/.kde/share/config/kdeglobals:<br />
[General]<br />
StandardFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
activeFont=Bitstream Vera Sans,6,-1,5,75,0,0,0,0,0<br />
fixed=Bitstream Vera Sans Mono,6,-1,5,50,0,0,0,0,0<br />
font=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
menuFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
taskbarFont=Bitstream Vera Sans,6,-1,5,50,1,0,0,0,0<br />
toolBarFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
<br />
To make your fonts even prettier enable the [[Fonts#Fonts_with_LCD_filter_enabled|LCD Fonts]].<br />
<br />
====Alternative Method====<br />
<br />
For me it worked far better to open the gnome appearance control panel, go to the fonts tab, click defaults, and change the resolution to be 96 dpi. Changing .Xdefaults doesnt work when running gnome, as gnome-settings-daemon overrides it. You can then leave all font sizes at their default, and things should look good. Simply changing the font sizes and leaving the DPI at its technically correct value (~134) gave me weird layout problems in some apps, and oddly large fonts in others.<br />
<br />
===Using stock kernel===<br />
<br />
Some users might want to use the stock kernel. Since the stock kernel lacks most of the necessary modules for Eee, we need to install them manually. There are two way of doing this: compile and install everything from source or use dkite's eeemodules packages.<br />
<br />
====Install All the Necessary Modules using dkite's eeemodule package==== <br />
IMPORTANT : A recent kernel upgrade no longer allows the madwifi dkite included in his eeemodules package to compile. For that reason and for the sake of keeping up to date, prurigro has contributed eeemodules-hal. This package is identical to dkite's except it uses madwifi-hal from http://snapshots.madwifi.org/madwifi-hal-0.10.5.6/ which is actually made with the eee's wirless card in mind and compiles well with the current kernel. eeemodules-hal is available in the AUR @ http://aur.archlinux.org/packages.php?ID=19256 .<br />
<br />
If anyone has webspace to throw a package compiled for the current installer's kernel, it would be beneficial to those without a linux desktop to make it themselves. Thanks<br />
(Accurate August 21st 2008) <br />
<br />
'''dkite''' have created a package that contains all the necessary modules for wifi, ethernet connection, acpi and video camera hardware that comes with the Eee PC. His package is to be use with the stock kernel. <br />
<br />
The following is the list of hardware/functions that are known to work with dkite's eeemodules Package:<br />
<br />
*Wireless <br />
*Ethernet <br />
*Webcam <br />
*Suspend/Resume<br />
<br />
You can get the package [http://members.shaw.ca/dkite from his website]. <br />
<br />
Currently there are three pre-complied package:<br />
<br />
#'''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' for use with Don't Panic kernel.<br />
#'''eeemodules-0.0.3-2.6.24.1.2-i686.pkg.tar.gz''' for the 2.6.24.14-2 kernel.<br />
<br />
If you have newer or other version of kernel26, then you will need to download '''eeemodules.tar.gz''', which contains PKGBUILD and all the necessary files, and build the package yourself. <br />
<br />
*'''ATTENTION:''' You will also need to rebuild the package, using eeemodules.tar.gz, every time you upgrade your kernel, or else your hardware (wifi, ethernet, etc.) will stop functioning.<br />
<br />
=====Installation Instructions=====<br />
<br />
Install the package with the following command:<br />
<br />
pacman -Uf eeemodules-<pkgver>.tar.gz<br />
<br />
Then run a depmod command:<br />
<br />
depmod<br />
<br />
* '''ATTENTION:''' Do ''not'' forget to run the depmod command after installing the package, otherwise your hardware won't function! <br />
<br />
Finally, edit /etc/rc.conf and add asus_acpi to the MODULES array:<br />
<br />
MODULES = (... asus_acpi ...)<br />
<br />
====Compile and Install All the Necessary Modules from Source====<br />
<br />
* '''NOTE:''' for anyone who read this wiki previously and wondered where the patched kernel download went; the latest arch kernel contains the patch that fixes the intel graphics vsync hardlock error, so no additional configuration need be done<br />
<br />
=====Install Network Adapter Drivers=====<br />
<br />
======Atl2 ethernet driver======<br />
<br />
* '''UPDATE:''' the atl2 ethernet is support by Arch Linux's stock kernel as of 2008.03, however, you must manually select the atl2 package during the installation.<br />
<br />
You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
<br />
Extract the sources. You may need to modify the kernel version listed in the Makefile.<br />
<br />
make clean<br />
make<br />
cp atl2.ko /lib/modules/2.6.24-ARCH/kernel/drivers/net # Change 2.6.24 as needed<br />
depmod<br />
<br />
======Atheros wireless ethernet driver======<br />
<br />
Instructions from http://wiki.eeeuser.com/ubuntu#wireless_internet_using_native_madwifi_drivers to patch madwifi. This replaces the Arch madwifi packages.<br />
<br />
wget 'http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw'<br />
wget http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
<br />
'''UPDATE:''' For the EEE PC 900, you just need to install the madwifi-newhal-svn package from the AUR, and then blacklist the ath5k module.<br />
<br />
==Known problems and their solutions==<br />
<br />
===Wireless doesn't work, even after installing custom Madwifi module===<br />
<br />
I found that Arch tried to use the ath5k module for wireless, and that meant it took control of the card rather than ath_pci (the module I had compiled and installed). I got a Madwifi status 3 message in dmesg when this happened.<br />
<br />
The solution is to blacklist the ath5k module in /etc/rc.conf:<br />
<br />
MODULES = ( ... !ath5k ... )<br />
<br />
===Laggy or Unresponsive ACPI Events===<br />
<br />
The latest kernel (2.6.26) introduces new problems with Eee's ACPI events handling. Basically, ACPI events become very laggy and after some time ACPI get disabled after a heavy usage (e.g. changing volume, brightness). This problem affects both stock kernel and toofishes' kernel.<br />
<br />
It appears that the solution is to apply this [http://bugzilla.kernel.org/attachment.cgi?id=16862 patch] ([http://bugzilla.kernel.org/show_bug.cgi?id=10724 original bug report]) to the kernel. <br />
<br />
*'''Note:''' the latest toofishes' kernel, version 2.6.26-1, now include the patch, but you can still use ighea's one for the extras features listed below.<br />
<br />
Until toofishes update his kernel to include the patch, you can use ighea's slightly modified toofishes' kernel that included the above patch, as well as other modifications:<br />
<br />
*Support for Wine <br />
*uvesafb is built as module <br />
*Use [http://bbs.archlinux.org/viewtopic.php?pid=393860#p393860 new eeepc-laptop driver] (which also handles fan-control) instead of older acus_acpi or asus-laptop -drivers.<br />
<br />
You can get the modified kernel, as well as the associative packages, from [http://koti.kapsi.fi/~ighea/eee/kernel-eee/ here].<br />
<br />
After you have downloaded the packages, Install them using this command:<br />
<br />
pacman -U kernel-eee-2.6.26-1-i686.pkg.tar.gz madwifi-eee-svn-3752-1-i686.pkg.tar.gz <br />
<br />
You might also want to use IgnorePkg-line in /etc/pacman.conf to hold packages from being accidentally updated.<br />
<br />
IgnorePkg = kernel-eee madwifi-eee-svn<br />
<br />
Also don't forget to upgrade ighea's acpi-eee package to version 9.6.<br />
<br />
===Shutdown Problem===<br />
<br />
If your Eee won't shutdown properly (i.e. the power indicator LED is on but the LCD screen is off), then add the following lines to your /etc/rc.local.shutdown file.<br />
<pre><br />
#! /bin/bash<br />
#<br />
# /etc/rc.local.shutdown: Local shutdown script.<br />
#<br />
<br />
# Comment or uncomment the following two lines according to your system configuration.<br />
<br />
/etc/rc.d/mpd stop # If you're using mpd, then you have to stop its daemon first.<br />
<br />
/etc/rc.d/alsa stop # If you're using ALSA daemon, then you also have to stop it.<br />
<br />
# The following line is Eee specific fix, you always need to have this line in /etc/rc.local.shutdown.<br />
<br />
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind<br />
</pre><br />
The above solution should fix the shutdown problem in most cases. But if for some reason the problem still persists, the module may not be able to be unloaded until after all services have finished. Do the above, then in /etc/rc.shutdown move <br />
<br />
if [ -x /etc/rc.local.shutdown ]; then<br />
/etc/rc.local.shutdown<br />
fi<br />
<br />
from where it was to directly above the line <br />
<br />
# Terminate all processes<br />
<br />
this will cause the rc.local.shutdown script to run after services have been exited. This fixed all issues for the person editing this note.<br />
<br />
===Unclean unmount during shutdown when having home directory mounted on SD card===<br />
<br />
If you experienced unclean unmount during shutdown when having your home directory on SD card, then add the following 3 lines to "Write to wtmp file before unmounting" section of your /etc/rc.shutdown file:<br />
<pre><br />
...<br />
<br />
stat_busy "Unmounting Filesystems"<br />
/bin/umount -a -t noramfs,notmpfs,nosysfs,noproc<br />
<br />
# Add these 3 lines<br />
sync;sync;sync;<br />
eject /dev/sdb # Or whichever is your SD-card's device name. /dev/disk/by-uuid/ followed by the UUID identifier is preferable though.<br />
sleep 3<br />
# End of hack<br />
<br />
stat_done<br />
<br />
...<br />
</pre><br />
<br />
===Booting from card without initrd===<br />
<br />
Let's say you decided to install Arch Linux on a card and compiled your own kernel (or used the kernel26eee kernel) without initrd. Card reader on EeePC is connected as an USB device. Unfortunately, USB storage devices are detected with a delay, so we must tell the kernel to wait until this device becomes available. You do this with "rootwait" option passed to kernel at boot time.<br />
<br />
===Sleeping and waking system on a card===<br />
<br />
If you have Arch Linux on a card, waking up from sleeping state will most likely fail. The only solution is to enable the CONFIG_USB_PERSIST option in kernel. The kernel26eee package should have this option enabled.<br />
<br />
===Display doesn't wake up properly===<br />
<br />
If you encounter black display (but apparently working system) after suspend/resume, consider using the "uswsusp" package (available in AUR) and correcting suspend2ram script in /etc/acpi, where you use this line to make the machine go to sleep:<br />
<br />
<pre>/usr/sbin/s2ram --force --vbe_post --vbe_mode</pre><br />
<br />
==Battery Tests==<br />
<br />
The following are reported battery runtimes:<br />
<br />
{| class="wikitable" style="text-align:left"<br />
|+Battery runtimes<br />
|-<br />
! Task !! Series !! Wireless !! Screen Brightness !! FSB Speed !! Fan Speed !! Runtime !! Comments<br />
|-<br />
! DVD Playback<br />
| 701 || On || Max || 85mhz || 100% || 134min || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! DVD Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! AVI Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading AVI from SSD<br />
|-<br />
! IM and Surf<br />
| 701 || On || ~30% || ??? || low || 173min || Normal web-browsing, Flash should reduce runtime a lot !<br />
|}<br />
<br />
N.B. - Will add battery runtimes as I am able to test them, please contribute.<br />
-- Grecko.1</div>Hiperi0nhttps://wiki.archlinux.org/index.php?title=Talk:ASUS_Eee_PC_901&diff=50795Talk:ASUS Eee PC 9012008-10-07T13:34:46Z<p>Hiperi0n: What about the 1000/1000H?</p>
<hr />
<div>What dependencies do people supposedly need to recompile the stock kernel for? (section Option 1: Compile and customize the stock kernel) I didn't recompile my kernel on my 901 and everything I can think of works fine. I think this section should be changed or clarified to explain why its recommended to recompile.<br />
<br />
--[[User:Chori|Chori]] 13:29, 23 September 2008 (EDT)<br />
There are some patches applied to the kernel source: in particular, to the acpi driver, to the mouse driver, to the rt2860sta driver, to improve them, fix bugs, and add functionality. It's true that you can run ArchLinux on the EEE 901 with just the stock kernel; but it's not optimized for it, and many users have experienced problems. Your point is well-taken, however, I'll clarify that section.<br />
<br />
== What about the 1000/1000H? ==<br />
<br />
In all the article only the 901 model is commented. In my opinion, as all the things also apply to the 1000/1000H models (I guess) it should be corrected, for example, writing 901/1000/1000H where 901 is.</div>Hiperi0n