https://wiki.archlinux.org/api.php?action=feedcontributions&user=Ekuber&feedformat=atomArchWiki - User contributions [en]2024-03-29T15:04:44ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=74975ASUS Eee PC 7012009-09-01T23:18:29Z<p>Ekuber: </p>
<hr />
<div>{{stub}}<br />
[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Русский|Инсталляция Arch Linux на Asus EEE PC}}<br />
{{i18n_links_end}}<br />
<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 />
Users of 901/1000 series Eee PCs should follow the [[Asus Eee PC 901|work in progress guide]].<br />
User of S101 could also check [[Asus Eee PC S101|work in progress guide]]<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, although this is being contested (see [http://wiki.eeeuser.com/ssd_write_limit this link] and [http://www.storagesearch.com/ssdmyths-endurance.html this other link]).<br />
<br />
Some other minor modifications can be made to decrease number of non-mandatory writes by applications: deactivate {{Filename|~/.viminfo}} in vi, deactivate less history file ({{Filename|~/.lesshst}}), and so on.<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 />
# [[PXE|Network (PXE)]]<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 (or at least it should, mine didn't, to be on the safe side, get toofishes' kernel &ndash; see below, before you get on with it). 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 />
'''Non-FTP install only:'''<br />
<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 />
# mount /dev/sd[x] /src<br />
<br />
===Start the Installation===<br />
Just run:<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 />
If you have an old arch and intend to use wired lan, then you'll need the ''atl2'' package (wired lan works out of the box on the newer kernels)<br />
<br />
===Install Customized Kernel or Keep stock Kernel===<br />
'''Finish the installation using the beginner's guide and reboot into your fresh install.'''<br />
<br />
At this point you can either continue and install a third party kernel that has been customized for the eee, or skip the next section and use the stock kernel. Note that the latest kernel supports most features straight out of the box, and so using the stock kernel should cause no major issues with modules.<br />
<br />
While the customized kernel makes things easier because you don't need to recompile unsupported modules after every major kernel update or reinstall them after every minor one; the stock kernel will always be up to date, have the latest patches and be fully compatible with arch's base system (that's not to say that kernel-eee won't). <br />
<br />
If you want to use the stock kernel (recommended) then just run a standard install and skip down to the Xorg setup section of this article.<br />
<br />
{{Note | You may have trouble with the stock kernel, especially if you are installing Arch onto an SD card.}}<br />
<br />
====Install Customized Kernel and All the Necessary Modules====<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 {{Filename|/etc/pacman.conf}} to use the repository.<br />
<br />
======Package List======<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' &ndash; customized kernel for Eee &ndash; it also contains the wireless, to load it, type modprobe ath5k or/and add it to MODULES line in {{Filename|[[rc.conf]]}} or/and use MOD_AUTOLOAD.<br />
*'''luvcview''' &ndash; webcam program for testing webcam driver<br />
<br />
======Installation Instruction======<br />
Simply use pacman to install the package you need. Install the packages with this command:<br />
# pacman -Sy kernel-eee<br />
<br />
Then, add the following to {{Filename|/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 />
====Using stock kernel====<br />
'''If you used the custom kernel above, skip this section.'''<br />
<br />
The stock kernel now supports wifi and acpi as standard (confirmed on the 701)<br />
<br />
===Small BIOS notice===<br />
<br />
Your wireless card might not turn on by default, if you want it to power up on boot, go to BIOS, the device tab, and make sure Wireless is enabled. Maybe you can try {{Codeline|"echo 1 > /sys/class/rfkill/rfkill0/state"}} too.<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 {{Filename|/etc/fstab}}:<br />
<br />
* Add "noatime" and "nodiratime" 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: {{Codeline|"tmpfs /var/log tmpfs size&#61;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 &ndash; the newer '''xf86-video-intel''' driver, or the older '''xf86-video-i810''' driver paired with 915resolution. The Intel driver is the focus upstream and is being actively developed so it is your best choice. (Note that as of 24th Feb 2009 only the xf86-video-intel driver is available through the standard repositories.)<br />
<br />
For just a basic X Server you need to install the xorg package:<br />
# pacman -Sy xorg<br />
<br />
To install the Intel graphics drivers:<br />
# pacman -Sy xf86-video-intel<br />
<br />
You may also wish to install the Synaptics drivers for the touchpad (not needed for EEE PC 900):<br />
# pacman -Sy xf86-input-synaptics<br />
<br />
<br />
If you choose to use the older i810 video, you will have to install xf86-video-i810 and 915resolution as well. <br />
'''Note''' that the i810 driver and the intel driver cannot both be installed at the same time.<br />
<br />
If you are not able to use the keyboard or the mouse you may also need to install the following packages, especially if you are getting errors like {{Codeline|"(EE) Failed to load module "Keyboard" (module does not exist, 0)"}}.<br />
<br />
# pacman -Sy xf86-input-keyboard xf86-input-mouse<br />
<br />
Then either drop the example Xorg configuration below into your {{Filename|/etc/X11/xorg.conf}} file OR use an automated Xorg configuration system. You can automatically generate an xorg.conf file, by running the following command:<br />
<br />
# Xorg -configure<br />
<br />
<br />
'''Example Xorg configuration:'''<br />
<br />
<pre><br />
Section "ServerLayout"<br />
Identifier "Arch Linux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<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 />
Option "AutoAddDevices" "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" "60"<br />
Option "RightEdge" "1070"<br />
Option "TopEdge" "90"<br />
Option "BottomEdge" "680"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "HorizEdgeScroll" "1"<br />
Option "VertEdgeScroll" "1" <br />
Option "RBCornerButton" "0"<br />
Option "RTCornerButton" "0"<br />
Option "MaxSpeed" "0.9"<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 />
The synaptics stuff can be removed if you have a EEE PC 900. The {{Codeline|Option "AutoAddDevices"}} line is important if you need a non-default XkbLayout, because if you don't have it, xorg will find 3 keyboards (at least with the 900 model).<br />
The Modeline has obviously to be removed or modified if you dont have a model with this resolution.<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 {{Filename|/etc/conf.d/915resolution}} to look like this:<br />
<br />
# Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
<br />
Now put the 915resolution daemon into your {{Filename|/etc/rc.conf}} file:<br />
<br />
DAEMONS=(... 915resolution ...)<br />
<br />
<br />
<br />
'''EDIT''' as of 08/15/09<br />
<br />
On the EEE PC 701 8gb the xf86-video-intel driver works. No need for xf86-input-keyboard or xf86-input-mouse.<br />
But to get the new X working use the following instead of "Xorg -configure":<br />
* http://wiki.archlinux.org/index.php/Xorg#Without_xorg.conf<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 {{Filename|/etc/modprobe.conf}} the following line for the EeePC 701<br />
options snd-hda-intel model=3stack-dig<br />
or the following one for the EeePC 900 model<br />
options snd-hda-intel model=auto<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 {{Filename|/etc/rc.local}} file.<br />
<br />
echo 1 > /sys/devices/platform/eeepc/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 />
$ uvcdynctrl --set "Exposure, Auto" 4<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 {{Filename|/etc/asound.state}} the following, change the 2 "false" to "true" like showing:<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....<br />
<br />
4. After editing run following as root<br />
# alsactl restore<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 (wifi, brightness, volume etc), an OSD, and be able to assign actions to things like the powerbutton and closing the lid, then you should install '''ighea's acpi-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 {{Filename|/etc/acpi/eee.conf}} to suit your tastes.<br />
<br />
*For those who use the wireless on/off acpi command; the {{Codeline|NETWORK_UP_COMMAND&#61;""}} setting in {{Filename|/etc/acpi/eee.conf}}, when applicable, should at least release the network. For example, using netcfg2, {{Codeline|NETWORK_UP_COMMAND&#61;"netcfg2 -a"}} will release the connections from before disabling wireless, allowing new ones to be made without netcfg thinking that it's already connected. It is also possible to reconnect to your previous network, however, the network tool you use needs to have a somewhat lengthy timeout as it takes 15-20 seconds for your wireless device to reappear. <br />
<br />
{{Note | Make sure '''asusosd''' is enabled on startup if you want to have the Graphic Indicators from Xandros. To run asusosd simply type {{Codeline|asusosd &}} at a command prompt.}}<br />
<br />
==== dkite's acpid_eee ====<br />
'''OUT OF DATE'''<br />
<br />
While everyone should be using ighea's acpi and dkite's acpi no longer functions properly; for development purposes and historical reasons, dkite's out of date acpi package is available on his [http://members.shaw.ca/dkite/ website].<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/cgit/dan/eee.git<br />
<br />
There are two ways to tweak the kernel. The first is simply to edit the {{Filename|kernelconfig}} file with your favorite editor and the second is to insert a {{Codeline|make menuconfig}} 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 {{Filename|kernelconfig}} file 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 />
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 />
<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 />
# pacman -S sudo<br />
<br />
As root, do the following:<br />
# visudo<br />
<br />
Add the following line to the file:<br />
USER HOST = NOPASSWD: /sbin/poweroff<br />
<br />
Where {{Codeline|USER}} is the user you want to be able to power down with and {{Codeline|HOST}} is your hostname (from {{Filename|/etc/rc.conf}}).<br />
<br />
Now, create a file called {{Filename|/etc/acpi/events/power}}, containing:<br />
# /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<br />
<br />
Make sure that you execute:<br />
# /etc/rc.d/acpid start<br />
<br />
And/or add acpid to the daemons list in {{Filename|/etc/rc.conf}}:<br />
DAEMONS=(hal, acpid ...)<br />
<br />
===Use cpufreq for power saving===<br />
<br />
{{Note | toofishes dropped CPU scaling from his latest kernel builds, due to the fact, confirmed by other users, that there were no effective power savings with p4-clockmod's module, and it introduced "unacceptable latency", even with relatively low percentage up thresholds.}}<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 {{Filename|/etc/rc.conf}} MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
<br />
Add 'cpufreq' to the DAEMONS array in {{Filename|/etc/rc.conf}} to have it start on startup.<br />
DAEMONS=(... cpufreq ...)<br />
<br />
Add the following into {{Filename|/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 />
{{Note | The merits of p4-clockmod are debatable. Particularly on the EEEPC 701, battery time isn't extended due to its usage, and some users have even reported less battery duration. More hints to the reasons why can be read in [http://www.codemonkey.org.uk/2009/01/18/forthcoming-p4clockmod/ this] fine blog entry.}}<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 />
<br />
Try changing this value:<br />
$ sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
<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 {{Filename|/etc/rc.local}}) if you wish to keep it, for example:<br />
<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 />
<br />
Also, following line is also reported to help makes system more responsive. You can use it by adding it to your {{Filename|/etc/rc.local}}:<br />
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate<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 {{Filename|[[rc.conf]]}}:<br />
...<br />
MOD_AUTOLOAD="no"<br />
...<br />
MODULES=(pciehp ath5k)<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 BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USB stick formatted in FAT32. To format the USBStick, use the cfdisk tool:<br />
# cfdisk /dev/sdc # could be something else than "c"<br />
<br />
Choose [delete], [type]: "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
NOTE to EEE PC 900 owners and possibly others: Using this method will require a flash drive formatted with a '''FAT16''' file-system. If the BIOS update process hangs up at "Reading file 900.ROM" for more than a few minutes then it should be safe to power down your EEE PC and reformat your flashdrive's file-system to the correct one. You can force FAT16 creation with the following command:<br />
# mkdosfs -F 16 /dev/device-path<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
$ cp /somewhere/blabla/.../thecurrentnameofthefile.ROM /path/to/mounted/usb_stick/701.rom<br />
The name of the copy '''must''' be xxxx.rom where xxxx is the model of your eee PC. (i.e. 900 users it's 900.rom)<br />
<br />
Next step, reboot the eeepc with the USB stick pluged-in, and press Alt+F2. 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 usable font sizes ===<br />
<br />
====The_glu's method====<br />
<br />
I found an easy solution that works on a 901:<br />
<br />
Edit {{Filename|/etc/X11/xinit/xserverrc}} and add "-dpi 134":<br />
exec /usr/bin/X -nolisten tcp -dpi 134<br />
<br />
Restart X and fonts should have the correct size. Notice it's won't works if you have Xft*dpi: in your {{Filename|.XDefaults}}.<br />
<br />
You don't need to edit your config file to set a smaller font size, I you did you should set font-size to 10 or you will have to small fonts...<br />
<br />
==== Old method ====<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 {{Filename|~/.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 {{Filename|~/.gtkrc-2.0}} (note that 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 {{Filename|~/.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 />
==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 {{Filename|/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 includes 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 />
# 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 {{Filename|/etc/pacman.conf}} to hold packages from being accidentally updated.<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 {{Filename|/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 />
<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 {{Filename|/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 {{Filename|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 {{Filename|/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 />
The command to do this is:<br />
echo 1 >/sys/bus/usb/devices/.../power/persist<br />
<br />
Replace the {{Codeline|"..."}} with the device like 1-3 or 1-5 where the first number is the bus and the second is the device <br />
<br />
Each device that is connected to your computer gets an entry in the sysfs "system file system" it is a virtual file system like proc<br />
<br />
More info:<br />
*http://www.mjmwired.net/kernel/Documentation/usb/persist.txt<br />
*http://forum.eeeuser.com/viewtopic.php?id=22712<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 />
/usr/sbin/s2ram --force --vbe_post --vbe_mode<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 />
! Programming and PDF reading<br />
| 1000HA || Off || ~40% || ??? || low || +6hs || Using Evince and SPE under XFCE with camera and USB disabled<br />
|-<br />
! Surf and OOo<br />
| 1000HA || On || ~40% || ??? || low || +4hs || Stock kernel without laptop-mode<br />
|-<br />
! Surf and OOo<br />
| 1000HA || On || ~40% || ??? || low || 5hs || Stock kernel with laptop-mode and other tweaks<br />
|}<br />
<br />
N.B. - Will add battery runtimes as I am able to test them, please contribute.<br />
<br />
-- Grecko.1<br />
<br />
Still tweaking, but disabling everything from BIOS got me about 6 hours and a half. With eee-kernel, I *could* get a little more.<br />
<br />
-- ekuber</div>Ekuberhttps://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=74973ASUS Eee PC 7012009-09-01T23:17:11Z<p>Ekuber: added 1000HA battery duration</p>
<hr />
<div>{{stub}}<br />
[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Русский|Инсталляция Arch Linux на Asus EEE PC}}<br />
{{i18n_links_end}}<br />
<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 />
Users of 901/1000 series Eee PCs should follow the [[Asus Eee PC 901|work in progress guide]].<br />
User of S101 could also check [[Asus Eee PC S101|work in progress guide]]<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, although this is being contested (see [http://wiki.eeeuser.com/ssd_write_limit this link] and [http://www.storagesearch.com/ssdmyths-endurance.html this other link]).<br />
<br />
Some other minor modifications can be made to decrease number of non-mandatory writes by applications: deactivate {{Filename|~/.viminfo}} in vi, deactivate less history file ({{Filename|~/.lesshst}}), and so on.<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 />
# [[PXE|Network (PXE)]]<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 (or at least it should, mine didn't, to be on the safe side, get toofishes' kernel &ndash; see below, before you get on with it). 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 />
'''Non-FTP install only:'''<br />
<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 />
# mount /dev/sd[x] /src<br />
<br />
===Start the Installation===<br />
Just run:<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 />
If you have an old arch and intend to use wired lan, then you'll need the ''atl2'' package (wired lan works out of the box on the newer kernels)<br />
<br />
===Install Customized Kernel or Keep stock Kernel===<br />
'''Finish the installation using the beginner's guide and reboot into your fresh install.'''<br />
<br />
At this point you can either continue and install a third party kernel that has been customized for the eee, or skip the next section and use the stock kernel. Note that the latest kernel supports most features straight out of the box, and so using the stock kernel should cause no major issues with modules.<br />
<br />
While the customized kernel makes things easier because you don't need to recompile unsupported modules after every major kernel update or reinstall them after every minor one; the stock kernel will always be up to date, have the latest patches and be fully compatible with arch's base system (that's not to say that kernel-eee won't). <br />
<br />
If you want to use the stock kernel (recommended) then just run a standard install and skip down to the Xorg setup section of this article.<br />
<br />
{{Note | You may have trouble with the stock kernel, especially if you are installing Arch onto an SD card.}}<br />
<br />
====Install Customized Kernel and All the Necessary Modules====<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 {{Filename|/etc/pacman.conf}} to use the repository.<br />
<br />
======Package List======<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' &ndash; customized kernel for Eee &ndash; it also contains the wireless, to load it, type modprobe ath5k or/and add it to MODULES line in {{Filename|[[rc.conf]]}} or/and use MOD_AUTOLOAD.<br />
*'''luvcview''' &ndash; webcam program for testing webcam driver<br />
<br />
======Installation Instruction======<br />
Simply use pacman to install the package you need. Install the packages with this command:<br />
# pacman -Sy kernel-eee<br />
<br />
Then, add the following to {{Filename|/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 />
====Using stock kernel====<br />
'''If you used the custom kernel above, skip this section.'''<br />
<br />
The stock kernel now supports wifi and acpi as standard (confirmed on the 701)<br />
<br />
===Small BIOS notice===<br />
<br />
Your wireless card might not turn on by default, if you want it to power up on boot, go to BIOS, the device tab, and make sure Wireless is enabled. Maybe you can try {{Codeline|"echo 1 > /sys/class/rfkill/rfkill0/state"}} too.<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 {{Filename|/etc/fstab}}:<br />
<br />
* Add "noatime" and "nodiratime" 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: {{Codeline|"tmpfs /var/log tmpfs size&#61;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 &ndash; the newer '''xf86-video-intel''' driver, or the older '''xf86-video-i810''' driver paired with 915resolution. The Intel driver is the focus upstream and is being actively developed so it is your best choice. (Note that as of 24th Feb 2009 only the xf86-video-intel driver is available through the standard repositories.)<br />
<br />
For just a basic X Server you need to install the xorg package:<br />
# pacman -Sy xorg<br />
<br />
To install the Intel graphics drivers:<br />
# pacman -Sy xf86-video-intel<br />
<br />
You may also wish to install the Synaptics drivers for the touchpad (not needed for EEE PC 900):<br />
# pacman -Sy xf86-input-synaptics<br />
<br />
<br />
If you choose to use the older i810 video, you will have to install xf86-video-i810 and 915resolution as well. <br />
'''Note''' that the i810 driver and the intel driver cannot both be installed at the same time.<br />
<br />
If you are not able to use the keyboard or the mouse you may also need to install the following packages, especially if you are getting errors like {{Codeline|"(EE) Failed to load module "Keyboard" (module does not exist, 0)"}}.<br />
<br />
# pacman -Sy xf86-input-keyboard xf86-input-mouse<br />
<br />
Then either drop the example Xorg configuration below into your {{Filename|/etc/X11/xorg.conf}} file OR use an automated Xorg configuration system. You can automatically generate an xorg.conf file, by running the following command:<br />
<br />
# Xorg -configure<br />
<br />
<br />
'''Example Xorg configuration:'''<br />
<br />
<pre><br />
Section "ServerLayout"<br />
Identifier "Arch Linux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<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 />
Option "AutoAddDevices" "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" "60"<br />
Option "RightEdge" "1070"<br />
Option "TopEdge" "90"<br />
Option "BottomEdge" "680"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "HorizEdgeScroll" "1"<br />
Option "VertEdgeScroll" "1" <br />
Option "RBCornerButton" "0"<br />
Option "RTCornerButton" "0"<br />
Option "MaxSpeed" "0.9"<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 />
The synaptics stuff can be removed if you have a EEE PC 900. The {{Codeline|Option "AutoAddDevices"}} line is important if you need a non-default XkbLayout, because if you don't have it, xorg will find 3 keyboards (at least with the 900 model).<br />
The Modeline has obviously to be removed or modified if you dont have a model with this resolution.<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 {{Filename|/etc/conf.d/915resolution}} to look like this:<br />
<br />
# Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
<br />
Now put the 915resolution daemon into your {{Filename|/etc/rc.conf}} file:<br />
<br />
DAEMONS=(... 915resolution ...)<br />
<br />
<br />
<br />
'''EDIT''' as of 08/15/09<br />
<br />
On the EEE PC 701 8gb the xf86-video-intel driver works. No need for xf86-input-keyboard or xf86-input-mouse.<br />
But to get the new X working use the following instead of "Xorg -configure":<br />
* http://wiki.archlinux.org/index.php/Xorg#Without_xorg.conf<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 {{Filename|/etc/modprobe.conf}} the following line for the EeePC 701<br />
options snd-hda-intel model=3stack-dig<br />
or the following one for the EeePC 900 model<br />
options snd-hda-intel model=auto<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 {{Filename|/etc/rc.local}} file.<br />
<br />
echo 1 > /sys/devices/platform/eeepc/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 />
$ uvcdynctrl --set "Exposure, Auto" 4<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 {{Filename|/etc/asound.state}} the following, change the 2 "false" to "true" like showing:<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....<br />
<br />
4. After editing run following as root<br />
# alsactl restore<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 (wifi, brightness, volume etc), an OSD, and be able to assign actions to things like the powerbutton and closing the lid, then you should install '''ighea's acpi-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 {{Filename|/etc/acpi/eee.conf}} to suit your tastes.<br />
<br />
*For those who use the wireless on/off acpi command; the {{Codeline|NETWORK_UP_COMMAND&#61;""}} setting in {{Filename|/etc/acpi/eee.conf}}, when applicable, should at least release the network. For example, using netcfg2, {{Codeline|NETWORK_UP_COMMAND&#61;"netcfg2 -a"}} will release the connections from before disabling wireless, allowing new ones to be made without netcfg thinking that it's already connected. It is also possible to reconnect to your previous network, however, the network tool you use needs to have a somewhat lengthy timeout as it takes 15-20 seconds for your wireless device to reappear. <br />
<br />
{{Note | Make sure '''asusosd''' is enabled on startup if you want to have the Graphic Indicators from Xandros. To run asusosd simply type {{Codeline|asusosd &}} at a command prompt.}}<br />
<br />
==== dkite's acpid_eee ====<br />
'''OUT OF DATE'''<br />
<br />
While everyone should be using ighea's acpi and dkite's acpi no longer functions properly; for development purposes and historical reasons, dkite's out of date acpi package is available on his [http://members.shaw.ca/dkite/ website].<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/cgit/dan/eee.git<br />
<br />
There are two ways to tweak the kernel. The first is simply to edit the {{Filename|kernelconfig}} file with your favorite editor and the second is to insert a {{Codeline|make menuconfig}} 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 {{Filename|kernelconfig}} file 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 />
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 />
<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 />
# pacman -S sudo<br />
<br />
As root, do the following:<br />
# visudo<br />
<br />
Add the following line to the file:<br />
USER HOST = NOPASSWD: /sbin/poweroff<br />
<br />
Where {{Codeline|USER}} is the user you want to be able to power down with and {{Codeline|HOST}} is your hostname (from {{Filename|/etc/rc.conf}}).<br />
<br />
Now, create a file called {{Filename|/etc/acpi/events/power}}, containing:<br />
# /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<br />
<br />
Make sure that you execute:<br />
# /etc/rc.d/acpid start<br />
<br />
And/or add acpid to the daemons list in {{Filename|/etc/rc.conf}}:<br />
DAEMONS=(hal, acpid ...)<br />
<br />
===Use cpufreq for power saving===<br />
<br />
{{Note | toofishes dropped CPU scaling from his latest kernel builds, due to the fact, confirmed by other users, that there were no effective power savings with p4-clockmod's module, and it introduced "unacceptable latency", even with relatively low percentage up thresholds.}}<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 {{Filename|/etc/rc.conf}} MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
<br />
Add 'cpufreq' to the DAEMONS array in {{Filename|/etc/rc.conf}} to have it start on startup.<br />
DAEMONS=(... cpufreq ...)<br />
<br />
Add the following into {{Filename|/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 />
{{Note | The merits of p4-clockmod are debatable. Particularly on the EEEPC 701, battery time isn't extended due to its usage, and some users have even reported less battery duration. More hints to the reasons why can be read in [http://www.codemonkey.org.uk/2009/01/18/forthcoming-p4clockmod/ this] fine blog entry.}}<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 />
<br />
Try changing this value:<br />
$ sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
<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 {{Filename|/etc/rc.local}}) if you wish to keep it, for example:<br />
<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 />
<br />
Also, following line is also reported to help makes system more responsive. You can use it by adding it to your {{Filename|/etc/rc.local}}:<br />
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate<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 {{Filename|[[rc.conf]]}}:<br />
...<br />
MOD_AUTOLOAD="no"<br />
...<br />
MODULES=(pciehp ath5k)<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 BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USB stick formatted in FAT32. To format the USBStick, use the cfdisk tool:<br />
# cfdisk /dev/sdc # could be something else than "c"<br />
<br />
Choose [delete], [type]: "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
NOTE to EEE PC 900 owners and possibly others: Using this method will require a flash drive formatted with a '''FAT16''' file-system. If the BIOS update process hangs up at "Reading file 900.ROM" for more than a few minutes then it should be safe to power down your EEE PC and reformat your flashdrive's file-system to the correct one. You can force FAT16 creation with the following command:<br />
# mkdosfs -F 16 /dev/device-path<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
$ cp /somewhere/blabla/.../thecurrentnameofthefile.ROM /path/to/mounted/usb_stick/701.rom<br />
The name of the copy '''must''' be xxxx.rom where xxxx is the model of your eee PC. (i.e. 900 users it's 900.rom)<br />
<br />
Next step, reboot the eeepc with the USB stick pluged-in, and press Alt+F2. 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 usable font sizes ===<br />
<br />
====The_glu's method====<br />
<br />
I found an easy solution that works on a 901:<br />
<br />
Edit {{Filename|/etc/X11/xinit/xserverrc}} and add "-dpi 134":<br />
exec /usr/bin/X -nolisten tcp -dpi 134<br />
<br />
Restart X and fonts should have the correct size. Notice it's won't works if you have Xft*dpi: in your {{Filename|.XDefaults}}.<br />
<br />
You don't need to edit your config file to set a smaller font size, I you did you should set font-size to 10 or you will have to small fonts...<br />
<br />
==== Old method ====<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 {{Filename|~/.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 {{Filename|~/.gtkrc-2.0}} (note that 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 {{Filename|~/.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 />
==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 {{Filename|/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 includes 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 />
# 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 {{Filename|/etc/pacman.conf}} to hold packages from being accidentally updated.<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 {{Filename|/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 />
<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 {{Filename|/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 {{Filename|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 {{Filename|/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 />
The command to do this is:<br />
echo 1 >/sys/bus/usb/devices/.../power/persist<br />
<br />
Replace the {{Codeline|"..."}} with the device like 1-3 or 1-5 where the first number is the bus and the second is the device <br />
<br />
Each device that is connected to your computer gets an entry in the sysfs "system file system" it is a virtual file system like proc<br />
<br />
More info:<br />
*http://www.mjmwired.net/kernel/Documentation/usb/persist.txt<br />
*http://forum.eeeuser.com/viewtopic.php?id=22712<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 />
/usr/sbin/s2ram --force --vbe_post --vbe_mode<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 />
! Programming and PDF reading<br />
| 1000HA || Off || ~40% || ??? || low || +6hs || Using Evince and SPE under XFCE with camera and USB disabled<br />
|-<br />
! Surf and OOo<br />
| 1000HA || On || ~40% || ??? || low || +4hs || Stock kernel without laptop-mode<br />
|-<br />
! Surf and OOo<br />
| 1000HA || On || ~40% || ??? || low || 5hs || Stock kernel with laptop-mode and other tweaks<br />
|}<br />
<br />
N.B. - Will add battery runtimes as I am able to test them, please contribute.<br />
ekuber - Still tweaking, but disabling everything from BIOS got me about 6 hours and a half. With eee-kernel, I *could* get a little more.<br />
-- Grecko.1</div>Ekuberhttps://wiki.archlinux.org/index.php?title=USB_Installation_Media_(Espa%C3%B1ol)&diff=73522USB Installation Media (Español)2009-08-08T14:50:26Z<p>Ekuber: /* La nueva y mejorada manera, bajo GNU/Linux */</p>
<hr />
<div>[[Category:Obteniendo e instalando Arch (Español)]]<br />
[[Category:CÓMOs (Español)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Install from USB stick}}<br />
{{i18n_entry|Türkçe|USB' den Kurulum (Türkçe)}}<br />
{{i18n_entry|Español|Cómo instalar desde pendrive (Español)}}<br />
{{i18n_links_end}}<br />
<br />
== La nueva y mejorada manera, bajo GNU/Linux ==<br />
<br />
Desde la versión de 2008.06, se proveen imágenes de disco para unidades flash USB. Pueden descargarse desde tu [http://archlinux.org/download/ mirror local] (son los archivos .img). Para instalar, primero asegúrate que el dispositivo USB se encuentra desmontado y ejecuta el siguiente comando (como ''root''):<br />
<br />
dd bs=8M if=image.img of=/dev/sd[x]<br />
<br />
donde ''image.img'' es la ruta del archivo img y ''/dev/sd[x]'' es tu dispositivo USB. *'''''Asegúrate de usar /dev/sdx y no /dev/sdx1.''''' '''¡Este es un error muy común!'''<br />
<br />
{{Warning|Este comando eliminará toda la información en tu pendrive. Asegúrese de realizar un backup.}}<br />
<br />
===UNetBootin===<br />
<br />
Otra manera de volver el dispositivo USB booteable, es usando [http://unetbootin.sourceforge.net/ UNetBootin]. Esta aplicación puede descargar una gran cantidad de distribuciones para grabar en tu disco. También puedes proveer tu propio archivo de imágen, el cual no no es necesario que sea una imagen especial para USB.<br />
<br />
== La nueva y mejorada manera, bajo Mac OS X ==<br />
<br />
Para utilizar dd en tu dispositivo USB bajo Mac es necesario realizar algunas "maniobras especiales". Primero, conecta tu dispositivo USB, OS X lo automontará, y ejecuta <br />
<br />
diskutil list<br />
<br />
en ''Terminal.app''. Debes averiguar como se llama el dispositivo conectado - el mío se llamaba ''/dev/disk1''. Una vez hecho esto, ejecuta <br />
<br />
diskutil unmountDisk /dev/disk1<br />
<br />
para desmontar las particiones del dispositivo (por ejemplo, /dev/disk1s1) pero manteniendo el dispositivo (por ejemplo, /dev/disk1). Ahora podemos continuar de los mismos pasos que para GNU/Linux que se encuentran arriba (pero usando bs=8192 si estas usando el dd de OS X, el número proviene de 1024*8).<br />
<br />
== La nueva y mejorada manera, bajo Windows ==<br />
<br />
Para escribir una imagen USB bajo Windows, es necesaria la aplicación [http://shounen.ru/soft/flashnul/ flashnul] ([http://translate.google.com/translate?u=http%3A%2F%2Fshounen.ru%2Fsoft%2Fflashnul%2F&hl=es&ie=UTF8&sl=ru&tl=es versión traducida al español de la página]), [http://www.4shared.com/file/70261292/1d43b6a9/flashnul-09.html/ también disponible aquí], o [http://www.cygwin.com/ Cygwin].<br />
<br />
=== Usando Flashnul ===<br />
<br />
Desde la consola, ejecuta flashnul con -p para determinar el índice de tu dispositivo USB. Por ejemplo, al ejecutarlo en mi máquina, esto es lo que obtengo:<br />
<br />
C:\>flashnul -p<br />
<br />
Avaible [sic] physical drives:<br />
0 size = 200048565760 (186 Gb)<br />
1 size = 400088457216 (372 Gb)<br />
2 size = 400088457216 (372 Gb)<br />
3 size = 4060086272 (3872 Mb)<br />
<br />
En mi caso, con un disco USB de 4 GB, el índice del dispositivo es 3.<br />
<br />
Cuando hallas determinado cual el dispositivo correcto, puedes escribir la imagen a tu disco, invocando ''flashnul'' con el índice correspondiente, -L, y la ruta al archivo de imagen. Por ejemplo,<br />
<br />
C:\>flashnul 3 -L path/to/arch/usb.img<br />
<br />
En caso de que estés seguro de lo que estás haciendo, tipea ''yes'', y espera a que termine de escribir al dispositivo. Si te da error de acceso al dispositivo, desconectar y reconectar el pendrive me funcionó.<br />
<br />
<b>¡Atención!</b><br />
<i>Yo tuve que ejecutarlo con "C:\flashnul\flashnul.exe <b>H:</b> -L c:\archlinux-2008.06-core-i686.img" para que funcione. De otra manera me tiraba constantemente error. -gejr </i><br />
<br />
=== Usando Cygwin ===<br />
<br />
Make sure your cygwin installation contains the dd package.<br />
<br />
Place your image file in your home directory, in my case it is:<br />
<br />
C:\cygwin\home\John\<br />
<br />
Run cygwin as administrator (required for cygwin to access hardware). To write to your USB drive use the following command:<br />
<br />
dd if=image.img of=\\.\[x]:<br />
<br />
where image.img is the path to the img file within the cygwin directory and \\.\[x]: is your USB device where x is the windows designated letter, in my case "\\.\d:".<br />
<br />
'''Note:''' This will irrevocably delete all files on your USB stick, so make sure you don't have any important files on the stick before doing this.<br />
<br />
===UNetBootin===<br />
<br />
Otra manera de volver el dispositivo USB booteable, es usando [http://unetbootin.sourceforge.net/ UNetBootin]. Esta aplicación puede descargar una gran cantidad de distribuciones para grabar en tu disco. También puedes proveer tu propio archivo de imágen, el cual no no es necesario que sea una imagen especial para USB.<br />
<br />
==Método viejo desde imagen ISO (cd), deprecado==<br />
*Preparar el pendrive:<br />
El archivo de imagen arch-ftp.img pesa alrededor de 150 MB, por lo que puede copiarse en un pendrive de 256 MB. El archivo de imagen arch-core.img pesa alrededor de ~300 MB, por lo que requiere un pendrive de 512 MB.<br />
<br />
1. Particionar el pendrive.<br />
Crear una partición de tipo FAT16, y hacerlo booteable. Recuerda su nombre, por ejemplo, /dev/sd[x]1.<br />
<br />
cfdisk /dev/sd[x]<br />
<br />
2. Crea un sistema de archivos FAT16 (es necesario tener instaladas las dosfstools)<br />
<br />
mkdosfs /dev/sd[x]1<br />
<br />
3. Obtener la ISO correspondiente desde www.archlinux.org<br />
<br />
4. Montar la ISO en un directorio temporario<br />
<br />
mkdir -p /mnt/archcd<br />
mount -o loop /Path/to/iso /mnt/archcd<br />
<br />
5. Montar el pendrive<br />
<br />
mkdir -p /mnt/usb/<br />
mount /dev/sd[x]1 /mnt/usb/<br />
<br />
6. Copiar la iso al pendrive<br />
<br />
cp -ra /mnt/archcd/* /mnt/usb/<br />
<br />
<br />
7. Copiar la información de booteo<br />
<br />
cd /mnt/usb/isolinux/<br />
cp vmlinuz /mnt/usb/<br />
cp initrd.img /mnt/usb/<br />
cp boot.* /mnt/usb/<br />
cp isolinux.cfg /mnt/usb/syslinux.cfg<br />
<br />
8. Instalar lilo y syslinux<sup>(1)</sup><br />
<br />
lilo -M /dev/sd[x] mbr<br />
syslinux -s /dev/sd[x]1<br />
<br />
===Luego de bootear desde el pendrive:===<br />
<br />
Comenzar la instalación logueándose como root e invocar el comando "/arch/setup".<br />
<br />
El instalador debería montar el dispositivo de origen de manera automática. Si falla, es posible montar el dispositivo de origen en el pendrive manualmente con el comando:<br />
<br />
mount /dev/sd[x] /src<br />
<br />
===Notas y problemas:===<br />
<br />
<sup>(1)</sup> Usar lilo no es realmente necesario, ya que syslinux realiza acciones de carga de tipo "floppy". Pero si encuentras errores de tipo "Can't load operating system", es necesario instalarlo.<br />
<br />
<sup>(2)</sup> Si encuentras errores del tipo de "Cluster sizes larger than 16K not supported" al bootear, esto significa que es necesario instalar una versión más reciente de syslinux.<br />
<br />
<sup>(3)</sup> El espacio no utilizado en el pendrive puede ser aprovechado para guardar archivos. Utilizando una aplicación como gparted para particionar el espacio no utilizado.</div>Ekuberhttps://wiki.archlinux.org/index.php?title=USB_flash_installation_medium&diff=73478USB flash installation medium2009-08-07T22:38:28Z<p>Ekuber: added spanish version</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Install from USB stick}}<br />
{{i18n_entry|Türkçe|USB' den Kurulum (Türkçe)}}<br />
{{i18n_entry|Español|Cómo instalar desde pendrive (Español)}}<br />
{{i18n_links_end}}<br />
<br />
== The New and Improved Way, on GNU/Linux ==<br />
<br />
Beginning from release 2008.06, USB images are provided. Download them from your [http://archlinux.org/download/ local mirror] (they are the .img files). To install, first ensure the USB device is unmounted and then issue the following command:<br />
<br />
dd bs=8M if=image.img of=/dev/sd[x]<br />
<br />
where ''image.img'' is the path to the img file and ''/dev/sd[x]'' is your USB device. *'''''Make sure to use /dev/sdx and not /dev/sdx1.''''' '''This is a very common error!'''<br />
<br />
{{Warning|This will irrevocably destroy all data on your USB stick.}}<br />
<br />
===UNetBootin===<br />
<br />
Another way to make a USB drive bootable, is by using [http://unetbootin.sourceforge.net/ UNetBootin]. This application can download most distributions for you and write it to your drive. Or you can provide your own images, which does not have to be a special USB image.<br />
<br />
== The New and Improved Way, on Mac OS X ==<br />
<br />
To be able to use dd on your usb device on a Mac you have to do some special maneuvers. First of all insert your usb device, OS X will automount it, and run<br />
<br />
diskutil list<br />
<br />
in Terminal.app. Figure out what your usb device is called - mine was called /dev/disk1. Now you run<br />
<br />
diskutil unmountDisk /dev/disk1<br />
<br />
to unmount the partitions on the device (i.e., /dev/disk1s1) while keeping the device proper (i.e., /dev/disk1). Now we can continue in accordance with the Linux instructions above (but use bs=8192 if you're using the OS X dd, the number comes from 1024*8).<br />
<br />
== The New and Improved Way, on Windows ==<br />
<br />
To write the USB image on Windows, you will need [http://shounen.ru/soft/flashnul/ flashnul] ([http://translate.google.com/translate?u=http%3A%2F%2Fshounen.ru%2Fsoft%2Fflashnul%2F&hl=en&ie=UTF8&sl=ru&tl=en English version of the page]) or [http://www.cygwin.com/ Cygwin].<br />
<br />
Edit [http://www.4shared.com/file/70261292/1d43b6a9/flashnul-09.html/ Working Link] --[[User:Anonymo|Anonymo]] 10:03, 4 April 2009 (EDT)<br />
<br />
=== The Flashnul Way ===<br />
<br />
From a command prompt, invoke flashnul with -p, and determine which device index is your USB drive. For example, my output looks like this:<br />
<br />
C:\>flashnul -p<br />
<br />
Avaible [sic] physical drives:<br />
0 size = 200048565760 (186 Gb)<br />
1 size = 400088457216 (372 Gb)<br />
2 size = 400088457216 (372 Gb)<br />
3 size = 4060086272 (3872 Mb)<br />
<br />
In my case, with a 4 GB USB drive, it is device index 3.<br />
<br />
When you have determined which device is the correct one, you can write the image to your drive, by invoking flashnul with the device index, -L, and the path to your image. In my case, it would be<br />
<br />
C:\>flashnul 3 -L path/to/arch/usb.img<br />
<br />
As long as you are really sure you want to write the data, type yes, then wait a bit for it to write. If you get an access denied error, unplugging and re-attaching the drive worked for me.<br />
<br />
<b>Note!</b><br />
<i>I had to do "C:\flashnul\flashnul.exe <b>H:</b> -L c:\archlinux-2008.06-core-i686.img" for it to work. I kept getting access denied if i just used the number. -gejr </i><br />
<br />
=== The Cygwin Way ===<br />
<br />
Make sure your cygwin installation contains the dd package.<br />
<br />
Place your image file in your home directory, in my case it is:<br />
<br />
C:\cygwin\home\John\<br />
<br />
Run cygwin as administrator (required for cygwin to access hardware). To write to your USB drive use the following command:<br />
<br />
dd if=image.img of=\\.\[x]:<br />
<br />
where image.img is the path to the img file within the cygwin directory and \\.\[x]: is your USB device where x is the windows designated letter, in my case "\\.\d:".<br />
<br />
'''Note:''' This will irrevocably delete all files on your USB stick, so make sure you don't have any important files on the stick before doing this.<br />
<br />
===UNetBootin===<br />
<br />
Another way to make a USB drive bootable, is by using [http://unetbootin.sourceforge.net/ UNetBootin]. This application can download most linux distributions for you and write it to your drive. Or you can provide your own images, which does not have to be a special USB image.<br />
<br />
==Old Method from ISO, deprecated==<br />
*Prepare USB stick:<br />
The arch-ftp.img is about 150 MB, so it should fit on a 256 MB USB stick. The arch-core.img is ~300 MB and should fit on a 512 MB stick.<br />
<br />
1. Partition the USB stick.<br />
Create one partition with FAT16 type, make it bootable. Remember its name, such as /dev/sd[x]1.<br />
<br />
cfdisk /dev/sd[x]<br />
<br />
2. Make a FAT16 filesystem (you need dosfstools)<br />
<br />
mkdosfs /dev/sd[x]1<br />
<br />
3. Get the arch-base install ISO from www.archlinux.org<br />
<br />
4. Mount the iso to an temporary directory<br />
<br />
mkdir -p /mnt/archcd<br />
mount -o loop /Path/to/iso /mnt/archcd<br />
<br />
5. Mount the USB Stick<br />
<br />
mkdir -p /mnt/usb/<br />
mount /dev/sd[x]1 /mnt/usb/<br />
<br />
6. Copy the .iso to the USB Stick<br />
<br />
cp -ra /mnt/archcd/* /mnt/usb/<br />
<br />
<br />
7. Copy the boot data<br />
<br />
cd /mnt/usb/isolinux/<br />
cp vmlinuz /mnt/usb/<br />
cp initrd.img /mnt/usb/<br />
cp boot.* /mnt/usb/<br />
cp isolinux.cfg /mnt/usb/syslinux.cfg<br />
<br />
8. Install MBR and syslinux<sup>(1)</sup><br />
<br />
lilo -M /dev/sd[x] mbr<br />
syslinux -s /dev/sd[x]1<br />
<br />
===After booting from the USB stick:===<br />
<br />
Start the installation by logging in as root and invoke the command "/arch/setup".<br />
<br />
The installer should mount the 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 />
===Notes and Troubleshooting:===<br />
<br />
<sup>(1)</sup> Using lilo is not really needed because syslinux does the "floppy" loading stuff. But if you get some error like "Can't load operating system" you have to perform the lilo command.<br />
<br />
<sup>(2)</sup> If you get "Cluster sizes larger than 16K not supported" error when booting this means you need to install more recent version of syslinux.<br />
<br />
<sup>(3)</sup> Space not used on the USB stick can still be used for storing files... Use a utility like gparted and add a partition to the unused space.</div>Ekuberhttps://wiki.archlinux.org/index.php?title=USB_Installation_Media_(Espa%C3%B1ol)&diff=73477USB Installation Media (Español)2009-08-07T22:37:46Z<p>Ekuber: CÓMO: Como instalar Arch (Español)</p>
<hr />
<div>[[Category:Obteniendo e instalando Arch (Español)]]<br />
[[Category:CÓMOs (Español)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Install from USB stick}}<br />
{{i18n_entry|Türkçe|USB' den Kurulum (Türkçe)}}<br />
{{i18n_entry|Español|Cómo instalar desde pendrive (Español)}}<br />
{{i18n_links_end}}<br />
<br />
== La nueva y mejorada manera, bajo GNU/Linux ==<br />
<br />
Desde la versión de 2008.06, se proveen imágenes de disco para unidades flash USB. Pueden descargarse desde tu [http://archlinux.org/download/ mirror local] (son los archivos .img). Para instalar, primero asegúrate que el dispositivo USB se encuentra desmontado y ejecuta el siguiente comando (como ''root''):<br />
<br />
dd bs=8M if=image.img of=/dev/sd[x]<br />
<br />
donde ''image.img'' es la ruta del archivo img y ''/dev/sd[x]'' es tu dispositivo USB. *'''''Asegúrate de usar /dev/sdx y no /dev/sdx1.''''' '''¡Este es un error muy común!'''<br />
<br />
{{Cuidado|Este comando eliminará toda la información en tu pendrive. Asegúrese de realizar un backup.}}<br />
<br />
===UNetBootin===<br />
<br />
Otra manera de volver el dispositivo USB booteable, es usando [http://unetbootin.sourceforge.net/ UNetBootin]. Esta aplicación puede descargar una gran cantidad de distribuciones para grabar en tu disco. También puedes proveer tu propio archivo de imágen, el cual no no es necesario que sea una imagen especial para USB.<br />
<br />
== La nueva y mejorada manera, bajo Mac OS X ==<br />
<br />
Para utilizar dd en tu dispositivo USB bajo Mac es necesario realizar algunas "maniobras especiales". Primero, conecta tu dispositivo USB, OS X lo automontará, y ejecuta <br />
<br />
diskutil list<br />
<br />
en ''Terminal.app''. Debes averiguar como se llama el dispositivo conectado - el mío se llamaba ''/dev/disk1''. Una vez hecho esto, ejecuta <br />
<br />
diskutil unmountDisk /dev/disk1<br />
<br />
para desmontar las particiones del dispositivo (por ejemplo, /dev/disk1s1) pero manteniendo el dispositivo (por ejemplo, /dev/disk1). Ahora podemos continuar de los mismos pasos que para GNU/Linux que se encuentran arriba (pero usando bs=8192 si estas usando el dd de OS X, el número proviene de 1024*8).<br />
<br />
== La nueva y mejorada manera, bajo Windows ==<br />
<br />
Para escribir una imagen USB bajo Windows, es necesaria la aplicación [http://shounen.ru/soft/flashnul/ flashnul] ([http://translate.google.com/translate?u=http%3A%2F%2Fshounen.ru%2Fsoft%2Fflashnul%2F&hl=es&ie=UTF8&sl=ru&tl=es versión traducida al español de la página]), [http://www.4shared.com/file/70261292/1d43b6a9/flashnul-09.html/ también disponible aquí], o [http://www.cygwin.com/ Cygwin].<br />
<br />
=== Usando Flashnul ===<br />
<br />
Desde la consola, ejecuta flashnul con -p para determinar el índice de tu dispositivo USB. Por ejemplo, al ejecutarlo en mi máquina, esto es lo que obtengo:<br />
<br />
C:\>flashnul -p<br />
<br />
Avaible [sic] physical drives:<br />
0 size = 200048565760 (186 Gb)<br />
1 size = 400088457216 (372 Gb)<br />
2 size = 400088457216 (372 Gb)<br />
3 size = 4060086272 (3872 Mb)<br />
<br />
En mi caso, con un disco USB de 4 GB, el índice del dispositivo es 3.<br />
<br />
Cuando hallas determinado cual el dispositivo correcto, puedes escribir la imagen a tu disco, invocando ''flashnul'' con el índice correspondiente, -L, y la ruta al archivo de imagen. Por ejemplo,<br />
<br />
C:\>flashnul 3 -L path/to/arch/usb.img<br />
<br />
En caso de que estés seguro de lo que estás haciendo, tipea ''yes'', y espera a que termine de escribir al dispositivo. Si te da error de acceso al dispositivo, desconectar y reconectar el pendrive me funcionó.<br />
<br />
<b>¡Atención!</b><br />
<i>Yo tuve que ejecutarlo con "C:\flashnul\flashnul.exe <b>H:</b> -L c:\archlinux-2008.06-core-i686.img" para que funcione. De otra manera me tiraba constantemente error. -gejr </i><br />
<br />
=== Usando Cygwin ===<br />
<br />
Make sure your cygwin installation contains the dd package.<br />
<br />
Place your image file in your home directory, in my case it is:<br />
<br />
C:\cygwin\home\John\<br />
<br />
Run cygwin as administrator (required for cygwin to access hardware). To write to your USB drive use the following command:<br />
<br />
dd if=image.img of=\\.\[x]:<br />
<br />
where image.img is the path to the img file within the cygwin directory and \\.\[x]: is your USB device where x is the windows designated letter, in my case "\\.\d:".<br />
<br />
'''Note:''' This will irrevocably delete all files on your USB stick, so make sure you don't have any important files on the stick before doing this.<br />
<br />
===UNetBootin===<br />
<br />
Otra manera de volver el dispositivo USB booteable, es usando [http://unetbootin.sourceforge.net/ UNetBootin]. Esta aplicación puede descargar una gran cantidad de distribuciones para grabar en tu disco. También puedes proveer tu propio archivo de imágen, el cual no no es necesario que sea una imagen especial para USB.<br />
<br />
==Método viejo desde imagen ISO (cd), deprecado==<br />
*Preparar el pendrive:<br />
El archivo de imagen arch-ftp.img pesa alrededor de 150 MB, por lo que puede copiarse en un pendrive de 256 MB. El archivo de imagen arch-core.img pesa alrededor de ~300 MB, por lo que requiere un pendrive de 512 MB.<br />
<br />
1. Particionar el pendrive.<br />
Crear una partición de tipo FAT16, y hacerlo booteable. Recuerda su nombre, por ejemplo, /dev/sd[x]1.<br />
<br />
cfdisk /dev/sd[x]<br />
<br />
2. Crea un sistema de archivos FAT16 (es necesario tener instaladas las dosfstools)<br />
<br />
mkdosfs /dev/sd[x]1<br />
<br />
3. Obtener la ISO correspondiente desde www.archlinux.org<br />
<br />
4. Montar la ISO en un directorio temporario<br />
<br />
mkdir -p /mnt/archcd<br />
mount -o loop /Path/to/iso /mnt/archcd<br />
<br />
5. Montar el pendrive<br />
<br />
mkdir -p /mnt/usb/<br />
mount /dev/sd[x]1 /mnt/usb/<br />
<br />
6. Copiar la iso al pendrive<br />
<br />
cp -ra /mnt/archcd/* /mnt/usb/<br />
<br />
<br />
7. Copiar la información de booteo<br />
<br />
cd /mnt/usb/isolinux/<br />
cp vmlinuz /mnt/usb/<br />
cp initrd.img /mnt/usb/<br />
cp boot.* /mnt/usb/<br />
cp isolinux.cfg /mnt/usb/syslinux.cfg<br />
<br />
8. Instalar lilo y syslinux<sup>(1)</sup><br />
<br />
lilo -M /dev/sd[x] mbr<br />
syslinux -s /dev/sd[x]1<br />
<br />
===Luego de bootear desde el pendrive:===<br />
<br />
Comenzar la instalación logueándose como root e invocar el comando "/arch/setup".<br />
<br />
El instalador debería montar el dispositivo de origen de manera automática. Si falla, es posible montar el dispositivo de origen en el pendrive manualmente con el comando:<br />
<br />
mount /dev/sd[x] /src<br />
<br />
===Notas y problemas:===<br />
<br />
<sup>(1)</sup> Usar lilo no es realmente necesario, ya que syslinux realiza acciones de carga de tipo "floppy". Pero si encuentras errores de tipo "Can't load operating system", es necesario instalarlo.<br />
<br />
<sup>(2)</sup> Si encuentras errores del tipo de "Cluster sizes larger than 16K not supported" al bootear, esto significa que es necesario instalar una versión más reciente de syslinux.<br />
<br />
<sup>(3)</sup> El espacio no utilizado en el pendrive puede ser aprovechado para guardar archivos. Utilizando una aplicación como gparted para particionar el espacio no utilizado.</div>Ekuber