https://wiki.archlinux.org/api.php?action=feedcontributions&user=Faelar&feedformat=atom
ArchWiki - User contributions [en]
2024-03-28T18:47:05Z
User contributions
MediaWiki 1.41.0
https://wiki.archlinux.org/index.php?title=Dash_as_/bin/sh&diff=187384
Dash as /bin/sh
2012-03-03T21:01:00Z
<p>Faelar: No '-' before 'f' after '-type' in the third cmd line.</p>
<hr />
<div>[[Category:Arch development (English)]]<br />
{{expansion}}<br />
{{accuracy}}<br />
<br />
[http://en.wikipedia.org/wiki/Debian_Almquist_shell Dash] is a minimalist POSIX-complient shell. It can be much faster than Bash, and takes up less memory when in use. Most POSIX compliant scripts specify {{ic|/bin/sh}} at the first line of the script, which means it will run {{ic|/bin/sh}} as the shell, which by default in Arch is a symlink to {{ic|/bin/bash}}.<br />
<br />
You can re-symlink {{ic|/bin/sh}} to {{ic|/bin/dash}}, which can increase system performance, but first you must verify that none of the scripts that aren't explicitly #!/bin/bash scripts are safely POSIX compliant and do not require any of Bash's features. <br />
<br />
This article is for those who want to help [[dash]] become the new {{ic|/bin/sh}}.<br />
<br />
From http://article.gmane.org/gmane.linux.arch.devel/11418:<br />
*http://mailman.archlinux.org/pipermail/arch-dev-public/2007-November/003053.html<br />
*https://launchpad.net/ubuntu/+spec/dash-as-bin-sh<br />
*https://wiki.ubuntu.com/DashAsBinSh<br />
*All install scripts must be sh-compatible (or we need a way of executing non-sh scripts, there is a bug open for that)<br />
*Any daemon/init script is probably written for /bin/bash as our rc.conf and other initscripts files use bash arrays, so those need to be pointed correctly<br />
<br />
==Identifying bashisms==<br />
<br />
Features of bash that aren't included in Dash ('bashisms') will not work without being explicitly pointed to {{ic|/bin/bash}}. The following instructions will allow you to find any scripts that may need modification. <br />
<br />
Install {{AUR|checkbashisms}} from the [[AUR]].<br />
<br />
===Common places to check===<br />
<br />
*Installed scripts with a {{Ic|#!/bin/sh}} shebang:<br />
$ find {,/usr}/bin -type f \<br />
-exec grep -q -- '^#!/bin/sh' {} \; \<br />
-exec checkbashisms -f -p {} +<br />
<br />
*Package install scripts:<br />
$ find /var/lib/pacman/local -mindepth 2 -type f -name install \<br />
-exec checkbashisms -f -p {} + 2>&1 |\<br />
grep -v -e '^you may get strange results' \<br />
-e 'does not appear to have a #! interpreter line;$'<br />
<br />
*Initscripts and daemons:<br />
$ find \<br />
/etc/rc.{conf,d,local{,.shutdown},multi,shutdown,single,sysinit} -type f \<br />
-exec checkbashisms -f -p {} + 2>&1 |\<br />
grep -v -e '^you may get strange results' \<br />
-e 'does not appear to have a #! interpreter line;$'<br />
<br />
==Relinking /bin/sh==<br />
Once you have verified that it won't break any functionality, it should be safe to relink {{ic|/bin/sh}}. To do so use the following command (as root):<br />
<br />
ln -sfT /bin/dash /bin/sh<br />
<br />
==Initscript status==<br />
<br />
* The FD checks with {{Ic|test -t}} in {{ic|/etc/rc.d/functions}} do not work correctly with dash, breaking colored output as a result. See http://bugs.archlinux.org/task/19551?project=1&order=id&sort=desc (the patch does not address this issue in particular).<br />
:* Try using {{Ic|test(1)}} instead of the dash builtin?<br />
:* Is the problem specific to calls involving {{Ic|init(1)}}?</div>
Faelar
https://wiki.archlinux.org/index.php?title=Graphics_tablet&diff=76381
Graphics tablet
2009-09-24T19:14:57Z
<p>Faelar: VirtualBox</p>
<hr />
<div>[[Category:Input devices (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
= Introduction =<br />
<br />
Before we begin, I would like to point out that this guide is only for a ''USB'' based Wacom tablets. Futhermore, you can either setup a static ''Xorg'' configuration, meaning things may not work if later on you plug your Wacom tablet into a different ''USB'' port, or follow the dynamic instructions further down. Finally this guide is based on my experience of installing my ''Graphire4'' tablet, so others may like to add things specific to other Wacom tablets. I do welcome others to update this wiki to include a wider range of information.<br />
<br />
I'd also like to mention that this wiki is very much influenced by the very helpful [http://gentoo-wiki.com/HOWTO_Wacom_Tablet Gentoo Linux Wiki - HOWTO Wacom Tablet], which I recommend anyone visit if they would like to learn about things that are not covered here.<br />
<br />
== Try Autodetection First ==<br />
<br />
I just installed linuxwacom-dev from AUR and everything worked without messing with xorg.conf!<br />
<br />
I have the following packages installed and running:<br />
xorg-server-1.6.2-1<br />
hal-0.5.12git20090421.4fc367-2<br />
udev-141-3<br />
linuxwacom-dev 0.8.3-8 (from AUR)<br />
<br />
my tablet: http://www.wacom.com.sg/price/graphire4/graphire4_A6.html<br />
aur package: http://aur.archlinux.org/packages.php?ID=25238<br />
<br />
the only thing i miss is that only the "pen" works, not the eraser. But i guess this can be accomplished by editing (/usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi) ... which i havent tried yet.<br />
<br />
and i had to configure GIMP (as described in this guide) to make pressure sensitivity work.<br />
<br />
p.s.: sorry for this quick and dirty formated post. i don't have much time right know but i want to safe people the frustration i had with previous wacom/xorg versions :)<br />
<br />
= Installing =<br />
<br />
== Install Linuxwacom ==<br />
<br />
Thanks to [http://linuxwacom.sourceforge.net The Linux Wacom Project], you only need to install the ''linuxwacom'' package, which contains everything needed to use a Wacom tablet on Linux. You can get this from the [[AUR]].<br />
<br />
== Configure Xorg ==<br />
<br />
{{Note | Static configuration is deprecated by the X.org project. Consider using HAL (see below) instead to get hotplugging and automatic configuration.}}<br />
<br />
Again, I'd like to make note that I only cover how to setup a static ''Xorg'' configuration, meaning things may not work if later on you plug your Wacom tablet into a different USB port.<br />
<br />
InputDevice "cursor" "SendCoreEvents"<br />
InputDevice "stylus" "SendCoreEvents"<br />
InputDevice "eraser" "SendCoreEvents"<br />
Firstly, add these to the ''ServerLayout'' section of your ''Xorg'' config ({{Filename|/etc/X11/xorg.conf}}).<br />
<br />
$ cat /proc/bus/input/devices<br />
Now we need to determine the location of your tablet ''device''. Run the command above, and take note of the ''event'' number of the ''Handlers'' row. We will use this to set the correct device in our ''Xorg'' config below.<br />
<br />
I: Bus=0003 Vendor=056a Product=0016 Version=0403<br />
N: Name="Wacom Graphire4 6x8"<br />
P: Phys=<br />
S: Sysfs=/class/input/input7<br />
H: Handlers=mouse2 event7 ts2 <br />
B: EV=1f<br />
B: KEY=1c63 0 70011 0 0 0 0 0 0 0 0<br />
B: REL=100<br />
B: ABS=100 3000003<br />
B: MSC=1<br />
Here is an example of the output for my ''Graphire4'' tablet. From this, we can determine that my tablet device goes through {{Filename|/dev/input/event7}}.<br />
<br />
Section "InputDevice"<br />
Identifier "stylus"<br />
Driver "wacom"<br />
Option "Type" "stylus"<br />
Option "Device" "/dev/input/event7"<br />
Option "USB" "on"<br />
Option "Mode" "Absolute"<br />
Option "Vendor" "WACOM"<br />
Option "Threshold" "5"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "eraser"<br />
Driver "wacom"<br />
Option "Type" "eraser"<br />
Option "Device" "/dev/input/event7"<br />
Option "USB" "on"<br />
Option "Mode" "Absolute"<br />
Option "Vendor" "WACOM"<br />
Option "Threshold" "5"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "cursor"<br />
Driver "wacom"<br />
Option "Type" "cursor"<br />
Option "Device" "/dev/input/event7"<br />
Option "USB" "on"<br />
Option "Mode" "Absolute"<br />
Option "Vendor" "WACOM"<br />
EndSection<br />
Now update your ''Xorg'' config ({{Filename|/etc/X11/xorg.conf}}) as above.<br />
<br />
To learn about each of the Wacom tablet ''Xorg'' options checkout the ''man pages'' found at [http://linuxwacom.sourceforge.net/index.php/howto/inputdev Linux Wacom Project HOWTO - 5.1 - Adding the InputDevices].<br />
<br />
I recommend you checkout [http://linuxwacom.sourceforge.net/index.php/howto/x11 Linux Wacom Project HOWTO - 5.0 - Configuring X11], I also recommend you checkout [http://gentoo-wiki.com/HOWTO_Wacom_Tablet#Xorg Gentoo Linux Wiki - HOWTO Wacom Tablet - Installing - Xorg].<br />
<br />
==== TwinView Setup ====<br />
<br />
If you are going to use two Monitors the apsect ratio while using the Tablet might feel unnatural. In order to fix this you need to add<br />
<br />
Option "TwinView" "horizontal"<br />
<br />
To all of your Wacom-InputDevice entries in the {{Filename|xorg.conf}} file.<br />
You may read more about that [http://ubuntuforums.org/showthread.php?t=640898 HERE]<br />
<br />
=== Graphire4 buttons ===<br />
<br />
InputDevice "pad" "SendCoreEvents"<br />
Add this to the ''ServerLayout'' section of your ''Xorg'' config ({{Filename|/etc/X11/xorg.conf}}).<br />
<br />
*Note, it was mentioned at [http://gentoo-wiki.com/HOWTO_Wacom_Tablet#Graphire4_buttons Gentoo Linux Wiki - HOWTO Wacom Tablet - Installing - Xorg - Graphire4 buttons] that there was information somewhere advising NOT to add "SendCoreEvents" to the line above, but it was also said that without this these buttons will not work.<br />
<br />
Section "InputDevice"<br />
Identifier "pad"<br />
Driver "wacom"<br />
Option "Type" "pad"<br />
Option "Device" "/dev/input/event7"<br />
Option "USB" "on"<br />
Option "ButtonsOnly" "on"<br />
EndSection<br />
Now update your ''Xorg'' config ({{Filename|/etc/X11/xorg.conf}}) as above.<br />
<br />
I recommend you checkout [http://gentoo-wiki.com/HOWTO_Wacom_Tablet#Graphire4_buttons Gentoo Linux Wiki - HOWTO Wacom Tablet - Installing - Xorg - Graphire4 buttons].<br />
<br />
=== Xorg crashes when logging in ===<br />
<br />
In case that happens to you you need to apply this patch to Xorg and recompile it (from http://sourceforge.net/tracker/index.php?func=detail&aid=1843335&group_id=69596&atid=525124):<br />
<br />
diff -ur xorg-server-1.4.orig/xkb/xkbLEDs.c xorg-server-1.4/xkb/xkbLEDs.c<br />
--- xorg-server-1.4.orig/xkb/xkbLEDs.c 2007-11-01 20:49:02.000000000<br />
+0100<br />
+++ xorg-server-1.4/xkb/xkbLEDs.c 2007-11-01 20:48:03.000000000<br />
+0100<br />
@@ -63,6 +63,9 @@<br />
<br />
sli= XkbFindSrvLedInfo(dev,XkbDfltXIClass,XkbDfltXIId,0);<br />
<br />
+ if (!sli)<br />
+ return 0;<br />
+<br />
if (state_changes&(XkbModifierStateMask|XkbGroupStateMask))<br />
update|= sli->usesEffective;<br />
if (state_changes&(XkbModifierBaseMask|XkbGroupBaseMask))<br />
<br />
Be advised that this patch could lead to unexpected behavior. It's no official patch and only use it at your own risk.<br />
<br />
<br />
=== Tablet devices still do not appear ===<br />
<br />
Start ''Xorg'' with tablet connected. Then look at logs ({{Filename|/var/log/Xorg.0.log}}) and search for those errors:<br />
<br />
Error opening /dev/input/wacom : Success<br />
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom<br />
No such file or directory.<br />
<br />
This error will show even when device exists.<br />
<br />
Second error is<br />
<br />
usbDetect: can not ioctl version<br />
Wacom xf86WcmWrite error : Invalid argument<br />
<br />
If there are those errors, check if your wacom device is {{Filename|/dev/input/ts3}} or another ts device (or symlink to this device). If it is, then device is handled by Compaq touchscreen emulation. This is ''tsdev'' module.<br />
Just unload the module<br />
<br />
# modprobe -r tsdev<br />
<br />
and add this module to blacklist in {{Filename|/etc/rc.conf}}.<br />
<br />
==Dynamic (udev) Xorg setup==<br />
Again thanks to [http://gentoo-wiki.com/HOWTO_Wacom_Tablet Gentoo Linux Wiki - HOWTO Wacom Tablet] for the information! This was done with a ''Volito2'', and so reflects the experiences with that tablet, but it should work for any tablet supported by the linuxwacom project.<br />
<br />
{{Note | The linuxwacom package from AUR already includes a udev-rules-file, so you might skip this part and move on to the {{Filename|xorg.conf}} configuration if you're using the linuxwacom package from AUR.}}<br />
<br />
Install ''udev'' from the repositories.<br />
Run the ''lsusb'' command. It should return something like this<br />
<br />
Bus 002 Device 007: ID 056a:0062 Wacom Co., Ltd<br />
Bus 002 Device 006: ID 03eb:0902 Atmel Corp.<br />
Bus 002 Device 005: ID 0bc2:0503 Seagate RSS LLC<br />
Bus 002 Device 004: ID 05e3:0660 Genesys Logic, Inc. USB 2.0 Hub<br />
Bus 002 Device 001: ID 1d6b:0002<br />
Bus 003 Device 001: ID 1d6b:0001<br />
Bus 001 Device 003: ID 06a3:8000 Saitek PLC<br />
Bus 001 Device 002: ID 045e:00d1 Microsoft Corp.<br />
Bus 001 Device 001: ID 1d6b:0001<br />
You can see from here my tablet among other devices. We are interested in the tablet and mouse - unless there is no mouse attached to the said computer of course.<br />
Next make the file {{Filename|10-local.rules}} in ''/etc/udev/rules.d''. You need to add these two lines<br />
<br />
KERNEL=="event*", SYSFS{idVendor}=="056a", NAME="input/%k", SYMLINK="input/wacom"<br />
KERNEL=="mouse*", SYSFS{idProduct}=="045e", NAME="input/%k", SYMLINK="input/mouse_udev"<br />
Of course you need to change '056a' and '045e' to what lsusb returns for you &ndash; I used the VendorID for my tablet and the ProductID for my mouse.<br />
Save the file and start udev using the command ''/etc/start_udev''<br />
Check to make sure that it has appeared in ''/dev/input''.<br />
<br />
bash-3.2# cd /dev/input<br />
bash-3.2# ls<br />
by-id event0 event2 event4 event6 event8 mouse0 mouse2 wacom<br />
by-path event1 event3 event5 event7 mice mouse1 mouse_udev<br />
You can even check that the device works by<br />
<br />
# cat wacom<br />
It should make lots of odd characters appear onscreen.<br />
If it works, then all that is left to do is add the relevent information to {{Filename|/etc/X11/xorg.conf}}.<br />
<br />
Section "InputDevice"<br />
Driver "wacom"<br />
Identifier "stylus"<br />
Option "Device" "/dev/input/wacom"<br />
Option "Type" "stylus"<br />
Option "USB" "on" # USB ONLY<br />
Option "Mode" "Relative" # other option: "Absolute"<br />
Option "Vendor" "WACOM"<br />
Option "tilt" "on" # add this if your tablet supports tilt<br />
Option "Threshold" "5" # the official linuxwacom howto advises this line<br />
EndSection<br />
Section "InputDevice"<br />
Driver "wacom"<br />
Identifier "eraser"<br />
Option "Device" "/dev/input/wacom"<br />
Option "Type" "eraser"<br />
Option "USB" "on" # USB ONLY<br />
Option "Mode" "Relative" # other option: "Absolute"<br />
Option "Vendor" "WACOM"<br />
Option "tilt" "on" # add this if your tablet supports tilt<br />
Option "Threshold" "5" # the official linuxwacom howto advises this line<br />
EndSection<br />
Section "InputDevice"<br />
Driver "wacom"<br />
Identifier "cursor"<br />
Option "Device" "/dev/input/wacom"<br />
Option "Type" "cursor"<br />
Option "USB" "on" # USB ONLY<br />
Option "Mode" "Relative" # other option: "Absolute"<br />
Option "Vendor" "WACOM"<br />
EndSection<br />
Make sure that you also change the path ({{Codeline|"Device"}}) to your mouse, as it will be {{Codeline|/dev/input/mouse_udev}} now.<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse1"<br />
Driver "mouse"<br />
Option "CorePointer"<br />
Option "Device" "/dev/input/mouse_udev"<br />
Option "SendCoreEvents" "true"<br />
Option "Protocol" "IMPS/2"<br />
Option "ZAxisMapping" "4 5"<br />
Option "Buttons" "5"<br />
EndSection<br />
Add this to the ''ServerLayout'' section<br />
<br />
InputDevice "cursor" "SendCoreEvents" <br />
InputDevice "stylus" "SendCoreEvents"<br />
InputDevice "eraser" "SendCoreEvents"<br />
And finally make sure to update the indentifier of your mouse in the ''ServerLayout'' section &ndash; as mine went from<br />
<br />
InputDevice "Mouse0" "CorePointer"<br />
to<br />
<br />
InputDevice "Mouse1" "CorePointer"<br />
<br />
==Xorg input hotplugging setup==<br />
<br />
To use a Wacom/WALTOP/N-Trig tablet with Xorg hotplugging create {{Filename|/etc/hal/fdi/policy/10-tablet.fdi}} with this code:<br />
<br />
<?xml version="1.0" encoding="UTF-8"?> &lt;!-- -*- SGML -*- --><br />
<br />
<deviceinfo version="0.2"><br />
<device><br />
<match key="info.capabilities" contains="input"><br />
<match key="info.product" contains="Wacom"><br />
<merge key="input.x11_driver" type="string">wacom</merge><br />
<merge key="input.x11_options.Type" type="string">stylus</merge><br />
</match><br />
<match key="info.product" contains="WALTOP"><br />
<merge key="input.x11_driver" type="string">wacom</merge><br />
<merge key="input.x11_options.Type" type="string">stylus</merge><br />
</match><br />
</match><br />
<!-- N-Trig Duosense Electromagnetic Digitizer --><br />
<match key="info.product" contains="HID 1b96:0001"><br />
<match key="info.parent" contains="if0"><br />
<merge key="input.x11_driver" type="string">wacom</merge><br />
<merge key="input.x11_options.Type" type="string">stylus</merge><br />
</match><br />
</match><br />
</device><br />
</deviceinfo><br />
<br />
Then kill your X server, restart HAL and start the X server again.<br />
<br />
=== Calibrating Tablet ===<br />
<br />
In order for calibration to work even when the screen is rotated (this applies for both serial and USB tablets), the wacom-names script is useful. It renames your X input devices so that they can be recognized by the linuxwacom driver. Download it from [http://ubuntuforums.org/attachment.php?attachmentid=109824&d=1239742307 here]. You need to be a Ubuntu forums member to download it. If you are not, here is the script. Remember, it was originally intended for Ubuntu so the instructions do not all apply to us Archers:<br />
<br />
# wacom-names script by Roger E. Critchlow, Jr. (4-12-09)<br />
# modified by gali98/Favux (4-14-09)<br />
#<br />
# Place the wacom-names script in /etc/init.d/wacom-names and link it as<br />
# /etc/rc{2,3,4,5}.d/S27wacom-names.<br />
# Use "sudo update-rc.d wacom start 27 2 3 4 5 ." or "sudo update-rc.d wacom defaults 27".<br />
# Using S27 starts the script after hal and before gdm. This allows us to modify the hal<br />
# properties before the xserver sees them for the first time.<br />
#<br />
# The script renames the input devices back to what wacomcpl and xsetwacom expect them to<br />
# be, so rotation and interactive calibration work. It also enables xorg.conf & .xinitrc<br />
# style configuration of Wacom features like the stylus button(s) and calibration.<br />
#<br />
# The script needs to be executable. chmod +x wacom-names<br />
<br />
#! /bin/sh<br />
## find any wacom devices<br />
for udi in `hal-find-by-property --key input.x11_driver --string wacom`<br />
do<br />
type=`hal-get-property --udi $udi --key input.x11_options.Type`<br />
## rewrite the names that the Xserver will use<br />
hal-set-property --udi $udi --key info.product --string $type<br />
#<br />
## To add a xorg.conf or xsetwacom (.xinitrc) style configuration, say mapping a stylus<br />
## button, you could add to the script:<br />
#case $type in<br />
#stylus|eraser)<br />
## eg: map stylus button 2 to mouse button 3 (right click)<br />
#hal-set-property --udi $udi --key input.x11_options.Button2 --string 3<br />
#<br />
#;;<br />
#esac<br />
done<br />
<br />
Copy and paste and (or directly) save it as wacom-names to '''/etc/rc.d''' and make it an executable.<br />
# chmod +x /etc/rc.d/wacom-names<br />
<br />
Add wacom-names to the DAEMONS line in your {{Filename|[[rc.conf]]}}. Make sure to put it after HAL, and do not background HAL, because this script will not work if it runs before HAL has started. For example:<br />
DAEMONS=(syslog-ng @crond hal @acpid @alsa @gpm wacom-names)<br />
<br />
Reboot your computer. From here you can either keep wacom-names in your rc.conf if your rotation script calls on xsetwacom directly, or if you just need the calibration data, you can now use wacomcpl.<br />
<br />
If you are looking for more information, this [http://ubuntuforums.org/showthread.php?t=1038949 thread] at the Ubuntu forums is incredibly useful, and also provided the link to Rec's wacom-names script.<br />
<br />
= WALTOP tablet support by the Wacom drivers =<br />
<br />
Since lately Wacom drivers cannot be started with WALTOP tablets, although the functionality is present. This is due to a vendor check in the ''wacom '' X.org driver. To bypass this check, download the ''linuxwacom'' sources (for example, the ''linuxwacom-cvs'' package from AUR) and apply a similar patch to {{Filename|src/xdrv/wcmUSB.c}}:<br />
<br />
% cat wcmUSB.c.diff <br />
528,529c528,529<br />
< /* vendor is wacom */<br />
< if (sID[1] == 0x056A)<br />
---<br />
> /* vendor is wacom or waltop*/<br />
> if (sID[1] == 0x056A || sID[1] == 0x172f)<br />
<br />
<br />
= The GIMP =<br />
<br />
To enabled proper usage, and pressure sensitive painting in [http://www.gimp.org The GIMP], just go to ''Preferences &rarr; Input Devices &rarr; Configure Extended Input Devices...''. Now for each of your ''eraser'', ''stylus'', and ''cursor'' '''devices''', set the '''mode''' to ''Screen'', and remember to save.<br />
<br />
*Please take note that if present, the ''pad'' '''device''' should be kept disabled as I don't think The GIMP supports such things. Alternatively, to use such features of your tablet you should map them to keyboard commands with a program such as [http://hem.bredband.net/devel/wacom/ Wacom ExpressKeys].<br />
<br />
*You should also take note that the tool selected for the ''stylus'' is independent to that of the ''eraser''. This can actually be quite handy, as you can have the ''eraser'' set to be used as any tool you like.<br />
<br />
I recommend you checkout [http://linuxwacom.sourceforge.net/index.php/howto/gimp Linux Wacom Project HOWTO - 10.0 - Working With Gimp], and the ''Setting up GIMP'' section of [http://www.gimptalk.com/forum/topic.php?t=17992&start=1 GIMP Talk - Community - Install Guide: Getting Wacom Drawing Tablets To Work In Gimp].<br />
<br />
= Inkscape =<br />
<br />
As in The GIMP, to do the same simply got to ''File &rarr; Input Devices...''. Now for each of your ''eraser'', ''stylus'', and ''cursor'' '''devices''', set the '''mode''' to ''Screen'', and remember to save.<br />
<br />
= Krita = <br />
<br />
To get your tablet working in Krita, simply go to ''Settings &rarr; Configure Krita...'' Click on ''Tablet'' and then like in Inkscape and GIMP set ''stylus'' and any others' mode to screen.<br />
<br />
== Bamboo ==<br />
<br />
{{Note | Some users reported problems with linuxwacom 0.8.1-1 and Bamboo. Their Cursor jumped around when trying to use the stylus-tilt to avoid that problem simply use linuxwacom 0.8.0 (You can simply edit the pkgver in the PKGBUILD).}}<br />
<br />
If you use an older version of linuxwacom it could happen that you will not be able to use your pen with GIMP or Inkscape when configured as above since the stylus is firing a button2 event instead of a button1 event, same with the eraser. To correct this add (don't just copy and paste the whole section, just add the part about the buttons) these lines to the appropriate section of your xorg.conf.<br />
<br />
Section "InputDevice"<br />
Driver "wacom"<br />
Identifier "stylus"<br />
Option "Button1" "1" #this line is important<br />
Option "Button2" "1" #this line is important<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Driver "wacom"<br />
Identifier "eraser"<br />
Option "Button1" "1" #this line is important<br />
Option "Button2" "1" #this line is important<br />
EndSection<br />
<br />
Be adviced that this way pressure sensitive painting in GIMP and Inkscape will work but the lower button of the pen will also fire a button1 event same as the stylus and eraser. You can not configure any other button for Button2, it got to be the same as Button1! There is no need to add these lines to the cursor section since the bamboo doesn't ship a mouse, still i advice you not to remove the cursor device as an input device, not even from the serverlayout section. That lead to an unstable xserver in my case.<br />
<br />
= Wacom and VirtualBox =<br />
<br />
''My current setup is :<br />
Guest OS: Windows XP<br />
Tablet: Wacom Graphire4<br />
Linux Driver: xf86-input-wacom 0.8.4-1''<br />
<br />
First, make sure that your tablet works well under Arch. Then, download and install the last driver from [http://www.wacom.com/downloads/drivers.php Wacom website] on the guest OS. Shutdown the virtual machine, go to '''Settings > USB'''. Select '''Add Filter From Device''' and select your tablet (e.g. WACOM CTE-440-U V4.0-3 [0403]). Select '''Edit Filter''', and change the last item '''Remote''' to '''Any'''.<br />
<br />
= Linuxwacom 0.8.1 bug =<br />
<br />
If you have trouble with the linuxwacom 0.8.1 beta/developer version driver as reported [http://bbs.archlinux.org/viewtopic.php?pid=421375 HERE], such as when you apply pressure the cursor freezes then you should try the linuxwacom 0.8.0 production version. Just download the existing PKGBUILD and other files from the [http://aur.archlinux.org/packages/linuxwacom/linuxwacom/ AUR] and change '''pkgver''' from 0.8.1 to '''0.8.0''', and the first '''md5sum''' from 4b78f1b66f6e9097a393cf1e3cdf87a3 to '''1d89b464392515492bb7b97c20e68d4e'''.<br />
<br />
= References =<br />
*[http://gentoo-wiki.com/HOWTO_Wacom_Tablet Gentoo Linux Wiki - HOWTO Wacom Tablet]<br />
*[http://linuxwacom.sourceforge.net/index.php/howto/main Linux Wacom Project HOWTO]<br />
*[http://www.gimptalk.com/forum/topic.php?t=17992&start=1 GIMP Talk - Community - Install Guide: Getting Wacom Drawing Tablets To Work In Gimp]<br />
* [http://ubuntuforums.org/showthread.php?t=1038949 Ubuntu Forums - Install a LinuxWacom Kernel Driver for Tablet PC's]</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=73724
User:Faelar
2009-08-10T23:14:53Z
<p>Faelar: Blanked the page</p>
<hr />
<div></div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=73722
User:Faelar
2009-08-10T23:11:12Z
<p>Faelar: guide off début traduction</p>
<hr />
<div>[[Category:Obtenir et installer Arch (Français)]]<br />
[[Category:HOWTOs (Français)]]<br />
<br />
{{Article summary start}}<br />
{{Article summary text| 1=<br />
<p>Documentation générale d'installation pour la distribution Arch Linux.</p><br />
<br />
<p>Ce guide est uniquement valide pour les versions 2009.08 ou plus récentes</p><br />
<br />
<p>Ce guide est maintenu dans le [http://projects.archlinux.org/?p=aif.git git aif] <br /><br />
Les patches/commentaires sont les bienvenus sur la [http://www.archlinux.org/mailman/listinfo/arch-releng mailing list releng]<br />
ou par courriel à [mailto:dieter@archlinux.org dieter@archlinux.org]</p><br />
<br />
<p>Ce guide est disponible dans le dossier /arch du media d'installation et sur<br />
[http://wiki.archlinux.org/index.php/Official_Arch_Linux_Install_Guide Le wiki arch]</p>}}<br />
{{Article summary heading|Langages disponibles}}<br />
<br />
{{i18n_entry|English|Official Arch Linux Install Guide}}<br />
{{i18n_entry|Français|Guide Officiel d'Installation d'Arch Linux (Français)}}<br />
<br />
{{Article summary heading|Articles en rapport}}<br />
<br />
{{Article summary wiki|http://wiki.archlinux.org/index.php/Manuel_du_Débutant_(Français) Manuel du Débutant}} (Si vous êtes nouveau sur Arch)<br />
{{Article summary end}}<br />
<br />
{{translateme}}<br />
<br />
<h1>Introduction</h1><br />
<br />
<h2>Qu'est-ce qu'Arch Linux?</h2><br />
<br />
<p>Arch Linux est une distribution Linux optimisée i686 et x86_64 développée indépendamment qui était à l'origine basée sur les idées de CRUX. <br /><br />
Le développement est focalisé sur un équilibre entre simplicité, élégance, justesse du code et logiciels dernier cri. <br /><br />
Sa conception simple et minimaliste la rend facile à enrichir et modeler en n'importe quel type de système que vous assemblez.</p></div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=73721
User:Faelar
2009-08-10T22:38:11Z
<p>Faelar: Replaced content with 'Rien pour l'instant ;)'</p>
<hr />
<div>Rien pour l'instant ;)</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=73716
User:Faelar
2009-08-10T22:31:17Z
<p>Faelar: traduction</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|Reinstalling GRUB}}<br />
{{i18n_entry|Español|Reinstalando GRUB}}<br />
{{i18n_entry|Česky|Přeinstalování GRUBu (Česky)}}<br />
{{i18n_entry|Italiano|Reinstalling GRUB (Italiano)}}<br />
{{i18n_entry|Ελληνικά|Reinstalling GRUB (Ελληνικά)}}<br />
{{i18n_entry|简体中文|重装GRUB}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==Introduction==<br />
<br />
Ce guide va vous montrer comment réinstaller GRUB avec un CD d'Installation d'Arch si vous perdez GRUB d'une manière ou d'une autre.<br />
<br />
===Notes===<br />
<br />
*Dans ce guide, j'utiliserai <tt>sda</tt> comme ma racine udev type de référence. Si vous utilisez une version du CD d'Installation pre-0.7.1, vous devrez substituer les références à udev par les références pour devfs. Voir [[Technical Terms#Hard Drives|Hard Drives]] si cela n'a pas de sens pour vous.<br />
<br />
*Aussi, sachez que ce guide vise les gens utilisant les pilotes SATA, pas IDE aussi substituez les noms IDE comme <tt>hda</tt> au lieu de <tt>sda</tt> si vous avez des périphériques IDE et que vous n'utilisez pas libata.<br />
<br />
== Démarrer le CD d'Installation ==<br />
La première chose dont vous aurez besoin est un [http://www.archlinux.org/download CD d'Installation]. N'importe quel CD d'Installation devrait convenir; Cependant, utiliser le dernier CD sera plus simple que d'utiliser un ancien CD.<br />
<br />
Démarrer le CD comme si vous faisiez une installation (N'utilisez '''PAS''' l'option <tt>root=</tt>) et rendez-vous à l'étape suivante.<br />
<br />
=== Monter et Chrooter dans votre installation actuelle ===<br />
Maintenant, vous devez monter votre installation actuelle. Le processus général pour ceci est le suivant :<br />
*NOTE : Vous devez savoir quelle est la bonne partition et le type du système de fichiers utilisé. J'utiliserai <tt>sda1</tt> comme partition racine et <tt>ext3</tt> comme système de fichiers dans cet exemple; adaptez cela à vos paramètres personnels.<br />
<br />
cd /<br />
# Si vous utilisez un CD pré-0.7.1, sda1 sera /dev/discs/disc0/part1<br />
mount -t ext3 /dev/sda1 /mnt<br />
mount -t proc proc /mnt/proc<br />
mount -t sysfs sys /mnt/sys<br />
mount -o bind /dev /mnt/dev<br />
<br />
chroot /mnt /bin/bash<br />
<br />
Maintenant vous devriez être identifié en tant que root, et dans votre installation actuelle comme si vous l'aviez juste démarré et vous êtiez connecté en root.<br />
<br />
Si votre dossier /boot est sur la même partition que votre /, passez à l'étape suivante. Si par contre il est sur une partition séparée (par exemple, /dev/sda2), alors vous devez monter cette partition maintenant dans /boot comme ça grub peut trouver les fichiers dont il a besoin :<br />
<br />
mount -t ext2 /dev/sda2 /boot<br />
<br />
===Réinstaller GRUB===<br />
Editez <tt>/boot/grub/menu.lst</tt> et assurez-vous que tout est en ordre. Une fois que vous êtes complètement sûr que <tt>menu.lst</tt> est correct, lancer la commande suivante :<br />
<br />
grub-install /dev/sda<br />
<br />
Cette commande devrait s'achever avec succès si vous avez suivi toutes les étapes. (Sinon, jetez un oeil aux notes ci-dessous.) C'est tout, vous avez fini ! Quittez chroot et redémarrez :<br />
<br />
cd /<br />
umount -a<br />
exit<br />
cd /<br />
umount -a<br />
reboot<br />
<br />
====Erreurs====<br />
Si vous recevez une erreur qui dit <tt>The file /boot/grub/stage1 not read correctly</tt>, cela veut probablement dire que votre fstab/mtab est incorrect pour une raison quelconque et nécessite d'être corrigé. Ces fichiers sont <tt>/etc/mtab</tt> et <tt>/etc/fstab</tt>. Editez les et assurez vous qu'ils pointent vers les bonnes partitions, alors relancez grub-install.<br />
<br />
Si cela ne suffit pas à rectifier le message d'erreur et que vous utilisez ext2/3 comme système de fichiers pour votre partition de boot, utilisez "tune2fs -l /dev/sda1" pour vérifier la taille de l'Inode de votre partition root/boot. N'importe quoi d'autre que 128 rendra grub incapable de lire la partition. La seule solution à ce problème est de recréer votre rootfs avec les bonnes options (corrigez /etc/mke2fs.conf et paramétrez inode_size à 128).<br />
<br />
Si vous recevez une erreur qui dit <tt>sed: can't read /boot/grub/device.map: No such file or directory</tt>, cela veut dire que vous devez utiliser l'option --recheck avec grub-install.<br />
<br />
grub-install --recheck /dev/sda<br />
<br />
Esperons que cela couvre tous les problèmes que vous pourriez rencontrer. Si vous recevez n'importe quel autre erreur, redémarré et suivez de nouveau ce guide étape par étape.</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=71301
User:Faelar
2009-06-27T13:28:37Z
<p>Faelar: /* Reinstalling GRUB */</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:System recovery (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Reinstalling GRUB}}<br />
{{i18n_entry|Español|Reinstalando GRUB}}<br />
{{i18n_entry|Česky|Přeinstalování GRUBu (Česky)}}<br />
{{i18n_entry|Italiano|Reinstalling GRUB (Italiano)}}<br />
{{i18n_entry|Ελληνικά|Reinstalling GRUB (Ελληνικά)}}<br />
{{i18n_entry|简体中文|重装GRUB}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==Introduction==<br />
<br />
Ce guide va vous montrer comment réinstaller GRUB avec un CD d'Installation d'Arch si vous perdez GRUB d'une manière ou d'une autre.<br />
<br />
===Notes===<br />
<br />
*Dans ce guide, j'utiliserai <tt>sda</tt> comme ma racine udev type de référence. Si vous utilisez une version du CD d'Installation pre-0.7.1, vous devrez substituer les références à udev par les références pour devfs. Voir [[Technical Terms#Hard Drives|Hard Drives]] si cela n'a pas de sens pour vous.<br />
<br />
*Aussi, sachez que ce guide vise les gens utilisant les pilotes SATA, pas IDE aussi substituez les noms IDE comme <tt>hda</tt> au lieu de <tt>sda</tt> si vous avez des périphériques IDE et que vous n'utilisez pas libata.<br />
<br />
== Démarrer le CD d'Installation ==<br />
La première chose dont vous aurez besoin est un [http://www.archlinux.org/download CD d'Installation]. N'importe quel CD d'Installation devrait convenir; Cependant, utiliser le dernier CD sera plus simple que d'utiliser un ancien CD.<br />
<br />
Démarrer le CD comme si vous faisiez une installation (N'utilisez '''PAS''' l'option <tt>root=</tt>) et rendez-vous à l'étape suivante.<br />
<br />
=== Monter et Chrooter dans votre installation actuelle ===<br />
Maintenant, vous devez monter votre installation actuelle. Le processus général pour ceci est le suivant :<br />
*NOTE : Vous devez savoir quelle est la bonne partition et le type du système de fichiers utilisé. J'utiliserai <tt>sda1</tt> comme partition racine et <tt>ext3</tt> comme système de fichiers dans cet exemple; adaptez cela à vos paramètres personnels.<br />
<br />
cd /<br />
# Si vous utilisez un CD pré-0.7.1, sda1 sera /dev/discs/disc0/part1<br />
mount -t ext3 /dev/sda1 /mnt<br />
mount -t proc proc /mnt/proc<br />
mount -t sysfs sys /mnt/sys<br />
mount -o bind /dev /mnt/dev<br />
<br />
chroot /mnt /bin/bash<br />
<br />
Maintenant vous devriez être identifié en tant que root, et dans votre installation actuelle comme si vous l'aviez juste démarré et vous êtiez connecté en root.<br />
<br />
Si votre dossier /boot est sur la même partition que votre /, passez à l'étape suivante. Si par contre il est sur une partition séparée (par exemple, /dev/sda2), alors vous devez monter cette partition maintenant dans /boot comme ça grub peut trouver les fichiers dont il a besoin :<br />
<br />
mount -t ext2 /dev/sda2 /boot<br />
<br />
===Réinstaller GRUB===<br />
Editez <tt>/boot/grub/menu.lst</tt> et assurez-vous que tout est en ordre. Une fois que vous êtes complètement sûr que <tt>menu.lst</tt> est correct, lancer la commande suivante :<br />
<br />
grub-install /dev/sda<br />
<br />
Cette commande devrait s'achever avec succès si vous avez suivi toutes les étapes. (Sinon, jetez un oeil aux notes ci-dessous.) C'est tout, vous avez fini ! Quittez chroot et redémarrez :<br />
<br />
cd /<br />
umount -a<br />
exit<br />
cd /<br />
umount -a<br />
reboot<br />
<br />
====Errors====<br />
If you get an error that says <tt>The file /boot/grub/stage1 not read correctly</tt>, it probably means that your fstab/mtab is incorrect for some reason and needs to be fixed. These files are <tt>/etc/mtab</tt> and <tt>/etc/fstab</tt>. Edit them and make sure they point to the correct partitions, then rerun grub-install.<br />
<br />
If this still doesn't fix the error message and you're using ext2/3 as filesystem for your boot partition, use "tune2fs -l /dev/sda1" to check for the Inode size of your root/boot partition. Anything else than 128 will make grub unable to read the partition. The only solution for this problem is to recreate your rootfs with the correct options (fix /etc/mke2fs.conf and set inode_size to 128).<br />
<br />
If you get an error that says <tt>sed: can't read /boot/grub/device.map: No such file or directory</tt>, it means that you need to use the --recheck option with grub-install.<br />
<br />
grub-install --recheck /dev/sda<br />
<br />
Hopefully that covers all the issues you should encounter. If you get any other errors, reboot and do the guide step-by-step again.</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=71300
User:Faelar
2009-06-27T13:24:39Z
<p>Faelar: /* Monter et Chrooter dans votre installation actuelle */</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:System recovery (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Reinstalling GRUB}}<br />
{{i18n_entry|Español|Reinstalando GRUB}}<br />
{{i18n_entry|Česky|Přeinstalování GRUBu (Česky)}}<br />
{{i18n_entry|Italiano|Reinstalling GRUB (Italiano)}}<br />
{{i18n_entry|Ελληνικά|Reinstalling GRUB (Ελληνικά)}}<br />
{{i18n_entry|简体中文|重装GRUB}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==Introduction==<br />
<br />
Ce guide va vous montrer comment réinstaller GRUB avec un CD d'Installation d'Arch si vous perdez GRUB d'une manière ou d'une autre.<br />
<br />
===Notes===<br />
<br />
*Dans ce guide, j'utiliserai <tt>sda</tt> comme ma racine udev type de référence. Si vous utilisez une version du CD d'Installation pre-0.7.1, vous devrez substituer les références à udev par les références pour devfs. Voir [[Technical Terms#Hard Drives|Hard Drives]] si cela n'a pas de sens pour vous.<br />
<br />
*Aussi, sachez que ce guide vise les gens utilisant les pilotes SATA, pas IDE aussi substituez les noms IDE comme <tt>hda</tt> au lieu de <tt>sda</tt> si vous avez des périphériques IDE et que vous n'utilisez pas libata.<br />
<br />
== Démarrer le CD d'Installation ==<br />
La première chose dont vous aurez besoin est un [http://www.archlinux.org/download CD d'Installation]. N'importe quel CD d'Installation devrait convenir; Cependant, utiliser le dernier CD sera plus simple que d'utiliser un ancien CD.<br />
<br />
Démarrer le CD comme si vous faisiez une installation (N'utilisez '''PAS''' l'option <tt>root=</tt>) et rendez-vous à l'étape suivante.<br />
<br />
=== Monter et Chrooter dans votre installation actuelle ===<br />
Maintenant, vous devez monter votre installation actuelle. Le processus général pour ceci est le suivant :<br />
*NOTE : Vous devez savoir quelle est la bonne partition et le type du système de fichiers utilisé. J'utiliserai <tt>sda1</tt> comme partition racine et <tt>ext3</tt> comme système de fichiers dans cet exemple; adaptez cela à vos paramètres personnels.<br />
<br />
cd /<br />
# Si vous utilisez un CD pré-0.7.1, sda1 sera /dev/discs/disc0/part1<br />
mount -t ext3 /dev/sda1 /mnt<br />
mount -t proc proc /mnt/proc<br />
mount -t sysfs sys /mnt/sys<br />
mount -o bind /dev /mnt/dev<br />
<br />
chroot /mnt /bin/bash<br />
<br />
Maintenant vous devriez être identifié en tant que root, et dans votre installation actuelle comme si vous l'aviez juste démarré et vous êtiez connecté en root.<br />
<br />
Si votre dossier /boot est sur la même partition que votre /, passez à l'étape suivante. Si par contre il est sur une partition séparée (par exemple, /dev/sda2), alors vous devez monter cette partition maintenant dans /boot comme ça grub peut trouver les fichiers dont il a besoin :<br />
<br />
mount -t ext2 /dev/sda2 /boot<br />
<br />
===Reinstalling GRUB===<br />
Edit <tt>/boot/grub/menu.lst</tt> and make sure that everything is in order. Once you are completely sure that <tt>menu.lst</tt> is correct, run the following command:<br />
<br />
grub-install /dev/sda<br />
<br />
This command should complete sucessfully if you have followed all the steps. (If not, take a look at the notes below.) That's it, you're done! Exit chroot and reboot:<br />
<br />
cd /<br />
umount -a<br />
exit<br />
cd /<br />
umount -a<br />
reboot<br />
<br />
====Errors====<br />
If you get an error that says <tt>The file /boot/grub/stage1 not read correctly</tt>, it probably means that your fstab/mtab is incorrect for some reason and needs to be fixed. These files are <tt>/etc/mtab</tt> and <tt>/etc/fstab</tt>. Edit them and make sure they point to the correct partitions, then rerun grub-install.<br />
<br />
If this still doesn't fix the error message and you're using ext2/3 as filesystem for your boot partition, use "tune2fs -l /dev/sda1" to check for the Inode size of your root/boot partition. Anything else than 128 will make grub unable to read the partition. The only solution for this problem is to recreate your rootfs with the correct options (fix /etc/mke2fs.conf and set inode_size to 128).<br />
<br />
If you get an error that says <tt>sed: can't read /boot/grub/device.map: No such file or directory</tt>, it means that you need to use the --recheck option with grub-install.<br />
<br />
grub-install --recheck /dev/sda<br />
<br />
Hopefully that covers all the issues you should encounter. If you get any other errors, reboot and do the guide step-by-step again.</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=71299
User:Faelar
2009-06-27T13:16:30Z
<p>Faelar: trad encore</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:System recovery (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Reinstalling GRUB}}<br />
{{i18n_entry|Español|Reinstalando GRUB}}<br />
{{i18n_entry|Česky|Přeinstalování GRUBu (Česky)}}<br />
{{i18n_entry|Italiano|Reinstalling GRUB (Italiano)}}<br />
{{i18n_entry|Ελληνικά|Reinstalling GRUB (Ελληνικά)}}<br />
{{i18n_entry|简体中文|重装GRUB}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==Introduction==<br />
<br />
Ce guide va vous montrer comment réinstaller GRUB avec un CD d'Installation d'Arch si vous perdez GRUB d'une manière ou d'une autre.<br />
<br />
===Notes===<br />
<br />
*Dans ce guide, j'utiliserai <tt>sda</tt> comme ma racine udev type de référence. Si vous utilisez une version du CD d'Installation pre-0.7.1, vous devrez substituer les références à udev par les références pour devfs. Voir [[Technical Terms#Hard Drives|Hard Drives]] si cela n'a pas de sens pour vous.<br />
<br />
*Aussi, sachez que ce guide vise les gens utilisant les pilotes SATA, pas IDE aussi substituez les noms IDE comme <tt>hda</tt> au lieu de <tt>sda</tt> si vous avez des périphériques IDE et que vous n'utilisez pas libata.<br />
<br />
== Démarrer le CD d'Installation ==<br />
La première chose dont vous aurez besoin est un [http://www.archlinux.org/download CD d'Installation]. N'importe quel CD d'Installation devrait convenir; Cependant, utiliser le dernier CD sera plus simple que d'utiliser un ancien CD.<br />
<br />
Démarrer le CD comme si vous faisiez une installation (N'utilisez '''PAS''' l'option <tt>root=</tt>) et rendez-vous à l'étape suivante.<br />
<br />
=== Monter et Chrooter dans votre installation actuelle ===<br />
Maintenant, vous devez monter votre installation actuelle. Le processus général pour ceci est le suivant :<br />
*NOTE : Vous devez savoir quelle est la bonne partition et le type du système de fichiers utilisé. J'utiliserai <tt>sda1</tt> comme partition racine et <tt>ext3</tt> comme système de fichiers dans cet exemple; adaptez cela à vos paramètres personnels.<br />
<br />
cd /<br />
# Si vous utilisez un CD pré-0.7.1, sda1 sera /dev/discs/disc0/part1<br />
mount -t ext3 /dev/sda1 /mnt<br />
mount -t proc proc /mnt/proc<br />
mount -t sysfs sys /mnt/sys<br />
mount -o bind /dev /mnt/dev<br />
<br />
chroot /mnt /bin/bash<br />
<br />
Now you should be logged in as root, and into your current installation as if you had just booted it and logged in as root.<br />
<br />
If your /boot directory is on the same partition as your /, move on to the next step. If on the other hand it's on a separate partition (for example, /dev/sda2), then you need to mount that partition now to /boot so that grub can find the files it needs:<br />
<br />
mount -t ext2 /dev/sda2 /boot<br />
<br />
===Reinstalling GRUB===<br />
Edit <tt>/boot/grub/menu.lst</tt> and make sure that everything is in order. Once you are completely sure that <tt>menu.lst</tt> is correct, run the following command:<br />
<br />
grub-install /dev/sda<br />
<br />
This command should complete sucessfully if you have followed all the steps. (If not, take a look at the notes below.) That's it, you're done! Exit chroot and reboot:<br />
<br />
cd /<br />
umount -a<br />
exit<br />
cd /<br />
umount -a<br />
reboot<br />
<br />
====Errors====<br />
If you get an error that says <tt>The file /boot/grub/stage1 not read correctly</tt>, it probably means that your fstab/mtab is incorrect for some reason and needs to be fixed. These files are <tt>/etc/mtab</tt> and <tt>/etc/fstab</tt>. Edit them and make sure they point to the correct partitions, then rerun grub-install.<br />
<br />
If this still doesn't fix the error message and you're using ext2/3 as filesystem for your boot partition, use "tune2fs -l /dev/sda1" to check for the Inode size of your root/boot partition. Anything else than 128 will make grub unable to read the partition. The only solution for this problem is to recreate your rootfs with the correct options (fix /etc/mke2fs.conf and set inode_size to 128).<br />
<br />
If you get an error that says <tt>sed: can't read /boot/grub/device.map: No such file or directory</tt>, it means that you need to use the --recheck option with grub-install.<br />
<br />
grub-install --recheck /dev/sda<br />
<br />
Hopefully that covers all the issues you should encounter. If you get any other errors, reboot and do the guide step-by-step again.</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=70232
User:Faelar
2009-06-09T11:04:51Z
<p>Faelar: /* Introduction */ début traduction</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:System recovery (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Reinstalling GRUB}}<br />
{{i18n_entry|Español|Reinstalando GRUB}}<br />
{{i18n_entry|Česky|Přeinstalování GRUBu (Česky)}}<br />
{{i18n_entry|Italiano|Reinstalling GRUB (Italiano)}}<br />
{{i18n_entry|Ελληνικά|Reinstalling GRUB (Ελληνικά)}}<br />
{{i18n_entry|简体中文|重装GRUB}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==Introduction==<br />
<br />
Ce guide va vous montrer comment réinstaller GRUB avec un CD d'Installation d'Arch si vous perdez GRUB d'une manière ou d'une autre.<br />
<br />
===Notes===<br />
<br />
*Dans ce guide, j'utiliserai <tt>sda</tt> comme ma racine udev type de référence. Si vous utilisez une version du CD d'Installation pre-0.7.1, vous devrez substituer les références à udev par les références pour devfs. Voir [[Technical Terms#Hard Drives|Hard Drives]] si cela n'a pas de sens pour vous.<br />
<br />
*Aussi, sachez que ce guide vise les gens utilisant les pilotes SATA, pas IDE aussi substituez les noms IDE comme <tt>hda</tt> au lieu de <tt>sda</tt> si vous avez des périphériques IDE et que vous n'utilisez pas libata.<br />
<br />
== Booting the Install CD ==<br />
The first thing you will need is an [http://www.archlinux.org/download Install CD]. Any install CD should work; however, using the latest CD will be easier than using an older CD.<br />
<br />
Boot the CD as if you were doing an installation ('''DO NOT''' use the <tt>root= option</tt>) and move on to the next step.<br />
<br />
=== Mount and Chroot into Your Current Installation ===<br />
Now, you need to mount your current installation. The general process for this is as follows:<br />
*NOTE: You need to know what the proper partitions and filesystem types are. I will use <tt>sda1</tt> as the root partition and <tt>ext3</tt> as the filesystem in this example; change those for your personal setup.<br />
<br />
cd /<br />
# If you are using a pre-0.7.1 CD, sda1 will be /dev/discs/disc0/part1<br />
mount -t ext3 /dev/sda1 /mnt<br />
mount -t proc proc /mnt/proc<br />
mount -t sysfs sys /mnt/sys<br />
mount -o bind /dev /mnt/dev<br />
<br />
chroot /mnt /bin/bash<br />
<br />
Now you should be logged in as root, and into your current installation as if you had just booted it and logged in as root.<br />
<br />
If your /boot directory is on the same partition as your /, move on to the next step. If on the other hand it's on a separate partition (for example, /dev/sda2), then you need to mount that partition now to /boot so that grub can find the files it needs:<br />
<br />
mount -t ext2 /dev/sda2 /boot<br />
<br />
===Reinstalling GRUB===<br />
Edit <tt>/boot/grub/menu.lst</tt> and make sure that everything is in order. Once you are completely sure that <tt>menu.lst</tt> is correct, run the following command:<br />
<br />
grub-install /dev/sda<br />
<br />
This command should complete sucessfully if you have followed all the steps. (If not, take a look at the notes below.) That's it, you're done! Exit chroot and reboot:<br />
<br />
cd /<br />
umount -a<br />
exit<br />
cd /<br />
umount -a<br />
reboot<br />
<br />
====Errors====<br />
If you get an error that says <tt>The file /boot/grub/stage1 not read correctly</tt>, it probably means that your fstab/mtab is incorrect for some reason and needs to be fixed. These files are <tt>/etc/mtab</tt> and <tt>/etc/fstab</tt>. Edit them and make sure they point to the correct partitions, then rerun grub-install.<br />
<br />
If this still doesn't fix the error message and you're using ext2/3 as filesystem for your boot partition, use "tune2fs -l /dev/sda1" to check for the Inode size of your root/boot partition. Anything else than 128 will make grub unable to read the partition. The only solution for this problem is to recreate your rootfs with the correct options (fix /etc/mke2fs.conf and set inode_size to 128).<br />
<br />
If you get an error that says <tt>sed: can't read /boot/grub/device.map: No such file or directory</tt>, it means that you need to use the --recheck option with grub-install.<br />
<br />
grub-install --recheck /dev/sda<br />
<br />
Hopefully that covers all the issues you should encounter. If you get any other errors, reboot and do the guide step-by-step again.</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=70231
User:Faelar
2009-06-09T10:58:47Z
<p>Faelar: </p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:System recovery (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Reinstalling GRUB}}<br />
{{i18n_entry|Español|Reinstalando GRUB}}<br />
{{i18n_entry|Česky|Přeinstalování GRUBu (Česky)}}<br />
{{i18n_entry|Italiano|Reinstalling GRUB (Italiano)}}<br />
{{i18n_entry|Ελληνικά|Reinstalling GRUB (Ελληνικά)}}<br />
{{i18n_entry|简体中文|重装GRUB}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==Introduction==<br />
<br />
This guide will show you how to reinstall GRUB with an Arch Installation CD if you lose GRUB somehow.<br />
<br />
===Notes===<br />
<br />
*In this guide, I'll be using <tt>sda</tt> as my root udev type references. If you are using a pre-0.7.1 installation CD, you will have to substitute udev references for devfs references. See [[Technical Terms#Hard Drives|Hard Drives]] if this doesn't make sense.<br />
<br />
*Also, be aware that this guide is aimed at people using SATA drives, not IDE so subsitute IDE names like <tt>hda</tt> iinstead of <tt>sda</tt> if you have IDE devices and you are not using libata.<br />
<br />
== Booting the Install CD ==<br />
The first thing you will need is an [http://www.archlinux.org/download Install CD]. Any install CD should work; however, using the latest CD will be easier than using an older CD.<br />
<br />
Boot the CD as if you were doing an installation ('''DO NOT''' use the <tt>root= option</tt>) and move on to the next step.<br />
<br />
=== Mount and Chroot into Your Current Installation ===<br />
Now, you need to mount your current installation. The general process for this is as follows:<br />
*NOTE: You need to know what the proper partitions and filesystem types are. I will use <tt>sda1</tt> as the root partition and <tt>ext3</tt> as the filesystem in this example; change those for your personal setup.<br />
<br />
cd /<br />
# If you are using a pre-0.7.1 CD, sda1 will be /dev/discs/disc0/part1<br />
mount -t ext3 /dev/sda1 /mnt<br />
mount -t proc proc /mnt/proc<br />
mount -t sysfs sys /mnt/sys<br />
mount -o bind /dev /mnt/dev<br />
<br />
chroot /mnt /bin/bash<br />
<br />
Now you should be logged in as root, and into your current installation as if you had just booted it and logged in as root.<br />
<br />
If your /boot directory is on the same partition as your /, move on to the next step. If on the other hand it's on a separate partition (for example, /dev/sda2), then you need to mount that partition now to /boot so that grub can find the files it needs:<br />
<br />
mount -t ext2 /dev/sda2 /boot<br />
<br />
===Reinstalling GRUB===<br />
Edit <tt>/boot/grub/menu.lst</tt> and make sure that everything is in order. Once you are completely sure that <tt>menu.lst</tt> is correct, run the following command:<br />
<br />
grub-install /dev/sda<br />
<br />
This command should complete sucessfully if you have followed all the steps. (If not, take a look at the notes below.) That's it, you're done! Exit chroot and reboot:<br />
<br />
cd /<br />
umount -a<br />
exit<br />
cd /<br />
umount -a<br />
reboot<br />
<br />
====Errors====<br />
If you get an error that says <tt>The file /boot/grub/stage1 not read correctly</tt>, it probably means that your fstab/mtab is incorrect for some reason and needs to be fixed. These files are <tt>/etc/mtab</tt> and <tt>/etc/fstab</tt>. Edit them and make sure they point to the correct partitions, then rerun grub-install.<br />
<br />
If this still doesn't fix the error message and you're using ext2/3 as filesystem for your boot partition, use "tune2fs -l /dev/sda1" to check for the Inode size of your root/boot partition. Anything else than 128 will make grub unable to read the partition. The only solution for this problem is to recreate your rootfs with the correct options (fix /etc/mke2fs.conf and set inode_size to 128).<br />
<br />
If you get an error that says <tt>sed: can't read /boot/grub/device.map: No such file or directory</tt>, it means that you need to use the --recheck option with grub-install.<br />
<br />
grub-install --recheck /dev/sda<br />
<br />
Hopefully that covers all the issues you should encounter. If you get any other errors, reboot and do the guide step-by-step again.</div>
Faelar
https://wiki.archlinux.org/index.php?title=Getting_Started&diff=56378
Getting Started
2008-12-27T21:34:16Z
<p>Faelar: languages added</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Getting_Started}}<br />
{{i18n_entry|Français|Pour_Commencer_(Français)}}<br />
{{i18n_links_end}}<br />
<br />
The following links are very useful in getting started with Arch Linux. Many of them will explain the philosophy of Arch and why it is different than other distributions. They are not meant to convince you to choose Arch-that choice is for you to make.<br />
<br />
[[Arch Linux]] - This article attempts to give a brief overview of Arch Linux. It briefly describes some of the tools of an installed Arch Linux system.<br />
<br />
[[Arch Compared To Other Distros]] - This page summarizes some of the similarities and differences between Arch and other distributions.<br />
<br />
[[FAQ]] - Self-explanatory. A list of common and frequently asked questions.<br />
<br />
[[The Arch Way]] - This page tries to describe the principles and philosophy of Arch Linux.<br />
<br />
[[Beginners Guide]] - This documentation will guide you through the whole process of installing and configuring Arch Linux.<br />
<br />
[[Official Arch Linux Install Guide]] - The guide to doing an install. A bit more general than the beginners guide above; it assumes the user is more experienced in UNIX methodology. The official location for this guide is [http://www.archlinux.org/static/docs/arch-install-guide.html here].<br />
<br />
[[Table of Contents (English)|Table of Contents]] - A listing of several helpful articles, covering everything from [[:Category: System administration (English)|System administration]] to [[:Category: Live Arch systems (English)|Live Arch systems]].<br />
<br />
[[ArchWiki Tutorial]] - This is a short tutorial on editing and contributing to the Arch Linux Wiki.</div>
Faelar
https://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=55595
ASUS Eee PC 701
2008-12-15T18:11:31Z
<p>Faelar: /* Speeding up udev for faster boot */</p>
<hr />
<div>{{stub}}<br />
[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
'''WARNING: THIS ARTICLE IS INCOMPLETE!''' Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum]. There is also a nice Arch Linux installation guide on the [http://wiki.eeeuser.com/installingarchlinux EeeUser Wiki].<br />
<br />
Note: Users of 901/1000 series eee pcs should follow the [[Asus Eee PC 901|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.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]] '''(Recommended)'''<br />
<br />
==Installing Arch Linux==<br />
<br />
* '''NOTE:''' Please refer to The [[Beginners_Guide]] for detailed instructions, if needed. Ideally, your CD/USB should boot up just fine on Eee PC without any need for additional options.<br />
<br />
===Booting Arch the installation CD/USB===<br />
<br />
The stock kernel on Arch installation media since 2008.06 and newer support Eee's ethernet network card (or at least it should, mine didn't, to be on the safe side, get toofishes' kernel - 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 />
<br />
* '''NOTE:''' Non-FTP install only<br />
The installer should mount USB source media automatically. If it fails you can manually mount the source media on the stick to the /src directory with the following command:<br />
<br />
mount /dev/sd[x] /src<br />
<br />
===Start the Installation===<br />
<br />
Just run<br />
<br />
/arch/setup<br />
<br />
To start the installation just like normal.<br />
<br />
===Prepare Hard Drive===<br />
<br />
The default Eee PC drive is split up into four partitions (here is [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* It is easiest to wipe the existing partitions and use one or two partitions for your install. One partition would be just '/', and two partitions would be '/boot' and '/'.<br />
* Choose "NONE" for swap in case your eee has a SSD (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* Select "ext2" as your filesystem in case your eee has a SSD (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]). If your model has a standard HD choose "ext3".<br />
<br />
===Select Packages===<br />
<br />
Choose the proper source of package, this should be done automatically if you are installing from USB.<br />
<br />
In addition to the '''BASE''' category, you also need all of the packages in the '''DEVEL''' category if you are planning on compiling stuffs on your Eee.<br />
<br />
If you intended to use wireless, then you'll also need the ''wireless_tools'' package from '''SUPPORT''' category.<br />
<br />
If you intend to use wired lan, then you'll need the ''atl2'' package<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 following [http://wiki.archlinux.org/index.php/Installing_Arch_Linux_on_the_Asus_EEE_PC#Using_stock_kernel this] guide to build modules for the eee that the default arch kernel currently doesn't support (wifi and acpi). 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 />
====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 /etc/pacman.conf to use the repository.<br />
<br />
======Package List======<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' <br />
customized kernel for Eee - it also contains the wireless, to load it, type modprobe ath5k or/and add it to MODULES line in rc.conf<br />
*'''luvcview''' <br />
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 />
<br />
pacman -Sy kernel-eee<br />
<br />
Then, add the following to /boot/grub/menu.lst; note that no initrd is needed:<br />
# (2) Arch Linux<br />
title Arch Linux EEE kernel<br />
root (hd0,0)<br />
kernel /boot/vmlinuzeee root=/dev/sda1 ro<br />
<br />
Restart and select Arch Linux EEE kernel from the grub boot menu.<br />
<br />
====Using stock kernel====<br />
'''If you used the custom kernel above, skip this section'''<br />
<br />
Since the stock kernel lacks the modules for wifi and acpi; support for these must be added seperately.<br />
<br />
=====Prepare your system for building unsupported modules=====<br />
If you have internet through wired lan, complete the beginner's guide up to and including '''Update System''', reboot and then continue selecting your [http://wiki.archlinux.org/index.php/Installing_Arch_Linux_on_the_Asus_EEE_PC#Select_your_desired_method_for_building_unsupported_modules desired method]<br />
<br />
'''If not''', you will need to build (at least) the wifi module twice, once for the current kernel and once for the new one. In this case use one of two methods:<br />
* '''METHOD 1 - eeemodules-hal package''' Download the URLs in the 'source' section of [http://aur.archlinux.org/packages/eeemodules-hal/eeemodules-hal/PKGBUILD this] and download [http://aur.archlinux.org/packages/eeemodules-hal/eeemodules-hal.tar.gz this], then use USB storage to transfer the downloaded files to the eee. After extracting eeemodules-hal.tar.gz, put the other files you downloaded into the eeemodules-hal directory and return here after following [http://wiki.archlinux.org/index.php/Installing_Arch_Linux_on_the_Asus_EEE_PC#Install_All_the_Necessary_Modules_using_the_eeemodules-hal_package this] guide to build and install the package.<br />
* '''METHOD 2 - madwifi source''' Download the latest Atheros wireless driver from [http://snapshots.madwifi-project.org/madwifi-hal-0.10.5.6/ here], then use USB storage to transfer the downloaded files to the eee. Return here after following [http://wiki.archlinux.org/index.php/Installing_Arch_Linux_on_the_Asus_EEE_PC#Atheros_wireless_ethernet_driver these] compile instructions.<br />
Once you have wireless internet, complete the beginner's guide up to and including '''Update System''', make sure you have any sources you need for the next section downloaded to your eee, reboot into the latest kernel (which once again lacks wireless) and then continue selecting your [http://wiki.archlinux.org/index.php/Installing_Arch_Linux_on_the_Asus_EEE_PC#Select_your_desired_method_for_building_unsupported_modules desired method] keeping in mind that you already have the sources downloaded.<br />
<br />
=====Select your desired method for building unsupported modules=====<br />
Module support for wifi and acpi can be added one of two ways:<br />
* '''METHOD 1 - eeemodules-hal package''' Use [http://wiki.archlinux.org/index.php/Installing_Arch_Linux_on_the_Asus_EEE_PC#Install_All_the_Necessary_Modules_using_the_eeemodules-hal_package this] guide to install the eeemodules-hal package, which provides all the missing modules for the eee (preferred approach)<br />
* '''METHOD 2 - madwifi & ASUS ACPI source''' Use [http://wiki.archlinux.org/index.php/Installing_Arch_Linux_on_the_Asus_EEE_PC#Compile_and_Install_All_the_Necessary_Modules_from_Source this] guide to download, compile and install all the modules manually<br />
<br />
=====Install All the Necessary Modules using the eeemodules-hal package=====<br />
Adapted from the now out of date package by '''dkite''', eeemodules-hal is a package to be used with Arch's stock kernel; it contains the modules for everything archlinux doesn't already support (wifi and acpi). <br />
<br />
*Download the package eeemodules-hal.tar.gz from the [http://aur.archlinux.org AUR] @ [http://aur.archlinux.org/packages.php?ID=19256 http://aur.archlinux.org/packages.php?ID=19256]. <br />
* '''IMPORTANT''' Uncompress it somewhere you can keep the package; this is the downside to using the stock kernel and an important step for this route because :<br />
-Each minor kernel upgrade (eg: 2.6.27.X) will overwrite asus_acpi, requiring that package you will be compiling is available for reinstall<br />
-Each major kernel upgrade (eg: 2.6.X) requires that modules are rebuilt against it; eeemodules-hal must be uninstalled, then the eee must be rebooted into the new kernel and eeemodules-hal rebuilt and reinstalled. Until reinstalling eeemodules-hal, wifi won't be available; unless wired lan is or you use a usb storage device to copy from another computer, the sources must have previously been downloaded onto the computer in order to compile.<br />
*In a console, change directory to the eeemodules-hal folder<br />
1. If this building over a previous build, ensure the old package file has been deleted or (preferably) backed up outside this directory<br />
2. To download any sources not already downloaded and compile, run 'makepkg'<br />
3. To install the package once its been compiled, run 'pacman -U eeemodules-hal<version>.tar.gz' (where <version> is the version of eeemodules-hal)<br />
''NOTE'': If it complains, you may need to run 'pacman -Uf eeemodules-hal<version>.tar.gz' to overwrite the asus_acpi provided by the kernel<br />
4. To enable asus_acpi on boot, add it to the MODULES array in /etc/rc.conf, MODULES = (... asus_acpi ...)<br />
5. If your wireless device hasn't activated after installing, you may need to blacklist the ath5k module in /etc/rc.conf 'MODULES = (... !ath5k ...)' and reboot<br />
<br />
=====Compile and Install All the Necessary Modules from Source=====<br />
'''IMPORTANT''' These must be recompiled and reinstalled after each major kernel upgrade (2.6.X). ASUS ACPI must also be reinstalled after each minor kernel upgrade (2.6.27.X)<br />
<br />
======Atheros wireless ethernet driver======<br />
'''NOTE''' This is also available in the the madwifi-newhal-svn package from the AUR<br />
<br />
Download the latest driver from http://snapshots.madwifi-project.org/madwifi-hal-0.10.5.6/ (If there are problems, revision 3879 is known to work)<br />
<br />
Uncompress the source from the snapshot and 'cd' to the source directory<br />
1. If this is building over a previous build, run 'make clean'<br />
2. Compile the sources by running 'BINDIR=/usr/bin MANDIR=/usr/man make'<br />
3. Install the driver by running 'sudo BINDIR=/usr/bin MANDIR=/usr/man make install'<br />
4. Now run 'depmod' or reboot your eee to use the newly installed drivers<br />
5. If your wireless device hasn't activated, you may need to blacklist the ath5k module in /etc/rc.conf 'MODULES = (... !ath5k ...)' and reboot<br />
<br />
======ASUS ACPI driver======<br />
Download the ASUS ACPI package from [ftp://ftp.asus.com/pub/ASUS/EeePC/701/ASUS_ACPI_071126.rar ftp://ftp.asus.com/pub/ASUS/EeePC/701/ASUS_ACPI_071126.rar] into ~/temp<br />
<br />
Download [http://aur.archlinux.org/packages/eeemodules-hal/eeemodules-hal.tar.gz http://aur.archlinux.org/packages/eeemodules-hal/eeemodules-hal.tar.gz] and extract acpi.patch and asus_acpi.makefile.patch into ~/temp<br />
<br />
1. cd ~/temp<br />
2. unrar e -y ASUS_ACPI_071126.rar<br />
3. tar xzf asus_acpi.tar.gz<br />
4. cd asus_acpi<br />
5. patch -p0 <../acpi.patch<br />
6. patch -p1 < ../asus_acpi.makefile.patch<br />
7. make<br />
8. sudo rm /lib/modules/$(uname -r)/kernel/drivers/acpi/asus_acpi.ko<br />
9. sudo install -D -m644 asus_acpi.ko /lib/modules/$(uname -r)/kernel/drivers/acpi/asus_acpi.ko<br />
10. To enable asus_acpi on boot, add it to the MODULES array in /etc/rc.conf, MODULES = (... asus_acpi ...)<br />
11. Now run 'sudo modprobe asus_acpi' or reboot your eee to use the newly installed drivers<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.<br />
<br />
===Add the Final Touch===<br />
<br />
After you have install kernel-eee and all the related packages as noted above, make these edits to /etc/fstab:<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* '''OPTIONAL:''' Add a new line: "tmpfs /var/log tmpfs size=1M 0 0" ('''WARNING:''' this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]. To save your startup/shutdown logs, look at the pitfalls link above).<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. The following is the guide on how to get the rest of your system working.<br />
<br />
===Xorg===<br />
<br />
You have two choices for video on the Eee - the newer <b>xf86-video-intel</b> driver, or the older <b>xf86-video-i810</b> driver paired with 915resolution. The intel driver is the focus upstream and is being actively developed so it is your best choice. <br />
<br />
However, if you wish to use composite extension (for Compiz Fusion, for example), then the old i810 driver might be a better option, mainly because XV video output does not work when composite is enabled on the currently intel driver and thus a lot of applications, such as Skype or UCView, will not function properly.<br />
<br />
You need these packages in addition to the Xorg's packages:<br />
<br />
pacman -Sy synaptics xf86-video-intel<br />
<br />
If you choose to use the older i810 video, you will have to install xf86-video-i810 and 915resolution as well. Note that the i810 driver and the intel driver cannot both be installed at the same time.<br />
<br />
Then, just drop in the following xorg.conf into your /etc/X11/ directory (updated Dec 3rd 2008 for change in synaptic config):<br />
<br />
<pre>Section "ServerLayout"<br />
Identifier "ArchLinux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "extmod"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail"<br />
Option "BlankTime" "5"<br />
Option "AIGLX" "false"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "keyboard"<br />
Driver "kbd"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbLayout" "us"<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "IMPS/2"<br />
Option "Emulate3Buttons" "yes"<br />
Option "ZAxisMapping" "4 5"<br />
Option "CorePointer"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "synaptics"<br />
Driver "synaptics"<br />
Option "Device" "/dev/psaux"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1000"<br />
Option "RightEdge" "5400"<br />
Option "TopEdge" "1000"<br />
Option "BottomEdge" "4900"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "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 />
If you want to set up the i810 driver instead, you will also have to configure 915resolution and add it to your daemons line. This is not needed for the intel driver. Edit the /etc/conf.d/915resolution to look like this:<br />
<br />
<pre># Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
</pre><br />
<br />
Now put the 915resolution daemon into your /etc/rc.conf file:<br />
<br />
<pre>DAEMONS=(... 915resolution ...)</pre><br />
<br />
===Sound, Webcam & Microphone===<br />
<br />
====Sound====<br />
<br />
Some people have reported sound working right out of the box with no troubles. However, others might need to add to /etc/modprobe.conf the following line for the EeePC 701<br />
<pre>options snd-hda-intel model=3stack-dig</pre><br />
or the following one for the EeePC 900 model<br />
<pre>options snd-hda-intel model=auto</pre><br />
<br />
If your internal microphone doesn't work, you probably have to turn the capture feature on. Simply fire up alsamixer, find your Capture control, and press spacebar to enable it.<br />
<br />
====Webcam====<br />
<br />
You can enable your built-in webcam by adding the following line to your /etc/rc.local file.<br />
<br />
echo 1 > /proc/acpi/asus/camera<br />
<br />
If you want the webcam application that the default Xandos installation uses, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14469 ucview from the AUR].<br />
<br />
The webcam also works fine with the latest version of Skype.<br />
<br />
If you already have mplayer installed you can launch :<br />
mplayer -fps 15 tv://<br />
<br />
I have yet to get it working with vlc or any other software such as xawtv. If you know how, please update this.<br />
<br />
*'''NOTE:''' For anyone who has accidentally disabled Auto Exposure for their webcam in luvcview (making the image dark), and can't enable it again, do the following:<br />
<br />
Install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14468 libwebcam from the AUR].<br />
<br />
Issue the following command:<br />
<pre>uvcdynctrl --set "Exposure, Auto" 4</pre><br />
<br />
*'''NOTE:''' Be sure the "OS Installation" option is set to "finished" in the BIOS' "Advanced" tab or your camera may not work in some applications (like Skype).<br />
<br />
====Microphone====<br />
<br />
Solution for problems with the internal microphone.<br />
<br />
1. First of all set in alsamixer "Input Source" to "i-Mic"<br />
<br />
2. Increase "Capture" and "i-Mic Boost" to your needs<br />
<br />
3. Edit /etc/asound.state the following, change the 2 "false" to "true" like showing:<br />
<pre><br />
....snap.....<br />
control.11 {<br />
comment.access 'read write'<br />
comment.type BOOLEAN<br />
comment.count 2<br />
iface MIXER<br />
name 'Capture Switch'<br />
value.0 true<br />
value.1 true<br />
}<br />
....snap....</pre><br />
<br />
4. After editing run following as root<br />
<pre>alsactl restore</pre><br />
<br />
5. Now your internal microphone should be working.<br />
<br />
===Getting Hot Keys, Graphic Indicators and Shutdown with the Power Button Working===<br />
<br />
If you want to have working hot keys (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 /etc/acpi/eee.conf to suit your tastes.<br />
<br />
*For those who use the wireless on/off acpi command; the NETWORK_UP_COMMAND="" setting in /etc/acpi/eee.conf, when applicable, should at least release the network. For example, using netcfg2, NETWORK_UP_COMMAND="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.<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/gitprojects/eee.git<br />
<br />
There are two ways to tweak the kernel. The first is simply to edit the <code>kernelconfig</code> file with your favorite editor and the second is to insert a <code>make menuconfig</code> line into the PKGBUILD before the kernel's compilation.<br />
<br />
===Using Wine with toofishes' kernel===<br />
<br />
Normally, Wine won't work with toofishes' kernel because it is compiled with VMSPLIT_2G_OPT option. In order to use Wine with toofishes' kernel, you have to recompile his kernel with VMSPLIT_3G option.<br />
<br />
Download the kernel PKGBUILD and all the necessary files from toofishes' gitweb using the above instructions, then change the following lines in the <code>kernelconfig</code> file<br><br />
from this:<br />
<pre><br />
...<br />
230 CONFIG_NOHIGHMEM=y<br />
231 # CONFIG_HIGHMEM4G is not set<br />
232 # CONFIG_HIGHMEM64G is not set<br />
233 # CONFIG_VMSPLIT_3G is not set<br />
234 # CONFIG_VMSPLIT_3G_OPT is not set<br />
235 # CONFIG_VMSPLIT_2G is not set<br />
236 CONFIG_VMSPLIT_2G_OPT=y<br />
237 # CONFIG_VMSPLIT_1G is not set<br />
...<br />
</pre><br />
<br />
to this:<br />
<pre><br />
...<br />
230 CONFIG_NOHIGHMEM=y<br />
231 # CONFIG_HIGHMEM4G is not set<br />
232 # CONFIG_HIGHMEM64G is not set<br />
233 CONFIG_VMSPLIT_3G=y<br />
234 # CONFIG_VMSPLIT_3G_OPT is not set<br />
235 # CONFIG_VMSPLIT_2G is not set<br />
236 # CONFIG_VMSPLIT_2G_OPT is not set<br />
237 # CONFIG_VMSPLIT_1G is not set<br />
...<br />
</pre><br />
Compile and install the kernel and Wine should now work.<br />
<br />
===Power down with the power button===<br />
<br />
* '''NOTE:''' If you are using ighea's acpi-eee or dkite's acpid_eee package then you should already be able to shutdown by pressing the power button and should not need to do this.<br />
<br />
The two alternatives here are described in [[Allow_users_to_shutdown]].<br />
<br />
If you don't already or don't plan to use sudo, it may be simpler to use the setuid /sbin/halt method, otherwise using sudo is preferred.<br />
<br />
Below are all the steps required for the sudo method. If you want to use the setuid method, read the article linked above and perform the 'power' file step here, while omitting the 'sudo' in it.<br />
<br />
<pre>pacman -S sudo</pre><br />
<br />
As root, do the following:<br />
<br />
<pre>visudo</pre><br />
<br />
Add the following line to the file:<br />
<br />
<pre>USER HOST = NOPASSWD: /sbin/poweroff</pre><br />
<br />
Where USER = the user you want to be able to power down with and HOST = your hostname (from /etc/rc.conf).<br />
<br />
Now, create a file called /etc/acpi/events/power, containing:<br />
<br />
<pre># /etc/acpi/events/power<br />
# This is called when the user presses the power button<br />
<br />
event=button/power (PWR.||PBTN)<br />
action=sudo /sbin/poweroff</pre><br />
<br />
Make sure that you execute<br />
<br />
<pre>/etc/rc.d/acpid start</pre><br />
<br />
And/or add acpid to the daemons list in /etc/rc.conf:<br />
<br />
<pre>DAEMONS=(hal, acpid ...</pre><br />
<br />
===Use cpufreq for power saving===<br />
<br />
* '''NOTE:''' If you are using toofishes's kernel, then processor scaling is already enable and you don't need to do the following steps.<br />
<br />
Install cpufrequtitls.<br />
pacman -S cpufrequtils<br />
<br />
For scaling down the processor you have to load the p4_clockmod module. Insert it into your /etc/rc.conf MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
<br />
Add 'cpufreq' to the DAEMONS array in /etc/rc.conf to have it start on startup.<br />
DAEMONS=(... cpufreq ...)<br />
<br />
Add the following into /etc/conf.d/cpufreq<br />
governor="ondemand"<br />
min_freq="113MHz"<br />
max_freq="900MHz"<br />
<br />
With enabled cpufreq it scales the processor between 113MHz up to max. frequency. That should save a lot on battery power. The stated 900MHz will be never reached by the eeePC, the p4_clockmod reports a wrong frequency here. But scaling works, you can feel it in the performance of eeePC that he slow down the processor.<br />
<br />
===More responsive system with ondemand governor===<br />
The default up_threshold (where it will bump to a faster speed) for the CPU governor is 80, which means it will increase the CPU speed when utilization is above 80%. This can make X applications have a bit of lag. <br />
Try changing this value:<br />
sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
With 40 it still leaves the majority of CPU cycles at the lowest available clock speed but increases responsiveness. You can add this line to one of your startup scripts (such as /etc/rc.local) if you wish to keep it, for example:<br />
<pre><br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
<br />
echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold<br />
</pre><br />
<br />
Also, following line is also reported to help makes system more responsive. You can use it by adding it to your /etc/rc.local:<br />
<pre><br />
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate<br />
</pre><br />
<br />
===Speeding up udev for faster boot===<br />
* [[Speedup udev]]<br />
*http://dev.laptop.org/ticket/4349<br />
*[http://www.eeesale.com/Asus-Eee-PC-overclock-Benchmarks.htm Speed up the Eee PC]<br />
<br />
You can also disable the autoload by editing your ''rc.conf'' :<br />
...<br />
MOD_AUTOLOAD="no"<br />
...<br />
MODULES=(pciehp 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's BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USBStick formated in fat32.<br />
To format an USBStick, use cfdisk tool :<br />
cfdisk /dev/sdc #could be something else than "c"<br />
Choose [delete], [type] : "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
cp /somewhere/blabla/.../thecurrentnameofthefile.rom /dev/sdc1/701.rom<br />
The name of the copy '''must''' be 701.rom<br />
<br />
Next step, reboot the eeepc with the USBStick pluged-in, and press<br />
Alt + F2<br />
It will launch the built-in tool. Everything should be Ok, you can make a coffee during the update. When it asks you to push the power-button it has finished.<br />
<br />
At the next boot, you'll be invited to configure the BIOS. Check if the everything is enabled (my webcam and wireless were disabled after the update) and if it displays the good version in the main screen. It's done !<br />
<br />
=== More usuable font sizes ===<br />
<br />
====The_glu's method====<br />
<br />
I found a easy solution who work on a 901 :<br />
<br />
Edit <code>/etc/X11/xinit/xserverrc</code> and add "-dpi 134"<br />
<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 .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 ~/.Xdefaults:<br />
Xft*dpi: 134<br />
<br />
This then caused the fonts to be even bigger, so I set them all to be font-size 6 by adding the following into ~/.gtkrc-2.0 (note this will be overwritten if you use any tools to change GTK settings):<br />
style "user-font"<br />
{<br />
font_name="Bitstream Vera Sans 6"<br />
}<br />
widget_class "*" style "user-font"<br />
<br />
To do the same with KDE fonts (without KDE installed) you have to add the following to ~/.kde/share/config/kdeglobals:<br />
[General]<br />
StandardFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
activeFont=Bitstream Vera Sans,6,-1,5,75,0,0,0,0,0<br />
fixed=Bitstream Vera Sans Mono,6,-1,5,50,0,0,0,0,0<br />
font=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
menuFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
taskbarFont=Bitstream Vera Sans,6,-1,5,50,1,0,0,0,0<br />
toolBarFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
<br />
To make your fonts even prettier enable the [[Fonts#Fonts_with_LCD_filter_enabled|LCD Fonts]].<br />
<br />
==== Alternative Method ====<br />
<br />
For me it worked far better to open the gnome appearance control panel, go to the fonts tab, click defaults, and change the resolution to be 96 dpi. Changing .Xdefaults doesnt work when running gnome, as gnome-settings-daemon overrides it. You can then leave all font sizes at their default, and things should look good. Simply changing the font sizes and leaving the DPI at its technically correct value (~134) gave me weird layout problems in some apps, and oddly large fonts in others.<br />
<br />
<br />
<br />
==Known problems and their solutions==<br />
<br />
===Wireless doesn't work, even after installing custom Madwifi module===<br />
<br />
I found that Arch tried to use the ath5k module for wireless, and that meant it took control of the card rather than ath_pci (the module I had compiled and installed). I got a Madwifi status 3 message in dmesg when this happened.<br />
<br />
The solution is to blacklist the ath5k module in /etc/rc.conf:<br />
<br />
MODULES = ( ... !ath5k ... )<br />
<br />
===Laggy or Unresponsive ACPI Events===<br />
<br />
The latest kernel (2.6.26) introduces new problems with Eee's ACPI events handling. Basically, ACPI events become very laggy and after some time ACPI get disabled after a heavy usage (e.g. changing volume, brightness). This problem affects both stock kernel and toofishes' kernel.<br />
<br />
It appears that the solution is to apply this [http://bugzilla.kernel.org/attachment.cgi?id=16862 patch] ([http://bugzilla.kernel.org/show_bug.cgi?id=10724 original bug report]) to the kernel. <br />
<br />
*'''Note:''' the latest toofishes' kernel, version 2.6.26-1, now include the patch, but you can still use ighea's one for the extras features listed below.<br />
<br />
Until toofishes update his kernel to include the patch, you can use ighea's slightly modified toofishes' kernel that included the above patch, as well as other modifications:<br />
<br />
*Support for Wine <br />
*uvesafb is built as module <br />
*Use [http://bbs.archlinux.org/viewtopic.php?pid=393860#p393860 new eeepc-laptop driver] (which also handles fan-control) instead of older acus_acpi or asus-laptop -drivers.<br />
<br />
You can get the modified kernel, as well as the associative packages, from [http://koti.kapsi.fi/~ighea/eee/kernel-eee/ here].<br />
<br />
After you have downloaded the packages, Install them using this command:<br />
<br />
pacman -U kernel-eee-2.6.26-1-i686.pkg.tar.gz madwifi-eee-svn-3752-1-i686.pkg.tar.gz <br />
<br />
You might also want to use IgnorePkg-line in /etc/pacman.conf to hold packages from being accidentally updated.<br />
<br />
IgnorePkg = kernel-eee madwifi-eee-svn<br />
<br />
Also don't forget to upgrade ighea's acpi-eee package to version 9.6.<br />
<br />
===Shutdown Problem===<br />
<br />
If your Eee won't shutdown properly (i.e. the power indicator LED is on but the LCD screen is off), then add the following lines to your /etc/rc.local.shutdown file.<br />
<pre><br />
#! /bin/bash<br />
#<br />
# /etc/rc.local.shutdown: Local shutdown script.<br />
#<br />
<br />
# Comment or uncomment the following two lines according to your system configuration.<br />
<br />
/etc/rc.d/mpd stop # If you're using mpd, then you have to stop its daemon first.<br />
<br />
/etc/rc.d/alsa stop # If you're using ALSA daemon, then you also have to stop it.<br />
<br />
# The following line is Eee specific fix, you always need to have this line in /etc/rc.local.shutdown.<br />
<br />
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind<br />
</pre><br />
The above solution should fix the shutdown problem in most cases. But if for some reason the problem still persists, the module may not be able to be unloaded until after all services have finished. Do the above, then in /etc/rc.shutdown move <br />
<br />
if [ -x /etc/rc.local.shutdown ]; then<br />
/etc/rc.local.shutdown<br />
fi<br />
<br />
from where it was to directly above the line <br />
<br />
# Terminate all processes<br />
<br />
this will cause the rc.local.shutdown script to run after services have been exited. This fixed all issues for the person editing this note.<br />
<br />
===Unclean unmount during shutdown when having home directory mounted on SD card===<br />
<br />
If you experienced unclean unmount during shutdown when having your home directory on SD card, then add the following 3 lines to "Write to wtmp file before unmounting" section of your /etc/rc.shutdown file:<br />
<pre><br />
...<br />
<br />
stat_busy "Unmounting Filesystems"<br />
/bin/umount -a -t noramfs,notmpfs,nosysfs,noproc<br />
<br />
# Add these 3 lines<br />
sync;sync;sync;<br />
eject /dev/sdb # Or whichever is your SD-card's device name. /dev/disk/by-uuid/ followed by the UUID identifier is preferable though.<br />
sleep 3<br />
# End of hack<br />
<br />
stat_done<br />
<br />
...<br />
</pre><br />
<br />
===Booting from card without initrd===<br />
<br />
Let's say you decided to install Arch Linux on a card and compiled your own kernel (or used the kernel26eee kernel) without initrd. Card reader on EeePC is connected as an USB device. Unfortunately, USB storage devices are detected with a delay, so we must tell the kernel to wait until this device becomes available. You do this with "rootwait" option passed to kernel at boot time.<br />
<br />
===Sleeping and waking system on a card===<br />
<br />
If you have Arch Linux on a card, waking up from sleeping state will most likely fail. The only solution is to enable the CONFIG_USB_PERSIST option in kernel. The kernel26eee package should have this option enabled.<br />
<br />
===Display doesn't wake up properly===<br />
<br />
If you encounter black display (but apparently working system) after suspend/resume, consider using the "uswsusp" package (available in AUR) and correcting suspend2ram script in /etc/acpi, where you use this line to make the machine go to sleep:<br />
<br />
<pre>/usr/sbin/s2ram --force --vbe_post --vbe_mode</pre><br />
<br />
==Battery Tests==<br />
<br />
The following are reported battery runtimes:<br />
<br />
{| class="wikitable" style="text-align:left"<br />
|+Battery runtimes<br />
|-<br />
! Task !! Series !! Wireless !! Screen Brightness !! FSB Speed !! Fan Speed !! Runtime !! Comments<br />
|-<br />
! DVD Playback<br />
| 701 || On || Max || 85mhz || 100% || 134min || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! DVD Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! AVI Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading AVI from SSD<br />
|-<br />
! IM and Surf<br />
| 701 || On || ~30% || ??? || low || 173min || Normal web-browsing, Flash should reduce runtime a lot !<br />
|}<br />
<br />
N.B. - Will add battery runtimes as I am able to test them, please contribute.<br />
-- Grecko.1</div>
Faelar
https://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=48133
ASUS Eee PC 701
2008-08-24T16:25:13Z
<p>Faelar: /* Speeding up udev for faster boot */ eeepc_laptop is now a part of toofishes' kernel and doesn't need to be loaded as a module.</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
'''WARNING: THIS ARTICLE IS INCOMPLETE!''' Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum]. There is also a nice Arch Linux installation guide on the [http://wiki.eeeuser.com/installingarchlinux EeeUser Wiki].<br />
<br />
==Before You Begin==<br />
<br />
===Avoiding Pitfalls===<br />
<br />
The install is pretty normal, except that you'll need to [http://forum.eeeuser.com/viewtopic.php?id=890 avoid the pitfalls] of our alternative Linux install:<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
The rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]] '''(Recommended)'''<br />
<br />
==Installing Arch Linux==<br />
<br />
* '''NOTE:''' Please refer to The [[Beginners_Guide]] for detailed instructions, if needed. Ideally, your CD/USB should boot up just fine on Eee PC without any need for additional options.<br />
<br />
===Booting Arch the installation CD/USB===<br />
<br />
The stock kernel on Arch installation media since 2008.06 and newer support Eee's ethernet network card. So there's no need to install any additional modules before or during the installation process to have a working network connection (unless you want to use wireless network card). <br />
<br />
===Start the Installation===<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 />
<br />
mount /dev/sd[x] /src<br />
<br />
Then just run<br />
<br />
/arch/setup<br />
<br />
To start the installation just like normal.<br />
<br />
===Prepare Hard Drive===<br />
<br />
The default Eee PC drive is split up into four partitions (here is [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* It is easiest to wipe the existing partitions and use one or two partitions for your install. One partition would be just '/', and two partitions would be '/boot' and '/'.<br />
* Choose "NONE" for swap (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
* Select "ext2" as your filesystem (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
<br />
===Select Packages===<br />
<br />
Choose the proper source of package, this should be done automatically if you are installing from USB.<br />
<br />
In addition to the '''BASE''' category, you also need all of the packages in the '''DEVEL''' category if you are planning on compiling stuffs on your Eee.<br />
<br />
If you intended to use wireless, then you'll also need the ''wireless_tools'' package from '''SUPPORT''' category.<br />
<br />
===Install Customized Kernel and All the Necessary Modules===<br />
<br />
After you have installed all the packages you want from your installation media of choice, the next step is to install the kernel that was customized for Eee and all the necessary modules. <br />
<br />
Since toofishes' kernel-eee is currently the most up to date one and contains all the necessary modules and patches for Eee (while the stock kernel lacks most of them), it is recommended that you use kernel-eee from toofishes' repository.<br />
<br />
====Eee repository from toofishes====<br />
toofishes created a repository for the Eee. You can find some basic packages like Pentium-M-optimized kernel and needed modules. Add<br />
[eee]<br />
Server = http://code.toofishes.net/packages/eee<br />
to your /etc/pacman.conf to use the repository.<br />
<br />
=====Package List=====<br />
<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' <br />
customized kernel for Eee<br />
*'''luvcview''' <br />
webcam program for testing webcam driver<br />
*'''madwifi-eee-svn''' <br />
wifi driver for Eee<br />
*'''eeepc-linux''' <br />
kernel module to change Eee's FSB speed and fan control<br />
<br />
=====Installation Instruction=====<br />
<br />
Simply use pacman to install the package that you need. For a working system, you'll need at least 3 packages: kernel-eee (the kernel), linux-uvc-eee-svn (webcam driver) and madwifi-eee-svn (the wifi driver).<br />
<br />
Install the packages with this command:<br />
<br />
pacman -Sy kernel-eee madwifi-eee-svn<br />
<br />
*'''ATTENTION:''' dkite's eeemodules package conflicts with the madwifi-eee-svn package. You need to remove dkite's eeemodules package before you can install toofishes madfwifi-eee-svn package.<br />
<br />
Then, add the following to /boot/grub/menu.lst; note that no initrd is needed:<br />
# (2) Arch Linux<br />
title Arch Linux EEE kernel<br />
root (hd0,0)<br />
kernel /boot/vmlinuzeee root=/dev/sda1 ro<br />
<br />
Restart and select Arch Linux EEE kernel from the grub boot menu.<br />
<br />
===Add the Final Touch===<br />
<br />
After you have install kernel-eee and all the related packages as noted above, make these edits to /etc/fstab:<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* '''OPTIONAL:''' Add a new line: "tmpfs /var/log tmpfs size=1M 0 0" ('''WARNING:''' this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]. To save your startup/shutdown logs, look at the pitfalls link above).<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. The following is the guide on how to get the rest of your system working.<br />
<br />
===Xorg===<br />
<br />
You have two choices for video on the Eee - the newer <b>xf86-video-intel</b> driver, or the older <b>xf86-video-i810</b> driver paired with 915resolution. The intel driver is the focus upstream and is being actively developed so it is your best choice. <br />
<br />
However, if you wish to use composite extension (for Compiz Fusion, for example), then the old i810 driver might be a better option, mainly because XV video output does not work when composite is enabled on the currently intel driver and thus a lot of applications, such as Skype or UCView, will not function properly.<br />
<br />
You need these packages in addition to the Xorg's packages:<br />
<br />
pacman -Sy synaptics xf86-video-intel<br />
<br />
If you choose to use the older i810 video, you will have to install xf86-video-i810 and 915resolution as well. Note that the i810 driver and the intel driver cannot both be installed at the same time.<br />
<br />
Then, just drop in the following xorg.conf into your /etc/X11/ directory:<br />
<br />
<pre>Section "ServerLayout"<br />
Identifier "ArchLinux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "extmod"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail"<br />
Option "BlankTime" "5"<br />
Option "AIGLX" "false"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "keyboard"<br />
Driver "kbd"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbLayout" "us"<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "IMPS/2"<br />
Option "Emulate3Buttons" "yes"<br />
Option "ZAxisMapping" "4 5"<br />
Option "CorePointer"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "synaptics"<br />
Driver "synaptics"<br />
Option "Device" "/dev/psaux"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1000"<br />
Option "RightEdge" "5400"<br />
Option "TopEdge" "1000"<br />
Option "BottomEdge" "4900"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "HorizScrollDelta" "0" <br />
Option "RBCornerButton" "0"<br />
Option "RTCornerButtom" "0"<br />
Option "MaxSpeed" "0.1"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "ASUS"<br />
ModelName "eeePC P701"<br />
Modeline "800x480" 29.58 800 816 896 992 480 481 484 497 -HSync +Vsync # 60 Hz<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "intel"<br />
VendorName "Intel Corporation"<br />
BoardName "Mobile 915GM/GMS/910GML Express Graphics Controller"<br />
BusID "PCI:0:2:0"<br />
Option "AccelMethod" "EXA"<br />
Option "MigrationHeuristic" "greedy"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</pre><br />
<br />
If you want to set up the i810 driver instead, you will also have to configure 915resolution and add it to your daemons line. This is not needed for the intel driver. Edit the /etc/conf.d/915resolution to look like this:<br />
<br />
<pre># Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
</pre><br />
<br />
Now put the 915resolution daemon into your /etc/rc.conf file:<br />
<br />
<pre>DAEMONS=(... 915resolution ...)</pre><br />
<br />
===Sound, Webcam & Microphone===<br />
<br />
====Sound====<br />
<br />
Some people have reported sound working right out of the box with no troubles. However, others might need to add to /etc/modprobe.conf the following line for the EeePC 701<br />
<pre>options snd-hda-intel model=3stack-dig</pre><br />
or the following one for the EeePC 900 model<br />
<pre>options snd-hda-intel model=auto</pre><br />
<br />
If your internal microphone doesn't work, you probably have to turn the capture feature on. Simply fire up alsamixer, find your Capture control, and press spacebar to enable it.<br />
<br />
====Webcam====<br />
<br />
You can enable your built-in webcam by adding the following line to your /etc/rc.local file.<br />
<br />
echo 1 > /proc/acpi/asus/camera<br />
<br />
If you want the webcam application that the default Xandos installation uses, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14469 ucview from the AUR].<br />
<br />
The webcam also works fine with the latest version of Skype.<br />
<br />
If you already have mplayer installed you can launch :<br />
mplayer -fps 15 tv://<br />
<br />
I have yet to get it working with vlc or any other software such as xawtv. If you know how, please update this.<br />
<br />
*'''NOTE:''' For anyone who has accidentally disabled Auto Exposure for their webcam in luvcview (making the image dark), and can't enable it again, do the following:<br />
<br />
Install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14468 libwebcam from the AUR].<br />
<br />
Issue the following command:<br />
<pre>uvcdynctrl --set "Exposure, Auto" 4</pre><br />
<br />
*'''NOTE:''' Be sure the "OS Installation" option is set to "finished" in the BIOS' "Advanced" tab or your camera may not work in some applications (like Skype).<br />
<br />
====Microphone====<br />
<br />
Solution for problems with the internal microphone.<br />
<br />
1. First of all set in alsamixer "Input Source" to "i-Mic"<br />
<br />
2. Increase "Capture" and "i-Mic Boost" to your needs<br />
<br />
3. Edit /etc/asound.state the following, change the 2 "false" to "true" like showing:<br />
<pre><br />
....snap.....<br />
control.11 {<br />
comment.access 'read write'<br />
comment.type BOOLEAN<br />
comment.count 2<br />
iface MIXER<br />
name 'Capture Switch'<br />
value.0 true<br />
value.1 true<br />
}<br />
....snap....</pre><br />
<br />
4. After editing run following as root<br />
<pre>alsactl restore</pre><br />
<br />
5. Now your internal microphone should be working.<br />
<br />
===Getting Hot Keys, Graphic Indicators and Shutdown with the Power Button Working===<br />
<br />
If you want to have working hot keys for changing brightness and volumes, graphic indicators working as well as shutdown when press the power button (just like in the stock Eee PC), then you should install '''ighea's acpi-eee''' or '''dkite's acpid_eee''' package.<br />
<br />
==== ighea's acpi-eee ====<br />
<br />
Get the latest package from [http://kapsi.fi/ighea/eee/acpi-eee/ here].<br />
<br />
The package can be easily installed with<br />
pacman -U acpi-eee-8-1-i686.pkg.tar.gz<br />
<br />
See messages during installation for more details and don't forget to edit /etc/acpi/eee.conf to suit your tastes.<br />
<br />
==== dkite's acpid_eee ====<br />
<br />
Package can also be download from his [http://members.shaw.ca/dkite/ website]<br />
<br />
The package itself can be install with<br />
<br />
pacman -Uf acpid_eee-0.0.3-1-i686.pkg.tar.gz.tar<br />
<br />
With '''both''' packages don't forget to start '''asusosd''' if you want to have the Graphic Indicators from Xandros.<br />
<br />
==Additional Tips & Tweaks==<br />
<br />
===kernel26eee tweaks===<br />
<br />
Toofishes's kernel, also known as kernel26eee, can be recompile to include custom features. You can download toofishes' kernel PKGBUILD and all the nesseary files from his gitweb by install git package and use the following command:<br />
<br />
git clone http://code.toofishes.net/gitprojects/eee.git<br />
<br />
There are two ways to tweak the kernal. The first is simply to edit the '''kernelconfig''' file with your favorite editor and the second is to insert a 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 compile 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 instruction, then change the following lines in 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 />
<br />
To this:<br />
<pre><br />
...<br />
230 CONFIG_NOHIGHMEM=y<br />
231 # CONFIG_HIGHMEM4G is not set<br />
232 # CONFIG_HIGHMEM64G is not set<br />
233 CONFIG_VMSPLIT_3G=y<br />
234 # CONFIG_VMSPLIT_3G_OPT is not set<br />
235 # CONFIG_VMSPLIT_2G is not set<br />
236 # CONFIG_VMSPLIT_2G_OPT is not set<br />
237 # CONFIG_VMSPLIT_1G is not set<br />
...<br />
</pre><br />
Compile and install the kernel and Wine should now works.<br />
<br />
===Power down with the power button===<br />
<br />
* '''NOTE:''' If you are using ighea's acpi-eee or dkite's acpid_eee package then you should already be able to shutdown by pressing the power button and should not need to do this.<br />
<br />
The two alternatives here are described in [[Allow_users_to_shutdown]].<br />
<br />
If you don't already or don't plan to use sudo, it may be simpler to use the setuid /sbin/halt method, otherwise using sudo is preferred.<br />
<br />
Below are all the steps required for the sudo method. If you want to use the setuid method, read the article linked above and perform the 'power' file step here, while omitting the 'sudo' in it.<br />
<br />
<pre>pacman -S sudo</pre><br />
<br />
As root, do the following:<br />
<br />
<pre>visudo</pre><br />
<br />
Add the following line to the file:<br />
<br />
<pre>USER HOST = NOPASSWD: /sbin/poweroff</pre><br />
<br />
Where USER = the user you want to be able to power down with and HOST = your hostname (from /etc/rc.conf).<br />
<br />
Now, create a file called /etc/acpi/events/power, containing:<br />
<br />
<pre># /etc/acpi/events/power<br />
# This is called when the user presses the power button<br />
<br />
event=button/power (PWR.||PBTN)<br />
action=sudo /sbin/poweroff</pre><br />
<br />
Make sure that you execute<br />
<br />
<pre>/etc/rc.d/acpid start</pre><br />
<br />
And/or add acpid to the daemons list in /etc/rc.conf:<br />
<br />
<pre>DAEMONS=(hal, acpid ...</pre><br />
<br />
===Use cpufreq for power saving===<br />
<br />
* '''NOTE:''' If you are using toofishes's kernel, then processor scaling is already enable and you don't need to do the following steps.<br />
<br />
Install cpufrequtitls.<br />
pacman -S cpufrequtils<br />
<br />
For scaling down the processor you have to load the p4_clockmod module. Insert it into your /etc/rc.conf MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
<br />
Add 'cpufreq' to the DAEMONS array in /etc/rc.conf to have it start on startup.<br />
DAEMONS=(... cpufreq ...)<br />
<br />
Add the following into /etc/conf.d/cpufreq<br />
governor="ondemand"<br />
min_freq="113MHz"<br />
max_freq="900MHz"<br />
<br />
With enabled cpufreq it scales the processor between 113MHz up to max. frequency. That should save a lot on battery power. The stated 900MHz will be never reached by the eeePC, the p4_clockmod reports a wrong frequency here. But scaling works, you can feel it in the performance of eeePC that he slow down the processor.<br />
<br />
===More responsive system with ondemand governor===<br />
The default up_threshold (where it will bump to a faster speed) for the CPU governor is 80, which means it will increase the CPU speed when utilization is above 80%. This can make X applications have a bit of lag. <br />
Try changing this value:<br />
sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
With 40 it still leaves the majority of CPU cycles at the lowest available clock speed but increases responsiveness. You can add this line to one of your startup scripts (such as /etc/rc.local) if you wish to keep it, for example:<br />
<pre><br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
<br />
echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold<br />
</pre><br />
<br />
Also, following line is also reported to help makes system more responsive. You can use it by adding it to your /etc/rc.local:<br />
<pre><br />
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate<br />
</pre><br />
<br />
===Speeding up udev for faster boot===<br />
* [[Speedup udev]]<br />
*http://dev.laptop.org/ticket/4349<br />
*[http://www.eeesale.com/Asus-Eee-PC-overclock-Benchmarks.htm Speed up the Eee PC]<br />
<br />
You can also disable the autoload by editing your ''rc.conf'' :<br />
...<br />
MOD_AUTOLOAD="no"<br />
...<br />
MODULES=(pciehp wlan ath_hal ath_pci)<br />
<br />
===Update your BIOS without Xandros===<br />
* '''Warning : you can break your system, do not update if you are not sure of what you are doing!'''<br />
<br />
First, you need to download the ''.rom'' file.<br />
*[http://update.eeepc.asus.com/bios/ Asus official's BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USBStick formated in fat32.<br />
To format an USBStick, use cfdisk tool :<br />
cfdisk /dev/sdc #could be something else than "c"<br />
Choose [delete], [type] : "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
cp /somewhere/blabla/.../thecurrentnameofthefile.rom /dev/sdc1/701.rom<br />
The name of the copy '''must''' be 701.rom<br />
<br />
Next step, reboot the eeepc with the USBStick pluged-in, and press<br />
Alt + F2<br />
It will launch the built-in tool. Everything should be Ok, you can make a coffee during the update. When it asks you to push the power-button it has finished.<br />
<br />
At the next boot, you'll be invited to configure the BIOS. Check if the everything is enable (my webcam and wireless were disable after the update) and if it displays the good version in the main screen. It's done !<br />
<br />
===More usuable font sizes===<br />
<br />
On a default installation with XFCE 4 my font sizes were too big, here is what I did to sort them out.<br />
<br />
First, I set the DPI by adding the following to ~/.Xdefaults:<br />
Xft*dpi: 134<br />
<br />
This then caused the fonts to be even bigger, so I set them all to be font-size 6 by adding the following into ~/.gtkrc-2.0 (note this will be overwritten if you use any tools to change GTK settings):<br />
style "user-font"<br />
{<br />
font_name="Bitstream Vera Sans 6"<br />
}<br />
widget_class "*" style "user-font"<br />
<br />
To do the same with KDE fonts (without KDE installed) you have to add the following to ~/.kde/share/config/kdeglobals:<br />
[General]<br />
StandardFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
activeFont=Bitstream Vera Sans,6,-1,5,75,0,0,0,0,0<br />
fixed=Bitstream Vera Sans Mono,6,-1,5,50,0,0,0,0,0<br />
font=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
menuFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
taskbarFont=Bitstream Vera Sans,6,-1,5,50,1,0,0,0,0<br />
toolBarFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
<br />
To make your fonts even prettier enable the [[Fonts#Fonts_with_LCD_filter_enabled|LCD Fonts]].<br />
<br />
===Using stock kernel===<br />
<br />
Some users might want to use the stock kernel. Since the stock kernel lacks most of the necessary modules for Eee, we need to install them manually. There are two way of doing this: compile and install everything from source or use dkite's eeemodules packages.<br />
<br />
====Install All the Necessary Modules using dkite's eeemodule package==== <br />
IMPORTANT : A recent kernel upgrade no longer allows the madwifi dkite included in his eeemodules package to compile. For that reason and for the sake of keeping up to date, prurigro has contributed eeemodules-hal. This package is identical to dkite's except it uses madwifi-hal from http://snapshots.madwifi.org/madwifi-hal-0.10.5.6/ which is actually made with the eee's wirless card in mind and compiles well with the current kernel. eeemodules-hal is available in the AUR @ http://aur.archlinux.org/packages.php?ID=19256 .<br />
<br />
If anyone has webspace to throw a package compiled for the current installer's kernel, it would be beneficial to those without a linux desktop to make it themselves. Thanks<br />
(Accurate August 21st 2008) <br />
<br />
'''dkite''' have created a package that contains all the necessary modules for wifi, ethernet connection, acpi and video camera hardware that comes with the Eee PC. His package is to be use with the stock kernel. <br />
<br />
The following is the list of hardware/functions that are known to work with dkite's eeemodules Package:<br />
<br />
*Wireless <br />
*Ethernet <br />
*Webcam <br />
*Suspend/Resume<br />
<br />
You can get the package [http://members.shaw.ca/dkite from his website]. <br />
<br />
Currently there are three pre-complied package:<br />
<br />
#'''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' for use with Don't Panic kernel.<br />
#'''eeemodules-0.0.3-2.6.24.1.2-i686.pkg.tar.gz''' for the 2.6.24.14-2 kernel.<br />
<br />
If you have newer or other version of kernel26, then you will need to download '''eeemodules.tar.gz''', which contains PKGBUILD and all the necessary files, and build the package yourself. <br />
<br />
*'''ATTENTION:''' You will also need to rebuild the package, using eeemodules.tar.gz, every time you upgrade your kernel, or else your hardware (wifi, ethernet, etc.) will stop functioning.<br />
<br />
=====Installation Instructions=====<br />
<br />
Install the package with the following command:<br />
<br />
pacman -Uf eeemodules-<pkgver>.tar.gz<br />
<br />
Then run a depmod command:<br />
<br />
depmod<br />
<br />
* '''ATTENTION:''' Do ''not'' forget to run the depmod command after installing the package, otherwise your hardware won't function! <br />
<br />
Finally, edit /etc/rc.conf and add asus_acpi to the MODULES array:<br />
<br />
MODULES = (... asus_acpi ...)<br />
<br />
====Compile and Install All the Necessary Modules from Source====<br />
<br />
* '''NOTE:''' for anyone who read this wiki previously and wondered where the patched kernel download went; the latest arch kernel contains the patch that fixes the intel graphics vsync hardlock error, so no additional configuration need be done<br />
<br />
=====Install Network Adapter Drivers=====<br />
<br />
======Atl2 ethernet driver======<br />
<br />
* '''UPDATE:''' the atl2 ethernet is support by Arch Linux's stock kernel as of 2008.03<br />
<br />
You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
<br />
Extract the sources. You may need to modify the kernel version listed in the Makefile.<br />
<br />
make clean<br />
make<br />
cp atl2.ko /lib/modules/2.6.24-ARCH/kernel/drivers/net # Change 2.6.24 as needed<br />
depmod<br />
<br />
======Atheros wireless ethernet driver======<br />
<br />
Instructions from http://wiki.eeeuser.com/ubuntu#wireless_internet_using_native_madwifi_drivers to patch madwifi. This replaces the Arch madwifi packages.<br />
<br />
wget 'http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw'<br />
wget http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
==Known problems and their solutions==<br />
<br />
===Wireless doesn't work, even after installing custom Madwifi module===<br />
<br />
I found that Arch tried to use the ath5k module for wireless, and that meant it took control of the card rather than ath_pci (the module I had compiled and installed). I got a Madwifi status 3 message in dmesg when this happened.<br />
<br />
The solution is to blacklist the ath5k module in /etc/rc.conf:<br />
<br />
MODULES = ( ... !ath5k ... )<br />
<br />
===Laggy or Unresponsive ACPI Events===<br />
<br />
The latest kernel (2.6.26) introduces new problems with Eee's ACPI events handling. Basically, ACPI events become very laggy and after some time ACPI get disabled after a heavy usage (e.g. changing volume, brightness). This problem affects both stock kernel and toofishes' kernel.<br />
<br />
It appears that the solution is to apply this [http://bugzilla.kernel.org/attachment.cgi?id=16862 patch] ([http://bugzilla.kernel.org/show_bug.cgi?id=10724 original bug report]) to the kernel. <br />
<br />
*'''Note:''' the latest toofishes' kernel, version 2.6.26-1, now include the patch, but you can still use ighea's one for the extras features listed below.<br />
<br />
Until toofishes update his kernel to include the patch, you can use ighea's slightly modified toofishes' kernel that included the above patch, as well as other modifications:<br />
<br />
*Support for Wine <br />
*uvesafb is built as module <br />
*Use [http://bbs.archlinux.org/viewtopic.php?pid=393860#p393860 new eeepc-laptop driver] (which also handles fan-control) instead of older acus_acpi or asus-laptop -drivers.<br />
<br />
You can get the modified kernel, as well as the associative packages, from [http://koti.kapsi.fi/~ighea/eee/kernel-eee/ here].<br />
<br />
After you have downloaded the packages, Install them using this command:<br />
<br />
pacman -U kernel-eee-2.6.26-1-i686.pkg.tar.gz madwifi-eee-svn-3752-1-i686.pkg.tar.gz <br />
<br />
You might also want to use IgnorePkg-line in /etc/pacman.conf to hold packages from being accidentally updated.<br />
<br />
IgnorePkg = kernel-eee madwifi-eee-svn<br />
<br />
Also don't forget to upgrade ighea's acpi-eee package to version 9.6.<br />
<br />
===Shutdown Problem===<br />
<br />
If your Eee won't shutdown properly (i.e. the power indicator LED is on but the LCD screen is off), then add the following lines to your /etc/rc.local.shutdown file.<br />
<pre><br />
#! /bin/bash<br />
#<br />
# /etc/rc.local.shutdown: Local shutdown script.<br />
#<br />
<br />
# Comment or uncomment the following two lines according to your system configuration.<br />
<br />
/etc/rc.d/mpd stop # If you're using mpd, then you have to stop its daemon first.<br />
<br />
/etc/rc.d/alsa stop # If you're using ALSA daemon, then you also have to stop it.<br />
<br />
# The following line is Eee specific fix, you always need to have this line in /etc/rc.local.shutdown.<br />
<br />
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind<br />
</pre><br />
The above solution should fix the shutdown problem in most cases. But if for some reason the problem still persists, the module may not be able to be unloaded until after all services have finished. Do the above, then in /etc/rc.shutdown move <br />
<br />
if [ -x /etc/rc.local.shutdown ]; then<br />
/etc/rc.local.shutdown<br />
fi<br />
<br />
from where it was to directly above the line <br />
<br />
# Terminate all processes<br />
<br />
this will cause the rc.local.shutdown script to run after services have been exited. This fixed all issues for the person editing this note.<br />
<br />
===Unclean unmount during shutdown when having home directory mounted on SD card===<br />
<br />
If you experienced unclean unmount during shutdown when having your home directory on SD card, then add the following 3 lines to "Write to wtmp file before unmounting" section of your /etc/rc.shutdown file:<br />
<pre><br />
...<br />
<br />
stat_busy "Unmounting Filesystems"<br />
/bin/umount -a -t noramfs,notmpfs,nosysfs,noproc<br />
<br />
# Add these 3 lines<br />
sync;sync;sync;<br />
eject /dev/sdb # Or whichever is your SD-card's device name. /dev/disk/by-uuid/ followed by the UUID identifier is preferable though.<br />
sleep 3<br />
# End of hack<br />
<br />
stat_done<br />
<br />
...<br />
</pre><br />
<br />
===Booting from card without initrd===<br />
<br />
Let's say you decided to install Arch Linux on a card and compiled your own kernel (or used the kernel26eee kernel) without initrd. Card reader on EeePC is connected as an USB device. Unfortunately, USB storage devices are detected with a delay, so we must tell the kernel to wait until this device becomes available. You do this with "rootwait" option passed to kernel at boot time.<br />
<br />
===Sleeping and waking system on a card===<br />
<br />
If you have Arch Linux on a card, waking up from sleeping state will most likely fail. The only solution is to enable the CONFIG_USB_PERSIST option in kernel. The kernel26eee package should have this option enabled.<br />
<br />
===Display doesn't wake up properly===<br />
<br />
If you encounter black display (but apparently working system) after suspend/resume, consider using the "uswsusp" package (available in AUR) and correcting suspend2ram script in /etc/acpi, where you use this line to make the machine go to sleep:<br />
<br />
<pre>/usr/sbin/s2ram --force --vbe_post --vbe_mode</pre><br />
<br />
==Battery Tests==<br />
<br />
The following are reported battery runtimes:<br />
<br />
{| class="wikitable" style="text-align:left"<br />
|+Battery runtimes<br />
|-<br />
! Task !! Series !! Wireless !! Screen Brightness !! FSB Speed !! Fan Speed !! Runtime !! Comments<br />
|-<br />
! DVD Playback<br />
| 701 || On || Max || 85mhz || 100% || 134min || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! DVD Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! AVI Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading AVI from SSD<br />
|-<br />
! IM and Surf<br />
| 701 || On || ~30% || ??? || low || 173min || Normal web-browsing, Flash should reduce runtime a lot !<br />
|}<br />
<br />
N.B. - Will add battery runtimes as I am able to test them, please contribute.<br />
-- Grecko.1</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=47405
User:Faelar
2008-08-09T21:51:04Z
<p>Faelar: Removing all content from page</p>
<hr />
<div></div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=47297
User:Faelar
2008-08-07T20:50:28Z
<p>Faelar: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
{{Navigate_i18n_mainpages}}<br />
<br />
== Guides d'Installation ==<br />
'''Si vous êtes nouveau sur Arch, le [[Manuel_du_Débutant_(Français)|Manuel du débutant]] devrait-être approprié,''' ou alors essayez '''le [[Official Arch Linux Install Guide|Guide Officiel d'Installation (en)]], pour une approche plus générale.<br />
<br />
Vous pourriez également être intéressé par : [[Post Installation Tips|Les Astuces Post-Installation (en)]] :: [[Configuring network|La Configuration du Réseau (en)]]<br />
== Pages Utiles ==<br />
<br />
Voici un extrait de quelques unes des pages les plus utiles du Wiki. <br />
<br />
==== &nbsp;&nbsp;[[Table_des_matières_(Français)|Table des Matières]] ====<br />
<br />
==== &nbsp;&nbsp;[[:Category:À_propos_d'Arch_(Français)|À propos d'Arch]] ====<br />
: [[ArchLinux_(Français)|Qu'est-ce qu'Arch Linux ?]] :: [[The_Arch_Way_(Français)|L'Esprit d'Arch]] :: [[Arch_Comparée_Aux_Autres_Distros|Arch Comparée Aux Autres Distributions]] :: [[FAQ_(Français)|FAQ]] :: [[Official Repositories|Les Dépôts Officiels (en)]] :: [[ArchLinux User-community Repository (AUR)|Le Dépôt Communautaire d'Arch (AUR) (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Administration_du_système_(Français)|Administration du Système]] ====<br />
: [[Pacman_(Français)|Pacman]] :: [[:Category: Package management (English)|Gestion des Paquets (en)]] :: [[Xorg|Configuration de Xorg (en)]] :: [[:Category: Desktop environments (English)|Environments de Bureau (en)]] :: [[ALSA|ALSA (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Guide_de_l'utilisateur_de_bureau_(Français)|Guide de l'utilisation Bureautique]] ====<br />
: [[:Category: Internet and Email (English)|Internet et Email (en)]] :: [[:Category: Office (English)|Bureautique (en)]] :: [[:Category: Audio/Video (English)|Audio/Vidéo (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Remise_en_état_du_système_(Français)|Remise en état du Sytème]] ====<br />
: [[Reinstalling GRUB|Réinstaller GRUB (en)]] :: [[Kernel Panics|Kernel Panics (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Développement_d'Arch_(Français)|Développement d'Arch]] ====<br />
: [[Community Projects|Projets de la Communauté (en)]] :: [[:Category: Live Arch systems (English)|Systèmes Arch "Live" (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Arch64 (English)|Arch64 (en)]] ====<br />
: [[Arch64 FAQ|Arch64 FAQ (en)]]<br />
<br />
== Les Nouvelles du Wiki ==<br />
<br />
Consultez la page des [[Wiki News|Nouvelles du Wiki (en)]] pour les derniers tuyaux du Wiki.<br />
<br />
Si vous avez un peu de temps pour des modifications mineures ou majeures, jettez un oeil à the [[Priority Todo]] and the [[WikiTodo]] pages pour voir comment vous pourriez aider. Nous sommes particulièrment intéressé in having people réorganiser pages non-Anglaises. S'il vous plait coordonnez vos actions avec les [[ContactList|admins et sysops]] ou les [[ArchWiki maintainers (English)|maintainers]].<br />
<br />
== Dans votre Langue ==<br />
Plus à l'aise reading articles dans votre propre langue ? Parcourez les catégories dans les langues suivantes : <br />
: [[:Category:English|English]] :: [[:Category:Česky|Česky]] :: [[:Category:Deutsch|Deutsch]] :: [[:Category:Français|Français]] :: [[:Category:Italiano|Italiano]] :: [[:Category:Lietuviškai|Lietuviškai]] :: [[:Category:Polski|Polski]] :: [[:Category:Русский|Русский]] ::[[:Category:Українська|Українська]] :: [[:Category:Српски|Српски]] :: [[:Category:ไทย|ไทย]] :: [[:Category:简体中文|简体中文]] :: [[:Category:正體中文|正體中文]]<br />
<br />
== Aide ==<br />
Si vous avez des difficultés à trouver ce que vous cherchez, essayez d'utiliser la fonction de recherche sur la gauche.<br />
<br />
Vous devez créer un compte pour éditer ce Wiki. Une fois terminé, vous pourrez jouer un peu dans le [[Sandbox|Bac-à-sable]] ou avec votre page utilisateur pour vous familiariser avec la synthaxe (markup) du ArchWiki. The available syntax is listed in the [[:Category:Help|Wiki Help Category]] and there is an [[:Category:ArchWiki Tools (English)|Archwiki Tools section]] with some HOWTOs and guidelines.</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=47296
User:Faelar
2008-08-07T20:48:25Z
<p>Faelar: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
{{Navigate_i18n_mainpages}}<br />
<br />
== Guides d'Installation ==<br />
'''Si vous êtes nouveau sur Arch, le [[Manuel_du_Débutant_(Français)|Manuel du débutant]] devrait-être approprié,''' ou alors essayez '''le [[Official Arch Linux Install Guide|Guide Officiel d'Installation (en)]], qui vise les utilisateurs GNU/Linux confirmés.<br />
<br />
Vous pourriez également être intéressé par : [[Post Installation Tips|Les Astuces Post-Installation (en)]] :: [[Configuring network|La Configuration du Réseau (en)]]<br />
== Pages Utiles ==<br />
<br />
Voici un extrait de quelques unes des pages les plus utiles du Wiki. <br />
<br />
==== &nbsp;&nbsp;[[Table_des_matières_(Français)|Table des Matières]] ====<br />
<br />
==== &nbsp;&nbsp;[[:Category:À_propos_d'Arch_(Français)|À propos d'Arch]] ====<br />
: [[ArchLinux_(Français)|Qu'est-ce qu'Arch Linux ?]] :: [[The_Arch_Way_(Français)|L'Esprit d'Arch]] :: [[Arch_Comparée_Aux_Autres_Distros|Arch Comparée Aux Autres Distributions]] :: [[FAQ_(Français)|FAQ]] :: [[Official Repositories|Les Dépôts Officiels (en)]] :: [[ArchLinux User-community Repository (AUR)|Le Dépôt Communautaire d'Arch (AUR) (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Administration_du_système_(Français)|Administration du Système]] ====<br />
: [[Pacman_(Français)|Pacman]] :: [[:Category: Package management (English)|Gestion des Paquets (en)]] :: [[Xorg|Configuration de Xorg (en)]] :: [[:Category: Desktop environments (English)|Environments de Bureau (en)]] :: [[ALSA|ALSA (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Guide_de_l'utilisateur_de_bureau_(Français)|Guide de l'utilisation Bureautique]] ====<br />
: [[:Category: Internet and Email (English)|Internet et Email (en)]] :: [[:Category: Office (English)|Bureautique (en)]] :: [[:Category: Audio/Video (English)|Audio/Vidéo (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Remise_en_état_du_système_(Français)|Remise en état du Sytème]] ====<br />
: [[Reinstalling GRUB|Réinstaller GRUB (en)]] :: [[Kernel Panics|Kernel Panics (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Développement_d'Arch_(Français)|Développement d'Arch]] ====<br />
: [[Community Projects|Projets de la Communauté (en)]] :: [[:Category: Live Arch systems (English)|Systèmes Arch "Live" (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Arch64 (English)|Arch64 (en)]] ====<br />
: [[Arch64 FAQ|Arch64 FAQ (en)]]<br />
<br />
== Les Nouvelles du Wiki ==<br />
<br />
Consultez la page des [[Wiki News|Nouvelles du Wiki (en)]] pour les derniers tuyaux du Wiki.<br />
<br />
Si vous avez un peu de temps pour des modifications mineures ou majeures, jettez un oeil à the [[Priority Todo]] and the [[WikiTodo]] pages pour voir comment vous pourriez aider. Nous sommes particulièrment intéressé in having people réorganiser pages non-Anglaises. S'il vous plait coordonnez vos actions avec les [[ContactList|admins et sysops]] ou les [[ArchWiki maintainers (English)|maintainers]].<br />
<br />
== Dans votre Langue ==<br />
Plus à l'aise reading articles dans votre propre langue ? Parcourez les catégories dans les langues suivantes : <br />
: [[:Category:English|English]] :: [[:Category:Česky|Česky]] :: [[:Category:Deutsch|Deutsch]] :: [[:Category:Français|Français]] :: [[:Category:Italiano|Italiano]] :: [[:Category:Lietuviškai|Lietuviškai]] :: [[:Category:Polski|Polski]] :: [[:Category:Русский|Русский]] ::[[:Category:Українська|Українська]] :: [[:Category:Српски|Српски]] :: [[:Category:ไทย|ไทย]] :: [[:Category:简体中文|简体中文]] :: [[:Category:正體中文|正體中文]]<br />
<br />
== Aide ==<br />
Si vous avez des difficultés à trouver ce que vous cherchez, essayez d'utiliser la fonction de recherche sur la gauche.<br />
<br />
Vous devez créer un compte pour éditer ce Wiki. Une fois terminé, vous pourrez jouer un peu dans le [[Sandbox|Bac-à-sable]] ou avec votre page utilisateur pour vous familiariser avec la synthaxe (markup) du ArchWiki. The available syntax is listed in the [[:Category:Help|Wiki Help Category]] and there is an [[:Category:ArchWiki Tools (English)|Archwiki Tools section]] with some HOWTOs and guidelines.</div>
Faelar
https://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=47288
ASUS Eee PC 701
2008-08-07T20:04:36Z
<p>Faelar: /* Eee 901 20G lsmod and lspci */ Was moved to the new page because it's from 901 model.</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
'''WARNING: THIS ARTICLE IS INCOMPLETE!''' Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum]. There is also a nice Arch Linux installation guide on the [http://wiki.eeeuser.com/installingarchlinux EeeUser Wiki].<br />
<br />
==Before You Begin==<br />
<br />
===Avoiding Pitfalls===<br />
<br />
The install is pretty normal, except that you'll need to [http://forum.eeeuser.com/viewtopic.php?id=890 avoid the pitfalls] of our alternative Linux install:<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
The rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]] '''(Recommended)'''<br />
<br />
==Installing Arch Linux==<br />
<br />
* '''NOTE:''' Please refer to The [[Beginners_Guide]] for detailed instructions, if needed. Ideally, your CD/USB should boot up just fine on Eee PC without any need for additional options.<br />
<br />
===Booting Arch the installation CD/USB===<br />
<br />
The stock kernel on Arch installation media since 2008.06 and newer support Eee's ethernet network card. So there's no need to install any additional modules before or during the installation process to have a working network connection (unless you want to use wireless network card). <br />
<br />
===Start the Installation===<br />
<br />
If you are installing from the USB, then issue<br />
<br />
mount /dev/sd[x] /src<br />
<br />
To mount the usb.<br />
<br />
Then just run<br />
<br />
/arch/setup<br />
<br />
To start the installation just like normal.<br />
<br />
===Prepare Hard Drive===<br />
<br />
The default Eee PC drive is split up into four partitions (here is [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* It is easiest to wipe the existing partitions and use one or two partitions for your install. One partition would be just '/', and two partitions would be '/boot' and '/'.<br />
* Choose "NONE" for swap (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
* Select "ext2" as your filesystem (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
<br />
===Select Packages===<br />
<br />
If you are installing from USB, then choose SRC as your source.<br />
<br />
In addition to the '''BASE''' category, you also need all of the packages in the '''DEVEL''' category if you are planning on compiling stuffs on your Eee.<br />
<br />
If you intended to use wireless, then you'll also need the ''wireless_tools'' package from '''SUPPORT''' category.<br />
<br />
===Install Customized Kernel and All the Necessary Modules===<br />
<br />
After you have install all the packages you want from your installation media of choice, the next step is to install the kernel that was customized for Eee and all the necessary modules. <br />
<br />
Since toofishes' kernel-eee is currently the most up to date one and contains all the necessary modules and patches for Eee (while the stock kernel lacks most of them), it is recommended that you use kernel-eee from toofishes' repository.<br />
<br />
====Eee repository from toofishes====<br />
toofishes created a repository for the Eee. You can find some basic packages like Pentium-M-optimized kernel and needed modules. Add<br />
[eee]<br />
Server = http://code.toofishes.net/packages/eee<br />
to your /etc/pacman.conf to use the repository.<br />
<br />
=====Package List=====<br />
<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' <br />
customized kernel for Eee<br />
*'''luvcview''' <br />
webcam program for testing webcam driver<br />
*'''madwifi-eee-svn''' <br />
wifi driver for Eee<br />
*'''eeepc-linux''' <br />
kernel module to change Eee's FSB speed and fan control<br />
<br />
=====Installation Instruction=====<br />
<br />
Simply use pacman to install the package that you need. For a working system, you'll need at least 3 packages: kernel-eee (the kernel), linux-uvc-eee-svn (webcam driver) and madwifi-eee-svn (the wifi driver).<br />
<br />
Install the packages with this command:<br />
<br />
pacman -Sy kernel-eee madwifi-eee-svn<br />
<br />
*'''ATTENTION:''' dkite's eeemodules package conflicts with the madwifi-eee-svn package. You need to remove dkite's eeemodules package before you can install toofishes madfwifi-eee-svn package.<br />
<br />
Then, add the following to /boot/grub/menu.lst; note that no initrd is needed:<br />
# (2) Arch Linux<br />
title Arch Linux EEE kernel<br />
root (hd0,0)<br />
kernel /boot/vmlinuzeee root=/dev/sda1 ro<br />
<br />
Restart and select Arch Linux EEE kernel from the grub boot menu.<br />
<br />
===Add the Final Touch===<br />
<br />
After you have install kernel-eee and all the related packages as noted above, make these edits to /etc/fstab:<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* '''OPTIONAL:''' Add a new line: "tmpfs /var/log tmpfs size=1M 0 0" ('''WARNING:''' this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]. To save your startup/shutdown logs, look at the pitfalls link above).<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. The following is the guide on how to get the rest of your system working.<br />
<br />
===Xorg===<br />
<br />
You have two choices for video on the Eee - the newer <b>xf86-video-intel</b> driver, or the older <b>xf86-video-i810</b> driver paired with 915resolution. The intel driver is the focus upstream and is being actively developed so it is your best choice. <br />
<br />
However, if you wish to use composite extension (for Compiz Fusion, for example), then the old i810 driver might be a better option, mainly because XV video output does not work when composite is enabled on the currently intel driver and thus a lot of applications, such as Skype or UCView, will not function properly.<br />
<br />
You need these packages in addition to the Xorg's packages:<br />
<br />
pacman -Sy synaptics xf86-video-intel<br />
<br />
If you choose to use the older i810 video, you will have to install xf86-video-i810 and 915resolution as well. Note that the i810 driver and the intel driver cannot both be installed at the same time.<br />
<br />
Then, just drop in the following xorg.conf into your /etc/X11/ directory:<br />
<br />
<pre>Section "ServerLayout"<br />
Identifier "ArchLinux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "extmod"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail"<br />
Option "BlankTime" "5"<br />
Option "AIGLX" "false"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "keyboard"<br />
Driver "kbd"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbLayout" "us"<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "IMPS/2"<br />
Option "Emulate3Buttons" "yes"<br />
Option "ZAxisMapping" "4 5"<br />
Option "CorePointer"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "synaptics"<br />
Driver "synaptics"<br />
Option "Device" "/dev/psaux"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1000"<br />
Option "RightEdge" "5400"<br />
Option "TopEdge" "1000"<br />
Option "BottomEdge" "4900"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "HorizScrollDelta" "0" <br />
Option "RBCornerButton" "0"<br />
Option "RTCornerButtom" "0"<br />
Option "MaxSpeed" "0.1"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "ASUS"<br />
ModelName "eeePC P701"<br />
Modeline "800x480" 29.58 800 816 896 992 480 481 484 497 -HSync +Vsync # 60 Hz<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "intel"<br />
VendorName "Intel Corporation"<br />
BoardName "Mobile 915GM/GMS/910GML Express Graphics Controller"<br />
BusID "PCI:0:2:0"<br />
Option "AccelMethod" "EXA"<br />
Option "MigrationHeuristic" "greedy"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</pre><br />
<br />
If you want to set up the i810 driver instead, you will also have to configure 915resolution and add it to your daemons line. This is not needed for the intel driver. Edit the /etc/conf.d/915resolution to look like this:<br />
<br />
<pre># Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
</pre><br />
<br />
Now put the 915resolution daemon into your /etc/rc.conf file:<br />
<br />
<pre>DAEMONS=(... 915resolution ...)</pre><br />
<br />
===Sound, Webcam & Microphone===<br />
<br />
====Sound====<br />
<br />
Some people have reported sound working right out of the box with no troubles. However, others might need to add the following line to /etc/modprobe.conf.<br />
<br />
<pre>options snd-hda-intel model=3stack-dig</pre><br />
<br />
If your internal microphone doesn't work, you probably have to turn the capture feature on. Simply fire up alsamixer, find your Capture control, and press spacebar to enable it.<br />
<br />
====Webcam====<br />
<br />
You can enable your built-in webcam by adding the following line to your /etc/rc.local file.<br />
<br />
echo 1 > /proc/acpi/asus/camera<br />
<br />
If you want the webcam application that the default Xandos installation uses, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14469 ucview from the AUR].<br />
<br />
The webcam also works fine with the latest version of Skype.<br />
<br />
If you already have mplayer installed you can launch :<br />
mplayer -fps 15 tv://<br />
<br />
I have yet to get it working with vlc or any other software such as xawtv. If you know how, please update this.<br />
<br />
*'''NOTE:''' For anyone who has accidentally disabled Auto Exposure for their webcam in luvcview (making the image dark), and can't enable it again, do the following:<br />
<br />
Install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14468 libwebcam from the AUR].<br />
<br />
Issue the following command:<br />
<pre>uvcdynctrl --set "Exposure, Auto" 4</pre><br />
<br />
*'''NOTE:''' Be sure the "OS Installation" option is set to "finished" in the BIOS' "Advanced" tab or your camera may not work in some applications (like Skype).<br />
<br />
====Microphone====<br />
<br />
Solution for problems with the internal microphone.<br />
<br />
1. First of all set in alsamixer "Input Source" to "i-Mic"<br />
<br />
2. Increase "Capture" and "i-Mic Boost" to your needs<br />
<br />
3. Edit /etc/asound.state the following, change the 2 "false" to "true" like showing:<br />
<pre><br />
....snap.....<br />
control.11 {<br />
comment.access 'read write'<br />
comment.type BOOLEAN<br />
comment.count 2<br />
iface MIXER<br />
name 'Capture Switch'<br />
value.0 true<br />
value.1 true<br />
}<br />
....snap....</pre><br />
<br />
4. After editing run following as root<br />
<pre>alsactl restore</pre><br />
<br />
5. Now your internal microphone should be working.<br />
<br />
===Getting Hot Keys, Graphic Indicators and Shutdown with the Power Button Working===<br />
<br />
If you want to have working hot keys for changing brightness and volumes, graphic indicators working as well as shutdown when press the power button (just like in the stock Eee PC), then you should install '''ighea's acpi-eee''' or '''dkite's acpid_eee''' package.<br />
<br />
==== ighea's acpi-eee ====<br />
<br />
Get the latest package from [http://kapsi.fi/ighea/eee/acpi-eee/ here].<br />
<br />
The package can be easily installed with<br />
pacman -U acpi-eee-8-1-i686.pkg.tar.gz<br />
<br />
See messages during installation for more details and don't forget to edit /etc/acpi/eee.conf to suit your tastes.<br />
<br />
==== dkite's acpid_eee ====<br />
<br />
Package can also be download from his [http://members.shaw.ca/dkite/ website]<br />
<br />
The package itself can be install with<br />
<br />
pacman -Uf acpid_eee-0.0.3-1-i686.pkg.tar.gz.tar<br />
<br />
With '''both''' packages don't forget to start '''asusosd''' if you want to have the Graphic Indicators from Xandros.<br />
<br />
==Additional Tips & Tweaks==<br />
<br />
===kernel26eee tweaks===<br />
<br />
Toofishes's kernel, also known as kernel26eee, can be recompile to include custom features. You can download toofishes' kernel PKGBUILD and all the nesseary files from his gitweb by install git package and use the following command:<br />
<br />
git clone http://code.toofishes.net/gitprojects/eee.git<br />
<br />
There are two ways to tweak the kernal. The first is simply to edit the '''kernelconfig''' file with your favorite editor and the second is to insert a 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 compile 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 instruction, then change the following lines in 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 />
<br />
To this:<br />
<pre><br />
...<br />
230 CONFIG_NOHIGHMEM=y<br />
231 # CONFIG_HIGHMEM4G is not set<br />
232 # CONFIG_HIGHMEM64G is not set<br />
233 CONFIG_VMSPLIT_3G=y<br />
234 # CONFIG_VMSPLIT_3G_OPT is not set<br />
235 # CONFIG_VMSPLIT_2G is not set<br />
236 # CONFIG_VMSPLIT_2G_OPT is not set<br />
237 # CONFIG_VMSPLIT_1G is not set<br />
...<br />
</pre><br />
Compile and install the kernel and Wine should now works.<br />
<br />
===Power down with the power button===<br />
<br />
* '''NOTE:''' If you are using ighea's acpi-eee or dkite's acpid_eee package then you should already be able to shutdown by pressing the power button and should not need to do this.<br />
<br />
The two alternatives here are described in [[Allow_users_to_shutdown]].<br />
<br />
If you don't already or don't plan to use sudo, it may be simpler to use the setuid /sbin/halt method, otherwise using sudo is preferred.<br />
<br />
Below are all the steps required for the sudo method. If you want to use the setuid method, read the article linked above and perform the 'power' file step here, while omitting the 'sudo' in it.<br />
<br />
<pre>pacman -S sudo</pre><br />
<br />
As root, do the following:<br />
<br />
<pre>visudo</pre><br />
<br />
Add the following line to the file:<br />
<br />
<pre>USER HOST = NOPASSWD: /sbin/poweroff</pre><br />
<br />
Where USER = the user you want to be able to power down with and HOST = your hostname (from /etc/rc.conf).<br />
<br />
Now, create a file called /etc/acpi/events/power, containing:<br />
<br />
<pre># /etc/acpi/events/power<br />
# This is called when the user presses the power button<br />
<br />
event=button/power (PWR.||PBTN)<br />
action=sudo /sbin/poweroff</pre><br />
<br />
Make sure that you execute<br />
<br />
<pre>/etc/rc.d/acpid start</pre><br />
<br />
And/or add acpid to the daemons list in /etc/rc.conf:<br />
<br />
<pre>DAEMONS=(hal, acpid ...</pre><br />
<br />
===Use cpufreq for power saving===<br />
<br />
* '''NOTE:''' If you are using toofishes's kernel, then processor scaling is already enable and you don't need to do the following steps.<br />
<br />
Install cpufrequtitls.<br />
pacman -S cpufrequtils<br />
<br />
For scaling down the processor you have to load the p4_clockmod module. Insert it into your /etc/rc.conf MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
<br />
Add 'cpufreq' to the DAEMONS array in /etc/rc.conf to have it start on startup.<br />
DAEMONS=(... cpufreq ...)<br />
<br />
Add the following into /etc/conf.d/cpufreq<br />
governor="ondemand"<br />
min_freq="113MHz"<br />
max_freq="900MHz"<br />
<br />
With enabled cpufreq it scales the processor between 113MHz up to max. frequency. That should save a lot on battery power. The stated 900MHz will be never reached by the eeePC, the p4_clockmod reports a wrong frequency here. But scaling works, you can feel it in the performance of eeePC that he slow down the processor.<br />
<br />
===More responsive system with ondemand governor===<br />
The default up_threshold (where it will bump to a faster speed) for the CPU governor is 80, which means it will increase the CPU speed when utilization is above 80%. This can make X applications have a bit of lag. <br />
Try changing this value:<br />
sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
With 40 it still leaves the majority of CPU cycles at the lowest available clock speed but increases responsiveness. You can add this line to one of your startup scripts (such as /etc/rc.local) if you wish to keep it, for example:<br />
<pre><br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
<br />
echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold<br />
</pre><br />
<br />
Also, following line is also reported to help makes system more responsive. You can use it by adding it to your /etc/rc.local:<br />
<pre><br />
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate<br />
</pre><br />
<br />
===Speeding up udev for faster boot===<br />
* [[Speedup udev]]<br />
*http://dev.laptop.org/ticket/4349<br />
*[http://www.eeesale.com/Asus-Eee-PC-overclock-Benchmarks.htm Speed up the Eee PC]<br />
<br />
You can also disable the autoload by editing your ''rc.conf'' :<br />
...<br />
MOD_AUTOLOAD="no"<br />
...<br />
MODULES=(pciehp wlan ath_hal ath_pci eeepc_laptop)<br />
<br />
===Update your BIOS without Xandros===<br />
* '''Warning : you can break your system, do not update if you are not sure of what you are doing!'''<br />
<br />
First, you need to download the ''.rom'' file.<br />
*[http://update.eeepc.asus.com/bios/ Asus official's BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USBStick formated in fat32.<br />
To format an USBStick, use cfdisk tool :<br />
cfdisk /dev/sdc #could be something else than "c"<br />
Choose [delete], [type] : "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
cp /somewhere/blabla/.../thecurrentnameofthefile.rom /dev/sdc1/701.rom<br />
The name of the copy '''must''' be 701.rom<br />
<br />
Next step, reboot the eeepc with the USBStick pluged-in, and press<br />
Alt + F2<br />
It will launch the built-in tool. Everything should be Ok, you can make a coffee during the update. When it asks you to push the power-button it has finished.<br />
<br />
At the next boot, you'll be invited to configure the BIOS. Check if the everything is enable (my webcam and wireless were disable after the update) and if it displays the good version in the main screen. It's done !<br />
<br />
===More usuable font sizes===<br />
<br />
On a default installation with XFCE 4 my font sizes were too big, here is what I did to sort them out.<br />
<br />
First, I set the DPI by adding the following to ~/.Xdefaults:<br />
Xft*dpi: 134<br />
<br />
This then caused the fonts to be even bigger, so I set them all to be font-size 6 by adding the following into ~/.gtkrc-2.0 (note this will be overwritten if you use any tools to change GTK settings):<br />
style "user-font"<br />
{<br />
font_name="Bitstream Vera Sans 6"<br />
}<br />
widget_class "*" style "user-font"<br />
<br />
To do the same with KDE fonts (without KDE installed) you have to add the following to ~/.kde/share/config/kdeglobals:<br />
[General]<br />
StandardFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
activeFont=Bitstream Vera Sans,6,-1,5,75,0,0,0,0,0<br />
fixed=Bitstream Vera Sans Mono,6,-1,5,50,0,0,0,0,0<br />
font=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
menuFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
taskbarFont=Bitstream Vera Sans,6,-1,5,50,1,0,0,0,0<br />
toolBarFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
<br />
To make your fonts even prettier enable the [[Fonts#Fonts_with_LCD_filter_enabled|LCD Fonts]].<br />
<br />
===Using stock kernel===<br />
<br />
Some users might want to use the stock kernel. Since the stock kernel lacks most of the necessary modules for Eee, we need to install them manually. There are two way of doing this: compile and install everything from source or use dkite's eeemodules packages.<br />
<br />
====Install All the Necessary Modules using dkite's eeemodule package==== <br />
<br />
'''dkite''' have created a package that contains all the necessary modules for wifi, ethernet connection, acpi and video camera hardware that comes with the Eee PC. His package is to be use with the stock kernel. <br />
<br />
The following is the list of hardware/functions that are known to work with dkite's eeemodules Package:<br />
<br />
*Wireless <br />
*Ethernet <br />
*Webcam <br />
*Suspend/Resume<br />
<br />
You can get the package [http://members.shaw.ca/dkite from his website]. <br />
<br />
Currently there are three pre-complied package:<br />
<br />
#'''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' for use with Don't Panic kernel.<br />
#'''eeemodules-0.0.3-2.6.24.1.2-i686.pkg.tar.gz''' for the 2.6.24.14-2 kernel.<br />
<br />
If you have newer or other version of kernel26, then you will need to download '''eeemodules.tar.gz''', which contains PKGBUILD and all the necessary files, and build the package yourself. <br />
<br />
*'''ATTENTION:''' You will also need to rebuild the package, using eeemodules.tar.gz, every time you upgrade your kernel, or else your hardware (wifi, ethernet, etc.) will stop functioning.<br />
<br />
=====Installation Instructions=====<br />
<br />
Install the package with the following command:<br />
<br />
pacman -Uf eeemodules-<pkgver>.tar.gz<br />
<br />
Then run a depmod command:<br />
<br />
depmod<br />
<br />
* '''ATTENTION:''' Do ''not'' forget to run the depmod command after installing the package, otherwise your hardware won't function! <br />
<br />
Finally, edit /etc/rc.conf and add asus_acpi to the MODULES array:<br />
<br />
MODULES = (... asus_acpi ...) <br />
<br />
====Compile and Install All the Necessary Modules from Source====<br />
<br />
* '''NOTE:''' for anyone who read this wiki previously and wondered where the patched kernel download went; the latest arch kernel contains the patch that fixes the intel graphics vsync hardlock error, so no additional configuration need be done<br />
<br />
=====Install Network Adapter Drivers=====<br />
<br />
======Atl2 ethernet driver======<br />
<br />
* '''UPDATE:''' the atl2 ethernet is support by Arch Linux's stock kernel as of 2008.03<br />
<br />
You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
<br />
Extract the sources. You may need to modify the kernel version listed in the Makefile.<br />
<br />
make clean<br />
make<br />
cp atl2.ko /lib/modules/2.6.24-ARCH/kernel/drivers/net # Change 2.6.24 as needed<br />
depmod<br />
<br />
======Atheros wireless ethernet driver======<br />
<br />
Instructions from http://wiki.eeeuser.com/ubuntu#wireless_internet_using_native_madwifi_drivers to patch madwifi. This replaces the Arch madwifi packages.<br />
<br />
wget 'http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw'<br />
wget http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
==Known problems and their solutions==<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 toofiches' kernel, 2.6.26-1 now include the patch, but you can still use ighea's one for the extras features listed below.<br />
<br />
Until toofishes update his kernel to include the patch, you can use ighea's slightly modified toofishes' kernel that included the above patch, as well as other modifications:<br />
<br />
*Support for Wine <br />
*uvesafb is built as module <br />
*Use [http://bbs.archlinux.org/viewtopic.php?pid=393860#p393860 new eeepc-laptop driver] (which also handles fan-control) instead of older acus_acpi or asus-laptop -drivers.<br />
<br />
You can get the modified kernel, as well as the associative packages, from [http://koti.kapsi.fi/~ighea/eee/kernel-eee/ here].<br />
<br />
After you have downloaded the packages, Install them using this command:<br />
<br />
pacman -U kernel-eee-2.6.26-1-i686.pkg.tar.gz madwifi-eee-svn-3752-1-i686.pkg.tar.gz <br />
<br />
You might also want to use IgnorePkg-line in /etc/pacman.conf to hold packages from being accidentally updated.<br />
<br />
IgnorePkg = kernel-eee madwifi-eee-svn<br />
<br />
Also don't forget to upgrade ighea's acpi-eee package to version 9.6.<br />
<br />
===Shutdown Problem===<br />
<br />
If your Eee won't shutdown properly (i.e. the power indicator LED is on but the LCD screen is off), then add the following lines to your /etc/rc.local.shutdown file.<br />
<pre><br />
#! /bin/bash<br />
#<br />
# /etc/rc.local.shutdown: Local shutdown script.<br />
#<br />
<br />
# Comment or uncomment the following two lines according to your system configuration.<br />
<br />
/etc/rc.d/mpd stop # If you're using mpd, then you have to stop its daemon first.<br />
<br />
/etc/rc.d/alsa stop # If you're using ALSA daemon, then you also have to stop it.<br />
<br />
# The following line is Eee specific fix, you always need to have this line in /etc/rc.local.shutdown.<br />
<br />
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind<br />
</pre><br />
The above solution should fix the shutdown problem in most cases. But if for some reason the problem still persists, the module may not be able to be unloaded until after all services have finished. Do the above, then in /etc/rc.shutdown move <br />
<br />
if [ -x /etc/rc.local.shutdown ]; then<br />
/etc/rc.local.shutdown<br />
fi<br />
<br />
from where it was to directly above the line <br />
<br />
# Terminate all processes<br />
<br />
this will cause the rc.local.shutdown script to run after services have been exited. This fixed all issues for the person editing this note.<br />
<br />
===Unclean unmount during shutdown when having home directory mounted on SD card===<br />
<br />
If you experienced unclean unmount during shutdown when having your home directory on SD card, then add the following 3 lines to "Write to wtmp file before unmounting" section of your /etc/rc.shutdown file:<br />
<pre><br />
...<br />
<br />
stat_busy "Unmounting Filesystems"<br />
/bin/umount -a -t noramfs,notmpfs,nosysfs,noproc<br />
<br />
# Add these 3 lines<br />
sync;sync;sync;<br />
eject /dev/sdb # Or whichever is your SD-card's device name. /dev/disk/by-uuid/ followed by the UUID identifier is preferable though.<br />
sleep 3<br />
# End of hack<br />
<br />
stat_done<br />
<br />
...<br />
</pre><br />
<br />
===Booting from card without initrd===<br />
<br />
Let's say you decided to install Arch Linux on a card and compiled your own kernel (or used the kernel26eee kernel) without initrd. Card reader on EeePC is connected as an USB device. Unfortunately, USB storage devices are detected with a delay, so we must tell the kernel to wait until this device becomes available. You do this with "rootwait" option passed to kernel at boot time.<br />
<br />
===Sleeping and waking system on a card===<br />
<br />
If you have Arch Linux on a card, waking up from sleeping state will most likely fail. The only solution is to enable the CONFIG_USB_PERSIST option in kernel. The kernel26eee package should have this option enabled.<br />
<br />
===Display doesn't wake up properly===<br />
<br />
If you encounter black display (but apparently working system) after suspend/resume, consider using the "uswsusp" package (available in AUR) and correcting suspend2ram script in /etc/acpi, where you use this line to make the machine go to sleep:<br />
<br />
<pre>/usr/sbin/s2ram --force --vbe_post --vbe_mode</pre><br />
<br />
==Battery Tests==<br />
<br />
The following are reported battery runtimes:<br />
<br />
{| class="wikitable" style="text-align:left"<br />
|+Battery runtimes<br />
|-<br />
! Task !! Series !! Wireless !! Screen Brightness !! FSB Speed !! Fan Speed !! Runtime !! Comments<br />
|-<br />
! DVD Playback<br />
| 701 || On || Max || 85mhz || 100% || 134min || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! DVD Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! AVI Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading AVI from SSD<br />
|-<br />
! IM and Surf<br />
| 701 || On || ~30% || ??? || low || 173min || Normal web-browsing, Flash should reduce runtime a lot !<br />
|}<br />
<br />
N.B. - Will add battery runtimes as I am able to test them, please contribute.<br />
-- Grecko.1</div>
Faelar
https://wiki.archlinux.org/index.php?title=ASUS_Eee_PC&diff=47287
ASUS Eee PC
2008-08-07T20:03:17Z
<p>Faelar: Added Eee 901 20G lsmod and lspci from the 70x/900 page</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{stub}} <br />
= Introduction =<br />
This should be the page to gather all information on installing and running arch on the Asus Eee. <br />
Why? Because the 'old' page is a bit confusing/outdated, wrongly named (makes finding it in a search hard) and the title limits it to just the install precedure.<br />
The 'old' page should be cleaned up and merged into this page, and any future information should also go on this page. If no one that actualy owns an Eee want to do it, then I (Mr.Elendig) can do it, but it will take some time.<br />
<br />
Until this page actualy get some contents, go to [[Installing Arch Linux on the Asus EEE PC]].<br />
<br />
= Eee 700 Series and 900=<br />
This should be filled with the majority of the content from [[Installing Arch Linux on the Asus EEE PC]].<br />
<br />
= Eee 901, 904, and 1000(H) =<br />
The 901, 904, and 1000(H) all seem to share much-of, if not all the same hardware. The steps for setting up Arch Linux are as follows.<br />
<br />
== Setting up the Network ==<br />
Two PKGBUILD files are available in the AUR to help you get your network interfaces up and running. The first is delcake's "atl1e" drivers for you wired ethernet, and the second is jbooth's "eeert2860" drivers for wireless.<br />
<br />
=== atl1e ===<br />
delcake's PKGBUILD is located [http://aur.archlinux.org/packages.php?ID=18663 here] in the AUR.<br />
Note that in order to build this package, you will need to get the unrar and unzip packages from the mirror of you choice, as well as the LinuxDrivers.zip source code linked on the AUR page unless you did your wireless drivers first.<br />
<br />
#Transfer the PKGBUILD to your Eee PC. Get the source files too if you don't have internet yet.<br />
#Install the unrar and unzip packages if you don't already have them.<br />
#Issue a 'makepkg' command at the location of the PKGBUILD.<br />
<br />
If all goes well, a .pkg.tar.gz file that starts with the name atl1e will have been created in the same folder.<br />
<br />
As root, run 'pacman -U <package name>.pkg.tar.gz' to install your newly created module.<br />
In order to detect it, run both 'depmod -a' and 'modprobe atl1e' as root in that order.<br />
<br />
At this point, you should be able to issue an 'ifconfig -a' command and see your brand new eth0 device staring back at you. Don't forget to add atl1e to your modules list in /etc/rc.conf to automatically load your ethernet module during boot.<br />
<br />
* '''WARNING:''' You will need to recompile this module any time you do a kernel upgrade, so hang on to that PKGBUILD and zip file.<br />
<br />
=== eeert2860 ===<br />
jbooth's PKGBUILD is located [http://aur.archlinux.org/packages.php?ID=18705 here] in the AUR.<br />
Note that in order to build this package, you will need to get the wireless_tools package from the mirror of your choice, as well as Ralink's drivers listed under the sources section unless you did your wired drivers first.<br />
<br />
#Transfer the PKGBUILD to your Eee PC. Get the source files too if you don't have internet yet.<br />
#Install the wireless_tools package if you don't already have it.<br />
#Issue a 'makepkg' command at the location of the PKGBUILD.<br />
*If your kernel is 2.6.25 or earlier, you will have to edit the PKGBUILD and comment out the first "sed" line in the build() function before running makepkg. This step should be eliminated before too long.<br />
<br />
Hopefully, the makepkg command went through without a hitch, and a .pkg.tar.gz file will have been created in the same folder.<br />
<br />
As root, run 'pacman -U <package name>.pkg.tar.gz' to install your newly created module.<br />
In order to detect it, run both 'depmod -a' and 'modprobe rt2860sta' as root in that order.<br />
<br />
Now you should see your ra0 wireless device in the output of 'ifconfig -a'. As root, run 'ifconfig ra0 up' to bring up the interface for configuration.<br />
<br />
*'''Still no ra0 device?''' Make sure that the WLAN device is enabled in your BIOS.<br />
<br />
* '''WARNING:''' You will need to recompile this module any time you do a kernel upgrade, so hang on to the PKGBUILD and .tar.bz2 file.<br />
<br />
==Eee 901 20G lsmod and lspci==<br />
'''<br />
Note :''' This section was moved from the 70x/900 page.<br />
<br />
The following are from a stock ASUS EeePC 901 20G Linux version:<br />
<br />
lsmod:<br />
<pre><br />
Module Size Used by<br />
acpi_cpufreq 5004 0 <br />
freq_table 1988 1 acpi_cpufreq<br />
usb_storage 22980 0 <br />
libusual 6352 1 usb_storage<br />
pciehp 31172 0 <br />
pci_hotplug 9672 1 pciehp<br />
ehci_hcd 25420 0 <br />
uhci_hcd 18636 0 <br />
usbhid 13444 0 <br />
usbcore 91992 6 usb_storage,libusual,ehci_hcd,uhci_hcd,usbhid<br />
snd_pcm_oss 33568 0 <br />
snd_mixer_oss 13056 1 snd_pcm_oss<br />
rt2860sta 468248 1 <br />
atl1e 26388 0 <br />
fuse 34516 0 <br />
asus_acpi 6560 0 <br />
button 5648 0 <br />
processor 19820 1 acpi_cpufreq<br />
battery 7940 0 <br />
ac 3524 0 <br />
autofs4 15876 0 <br />
sr_mod 13284 0 <br />
cdrom 30624 1 sr_mod<br />
snd_hda_intel 284112 0 <br />
snd_pcm 50696 2 snd_pcm_oss,snd_hda_intel<br />
snd_timer 15556 1 snd_pcm<br />
snd_page_alloc 6728 2 snd_hda_intel,snd_pcm<br />
snd_hwdep 6084 1 snd_hda_intel<br />
snd 34852 6 snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep<br />
soundcore 3744 1 snd<br />
genrtc 6028 0<br />
</pre><br />
<br />
lspci:<br />
<pre><br />
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)<br />
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)<br />
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)<br />
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)<br />
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)<br />
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)<br />
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)<br />
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)<br />
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
01:00.0 Network controller: RaLink RT2790 Wireless 802.11n PCIe<br />
03:00.0 Ethernet controller: Atheros Corp. L1e Gigabit Ethernet Adapter (rev b0)<br />
</pre></div>
Faelar
https://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=47286
ASUS Eee PC 701
2008-08-07T19:56:46Z
<p>Faelar: /* Speeding up udev for faster boot */ skip the autoload process</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
'''WARNING: THIS ARTICLE IS INCOMPLETE!''' Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum]. There is also a nice Arch Linux installation guide on the [http://wiki.eeeuser.com/installingarchlinux EeeUser Wiki].<br />
<br />
==Before You Begin==<br />
<br />
===Avoiding Pitfalls===<br />
<br />
The install is pretty normal, except that you'll need to [http://forum.eeeuser.com/viewtopic.php?id=890 avoid the pitfalls] of our alternative Linux install:<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
The rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]] '''(Recommended)'''<br />
<br />
==Installing Arch Linux==<br />
<br />
* '''NOTE:''' Please refer to The [[Beginners_Guide]] for detailed instructions, if needed. Ideally, your CD/USB should boot up just fine on Eee PC without any need for additional options.<br />
<br />
===Booting Arch the installation CD/USB===<br />
<br />
The stock kernel on Arch installation media since 2008.06 and newer support Eee's ethernet network card. So there's no need to install any additional modules before or during the installation process to have a working network connection (unless you want to use wireless network card). <br />
<br />
===Start the Installation===<br />
<br />
If you are installing from the USB, then issue<br />
<br />
mount /dev/sd[x] /src<br />
<br />
To mount the usb.<br />
<br />
Then just run<br />
<br />
/arch/setup<br />
<br />
To start the installation just like normal.<br />
<br />
===Prepare Hard Drive===<br />
<br />
The default Eee PC drive is split up into four partitions (here is [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* It is easiest to wipe the existing partitions and use one or two partitions for your install. One partition would be just '/', and two partitions would be '/boot' and '/'.<br />
* Choose "NONE" for swap (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
* Select "ext2" as your filesystem (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
<br />
===Select Packages===<br />
<br />
If you are installing from USB, then choose SRC as your source.<br />
<br />
In addition to the '''BASE''' category, you also need all of the packages in the '''DEVEL''' category if you are planning on compiling stuffs on your Eee.<br />
<br />
If you intended to use wireless, then you'll also need the ''wireless_tools'' package from '''SUPPORT''' category.<br />
<br />
===Install Customized Kernel and All the Necessary Modules===<br />
<br />
After you have install all the packages you want from your installation media of choice, the next step is to install the kernel that was customized for Eee and all the necessary modules. <br />
<br />
Since toofishes' kernel-eee is currently the most up to date one and contains all the necessary modules and patches for Eee (while the stock kernel lacks most of them), it is recommended that you use kernel-eee from toofishes' repository.<br />
<br />
====Eee repository from toofishes====<br />
toofishes created a repository for the Eee. You can find some basic packages like Pentium-M-optimized kernel and needed modules. Add<br />
[eee]<br />
Server = http://code.toofishes.net/packages/eee<br />
to your /etc/pacman.conf to use the repository.<br />
<br />
=====Package List=====<br />
<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' <br />
customized kernel for Eee<br />
*'''luvcview''' <br />
webcam program for testing webcam driver<br />
*'''madwifi-eee-svn''' <br />
wifi driver for Eee<br />
*'''eeepc-linux''' <br />
kernel module to change Eee's FSB speed and fan control<br />
<br />
=====Installation Instruction=====<br />
<br />
Simply use pacman to install the package that you need. For a working system, you'll need at least 3 packages: kernel-eee (the kernel), linux-uvc-eee-svn (webcam driver) and madwifi-eee-svn (the wifi driver).<br />
<br />
Install the packages with this command:<br />
<br />
pacman -Sy kernel-eee madwifi-eee-svn<br />
<br />
*'''ATTENTION:''' dkite's eeemodules package conflicts with the madwifi-eee-svn package. You need to remove dkite's eeemodules package before you can install toofishes madfwifi-eee-svn package.<br />
<br />
Then, add the following to /boot/grub/menu.lst; note that no initrd is needed:<br />
# (2) Arch Linux<br />
title Arch Linux EEE kernel<br />
root (hd0,0)<br />
kernel /boot/vmlinuzeee root=/dev/sda1 ro<br />
<br />
Restart and select Arch Linux EEE kernel from the grub boot menu.<br />
<br />
===Add the Final Touch===<br />
<br />
After you have install kernel-eee and all the related packages as noted above, make these edits to /etc/fstab:<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* '''OPTIONAL:''' Add a new line: "tmpfs /var/log tmpfs size=1M 0 0" ('''WARNING:''' this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]. To save your startup/shutdown logs, look at the pitfalls link above).<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. The following is the guide on how to get the rest of your system working.<br />
<br />
===Xorg===<br />
<br />
You have two choices for video on the Eee - the newer <b>xf86-video-intel</b> driver, or the older <b>xf86-video-i810</b> driver paired with 915resolution. The intel driver is the focus upstream and is being actively developed so it is your best choice. <br />
<br />
However, if you wish to use composite extension (for Compiz Fusion, for example), then the old i810 driver might be a better option, mainly because XV video output does not work when composite is enabled on the currently intel driver and thus a lot of applications, such as Skype or UCView, will not function properly.<br />
<br />
You need these packages in addition to the Xorg's packages:<br />
<br />
pacman -Sy synaptics xf86-video-intel<br />
<br />
If you choose to use the older i810 video, you will have to install xf86-video-i810 and 915resolution as well. Note that the i810 driver and the intel driver cannot both be installed at the same time.<br />
<br />
Then, just drop in the following xorg.conf into your /etc/X11/ directory:<br />
<br />
<pre>Section "ServerLayout"<br />
Identifier "ArchLinux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "extmod"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail"<br />
Option "BlankTime" "5"<br />
Option "AIGLX" "false"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "keyboard"<br />
Driver "kbd"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbLayout" "us"<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "IMPS/2"<br />
Option "Emulate3Buttons" "yes"<br />
Option "ZAxisMapping" "4 5"<br />
Option "CorePointer"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "synaptics"<br />
Driver "synaptics"<br />
Option "Device" "/dev/psaux"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1000"<br />
Option "RightEdge" "5400"<br />
Option "TopEdge" "1000"<br />
Option "BottomEdge" "4900"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "HorizScrollDelta" "0" <br />
Option "RBCornerButton" "0"<br />
Option "RTCornerButtom" "0"<br />
Option "MaxSpeed" "0.1"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "ASUS"<br />
ModelName "eeePC P701"<br />
Modeline "800x480" 29.58 800 816 896 992 480 481 484 497 -HSync +Vsync # 60 Hz<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "intel"<br />
VendorName "Intel Corporation"<br />
BoardName "Mobile 915GM/GMS/910GML Express Graphics Controller"<br />
BusID "PCI:0:2:0"<br />
Option "AccelMethod" "EXA"<br />
Option "MigrationHeuristic" "greedy"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</pre><br />
<br />
If you want to set up the i810 driver instead, you will also have to configure 915resolution and add it to your daemons line. This is not needed for the intel driver. Edit the /etc/conf.d/915resolution to look like this:<br />
<br />
<pre># Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
</pre><br />
<br />
Now put the 915resolution daemon into your /etc/rc.conf file:<br />
<br />
<pre>DAEMONS=(... 915resolution ...)</pre><br />
<br />
===Sound, Webcam & Microphone===<br />
<br />
====Sound====<br />
<br />
Some people have reported sound working right out of the box with no troubles. However, others might need to add the following line to /etc/modprobe.conf.<br />
<br />
<pre>options snd-hda-intel model=3stack-dig</pre><br />
<br />
If your internal microphone doesn't work, you probably have to turn the capture feature on. Simply fire up alsamixer, find your Capture control, and press spacebar to enable it.<br />
<br />
====Webcam====<br />
<br />
You can enable your built-in webcam by adding the following line to your /etc/rc.local file.<br />
<br />
echo 1 > /proc/acpi/asus/camera<br />
<br />
If you want the webcam application that the default Xandos installation uses, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14469 ucview from the AUR].<br />
<br />
The webcam also works fine with the latest version of Skype.<br />
<br />
If you already have mplayer installed you can launch :<br />
mplayer -fps 15 tv://<br />
<br />
I have yet to get it working with vlc or any other software such as xawtv. If you know how, please update this.<br />
<br />
*'''NOTE:''' For anyone who has accidentally disabled Auto Exposure for their webcam in luvcview (making the image dark), and can't enable it again, do the following:<br />
<br />
Install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14468 libwebcam from the AUR].<br />
<br />
Issue the following command:<br />
<pre>uvcdynctrl --set "Exposure, Auto" 4</pre><br />
<br />
*'''NOTE:''' Be sure the "OS Installation" option is set to "finished" in the BIOS' "Advanced" tab or your camera may not work in some applications (like Skype).<br />
<br />
====Microphone====<br />
<br />
Solution for problems with the internal microphone.<br />
<br />
1. First of all set in alsamixer "Input Source" to "i-Mic"<br />
<br />
2. Increase "Capture" and "i-Mic Boost" to your needs<br />
<br />
3. Edit /etc/asound.state the following, change the 2 "false" to "true" like showing:<br />
<pre><br />
....snap.....<br />
control.11 {<br />
comment.access 'read write'<br />
comment.type BOOLEAN<br />
comment.count 2<br />
iface MIXER<br />
name 'Capture Switch'<br />
value.0 true<br />
value.1 true<br />
}<br />
....snap....</pre><br />
<br />
4. After editing run following as root<br />
<pre>alsactl restore</pre><br />
<br />
5. Now your internal microphone should be working.<br />
<br />
===Getting Hot Keys, Graphic Indicators and Shutdown with the Power Button Working===<br />
<br />
If you want to have working hot keys for changing brightness and volumes, graphic indicators working as well as shutdown when press the power button (just like in the stock Eee PC), then you should install '''ighea's acpi-eee''' or '''dkite's acpid_eee''' package.<br />
<br />
==== ighea's acpi-eee ====<br />
<br />
Get the latest package from [http://kapsi.fi/ighea/eee/acpi-eee/ here].<br />
<br />
The package can be easily installed with<br />
pacman -U acpi-eee-8-1-i686.pkg.tar.gz<br />
<br />
See messages during installation for more details and don't forget to edit /etc/acpi/eee.conf to suit your tastes.<br />
<br />
==== dkite's acpid_eee ====<br />
<br />
Package can also be download from his [http://members.shaw.ca/dkite/ website]<br />
<br />
The package itself can be install with<br />
<br />
pacman -Uf acpid_eee-0.0.3-1-i686.pkg.tar.gz.tar<br />
<br />
With '''both''' packages don't forget to start '''asusosd''' if you want to have the Graphic Indicators from Xandros.<br />
<br />
==Additional Tips & Tweaks==<br />
<br />
===kernel26eee tweaks===<br />
<br />
Toofishes's kernel, also known as kernel26eee, can be recompile to include custom features. You can download toofishes' kernel PKGBUILD and all the nesseary files from his gitweb by install git package and use the following command:<br />
<br />
git clone http://code.toofishes.net/gitprojects/eee.git<br />
<br />
There are two ways to tweak the kernal. The first is simply to edit the '''kernelconfig''' file with your favorite editor and the second is to insert a 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 compile 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 instruction, then change the following lines in 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 />
<br />
To this:<br />
<pre><br />
...<br />
230 CONFIG_NOHIGHMEM=y<br />
231 # CONFIG_HIGHMEM4G is not set<br />
232 # CONFIG_HIGHMEM64G is not set<br />
233 CONFIG_VMSPLIT_3G=y<br />
234 # CONFIG_VMSPLIT_3G_OPT is not set<br />
235 # CONFIG_VMSPLIT_2G is not set<br />
236 # CONFIG_VMSPLIT_2G_OPT is not set<br />
237 # CONFIG_VMSPLIT_1G is not set<br />
...<br />
</pre><br />
Compile and install the kernel and Wine should now works.<br />
<br />
===Power down with the power button===<br />
<br />
* '''NOTE:''' If you are using ighea's acpi-eee or dkite's acpid_eee package then you should already be able to shutdown by pressing the power button and should not need to do this.<br />
<br />
The two alternatives here are described in [[Allow_users_to_shutdown]].<br />
<br />
If you don't already or don't plan to use sudo, it may be simpler to use the setuid /sbin/halt method, otherwise using sudo is preferred.<br />
<br />
Below are all the steps required for the sudo method. If you want to use the setuid method, read the article linked above and perform the 'power' file step here, while omitting the 'sudo' in it.<br />
<br />
<pre>pacman -S sudo</pre><br />
<br />
As root, do the following:<br />
<br />
<pre>visudo</pre><br />
<br />
Add the following line to the file:<br />
<br />
<pre>USER HOST = NOPASSWD: /sbin/poweroff</pre><br />
<br />
Where USER = the user you want to be able to power down with and HOST = your hostname (from /etc/rc.conf).<br />
<br />
Now, create a file called /etc/acpi/events/power, containing:<br />
<br />
<pre># /etc/acpi/events/power<br />
# This is called when the user presses the power button<br />
<br />
event=button/power (PWR.||PBTN)<br />
action=sudo /sbin/poweroff</pre><br />
<br />
Make sure that you execute<br />
<br />
<pre>/etc/rc.d/acpid start</pre><br />
<br />
And/or add acpid to the daemons list in /etc/rc.conf:<br />
<br />
<pre>DAEMONS=(hal, acpid ...</pre><br />
<br />
===Use cpufreq for power saving===<br />
<br />
* '''NOTE:''' If you are using toofishes's kernel, then processor scaling is already enable and you don't need to do the following steps.<br />
<br />
Install cpufrequtitls.<br />
pacman -S cpufrequtils<br />
<br />
For scaling down the processor you have to load the p4_clockmod module. Insert it into your /etc/rc.conf MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
<br />
Add 'cpufreq' to the DAEMONS array in /etc/rc.conf to have it start on startup.<br />
DAEMONS=(... cpufreq ...)<br />
<br />
Add the following into /etc/conf.d/cpufreq<br />
governor="ondemand"<br />
min_freq="113MHz"<br />
max_freq="900MHz"<br />
<br />
With enabled cpufreq it scales the processor between 113MHz up to max. frequency. That should save a lot on battery power. The stated 900MHz will be never reached by the eeePC, the p4_clockmod reports a wrong frequency here. But scaling works, you can feel it in the performance of eeePC that he slow down the processor.<br />
<br />
===More responsive system with ondemand governor===<br />
The default up_threshold (where it will bump to a faster speed) for the CPU governor is 80, which means it will increase the CPU speed when utilization is above 80%. This can make X applications have a bit of lag. <br />
Try changing this value:<br />
sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
With 40 it still leaves the majority of CPU cycles at the lowest available clock speed but increases responsiveness. You can add this line to one of your startup scripts (such as /etc/rc.local) if you wish to keep it, for example:<br />
<pre><br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
<br />
echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold<br />
</pre><br />
<br />
Also, following line is also reported to help makes system more responsive. You can use it by adding it to your /etc/rc.local:<br />
<pre><br />
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate<br />
</pre><br />
<br />
===Speeding up udev for faster boot===<br />
* [[Speedup udev]]<br />
*http://dev.laptop.org/ticket/4349<br />
*[http://www.eeesale.com/Asus-Eee-PC-overclock-Benchmarks.htm Speed up the Eee PC]<br />
<br />
You can also disable the autoload by editing your ''rc.conf'' :<br />
...<br />
MOD_AUTOLOAD="no"<br />
...<br />
MODULES=(pciehp wlan ath_hal ath_pci eeepc_laptop)<br />
<br />
===Update your BIOS without Xandros===<br />
* '''Warning : you can break your system, do not update if you are not sure of what you are doing!'''<br />
<br />
First, you need to download the ''.rom'' file.<br />
*[http://update.eeepc.asus.com/bios/ Asus official's BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USBStick formated in fat32.<br />
To format an USBStick, use cfdisk tool :<br />
cfdisk /dev/sdc #could be something else than "c"<br />
Choose [delete], [type] : "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
cp /somewhere/blabla/.../thecurrentnameofthefile.rom /dev/sdc1/701.rom<br />
The name of the copy '''must''' be 701.rom<br />
<br />
Next step, reboot the eeepc with the USBStick pluged-in, and press<br />
Alt + F2<br />
It will launch the built-in tool. Everything should be Ok, you can make a coffee during the update. When it asks you to push the power-button it has finished.<br />
<br />
At the next boot, you'll be invited to configure the BIOS. Check if the everything is enable (my webcam and wireless were disable after the update) and if it displays the good version in the main screen. It's done !<br />
<br />
===More usuable font sizes===<br />
<br />
On a default installation with XFCE 4 my font sizes were too big, here is what I did to sort them out.<br />
<br />
First, I set the DPI by adding the following to ~/.Xdefaults:<br />
Xft*dpi: 134<br />
<br />
This then caused the fonts to be even bigger, so I set them all to be font-size 6 by adding the following into ~/.gtkrc-2.0 (note this will be overwritten if you use any tools to change GTK settings):<br />
style "user-font"<br />
{<br />
font_name="Bitstream Vera Sans 6"<br />
}<br />
widget_class "*" style "user-font"<br />
<br />
To do the same with KDE fonts (without KDE installed) you have to add the following to ~/.kde/share/config/kdeglobals:<br />
[General]<br />
StandardFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
activeFont=Bitstream Vera Sans,6,-1,5,75,0,0,0,0,0<br />
fixed=Bitstream Vera Sans Mono,6,-1,5,50,0,0,0,0,0<br />
font=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
menuFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
taskbarFont=Bitstream Vera Sans,6,-1,5,50,1,0,0,0,0<br />
toolBarFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
<br />
To make your fonts even prettier enable the [[Fonts#Fonts_with_LCD_filter_enabled|LCD Fonts]].<br />
<br />
===Using stock kernel===<br />
<br />
Some users might want to use the stock kernel. Since the stock kernel lacks most of the necessary modules for Eee, we need to install them manually. There are two way of doing this: compile and install everything from source or use dkite's eeemodules packages.<br />
<br />
====Install All the Necessary Modules using dkite's eeemodule package==== <br />
<br />
'''dkite''' have created a package that contains all the necessary modules for wifi, ethernet connection, acpi and video camera hardware that comes with the Eee PC. His package is to be use with the stock kernel. <br />
<br />
The following is the list of hardware/functions that are known to work with dkite's eeemodules Package:<br />
<br />
*Wireless <br />
*Ethernet <br />
*Webcam <br />
*Suspend/Resume<br />
<br />
You can get the package [http://members.shaw.ca/dkite from his website]. <br />
<br />
Currently there are three pre-complied package:<br />
<br />
#'''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' for use with Don't Panic kernel.<br />
#'''eeemodules-0.0.3-2.6.24.1.2-i686.pkg.tar.gz''' for the 2.6.24.14-2 kernel.<br />
<br />
If you have newer or other version of kernel26, then you will need to download '''eeemodules.tar.gz''', which contains PKGBUILD and all the necessary files, and build the package yourself. <br />
<br />
*'''ATTENTION:''' You will also need to rebuild the package, using eeemodules.tar.gz, every time you upgrade your kernel, or else your hardware (wifi, ethernet, etc.) will stop functioning.<br />
<br />
=====Installation Instructions=====<br />
<br />
Install the package with the following command:<br />
<br />
pacman -Uf eeemodules-<pkgver>.tar.gz<br />
<br />
Then run a depmod command:<br />
<br />
depmod<br />
<br />
* '''ATTENTION:''' Do ''not'' forget to run the depmod command after installing the package, otherwise your hardware won't function! <br />
<br />
Finally, edit /etc/rc.conf and add asus_acpi to the MODULES array:<br />
<br />
MODULES = (... asus_acpi ...) <br />
<br />
====Compile and Install All the Necessary Modules from Source====<br />
<br />
* '''NOTE:''' for anyone who read this wiki previously and wondered where the patched kernel download went; the latest arch kernel contains the patch that fixes the intel graphics vsync hardlock error, so no additional configuration need be done<br />
<br />
=====Install Network Adapter Drivers=====<br />
<br />
======Atl2 ethernet driver======<br />
<br />
* '''UPDATE:''' the atl2 ethernet is support by Arch Linux's stock kernel as of 2008.03<br />
<br />
You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
<br />
Extract the sources. You may need to modify the kernel version listed in the Makefile.<br />
<br />
make clean<br />
make<br />
cp atl2.ko /lib/modules/2.6.24-ARCH/kernel/drivers/net # Change 2.6.24 as needed<br />
depmod<br />
<br />
======Atheros wireless ethernet driver======<br />
<br />
Instructions from http://wiki.eeeuser.com/ubuntu#wireless_internet_using_native_madwifi_drivers to patch madwifi. This replaces the Arch madwifi packages.<br />
<br />
wget 'http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw'<br />
wget http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
==Known problems and their solutions==<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 toofiches' kernel, 2.6.26-1 now include the patch, but you can still use ighea's one for the extras features listed below.<br />
<br />
Until toofishes update his kernel to include the patch, you can use ighea's slightly modified toofishes' kernel that included the above patch, as well as other modifications:<br />
<br />
*Support for Wine <br />
*uvesafb is built as module <br />
*Use [http://bbs.archlinux.org/viewtopic.php?pid=393860#p393860 new eeepc-laptop driver] (which also handles fan-control) instead of older acus_acpi or asus-laptop -drivers.<br />
<br />
You can get the modified kernel, as well as the associative packages, from [http://koti.kapsi.fi/~ighea/eee/kernel-eee/ here].<br />
<br />
After you have downloaded the packages, Install them using this command:<br />
<br />
pacman -U kernel-eee-2.6.26-1-i686.pkg.tar.gz madwifi-eee-svn-3752-1-i686.pkg.tar.gz <br />
<br />
You might also want to use IgnorePkg-line in /etc/pacman.conf to hold packages from being accidentally updated.<br />
<br />
IgnorePkg = kernel-eee madwifi-eee-svn<br />
<br />
Also don't forget to upgrade ighea's acpi-eee package to version 9.6.<br />
<br />
===Shutdown Problem===<br />
<br />
If your Eee won't shutdown properly (i.e. the power indicator LED is on but the LCD screen is off), then add the following lines to your /etc/rc.local.shutdown file.<br />
<pre><br />
#! /bin/bash<br />
#<br />
# /etc/rc.local.shutdown: Local shutdown script.<br />
#<br />
<br />
# Comment or uncomment the following two lines according to your system configuration.<br />
<br />
/etc/rc.d/mpd stop # If you're using mpd, then you have to stop its daemon first.<br />
<br />
/etc/rc.d/alsa stop # If you're using ALSA daemon, then you also have to stop it.<br />
<br />
# The following line is Eee specific fix, you always need to have this line in /etc/rc.local.shutdown.<br />
<br />
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind<br />
</pre><br />
The above solution should fix the shutdown problem in most cases. But if for some reason the problem still persists, the module may not be able to be unloaded until after all services have finished. Do the above, then in /etc/rc.shutdown move <br />
<br />
if [ -x /etc/rc.local.shutdown ]; then<br />
/etc/rc.local.shutdown<br />
fi<br />
<br />
from where it was to directly above the line <br />
<br />
# Terminate all processes<br />
<br />
this will cause the rc.local.shutdown script to run after services have been exited. This fixed all issues for the person editing this note.<br />
<br />
===Unclean unmount during shutdown when having home directory mounted on SD card===<br />
<br />
If you experienced unclean unmount during shutdown when having your home directory on SD card, then add the following 3 lines to "Write to wtmp file before unmounting" section of your /etc/rc.shutdown file:<br />
<pre><br />
...<br />
<br />
stat_busy "Unmounting Filesystems"<br />
/bin/umount -a -t noramfs,notmpfs,nosysfs,noproc<br />
<br />
# Add these 3 lines<br />
sync;sync;sync;<br />
eject /dev/sdb # Or whichever is your SD-card's device name. /dev/disk/by-uuid/ followed by the UUID identifier is preferable though.<br />
sleep 3<br />
# End of hack<br />
<br />
stat_done<br />
<br />
...<br />
</pre><br />
<br />
===Booting from card without initrd===<br />
<br />
Let's say you decided to install Arch Linux on a card and compiled your own kernel (or used the kernel26eee kernel) without initrd. Card reader on EeePC is connected as an USB device. Unfortunately, USB storage devices are detected with a delay, so we must tell the kernel to wait until this device becomes available. You do this with "rootwait" option passed to kernel at boot time.<br />
<br />
===Sleeping and waking system on a card===<br />
<br />
If you have Arch Linux on a card, waking up from sleeping state will most likely fail. The only solution is to enable the CONFIG_USB_PERSIST option in kernel. The kernel26eee package should have this option enabled.<br />
<br />
===Display doesn't wake up properly===<br />
<br />
If you encounter black display (but apparently working system) after suspend/resume, consider using the "uswsusp" package (available in AUR) and correcting suspend2ram script in /etc/acpi, where you use this line to make the machine go to sleep:<br />
<br />
<pre>/usr/sbin/s2ram --force --vbe_post --vbe_mode</pre><br />
<br />
==Battery Tests==<br />
<br />
The following are reported battery runtimes:<br />
<br />
{| class="wikitable" style="text-align:left"<br />
|+Battery runtimes<br />
|-<br />
! Task !! Series !! Wireless !! Screen Brightness !! FSB Speed !! Fan Speed !! Runtime !! Comments<br />
|-<br />
! DVD Playback<br />
| 701 || On || Max || 85mhz || 100% || 134min || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! DVD Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! AVI Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading AVI from SSD<br />
|-<br />
! IM and Surf<br />
| 701 || On || ~30% || ??? || low || 173min || Normal web-browsing, Flash should reduce runtime a lot !<br />
|}<br />
<br />
N.B. - Will add battery runtimes as I am able to test them, please contribute.<br />
-- Grecko.1<br />
<br />
==Eee 901 20G lsmod and lspci==<br />
<br />
The following are from a stock ASUS EeePC 901 20G Linux version:<br />
<br />
lsmod:<br />
<pre><br />
Module Size Used by<br />
acpi_cpufreq 5004 0 <br />
freq_table 1988 1 acpi_cpufreq<br />
usb_storage 22980 0 <br />
libusual 6352 1 usb_storage<br />
pciehp 31172 0 <br />
pci_hotplug 9672 1 pciehp<br />
ehci_hcd 25420 0 <br />
uhci_hcd 18636 0 <br />
usbhid 13444 0 <br />
usbcore 91992 6 usb_storage,libusual,ehci_hcd,uhci_hcd,usbhid<br />
snd_pcm_oss 33568 0 <br />
snd_mixer_oss 13056 1 snd_pcm_oss<br />
rt2860sta 468248 1 <br />
atl1e 26388 0 <br />
fuse 34516 0 <br />
asus_acpi 6560 0 <br />
button 5648 0 <br />
processor 19820 1 acpi_cpufreq<br />
battery 7940 0 <br />
ac 3524 0 <br />
autofs4 15876 0 <br />
sr_mod 13284 0 <br />
cdrom 30624 1 sr_mod<br />
snd_hda_intel 284112 0 <br />
snd_pcm 50696 2 snd_pcm_oss,snd_hda_intel<br />
snd_timer 15556 1 snd_pcm<br />
snd_page_alloc 6728 2 snd_hda_intel,snd_pcm<br />
snd_hwdep 6084 1 snd_hda_intel<br />
snd 34852 6 snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep<br />
soundcore 3744 1 snd<br />
genrtc 6028 0<br />
</pre><br />
<br />
lspci:<br />
<pre><br />
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)<br />
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)<br />
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)<br />
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)<br />
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)<br />
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)<br />
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)<br />
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)<br />
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
01:00.0 Network controller: RaLink RT2790 Wireless 802.11n PCIe<br />
03:00.0 Ethernet controller: Atheros Corp. L1e Gigabit Ethernet Adapter (rev b0)<br />
</pre></div>
Faelar
https://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=47285
ASUS Eee PC 701
2008-08-07T19:49:16Z
<p>Faelar: /* Laggy or Unresponsive ACPI Events */ patch now present in toofishes' kernel too</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
'''WARNING: THIS ARTICLE IS INCOMPLETE!''' Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum]. There is also a nice Arch Linux installation guide on the [http://wiki.eeeuser.com/installingarchlinux EeeUser Wiki].<br />
<br />
==Before You Begin==<br />
<br />
===Avoiding Pitfalls===<br />
<br />
The install is pretty normal, except that you'll need to [http://forum.eeeuser.com/viewtopic.php?id=890 avoid the pitfalls] of our alternative Linux install:<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
The rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]] '''(Recommended)'''<br />
<br />
==Installing Arch Linux==<br />
<br />
* '''NOTE:''' Please refer to The [[Beginners_Guide]] for detailed instructions, if needed. Ideally, your CD/USB should boot up just fine on Eee PC without any need for additional options.<br />
<br />
===Booting Arch the installation CD/USB===<br />
<br />
The stock kernel on Arch installation media since 2008.06 and newer support Eee's ethernet network card. So there's no need to install any additional modules before or during the installation process to have a working network connection (unless you want to use wireless network card). <br />
<br />
===Start the Installation===<br />
<br />
If you are installing from the USB, then issue<br />
<br />
mount /dev/sd[x] /src<br />
<br />
To mount the usb.<br />
<br />
Then just run<br />
<br />
/arch/setup<br />
<br />
To start the installation just like normal.<br />
<br />
===Prepare Hard Drive===<br />
<br />
The default Eee PC drive is split up into four partitions (here is [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* It is easiest to wipe the existing partitions and use one or two partitions for your install. One partition would be just '/', and two partitions would be '/boot' and '/'.<br />
* Choose "NONE" for swap (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
* Select "ext2" as your filesystem (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
<br />
===Select Packages===<br />
<br />
If you are installing from USB, then choose SRC as your source.<br />
<br />
In addition to the '''BASE''' category, you also need all of the packages in the '''DEVEL''' category if you are planning on compiling stuffs on your Eee.<br />
<br />
If you intended to use wireless, then you'll also need the ''wireless_tools'' package from '''SUPPORT''' category.<br />
<br />
===Install Customized Kernel and All the Necessary Modules===<br />
<br />
After you have install all the packages you want from your installation media of choice, the next step is to install the kernel that was customized for Eee and all the necessary modules. <br />
<br />
Since toofishes' kernel-eee is currently the most up to date one and contains all the necessary modules and patches for Eee (while the stock kernel lacks most of them), it is recommended that you use kernel-eee from toofishes' repository.<br />
<br />
====Eee repository from toofishes====<br />
toofishes created a repository for the Eee. You can find some basic packages like Pentium-M-optimized kernel and needed modules. Add<br />
[eee]<br />
Server = http://code.toofishes.net/packages/eee<br />
to your /etc/pacman.conf to use the repository.<br />
<br />
=====Package List=====<br />
<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' <br />
customized kernel for Eee<br />
*'''luvcview''' <br />
webcam program for testing webcam driver<br />
*'''madwifi-eee-svn''' <br />
wifi driver for Eee<br />
*'''eeepc-linux''' <br />
kernel module to change Eee's FSB speed and fan control<br />
<br />
=====Installation Instruction=====<br />
<br />
Simply use pacman to install the package that you need. For a working system, you'll need at least 3 packages: kernel-eee (the kernel), linux-uvc-eee-svn (webcam driver) and madwifi-eee-svn (the wifi driver).<br />
<br />
Install the packages with this command:<br />
<br />
pacman -Sy kernel-eee madwifi-eee-svn<br />
<br />
*'''ATTENTION:''' dkite's eeemodules package conflicts with the madwifi-eee-svn package. You need to remove dkite's eeemodules package before you can install toofishes madfwifi-eee-svn package.<br />
<br />
Then, add the following to /boot/grub/menu.lst; note that no initrd is needed:<br />
# (2) Arch Linux<br />
title Arch Linux EEE kernel<br />
root (hd0,0)<br />
kernel /boot/vmlinuzeee root=/dev/sda1 ro<br />
<br />
Restart and select Arch Linux EEE kernel from the grub boot menu.<br />
<br />
===Add the Final Touch===<br />
<br />
After you have install kernel-eee and all the related packages as noted above, make these edits to /etc/fstab:<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* '''OPTIONAL:''' Add a new line: "tmpfs /var/log tmpfs size=1M 0 0" ('''WARNING:''' this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]. To save your startup/shutdown logs, look at the pitfalls link above).<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. The following is the guide on how to get the rest of your system working.<br />
<br />
===Xorg===<br />
<br />
You have two choices for video on the Eee - the newer <b>xf86-video-intel</b> driver, or the older <b>xf86-video-i810</b> driver paired with 915resolution. The intel driver is the focus upstream and is being actively developed so it is your best choice. <br />
<br />
However, if you wish to use composite extension (for Compiz Fusion, for example), then the old i810 driver might be a better option, mainly because XV video output does not work when composite is enabled on the currently intel driver and thus a lot of applications, such as Skype or UCView, will not function properly.<br />
<br />
You need these packages in addition to the Xorg's packages:<br />
<br />
pacman -Sy synaptics xf86-video-intel<br />
<br />
If you choose to use the older i810 video, you will have to install xf86-video-i810 and 915resolution as well. Note that the i810 driver and the intel driver cannot both be installed at the same time.<br />
<br />
Then, just drop in the following xorg.conf into your /etc/X11/ directory:<br />
<br />
<pre>Section "ServerLayout"<br />
Identifier "ArchLinux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "extmod"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail"<br />
Option "BlankTime" "5"<br />
Option "AIGLX" "false"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "keyboard"<br />
Driver "kbd"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbLayout" "us"<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "IMPS/2"<br />
Option "Emulate3Buttons" "yes"<br />
Option "ZAxisMapping" "4 5"<br />
Option "CorePointer"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "synaptics"<br />
Driver "synaptics"<br />
Option "Device" "/dev/psaux"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1000"<br />
Option "RightEdge" "5400"<br />
Option "TopEdge" "1000"<br />
Option "BottomEdge" "4900"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "HorizScrollDelta" "0" <br />
Option "RBCornerButton" "0"<br />
Option "RTCornerButtom" "0"<br />
Option "MaxSpeed" "0.1"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "ASUS"<br />
ModelName "eeePC P701"<br />
Modeline "800x480" 29.58 800 816 896 992 480 481 484 497 -HSync +Vsync # 60 Hz<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "intel"<br />
VendorName "Intel Corporation"<br />
BoardName "Mobile 915GM/GMS/910GML Express Graphics Controller"<br />
BusID "PCI:0:2:0"<br />
Option "AccelMethod" "EXA"<br />
Option "MigrationHeuristic" "greedy"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</pre><br />
<br />
If you want to set up the i810 driver instead, you will also have to configure 915resolution and add it to your daemons line. This is not needed for the intel driver. Edit the /etc/conf.d/915resolution to look like this:<br />
<br />
<pre># Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
</pre><br />
<br />
Now put the 915resolution daemon into your /etc/rc.conf file:<br />
<br />
<pre>DAEMONS=(... 915resolution ...)</pre><br />
<br />
===Sound, Webcam & Microphone===<br />
<br />
====Sound====<br />
<br />
Some people have reported sound working right out of the box with no troubles. However, others might need to add the following line to /etc/modprobe.conf.<br />
<br />
<pre>options snd-hda-intel model=3stack-dig</pre><br />
<br />
If your internal microphone doesn't work, you probably have to turn the capture feature on. Simply fire up alsamixer, find your Capture control, and press spacebar to enable it.<br />
<br />
====Webcam====<br />
<br />
You can enable your built-in webcam by adding the following line to your /etc/rc.local file.<br />
<br />
echo 1 > /proc/acpi/asus/camera<br />
<br />
If you want the webcam application that the default Xandos installation uses, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14469 ucview from the AUR].<br />
<br />
The webcam also works fine with the latest version of Skype.<br />
<br />
If you already have mplayer installed you can launch :<br />
mplayer -fps 15 tv://<br />
<br />
I have yet to get it working with vlc or any other software such as xawtv. If you know how, please update this.<br />
<br />
*'''NOTE:''' For anyone who has accidentally disabled Auto Exposure for their webcam in luvcview (making the image dark), and can't enable it again, do the following:<br />
<br />
Install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14468 libwebcam from the AUR].<br />
<br />
Issue the following command:<br />
<pre>uvcdynctrl --set "Exposure, Auto" 4</pre><br />
<br />
*'''NOTE:''' Be sure the "OS Installation" option is set to "finished" in the BIOS' "Advanced" tab or your camera may not work in some applications (like Skype).<br />
<br />
====Microphone====<br />
<br />
Solution for problems with the internal microphone.<br />
<br />
1. First of all set in alsamixer "Input Source" to "i-Mic"<br />
<br />
2. Increase "Capture" and "i-Mic Boost" to your needs<br />
<br />
3. Edit /etc/asound.state the following, change the 2 "false" to "true" like showing:<br />
<pre><br />
....snap.....<br />
control.11 {<br />
comment.access 'read write'<br />
comment.type BOOLEAN<br />
comment.count 2<br />
iface MIXER<br />
name 'Capture Switch'<br />
value.0 true<br />
value.1 true<br />
}<br />
....snap....</pre><br />
<br />
4. After editing run following as root<br />
<pre>alsactl restore</pre><br />
<br />
5. Now your internal microphone should be working.<br />
<br />
===Getting Hot Keys, Graphic Indicators and Shutdown with the Power Button Working===<br />
<br />
If you want to have working hot keys for changing brightness and volumes, graphic indicators working as well as shutdown when press the power button (just like in the stock Eee PC), then you should install '''ighea's acpi-eee''' or '''dkite's acpid_eee''' package.<br />
<br />
==== ighea's acpi-eee ====<br />
<br />
Get the latest package from [http://kapsi.fi/ighea/eee/acpi-eee/ here].<br />
<br />
The package can be easily installed with<br />
pacman -U acpi-eee-8-1-i686.pkg.tar.gz<br />
<br />
See messages during installation for more details and don't forget to edit /etc/acpi/eee.conf to suit your tastes.<br />
<br />
==== dkite's acpid_eee ====<br />
<br />
Package can also be download from his [http://members.shaw.ca/dkite/ website]<br />
<br />
The package itself can be install with<br />
<br />
pacman -Uf acpid_eee-0.0.3-1-i686.pkg.tar.gz.tar<br />
<br />
With '''both''' packages don't forget to start '''asusosd''' if you want to have the Graphic Indicators from Xandros.<br />
<br />
==Additional Tips & Tweaks==<br />
<br />
===kernel26eee tweaks===<br />
<br />
Toofishes's kernel, also known as kernel26eee, can be recompile to include custom features. You can download toofishes' kernel PKGBUILD and all the nesseary files from his gitweb by install git package and use the following command:<br />
<br />
git clone http://code.toofishes.net/gitprojects/eee.git<br />
<br />
There are two ways to tweak the kernal. The first is simply to edit the '''kernelconfig''' file with your favorite editor and the second is to insert a 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 compile 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 instruction, then change the following lines in 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 />
<br />
To this:<br />
<pre><br />
...<br />
230 CONFIG_NOHIGHMEM=y<br />
231 # CONFIG_HIGHMEM4G is not set<br />
232 # CONFIG_HIGHMEM64G is not set<br />
233 CONFIG_VMSPLIT_3G=y<br />
234 # CONFIG_VMSPLIT_3G_OPT is not set<br />
235 # CONFIG_VMSPLIT_2G is not set<br />
236 # CONFIG_VMSPLIT_2G_OPT is not set<br />
237 # CONFIG_VMSPLIT_1G is not set<br />
...<br />
</pre><br />
Compile and install the kernel and Wine should now works.<br />
<br />
===Power down with the power button===<br />
<br />
* '''NOTE:''' If you are using ighea's acpi-eee or dkite's acpid_eee package then you should already be able to shutdown by pressing the power button and should not need to do this.<br />
<br />
The two alternatives here are described in [[Allow_users_to_shutdown]].<br />
<br />
If you don't already or don't plan to use sudo, it may be simpler to use the setuid /sbin/halt method, otherwise using sudo is preferred.<br />
<br />
Below are all the steps required for the sudo method. If you want to use the setuid method, read the article linked above and perform the 'power' file step here, while omitting the 'sudo' in it.<br />
<br />
<pre>pacman -S sudo</pre><br />
<br />
As root, do the following:<br />
<br />
<pre>visudo</pre><br />
<br />
Add the following line to the file:<br />
<br />
<pre>USER HOST = NOPASSWD: /sbin/poweroff</pre><br />
<br />
Where USER = the user you want to be able to power down with and HOST = your hostname (from /etc/rc.conf).<br />
<br />
Now, create a file called /etc/acpi/events/power, containing:<br />
<br />
<pre># /etc/acpi/events/power<br />
# This is called when the user presses the power button<br />
<br />
event=button/power (PWR.||PBTN)<br />
action=sudo /sbin/poweroff</pre><br />
<br />
Make sure that you execute<br />
<br />
<pre>/etc/rc.d/acpid start</pre><br />
<br />
And/or add acpid to the daemons list in /etc/rc.conf:<br />
<br />
<pre>DAEMONS=(hal, acpid ...</pre><br />
<br />
===Use cpufreq for power saving===<br />
<br />
* '''NOTE:''' If you are using toofishes's kernel, then processor scaling is already enable and you don't need to do the following steps.<br />
<br />
Install cpufrequtitls.<br />
pacman -S cpufrequtils<br />
<br />
For scaling down the processor you have to load the p4_clockmod module. Insert it into your /etc/rc.conf MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
<br />
Add 'cpufreq' to the DAEMONS array in /etc/rc.conf to have it start on startup.<br />
DAEMONS=(... cpufreq ...)<br />
<br />
Add the following into /etc/conf.d/cpufreq<br />
governor="ondemand"<br />
min_freq="113MHz"<br />
max_freq="900MHz"<br />
<br />
With enabled cpufreq it scales the processor between 113MHz up to max. frequency. That should save a lot on battery power. The stated 900MHz will be never reached by the eeePC, the p4_clockmod reports a wrong frequency here. But scaling works, you can feel it in the performance of eeePC that he slow down the processor.<br />
<br />
===More responsive system with ondemand governor===<br />
The default up_threshold (where it will bump to a faster speed) for the CPU governor is 80, which means it will increase the CPU speed when utilization is above 80%. This can make X applications have a bit of lag. <br />
Try changing this value:<br />
sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
With 40 it still leaves the majority of CPU cycles at the lowest available clock speed but increases responsiveness. You can add this line to one of your startup scripts (such as /etc/rc.local) if you wish to keep it, for example:<br />
<pre><br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
<br />
echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold<br />
</pre><br />
<br />
Also, following line is also reported to help makes system more responsive. You can use it by adding it to your /etc/rc.local:<br />
<pre><br />
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate<br />
</pre><br />
<br />
===Speeding up udev for faster boot===<br />
* [[Speedup udev]]<br />
*http://dev.laptop.org/ticket/4349<br />
*[http://www.eeesale.com/Asus-Eee-PC-overclock-Benchmarks.htm Speed up the Eee PC]<br />
<br />
===Update your BIOS without Xandros===<br />
* '''Warning : you can break your system, do not update if you are not sure of what you are doing!'''<br />
<br />
First, you need to download the ''.rom'' file.<br />
*[http://update.eeepc.asus.com/bios/ Asus official's BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USBStick formated in fat32.<br />
To format an USBStick, use cfdisk tool :<br />
cfdisk /dev/sdc #could be something else than "c"<br />
Choose [delete], [type] : "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
cp /somewhere/blabla/.../thecurrentnameofthefile.rom /dev/sdc1/701.rom<br />
The name of the copy '''must''' be 701.rom<br />
<br />
Next step, reboot the eeepc with the USBStick pluged-in, and press<br />
Alt + F2<br />
It will launch the built-in tool. Everything should be Ok, you can make a coffee during the update. When it asks you to push the power-button it has finished.<br />
<br />
At the next boot, you'll be invited to configure the BIOS. Check if the everything is enable (my webcam and wireless were disable after the update) and if it displays the good version in the main screen. It's done !<br />
<br />
===More usuable font sizes===<br />
<br />
On a default installation with XFCE 4 my font sizes were too big, here is what I did to sort them out.<br />
<br />
First, I set the DPI by adding the following to ~/.Xdefaults:<br />
Xft*dpi: 134<br />
<br />
This then caused the fonts to be even bigger, so I set them all to be font-size 6 by adding the following into ~/.gtkrc-2.0 (note this will be overwritten if you use any tools to change GTK settings):<br />
style "user-font"<br />
{<br />
font_name="Bitstream Vera Sans 6"<br />
}<br />
widget_class "*" style "user-font"<br />
<br />
To do the same with KDE fonts (without KDE installed) you have to add the following to ~/.kde/share/config/kdeglobals:<br />
[General]<br />
StandardFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
activeFont=Bitstream Vera Sans,6,-1,5,75,0,0,0,0,0<br />
fixed=Bitstream Vera Sans Mono,6,-1,5,50,0,0,0,0,0<br />
font=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
menuFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
taskbarFont=Bitstream Vera Sans,6,-1,5,50,1,0,0,0,0<br />
toolBarFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
<br />
To make your fonts even prettier enable the [[Fonts#Fonts_with_LCD_filter_enabled|LCD Fonts]].<br />
<br />
===Using stock kernel===<br />
<br />
Some users might want to use the stock kernel. Since the stock kernel lacks most of the necessary modules for Eee, we need to install them manually. There are two way of doing this: compile and install everything from source or use dkite's eeemodules packages.<br />
<br />
====Install All the Necessary Modules using dkite's eeemodule package==== <br />
<br />
'''dkite''' have created a package that contains all the necessary modules for wifi, ethernet connection, acpi and video camera hardware that comes with the Eee PC. His package is to be use with the stock kernel. <br />
<br />
The following is the list of hardware/functions that are known to work with dkite's eeemodules Package:<br />
<br />
*Wireless <br />
*Ethernet <br />
*Webcam <br />
*Suspend/Resume<br />
<br />
You can get the package [http://members.shaw.ca/dkite from his website]. <br />
<br />
Currently there are three pre-complied package:<br />
<br />
#'''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' for use with Don't Panic kernel.<br />
#'''eeemodules-0.0.3-2.6.24.1.2-i686.pkg.tar.gz''' for the 2.6.24.14-2 kernel.<br />
<br />
If you have newer or other version of kernel26, then you will need to download '''eeemodules.tar.gz''', which contains PKGBUILD and all the necessary files, and build the package yourself. <br />
<br />
*'''ATTENTION:''' You will also need to rebuild the package, using eeemodules.tar.gz, every time you upgrade your kernel, or else your hardware (wifi, ethernet, etc.) will stop functioning.<br />
<br />
=====Installation Instructions=====<br />
<br />
Install the package with the following command:<br />
<br />
pacman -Uf eeemodules-<pkgver>.tar.gz<br />
<br />
Then run a depmod command:<br />
<br />
depmod<br />
<br />
* '''ATTENTION:''' Do ''not'' forget to run the depmod command after installing the package, otherwise your hardware won't function! <br />
<br />
Finally, edit /etc/rc.conf and add asus_acpi to the MODULES array:<br />
<br />
MODULES = (... asus_acpi ...) <br />
<br />
====Compile and Install All the Necessary Modules from Source====<br />
<br />
* '''NOTE:''' for anyone who read this wiki previously and wondered where the patched kernel download went; the latest arch kernel contains the patch that fixes the intel graphics vsync hardlock error, so no additional configuration need be done<br />
<br />
=====Install Network Adapter Drivers=====<br />
<br />
======Atl2 ethernet driver======<br />
<br />
* '''UPDATE:''' the atl2 ethernet is support by Arch Linux's stock kernel as of 2008.03<br />
<br />
You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
<br />
Extract the sources. You may need to modify the kernel version listed in the Makefile.<br />
<br />
make clean<br />
make<br />
cp atl2.ko /lib/modules/2.6.24-ARCH/kernel/drivers/net # Change 2.6.24 as needed<br />
depmod<br />
<br />
======Atheros wireless ethernet driver======<br />
<br />
Instructions from http://wiki.eeeuser.com/ubuntu#wireless_internet_using_native_madwifi_drivers to patch madwifi. This replaces the Arch madwifi packages.<br />
<br />
wget 'http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw'<br />
wget http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
==Known problems and their solutions==<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 toofiches' kernel, 2.6.26-1 now include the patch, but you can still use ighea's one for the extras features listed below.<br />
<br />
Until toofishes update his kernel to include the patch, you can use ighea's slightly modified toofishes' kernel that included the above patch, as well as other modifications:<br />
<br />
*Support for Wine <br />
*uvesafb is built as module <br />
*Use [http://bbs.archlinux.org/viewtopic.php?pid=393860#p393860 new eeepc-laptop driver] (which also handles fan-control) instead of older acus_acpi or asus-laptop -drivers.<br />
<br />
You can get the modified kernel, as well as the associative packages, from [http://koti.kapsi.fi/~ighea/eee/kernel-eee/ here].<br />
<br />
After you have downloaded the packages, Install them using this command:<br />
<br />
pacman -U kernel-eee-2.6.26-1-i686.pkg.tar.gz madwifi-eee-svn-3752-1-i686.pkg.tar.gz <br />
<br />
You might also want to use IgnorePkg-line in /etc/pacman.conf to hold packages from being accidentally updated.<br />
<br />
IgnorePkg = kernel-eee madwifi-eee-svn<br />
<br />
Also don't forget to upgrade ighea's acpi-eee package to version 9.6.<br />
<br />
===Shutdown Problem===<br />
<br />
If your Eee won't shutdown properly (i.e. the power indicator LED is on but the LCD screen is off), then add the following lines to your /etc/rc.local.shutdown file.<br />
<pre><br />
#! /bin/bash<br />
#<br />
# /etc/rc.local.shutdown: Local shutdown script.<br />
#<br />
<br />
# Comment or uncomment the following two lines according to your system configuration.<br />
<br />
/etc/rc.d/mpd stop # If you're using mpd, then you have to stop its daemon first.<br />
<br />
/etc/rc.d/alsa stop # If you're using ALSA daemon, then you also have to stop it.<br />
<br />
# The following line is Eee specific fix, you always need to have this line in /etc/rc.local.shutdown.<br />
<br />
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind<br />
</pre><br />
The above solution should fix the shutdown problem in most cases. But if for some reason the problem still persists, the module may not be able to be unloaded until after all services have finished. Do the above, then in /etc/rc.shutdown move <br />
<br />
if [ -x /etc/rc.local.shutdown ]; then<br />
/etc/rc.local.shutdown<br />
fi<br />
<br />
from where it was to directly above the line <br />
<br />
# Terminate all processes<br />
<br />
this will cause the rc.local.shutdown script to run after services have been exited. This fixed all issues for the person editing this note.<br />
<br />
===Unclean unmount during shutdown when having home directory mounted on SD card===<br />
<br />
If you experienced unclean unmount during shutdown when having your home directory on SD card, then add the following 3 lines to "Write to wtmp file before unmounting" section of your /etc/rc.shutdown file:<br />
<pre><br />
...<br />
<br />
stat_busy "Unmounting Filesystems"<br />
/bin/umount -a -t noramfs,notmpfs,nosysfs,noproc<br />
<br />
# Add these 3 lines<br />
sync;sync;sync;<br />
eject /dev/sdb # Or whichever is your SD-card's device name. /dev/disk/by-uuid/ followed by the UUID identifier is preferable though.<br />
sleep 3<br />
# End of hack<br />
<br />
stat_done<br />
<br />
...<br />
</pre><br />
<br />
===Booting from card without initrd===<br />
<br />
Let's say you decided to install Arch Linux on a card and compiled your own kernel (or used the kernel26eee kernel) without initrd. Card reader on EeePC is connected as an USB device. Unfortunately, USB storage devices are detected with a delay, so we must tell the kernel to wait until this device becomes available. You do this with "rootwait" option passed to kernel at boot time.<br />
<br />
===Sleeping and waking system on a card===<br />
<br />
If you have Arch Linux on a card, waking up from sleeping state will most likely fail. The only solution is to enable the CONFIG_USB_PERSIST option in kernel. The kernel26eee package should have this option enabled.<br />
<br />
===Display doesn't wake up properly===<br />
<br />
If you encounter black display (but apparently working system) after suspend/resume, consider using the "uswsusp" package (available in AUR) and correcting suspend2ram script in /etc/acpi, where you use this line to make the machine go to sleep:<br />
<br />
<pre>/usr/sbin/s2ram --force --vbe_post --vbe_mode</pre><br />
<br />
==Battery Tests==<br />
<br />
The following are reported battery runtimes:<br />
<br />
{| class="wikitable" style="text-align:left"<br />
|+Battery runtimes<br />
|-<br />
! Task !! Series !! Wireless !! Screen Brightness !! FSB Speed !! Fan Speed !! Runtime !! Comments<br />
|-<br />
! DVD Playback<br />
| 701 || On || Max || 85mhz || 100% || 134min || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! DVD Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! AVI Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading AVI from SSD<br />
|-<br />
! IM and Surf<br />
| 701 || On || ~30% || ??? || low || 173min || Normal web-browsing, Flash should reduce runtime a lot !<br />
|}<br />
<br />
N.B. - Will add battery runtimes as I am able to test them, please contribute.<br />
-- Grecko.1<br />
<br />
==Eee 901 20G lsmod and lspci==<br />
<br />
The following are from a stock ASUS EeePC 901 20G Linux version:<br />
<br />
lsmod:<br />
<pre><br />
Module Size Used by<br />
acpi_cpufreq 5004 0 <br />
freq_table 1988 1 acpi_cpufreq<br />
usb_storage 22980 0 <br />
libusual 6352 1 usb_storage<br />
pciehp 31172 0 <br />
pci_hotplug 9672 1 pciehp<br />
ehci_hcd 25420 0 <br />
uhci_hcd 18636 0 <br />
usbhid 13444 0 <br />
usbcore 91992 6 usb_storage,libusual,ehci_hcd,uhci_hcd,usbhid<br />
snd_pcm_oss 33568 0 <br />
snd_mixer_oss 13056 1 snd_pcm_oss<br />
rt2860sta 468248 1 <br />
atl1e 26388 0 <br />
fuse 34516 0 <br />
asus_acpi 6560 0 <br />
button 5648 0 <br />
processor 19820 1 acpi_cpufreq<br />
battery 7940 0 <br />
ac 3524 0 <br />
autofs4 15876 0 <br />
sr_mod 13284 0 <br />
cdrom 30624 1 sr_mod<br />
snd_hda_intel 284112 0 <br />
snd_pcm 50696 2 snd_pcm_oss,snd_hda_intel<br />
snd_timer 15556 1 snd_pcm<br />
snd_page_alloc 6728 2 snd_hda_intel,snd_pcm<br />
snd_hwdep 6084 1 snd_hda_intel<br />
snd 34852 6 snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep<br />
soundcore 3744 1 snd<br />
genrtc 6028 0<br />
</pre><br />
<br />
lspci:<br />
<pre><br />
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)<br />
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)<br />
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)<br />
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)<br />
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)<br />
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)<br />
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)<br />
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)<br />
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
01:00.0 Network controller: RaLink RT2790 Wireless 802.11n PCIe<br />
03:00.0 Ethernet controller: Atheros Corp. L1e Gigabit Ethernet Adapter (rev b0)<br />
</pre></div>
Faelar
https://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=46890
ASUS Eee PC 701
2008-08-02T14:16:23Z
<p>Faelar: /* Battery Tests */ IM and Surf</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
'''WARNING: THIS ARTICLE IS INCOMPLETE!''' Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum]. There is also a nice Arch Linux installation guide on the [http://wiki.eeeuser.com/installingarchlinux EeeUser Wiki].<br />
<br />
==Before You Begin==<br />
<br />
===Avoiding Pitfalls===<br />
<br />
The install is pretty normal, except that you'll need to [http://forum.eeeuser.com/viewtopic.php?id=890 avoid the pitfalls] of our alternative Linux install:<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
The rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]] '''(Recommended)'''<br />
<br />
==Installing Arch Linux==<br />
<br />
* '''NOTE:''' Please refer to The [[Beginners_Guide]] for detailed instructions, if needed. Ideally, your CD/USB should boot up just fine on Eee PC without any need for additional options.<br />
<br />
===Booting Arch the installation CD/USB===<br />
<br />
The stock kernel on Arch installation media since 2008.06 and newer support Eee's ethernet network card. So there's no need to install any additional modules before or during the installation process to have a working network connection (unless you want to use wireless network card). <br />
<br />
===Start the Installation===<br />
<br />
If you are installing from the USB, then issue<br />
<br />
mount /dev/sd[x] /src<br />
<br />
To mount the usb.<br />
<br />
Then just run<br />
<br />
/arch/setup<br />
<br />
To start the installation just like normal.<br />
<br />
===Prepare Hard Drive===<br />
<br />
The default Eee PC drive is split up into four partitions (here is [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* It is easiest to wipe the existing partitions and use one or two partitions for your install. One partition would be just '/', and two partitions would be '/boot' and '/'.<br />
* Choose "NONE" for swap (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
* Select "ext2" as your filesystem (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
<br />
===Select Packages===<br />
<br />
If you are installing from USB, then choose SRC as your source.<br />
<br />
In addition to the '''BASE''' category, you also need all of the packages in the '''DEVEL''' category if you are planning on compiling stuffs on your Eee.<br />
<br />
If you intended to use wireless, then you'll also need the ''wireless_tools'' package from '''SUPPORT''' category.<br />
<br />
===Install Customized Kernel and All the Necessary Modules===<br />
<br />
After you have install all the packages you want from your installation media of choice, the next step is to install the kernel that was customized for Eee and all the necessary modules. <br />
<br />
Since toofishes' kernel-eee is currently the most up to date one and contains all the necessary modules and patches for Eee (while the stock kernel lacks most of them), it is recommended that you use kernel-eee from toofishes' repository.<br />
<br />
====Eee repository from toofishes====<br />
toofishes created a repository for the Eee. You can find some basic packages like Pentium-M-optimized kernel and needed modules. Add<br />
[eee]<br />
Server = http://code.toofishes.net/packages/eee<br />
to your /etc/pacman.conf to use the repository.<br />
<br />
=====Package List=====<br />
<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' <br />
customized kernel for Eee<br />
*'''luvcview''' <br />
webcam program for testing webcam driver<br />
*'''madwifi-eee-svn''' <br />
wifi driver for Eee<br />
*'''eeepc-linux''' <br />
kernel module to change Eee's FSB speed and fan control<br />
<br />
=====Installation Instruction=====<br />
<br />
Simply use pacman to install the package that you need. For a working system, you'll need at least 3 packages: kernel-eee (the kernel), linux-uvc-eee-svn (webcam driver) and madwifi-eee-svn (the wifi driver).<br />
<br />
Install the packages with this command:<br />
<br />
pacman -Sy kernel-eee madwifi-eee-svn<br />
<br />
*'''ATTENTION:''' dkite's eeemodules package conflicts with the madwifi-eee-svn package. You need to remove dkite's eeemodules package before you can install toofishes madfwifi-eee-svn package.<br />
<br />
Then, add the following to /boot/grub/menu.lst; note that no initrd is needed:<br />
# (2) Arch Linux<br />
title Arch Linux EEE kernel<br />
root (hd0,0)<br />
kernel /boot/vmlinuzeee root=/dev/sda1 ro<br />
<br />
Restart and select Arch Linux EEE kernel from the grub boot menu.<br />
<br />
===Add the Final Touch===<br />
<br />
After you have install kernel-eee and all the related packages as noted above, make these edits to /etc/fstab:<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* '''OPTIONAL:''' Add a new line: "tmpfs /var/log tmpfs size=1M 0 0" ('''WARNING:''' this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]. To save your startup/shutdown logs, look at the pitfalls link above).<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. The following is the guide on how to get the rest of your system working.<br />
<br />
===Xorg===<br />
<br />
You have two choices for video on the Eee - the newer <b>xf86-video-intel</b> driver, or the older <b>xf86-video-i810</b> driver paired with 915resolution. The intel driver is the focus upstream and is being actively developed so it is your best choice. <br />
<br />
However, if you wish to use composite extension (for Compiz Fusion, for example), then the old i810 driver might be a better option, mainly because XV video output does not work when composite is enabled on the currently intel driver and thus a lot of applications, such as Skype or UCView, will not function properly.<br />
<br />
You need these packages in addition to the Xorg's packages:<br />
<br />
pacman -Sy synaptics xf86-video-intel<br />
<br />
If you choose to use the older i810 video, you will have to install xf86-video-i810 and 915resolution as well. Note that the i810 driver and the intel driver cannot both be installed at the same time.<br />
<br />
Then, just drop in the following xorg.conf into your /etc/X11/ directory:<br />
<br />
<pre>Section "ServerLayout"<br />
Identifier "ArchLinux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "extmod"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail"<br />
Option "BlankTime" "5"<br />
Option "AIGLX" "false"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "keyboard"<br />
Driver "kbd"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbLayout" "us"<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "IMPS/2"<br />
Option "Emulate3Buttons" "yes"<br />
Option "ZAxisMapping" "4 5"<br />
Option "CorePointer"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "synaptics"<br />
Driver "synaptics"<br />
Option "Device" "/dev/psaux"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1000"<br />
Option "RightEdge" "5400"<br />
Option "TopEdge" "1000"<br />
Option "BottomEdge" "4900"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "HorizScrollDelta" "0" <br />
Option "RBCornerButton" "0"<br />
Option "RTCornerButtom" "0"<br />
Option "MaxSpeed" "0.1"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "ASUS"<br />
ModelName "eeePC P701"<br />
Modeline "800x480" 29.58 800 816 896 992 480 481 484 497 -HSync +Vsync # 60 Hz<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "intel"<br />
VendorName "Intel Corporation"<br />
BoardName "Mobile 915GM/GMS/910GML Express Graphics Controller"<br />
BusID "PCI:0:2:0"<br />
Option "AccelMethod" "EXA"<br />
Option "MigrationHeuristic" "greedy"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</pre><br />
<br />
If you want to set up the i810 driver instead, you will also have to configure 915resolution and add it to your daemons line. This is not needed for the intel driver. Edit the /etc/conf.d/915resolution to look like this:<br />
<br />
<pre># Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
</pre><br />
<br />
Now put the 915resolution daemon into your /etc/rc.conf file:<br />
<br />
<pre>DAEMONS=(... 915resolution ...)</pre><br />
<br />
===Sound, Webcam & Microphone===<br />
<br />
====Sound====<br />
<br />
Some people have reported sound working right out of the box with no troubles. However, others might need to add the following line to /etc/modprobe.conf.<br />
<br />
<pre>options snd-hda-intel model=3stack-dig</pre><br />
<br />
If your internal microphone doesn't work, you probably have to turn the capture feature on. Simply fire up alsamixer, find your Capture control, and press spacebar to enable it.<br />
<br />
====Webcam====<br />
<br />
You can enable your built-in webcam by adding the following line to your /etc/rc.local file.<br />
<br />
echo 1 > /proc/acpi/asus/camera<br />
<br />
If you want the webcam application that the default Xandos installation uses, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14469 ucview from the AUR].<br />
<br />
The webcam also works fine with the latest version of Skype.<br />
<br />
If you already have mplayer installed you can launch :<br />
mplayer -fps 15 tv://<br />
<br />
I have yet to get it working with vlc or any other software such as xawtv. If you know how, please update this.<br />
<br />
*'''NOTE:''' For anyone who has accidentally disabled Auto Exposure for their webcam in luvcview (making the image dark), and can't enable it again, do the following:<br />
<br />
Install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14468 libwebcam from the AUR].<br />
<br />
Issue the following command:<br />
<pre>uvcdynctrl --set "Exposure, Auto" 4</pre><br />
<br />
*'''NOTE:''' Be sure the "OS Installation" option is set to "finished" in the BIOS' "Advanced" tab or your camera may not work in some applications (like Skype).<br />
<br />
====Microphone====<br />
<br />
Solution for problems with the internal microphone.<br />
<br />
1. First of all set in alsamixer "Input Source" to "i-Mic"<br />
<br />
2. Increase "Capture" and "i-Mic Boost" to your needs<br />
<br />
3. Edit /etc/asound.state the following, change the 2 "false" to "true" like showing:<br />
<pre><br />
....snap.....<br />
control.11 {<br />
comment.access 'read write'<br />
comment.type BOOLEAN<br />
comment.count 2<br />
iface MIXER<br />
name 'Capture Switch'<br />
value.0 true<br />
value.1 true<br />
}<br />
....snap....</pre><br />
<br />
4. After editing run following as root<br />
<pre>alsactl restore</pre><br />
<br />
5. Now your internal microphone should be working.<br />
<br />
===Getting Hot Keys, Graphic Indicators and Shutdown with the Power Button Working===<br />
<br />
If you want to have working hot keys for changing brightness and volumes, graphic indicators working as well as shutdown when press the power button (just like in the stock Eee PC), then you should install '''ighea's acpi-eee''' or '''dkite's acpid_eee''' package.<br />
<br />
==== ighea's acpi-eee ====<br />
<br />
Get the latest package from [http://kapsi.fi/ighea/eee/acpi-eee/ here].<br />
<br />
The package can be easily installed with<br />
pacman -U acpi-eee-8-1-i686.pkg.tar.gz<br />
<br />
See messages during installation for more details and don't forget to edit /etc/acpi/eee.conf to suit your tastes.<br />
<br />
==== dkite's acpid_eee ====<br />
<br />
Package can also be download from his [http://members.shaw.ca/dkite/ website]<br />
<br />
The package itself can be install with<br />
<br />
pacman -Uf acpid_eee-0.0.3-1-i686.pkg.tar.gz.tar<br />
<br />
With '''both''' packages don't forget to start '''asusosd''' if you want to have the Graphic Indicators from Xandros.<br />
<br />
==Additional Tips & Tweaks==<br />
<br />
===kernel26eee tweaks===<br />
<br />
Toofishes's kernel, also known as kernel26eee, can be recompile to include custom features. You can download toofishes' kernel PKGBUILD and all the nesseary files from his gitweb by install git package and use the following command:<br />
<br />
git clone http://code.toofishes.net/gitprojects/eee.git<br />
<br />
There are two ways to tweak the kernal. The first is simply to edit the '''kernelconfig''' file with your favorite editor and the second is to insert a 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 compile 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 instruction, then change the following lines in 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 />
<br />
To this:<br />
<pre><br />
...<br />
230 CONFIG_NOHIGHMEM=y<br />
231 # CONFIG_HIGHMEM4G is not set<br />
232 # CONFIG_HIGHMEM64G is not set<br />
233 CONFIG_VMSPLIT_3G=y<br />
234 # CONFIG_VMSPLIT_3G_OPT is not set<br />
235 # CONFIG_VMSPLIT_2G is not set<br />
236 # CONFIG_VMSPLIT_2G_OPT is not set<br />
237 # CONFIG_VMSPLIT_1G is not set<br />
...<br />
</pre><br />
Compile and install the kernel and Wine should now works.<br />
<br />
===Power down with the power button===<br />
<br />
* '''NOTE:''' If you are using ighea's acpi-eee or dkite's acpid_eee package then you should already be able to shutdown by pressing the power button and should not need to do this.<br />
<br />
The two alternatives here are described in [[Allow_users_to_shutdown]].<br />
<br />
If you don't already or don't plan to use sudo, it may be simpler to use the setuid /sbin/halt method, otherwise using sudo is preferred.<br />
<br />
Below are all the steps required for the sudo method. If you want to use the setuid method, read the article linked above and perform the 'power' file step here, while omitting the 'sudo' in it.<br />
<br />
<pre>pacman -S sudo</pre><br />
<br />
As root, do the following:<br />
<br />
<pre>visudo</pre><br />
<br />
Add the following line to the file:<br />
<br />
<pre>USER HOST = NOPASSWD: /sbin/poweroff</pre><br />
<br />
Where USER = the user you want to be able to power down with and HOST = your hostname (from /etc/rc.conf).<br />
<br />
Now, create a file called /etc/acpi/events/power, containing:<br />
<br />
<pre># /etc/acpi/events/power<br />
# This is called when the user presses the power button<br />
<br />
event=button/power (PWR.||PBTN)<br />
action=sudo /sbin/poweroff</pre><br />
<br />
Make sure that you execute<br />
<br />
<pre>/etc/rc.d/acpid start</pre><br />
<br />
And/or add acpid to the daemons list in /etc/rc.conf:<br />
<br />
<pre>DAEMONS=(hal, acpid ...</pre><br />
<br />
===Use cpufreq for power saving===<br />
<br />
* '''NOTE:''' If you are using toofishes's kernel, then processor scaling is already enable and you don't need to do the following steps.<br />
<br />
Install cpufrequtitls.<br />
pacman -S cpufrequtils<br />
<br />
For scaling down the processor you have to load the p4_clockmod module. Insert it into your /etc/rc.conf MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
<br />
Add 'cpufreq' to the DAEMONS array in /etc/rc.conf to have it start on startup.<br />
DAEMONS=(... cpufreq ...)<br />
<br />
Add the following into /etc/conf.d/cpufreq<br />
governor="ondemand"<br />
min_freq="113MHz"<br />
max_freq="900MHz"<br />
<br />
With enabled cpufreq it scales the processor between 113MHz up to max. frequency. That should save a lot on battery power. The stated 900MHz will be never reached by the eeePC, the p4_clockmod reports a wrong frequency here. But scaling works, you can feel it in the performance of eeePC that he slow down the processor.<br />
<br />
===More responsive system with ondemand governor===<br />
The default up_threshold (where it will bump to a faster speed) for the CPU governor is 80, which means it will increase the CPU speed when utilization is above 80%. This can make X applications have a bit of lag. <br />
Try changing this value:<br />
sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
With 40 it still leaves the majority of CPU cycles at the lowest available clock speed but increases responsiveness. You can add this line to one of your startup scripts (such as /etc/rc.local) if you wish to keep it, for example:<br />
<pre><br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
<br />
echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold<br />
</pre><br />
<br />
Also, following line is also reported to help makes system more responsive. You can use it by adding it to your /etc/rc.local:<br />
<pre><br />
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate<br />
</pre><br />
<br />
===Speeding up udev for faster boot===<br />
* [[Speedup udev]]<br />
*http://dev.laptop.org/ticket/4349<br />
*[http://www.eeesale.com/Asus-Eee-PC-overclock-Benchmarks.htm Speed up the Eee PC]<br />
<br />
===Update your BIOS without Xandros===<br />
* '''Warning : you can break your system, do not update if you are not sure of what you are doing!'''<br />
<br />
First, you need to download the ''.rom'' file.<br />
*[http://update.eeepc.asus.com/bios/ Asus official's BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USBStick formated in fat32.<br />
To format an USBStick, use cfdisk tool :<br />
cfdisk /dev/sdc #could be something else than "c"<br />
Choose [delete], [type] : "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
cp /somewhere/blabla/.../thecurrentnameofthefile.rom /dev/sdc1/701.rom<br />
The name of the copy '''must''' be 701.rom<br />
<br />
Next step, reboot the eeepc with the USBStick pluged-in, and press<br />
Alt + F2<br />
It will launch the built-in tool. Everything should be Ok, you can make a coffee during the update. When it asks you to push the power-button it has finished.<br />
<br />
At the next boot, you'll be invited to configure the BIOS. Check if the everything is enable (my webcam and wireless were disable after the update) and if it displays the good version in the main screen. It's done !<br />
<br />
===More usuable font sizes===<br />
<br />
On a default installation with XFCE 4 my font sizes were too big, here is what I did to sort them out.<br />
<br />
First, I set the DPI by adding the following to ~/.Xdefaults:<br />
Xft*dpi: 134<br />
<br />
This then caused the fonts to be even bigger, so I set them all to be font-size 6 by adding the following into ~/.gtkrc-2.0 (note this will be overwritten if you use any tools to change GTK settings):<br />
style "user-font"<br />
{<br />
font_name="Bitstream Vera Sans 6"<br />
}<br />
widget_class "*" style "user-font"<br />
<br />
To do the same with KDE fonts (without KDE installed) you have to add the following to ~/.kde/share/config/kdeglobals:<br />
[General]<br />
StandardFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
activeFont=Bitstream Vera Sans,6,-1,5,75,0,0,0,0,0<br />
fixed=Bitstream Vera Sans Mono,6,-1,5,50,0,0,0,0,0<br />
font=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
menuFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
taskbarFont=Bitstream Vera Sans,6,-1,5,50,1,0,0,0,0<br />
toolBarFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
<br />
To make your fonts even prettier enable the [[Fonts#Fonts_with_LCD_filter_enabled|LCD Fonts]].<br />
<br />
===Using stock kernel===<br />
<br />
Some users might want to use the stock kernel. Since the stock kernel lacks most of the necessary modules for Eee, we need to install them manually. There are two way of doing this: compile and install everything from source or use dkite's eeemodules packages.<br />
<br />
====Install All the Necessary Modules using dkite's eeemodule package==== <br />
<br />
'''dkite''' have created a package that contains all the necessary modules for wifi, ethernet connection, acpi and video camera hardware that comes with the Eee PC. His package is to be use with the stock kernel. <br />
<br />
The following is the list of hardware/functions that are known to work with dkite's eeemodules Package:<br />
<br />
*Wireless <br />
*Ethernet <br />
*Webcam <br />
*Suspend/Resume<br />
<br />
You can get the package [http://members.shaw.ca/dkite from his website]. <br />
<br />
Currently there are three pre-complied package:<br />
<br />
#'''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' for use with Don't Panic kernel.<br />
#'''eeemodules-0.0.3-2.6.24.1.2-i686.pkg.tar.gz''' for the 2.6.24.14-2 kernel.<br />
<br />
If you have newer or other version of kernel26, then you will need to download '''eeemodules.tar.gz''', which contains PKGBUILD and all the necessary files, and build the package yourself. <br />
<br />
*'''ATTENTION:''' You will also need to rebuild the package, using eeemodules.tar.gz, every time you upgrade your kernel, or else your hardware (wifi, ethernet, etc.) will stop functioning.<br />
<br />
=====Installation Instructions=====<br />
<br />
Install the package with the following command:<br />
<br />
pacman -Uf eeemodules-<pkgver>.tar.gz<br />
<br />
Then run a depmod command:<br />
<br />
depmod<br />
<br />
* '''ATTENTION:''' Do ''not'' forget to run the depmod command after installing the package, otherwise your hardware won't function! <br />
<br />
Finally, edit /etc/rc.conf and add asus_acpi to the MODULES array:<br />
<br />
MODULES = (... asus_acpi ...) <br />
<br />
====Compile and Install All the Necessary Modules from Source====<br />
<br />
* '''NOTE:''' for anyone who read this wiki previously and wondered where the patched kernel download went; the latest arch kernel contains the patch that fixes the intel graphics vsync hardlock error, so no additional configuration need be done<br />
<br />
=====Install Network Adapter Drivers=====<br />
<br />
======Atl2 ethernet driver======<br />
<br />
* '''UPDATE:''' the atl2 ethernet is support by Arch Linux's stock kernel as of 2008.03<br />
<br />
You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
<br />
Extract the sources. You may need to modify the kernel version listed in the Makefile.<br />
<br />
make clean<br />
make<br />
cp atl2.ko /lib/modules/2.6.24-ARCH/kernel/drivers/net # Change 2.6.24 as needed<br />
depmod<br />
<br />
======Atheros wireless ethernet driver======<br />
<br />
Instructions from http://wiki.eeeuser.com/ubuntu#wireless_internet_using_native_madwifi_drivers to patch madwifi. This replaces the Arch madwifi packages.<br />
<br />
wget 'http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw'<br />
wget http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
==Known problems and their solutions==<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 />
Until toofishes update his kernel to include the patch, you can use ighea's slightly modified toofishes' kernel that included the above patch, as well as other modifications:<br />
<br />
*Support for Wine <br />
*uvesafb is built as module <br />
*Use [http://bbs.archlinux.org/viewtopic.php?pid=393860#p393860 new eeepc-laptop driver] (which also handles fan-control) instead of older acus_acpi or asus-laptop -drivers.<br />
<br />
You can get the modified kernel, as well as the associative packages, from [http://koti.kapsi.fi/~ighea/eee/kernel-eee/ here].<br />
<br />
After you have downloaded the packages, Install them using this command:<br />
<br />
pacman -U kernel-eee-2.6.26-1-i686.pkg.tar.gz madwifi-eee-svn-3752-1-i686.pkg.tar.gz <br />
<br />
You might also want to use IgnorePkg-line in /etc/pacman.conf to hold packages from being accidentally updated.<br />
<br />
IgnorePkg = kernel-eee madwifi-eee-svn<br />
<br />
Also don't forget to upgrade ighea's acpi-eee package to version 9.6.<br />
<br />
===Shutdown Problem===<br />
<br />
If your Eee won't shutdown properly (i.e. the power indicator LED is on but the LCD screen is off), then add the following lines to your /etc/rc.local.shutdown file.<br />
<pre><br />
#! /bin/bash<br />
#<br />
# /etc/rc.local.shutdown: Local shutdown script.<br />
#<br />
<br />
# Comment or uncomment the following two lines according to your system configuration.<br />
<br />
/etc/rc.d/mpd stop # If you're using mpd, then you have to stop its daemon first.<br />
<br />
/etc/rc.d/alsa stop # If you're using ALSA daemon, then you also have to stop it.<br />
<br />
# The following line is Eee specific fix, you always need to have this line in /etc/rc.local.shutdown.<br />
<br />
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind<br />
</pre><br />
The above solution should fix the shutdown problem in most cases. But if for some reason the problem still persists, the module may not be able to be unloaded until after all services have finished. Do the above, then in /etc/rc.shutdown move <br />
<br />
if [ -x /etc/rc.local.shutdown ]; then<br />
/etc/rc.local.shutdown<br />
fi<br />
<br />
from where it was to directly above the line <br />
<br />
# Terminate all processes<br />
<br />
this will cause the rc.local.shutdown script to run after services have been exited. This fixed all issues for the person editing this note.<br />
<br />
===Unclean unmount during shutdown when having home directory mounted on SD card===<br />
<br />
If you experienced unclean unmount during shutdown when having your home directory on SD card, then add the following 3 lines to "Write to wtmp file before unmounting" section of your /etc/rc.shutdown file:<br />
<pre><br />
...<br />
<br />
stat_busy "Unmounting Filesystems"<br />
/bin/umount -a -t noramfs,notmpfs,nosysfs,noproc<br />
<br />
# Add these 3 lines<br />
sync;sync;sync;<br />
eject /home<br />
sleep 3<br />
# End of hack<br />
<br />
stat_done<br />
<br />
...<br />
</pre><br />
<br />
===Booting from card without initrd===<br />
<br />
Let's say you decided to install Arch Linux on a card and compiled your own kernel (or used the kernel26eee kernel) without initrd. Card reader on EeePC is connected as an USB device. Unfortunately, USB storage devices are detected with a delay, so we must tell the kernel to wait until this device becomes available. You do this with "rootwait" option passed to kernel at boot time.<br />
<br />
===Sleeping and waking system on a card===<br />
<br />
If you have Arch Linux on a card, waking up from sleeping state will most likely fail. The only solution is to enable the CONFIG_USB_PERSIST option in kernel. The kernel26eee package should have this option enabled.<br />
<br />
===Display doesn't wake up properly===<br />
<br />
If you encounter black display (but apparently working system) after suspend/resume, consider using the "uswsusp" package (available in AUR) and correcting suspend2ram script in /etc/acpi, where you use this line to make the machine go to sleep:<br />
<br />
<pre>/usr/sbin/s2ram --force --vbe_post --vbe_mode</pre><br />
<br />
==Battery Tests==<br />
<br />
The following are reported battery runtimes:<br />
<br />
{| class="wikitable" style="text-align:left"<br />
|+Battery runtimes<br />
|-<br />
! Task !! Series !! Wireless !! Screen Brightness !! FSB Speed !! Fan Speed !! Runtime !! Comments<br />
|-<br />
! DVD Playback<br />
| 701 || On || Max || 85mhz || 100% || 134min || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! DVD Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading DVD ISO from 16gig SDHC Card<br />
|-<br />
! AVI Playback<br />
| 701 || Off || Max || 85mhz || 100% || ??? || Reading AVI from SSD<br />
|-<br />
! IM and Surf<br />
| 701 || On || ~30% || ??? || low || 173min || Normal web-browsing, Flash should reduce runtime a lot !<br />
|}<br />
<br />
N.B. - Will add battery runtimes as I am able to test them, please contribute.<br />
-- Grecko.1<br />
<br />
==Eee 901 20G lsmod and lspci==<br />
<br />
The following are from a stock ASUS EeePC 901 20G Linux version:<br />
<br />
lsmod:<br />
<pre><br />
Module Size Used by<br />
acpi_cpufreq 5004 0 <br />
freq_table 1988 1 acpi_cpufreq<br />
usb_storage 22980 0 <br />
libusual 6352 1 usb_storage<br />
pciehp 31172 0 <br />
pci_hotplug 9672 1 pciehp<br />
ehci_hcd 25420 0 <br />
uhci_hcd 18636 0 <br />
usbhid 13444 0 <br />
usbcore 91992 6 usb_storage,libusual,ehci_hcd,uhci_hcd,usbhid<br />
snd_pcm_oss 33568 0 <br />
snd_mixer_oss 13056 1 snd_pcm_oss<br />
rt2860sta 468248 1 <br />
atl1e 26388 0 <br />
fuse 34516 0 <br />
asus_acpi 6560 0 <br />
button 5648 0 <br />
processor 19820 1 acpi_cpufreq<br />
battery 7940 0 <br />
ac 3524 0 <br />
autofs4 15876 0 <br />
sr_mod 13284 0 <br />
cdrom 30624 1 sr_mod<br />
snd_hda_intel 284112 0 <br />
snd_pcm 50696 2 snd_pcm_oss,snd_hda_intel<br />
snd_timer 15556 1 snd_pcm<br />
snd_page_alloc 6728 2 snd_hda_intel,snd_pcm<br />
snd_hwdep 6084 1 snd_hda_intel<br />
snd 34852 6 snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep<br />
soundcore 3744 1 snd<br />
genrtc 6028 0<br />
</pre><br />
<br />
lspci:<br />
<pre><br />
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)<br />
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)<br />
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)<br />
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)<br />
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)<br />
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)<br />
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)<br />
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)<br />
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
01:00.0 Network controller: RaLink RT2790 Wireless 802.11n PCIe<br />
03:00.0 Ethernet controller: Atheros Corp. L1e Gigabit Ethernet Adapter (rev b0)<br />
</pre></div>
Faelar
https://wiki.archlinux.org/index.php?title=Openbox&diff=44915
Openbox
2008-07-10T18:04:41Z
<p>Faelar: /* Tips & Tricks */</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Openbox}}<br />
{{i18n_entry|Русский|Openbox (Русский)}}<br />
{{i18n_entry|Español|Openbox (Español)}}<br />
{{i18n_links_end}}<br />
<br />
= Introduction =<br />
<br />
Openbox is a lightweight and highly configurable window manager with extensive standards support. Its features are well-documented at the [http://icculus.org/openbox/ official website]. This article will pertain to running Openbox under Arch Linux.<br />
<br />
<br />
= Installation =<br />
Openbox is available from the standard repositories:<br />
# pacman -S openbox<br />
<br />
Once installed, pacman will direct you to copy the default <tt>menu.xml</tt> & <tt>rc.xml</tt> configuration files to <tt>~/.config/openbox/</tt>, for example:<br />
<br />
$ mkdir -p ~/.config/openbox/<br />
$ cp /etc/xdg/openbox/rc.xml ~/.config/openbox/rc.xml<br />
$ cp /etc/xdg/openbox/menu.xml ~/.config/openbox/menu.xml<br />
'''''Note:''' do this as a regular user, not as root.''<br />
<br />
<tt>rc.xml</tt> is the core configuration file for Openbox. It is used to manage keyboard shortcuts, themes, virtual desktops and other features.<br />
<br />
<tt>menu.xml</tt> controls the Openbox application menu that appears when you click on your desktop. The default items are pretty sparse, but it's very easy to modify the menu structure to suit your needs. See the menu section below for more details, or visit the [http://icculus.org/openbox/ Openbox website].<br />
<br />
= Getting Started =<br />
<br />
== Using Openbox ==<br />
To run Openbox on its own, simply add the following to the bottom of ~/.xinitrc:<br />
exec openbox-session<br />
<br />
== Using Openbox with GNOME ==<br />
# If you use GDM, select the "GNOME/Openbox" login option<br />
# If you use startx, add '''exec openbox-gnome-session''' to ~/.xinitrc<br />
# From the shell:<br />
xinit /usr/bin/openbox-gnome-session<br />
<br />
== Using Openbox with KDE ==<br />
# If you use KDM, select the "KDE/Openbox" login option<br />
# If you use startx, add '''exec openbox-kde-session''' to ~/.xinitrc<br />
# From the shell:<br />
xinit /usr/bin/openbox-kde-session<br />
<br />
== Using Openbox with Xfce4 ==<br />
Log into a normal Xfce4 session. From your terminal of choice, do:<br />
<br />
killall xfwm4 ; openbox & exit<br />
<br />
This will kill xfwm4, run Openbox, and close the terminal. <br />
<br />
Log out, making sure to check the "Save session for future logins" checkbox.<br />
<br />
On next login, Xfce4 will use Openbox as its WM.<br />
<br />
To be able to exit the session using xfce4-session, open your file ~/.config/openbox/menu.xml (if it isn't there, copy it from /etc/xdg/openbox/menu.xml). <br />
<br />
Look for the entry:<br />
<br />
<item label="Exit Openbox"><br />
<action name="Exit"><br />
<prompt>yes</prompt><br />
</action><br />
</item><br />
<br />
and change it to:<br />
<br />
<item label="Exit Openbox"><br />
<action name="Exit"><br />
<prompt>yes</prompt><br />
<command>xfce4-session-logout</command><br />
</action><br />
</item><br />
<br />
Otherwise, using the "Exit" entry of the root-menu will cause Openbox to terminate its execution, leaving you without a window manager.<br />
<br />
If you have an issue changing between virtual desktops with the mouse wheel skipping over virtual desktops, open your ~/.config/openbox/rc.xml file and move the mouse binds with actions "DesktopPrevious" and "DesktopNext" from the context "Desktop" to the context "Root" (you may need to define the Root context).<br />
<br />
If you want to use the Openbox root-menu instead of Xfce's, you may terminate Xfdesktop by running the following command in a terminal:<br />
<br />
xfdesktop --quit<br />
<br />
However, Xfdesktop manages the wallpaper and desktop icons, requiring you to use other utilities, such as ROX, for these functions.<br />
<br />
(When terminating Xfdesktop, the above issue with the virtual desktops is no longer a problem.)<br />
<br />
= Configuration =<br />
<br />
== Preferences ==<br />
Currently, there are two options for configuring the core Openbox preferences; manually edit the '''rc.xml''', or use the ObConf tool.<br />
<br />
=== Setting Preferences Manually ===<br />
<br />
To configure Openbox manually, simply edit '''~/.config/openbox/rc.xml''' with your favourite text editor. The config file provides plenty of comments throughout, and [http://icculus.org/openbox/index.php/Help:Contents full documentation] is available at the official website.<br />
<br />
=== Setting Preferences with ObConf ===<br />
<br />
[http://icculus.org/openbox/index.php/ObConf:About ObConf] is GUI-based Openbox configuration tool, which can be used to set most preferences including themes, virtual desktops, window properties and desktop margins.<br />
<br />
To install ObConf, run:<br />
# pacman -S obconf<br />
<br />
'''''Note:''''' ObConf cannot be used to configure keyboard shortcuts and some other advanced features. For these modifications, you must edit '''rc.xml''' manually (see above.)<br />
<br />
== Menu Management ==<br />
<br />
The default Openbox menu includes a variety of applications to get you started, but you'll probably want to customize this at some point. There are a number of ways to do so:<br />
<br />
=== Manually ===<br />
Similar to the '''rc.xml''' file, you can edit '''~/.config/openbox/menu.xml''' with your favourite text editor. Although many of the settings are self-explanatory, [http://icculus.org/openbox/index.php/Help:Menus full documentation] is available.<br />
<br />
=== MenuMaker ===<br />
[http://menumaker.sourceforge.net/ MenuMaker] is a powerful tool that creates XML-based menus for a variety of Window Managers, including Openbox. MenuMaker will search your computer for executable programs and create an XML menu based on the results. It can be configured to exclude Legacy X, GNOME, KDE, or Xfce applications if the user desires.<br />
<br />
MenuMaker is available from the [http://aur.archlinux.org/packages.php?ID=10894 AUR]. <br />
<br />
Once installed, you can generate a complete menu by running:<br />
$ mmaker -v OpenBox3<br />
<br />
By default, MenuMaker will not overwrite an existing menu.xml. To do so, run it with the -f (force) argument:<br />
<br />
$ mmaker -vf OpenBox3<br />
<br />
To see a full list of options, run '''mmaker --help'''<br />
<br />
This will give you a pretty thorough menu. Now you can modify the menu.xml by hand, or simply regenerate the list whenever you install new software.<br />
<br />
=== Obmenu ===<br />
Obmenu is a GUI-based menu editor for Openbox. For those who don't enjoy mucking about in XML source code, this is probably the best option for you.<br />
<br />
It is available in the community repository:<br />
# pacman -S obmenu<br />
<br />
Once installed, simply run '''obmenu''' and add or remove the desired applications.<br />
<br />
==== obm-xdg ====<br />
<tt>obm-xdg</tt> is a command-line tool that comes with Obmenu. It can generate a categorized sub-menu of installed GTK/GNOME applications.<br />
<br />
To use obm-xdg, add the following line to '''~/.config/openbox/menu.xml''':<br />
<br />
<menu execute="obm-xdg" id="xdg-menu" label="xdg"/><br />
<br />
Then run '''openbox --reconfigure''' to refresh the Openbox menu. You should now see a sub-menu labeled '''xdg''' in your menu.<br />
<br />
'''''NOTE:''' If you do not have GNOME installed, then you need to install '''gnome-menus''' package for obm-xdg to work.''<br />
<br />
== Startup Programs ==<br />
Openbox 3.4+ features support for running programs at startup. This is provided by the "openbox-session" command.<br />
<br />
There are two ways to enable autostart:<br />
# If you use startx to log into your X session, change the line that executes ''openbox'' to execute '''openbox-session''' instead.<br />
# If you log in with GDM/KDM, then select the ''Openbox'' session and it will automatically use autostart.<br />
<br />
Startup programs are managed in '''~/.config/openbox/autostart.sh'''. Full instructions and best practices for how to do this are available at the [http://icculus.org/openbox/index.php/Help:Autostart Openbox website].<br />
<br />
== Per-application settings ==<br />
Openbox 3.3+ features per-application settings, allowing you to define rules for your programs. For example, you can:<br />
* load your web browser on a certain desktop<br />
* load your terminal without a window border<br />
* load your torrent client at a certain position on your screen<br />
<br />
These are defined in '''~/.config/openbox/rc.xml'''. As you might expect, the instructions are well-documented within the file itself. Full details can also be found here: http://icculus.org/openbox/index.php/Help:Applications<br />
<br />
== Theming and Appearance ==<br />
Aside from the Openbox Themes, the following section is intended for users who have configured Openbox to run as a standalone desktop, without the assistance of GNOME or KDE.<br />
<br />
=== Openbox Themes ===<br />
Openbox themes control the appearance of window borders, including the titlebar and titlebar buttons. <br />
<br />
Additional themes are available from the standard repositories:<br />
<br />
# pacman -S openbox-themes<br />
<br />
This package is by no means definitive. [http://www.box-look.org/index.php?xcontentmode=7402 box-look.org] is another great resource for Openbox themes.<br />
<br />
Downloaded themes should be extracted to '''~/.themes''' and can be installed or selected with the [[Openbox#Preferences|ObConf]] tool.<br />
<br />
Creating new themes is fairly easy and again [http://icculus.org/openbox/index.php/Help:Themes well-documented].<br />
<br />
=== Desktop Wallpaper ===<br />
<br />
Openbox itself does not include a way to change the wallpaper. This can be done easily with programs like [[Feh]] or [[Nitrogen]]. Other options include ImageMagick, hsetroot and xsetbg.<br />
<br />
===KDE Themes===<br />
KDE apps can be themed and colored to closely match your GTK2 apps by invoking kcontrol, part of the '''kdeadmin''' package.<br />
<br />
=== GTK Themes ===<br />
===== GTK2/GTK+ =====<br />
GTK+ themes can be managed easily with the ''gtk-chtheme'' or ''switch2'' utilities. To install, run:<br />
# pacman -S gtk-chtheme<br />
and/or<br />
# pacman -S gtk-theme-switch2<br />
Then run '''gtk-chtheme''' or '''switch2''' and set the desired theme.<br />
<br />
===== GTK1 =====<br />
For legacy GTK1 themes, install the '''gtk-theme-switch''' package:<br />
# pacman -S gtk-theme-switch<br />
Then run '''''switch''''' to select a desired theme.<br />
<br />
=== GTK Fonts ===<br />
If you want to change the type and size of your fonts, add the following to '''~/.gtkrc.mine''':<br />
style "user-font"<br />
{<br />
font_name = "[font-name] [size]"<br />
}<br />
widget_class "*" style "user-font"<br />
gtk-font-name = "[font-name] [size]"<br />
<br />
where [font-name] [size] is the desired font and point size. For example:<br />
style "user-font"<br />
{<br />
font_name = "DejaVu Sans 8"<br />
}<br />
widget_class "*" style "user-font"<br />
gtk-font-name = "DejaVu Sans 8"<br />
<br />
Both <tt>font_name</tt> and <tt>gtk-font-name</tt> fields are required for backwards compatibility.<br />
<br />
=== GTK Icons ===<br />
Extract the desired icon theme to '''/usr/share/icons''' (system-wide access) or '''~/.icons''' (local user access).<br />
<br />
Add the following to ~/.gtkrc.mine: <br />
gtk-icon-theme-name = "[name-of-icon-theme]"<br />
<br />
where [name-of-icon-theme] is the name of the icon theme directory. For example:<br />
gtk-icon-theme-name = "Tango"<br />
<br />
Ensure ~/.gtkrc-2.0 is configured to parse ~/.gtkrc.mine:<br />
<br />
# ~/.gtkrc-2.0<br />
# -- THEME AUTO-WRITTEN DO NOT EDIT<br />
include "/usr/share/themes/Rezlooks-Gilouche/gtk-2.0/gtkrc"<br />
include "/home/username/.gtkrc.mine"<br />
# -- THEME AUTO-WRITTEN DO NOT EDIT<br />
<br />
=== Mouse cursor themes ===<br />
Extract the desired Xcursor theme to either '''/usr/share/icons''' (system-wide access) or '''~/.icons''' (local user access).<br />
<br />
Add this to ~/.Xdefaults:<br />
Xcursor.theme: [name-of-cursor-theme]<br />
where [name-of-cursor-theme] is the name of the cursor theme directory. For example:<br />
Xcursor.theme: Vanilla-DMZ-AA<br />
<br />
=== Desktop Icons ===<br />
Openbox does not provide a means to display icons on the desktop. PcmanFM, [http://rox.sourceforge.net ROX], [http://idesk.sourceforge.net iDesk], or even Nautilus (and the gnome-settings-daemon) can provide this function. <br />
<br />
ROX and PCmanFM have the additional advantage of being lightweight file managers.<br />
<br />
= Tips & Tricks =<br />
<br />
== Recommended Programs == <br />
<br />
=== Login Managers ===<br />
[http://slim.berlios.de/ SLiM] provides a lightweight and elegant graphical login solution for standalone Openbox configurations. Refer to Arch's [[SLiM]] wiki for detailed instructions.<br />
<br />
=== Composite Desktop ===<br />
[[Xcompmgr]] is a lightweight composite manager capable of rendering drop shadows, fading and simple window transparency within Openbox and other window managers.<br />
<br />
=== Application Launchers ===<br />
==== dmenu ====<br />
Set-up dmenu as described in the [[dmenu]] wiki article.<br />
<br />
Then, add the following entry to the <keyboard> section '''~/.config/openbox/rc.xml''' to enable a shortcut to launch dmenu:<br />
<keybind key="W-p"><br />
<action name="Execute"><br />
<command>~/path/to/your/dmenu-script</command><br />
</action><br />
</keybind><br />
<br />
==== Gmrun ====<br />
[http://sourceforge.net/projects/gmrun gmrun] provides an excellent Run dialog box, similar to the Alt+F2 features found in Gnome and KDE:<br />
pacman -S gmrun<br />
Add the following entry to the <keyboard> section '''~/.config/openbox/rc.xml''' to enable Alt+F2 functionality:<br />
<keybind key="A-F2"><br />
<action name="execute"><execute>gmrun</execute></action><br />
</keybind><br />
<br />
=== File managers ===<br />
<br />
There are many possibilities, but the most popular lightweight file managers are:<br />
* [http://thunar.xfce.org Thunar]. Thunar supports auto-mount features and other plugins. <br />
pacman -S thunar<br />
Thunar may be started in daemon mode for tighter desktop integration. For instance, inserting a USB pendrive will invoke a Thunar window to popup, with the drive contents listed in the window. <br />
<br />
To start Thunar in daemon mode, edit ~/.config/openbox/autostart.sh and add:<br />
thunar --daemon &<br />
<br />
* [http://rox.sourceforge.net ROX] (ROX provides desktop icons)<br />
pacman -S rox<br />
* [http://pcmanfm.sourceforge.net PCMan] (pcmanfm also provides desktop icons)<br />
pacman -S pcmanfm<br />
For even lighter options, consider [http://www.obsession.se/gentoo/ Gentoo] or [http://emelfm.sourceforge.net/ emelFM], both of which use the familiar 'Midnight Commander' two pane layout (these two require gtk 1.2.x).<br />
<br />
Of course, you can also use GNOME's Nautilus. Although slower than the above solutions, it has the additional advantage of VFS support (e.g. remote SSH, FTP and Samba connections).<br />
<br />
=== Panels, Trays, and Pagers ===<br />
<br />
There are quite a lot of utilities available that provide a panel (taskbar), system tray, and pager to Openbox. The most common are:<br />
<br />
'''Panels'''<br />
* [http://wiki.archlinux.org/index.php/PyPanel PyPanel]<br />
* [http://nsf.110mb.com/bmpanel/ bmpanel]<br />
* [http://code.google.com/p/ttm/ Tint]<br />
* [http://sourceforge.net/projects/lxpanel LXPanel]<br />
* [http://fbpanel.sourceforge.net fbpanel]<br />
* [http://perlpanel.org/ PerlPanel]<br />
* [http://www.chatjunkies.org/fspanel/ fspanel]<br />
* [http://www.xfce.org/projects/xfce4-panel/ xfce4-panel]<br />
* [http://developer.gnome.org/arch/gnome/corecomponents/panel/ gnome-panel]<br />
* [http://code.google.com/p/avant-window-navigator/ avant-window-navigator]<br />
* [http://developer.berlios.de/projects/cairo-dock/ cairo-dock]<br />
<br />
'''Trays'''<br />
* [http://stalonetray.sourceforge.net/ Stalonetray]<br />
* [http://download.gna.org/fvwm-crystal/trayer/1.0/ Trayer]<br />
<br />
'''Pagers'''<br />
* [http://projects.l3ib.org/trac/visibility Visibility]<br />
* [http://bbtools.sourceforge.net/ bbpager]<br />
* [http://aur.archlinux.org/packages.php?ID=970 netwmpager]<br />
* [http://useperl.ru/ipager/index.en.html IPager]<br />
<br />
Make your choice and add it to your startup file.<br />
<br />
== Get xprop values for per-app settings quickly ==<br />
If you use per-application settings frequently, you might find this bash alias handy:<br />
<br />
alias xp='xprop | grep "WM_WINDOW_ROLE\|WM_CLASS" && echo "WM_CLASS(STRING) = \"NAME\", \"CLASS\""'<br />
<br />
To use, run '''xp''' and click on the running program that you'd like to define with per-app settings. The result will display only the info that Openbox requires, namely the WM_WINDOW_ROLE and WM_CLASS (name and class) values:<br />
<br />
[thayer@dublin:~] $ xp<br />
WM_WINDOW_ROLE(STRING) = "roster"<br />
WM_CLASS(STRING) = "gajim.py", "Gajim.py"<br />
WM_CLASS(STRING) = "NAME", "CLASS"<br />
<br />
== Linking the menu to a command ==<br />
Some people would want to link the Openbox main menu, or any other, to a command. This is useful for creating a menu button in a panel, for example. Although Openbox doesn't support this, a very simple script , xdotool, can simulate a keypress by running a command. Xdotool is available on AUR [http://aur.archlinux.org/packages.php?do_Details=1&ID=14789&O=0&L=0&C=0&K=xdotool&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd here]. To use it, simply add the following code to the <keyboard> section of your rc.xml:<br />
<keybind key="A-C-q"><br />
<action name="ShowMenu"><br />
<menu>root-menu</menu><br />
</action><br />
</keybind><br />
Restart/reconfigure Openbox. You can now magically summon your menu at your cursor position by running the following command:<br />
# xdotool key ctrl+alt+q<br />
Of course, you can change the shortcut to your liking.<br />
<br />
== Urxvt in the background == <br />
With Openbox, running a terminal as desktop background is easy. You won't need '''devilspie''' here.<br />
<br />
First you must enable transparency, open your '''.Xdefaults''' file (if it doesn't exist yet, create it in your home folder).<br />
URxvt*transparent:true<br />
URxvt*scrollBar:false<br />
URxvt*geometry:124x24 #I don't use the whole screen, if you want a full screen term don't bother with this and see below.<br />
URxvt*borderLess:true<br />
URxvt*foreground:Black #Font color. My wallpaper is White, you may wish to change this to White.<br />
<br />
Then edit your '''.config/openbox/rc.xml''' file :<br />
<application name="urxvt"><br />
<decor>no</decor><br />
<focus>yes</focus><br />
<position><br />
<x>center</x><br />
<y>20</y><br />
</position><br />
<layer>below</layer><br />
<desktop>all</desktop><br />
<maximized>true</maximized> #Only if you want a full size terminal.<br />
</application><br />
<br />
The ''magic'' comes from the '''<layer>below</layer>''' line, which place the application under all others. Here Urxvt is displayed on all desktops, change it to your convenience.<br />
<br />
= Additional Resources =<br />
* [http://icculus.org/openbox/ Openbox Website] - The official website<br />
* [http://planetob.openmonkey.com/ Planet Openbox] - Openbox news portal<br />
* [http://www.box-look.org/ Box-Look.org] - A good resource for themes and related artwork<br />
* [http://archux.com/page/application-recommendations Application recommendations]</div>
Faelar
https://wiki.archlinux.org/index.php?title=Newcomers_Guide&diff=44402
Newcomers Guide
2008-07-07T16:40:12Z
<p>Faelar: French i18n link added</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:About Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|Dansk|Dansk_Begynderguide}}<br />
{{i18n_entry|简体中文|Beginners Guide 新手指南}}<br />
{{i18n_entry|Deutsch|Beginners Guide (Deutsch)}}<br />
{{i18n_entry|English|Beginners Guide}}<br />
{{i18n_entry|Español|Guía Para Principiantes}}<br />
{{i18n_entry|Français|Manuel_du_Débutant_(Français)}}<br />
{{i18n_entry|Česky|Průvodce začátečníka (Česky)}}<br />
{{i18n_entry|Italiano|Beginners Guide (Italiano)}}<br />
{{i18n_entry|Lietuviškai|Pradedančiųjų gidas (Lietuviškai)}}<br />
{{i18n_entry|Português Brasil|Guia do Iniciante(Português do Brasil)}}<br />
{{i18n_entry|Türkçe|Beginners Guide (Türkçe)}}<br />
{{i18n_links_end}}<br />
==Preface==<br />
<br />
=====Everything you ever wanted to know about installing Arch, but were afraid to ask=====<br />
Welcome. This document will guide you through the process of installing and configuring [[ArchLinux|Arch Linux]]; a simple, agile and lightweight GNU/Linux distribution, <code>UNIX</code>-like operating system. Arch Linux requires a certain level of intimate knowledge of its configuration and of <code>UNIX</code>-like system methodology and for this reason, extra explanatory information is included. It is aimed at new Arch users, but strives to serve as a strong reference and informative base for all. <br />
<br />
Since GNU/Linux Distributions are fundamentally 'modular' by design, the article is logically divided into 3 main components of a desktop <code>UNIX</code>-like operating system:<br />
<br />
'''[[#Part I: Install the Base System|Part I: Installing the Base system]]'''<br />
<br />
'''[[#Part II: Install X and configure ALSA|Part II: Installing X and configuring ALSA]]'''<br />
<br />
'''[[#Part III: Installing and configuring a Desktop Environment|Part III: Installing a Desktop Environment]]'''<br />
<br />
=====DON'T PANIC!=====<br />
The Arch Linux system is assembled by the ''user'', from the shell, using basic command line tools. This is '''[[The Arch Way]].''' Unlike the more rigid structures of other distributions and installers, there are no default environments nor configurations chosen for you. From the command line, ''you'' will add packages from the Arch repositories using the [[pacman]] tool via your internet connection and manually configure your installation until your system is customized to your requirements. This method allows for maximum flexibility, choice, and system resource control ''from the base up''.<br />
<br />
Arch Linux is aimed at GNU/Linux users who desire minimal 'code separation' from their machine.<br />
<br />
=====[[The Arch Way]]=====<br />
<br />
'''''The design principles behind Arch are aimed at keeping it [[The Arch Way|simple]].'' '''<br />
<br />
'Simple', in this context, shall mean 'without unnecessary additions, modifications, or complications'. In short; an elegant, minimalist approach.<br />
<br />
'''Some thoughts to keep in mind:'''<br />
<br />
*''" 'Simple' is defined from a technical standpoint, not a usability standpoint. It is better to be technically elegant with a higher learning curve, than to be easy to use and technically [inferior]." -Aaron Griffin''<br />
<br />
*''Entia non sunt multiplicanda praeter necessitatem'' or "Entities should not be multiplied unnecessarily." -Occam's razor. The term ''razor'' refers to the act of shaving away unnecessary complications to arrive at the simplest explanation, method or theory.<br />
<br />
*''"The extraordinary part of [my method] lies in its simplicity..I always believe that the simple way is the right way."'' - Bruce Lee<br />
<br />
{{Box Note |'''Following this guide closely is essential in order to successfully install a properly configured Arch Linux system, so ''please'' read it thoroughly.'''}}<br />
* You may wish to make a print out of this guide which will serve as a useful Arch Linux user reference. <br />
*''If you would like to add to this wiki, please include the "Why" as well as the "How", where appropriate. The best documentation teaches us how, as well as why!''<br />
* The Arch wiki is an excellent resource and should be consulted for issues [http://wiki.archlinux.org/index.php/Main_Page first]; IRC (freenode #archlinux), and the [http://bbs.archlinux.org/ forums] are also available if the answer cannot be found.<br />
----<br />
Welcome to Arch! Now, let's get started.<br />
<br />
==Part I: Install the Base System==<br />
<br />
===Obtain the latest Installation media ===<br />
<br />
You can obtain Arch's latest installation media from [http://archlinux.org/download/ here].<br />
<br />
*Both the Core installer and the FTP/HTTP-downloads provide only the necessary packages to create an '''Arch Linux base system'''. ''Note that the Base System does not include a GUI. It is mainly comprised of the GNU toolchain, (compiler, assembler, linker, libraries, shell, and a few useful utilities) the Linux kernel, and a few extra libraries and modules.'' <br />
*Expanding your Arch Linux system beyond the base system, to include extra software, a Graphical User Interface, etc., is achieved from the command line, ''by the user'', via the pacman package manager to grab i686/x86-64 binary packages. The process is covered in detail below.<br />
====CD installer====<br />
Burn the .iso to a CD with your favorite burner, and continue with [[#Boot Arch Linux Installer | Boot Arch Linux Installer]]<br />
{{Box Note| Generally, using a maximum speed of no more than 8x is recommended for reliable burns, and some users recommend speeds '''''as low as 4x or 2x!''''' If you are experiencing unexpected behavior from the CD, try burning at the minimum speed supported by your system.}}<br />
<br />
====USB stick====<br />
Insert an empty or expendable USB stick, determine its path, and dd the .img to the USB stick like so:<br />
dd if=archlinux-2008.06-[core_or_ftp]-i686.img of=/dev/sd''x''<br />
where ''if='' is the path to the img file and ''of='' is your USB device. Make sure to use /dev/sdx and not /dev/sdx1.<br />
<br />
'''Note:''' ''This will destroy all data on your USB stick.''<br />
<br />
Continue with [[#Boot Arch Linux Installer | Boot Arch Linux Installer]]<br />
<br />
===Boot Arch Linux Installer===<br />
As you follow these directions, you may find the [[Official Arch Linux Install Guide]] helpful as well. <br />
<br />
Insert the CD or USB stick and boot from it. You may have to <br />
change the boot order in your computer BIOS or press a key (usually DEL, F1, F2, F11 or F12) during the BIOS POST phase.<br />
<br />
Memory requirements:<br />
<br />
* CORE : 160 MB RAM x86_64/i686 (all packages selected, with swap partition)<br />
* FTP : 160 MB RAM x86_64/i686 (all packages selected, with swap partition)<br />
<br />
Choose Boot Archlive or Boot Archlive [legacy IDE] if you have trouble with libata/PATA. <br />
<br />
To change boot options press '''e''' for editing the boot lines. Many users may wish to change the resolution of the framebuffer, for more readable console output. Append:<br />
vga=773<br />
to the kernel line, followed by <ENTER>, for a 1024x768 framebuffer. Hit '''b''' to boot.<br />
<br />
The system will now boot and present a login prompt.<br />
<br />
===Login and Changing the keymap===<br />
Login as 'root'. If you have a non-US keyboard layout do:<br />
km<br />
at the prompt, and choose your keymap/console font.<br />
<br />
That's right, the ever-popular '''km''' program is back as of 2008-06!<br />
<br />
===Documentation===<br />
The guide you are now reading is available on the live system. Change to vc/2 with <ALT>-F2 and do:<br />
less /arch/beginnersguide.txt<br />
'''Less''' will allow you to page through the document. Change back to vc/1 with <ALT>-F1. <br />
<br />
Change back to vc/2 if you need to reference the Beginner's Guide at any time.<br />
<br />
===Start the Installation===<br />
As root, run the installer script from vc/1:<br />
/arch/setup <br />
<br />
====Select an installation source====<br />
After a welcome screen, you will be prompted for an installation source. Choose the appropriate source for the installer you are using. <br />
* If you chose the CORE installer, continue below with [[#Prepare Hard Drive|Prepare Hard Drive]].<br />
* FTP/HTTP only: You shall be prompted to load ethernet drivers manually, if desired. Udev is quite effective at loading the required modules, so you may assume it has already done so. You may verify this by invoking ifconfig -a from vc/3. (Select OK to continue.)<br />
<br />
===Configure Network (FTP/HTTP)===<br />
Available Interfaces will be presented. If an interface and HWaddr is listed, then your module has already been loaded. If your interface is not listed, you may probe it from the installer, or manually do so from another virtual console.<br />
<br />
The following screen will prompt you to ''Select the interface, Probe,'' or ''Cancel''. Choose the appropriate interface and continue.<br />
<br />
The installer will then ask if you wish to use DHCP. Choosing Yes will run '''dhcpcd''' to discover an available gateway and request an IP address; Choosing No will prompt you for your static IP, netmask, broadcast, gateway DNS IP, HTTP proxy, and FTP proxy. Lastly, you will be presented with an overview to ensure your entries are correct.<br />
<br />
====Wireless Quickstart (If you need wireless connectivity during the installation process)====<br />
<br />
The wireless drivers and utilities are now available to you in the live environment of the installation media. <br />
<br />
If you need wireless functionality from the initial installation (live installer environment) onwards, the basic procedure will be:<br />
* Switch to a free virtual console, e.g.: <ALT>+F3<br />
* Identify your wireless card and appropriate module:<br />
hwdetect --show-net<br />
* Ensure udev has loaded the module:<br />
lsmod | grep <name_of_module><br />
* If not, probe it:<br />
modprobe <name_of_module><br />
* Ensure the driver has created a usable wireless kernel interface:<br />
iwconfig<br />
(Output should show an available wireless interface)<br />
* Bring the interface up with <code>ifconfig <interface> up</code>. <br />
<br />
An example, using an atheros card and madwifi driver:<br />
ifconfig ath0 up<br />
(Remember, your interface may be named something else, depending on your module (driver) and chipset: wlan0, eth1, etc.)<br />
* Specify the id of the wireless network with iwconfig <interface> essid <youressid> key <yourwepkey>, e.g.:<br />
iwconfig ath0 essid linksys key 0241baf34c<br />
* Acquire an IP address with dhcpcd <interface>. e.g.:<br />
dhcpcd ath0<br />
* Ensure you can route:<br />
ping -c 3 www.google.com<br />
Done.<br />
<br />
After the initial Arch installation is complete, you may wish to refer to [[Wireless Setup]] to ensure a permanent configuration solution for your system.<br />
<br />
<br />
Return to vc/1 with <ALT>+F1. Continue with [[#Prepare Hard Drive|Prepare Hard Drive]]<br />
<br />
===Prepare Hard Drive===<br />
Select the first menu entry "Prepare Hard Drive". <br />
* Option 1: Auto Prepare<br />
Auto-Prepare divides your disk into the following configuration:<br />
<br />
* ext2 /boot partition, default size 32MB. ''You will be prompted to modify the size to you requirement.''<br />
* swap partition, default size 256MB. ''You will be prompted to modify the size to you requirement.'' <br />
* A Separate / and /home partition, (sizes can also be specified). You may choose from ext2, ext3, reiserfs, xfs and jfs, but note that ''both / and /home must share the same fs type'' if choosing the Auto Prepare option.<br />
<br />
Be warned that Auto-prepare will completely erase the chosen hard drive. Read the warning presented by the installer very carefully, and make sure the correct device is about to be partitioned.<br />
<br />
* Option 2: '''(Recommended)''' Partition Hard Drives (with cfdisk)<br />
<br />
This option will allow for the most robust and customized partitioning solution for your personal needs. <br />
<br />
''At this point, more advanced GNU/Linux users who are familiar and comfortable with manually partitioning may wish to skip down to '''[[#Select Packages|Select Packages]]''' below.''<br />
<br />
====Partition Hard Drives====<br />
<br />
=====Partition Info=====<br />
<br />
Partitioning a hard disk drive defines specific areas (the partitions) within the disk, that will each appear and behave as a separate disk and upon which a filesystem may be created (formatted). There exist 3 types of disk partitions: '''Primary, Extended, and Logical.''' <br />
<br />
'''Primary''' partitions can be bootable, and are limited to 4. If a partitioning scheme requires more than 4 partitions, we are forced to use an '''extended''' partition which will contain '''logical''' partitions.<br />
<br />
Extended partitions are not usable by themselves; they are merely a "container" for logical partitions. If required, a hard disk shall contain only one extended partition; which shall then be sub-divided into logical partitions. <br />
<br />
When partitioning a disk, one can observe this numbering scheme by creating primary partitions sda1-3 followed by creating an extended partition, sda4, and subsequently creating logical partition(s) within the extended partition; sda5, sda6, and so on.<br />
<br />
=====Swap Partition=====<br />
A swap partition is a place on your hard drive where virtual ram resides, allowing the kernel to easily use disk storage for data that does not fit into physical RAM. <br />
<br />
Historically, the general rule for swap partition size was 2x the amount of physical RAM. Over time, as computers have gained ever larger memory capacities, this rule has become increasingly deprecated. Generally, on machines with up to 512MB RAM, the 2x rule is usually quite sufficient. On machines with 1GB RAM, generally a 1x rule is adequate. If you have gratuitous amounts of RAM (more than 1024 MB) it may be possible to completely forgo a swap partition altogether, though this is not recommended. We will create a 1 GB swap partition in this example.<br />
{{Box Note|If you plan on using suspend-to-disk, (hibernate) you must have a swap partition at least '''equal''' in size to the amount of physical RAM, and some Arch users even recommend oversizing it beyond the amount of physical RAM by 10-15%, to allow for possible bad sectors.}}<br />
<br />
=====Partition Scheme=====<br />
A disk partitioning scheme is a very personalized preference. Each user's choices will be unique to their own computing habits and requirements. Filesystem candidates for separate partitions include:<br />
<br />
'''/''' (root) ''The root filesystem is the primary filesystem from which all other filesystems stem; the top of the hierarchy. All files and directories appear under the root directory "/", even if they are stored on different physical devices. The contents of the root filesystem must be adequate to boot, restore, recover, and/or repair the system.'' <br />
<br />
'''/boot''' ''This directory contains the kernel and ramdisk images as well as the bootloader configuration file, and bootloader stages. /boot also stores data that is used before the kernel begins executing user-mode programs. This may include saved master boot sectors and sector map files.''<br />
<br />
'''/home''' ''User data and user specific configuration files for applications are stored in each user's home directory in a file that starts with the '.' character (a "dot file").''<br />
<br />
'''/usr''' ''While root is the primary filesystem, /usr is the secondary hierarchy, for user data, containing the majority of (multi-)user utilities and applications. /usr is shareable, read-only data. This means that /usr shall be shareable between various hosts and must not be written to, except in the case of system update/upgrade. Any information that is host-specific or varies with time is stored elsewhere.''<br />
<br />
'''/tmp''' ''directory for programs that require temporary files''<br />
<br />
'''/var''' ''contains variable data; spool directories and files, administrative and logging data, pacman's cache, the ABS tree, etc.''<br />
*It is generally considered good practice and more versatile to at least have / and /home on separate partitions. <br />
*Having separate partitions for ''all'' of the above listed directories may be the most appropriate choice for those who are vigilant about control, stability, integrity and security.<br />
<br />
In this example, we shall use one partition for /, one partition for /home, and a swap partition.<br />
<br />
{{Box Note | /var contains many small files. You may wish to take this into consideration when choosing a filesystem type for it.}}<br />
<br />
=====cfdisk=====<br />
Start by creating the primary partition that will contain the '''root''', (/) filesystem. <br />
<br />
Choose '''N'''ew -> Primary and enter the size you want (something between 4 and 12 GB is a good choice for a full-featured Linux system). Put the partition at the beginning of the disk. <br />
<br />
Also choose the '''T'''ype by designating it as '83 Linux'. The created / partition should appear as sda1.<br />
<br />
Next, create a partition for swap. Select an appropriate size and specify the '''T'''ype as 82 (Linux swap / Solaris). The created swap partition should appear as sda2.<br />
<br />
Lastly, create another partition for your /home directory. Choose another primary partition and set the desired size.<br />
<br />
Likewise, select the '''T'''ype as 83 Linux. The created /home partition should appear as sda3.<br />
<br />
Example:<br />
<br />
Name Flags Part Type FS Type [Label] Size (MB)<br />
-------------------------------------------------------------------------<br />
sda1 Primary Linux 10240 #root<br />
sda2 Primary Linux swap / Solaris 1024 #swap<br />
sda3 Primary Linux 26480 #home<br />
<br />
Choose '''W'''rite and type ''''yes''''. Beware that this operation may destroy data on your disk. Choose '''Q'''uit to leave the partitioner. <br />
Choose Done to leave this menu and continue with "Set Filesystem Mountpoints".<br />
<br />
{{Box Note | Since the latest developments of the Linux kernel which include the libata and PATA modules, all IDE, SATA and SCSI drives have adopted the sd''x'' naming scheme. This is perfectly normal and should not be a concern.}}<br />
<br />
====Set Filesystem Mountpoints====<br />
First you will be asked for your swap partition. Choose the appropriate partition (sda2 in this example). You will be asked if you want to create a swap filesystem; select yes. Next, choose where to mount the / (root) directory (sda1 in the example). You will be asked what kind of filesystem you want.<br />
<br />
=====Filesystem Types=====<br />
<br />
Again, a filesystem type is a very subjective matter which comes down to personal preference. Each one has its own advantages and disadvantages, and differences in performance are often more likely to be attributable to placebo than to human-perceivable measurements. Here is a very brief overview of supported filesystems:<br />
<br />
1. '''ext2''' ''Second Extended Filesystem''- Old, reliable GNU/Linux filesystem. Very stable, but ''without journaling support''. May be inconvenient for root (/) and /home, due to very long fsck's. ''An ext2 filesystem can easily be converted to ext3.''<br />
<br />
2. '''ext3''' ''Third Extended Filesystem''- Essentially the ext2 system, but with journaling support. ext3 is completely compatible with ext2. ''Extremely'' stable, mature, and by far the most widely used, supported and developed GNU/Linux FS.<br />
<br />
'''High Performance Filesystems:'''<br />
<br />
3. '''ReiserFS''' - Hans Reiser's high-performance journaling FS uses a very interesting method of data throughput. ReiserFS is touted as very fast, especially when dealing with many small files. ReiserFS is fast at formatting, yet comparatively slow at mounting. Quite mature and stable. ReiserFS is not actively developed at this time (Reiser4 is the new Reiser filesystem).<br />
<br />
4. '''JFS''' - IBM's '''J'''ournaled '''F'''ile'''S'''ystem- the first filesystem to offer journaling has had many years of use in the IBM AIX® OS before being ported to Linux. JFS currently uses the least CPU resources of any Linux filesystem. Very fast at formatting, mounting and fsck's, and very good all-around performance, especially in conjunction with the deadline I/O scheduler. (See [[JFS]].) Not as widely supported as ext or ReiserFS, but very mature and stable.<br />
<br />
5. '''XFS''' - Another early journaling filesystem originally developed by Silicon Graphics for the IRIX OS and ported to Linux. XFS is best suited for very fast throughput on large files. Very fast at formatting and mounting. Generally benchmarked as slower with many small files, in comparison to other filesystems. XFS is very mature and is currently the only available stable Linux FS with online defragmentation ability.<br />
<br />
===== A note on Journaling=====<br />
All above filesystems, except ext2, utilize [http://en.wikipedia.org/wiki/Journaling_file_system journaling]. Journaling file systems are fault-resilient file systems that use a journal to log changes before they're committed to the file system to avoid metadata corruption in the event of a crash. Note that not all journaling techniques are alike; specifically, only ext3 offers ''data-mode journaling'', (though, not by default), which journals ''both'' data ''and'' meta-data (but with significant speed penalty). The others only offer ''ordered-mode journaling'', which journals meta-data only. While all will return your filesystem to a valid state after recovering from a crash, ''data-mode journaling'' offers the greatest protection against file system corruption and data loss but can suffer from performance degradation, as all data is written twice (first to the journal, then to the disk). Depending on how important your data is, this may be a consideration in choosing your filesystem type.<br />
<br />
Choose and create the filesystem (format the partition) for / by selecting '''yes'''. You will now be prompted to add any additional partitions. In our example, only sda3 is remaining. Choose a filesystem type and mount it as /home. Again, create the filesystem and choose Done. Return to main menu.<br />
<br />
===Select Packages===<br />
<br />
*Core ISO: Choose CD as source and select the appropriate CD drive if you have more than one.<br />
*FTP ISO: Select an FTP/HTTP mirror. ''Note that archlinux.org is throttled to 50KB/s''.<br />
<br />
Package selection is split into two stages. First, you will select package categories, then you will be presented will the full lists of packages in the selected categories, allowing you to fine-tune your selections. The space bar selects and unselects the categories.<br />
<br />
*'''BASE:''' Contains the minimal GNU/Linux package set; just enough for a barebones environment; The linux kernel, GNU, fsprogs, bootloader, editor, bash, etc.<br />
*'''SUPPORT:''' Additional convenience packages for networking and filesystems, etc; gpm, fuse, dnsutils, wireless drivers, ndiswrapper, ntfs-3g, and so forth.<br />
*'''DEVEL:''' Critical software compiling tools such as GCC, autoconf, automake and make.<br />
*'''LIB:''' A thimbleful of various extra libraries such as gmp, lebelf, libevent, etc. <br />
<br />
Choose OK to continue and then choose 'yes' for 'Select all packages by default', for now.<br />
<br />
The next screen will present you with the selected packages within your selected categories. Leaving all selected is a safe choice for beginners, while more experienced users will wish to trim a few unnecessary packages. (For instance, an unneeded filesystem type utility, unneeded drivers, etc.)<br />
<br />
===Install Packages===<br />
Next, choose 'Install Packages'. You will be asked if you wish to keep the packages in the pacman cache. If you choose 'yes', you will have the flexibility to [[Downgrade packages|downgrade]] to previous package versions in the future, so this is recommended (you can always clear the cache in the future). The installer script will now install the selected packages, as well as the default Arch 2.6 kernel, to your system. <br />
*FTP ISO: The [[Pacman]] package manager will now download and install your selected packages. (See vc/5 for output, vc/1 to return to the installer)<br />
*CORE ISO: The packages will be installed from the CD.<br />
<br />
Note: For Arch 2007.08 FTP installation: after 'Install Packages' you have to upgrade pacman (<ALT>+F3, pacman -Sy pacman) and again 'Install Packages'.<br />
<br />
===Configure the System===<br />
''Closely following and understanding these steps is of key importance to ensure a properly configured system.'' <br />
<br />
The installer will ask if you want to choose [[Hwdetect|hwdetect]] to gather information for your configuration. Beginners should choose 'yes'. <br />
<br />
Advanced users who are thoroughly familiar with their hardware, required modules, and who are able to manually configure /etc/rc.conf, /etc/mkinitcpio and /etc/fstab, etc. from scratch may wish to choose 'no'. (Needless to say, this option is very involved, beyond the scope of this guide, and therefore is not covered.)<br />
<br />
Next, you will be asked if you need support for booting from USB devices, FireWire devices, PCMCIA devices, NFS shares, software RAID arrays, LVM2 volumes, encrypted volumes, and DSDT support. Choose yes if you need it; in our example nothing is needed. <br />
<br />
Now you will be asked which text editor you want to use; choose [http://en.wikipedia.org/wiki/Nano_%28text_editor%29 nano] or [http://en.wikipedia.org/wiki/Vim_%28text_editor%29 vim] (recommended). You will be presented with a menu including the main configuration files for your system. <br />
=====Can the installer handle this more automatically?=====<br />
Hiding the process of system configuration is in direct opposition to [[The Arch Way]]. While it is true that recent versions of the kernel and hardware probing tools offer excellent hardware support and auto-configuration, Arch presents the user all pertinent configuration files during installation for the purpose of ''transparency''. By the time you have finished modifying these files to your specifications, you will have learned the simple method of manual Arch Linux system configuration and become more familiar with the base structure, leaving you better prepared to use your new installation productively.<br />
<br />
====='''/etc/rc.conf'''=====<br />
Arch Linux follows in the '''*BSD''' tradition of utilizing '''/etc/rc.conf''' as the principal location for system configuration. This one file contains a wide range of configuration information, principally used at system startup. As its name directly implies, it also contains settings for and invokes the /etc/rc* files, and is, of course, sourced ''by'' these files. /etc/rc.conf offers a simple, elegant method of streamlining system resource configuration by encompassing a wide range of control, readily accessible for the Arch user. <br />
* '''LOCALIZATION''' section<br />
** '''LOCALE'''=: This sets your system locale, which will be used by all i18n-aware applications and utilities. You can get a list of the available locales by running 'locale -a' from the command line. This setting's default is fine for US English users. <br />
** '''HARDWARECLOCK'''=: Specifies whether the hardware clock, which is synchronized on bootup and on shutdown, stores '''UTC''' time, or the '''localtime'''. UTC makes sense because it greatly simplifies changing timezones and daylight savings time. localtime is necessary if you dual boot with an operating system such as Windows, that only stores localtime to the hardware clock.<br />
** '''TIMEZONE'''=: Specify your TIMEZONE. (All available zones are under /usr/share/zoneinfo/).<br />
** '''KEYMAP'''=: The available keymaps are in /usr/share/kbd/keymaps. Please note that this setting is only valid for your TTYs, not any graphical window managers or X!<br />
** '''CONSOLEFONT'''=: Available console fonts reside under /usr/share/kbd/consolefonts/ if you must change. The default (blank) is safe.<br />
** '''CONSOLEMAP'''=: Defines the console map to load with the setfont program on bootup. Possible maps are found in /usr/share/kbd/consoletrans, if needed. The default (blank) is safe. <br />
** '''USECOLOR'''=: Select "yes" if you have a color monitor and wish to have colors in your consoles.<br />
<br />
LOCALE="en_US.utf8"<br />
HARDWARECLOCK="localtime"<br />
TIMEZONE="US/Eastern"<br />
KEYMAP="us"<br />
CONSOLEFONT=<br />
CONSOLEMAP=<br />
USECOLOR="yes"<br />
* '''HARDWARE''' section<br />
** '''MOD_AUTOLOAD'''=: Setting this to "yes" will utilize '''udev''' to automatically probe hardware and load the appropriate modules during boot-up, (convenient with the default modular kernel). Setting this to "no" will rely on the user's ability to specify this information manually, or compile their own custom kernel and modules, etc. <br />
** '''MOD_BLACKLIST'''=: This has become deprecated in favor of adding blacklisted modules directly to the '''MODULES=''' line below. <br />
** '''MODULES'''=: Specify additional MODULES if you know that an important module is missing, ('''hwdetect''' should have filled in the most important modules). Also specify any blacklisted modules by prefixing them with a bang (!). Udev will be forced NOT to load blacklisted modules. In the example, the IPv6 module as well as the annoying pcspeaker are blacklisted. <br />
# Scan hardware and load required modules at bootup<br />
MOD_AUTOLOAD="yes"<br />
# Module Blacklist - Deprecated<br />
MOD_BLACKLIST=()<br />
#<br />
MODULES=(e100 eepro100 mii slhc snd-ac97-codec snd-intel8x0 soundcore !net-pf-10 !pcspkr)<br />
* '''NETWORKING''' section<br />
** '''HOSTNAME'''=:Set your HOSTNAME to your liking.<br />
** '''eth0'''=: 'Ethernet, card 0'. Adjust the interface IP address, netmask and broadcast address ''if'' you are using '''static IP'''. Set eth0="dhcp" if you want to use '''DHCP'''<br />
** '''INTERFACES'''=: Specify any/all interfaces here. If you do not use DHCP to configure a device, just keep in mind that the value of the variable (whose name must be equal to the name of the device which is supposed to be configured) equals the line which would be appended to the ifconfig command if you were to configure the device manually in the shell.<br />
** '''gateway'''=: If you are using '''static IP''', set the gateway address. Ignore this entry if using '''DHCP'''<br />
** '''ROUTES'''=: If you are using static '''IP''', remove the '''!''' in front of 'gateway'. Leave the '''!''' if using '''DHCP'''<br />
<br />
Example, using '''DHCP''':<br />
HOSTNAME="arch"<br />
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255" <br />
eth0="dhcp"<br />
INTERFACES=(eth0)<br />
gateway="default gw 192.168.0.1"<br />
ROUTES=(!gateway)<br />
{{Box Note | Arch uses the '''dhcpcd''' DHCP client. Alternatively, '''dhclient''' is available from the [extra] repository via pacman.}}<br />
* '''DAEMONS''' section<br />
This array simply lists the names of those scripts contained in /etc/rc.d/ which are to be started during the boot process, and the order in which they start. <br />
DAEMONS=(@network syslog-ng netfs crond)<br />
*If a script name is prefixed with a bang (!), it is not executed. <br />
*If a script is prefixed with an "at" symbol (@), then it will be executed in the background; the startup sequence will not wait for successful completion of each daemon before continuing to the next. (Useful for speeding up system boot).<br />
*Edit this array whenever new system services are installed, if starting them automatically during bootup is desired. <br />
<br />
This 'BSD-style' init, is the Arch way of handling what others handle with various symlinks to an /etc/init.d directory.<br />
<br />
======About DAEMONS======<br />
You do not have to change the [[daemons]] line at this time, but it is useful to explain what daemons are, because we need them later in this guide. <br />
<br />
Analogous to a Windows service, a ''daemon'' is a program that runs in the background, waiting for events to occur and offering services. A good example is a webserver that waits for a request to deliver a page or an SSH server waiting for someone trying to log in. While these are full-featured applications, there are daemons whose work is not that visible. Examples are a daemon which writes messages into a log file (e.g. syslog, metalog), a daemon which lowers your CPU's frequency if your system has nothing to do (e.g.:cpufreq), and a daemon which offers you a graphical login (e.g.: gdm, kdm). All these programs can be added to the daemons line and will be started when the system boots. Useful daemons will be presented during this guide.<br />
<br />
Historically, the term ''daemon'' was coined by the programmers of MIT's Project MAC. They took the name from ''Maxwell's demon'', an imaginary being from a famous thought experiment that constantly works in the background, sorting molecules. <code>UNIX</code> systems inherited this terminology and created the backronym '''d'''isk '''a'''nd '''e'''xecution '''mon'''itor. <br />
<br />
*'''''Tip: All Arch daemons reside under /etc/rc.d/'''''<br />
<br />
=====/etc/fstab=====<br />
The '''fstab''' (for '''f'''ile '''s'''ystems '''tab'''le) is part of the system configuration listing all available disks and disk partitions, and indicating how they are to be initialized or otherwise integrated into the overall system's filesystem. The '''/etc/fstab''' file is most commonly used by the '''mount''' command. The mount command takes a filesystem on a device, and adds it to the main system heirarchy that you see when you use your system. '''mount -a''' is called from /etc/rc.sysinit, about 3/4 of the way through the boot process, and reads /etc/fstab to determine which options should be used when mounting the specified devices therein. If '''noauto''' is appended to a filesystem in /etc/fstab, '''mount -a''' will not mount it at boot.<br />
<br />
An example '''/etc/fstab''':<br />
<br />
#<br />
# /etc/fstab: static file system information<br />
#<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
none /dev/pts devpts defaults 0 0<br />
none /dev/shm tmpfs defaults 0 0<br />
#/dev/cdrom /media/cdrom auto ro,user,noauto,unhide 0 0<br />
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0<br />
#/dev/fd0 /media/fl auto user,noauto 0 0<br />
/dev/disk/by-uuid/0ec-933.. / jfs defaults,noatime,nodiratime 0 1<br />
/dev/disk/by-uuid/7ef-223.. /home jfs defaults,noatime,nodiratime 0 2<br />
/dev/disk/by-uuid/530-1e-.. swap swap defaults 0 0<br />
<br />
Modify your '''fstab''' to your requirements.<br />
{{Box Note | As of 2008-04rc, Arch is now utilizing the UUID, or Universally Unique Identifier naming convention, for consistent device mapping. This is due to active developments in the kernel and also udev, which may randomly change the ordering in which drivers for storage controllers are loaded, yielding an unbootable system/kernel panic. Nearly every motherboard has several controllers (onboard SATA, onboard IDE), and due to the aforementioned development updates, /dev/sda may become /dev/sdb on the next reboot- hence the persistent device naming convention of UUID has been adopted for reliability. ''If you do not need nor wish to use UUID, simply change your fstab to use whatever naming convention desired.'' (See [[Persistent block device naming| this wiki article]] for more information on persistent block device naming. )}}<br />
ls -lF /dev/disk/by-uuid/<br />
Will list all partitions by uuid.<br />
<br />
*If you plan on using '''hal''' to automount media such as DVDs, you may wish to comment out the cdrom and dvd entries in preparation for '''hal''', which will be installed later in this guide.<br />
<br />
{{Box Note | '''''The 'noatime' and 'nodiratime' options may safely be appended to / and /home regardless of your specified filesystem type for increased speed, performance, and power efficiency, for laptops as well as desktops.'''''}}<br />
<br />
Expanded information available in the [[Fstab]] wiki entry.<br />
<br />
====='''/etc/mkinitcpio.conf and /etc/modprobe.conf'''=====<br />
Editing these configurations is unnecessary at this point. <br />
<br />
* '''mkinitcpio.conf''' This file allows you to fine-tune the initial ram filesystem (also commonly referred to as the initial ramdisk or "initrd") for your system. The initrd is a gzipped image that is read by the kernel during bootup. The purpose of the initrd is to bootstrap the system to the point where it can access the root filesystem. This means it has to load any modules that are required for devices like IDE, SCSI, or SATA drives (or USB/FW, if you are booting off a USB/FW drive). Once the initrd loads the proper modules, either manually or through udev, it passes control to the Arch system and your bootup continues. For this reason, the initrd only needs to contain the modules necessary to access the root filesystem. It does not need to contain every module you would ever want to use. The majority of your everyday modules will be loaded later on by udev, during the init process.<br />
<br />
* '''modprobe.conf''' can be used to set special configuration options for the kernel modules<br />
<br />
=====/etc/resolv.conf (for Static IP)=====<br />
The ''resolver'' is a set of routines in the C library that provide access to the Internet Domain Name System (DNS). One of the main functions of DNS is to translate domain names into IP addresses, to make the Web a friendlier place. The resolver configuration file, or /etc/resolv.conf, contains information that is read by the resolver routines the first time they are invoked by a process.<br />
<br />
*''If you are using DHCP, you may safely ignore this file, as by default, it will be dynamically created and destroyed by the dhcpcd daemon. You may change this default behavior if you wish. (See [[Network]]).''<br />
<br />
If you use a static IP, set your DNS servers in /etc/resolv.conf (nameserver <ip-address>). You may have as many as you wish, e.g.:<br />
nameserver 4.2.2.1<br />
nameserver 4.2.2.2<br />
<br />
If you are using a router, you will probably want to specify your DNS servers in the router itself, and merely point to it from your '''/etc/resolv.conf''', using your router's IP (which is also your gateway from '''/etc/rc.conf'''), e.g.:<br />
nameserver 192.168.1.1<br />
<br />
If using '''DHCP''', you may also specify your DNS servers in the router, or allow automatic assignment from your ISP, if your ISP is so equipped.<br />
<br />
=====/etc/hosts=====<br />
<br />
This file associates IP addresses with hostnames and aliases, one line per IP address. For each host a single line should be present with the following information:<br />
<IP-address> <hostname> [aliases...]<br />
Add your ''hostname'', coinciding with the one specified in /etc/rc.conf, as an alias, so that it looks like this:<br />
127.0.0.1 localhost.localdomain localhost '''''yourhostname'''''<br />
{{Box Note |''This format, '''including the 'localhost' and your actual host name''', is required for program compatibility! Errors in this entry may cause poor network performance and/or certain programs to open very slowly, or not work at all. This is a very common error for beginners.''}}<br />
<br />
If you use a static IP, add another line using the syntax: <static-IP> <hostname.domainname.org> <hostname> e.g.:<br />
192.168.1.100 '''''yourhostname'''''.domain.org '''''yourhostname'''''<br />
<br />
*'''TIP''': For convenience, you may also use /etc/hosts aliases for hosts on your network, and/or on the Web, e.g.:<br />
64.233.169.103 www.google.com g<br />
192.168.1.90 media<br />
192.168.1.88 data<br />
The above example would allow you to access google simply by typing 'g' into your browser, and access to a media and data server on your network by name and without the need for typing out their respective IP addresses.<br />
<br />
=====/etc/hosts.deny and /etc/hosts.allow=====<br />
Modify these configurations according to your needs if you plan on using the [[SSH|ssh]] daemon. The default configuration will reject all incoming connections, not only ssh connections. Edit your '''/etc/hosts.allow '''file and add the appropriate parameters: <br />
<br />
* let everyone connect to you<br />
sshd: ALL<br />
<br />
* restrict it to a certain ip<br />
sshd: 192.168.0.1<br />
<br />
* OR restrict for an IP range<br />
sshd: 10.0.0.0/255.255.255.0<br />
<br />
If you do not plan on using the [[SSH|ssh]] daemon, leave this file at the default, (empty), for added security.<br />
<br />
=====/etc/locale.gen=====<br />
<br />
The '''locale-gen''' command reads from '''/etc/locale.gen''' to generate specific locales. They can then be used by '''glibc''' and any other locale-aware program or library for rendering "peculiar" text, correctly displaying regional monetary values, time and date formats, alphabetic idiosyncrasies, and other locale-specific standards. The ability to setup a default locale is a great built-in privilege of using a <code>UNIX</code>-like operating system.<br />
<br />
By default /etc/locale.gen is an empty file with commented documentation. Once edited, the file remains untouched. '''locale-gen''' runs on every '''glibc''' upgrade, generating all the locales specified in /etc/locale.gen.<br />
<br />
Choose the locale(s) you need (remove the # in front of the lines you want), e.g.:<br />
en_US ISO-8859-1<br />
en_US.UTF-8 <br />
<br />
The installer will now run the locale-gen script, which will generate the locales you specified. You may change your locale in the future by editing /etc/locale.gen and subsequently running 'locale-gen' as root.<br />
<br />
{{Box Note |'''''If you fail to choose your locale, this will lead to a "The current locale is invalid..." error. This is perhaps the most common mistake by new Arch users, and also leads to the most commonly asked questions on the forum.'''''}}<br />
<br />
=====Root password=====<br />
Finally, set a root password and make sure that you remember it later. Return to the main menu and continue with installing bootloader.<br />
<br />
=====Pacman-Mirror=====<br />
Choose a mirror repository for '''pacman'''. <br />
*''archlinux.org is throttled, limiting downloads to 50KB/s'' <br />
<br />
Return to the main menu.<br />
<br />
===Install Bootloader===<br />
Because we have no secondary operating system in our example, we will need a bootloader. [http://www.gnu.org/software/grub/ GNU GRUB] is the recommended bootloader. Alternatively, you may choose [http://lilo.go.dyndns.org/ LILO]. <br />
====GRUB====<br />
The provided '''GRUB''' configuration ('''/boot/grub/menu.lst''') should be sufficient, but verify its contents to ensure accuracy. You may want to alter the resolution of the console by adding a vga=<number> kernel argument corresponding to your desired virtual console resolution. (A table of resolutions and the corresponding numbers is printed in the menu.lst.)<br />
<br />
Example: <br />
title Arch Linux (Main)<br />
root (hd0,0) <br />
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/0ec1-9339.. ro vga=773<br />
initrd /boot/kernel26.img<br />
{{Box Note | '''''The linux kernel, 'vmlinuz', is so named because it incorporated '''v'''irtual '''m'''emory capability early in its development. The '''z''' denotes a zipped (compressed) image.'''''}}<br />
<br />
Explanation:<br />
<br />
Line 1: '''title''': A printed menu selection. "Arch Linux (Main)" will be printed on the screen as a menu selection.<br />
<br />
Line 2: '''root''': '''GRUB''''s root; the drive and partition where the kernel (/boot) resides, according to system BIOS. (More accurately, where GRUB's stage2 file resides). '''NOT necessarily the root''' (/) file system, as they can reside on separate partitions. GRUB's numbering scheme starts at 0, and uses an hd''x,x'' format regardless of IDE or SATA, and enclosed within parentheses. <br />
<br />
The example indicates that /boot is on the first partition of the first drive, according to BIOS, or, (hd0,0).<br />
<br />
Line 3: '''kernel''': This line specifies:<br />
<br />
* The path and filename of the kernel '''''relative to GRUB's root'''''.<br />
In the example, /boot is merely a directory residing on the same partition as / and '''vmlinuz26''' is the kernel filename; '''/boot/vmlinuz26'''. ''If /boot were on a separate partition, the path and filename would be simply '''/vmlinuz26''', being relative to '''GRUB''''s root.'' <br />
<br />
* The root= argument to the kernel statement specifies the partition containing the root (/) directory in the booted system, (more accurately, the partition containing '''/sbin/init'''), ''according to the UUID numbering scheme'' as of 2008-04rc, which uses the /dev/disk/by-uuid/xxxx-xxxx-xxxx format. <br />
<br />
*An easy way to distinguish the 2 appearances of 'root' in /boot/grub/menu.lst is to remember that the first root statement ''informs GRUB where the kernel resides'', whereas the second root= kernel argument ''tells the kernel where the root filesystem (/) resides''.<br />
<br />
* Kernel options. <br />
<br />
In our example, '''ro''' mounts the filesystem as read only during startup, and the '''"vga=773"''' argument will give a 1024x768 framebuffer with 256 color depth.<br />
<br />
Line 4: '''initrd''': (For Initial RAM disk) The path and filename of the initial RAM filesystem '''relative to GRUB''''s root. Again, in the example, /boot is merely a directory residing on the same partition as / and '''kernel26.img''' is the initrd filename; '''/boot/kernel26.img'''. ''If /boot were on a separate partition, the path and filename would be simply '''/kernel26.img''', being relative to '''GRUB''''s root.'' <br />
<br />
Install the '''GRUB''' bootloader to the master boot record, (sda in our example).<br />
<br />
===Reboot===<br />
<br />
That's it; You have configured and installed your Arch Linux base system. Exit the install, and type the magic word:<br />
<br />
reboot<br />
(Be sure to remove the installer CD)<br />
<br />
Your new Arch Linux system will boot up and finish with a login prompt (you may want to change the boot order in your '''BIOS''' back to booting from hard disk).<br />
<br />
'''Congratulations, and welcome to your shiny, new Arch Linux base system!'''<br />
<br />
Your new Arch Linux base system is now a functional GNU/Linux environment ready for customization. From here, you may build this elegant set of tools into whatever you wish or require for your purposes. <br />
<br />
Login with the root account. We will configure pacman and update the system as root, then add a normal user. <br />
{{Box Note |Virtual consoles 1-6 are available.}}<br />
<br />
===Configuring the network (if necessary)===<br />
*''This section will assist you in configuring most types of networks, if your network configuration is not working for you.''<br />
<br />
If you properly configured your system, you should have a working network. Try to ping www.google.com to verify this.<br />
ping -c 3 www.google.com<br />
<br />
''If you have successfully established a network connection, continue with '''[[#Update, Sync and Upgrade the system with pacman|Update, Sync and Upgrade the system with pacman]]'''.''<br />
<br />
If, after trying to ping www.google.com, you get an "unknown host" error, you may conclude that your network is not properly configured. You may choose to double-check the following files for integrity and proper settings:<br />
<br />
'''/etc/rc.conf''' # Specifically, check your HOSTNAME= and NETWORKING section for typos and errors.<br />
<br />
'''/etc/hosts''' # Double-check your format. (See above.)<br />
<br />
'''/etc/resolv.conf''' # If you are using a static IP. If you are using DHCP, this file will be dynamically created and destroyed by default, but can be changed to your preference. (See [[Network]].)<br />
<br />
Advanced instructions for configuring the network can be found in the [[Network]] article.<br />
<br />
====Wired LAN====<br />
<br />
Check your Ethernet with<br />
ifconfig -a<br />
All interfaces will be listed. You should see an entry for eth0, or perhaps eth1. <br />
*'''Static IP'''<br />
<br />
If required, you can set a new static IP with:<br />
ifconfig eth0 <ip address> netmask <netmask> up <br />
and the default gateway with<br />
route add default gw <ip address of the gateway><br />
Verify that /etc/resolv.conf contains your DNS server and add it if it is missing. <br />
Check your network again with ping www.google.com. If everything is working now, adjust /etc/rc.conf as described above for static IP. <br />
*'''DHCP'''<br />
If you have a DHCP server/router in your network try:<br />
dhcpcd eth0<br />
If this is working, adjust /etc/rc.conf as described above, for dynamic IP.<br />
<br />
====Wireless LAN====<br />
Detailed setup guide: [[Wireless Setup]]<br />
<br />
====Analog Modem====<br />
To be able to use a Hayes-compatible, external, analog modem, you need to at least have the ppp package installed. Modify the file /etc/ppp/options to suit your needs and according to man pppd. You will need to define a chat script to supply your username and password to the ISP after the initial connection has been established. The manpages for pppd and chat have examples in them that should suffice to get a connection up and running if you're either experienced or stubborn enough. With udev, your serial ports usually are /dev/tts/0 and /dev/tts/1.<br />
Tip: Read [[Dialup without a dialer HOWTO]].<br />
<br />
Instead of fighting a glorious battle with the plain pppd, you may opt to install wvdial or a similar tool to ease the setup process considerably. In case you're using a so-called WinModem, which is basically a PCI plugin card working as an internal analog modem, you should indulge in the vast information found on the [http://www.linmodems.org/ LinModem] homepage.<br />
<br />
====ISDN====<br />
<br />
Setting up ISDN is done in three steps:<br />
# Install and configure hardware<br />
# Install and configure the ISDN utilities<br />
# Add settings for your ISP <br />
<br />
The current Arch stock kernels include the necessary ISDN modules, meaning that you will not need to recompile your kernel unless you're about to use rather odd ISDN hardware. After physically installing your ISDN card in your machine or plugging in your USB ISDN-Box, you can try loading the modules with modprobe. Nearly all passive ISDN PCI cards are handled by the hisax module, which needs two parameters: type and protocol. You must set protocol to '1' if your country uses the 1TR6 standard, '2' if it uses EuroISDN (EDSS1), '3' if you're hooked to a so-called leased-line without D-channel, and '4' for US NI1.<br />
<br />
Details on all those settings and how to set them is included in the kernel documentation, more specifically in the isdn subdirectory, and available online. The type parameter depends on your card; a list of all possible types can be found in the README.HiSax kernel documentation. Choose your card and load the module with the appropriate options like this:<br />
<br />
modprobe hisax type=18 protocol=2<br />
<br />
This will load the hisax module for my ELSA Quickstep 1000PCI, being used in Germany with the EDSS1 protocol. You should find helpful debugging output in your /var/log/everything.log file, in which you should see your card being prepared for action. Please note that you will probably need to load some USB modules before you can work with an external USB ISDN Adapter.<br />
<br />
Once you have confirmed that your card works with certain settings, you can add the module options to your /etc/modprobe.conf:<br />
<br />
alias ippp0 hisax<br />
options hisax type=18 protocol=2<br />
<br />
Alternatively, you can add only the options line here, and add hisax to your MODULES array in the rc.conf. It's your choice, really, but this example has the advantage that the module will not be loaded until it's really needed.<br />
<br />
That being done, you should have working, supported hardware. Now you need the basic utilities to actually use it!<br />
<br />
Install the isdn4k-utils package, and read the manpage to isdnctrl; it'll get you started. Further down in the manpage you will find explanations on how to create a configuration file that can be parsed by isdnctrl, as well as some helpful setup examples. Please note that you have to add your SPID to your MSN setting separated by a colon if you use US NI1.<br />
<br />
After you have configured your ISDN card with the isdnctrl utility, you should be able to dial into the machine you specified with the PHONE_OUT parameter, but fail the username and password authentication. To make this work add your username and password to /etc/ppp/pap-secrets or /etc/ppp/chap-secrets as if you were configuring a normal analogous PPP link, depending on which protocol your ISP uses for authentication. If in doubt, put your data into both files.<br />
<br />
If you set up everything correctly, you should now be able to establish a dial-up connection with<br />
isdnctrl dial ippp0<br />
as root. If you have any problems, remember to check the logfiles!<br />
<br />
====DSL (PPPoE)====<br />
<br />
These instructions are relevant to you only if your PC itself is supposed to manage the connection to your ISP. You do not need to do anything but define a correct default gateway if you are using a separate router of some sort to do the grunt work.<br />
<br />
Before you can use your DSL online connection, you will have to physically install the network card that is supposed to be connected to the DSL-Modem into your computer. After adding your newly installed network card to the modules.conf/modprobe.conf or the MODULES array, you should install the rp-pppoe package and run the pppoe-setup script to configure your connection. After you have entered all the data, you can connect and disconnect your line with<br />
<br />
/etc/rc.d/adsl start<br />
<br />
and<br />
<br />
/etc/rc.d/adsl stop<br />
<br />
respectively. The setup usually is rather easy and straightforward, but feel free to read the manpages for hints. If you want to automatically 'dial in' on boot-up, add adsl to your DAEMONS array.<br />
<br />
===Update, Sync and Upgrade the system with [[pacman]]===<br />
Now we will update the system using [[pacman]]. <br />
<br />
====What is pacman ?====<br />
[[Pacman]] is the '''pac'''kage '''man'''ager of Arch Linux. Pacman is written in C and is fast, simple, and extremely versatile. It manages your entire package system and handles installation, removal, package downgrade (through cache), custom compiled package handling, automatic dependency resolution, remote and local searches and much more. Arch uses the .tar.gz package format, which further enhances pacman's speed; Gzipped tarballs, though slightly larger, are decompressed much faster than their Bzipped counterparts, and are therefore generally installed more expediently. <br />
<br />
We will use pacman to download software packages from remote repositories and install them onto your system.<br />
<br />
Pacman is the most important tool in your Arch Linux toolbox for building the base system into whatsoever you please.<br />
<br />
====Configuring pacman====<br />
<br />
=====Package Repositories and /etc/pacman.conf=====<br />
Arch currently offers the following repositories readily accessible through pacman:<br />
<br />
'''[core]'''<br />
<br />
The simple principle behind [core] is to provide only one of each necessary tool for a base Arch Linux system; The GNU toolchain, the Linux kernel, one editor, one command line browser, etc. (There are a few exceptions to this. For instance, both vi and nano are provided, allowing the user to choose one or both.) It contains all the packages that MUST be in perfect working order to make sure your system continues to run. These are the absolute system-critical packages. Developer maintained.<br />
<br />
*''The Core installation media simply contains an installer script, and a snapshot of the core repository.''<br />
<br />
'''[extra]'''<br />
<br />
The [extra] repository contains all Arch packages that are not themselves necessary for a base Arch system, but contribute to a more full-featured environment. '''X''', KDE, and Apache, for instance, can be found here. Developer maintained.<br />
<br />
'''[unstable]'''<br />
<br />
The [unstable] repository contains experimental and unstable software, especially if the development version of a package has become popular for some reason. For example, perhaps the upstream stable version is hopelessly out of date, or the unstable version has some groundbreaking changes that a lot of users seem interested in, like experimental kernel drivers or -svn package versions. Developer maintained.<br />
<br />
{{Box Note |'''Contrary to popular belief, it is perfectly safe to enable the unstable repository, as there are no name collisions with [core], [community] or [extra]. Packages from [unstable] are only installed if you explicitly do so. If there is a conflict between an [Unstable] package and an installed package, pacman will warn you and resolve the conflict, if prompted, by removing the installed package.'''}}<br />
<br />
The [unstable] repository is currently not maintained for ''x86_64''.<br />
<br />
'''[testing]'''<br />
<br />
The [testing] repository contains packages that are candidates for the [core], [extra] or [unstable] repositories. New packages go into [testing] if:<br />
* they are expected to break something on update and need to be tested first<br />
* they require other packages to be rebuilt. In this case, all packages that need to be rebuilt are put into [testing] first and when all rebuilds are done, they are moved back to the other repositories. Developer maintained.<br />
<br />
[testing] is the only repository that can have name collisions with any of the other official repositories. If enabled, it has to be the first repo listed in your ''pacman.conf'' file.<br />
<br />
{{Box Note|'''''Be careful when enabling [testing]. Your system may break after you update with [testing] enabled. Only experienced users should use it.'''''}}<br />
<br />
'''[community]'''<br />
<br />
The [community] repository is maintained by the ''Trusted Users (TUs)'' and is part of the ''Arch User Repository ([[AUR]])''. It contains binary packages from the ''AUR'' that have enough votes and were adopted by a ''TU''. Like all repos listed above, [community] may be readily accessed by pacman.<br />
<br />
The '''[[AUR]]''' also contains the '''unsupported''' branch, which cannot be accessed directly by pacman*. [unsupported] contains more than 8 thousand PKGBUILD scripts for building packages from source, that may be unavailable through the other repos. <br />
<br />
<nowiki>*</nowiki> '''''[[AUR Helpers]]''''' can help you seamlessly access AUR.<br />
<br />
'''/etc/pacman.conf'''<br />
<br />
pacman will attempt to read /etc/pacman.conf each time it is invoked. This configuration file is divided into sections, or repositories. Each section defines a package [[Official Repositories|repository]] that pacman can use when searching for packages. The exception to this is the options section, which defines global options.<br />
nano /etc/pacman.conf<br />
Example:<br />
[core]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
[extra]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
#[unstable]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
[community]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
Enable all desired repositories (remove the # in front of the 'Include =' and '[repository]' lines).<br />
<br />
<br />
*'''''When choosing repos, be sure to uncomment both the repository header lines in [brackets] as well as the 'Include =' lines. Failure to do so will result in the selected repository being omitted! This is a very common error.'' '''<br />
<br />
=====/etc/pacman.d/mirrorlist=====<br />
Faster mirrors will dramatically improve pacman performance, and your overall Arch Linux experience.<br />
<br />
Edit /etc/pacman.d/mirrorlist:<br />
nano /etc/pacman.d/mirrorlist<br />
Remove all mirrors which are not on your continent, or are extremely distant. (Using nano, you may use CTRL-K to cut each unneeded line.) <br />
<br />
Edit /etc/pacman.d/mirrorlist by placing the best mirror at the top of the list. (Recall that archlinux.org is throttled to 50KB/s). If using nano, you can cut a line with CTRL-K and paste with CTRL-U. <br />
<br />
After changing mirrors, issue the following command:<br />
pacman -Syy<br />
This will force pacman to resynchronize with the new repo. Issuing pacman -Syy ''whenever a mirror is changed'', is good practice and will avoid possible headaches.<br />
=====Ignoring packages=====<br />
When you execute the command "pacman -Syu", your entire system will be updated. It is possible that you want to prevent a package from being upgraded. An example could be the kernel (kernel26) or a package for which an upgrade may prove problematic for your system. In this case, you have two options; indicate the packages you want to skip in the pacman command line using the --ignore switch (do pacman -S --help for details) or permanently indicate the packages you want to skip in your /etc/pacman.conf file:<br />
<br />
IgnorePkg = kernel26<br />
The typical way to use Arch is to use pacman to install all packages unless there is no package available, in which case you can build your own package using [[ABS]]. Many user-contributed packages are available in the Arch User Repository. You are expected to keep your system up to date with pacman -Syu, rather than selectively upgrading packages. Use of '''IgnorePkg''' in /etc/pacman.conf is therefore discouraged, and should be used sparingly, if you know what you are doing.<br />
<br />
You may diverge from this typical usage as you wish; just be warned that there is a greater chance that things will not work as intended and that it could break your system. The majority of complaints happen when selective upgrading or unusual compilation is performed.<br />
<br />
=====Ignoring Configuration Files=====<br />
In the same vein, you can also "protect" your configuration/system files from being overwritten during "pacman -Su" using the following option in your /etc/pacman.conf<br />
<br />
NoUpgrade = etc/lilo.conf boot/grub/menu.lst<br />
<br />
====Update System====<br />
Update, sync, and '''upgrade''' your entire new system with:<br />
pacman -Syu<br />
pacman will now fetch the latest information about available packages and perform all available upgrades. (You may be prompted to upgrade pacman itself at this point. If so, say yes, and then reissue the pacman -Syu command when finished.) <br />
Reboot if a kernel upgrade has occurred. <br />
{{Box Note|'''''Occasionally, configuration changes may take place requiring user action during an update; read pacman's output for any pertinent information.'''''}}<br />
If the messages go by too fast to read, you can look at them later at /var/log/pacman.log.<br />
<br />
=====The beauty of the Arch rolling release model=====<br />
Keep in mind that Arch is a '''rolling release''' distribution. This means there is never a reason to reinstall or perform elaborate system rebuilds to upgrade to the newest version. Simply issuing '''pacman -Syu''' periodically keeps your entire system up-to-date and on the bleeding edge. At the end of this upgrade, your system is completely current. <br />
Reboot if a kernel upgrade has occurred.<br />
<br />
====Get familiar with pacman====<br />
Pacman is the Arch user's best friend. It is highly recommended to study and learn how to use the pacman tool. Try:<br />
man pacman<br />
Check out the bottom of this article, and look up the [[pacman]] wiki entries at your leisure.<br />
<br />
<br />
<br />
===Add a user and setup groups===<br />
You should not do your everyday work using the root account. It is more than poor practice; it is dangerous. Root is for administrative tasks. Instead, add a normal user account using:<br />
adduser<br />
While most default options are safe to use, you may want to add audio, optical, storage, video, and wheel when prompted for additional groups (separate them with a comma and no space) - especially if you are planning on having a full-featured desktop environment. <br />
<br />
Groups and users thereof are defined in /etc/group. <br />
<br />
They include:<br />
<br />
*'''audio''' - for tasks involving sound card and related software<br />
*'''floppy''' - for access to a floppy if applicable<br />
*'''lp''' - for managing printing tasks<br />
*'''optical''' - for managing tasks pertaining to the optical drive(s)<br />
*'''storage''' - for managing storage devices<br />
*'''video''' - for video tasks and 3d acceleration<br />
*'''wheel''' - for using sudo<br />
<br />
See the [[Groups]] article to understand what groups you need to be a member of. <br />
<br />
Check the man pages for usermod and gpasswd for more information.<br />
===Install and setup Sudo===<br />
<br />
See [[Sudo]]<br />
<br />
==Part II: Install X and configure ALSA==<br />
<br />
<br />
===Configure the audio card with alsamixer===<br />
The Advanced Linux Sound Architecture (known by the acronym '''ALSA''') is a Linux kernel component intended to replace the original Open Sound System (OSS) for providing device drivers for sound cards. Besides the sound device drivers, '''ALSA''' also bundles a user space library for application developers who want to use driver features with a higher level API than direct interaction with the kernel drivers. <br />
-----<br />
{{Box Note|udev will automatically probe your hardware on boot-up, loading the corresponding module for your audio card. Your sound should already be working, but you cannot hear anything because it is muted by default.}} <br />
The alsa-utils package contains alsamixer, which will allow us to configure the sound device from the console. (You may also run alsamixer from an '''X''' environment later.)<br />
<br />
Install the alsa-utils package:<br />
pacman -S alsa-utils<br />
Did you add your normal user to the audio group? If not, now would be a good time. As root do:<br />
gpasswd -a yourusername audio<br />
Log out the root user, and login as non-root user.<br />
<br />
As '''''normal, non-root''''' user, do: <br />
'''$''' alsamixer<br />
Unmute the Master and PCM channels by scrolling to them with cursor left/right and pressing '''M'''. Increase the volume levels with the cursor-up key. (70-90 Should be a safe range.) Some machines, (like the Thinkpad T61), have a '''Speaker''' channel which must be unmuted and adjusted as well. Leave alsamixer by pressing ESC. <br />
==== Sound Test ====<br />
Test your sound configuration as normal user using aplay:<br />
aplay /usr/share/sounds/alsa/Front_Center.wav<br />
You should hear a very eloquent woman say, "Front, center."<br />
<br />
''Note: If you still cannot hear any sound, try checking (by running alsamixer) if Speaker is muted. If so, press '''M''' to unmute it and then try playing the test sound again.''<br />
<br />
Then run alsactl as root:<br />
alsactl store<br />
This will create '/etc/asound.state', saving the alsamixer settings. <br />
<br />
Also, add the alsa ''daemon'' to your DAEMONS section in /etc/rc.conf to automatically restore the mixer settings on boot-up.<br />
nano /etc/rc.conf<br />
DAEMONS=(syslog-ng network crond '''alsa''')<br />
''Note that the alsa daemon merely restores your volume mixer levels on boot up by reading /etc/asound.state. It is separate from the alsa audio library (and kernel level API).''<br />
<br />
Expanded information available in the [[ALSA]] wiki entry.<br />
<br />
===Installing and configuring X===<br />
The '''X''' Window System (commonly '''X11''', or just simply '''X''') is a networking and display protocol which provides windowing on bitmap displays. It provides the standard toolkit and protocol to build graphical user interfaces (GUIs) on <code>UNIX</code>-like operating systems.<br />
<br />
'''X''' provides the basic framework, or primitives, for building GUI environments: drawing and moving windows on the screen and interacting with a mouse and/or keyboard. '''X''' does not mandate the user interface — individual client programs handle this. <br />
<br />
'''X''' is so named because it was preceded by the '''W''' Window System, originally developed at Stanford University. <br />
-----<br />
<br />
{{Box Note| If you plan on using an '''open-source''' video driver, and need 3d acceleration, it is recommended to install the libgl library before installing Xorg:}}<br />
pacman -S libgl<br />
''(Proprietary video drivers provide their own gl library implementations.)''<br />
----- <br />
Now we will install the base Xorg packages using pacman. This is the first step in building a GUI.<br />
<br />
pacman -S xorg<br />
3d utilities such as glxgears are included in the '''mesa''' package:<br />
pacman -S mesa<br />
<br />
Now we have the base packages we need for running the '''X''' Server. You should add the driver for your graphics card now (e.g. xf86-video-<name>). The easiest way to configure X.org is by installing the correct driver packages first, and then generating /etc/X11/xorg.conf using an autoconfiguration script, like Xorg -configure.<br />
<br />
You will need knowledge of which video chipset your machine has. If you do not know, use the lspci program:<br />
lspci | grep VGA<br />
<br />
If you need a list of all '''open-source''' video drivers, do: <br />
pacman -Ss xf86-video | less<br />
Here is a list of '''open source''' drivers, and the corresponding video chipsets.<br />
*'''xf86-video-apm''' Alliance ProMotion video driver<br />
*'''xf86-video-ark''' ark video driver<br />
*'''xf86-video-ati''' ati video driver<br />
*'''xf86-video-chips''' Chips and Technologies video driver<br />
*'''xf86-video-cirrus''' Cirrus Logic video driver<br />
*'''xf86-video-dummy''' dummy video driver<br />
*'''xf86-video-fbdev''' framebuffer video driver<br />
*'''xf86-video-glint''' GLINT/Permedia video driver<br />
*'''xf86-video-i128''' Number 0 i128 video driver<br />
*'''xf86-video-i740''' Intel i740 video driver<br />
*'''xf86-video-i810''' Intel i810/i830/i9xx video drivers (deprecated - use -intel)<br />
*'''xf86-video-intel''' Newer Version of Intel i810/i830/i9xx video drivers<br />
*'''xf86-video-imstt''' Integrated Micro Solutions Twin Turbo vidoe driver<br />
*'''xf86-video-mga''' mga video driver (Matrox Graphics Adapter)<br />
*'''xf86-video-neomagic''' neomagic video driver<br />
*'''xf86-video-nv''' nvidia nv video driver<br />
*'''xf86-video-rendition''' Rendition video driver<br />
*'''xf86-video-s3''' S3 video driver<br />
*'''xf86-video-s3virge''' S3 Virge video driver<br />
*'''xf86-video-savage''' savage video driver<br />
*'''xf86-video-siliconmotion''' siliconmotion video driver<br />
*'''xf86-video-sis''' SiS video driver<br />
*'''xf86-video-sisusb''' SiS USB video driver<br />
*'''xf86-video-tdfx''' tdfx video driver<br />
*'''xf86-video-trident''' Trident video driver<br />
*'''xf86-video-tseng''' tseng video driver<br />
*'''xf86-video-unichrome''' Unichrome video drivers<br />
*'''xf86-video-v4l''' v4l video driver<br />
*'''xf86-video-vesa''' vesa video driver<br />
*'''xf86-video-vga''' VGA 16 color video driver<br />
*'''xf86-video-via''' via video driver<br />
*'''xf86-video-vmware ''' vmware video driver<br />
*'''xf86-video-voodoo ''' voodoo video driver<br />
<br />
* Note that the '''vesa''' driver is the most generic, and should work with almost any modern video chipset. If you cannot find a suitable driver for your video chipset, vesa '''should''' work.<br />
<br />
*If you have an NVIDIA or ATI video adapter, you may wish to install the proprietary NVIDIA or ATI drivers. '''Installing proprietary video drivers is covered [[#Using proprietary Graphics Driver (NVIDIA, ATI)|below]].'''<br />
<br />
Use pacman to install the appropriate video driver for your video card/onboard video. e.g.:<br />
pacman -S xf86-video-savage<br />
(for the Savage driver.)<br />
<br />
===Create /etc/X11/xorg.conf===<br />
=====What is /etc/X11/xorg.conf?=====<br />
/etc/X11/xorg.conf is the main configuration file for your '''X''' Window System, the foundation of your '''G'''raphical '''U'''ser '''I'''nterface. It is a plain text file ordered into sections and subsections. Important sections are ''Files, InputDevice, Module, Monitor, Modes, Screen, Device, and ServerLayout''. Sections can appear in any order and there may be more than one section of each kind, for example, if you have more than one monitor, or if your laptop has a trackpoint as well as a mouse. <br />
------<br />
By default, you will not have an Xorg config file, as the newest versions of Xorg feature autodetection. ''If'' the autodetection ''works satisfactorily'' and you do not need to specify special features such as aiglx, compositing and so forth, you may forgo creating an xorg.conf file. <br />
<br />
''Most people will still find that they need to generate a config file, however.''<br />
<br />
Advanced users may wish to manually create their own xorg.conf file. You may also use the Xorg -configure script to generate a basic config file. As root, do:<br />
Xorg -configure<br />
This will create a config file at /root/xorg.conf.new <br />
<br />
To test the server, run:<br />
X -config /root/xorg.conf.new<br />
'''X''' should start with the white hollow vector '''X''' in the center of the screen, which should respond to mouse, trackpoint or touchpad movement. Use CTRL-Alt-Backspace to exit '''X'''.<br />
<br />
Inspect your config file in case of errors:<br />
<br />
nano /root/xorg.conf.new<br />
<br />
Ensure the Xorg -configure script has correctly specified your video driver. e.g.:<br />
Section "Device"<br />
<br />
...<br />
<br />
Driver "savage"<br />
<br />
...<br />
<br />
EndSection<br />
<br />
Ensure there are horizontal sync and vertical refresh specs under section "Monitor". If not, add them:<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
HorizSync 30.0 - 130.0 # Safe for LCD's<br />
VertRefresh 50.0 - 100.0 # Safe for LCD's and most CRT's.<br />
EndSection<br />
(If you do not know these specs, consult your monitor's documentation.)<br />
<br />
Specify your default color depth under section "Screen":<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
(Typically, this will be set to 24 for true color.)<br />
<br />
Also add your desired Modes to your "Display" subsection, at least under the Depth 24 header, e.g.:<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
Modes "1024x768" "800x600" "640x480"<br />
Add the following section, if you wish to enable eye candy which requires the composite extension: <br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
Try your config again, after modifying:<br />
X -config /root/xorg.conf.new<br />
Ensure an '''X''' session opens, without errors, and move the generated config file to /etc/X11/:<br />
mv /root/xorg.conf.new /etc/X11/xorg.conf<br />
Detailed instructions in the [[Xorg]] article.<br />
<br />
====Alternative xorg.conf generation====<br />
If Xorg -configure is not generating a usable xorg.conf, you may alternatively use the hwd tool. Install with:<br />
pacman -S hwd<br />
And run with<br />
hwd -xa<br />
You may also try the xorgcfg script:<br />
xorgcfg <br />
Lastly, you may choose xorgconfig, which will interactively prompt you for hardware information to create a basic xorg.conf:<br />
xorgconfig<br />
Continue with '''[[#Simple baseline X test|Simple baseline X test]]'''<br />
<br />
===Using proprietary Graphics Driver (NVIDIA, ATI)===<br />
You may choose to use the proprietary video drivers from NVIDIA or ATI. <br />
====NVIDIA Graphic Cards====<br />
The NVIDIA proprietary drivers are generally considered to be of good quality, and offer 3D performance, whereas the open source '''nv''' driver offers only 2d support at this time. <br />
<br />
Before you configure your Graphics Card you will need to know which driver fits. Arch currently has 3 different driver packages that each match a certain subset of Cards: <br />
<br />
'''1. nvidia-71xx''' ''for very old Cards like TNT and TNT2''<br />
<br />
'''2. nvidia-96xx''' ''slightly newer cards up to the GF 4''<br />
<br />
'''3. nvidia''' ''newest GPUs after the GF 4''<br />
<br />
Consult the NVIDIA-Homepage to see which one is for you. The difference is only for the installation; Configuration works the same with every driver.<br />
<br />
Select and install the appropriate NVIDIA driver ''for your card'', e.g.: <br />
pacman -S nvidia-96xx<br />
<br />
The NVIDIA package has a utility for updating your existing /etc/X11/xorg.conf for use with the NVIDIA driver:<br />
nvidia-xconfig<br />
<br />
It also has several options which will further specify the contents and options of the xorg.conf file.<br />
For example,<br />
nvidia-xconfig --composite --add-argb-glx-visuals<br />
<br />
For more detailed information, see nvidia-xconfig(1).<br />
<br />
Some useful tweaking options in the device section are (beware that these may not work on your system):<br />
Option "RenderAccel" "true"<br />
Option "NoLogo" "true"<br />
Option "AGPFastWrite" "true"<br />
Option "EnablePageFlip" "true"<br />
Make sure all instances of DRI are commented out:<br />
# Load "dri"<br />
Double check your /etc/X11/xorg.conf to make sure your default depth, horizontal sync, vertical refresh, and resolutions are acceptable.<br />
<br />
Update kernel module dependencies:<br />
depmod -a<br />
<br />
Advanced instructions for nvidia configuration can be found in the [[NVIDIA]] article.<br />
<br />
Continue with '''[[#Simple baseline X test|Simple baseline X test]]'''<br />
<br />
====ATI Graphic Cards====<br />
ATI owners have two options for drivers. If you are unsure which driver to use, please try the open-source one first. The open-source driver will suit most needs along with being generally less problematic.<br />
<br />
Install the '''proprietary''' ATI Driver with<br />
pacman -S catalyst<br />
Use the aticonfig tool to modify the xorg.conf.<br />
<br />
Install the '''open-source''' ATI Driver with<br />
pacman -S xf86-video-ati<br />
Currently, the performance of the open-source driver is not on par with that of the proprietary one. It also lacks TV-out, dual-link DVI support, and possibly other features. On the other hand, it supports Aiglx and has better dual-head support.<br />
{{Box Note| The latest proprietary driver does support [[AIGLX]] now. To use [[Compiz]] or [[Beryl]] add Option "AIGLX" "True" to Section ServerFlags and Option "Composite" "True" to Section Extensions.}}<br />
Advanced instructions for ATI configuration can be found in the [[ATI | ATI wiki]].<br />
<br />
===Simple baseline X test===<br />
<br />
At this point, you should have xorg installed, with a suitable video driver and an /etc/X11/xorg.conf configuration file. If you want to test your configuration quickly, to ensure your ability to start '''X''' from the command line before installing a complete desktop environment, you can do so by invoking '''xterm'''. Xterm is a very simple terminal emulator which runs in the '''X '''Server environment; it is installed as part of the base xorg packages. More advanced users who are comfortable with '''X''' configuration may choose to skip this optional step.<br />
<br />
Prepare for the test by configuring a ~/.xinitrc:<br />
<br />
===== ~/.xinitrc =====<br />
This file dictates what '''X''' Window client is invoked with the '''startx''' and/or '''xinit''' command ''on a per-user basis''. (The '''startx''' script is merely a front end to the more versatile '''xinit''' command.) It also can contain other startup items for the '''X''' environment.<br />
{{Box Note | '''.xinitrc''' is a so-called 'dot' (.) file. Files in a UNIX filesystem which are preceded with a dot (.) are 'hidden', and will not show up with a regular 'ls' command, usually for the sake of keeping directories tidy. Dot files may be seen by issuing '''ls -a'''. The 'rc' denotes ''Run Commands'' and simply indicates that it is a configuration file. Since it controls how a program runs, it is (although historically incorrect) also said to stand for "Run Control".}}<br />
<br />
'''startx/xinit''' will start the '''X''' server and clients. To determine the client to run, '''startx/xinit''' will first look for a .xinitrc file in the user's home directory. In the absence of file ~/.xinitrc, it defaults to the global xinitrc in the xinit library directory; /etc/X11/xinit/xinitrc, which defaults to using the TWM window manager. (Hence, if you invoke startx without a ~/.xinitrc file, a TWM session will start.)<br />
<br />
Switch to your '''''normal, non-root''''' user:<br />
su yourusername<br />
* /etc/skel/ contains files and directories to provide sane defaults for newly created user accounts. The name '''skel''' is derived from the word '''skeleton''', because the files it contains form the basic structure for users' home directories.<br />
Copy the sample xinitrc file from /etc/skel/ to your home directory: <br />
<br />
cp /etc/skel/.xinitrc ~/<br />
Edit the file: <br />
nano ~/.xinitrc<br />
and add:<br />
<br />
exec xterm<br />
<br />
So that it looks like this:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
exec xterm<br />
# exec wmaker<br />
# exec startkde<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
<br />
''Be sure to have only one uncommented '''exec''' line in your ~/.xinitrc at this time''. Below, we shall edit this file again to specify the appropriate desktop environment/window manager of your choice.<br />
<br />
Finally, test your configurations by starting '''X''' as '''normal, non-root''' user, with:<br />
<br />
startx<br />
or<br />
xinit<br />
You should have an '''xterm''' session open up. You can exit the '''X''' Server with Ctrl+Alt+Backspace, or by typing "exit". If you have problems starting '''X''', you can look for errors in the /var/log/Xorg.0.log file and on the console output of the console you started '''X''' from.<br />
<br />
If you prove a properly configured /etc/X11/xorg.conf by successfully running the test, you can be assured that your DE/WM of choice will work smoothly.<br />
<br />
Advanced instructions for Xorg configuration can be found in the [[Xorg]] article.<br />
<br />
==Part III: Installing and configuring a Desktop Environment ==<br />
While The '''X''' Window System provides the basic framework for building a ''graphical user interface'' (GUI), a '''Desktop Environment''' (DE), works atop and in conjunction with '''X''', to provide a completely functional and dynamic GUI. A DE typically provides icons, applets, windows, toolbars, folders, wallpapers, applications and abilities like drag and drop. The particular functionalities and designs of each DE will uniquely affect your overall environment and experience. Therefore, choosing a DE is a very subjective and personal decision. Choose the best environment for ''your'' needs.<br />
<br />
* If you want something full-featured and similar to Windows and Mac OSX, '''[[#KDE|KDE]]''' is a good choice<br />
* If you want something slightly more minimalist, which follows the K.I.S.S. principle more closely, '''[[#GNOME|GNOME]]''' is a good choice<br />
* '''[[#Xfce|Xfce]]''' is generally perceived as similar to GNOME, but lighter and less demanding on system resources, yet still visually pleasing and providing a very complete environment.<br />
* '''[[#LXDE|LXDE]]''' is an even lighter choice than Xfce. It provides the most things you need for a modern desktop while keeping relatively low system resource usage. It's not yet as powerful or as complete as GNOME or Xfce, but it can serve your daily needs well. <br />
<br />
If you desire a lighter, less demanding GUI, you may choose to simply install a '''Window Manager''', or WM. A WM controls the placement and appearance of application windows in conjunction with the X Window System but does NOT provide such additions as panels, applets, icons, applications, etc.<br />
* Lightweight floating WM's include: '''Openbox, Fluxbox, fvwm2''', '''Windowmaker, Pekwm, and TWM'''.<br />
* If you need something completely different, try '''Awesome, ion, wmii, dwm, or xmonad'''.<br />
<br />
===Install Fonts===<br />
At this point, you may wish to install visually pleasing, true type fonts, before installing a desktop environment/window manager. Dejavu and bitstream-vera are good, general-purpose font sets. You may also want to have the Microsoft font sets, which are especially popular on websites. <br />
<br />
Install with:<br />
pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera<br />
<br />
===~/.xinitrc (again)===<br />
<br />
As '''non-root user''', edit your /home/username/.xinitrc to utilize the DE you wish to use. This will allow you to use '''startx/xinit''' from the shell, in the future, to open your DE/WM of choice:<br />
<br />
nano ~/.xinitrc<br />
<br />
Uncomment or add the ''''exec''' ..' line of the appropriate desktop environment/window manager. Some examples are below:<br />
<br />
For the Xfce4 desktop environment:<br />
exec startxfce4 <br />
<br />
For the KDE desktop environment:<br />
exec startkde<br />
A '''startkde''' or '''startxfce4''' command starts the KDE or Xfce4 desktop environment. This command does not finish until you logout of the DE. Normally the shell would wait for KDE to finish, then run the next command. The "exec" prefix to this command tells the shell that this is the last command, so the shell does not need to wait to run a subsequent command.<br />
<br />
Remember to have only one uncommented '''exec''' line in your ~/.xinitrc for now. <br />
<br />
Continue below, installing the DE/WM of your choice.<br />
<br />
===GNOME===<br />
====About GNOME====<br />
The '''G'''NU '''N'''etwork '''O'''bject '''M'''odel '''E'''nvironment. The GNOME project provides two things: The GNOME desktop environment, an intuitive and attractive desktop for end-users, and the GNOME development platform, an extensive framework for building applications that integrate into the rest of the desktop.<br />
<br />
====Installation====<br />
Install the base GNOME environment with:<br />
pacman -S gnome<br />
<br />
Additionally, you can install the extras:<br />
pacman -S gnome-extra<br />
<br />
It's safe to choose all packages shown in the extra package. <br />
<br />
=====Useful DAEMONS for GNOME=====<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. The '''hal''' daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The '''fam''' daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system. Both '''hal''' and '''fam''' make life easier for the GNOME user. The hal and fam packages are installed when you install GNOME, but must be invoked to become useful.<br />
<br />
You may want to install a graphical login manager. For GNOME, the '''gdm''' daemon is a good choice. <br />
<br />
As root:<br />
pacman -S gdm<br />
You will almost certainly want the '''hal''' and '''fam''' daemons.<br />
<br />
Start hal and fam:<br />
/etc/rc.d/hal start<br />
<br />
/etc/rc.d/fam start<br />
<br />
Add them to your /etc/rc.conf DAEMONS section, so they will be invoked on bootup:<br />
nano /etc/rc.conf<br />
<br />
DAEMONS=(syslog-ng network crond alsa '''hal fam gdm''')<br />
(If you prefer to log into the console and manually start X, leave out gdm.)<br />
<br />
<br />
As normal user, start X:<br />
startx<br />
If ~/.xinitrc is not configured for GNOME, you may always start it with '''xinit''':<br />
xinit /usr/bin/gnome-session<br />
You may want to install a terminal and an editor. I would recommend gnome-terminal (part of the group gnome-extra) and geany:<br />
pacman -S geany gnome-terminal<br />
<br />
Advanced instructions for installing and configuring GNOME can be found in the [[Gnome]] article.<br />
<br />
Congratulations! Welcome to your GNOME desktop environment on your new Arch Linux system! You may wish to continue by viewing '''[[#Tweaks/Finishing touches|Tweaks and finishing touches]]''', or the rest of the information below. You may also be interested in the [[Post Installation Tips]] wiki article.<br />
<br />
====Eye Candy====<br />
You may find the default GNOME theme and icons not very attractive. A nice gtk theme is murrine. Install it with<br />
pacman -S gtk-engine-murrine<br />
and select it with System->Preferences->Theme. You can find more themes, icons, and wallpaper at [http://www.gnome-look.org Gnome Look].<br />
<br />
===KDE===<br />
====About KDE====<br />
The '''K''' '''D'''esktop '''E'''nvironment. KDE is a powerful Free Software graphical desktop environment for GNU/Linux and <code>UNIX</code> workstations. It combines ease of use, contemporary functionality, and outstanding graphical design with the technological superiority of <code>UNIX</code>-like operating systems.<br />
<br />
====Installation====<br />
Arch offers several versions of kde: '''kde, kdebase, and KDEmod'''. Choose '''one''' of the following, and continue below with '''[[#Useful KDE DAEMONS|Useful KDE DAEMONS]]''': <br />
<br />
'''1.)''' Package '''kde''' is the complete, vanilla KDE, ~300MB.<br />
pacman -S kde<br />
'''2.)''' Package '''kdebase''' is a slimmed-down version with less applications, ~80MB.<br />
pacman -S kdebase<br />
'''3.)''' Lastly, '''KDEmod''' is an Arch Linux exclusive, community-driven system which is modified for extreme performance and modularity. The KDEmod project website can be found at [http://kdemod.ath.cx/ http://kdemod.ath.cx/]. KDEmod is extremely fast, lightweight and responsive, with a pleasing, customized theme.<br />
<br />
====Useful KDE DAEMONS====<br />
<br />
KDE will require the '''hal''' ('''H'''ardware '''A'''bstraction '''L'''ayer) and '''fam''' ('''F'''ile '''A'''lteration '''M'''onitor) daemons. The '''kdm''' daemon is the '''K''' '''D'''isplay '''M'''anager, which provides a '''graphical login''', if desired.<br />
<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. The hal daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The fam daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system.. Both '''hal''' and '''fam''' make life easier for the KDE user. The hal, fam and kdm packages are installed when you install KDE, but must be invoked to become useful.<br />
-----<br />
Start hal and fam:<br />
<br />
/etc/rc.d/hal start<br />
<br />
/etc/rc.d/fam start<br />
{{Box Note|The hal daemon relies on, and will automatically start, the dbus daemon.}}<br />
Edit your DAEMONS section in /etc/rc.conf:<br />
nano /etc/rc.conf<br />
Add '''hal''' and '''fam''' to your DAEMONS section, to invoke them on bootup. If you prefer a graphical login, add '''kdm''' as well: <br />
DAEMONS=(syslog-ng network crond alsa '''hal fam kdm''')<br />
*This method will start the system at runlevel 3, (/etc/inittab default, multiuser mode), and then start KDM as a daemon. <br />
<br />
*Some users prefer an alternative method of starting a display manager like KDM on bootup by utilizing the /etc/inittab method and starting the system at runlevel 5. See [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]] for more.<br />
<br />
*If you prefer to log into the '''console''' at runlevel 3, and manually start X, leave out kdm, or comment it out with an exclamation. ( ! )<br />
<br />
Now try starting your X Server as normal user:<br />
startx<br />
Advanced instructions for installing and configuring KDE can be found in the [[KDE]] article.<br />
<br />
Congratulations! Welcome to your KDE desktop environment on your new Arch Linux system! You may wish to continue by viewing '''[[#Tweaks/Finishing touches|Tweaks and finishing touches]]''', or the rest of the information below. You may also be interested in the [[Post Installation Tips]] wiki article.<br />
<br />
===Xfce===<br />
====About Xfce====<br />
The cholesterol-free '''X''' environment. Xfce, like GNOME or KDE, is a desktop environment, but aims to be fast and lightweight while remaining visually appealing and easy to use. It contains a suite of apps like a root window app, window manager, file manager, panel, etc. Xfce is written using the GTK2 toolkit (like GNOME) and contains its own development environment (libraries, daemons, etc) similar to other big DEs. Unlike GNOME or KDE, Xfce is lightweight and designed more around CDE than Windows or Mac. It has a much slower development cycle, but is very stable and extremely fast. Xfce is great for older hardware, and will fly with especially great speed on newer machines as well.<br />
<br />
====Installation====<br />
Install Xfce: <br />
pacman -S xfce4 <br />
You may also wish to install themes and extras:<br />
pacman -S xfce4-goodies gtk2-themes-collection<br />
If you want to admire 'Tips and Tricks' on login, you must install the '''fortune-mod''' package:<br />
pacman -S fortune-mod <br />
====Useful DAEMONS====<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. The hal daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The fam daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system. The hal and fam packages are installed when you install Xfce, but must be invoked to become useful.<br />
<br />
Start hal and fam:<br />
<br />
/etc/rc.d/hal start<br />
<br />
/etc/rc.d/fam start<br />
{{Box Note|The hal daemon relies on, and will automatically start, the dbus daemon.}}<br />
Edit your DAEMONS section in /etc/rc.conf:<br />
nano /etc/rc.conf<br />
Add '''hal''' and '''fam''' to your DAEMONS section, to invoke them on bootup.<br />
<br />
Advanced instructions for installing and configuring Xfce can be found in the [[Xfce]] article.<br />
<br />
If you wish to install one, see [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]]<br />
<br />
Congratulations! Welcome to your Xfce desktop environment on your new Arch Linux system! You may wish to continue by viewing '''[[#Tweaks/Finishing touches|Tweaks and finishing touches]]''', or the rest of the information below. You may also be interested in the [[Post Installation Tips]] wiki article.<br />
<br />
===LXDE===<br />
====About LXDE====<br />
LXDE, or Lightweight X11 Desktop Environment, is a new project aimed to provide a new modern desktop environment which is lightweight and fast. It's not designed to be powerful and bloated, but to be usable and slim enough, and keep the resource usage low. Quite different from other known desktop environments, every components of LXDE are not tightly integrated. Most of them can work independently without each other and can be easily replaced with other programs. This modular design eliminates all unnecessary dependencies and provides more flexibility. Go to http://lxde.org/ for details and screenshots.<br />
<br />
====Installation====<br />
Please refer to the official wiki of LXDE. The packages are readily available in arch repo, and there is an updated [http://lxde.org/wiki/ArchLinux installation guide for ArchLinux].<br />
<br />
<br />
===*box===<br />
====Fluxbox====<br />
Fluxbox © is yet another windowmanager for X.<br />
It's based on the Blackbox 0.61.1 code. Fluxbox looks like blackbox and handles styles, colors, window placement and similar things exactly like blackbox (100% theme/style compability).<br />
<br />
Install Fluxbox using <br />
pacman -S fluxbox fluxconf<br />
<br />
If you use gdm/kdm a new fluxbox session will be automatically added. Otherwise, you should modify your user's .xinitrc and add this to it:<br />
exec startfluxbox <br />
<br />
More information is available in the [[Fluxbox]] article.<br />
<br />
====Openbox====<br />
Openbox is a standards compliant, fast, light-weight, extensible window manager.<br />
<br />
Openbox works with your applications, and makes your desktop easier to manage. This is because the approach to its development was the opposite of what seems to be the general case for window managers. Openbox was written first to comply with standards and to work properly. Only when that was in place did the team turn to the visual interface.<br />
<br />
Openbox is fully functional as a stand-alone working environment, or can be used as a drop-in replacement for the default window manager in the GNOME or KDE desktop environments. <br />
<br />
Install openbox using<br />
pacman -S openbox<br />
Additional configuration tools are also available, if desired:<br />
pacman -S obconf obmenu<br />
<br />
Once openbox is installed you will get a message to move menu.xml & rc.xml to ~/.config/openbox/ in your home directory:<br />
<br />
mkdir -p ~/.config/openbox/<br />
cp /etc/xdg/openbox/rc.xml ~/.config/openbox/<br />
cp /etc/xdg/openbox/menu.xml ~/.config/openbox/<br />
<br />
'''rc.xml''' is the main configuration file for OpenBox. It may be manually edited, (or you can use OBconf). '''menu.xml''' configures the right-click menu.<br />
<br />
You may log into OpenBox via graphical login using KDM/GDM, or from the shell using '''startx''', in which case you will need to edit your ~/.xinitrc (as non-root user) and add the following:<br />
<br />
exec openbox-session<br />
You may also start OpenBox from the shell using '''xinit''':<br />
xinit /usr/bin/openbox-session<br />
* Openbox may also be used as the window manager for GNOME, KDE, and Xfce.<br />
For KDM there is nothing left to do; openbox is listed in the sessions menu in KDM.<br />
<br />
Some useful, lightweight programs for OpenBox are:<br />
* PyPanel or LXpanel if you want a panel<br />
* feh if you want to set the background<br />
* ROX if you want a simple file manager (also provides simple icons)<br />
* PcmanFM a lightweight but versatile file manager (also provides desktop icon functionality)<br />
* iDesk (available in [[AUR]]) for providing desktop icons<br />
<br />
More information is available in the [[Openbox]] article.<br />
<br />
===fvwm2===<br />
FVWM is an extremely powerful ICCCM-compliant multiple virtual desktop window manager for the X Window system. Development is active, and support is excellent. <br />
<br />
Install fvwm2 with<br />
pacman -S fvwm <br />
<br />
fvwm will automatically be listed in kdm/gdm in the sessions menu. Otherwise, add <br />
exec fvwm <br />
<br />
to your user's .xinitrc.<br />
<br />
Note that this stable version of fvwm is a few years old. If you want a more recent version of fvwm, there is a fvwm-devel package in the unstable repo.<br />
<br />
=APPENDIX=<br />
==Tweaks/Finishing touches==<br />
===Install an AUR Helper===<br />
[[AUR Helpers]] add seamless access to the [[AUR]]. They vary in their features, but can ease in searching, fetching, building, and installing from over 9000 PKGBUILDs found in AUR.<br />
<br />
===HAL===<br />
Since you have now installed a desktop environment/window manager, and if you did not do so earlier, now would be a good time to also install HAL. HAL allows plug-and-play for your mobile phone, your iPod, your external HD's, etc. It will mount the device and make a nice visual icon on your desktop and/or in 'My Computer', allowing you to access the device after you have plugged it in instead of having to manually configure the /etc/fstab file or udev rules for each and every new device.<br />
<br />
KDE, GNOME and XFCE all use HAL.<br />
<br />
The installation procedure is described in the [[HAL]] article. Some information can also be found at [http://en.wikipedia.org/wiki/HAL_(software) Wikipedia].<br />
<br />
===Backgrounding DAEMONS on startup===<br />
<br />
To speed up system start up procedure, background selected DAEMONS in /etc/rc.conf by prefixing them with a '@' e.g.:<br />
<br />
DAEMONS=(syslog-ng @network crond @alsa @hal @fam @kdm)<br />
This will enable daemons to load in the background, without waiting for the preceding daemon to load first.<br />
<br />
Prefix any daemons which you do not need with a bang (!) e.g.:<br />
<br />
DAEMONS=(syslog-ng @network !netfs !crond @alsa @hal @fam @kdm)<br />
<br />
Alternatively, you may also simply remove unneeded daemons.<br />
<br />
===Beautifying Fonts for LCD's===<br />
See [[Fonts]]<br />
<br />
===Adjusting Mouse for scroll wheel===<br />
While your mouse should be working out of the box, you may want to use your scroll wheel. Add this to your Input Section (mouse0):<br />
Option "ZAxisMapping" "4 5 6 7"<br />
<br />
===Get All Mouse Buttons Working===<br />
See [[Get All Mouse Buttons Working]]<br />
<br />
===Configuring Touchpad for Laptops===<br />
See [[Touchpad Synaptics]]<br />
<br />
===Adjusting Keyboard Layout===<br />
You may want to change your keyboard layout. To do this edit your /etc/X11/xorg.conf and add these lines in the InputDevice Section (Keyboard0) (the example shows a German keyboard layout with no dead keys; alter this to fit your needs).<br />
Option "XkbLayout" "de"<br />
Option "XkbVariant" "nodeadkeys"<br />
<br />
===Additional tweaks for laptops===<br />
ACPI support is needed if you want to use some special functions on your notebook (e.g. sleep, sleep when lid is closed, special keys...). Install <tt>acpid</tt> using<br />
pacman -S acpid<br />
and add it to the daemons in /etc/rc.conf. <tt>acpid</tt> should be started before <tt>hal</tt> and <tt>dbus</tt>, so take care to place it before any calls to hal and dbus. Manually, it can be started by<br />
/etc/rc.d/acpid start<br />
<br />
More-specific information about Arch Linux on various Laptops can be found at [[:Category:Laptops (English)]]<br />
<br />
===Configuring CPU frequency scaling===<br />
Modern processors can decrease their frequency and voltage to reduce heat and power consumption. Less heat leads to a quieter system; Laptop users will definitely want this, but even a desktop system will benefit from it. Install cpufrequtils with<br />
pacman -S cpufrequtils<br />
Edit the config file /etc/conf.d/cpufreq and change <br />
governor="ondemand"<br />
which dynamically increases the CPU frequency if needed (which is a safe choice on desktop systems too). Alter min_freq and max_freq to match your system's CPU spec. If you do not know the frequencies, run ''cpufreq-info'' after loading one of the frequency scaling modules. You can also comment out or delete the min_freq and max_freq lines: things will work automatically. Add the frequency scaling modules to your /etc/rc.conf modules line. Most modern notebooks and desktops can simply use the ''acpi-cpufreq'' driver, however other options include the ''p4-clockmod, powernow-k6, powernow-k7, powernow-k8, and speedstep-centrino'' drivers. Load the module with<br />
modprobe <modulname> <br />
and start cpufreq with<br />
/etc/rc.d/cpufreq start<br />
For more details, see [[Cpufrequtils]]<br />
<br />
===Pm-Utils===<br />
The pm-utils package will allow you to suspend-to-RAM and hibernate: <br />
pacman -S pm-utils<br />
[[Pm-utils]] wiki page.<br />
<br />
===Laptop-Mode===<br />
The laptop-mode-tools package is sort of a one-stop configuration for all laptop power management utilities. It works in conjunction with other installed tools to fully configure everything from hard disk spin-down to X display DPMS standby times, if desired.<br />
pacman -S laptop-mode-tools<br />
Add laptop-mode to your DAEMONS= line in /etc/rc.conf and configure /etc/laptop-mode/laptop-mode.conf.<br />
<br />
==File and directory explanation==<br />
<br />
'''/boot/grub/menu.lst'''<br />
<br />
GRUB is the default bootloader for Arch Linux. You should check and<br />
modify this file to accommodate your boot setup.<br />
<br />
Configuring GRUB is quite easy, the biggest hurdle is that it uses yet<br />
another device naming scheme different from /dev; Your hard disks as a<br />
whole are referred to as (hd0), (hd1), etc., sequentially numbered in<br />
order of appearance on the IDE/SCSI bus, (as dictated by BIOS) just like the sda, sdb, etc.<br />
names in /dev. The partitions of a disk are referred to with (hd0,0),<br />
(hd0,1) and so on, with 0 corresponding to the first entity. A few<br />
conversion examples are included in the default menu.lst to aid your<br />
understanding. <br />
<br />
{{ Box Note | The first appearance of 'root (hdx,x)' may be misleading. The '''root''' command is specifying '''''GRUB''''''s root, which corresponds to ''where the kernel resides, i.e. '''/boot'''''. Ensure that the drive and partition are correct, since '''''/boot''', does not necessarily share the same partition as the root filesystem, or /''.}}<br />
<br />
Once you have grasped the concept of device naming, choose a title for your boot section(s), create a kernel line that includes the partition and path to where the kernel resides, and supply the correct root filesystem device and partition as a parameter to the kernel root option to have it mounted as / on bootup, as well as any boot<br />
parameters. If using the stock Arch 2.6.x kernel, you'll also need an<br />
initrd line that points to the kernel26.img file in your /boot<br />
directory. The path to the initramfs on the initrd line will be the same as<br />
the path to vmlinuz26 that you provide on the kernel line, since both reside under /boot. You should<br />
be fine with the defaults, just check whether the partition<br />
information is correct in the root and kernel lines.<br />
<br />
To create a boot option that loads the bootsector of a different OS,<br />
the following example might be helpful. You will probably succeed in<br />
starting any Microsoft-based operating system with it, just add this<br />
block to the file after any other sections, and modify the partition<br />
device accordingly to refer to the partition containing the bootsector<br />
of the OS you are intending to boot.<br />
(1) Other OS<br />
title My Other OS<br />
rootnoverify (hd0,1)<br />
makeactive<br />
chainloader +1<br />
<br />
For advanced configuration of other OSes, please refer to the online<br />
GRUB manual.<br />
<br />
After checking your bootloader configuration for correctness, you'll<br />
be prompted for a partition to install the loader to. Unless you're<br />
using yet another boot loader, you should install GRUB to the MBR of<br />
the installation disk, which is usually represented by the appropriate<br />
device name without a number suffix.<br />
<br />
'''/etc/conf.d/*'''<br />
<br />
Some daemon scripts will have a matching configuration file in this<br />
directory that contains some more-or-less useful default values. When<br />
a daemon is started, it will first source the settings from it's<br />
config file within this directory, and then source /etc/rc.conf.<br />
Arch's simple, transparent scripting approach means you can easily centralize all your daemon configuration options in your /etc/rc.conf simply by setting an appropriate variable<br />
value, or, split up your configuration over multiple files if you<br />
prefer a decentralized approach to this issue. <br />
<br />
'''/etc/profile'''<br />
<br />
This script is run on each user login to initialize the system. It also globally defines PS1, $PATH, bash aliases, etc. It is kept quite simple under Arch Linux, as most things are. You may wish to edit or customize it to suit your needs.<br />
<br />
==Boot Scripts==<br />
<br />
Arch Linux uses a fairly simple bootup sequence quite similar to *BSDs. The first boot script to run is /etc/rc.sysinit. When it's done, /etc/rc.multi will be called (in a normal bootup). The last script to run will be /etc/rc.local. When started in runlevel 1, the single user mode, the script /etc/rc.single is run instead of /etc/rc.multi. You will not find an endless symlink collection in the /etc/rc?.d/ directories to define the bootup sequence for all possible runlevels. In fact, due to this approach Arch only really has three runlevels, if you take starting up X in runlevel 5 into account. The boot scripts are using the variables and definitions found in the /etc/rc.conf file and also a set of general functions defined in the<br />
/etc/rc.d/functions script. If you plan to write your own daemon<br />
files, you should consider having a look at this file and existing<br />
daemon scripts.<br />
<br />
Boot Script Overview<br />
#/etc/inittab<br />
#/etc/rc.sysinit<br />
#/etc/rc.single<br />
#/etc/rc.multi<br />
#/etc/rc.local<br />
#/etc/rc.shutdown<br />
#/etc/rc.local.shutdown<br />
#/etc/rc.d/*<br />
<br />
'''/etc/inittab'''<br />
<br />
After the kernel is loaded, it looks for the program <code>init</code> which resides at /sbin/init. <code>init</code> reads the file /etc/inittab, which tells it what to do. Looking over the inittab script, you will find that the first uncommented line defines the default system runlevel, or, 3. The next thing it is told to do is to run an initialization script. The program that executes (or interprets) this script is bash, the same program that gives you a command prompt. In Arch Linux, the main initialization script is /etc/rc.sysinit. /etc/inittab also defines your virtual consoles, which are 'respawned' by /sbin/init if terminated. Lastly, inittab defines a login manager, if starting the system at runlevel 5 is desired. The login manager is also respawned by /sbin/init if terminated.<br />
<br />
'''/etc/rc.sysinit'''<br />
<br />
The main system boot script, which mounts filesystems, runs udev, activates swap, loads modules, sets localization parameters, etc. <br />
<br />
'''/etc/rc.single'''<br />
<br />
Single-user startup. Not used in a normal boot-up. If the system is started in single-user mode, for example with the kernel parameter 1 before booting or during normal multi-user operation with the command init 1, this script makes sure no daemons are running except for the bare minimum; syslog-ng and udev. The single-user mode is useful if you need to make any changes to the system while making sure that no remote user can do anything that might cause data loss or damage. <br />
For desktop users, this mode is usually quite useless.<br />
<br />
'''/etc/rc.multi'''<br />
<br />
Multi-user startup script. It starts all daemons you configured in the DAEMONS array (set in /etc/rc.conf) after which it calls /etc/rc.local. <br />
<br />
'''/etc/rc.local'''<br />
<br />
Local multi-user startup script. It is a good place to put any last-minute commands you want the system to run at the very end of the bootup process. Most common system configuration tasks, like loading modules, changing<br />
the console font or setting up devices, usually have a dedicated place where they belong. To avoid confusion, you should make sure that whatever you intend to add to your rc.local is not already residing in /etc/profile.d/, or any other already existing config location instead.<br />
<br />
'''/etc/rc.shutdown''' <br />
<br />
System shutdown script. It stops daemons, unmounts filesystems, deactivates the swap, etc. <br />
<br />
'''/etc/rc.local.shutdown''' (Optional)<br />
<br />
Analogous to the /etc/rc.local file, this file may contain any commands you want to run right before the common rc.shutdown is executed. Please note that this file does not exist by default, and for it to work properly, it must be set as executable.<br />
<br />
<br />
'''/etc/rc.d/*'''<br />
<br />
This directory contains the daemon scripts referred to from the rc.conf's DAEMONS= array. In addition to being called on bootup, you can use these scripts when the system is running to manage the services of your system. For example the command<br />
/etc/rc.d/postfix stop<br />
<br />
will stop the postfix daemon. This directory is not in the $PATH by default, but may be added for convenience. Obviously a corresponding daemon script only exists when the appropriate package has been installed (in this case postfix). With a base system install, there are few scripts in here, but rest assured that all relevant daemon scripts end up here. If you wish, you can, of course, create your own scripts and place them here, to be called by the DAEMONS= array in /etc/rc.conf on system startup. <br />
<br />
This directory is pretty much the equivalent to the /etc/rc3.d/ or /etc/init.d/ directories of other distributions, but without all the symlink hassle. The lack of symlink requirement is a defining difference of a *BSD-style init framework, vs a sysvinit.<br />
<br />
==Useful Applications==<br />
This section will never be complete. It just shows some good applications for the everyday user. <br />
<br />
'''KDE users NOTE''': Since KDE resides in /opt, you will most likely have to log out and in after initial installation to update your PATH before these programs can be used.<br />
===Internet===<br />
<br />
=====Firefox=====<br />
The ever-popular Firefox web browser is available through pacman, although it doesnt have its official branding, so the program appears when opened as Mindfield. Install with:<br />
<br />
pacman -S firefox<br />
Be sure and install 'flashplugin', 'mplayer', 'mplayer-plugin', and the 'codecs' packages for a complete web experience:<br />
pacman -S flashplugin mplayer mplayer-plugin codecs<br />
(The codecs package contains codecs for Quicktime and Realplayer content.)<br />
<br />
Thunderbird is useful for managing your emails. If you are using GNOME you may want to take a look at Epiphany and Evolution; if you are using KDE Konqueror and KMail could be your choice. If you want something completely different you can still use Opera. Finally, if you are working on the system console - or in a terminal session - you could use various text-based browsers like ELinks, Links and Lynx, and manage your emails with [[Mutt]]. Pidgin (previously known as Gaim) and Kopete are good instant messengers for GNOME and KDE, respectively. PSI and Gajim are perfect if you are using only Jabber or Google Talk.<br />
<br />
===Office===<br />
OpenOffice is a complete office suite (similar to Microsoft Office). Abiword is a good, small alternative word processor, and Gnumeric an Excel replacement for the GNOME desktop. KOffice is a complete office suite for the KDE Desktop. GIMP (or GIMPShop) is a pixel-based graphics program (similar to Adobe Photoshop), while Inkscape is a vector-based graphics program (like Adobe Illustrator). And, of course, Arch comes with a full set of LaTeX Programs: tetex has been popular for many years and still works, and its successor [[Texlive]] is available from the [[AUR]] repository.<br />
<br />
==Multimedia ==<br />
<br />
<br />
===Video Player===<br />
====VLC====<br />
VLC Player is a multimedia player for Linux. To install it, simply type the code below.<br />
<br />
pacman -S vlc<br />
<br />
(TODO) Instructions for VLC mozilla plug-in<br />
<br />
====Mplayer====<br />
MPlayer is a multimedia player for Linux. To install it, simply type the code below.<br />
<br />
pacman -S mplayer<br />
<br />
It also has a Mozilla plug-in for videos and streams embedded in web pages. To install it, simply type the code below.<br />
<br />
pacman -S mplayer-plugin<br />
<br />
If you use KDE, KMplayer is a better choice. It comes with a plug-in for videos and streams embedded in web pages, which works with Konqueror. To install it, simply type the code below.<br />
<br />
pacman -S kmplayer<br />
<br />
(TODO) GMPlayer instructions<br />
<br />
====Xine====<br />
<br />
Xine is an excellent player, especially for DVDs.<br />
<br />
pacman -S xine-ui<br />
The libdvdcss library provides DVD decoding for encrypted DVDs. ''Ensure the legality of using libdvdcss in your country before installing!''<br />
pacman -S libdvdcss<br />
<br />
====GNOME====<br />
=====Totem=====<br />
[http://www.gnome.org/projects/totem/ Totem] is the official movie player of the GNOME desktop environment based on xine-lib or GStreamer (gstreamer is the default which installs with the arch totem package). It features a playlist, a full-screen mode, seek and volume controls, as well as keyboard navigation.<br />
It comes with added functionality such as:<br />
<br />
* Video thumbnailer for the file manager<br />
* Nautilus properties tab<br />
* Epiphany / Mozilla (Firefox) plugin to view movies inside your browser <br />
* Webcam utility (in development)<br />
<br />
Totem-xine is still the better choice if you want to watch DVDs.<br />
<br />
Totem is part of the gnome-extra group; the Totem webbrowser plugin is not.<br />
<br />
To install separately:<br />
pacman -S totem<br />
<br />
To install the Totem webbrowser plugin:<br />
pacman -S totem-plugin<br />
<br />
====KDE====<br />
=====Kaffeine=====<br />
Kaffeine is a good option for KDE users. To install it, simply type the code below.<br />
<br />
pacman -S kaffeine<br />
<br />
===Audio Player===<br />
====Gnome/Xfce====<br />
=====Exaile=====<br />
[[Exaile]] is a music player written in Python that makes use of the GTK+ toolkit. It tries to be close to the popular Amarok, but in GTK. It is in [community], so install with:<br />
pacman -S exaile<br />
<br />
=====Rhythmbox=====<br />
[http://www.gnome.org/projects/rhythmbox/ Rhythmbox] is an integrated music management application, originally inspired by Apple's iTunes. It is free software, designed to work well under the GNOME Desktop, and based on the powerful GStreamer media framework.<br />
<br />
Rhythmbox has a number of features, including:<br />
<br />
* Easy-to-use music browser<br />
* Searching and sorting<br />
* Comprehensive audio format support through GStreamer<br />
* Internet radio support<br />
* Playlists<br />
<br />
To install rhythmbox:<br />
pacman -S rhythmbox<br />
<br />
=====Quod Libet=====<br />
[http://www.sacredchao.net/quodlibet Quod Libet] is a music manager that uses the GStreamer media framework to play audio files. This allows it to play all the file-types that Rhythmbox (which uses GStreamer too) can play. Quod Libet is more suited to non-Gnome desktops since it has a smaller footprint and fewer dependencies than Rhythmbox (Rhythmbox depends on nautilus, which requires a lot of GNOME to be installed).<br />
<br />
In addition to the music player/manager, Quod Libet also includes Ex Falso, a tag editor.<br />
<br />
Quod Libet's features include:<br />
<br />
* Easy-to-use music browser<br />
* Searching<br />
* Comprehensive audio format support through GStreamer<br />
* Easy Playlist management<br />
<br />
To install Quod Libet:<br />
pacman -S quodlibet<br />
<br />
Other good audio players are Banshee and Listen. See [http://gnomefiles.org/ Gnomefiles] to compare them.<br />
<br />
====KDE====<br />
=====Amarok=====<br />
[http://amarok.kde.org/ Amarok] is one of the best audio players and music library systems available for KDE. To install it, simply type the code below.<br />
<br />
pacman -S amarok-base<br />
<br />
====Console====<br />
[http://moc.daper.net/ Moc] is a ncurses-based audio player for the console; another good choice is [http://musicpd.org/ mpd].<br />
<br />
Another excellent choice is [http://freshmeat.net/projects/cmus/ cmus].<br />
<br />
====Other X-based====<br />
(TODO) Xmms, audacious, bmpx.<br />
<br />
===Codecs and other multimedia content types (i686 only) ===<br />
====DVD====<br />
You can use xine-ui, totem-xine, mplayer or kaffeine (just to name three of the big ones) to watch DVDs. The only thing you may miss is libdvdcss. Beware that using it may be illegal in some countries.<br />
<br />
====Flash====<br />
Install the flash plugin using<br />
pacman -S flashplugin<br />
to enable Macromedia (now Adobe) Flash in your browser, if you run KDE you should see this after installing flash. http://wiki.archlinux.org/index.php/Flash_and_Adobe_Acrobat_browser_plugins#Fixing_Flash_in_Konqueror<br />
<br />
====Quicktime====<br />
Quicktime codecs are contained in the codecs package. Just type<br />
pacman -S codecs<br />
to install them.<br />
====Realplayer====<br />
The codec for Realplayer 9 is contained in the codecs package. Just type<br />
pacman -S codecs<br />
to install them. Realplayer 10 is available as a binary package for Linux. You can get it from AUR [http://aur.archlinux.org/packages.php?do_Details=1&ID=1590&O=0&L=0&C=0&K=realplay&SB=&SO=&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd here].<br />
<br />
===CD and DVD Burning===<br />
====GNOME====<br />
=====Brasero=====<br />
[http://www.gnome.org/projects/brasero/ Brasero] is an application that burns CDs/DVDs for the GNOME Desktop. It is designed to be as simple as possible and has some unique features to enable users to create their discs easily and quickly.<br />
<br />
To install:<br />
pacman -S brasero<br />
<br />
====KDE====<br />
=====K3b=====<br />
K3b (from '''K'''DE '''B'''urn '''B'''aby '''B'''urn) is a free software CD and DVD authoring application for GNU/Linux and other <code>UNIX</code>-like operating systems designed for KDE. As is the case with most KDE applications, K3b is written in the C++ programming language and uses the Qt GUI toolkit. K3b provides a graphical user interface to perform most CD/DVD burning tasks like creating an Audio CD from a set of audio files or copying a CD/DVD, as well as more advanced tasks such as burning eMoviX CD/DVDs. It can also perform direct disc-to-disc copies. The program has many default settings which can be customized by more experienced users. The actual disc recording in K3b is done by the command line utilities cdrecord or wodim, cdrdao, and growisofs. As of version 1.0, K3b features a built-in DVD ripper.- licensed under the GPL.<br />
<br />
K3b was voted LinuxQuestions.org's Multimedia Utility of the Year (2006) by the majority (70%) of voters. <br />
-----<br />
To install:<br />
pacman -S k3b<br />
<br />
=====(Todo) cdrecord, graveman...=====<br />
<br />
<br />
<br />
<br />
Most CD burners are wrappers for cdrecord:<br />
<br />
pacman -S cdrkit<br />
<br />
If you install packages for CD/DVD burning applications like Brasero or K3B it also installs the CD/DVD burning library for it, like libburn or cdrkit.<br />
<br />
A good command-line DVD-burning tool is growisofs:<br />
<br />
pacman -S dvd+rw-tools<br />
<br />
===TV-Cards===<br />
<br />
There are several things to do if you want to watch TV under (Arch) Linux. The most important task is to find out which chip your tuner is using. However, quite a lot are supported. Be sure to check at a Hardware Database to be sure (see [http://en.opensuse.org/HCL/TV_Cards this list], for example). Once you know your Model, there are just a few steps ahead to get you going.<br />
<br />
In most cases, you will need to use the bttv-drivers (other drivers exist, like [http://linux.bytesex.org/v4l2/drivers.html V4L]) together with the I2C-modules. Configuring those is the hardest task. If you are lucky, a<br />
modprobe bttv<br />
will autodetect the card (check dmesg for results). In that case, you need only to install an application to watch TV. We will look at that later, though.<br />
If the autodetection did not work, you will need to check the file CARDLIST, which is included in the tarball of [http://dl.bytesex.org/releases/video4linux/ bttv] to find out the right parameters for your card. A PV951 without radio support would need this line:<br />
modprobe bttv card=42 radio=0<br />
Some cards need the following line to produce sound:<br />
modprobe tvaudio<br />
However, that varies. So just try it out. Some other cards demand the following line:<br />
modprobe tuner<br />
This is subject to trial-and-error, too.<br />
<br />
TODO: clarify the installation-procedure<br />
<br />
To actually watch TV, install the xawtv-package with<br />
pacman -S xawtv <br />
and read its manpage.<br />
<br />
TODO: clarify some possible problems and procedures. Introduction to XAWTV on another page?<br />
<br />
===Digital Cameras===<br />
Most newer digital cameras are supported as USB mass storage devices, which means that you can simply plug it in and copy the images. Older cameras may use the PTP (Picture Transfer Protocol) which requires a "special driver". gPhoto2 provides this driver and allows a shell-based transfer of the images; digikam (for KDE) and gthumb (for GNOME, gtkam would be another choice) use this driver and offer a nice GUI.<br />
<br />
===USB Memory Sticks / Hard Disks===<br />
USB Memory Sticks and hard disks are supported out of the box with the USB mass storage device driver and will appear as a new SCSI device (/dev/sdX). If you are using KDE or GNOME you should use dbus and hal (add them to your daemons in /etc/rc.conf), and they will be automatically mounted. If you use a different Desktop Environment you may have a look at ivman.<br />
<br />
==Maintaining the system==<br />
===Pacman===<br />
[[Pacman]] is both a binary and source package manager which is able to download, install, and upgrade packages from both remote and local repositories with full dependency handling, and has easy-to-understand tools for crafting your own packages too.<br />
<br />
A more-detailed description of Pacman can be found in [[Pacman|its article]].<br />
<br />
====Useful commands====<br />
To view the options available for a particular operational command, say '''-Q''', just append it with '''-h''':<br />
pacman -Qh<br />
<br />
To synchronize and update the local packages database with the remote repositories (it is a good idea to do this before installing and upgrading packages):<br />
pacman -Sy<br />
<br />
To '''upgrade''' all packages on the system:<br />
pacman -Su<br />
<br />
To sync, update, and '''upgrade''' all the packages on the system with one command:<br />
pacman -Syu<br />
<br />
To install or upgrade a single package or list of packages (including dependencies):<br />
pacman -S packageA packageB<br />
<br />
You can also sync, update the package database, and install packages in one command:<br />
pacman -Sy packageA packageB<br />
<br />
To remove a single package, leaving all of its dependencies installed:<br />
pacman -R package<br />
<br />
To remove a package and all of the package's dependencies which are not used by any other installed package:<br />
pacman -Rs package<br />
('''-Rs''' is typically preferred vs '''R''' to remove any package as it will clean up all unused dependencies)<br />
<br />
To remove all of the package's now unneeded dependencies and also instruct pacman to ignore file backup designations. (Normally, when a file is removed from the system the database is checked to see if the file should be renamed with a ".pacsave" extension.):<br />
pacman -Rsn package<br />
<br />
To search the remote (repo) package database for a list of packages matching a given keyword:<br />
pacman -Ss keyword<br />
<br />
To list all packages on your system<br />
pacman -Q<br />
<br />
To list all packages on your system without the version strings, we add the '''-q''' option:<br />
pacman -Qq<br />
<br />
To search (query) the local (your machine) package database for a given package:<br />
pacman -Q package <br />
<br />
To search (query) the local (your machine) package database for a given package and list all pertinent information:<br />
pacman -Qi package<br />
<br />
To list all files installed by a given ''package'':<br />
<tt>pacman -Ql ''package''</tt><br />
Conversely, to find the package that owns a given file (in this example, the ''ls'' executable):<br />
<tt>pacman -Qo /bin/ls</tt><br />
To find all unused packages (orphans):<br />
pacman -Qdt<br />
Missing libraries: Suppose you receive an error message like this:<br />
<tt>mplayer: error while loading shared libraries: ''libgssapi.so.2'': cannot open shared object file: No such file or directory</tt><br />
This may be an indication that a package you have previously installed is now corrupt (some or all of its files are missing). You should try to find the package name that provides the missing shared library. In this example, you could type:<br />
<tt>pacman -Ql | grep ''libgssapi.so.2''</tt><br />
The first column in the output is the package name:<br />
<tt>heimdal /usr/lib/libgssapi.so.2<br />
heimdal /usr/lib/libgssapi.so.2.0.0<br />
</tt><br />
Then, you can just re-install it:<br />
<tt>pacman -Sy heimdal</tt><br />
<br />
To defragment pacman's cache database and optimize for speed:<br />
pacman-optimize<br />
<br />
To count how many packages are currently on your system:<br />
pacman -Q | wc -l<br />
<br />
To install a package compiled from source using ABS and makepkg:<br />
pacman -U packagename.pkg.tar.gz<br />
<br />
Note: There are countless additional pacman functions and commands. Try man pacman and consult the [[pacman]] wiki entries.<br />
<br />
====Files====<br />
There are a number of files left and created by pacman and other programs to facilitate maintenance and to conform to a safe computing practice. When pacman is installing something, the package contains information on whether to back up a particular file. Such files will have the '''.pacsave''' extension. When you force a "NoUpgrade" on a file via [http://www.archlinux.org/pacman/pacman.conf.5.html pacman.conf], it will not be replaced during an upgrade and the new file will come with the '''.pacnew''' extension. For example, you have edited a configuration file thoroughly and you do not want an upgrade of the respective package to replace the file with a new one, we must have the following line in '''/etc/pacman.conf''':<br />
NoUpgrade = /path/to/config/file<br />
To view the differences of the old and new versions of these files, we can either edit them manually or use a '''diff''' utility to take note of the differences. There is an automated tool to find and view such files available from the '''community''' repository:<br />
pacman -S pacman-contrib<br />
cd ~/<br />
pacdiff # as root<br />
There is a bug in the above tool where if you navigate to '''/etc''' and run it from there, the paths will be messed up. We remain on the safer side by being at "home". You may want to run it as user first in case you happen to be a careless person (you may just overwrite or remove files because you ''think'' that is the right way).<br><br />
<br />
There are other types of leftovers depending on the programs available on your system. Some will create backups with a '''.bak''' extension, while others with something like "'''~'''" or "'''-'''". Unfortunately, there is currently no way to "automatically" find and review them. Fear not, as we have no need for automated tools to deal with such trivial tasks. Simply use '''locate''' to search for them:<br />
locate -e *.~ *.- *.bak<br />
And we can use something useful like '''vimdiff''' to look at the differences manually:<br />
pacman -S vim<br />
vimdiff file1 file2<br />
<br />
==Polishing & Further information==<br />
For further information and support you can go to the [http://www.archlinux.org/ homepage], [[Special:Search|search the wiki]], the [http://bbs.archlinux.org/ forums], the [[ArchChannel|IRC channel]], and the [http://www.archlinux.org/mailman/listinfo/ mailing lists].<br />
=====FAQs=====<br />
See [[Arch FAQs for newbies]]<br />
<br />
There is also an [http://bbs.archlinux.org/viewforum.php?id=23 Arch Subforum] devoted to beginners.<br />
<br />
=====Terminology=====<br />
For more information on the jargon used in Arch, look at [[Arch Terminology/Jargon for newbies|this article]].<br />
<br />
=====Where to go from here?=====<br />
<br />
You may also be interested in:<br />
<br />
[[Post Installation Tips]]<br />
<br />
[[ArchLinux User-community Repository (AUR)]]<br />
<br />
[[Get All Mouse Buttons Working]]<br />
<br />
[[Improve Pacman Performance]]<br />
<br />
[[Kernel Compilation]]<br />
<br />
[[Pm-utils]]<br />
<br />
[[Cpufrequtils]]<br />
<br />
[[:Category:Eye candy (English)| Eye Candy]]<br />
<br />
==External links==<br />
* [http://archux.com/page/installation-guide/ Arch Linux installation guide with images and videos]</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=44300
User:Faelar
2008-07-06T10:53:54Z
<p>Faelar: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
{{Navigate_i18n_mainpages}}<br />
<br />
== Guides d'Installation ==<br />
'''Si vous êtes nouveau sur Arch, le [[Beginners Guide|Manuel du débutant (en)]] devrait-être approprié,''' ou alors essayez '''le [[Official Arch Linux Install Guide|Guide Officiel d'Installation (en)]], qui vise les utilisateurs GNU/Linux confirmés.<br />
<br />
Vous pourriez également être intéressé par : [[Post Installation Tips|Les Astuces Post-Installation (en)]] :: [[Configuring network|La Configuration du Réseau (en)]]<br />
== Pages Utiles ==<br />
<br />
Voici un extrait de quelques unes des pages les plus utiles du Wiki. <br />
<br />
==== &nbsp;&nbsp;[[Table_des_matières_(Français)|Table des Matières]] ====<br />
<br />
==== &nbsp;&nbsp;[[:Category:À_propos_d'Arch_(Français)|À propos d'Arch]] ====<br />
: [[ArchLinux_(Français)|Qu'est-ce qu'Arch Linux ?]] :: [[The_Arch_Way_(Français)|L'Esprit d'Arch]] :: [[Arch_Comparée_Aux_Autres_Distros|Arch Comparée Aux Autres Distributions]] :: [[FAQ_(Français)|FAQ]] :: [[Official Repositories|Les Dépôts Officiels (en)]] :: [[ArchLinux User-community Repository (AUR)|Le Dépôt Communautaire d'Arch (AUR) (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Administration_du_système_(Français)|Administration du Système]] ====<br />
: [[Pacman_(Français)|Pacman]] :: [[:Category: Package management (English)|Gestion des Paquets (en)]] :: [[Xorg|Configuration de Xorg (en)]] :: [[:Category: Desktop environments (English)|Environments de Bureau (en)]] :: [[ALSA|ALSA (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Guide_de_l'utilisateur_de_bureau_(Français)|Guide de l'utilisation Bureautique]] ====<br />
: [[:Category: Internet and Email (English)|Internet et Email (en)]] :: [[:Category: Office (English)|Bureautique (en)]] :: [[:Category: Audio/Video (English)|Audio/Vidéo (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Remise_en_état_du_système_(Français)|Remise en état du Sytème]] ====<br />
: [[Reinstalling GRUB|Réinstaller GRUB (en)]] :: [[Kernel Panics|Kernel Panics (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Développement_d'Arch_(Français)|Développement d'Arch]] ====<br />
: [[Community Projects|Projets de la Communauté (en)]] :: [[:Category: Live Arch systems (English)|Systèmes Arch "Live" (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Arch64 (English)|Arch64 (en)]] ====<br />
: [[Arch64 FAQ|Arch64 FAQ (en)]]<br />
<br />
== Les Nouvelles du Wiki ==<br />
<br />
Consultez la page des [[Wiki News|Nouvelles du Wiki (en)]] pour les derniers tuyaux du Wiki.<br />
<br />
Si vous avez un peu de temps pour des modifications mineures ou majeures, jettez un oeil à the [[Priority Todo]] and the [[WikiTodo]] pages pour voir comment vous pourriez aider. Nous sommes particulièrment intéressé in having people réorganiser pages non-Anglaises. S'il vous plait coordonnez vos actions avec les [[ContactList|admins et sysops]] ou les [[ArchWiki maintainers (English)|maintainers]].<br />
<br />
== Dans votre Langue ==<br />
Plus à l'aise reading articles dans votre propre langue ? Parcourez les catégories dans les langues suivantes : <br />
: [[:Category:English|English]] :: [[:Category:Česky|Česky]] :: [[:Category:Deutsch|Deutsch]] :: [[:Category:Français|Français]] :: [[:Category:Italiano|Italiano]] :: [[:Category:Lietuviškai|Lietuviškai]] :: [[:Category:Polski|Polski]] :: [[:Category:Русский|Русский]] ::[[:Category:Українська|Українська]] :: [[:Category:Српски|Српски]] :: [[:Category:ไทย|ไทย]] :: [[:Category:简体中文|简体中文]] :: [[:Category:正體中文|正體中文]]<br />
<br />
== Aide ==<br />
Si vous avez des difficultés à trouver ce que vous cherchez, essayez d'utiliser la fonction de recherche sur la gauche.<br />
<br />
Vous devez créer un compte pour éditer ce Wiki. Une fois terminé, vous pourrez jouer un peu dans le [[Sandbox|Bac-à-sable]] ou avec votre page utilisateur pour vous familiariser avec la synthaxe (markup) du ArchWiki. The available syntax is listed in the [[:Category:Help|Wiki Help Category]] and there is an [[:Category:ArchWiki Tools (English)|Archwiki Tools section]] with some HOWTOs and guidelines.</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=44299
User:Faelar
2008-07-06T10:51:38Z
<p>Faelar: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
{{Navigate_i18n_mainpages}}<br />
<br />
== Guides d'Installation ==<br />
'''Si vous êtes nouveau sur Arch, le [[Beginners Guide|Manuel du débutant (en)]] devrait-être approprié,''' ou alors essayez '''le [[Official Arch Linux Install Guide|Guide Officiel d'Installation (en)]], qui vise les utilisateurs GNU/Linux confirmés.<br />
<br />
Vous pourriez également être intéressé par : [[Post Installation Tips|Les Astuces Post-Installation (en)]] :: [[Configuring network|La Configuration du Réseau (en)]]<br />
== Pages Utiles ==<br />
<br />
Voici un extrait de quelques unes des pages les plus utiles du Wiki. <br />
<br />
==== &nbsp;&nbsp;[[Table_des_matières_(Français)|Table des Matières]] ====<br />
<br />
==== &nbsp;&nbsp;[[:Category:À_propos_d'Arch_(Français)|À propos d'Arch]] ====<br />
: [[ArchLinux_(Français)|Qu'est-ce qu'Arch Linux ?]] :: [[The_Arch_Way_(Français)|L'Esprit d'Arch]] :: [[Arch_Comparée_Aux_Autres_Distros|Arch Comparée Aux Autres Distributions]] :: [[FAQ_(Français)|FAQ]] :: [[Official Repositories|Les Dépôts Officiels (en)]] :: [[ArchLinux User-community Repository (AUR)|Le Dépôt Communautaire d'Arch (AUR) (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Administration_du_système_(Français)|Administration du Système]] ====<br />
: [[Pacman_(Français)|Pacman]] :: [[:Category: Package management (English)|Gestion des Paquets (en)]] :: [[Xorg|Configuration Xorg (en)]] :: [[:Category: Desktop environments (English)|Environments de Bureau (en)]] :: [[ALSA|ALSA (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Guide_de_l'utilisateur_de_bureau_(Français)|Guide de l'utilisation Bureautique]] ====<br />
: [[:Category: Internet and Email (English)|Internet et Email (en)]] :: [[:Category: Office (English)|Bureautique (en)]] :: [[:Category: Audio/Video (English)|Audio/Vidéo (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Remise_en_état_du_système_(Français)|Remise en état du Sytème]] ====<br />
: [[Reinstalling GRUB|Réinstaller GRUB (en)]] :: [[Kernel Panics|Kernel Panics (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Développement_d'Arch_(Français)|Développement d'Arch]] ====<br />
: [[Community Projects|Projets de la Communauté (en)]] :: [[:Category: Live Arch systems (English)|Systèmes Arch "Live" (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Arch64 (English)|Arch64 (en)]] ====<br />
: [[Arch64 FAQ|Arch64 FAQ (en)]]<br />
<br />
== Les Nouvelles du Wiki ==<br />
<br />
Consultez la page des [[Wiki News|Nouvelles du Wiki (en)]] pour les derniers tuyaux du Wiki.<br />
<br />
Si vous avez un peu de temps pour des modifications mineures ou majeures, jettez un oeil à the [[Priority Todo]] and the [[WikiTodo]] pages pour voir comment vous pourriez aider. Nous sommes particulièrment intéressé in having people réorganiser pages non-Anglaises. S'il vous plait coordonnez vos actions avec les [[ContactList|admins et sysops]] ou les [[ArchWiki maintainers (English)|maintainers]].<br />
<br />
== Dans votre Langue ==<br />
Plus à l'aise reading articles dans votre propre langue ? Parcourez les catégories dans les langues suivantes : <br />
: [[:Category:English|English]] :: [[:Category:Česky|Česky]] :: [[:Category:Deutsch|Deutsch]] :: [[:Category:Français|Français]] :: [[:Category:Italiano|Italiano]] :: [[:Category:Lietuviškai|Lietuviškai]] :: [[:Category:Polski|Polski]] :: [[:Category:Русский|Русский]] ::[[:Category:Українська|Українська]] :: [[:Category:Српски|Српски]] :: [[:Category:ไทย|ไทย]] :: [[:Category:简体中文|简体中文]] :: [[:Category:正體中文|正體中文]]<br />
<br />
== Aide ==<br />
Si vous avez des difficultés à trouver ce que vous cherchez, essayez d'utiliser la fonction de recherche sur la gauche.<br />
<br />
Vous devez créer un compte pour éditer ce Wiki. Une fois terminé, vous pourrez jouer un peu dans le [[Sandbox|Bac-à-sable]] ou avec votre page utilisateur pour vous familiariser avec la synthaxe (markup) du ArchWiki. The available syntax is listed in the [[:Category:Help|Wiki Help Category]] and there is an [[:Category:ArchWiki Tools (English)|Archwiki Tools section]] with some HOWTOs and guidelines.</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=44277
User:Faelar
2008-07-06T00:24:39Z
<p>Faelar: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
{{Navigate_i18n_mainpages}}<br />
<br />
== Guides d'Installation ==<br />
'''Si vous êtes nouveau sur Arch, le [[Beginners Guide|Manuel du débutant (en)]] devrait-être approprié,''' ou alors essayez '''le [[Official Arch Linux Install Guide|Guide Officiel d'Installation (en)]], qui vise les utilisateurs GNU/Linux confirmés.<br />
<br />
Vous pourriez également être intéressé par : [[Post Installation Tips|Les Astuces Post-Installation (en)]] :: [[Configuring network|La Configuration du Réseau (en)]]<br />
== Pages Utiles ==<br />
<br />
Voici un extrait de quelques unes des pages les plus utiles du Wiki. <br />
<br />
==== &nbsp;&nbsp;[[Table_des_matières_(Français)|Table des Matières]] ====<br />
<br />
==== &nbsp;&nbsp;[[:Category:À_propos_d'Arch_(Français)|À propos d'Arch]] ====<br />
: [[ArchLinux_(Français)|Qu'est-ce qu'Arch Linux ?]] :: [[The_Arch_Way_(Français)|L'Esprit d'Arch]] :: [[Arch_Comparée_Aux_Autres_Distros|Arch Comparée Aux Autres Distributions]] :: [[FAQ_(Français)|FAQ]] :: [[Official Repositories|Les Dépôts Officiels (en)]] :: [[ArchLinux User-community Repository (AUR)|Le Dépôt Communautaire d'Arch (AUR) (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Administration_du_système_(Français)|Administration du Système]] ====<br />
: [[Pacman_(Français)|Pacman]] :: [[:Category: Package management (English)|Gestion des Paquets (en)]] :: [[Xorg|Configuration Xorg (en)]] :: [[:Category: Desktop environments (English)|Environments de Bureau (en)]] :: [[ALSA|ALSA (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Guide_de_l'utilisateur_de_bureau_(Français)|Guide de l'utilisation Bureautique]] ====<br />
: [[:Category: Internet and Email (English)|Internet et Email (en)]] :: [[:Category: Office (English)|Bureautique (en)]] :: [[:Category: Audio/Video (English)|Audio/Vidéo (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Remise_en_état_du_système_(Français)|Remise en état du Sytème]] ====<br />
: [[Reinstalling GRUB|Réinstaller GRUB (en)]] :: [[Kernel Panics|Kernel Panics (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Développement_d'Arch_(Français)|Développer d'Arch]] ====<br />
: [[Community Projects|Projets de la Communauté (en)]] :: [[:Category: Live Arch systems (English)|Systèmes Arch "Live" (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Arch64 (English)|Arch64 (en)]] ====<br />
: [[Arch64 FAQ|Arch64 FAQ (en)]]<br />
<br />
== Les Nouvelles du Wiki ==<br />
<br />
Consultez la page des [[Wiki News|Nouvelles du Wiki (en)]] pour les derniers tuyaux du Wiki.<br />
<br />
Si vous avez un peu de temps pour des modifications mineures ou majeures, jettez un oeil à the [[Priority Todo]] and the [[WikiTodo]] pages pour voir comment vous pourriez aider. Nous sommes particulièrment intéressé in having people réorganiser pages non-Anglaises. S'il vous plait coordonnez vos actions avec les [[ContactList|admins et sysops]] ou les [[ArchWiki maintainers (English)|maintainers]].<br />
<br />
== Dans votre Langue ==<br />
Plus à l'aise reading articles dans votre propre langue ? Parcourez les catégories dans les langues suivantes : <br />
: [[:Category:English|English]] :: [[:Category:Česky|Česky]] :: [[:Category:Deutsch|Deutsch]] :: [[:Category:Français|Français]] :: [[:Category:Italiano|Italiano]] :: [[:Category:Lietuviškai|Lietuviškai]] :: [[:Category:Polski|Polski]] :: [[:Category:Русский|Русский]] ::[[:Category:Українська|Українська]] :: [[:Category:Српски|Српски]] :: [[:Category:ไทย|ไทย]] :: [[:Category:简体中文|简体中文]] :: [[:Category:正體中文|正體中文]]<br />
<br />
== Aide ==<br />
Si vous avez des difficultés à trouver ce que vous cherchez, essayez d'utiliser la fonction de recherche sur la gauche.<br />
<br />
Vous devez créer un compte pour éditer ce Wiki. Une fois terminé, vous pourrez jouer un peu dans le [[Sandbox|Bac-à-sable]] ou avec votre page utilisateur pour vous familiariser avec la synthaxe (markup) du ArchWiki. The available syntax is listed in the [[:Category:Help|Wiki Help Category]] and there is an [[:Category:ArchWiki Tools (English)|Archwiki Tools section]] with some HOWTOs and guidelines.</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=44276
User:Faelar
2008-07-06T00:22:04Z
<p>Faelar: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
{{Navigate_i18n_mainpages}}<br />
<br />
== Guides d'Installation ==<br />
'''Si vous êtes nouveau sur Arch, le [[Beginners Guide|Manuel du débutant (en)]] devrait-être approprié,''' ou alors essayez '''le [[Official Arch Linux Install Guide|Guide Officiel d'Installation (en)]], qui vise les utilisateurs GNU/Linux confirmés.<br />
<br />
Vous pourriez également être intéressé par : [[Post Installation Tips|Les Astuces Post-Installation (en)]] :: [[Configuring network|La Configuration du Réseau (en)]]<br />
== Pages Utiles ==<br />
<br />
Voici un extrait de quelques unes des pages les plus utiles du ArchWiki. <br />
<br />
==== &nbsp;&nbsp;[[Table_des_matières_(Français)|Table des Matières]] ====<br />
<br />
==== &nbsp;&nbsp;[[:Category:À_propos_d'Arch_(Français)|À propos d'Arch]] ====<br />
: [[ArchLinux_(Français)|Qu'est-ce qu'Arch Linux ?]] ::[[The_Arch_Way_(Français)|L'Esprit d'Arch]] :: [[Arch_Comparée_Aux_Autres_Distros|Arch Comparée Aux Autres Distributions]] :: [[FAQ_(Français)|FAQ]] :: [[Official Repositories|Les Dépôts Officiels (en)]] :: [[ArchLinux User-community Repository (AUR)|Le Dépôt Communautaire d'Arch (AUR) (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Administration_du_système_(Français)|Administration du Système]] ====<br />
: [[Pacman_(Français)|Pacman]] :: [[:Category: Package management (English)|Gestion des Paquets (en)]] :: [[Xorg|Configuration Xorg (en)]] :: [[:Category: Desktop environments (English)|Environments de Bureau (en)]] :: [[ALSA|ALSA (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Guide_de_l'utilisateur_de_bureau_(Français)|Guide de l'utilisation Bureautique]] ====<br />
: [[:Category: Internet and Email (English)|Internet et Email (en)]] :: [[:Category: Office (English)|Bureautique (en)]] :: [[:Category: Audio/Video (English)|Audio/Vidéo (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Remise_en_état_du_système_(Français)|Remise en état du Sytème]] ====<br />
: [[Reinstalling GRUB|Réinstaller GRUB (en)]] :: [[Kernel Panics (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Développement_d'Arch_(Français)|Développer d'Arch]] ====<br />
: [[Community Projects|Projets de la Communauté (en)]] :: [[:Category: Live Arch systems (English)|Systèmes Arch "Live" (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Arch64 (English)|Arch64 (en)]] ====<br />
: [[Arch64 FAQ|Arch64 FAQ (en)]]<br />
<br />
== Les Nouvelles du Wiki ==<br />
<br />
Consultez la page des [[Wiki News|Nouvelles du Wiki (en)]] pour les derniers tuyaux du Wiki.<br />
<br />
Si vous avez un peu de temps pour des modifications mineures ou majeures, jettez un oeil à the [[Priority Todo]] and the [[WikiTodo]] pages pour voir comment vous pourriez aider. Nous sommes particulièrment intéressé in having people réorganiser pages non-Anglaises. S'il vous plait coordonnez vos actions avec les [[ContactList|admins et sysops]] ou les [[ArchWiki maintainers (English)|maintainers]].<br />
<br />
== Dans votre Langue ==<br />
Plus à l'aise reading articles dans votre propre langue ? Parcourez les catégories dans les langues suivantes : <br />
: [[:Category:English|English]] :: [[:Category:Česky|Česky]] :: [[:Category:Deutsch|Deutsch]] :: [[:Category:Français|Français]] :: [[:Category:Italiano|Italiano]] :: [[:Category:Lietuviškai|Lietuviškai]] :: [[:Category:Polski|Polski]] :: [[:Category:Русский|Русский]] ::[[:Category:Українська|Українська]] :: [[:Category:Српски|Српски]] :: [[:Category:ไทย|ไทย]] :: [[:Category:简体中文|简体中文]] :: [[:Category:正體中文|正體中文]]<br />
<br />
== Aide ==<br />
Si vous avez des difficultés à trouver ce que vous cherchez, essayez d'utiliser la fonction de recherche sur la gauche.<br />
<br />
Vous devez créer un compte pour éditer ce Wiki. Une fois terminé, vous pourrez jouer un peu dans le [[Sandbox|Bac-à-sable]] ou avec votre page utilisateur pour vous familiariser avec la synthaxe (markup) du ArchWiki. The available syntax is listed in the [[:Category:Help|Wiki Help Category]] and there is an [[:Category:ArchWiki Tools (English)|Archwiki Tools section]] with some HOWTOs and guidelines.</div>
Faelar
https://wiki.archlinux.org/index.php?title=User:Faelar&diff=44275
User:Faelar
2008-07-06T00:16:18Z
<p>Faelar: New page: __NOTOC__ __NOEDITSECTION__ {{Navigate_i18n_mainpages}} == Guides d'Installation == '''Si vous êtes nouveau sur Arch, le Manuel du débutant (en) devrait-être appro...</p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
{{Navigate_i18n_mainpages}}<br />
<br />
== Guides d'Installation ==<br />
'''Si vous êtes nouveau sur Arch, le [[Beginners Guide|Manuel du débutant (en)]] devrait-être approprié,''' ou alors essayez '''le [[Official Arch Linux Install Guide|Guide Officiel d'Installation (en)]], qui vise les utilisateurs GNU/Linux confirmés.<br />
<br />
Vous pourriez également être intéressé par : [[Post Installation Tips|Les Astuces Post-Installation (en)]] :: [[Configuring network|La Configuration du Réseau (en)]]<br />
== Pages Utiles ==<br />
<br />
Voici un extrait de quelques unes des pages les plus utiles du ArchWiki. <br />
<br />
==== &nbsp;&nbsp;[[Table_des_matières_(Français)|Table des Matières]] ====<br />
<br />
==== &nbsp;&nbsp;[[:Category: About Arch (English)|À propos d'Arch (en)]] ====<br />
: [[ArchLinux_(Français)|Qu'est-ce qu'Arch Linux ?]] ::[[The_Arch_Way_(Français)|L'Esprit d'Arch]] :: [[Arch_Comparée_Aux_Autres_Distros|Arch Comparée Aux Autres Distributions]] :: [[FAQ_(Français)|FAQ]] :: [[Official Repositories|Les Dépôts Officiels (en)]] :: [[ArchLinux User-community Repository (AUR)|Le Dépôt Communautaire d'Arch (AUR) (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Administration_du_système_(Français)|Administration du Système]] ====<br />
: [[Pacman_(Français)|Pacman]] :: [[:Category: Package management (English)|Gestion des Paquets (en)]] :: [[Xorg|Configuration Xorg (en)]] :: [[:Category: Desktop environments (English)|Environments de Bureau (en)]] :: [[ALSA|ALSA (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: Desktop user's guide (English)|Guide de la Bureautique (en)]] ====<br />
: [[:Category: Internet and Email (English)|Internet et Email (en)]] :: [[:Category: Office (English)|Bureautique (en)]] :: [[:Category: Audio/Video (English)|Audio/Vidéo (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:System recovery (English)|Réparation du Sytème (en)]] ====<br />
: [[Reinstalling GRUB|Réinstaller GRUB (en)]] :: [[Kernel Panics (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: Arch development (English)|Développer pour Arch (en)]] ====<br />
: [[Community Projects|Projets de la Communauté (en)]] :: [[:Category: Live Arch systems (English)|Systèmes Arch "Live" (en)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:Arch64 (English)|Arch64 (en)]] ====<br />
: [[Arch64 FAQ|Arch64 FAQ (en)]]<br />
<br />
== Les Nouvelles du Wiki ==<br />
<br />
Consultez la page des [[Wiki News|Nouvelles du Wiki (en)]] pour les derniers tuyaux du Wiki.<br />
<br />
Si vous avez un peu de temps pour des modifications mineures ou majeures, jettez un oeil à the [[Priority Todo]] and the [[WikiTodo]] pages pour voir comment vous pourriez aider. Nous sommes particulièrment intéressé in having people réorganiser pages non-Anglaises. S'il vous plait coordonnez vos actions avec les [[ContactList|admins et sysops]] ou les [[ArchWiki maintainers (English)|maintainers]].<br />
<br />
== Dans votre Langue ==<br />
Plus à l'aise reading articles dans votre propre langue ? Parcourez les catégories dans les langues suivantes : <br />
: [[:Category:English|English]] :: [[:Category:Česky|Česky]] :: [[:Category:Deutsch|Deutsch]] :: [[:Category:Français|Français]] :: [[:Category:Italiano|Italiano]] :: [[:Category:Lietuviškai|Lietuviškai]] :: [[:Category:Polski|Polski]] :: [[:Category:Русский|Русский]] ::[[:Category:Українська|Українська]] :: [[:Category:Српски|Српски]] :: [[:Category:ไทย|ไทย]] :: [[:Category:简体中文|简体中文]] :: [[:Category:正體中文|正體中文]]<br />
<br />
== Aide ==<br />
Si vous avez des difficultés à trouver ce que vous cherchez, essayez d'utiliser la fonction de recherche sur la gauche.<br />
<br />
Vous devez créer un compte pour éditer ce Wiki. Une fois terminé, vous pourrez jouer un peu dans le [[Sandbox|Bac-à-sable]] ou avec votre page utilisateur pour vous familiariser avec la synthaxe (markup) du ArchWiki. The available syntax is listed in the [[:Category:Help|Wiki Help Category]] and there is an [[:Category:ArchWiki Tools (English)|Archwiki Tools section]] with some HOWTOs and guidelines.</div>
Faelar
https://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=42083
ASUS Eee PC 701
2008-05-27T19:14:58Z
<p>Faelar: /* Webcam */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
'''WARNING: THIS ARTICLE IS INCOMPLETE!''' Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum]. There is also a nice Arch Linux installation guide on the [http://wiki.eeeuser.com/installingarchlinux EeeUser Wiki].<br />
<br />
==Before You Begin==<br />
<br />
===Avoiding Pitfalls===<br />
<br />
The install is pretty normal, except that you'll need to [http://forum.eeeuser.com/viewtopic.php?id=890 avoid the pitfalls] of our alternative Linux install:<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
The rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]] (Recommended)<br />
<br />
Unfortunately, the kernel does not include drivers for a LAN or Wireless install.<br />
<br />
==Installing Arch Linux==<br />
<br />
Note: if you're using the USB pen drive as your media, then [[Install_from_USB_stick#After_booting_from_the_USB_stick:|follow these instructions]] to create the installation USB stick.<br />
<br />
===Download the necessary drivers/modules/patches===<br />
<br />
Since the stock kernel doesn't supports either the Eee ethernet or wireless network cards, you might want to download the ethernet or wireless drivers/modules that you need and copy them to the installation USB stick.<br />
<br />
*You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
*Wireless driver can be downloaded from [http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz here]. <br />
**The wireless driver requires a patch to make it work with the Eee PC. The patch can be download from [http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw here]<br />
<br />
*If you want to use dkite's eeemodules package, you should download the package from his [http://members.shaw.ca/dkite website] and put it on USB for ease of installing. Especially important is the '''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''', because we will need to install this package after installation for wireless and ethernet to work.<br />
<br />
*for anyone who read this wiki previously and wondered where the patched kernel download went; the latest arch kernel contains the patch that fixes the intel graphics vsync hardlock error, so no additional configuration need be done<br />
<br />
===Booting Arch the installation CD/USB===<br />
<br />
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 />
===Start the Installation===<br />
<br />
If you are installing from the USB, then issue<br />
<br />
mount /dev/sd[x] /src<br />
<br />
To mount the usb.<br />
<br />
Then just run<br />
<br />
/arch/setup<br />
<br />
To start the installation just like normal.<br />
<br />
===Prepare Hard Drive===<br />
<br />
The default Eee PC drive is split up into four partitions (here is [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* It is easiest to wipe the existing partitions and use one or two partitions for your install. One partition would be just '/', and two partitions would be '/boot' and '/'.<br />
* Choose "NONE" for swap (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
* Select "ext2" as your filesystem (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
<br />
===Select Packages===<br />
<br />
If you are installing from USB, then choose SRC as your source.<br />
<br />
In addition to the '''BASE''' category, we also need all the packages in the '''DEVEL''' category for compiling our ethernet/wireless drivers.<br />
<br />
If you intended to use wireless, then you'll also need the ''wireless_tools'' package from '''SUPPORT''' category.<br />
<br />
===Configure System===<br />
<br />
Edit /etc/rc.conf and add asus_acpi to the MODULES array:<br />
<br />
MODULES = (... asus_acpi ...) <br />
<br />
Arch will complain about this, pay no attention to the error message because once we install the patched version of asus_acpi module using dkite's package, the error message will disappear.<br />
<br />
Make these edits to "/etc/fstab":<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* '''(OPTIONAL)''' Add a new line: "tmpfs /var/log tmpfs size=1M 0 0" (WARNING: this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
** To save your startup/shutdown logs, look at the pitfalls link above.<br />
<br />
===Install Network Adapter Drivers===<br />
<br />
===== Build from sources =====<br />
Update: the atl2 ethernet is support by Arch Linux's stock kernel as of 2008.03<br />
<br />
After the installation, The first thing you will noticed after booting into your newly installed Arch Linux is that the network adapters (both ethernet and wireless) are not working. To install the drivers, mount the USB stick that contains the drivers by issues the following commands:<br />
<br />
mkdir /mnt/usb<br />
mount /dev/sd[x] /mnt/usb<br />
<br />
Then follow the following instructions to install your network driver.<br />
<br />
======Atl2 ethernet driver======<br />
<br />
You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
<br />
Extract the sources. You may need to modify the kernel version listed in the Makefile.<br />
<br />
make clean<br />
make<br />
cp atl2.ko /lib/modules/2.6.24-ARCH/kernel/drivers/net # Change 2.6.24 as needed<br />
depmod<br />
<br />
======Atheros wireless ethernet driver======<br />
<br />
Instructions from http://wiki.eeeuser.com/ubuntu#wireless_internet_using_native_madwifi_drivers to patch madwifi. This replaces the Arch madwifi packages.<br />
<br />
wget 'http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw'<br />
wget http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
If you have already downloaded both the driver source & the patch and have moved them into the USB, then both move the driver source & the patch into the same directory and issues the following command:<br />
<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
Working against stock kernel.<br />
<br />
=====Install wireless and ethernet drivers using dkite's eeemodules Package=====<br />
<br />
Another way to install both wireless and ethernet drivers/modules, instate of having to build and install the drivers/modules yourself, is to use dkite's eeemodules Package, which included both wireless and ethernet drivers/modules, among other things.<br />
<br />
Since Don't Panic installation CD comes with kernel version 2.6.22.9, we will need to use '''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' package, which you can get from [http://members.shaw.ca/dkite his website], if you haven't got it already.<br />
<br />
Mount the USB that contains the package and install it with this command:<br />
<br />
pacman -Uf eeemodules-2.6.22.9-1-i686.pkg.tar.gz<br />
<br />
Then load the modules with<br />
<br />
depmod<br />
<br />
Restart and now you should have a working wireless/ethernet connection.<br />
<br />
====Install All the Necessary Modules====<br />
<br />
After you have installed and configured the driver, proceed to upgrade the system with pacman -Syu command. After the upgrade is complete, it is the time to decide which methods you would like to use to install the modules:<br />
<br />
'''ATTENTION:''' Do ''NOT'' restart after upgrade the system and before you install the modules using one of the following methods, or your hardware (wifi, ethernet, etc.) ''WILL'' stop functioning.<br />
<br />
'''dkite''' have created a package that contains all the necessary modules for wifi, ethernet connection, acpi and video camera hardware that comes with the Eee PC. His package is to be use with the stock kernel. <br />
<br />
The following is the list of hardware/functions that are known to work with dkite's eeemodules Package:<br />
<br />
*Wireless <br />
*Ethernet <br />
*Webcam <br />
*Suspend/Resume<br />
<br />
You can get the package [http://members.shaw.ca/dkite from his website]. <br />
<br />
Currently there are three pre-complied package:<br />
<br />
#'''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' for use with Don't Panic kernel.<br />
#'''eeemodules-0.0.3-2.6.24.1.2-i686.pkg.tar.gz''' for the 2.6.24.14-2 kernel.<br />
<br />
If you have newer or other version of kernel26, then you will need to download '''eeemodules.tar.gz''', which contains PKGBUILD and all the necessary files, and build the package yourself. <br />
<br />
*'''ATTENTION:''' You will also need to rebuild the package, using eeemodules.tar.gz, every time you upgrade your kernel, or else your hardware (wifi, ethernet, etc.) will stop functioning.<br />
<br />
=====Installation Instructions=====<br />
<br />
Install the package with the following command:<br />
<br />
pacman -Uf eeemodules-<pkgver>.tar.gz<br />
<br />
Then run a depmod command:<br />
<br />
depmod<br />
<br />
'''Attention:''' Do ''not'' forget to run the depmod command after installing the package, otherwise your hardware won't function! <br />
<br />
If you want to use the webcam then you might also need to load the asus_acpi module. Edit the /etc/rc.conf file and insert asus_acpi into MODULES array:<br />
<br />
MODULES = (... asus_acpi ...)<br />
<br />
====Eee repository from toofishes====<br />
toofishes created a repository for the eee. You can find some basic packages like Pentium-M-optimized kernel and needed modules. Add<br />
[eee]<br />
Server = http://code.toofishes.net/packages/eee<br />
to your /etc/pacman.conf to use the repository.<br />
<br />
=====Package List=====<br />
<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' <br />
customized kernel for Eee<br />
*'''linux-uvc-eee-svn''' <br />
webcam driver for Eee<br />
*'''luvcview''' <br />
webcam program for testing webcam driver<br />
*'''madwifi-eee-svn''' <br />
wifi driver for Eee<br />
*'''eeepc-linux''' <br />
kernel module to change Eee's FSB speed and fan control<br />
<br />
=====Installation Instruction=====<br />
<br />
Simply use pacman to install the package that you need. For a working system, you'll need at least 3 packages: kernel-eee (the kernel), linux-uvc-eee-svn (webcam driver) and madwifi-eee-svn (the wifi driver).<br />
<br />
Install the packages with this command:<br />
<br />
pacman -Sy kernel-eee linux-uvc-eee-svn madwifi-eee-svn<br />
<br />
'''ATTENTION:''' dkite's eeemodules package conflicts with the madwifi-eee-svn package. You need to remove dkite's eeemodules package before you can install toofishes madfwifi-eee-svn package.<br />
<br />
Then, add the following to /boot/grub/menu.lst; note that no initrd is needed:<br />
# (2) Arch Linux<br />
title Arch Linux EEE kernel<br />
root (hd0,0)<br />
kernel /boot/vmlinuzeee root=/dev/sda1 ro<br />
<br />
Restart and select Arch Linux EEE kernel from the grub boot menu.<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. The following is the guide on how to get the rest of your system working.<br />
<br />
===Xorg===<br />
<br />
You have two choices for video on the Eee- the newer <b>xf86-video-intel</b> driver, or the older <b>xf86-video-i810</b> driver paired with 915resolution. Unless there is a compelling reason to use the i810 driver, the intel driver is the focus upstream and is being actively developed so it is your best choice.<br />
<br />
You need these packages in addition to the Xorg's packages:<br />
<br />
pacman -Sy synaptics xf86-video-intel<br />
<br />
If you choose to use the older i180 video, you will have to install xf86-video-i810 and 915resolution as well. Note that the i180 driver and the intel driver cannot both be installed at the same time.<br />
<br />
Then, just drop in the following xorg.conf into your /etc/X11/ directory:<br />
<br />
<pre>Section "ServerLayout"<br />
Identifier "ArchLinux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "extmod"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail"<br />
Option "BlankTime" "5"<br />
Option "AIGLX" "false"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "keyboard"<br />
Driver "kbd"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbLayout" "us"<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "IMPS/2"<br />
Option "Emulate3Buttons" "yes"<br />
Option "ZAxisMapping" "4 5"<br />
Option "CorePointer"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "synaptics"<br />
Driver "synaptics"<br />
Option "Device" "/dev/psaux"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1000"<br />
Option "RightEdge" "5400"<br />
Option "TopEdge" "1000"<br />
Option "BottomEdge" "4900"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "HorizScrollDelta" "0" <br />
Option "RBCornerButton" "0"<br />
Option "RTCornerButtom" "0"<br />
Option "MaxSpeed" "0.1"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "ASUS"<br />
ModelName "eeePC P701"<br />
Modeline "800x480" 29.58 800 816 896 992 480 481 484 497 -HSync +Vsync # 60 Hz<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "intel"<br />
VendorName "Intel Corporation"<br />
BoardName "Mobile 915GM/GMS/910GML Express Graphics Controller"<br />
BusID "PCI:0:2:0"<br />
Option "AccelMethod" "EXA"<br />
Option "MigrationHeuristic" "greedy"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</pre><br />
<br />
If you want to set up the i810 driver instead, you will also have to configure 915resolution and add it to your daemons line. This is not needed for the intel driver. Edit the /etc/conf.d/915resolution to look like this:<br />
<br />
<pre># Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
</pre><br />
<br />
Now put the 915resolution daemon into your /etc/rc.conf file:<br />
<br />
<pre>DAEMONS=(... 915resolution ...)</pre><br />
<br />
===Sound, Webcam & Microphone===<br />
<br />
====Sound====<br />
<br />
Some people have reported sound working right out of the box with no troubles. However, others might need to add the following line to /etc/modprobe.conf.<br />
<br />
<pre>options snd-hda-intel model=3stack-dig</pre><br />
<br />
If your internal microphone doesn't work, you probably have to turn the capture feature on. Simply fire up alsamixer, find your Capture control, and press spacebar to enable it.<br />
<br />
====Webcam====<br />
<br />
If you installed dkite eeemodules package or toofishes's linux-uvc-eee-svn package, then you should already have webcam driver installed and don't need to install Linux UVC device driver. Just add: <br />
<br />
echo 1 > /proc/acpi/asus/camera<br />
<br />
to your /etc/rc.local file should be suffice to get your webcam working.<br />
<br />
If somehow you don't want to use either dkite eeemodules package or toofishes's linux-uvc-eee-svn package, or prefers to install the driver yourself, then follows the following instructions.<br />
<br />
First, install the Linux UVC device driver. Make sure you have the community repository enabled, and run:<br />
<pre>pacman -S linux-uvc-svn</pre><br />
Then just turn on the webcam (This requires the asus_acpi module):<br />
<pre>echo 1 > /proc/acpi/asus/camera</pre><br />
If you want a simple application application to test it out with, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=7763 luvcview from the AUR], and run it with:<br />
<pre>luvcview -f yuv</pre><br />
<br />
Alternatively, if you want the webcam application that the default Xandos installation uses, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14469 ucview from the AUR].<br />
<br />
The webcam also works fine with the latest version of Skype.<br />
<br />
If you already have mplayer installed you can launch :<br />
mplayer -fps 15 tv://<br />
<br />
I have yet to get it working with vlc or any other software such as xawtv. If you know how, please update this.<br />
<br />
*'''NOTE:''' For anyone who has accidentally disabled Auto Exposure for their webcam in luvcview (making the image dark), and can't enable it again, do the following:<br />
<br />
Install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14468 libwebcam from the AUR].<br />
<br />
Issue the following command:<br />
<pre>uvcdynctrl --set "Exposure, Auto" 4</pre><br />
<br />
*'''NOTE:''' Be sure the "OS Installation" option is set to "finished" in the BIOS' "Advanced" tab or your camera may not work in some applications (like Skype).<br />
<br />
====Microphone====<br />
<br />
Solution for problems with the internal microphone.<br />
<br />
1. First of all set in alsamixer "Input Source" to "i-Mic"<br />
<br />
2. Increase "Capture" and "i-Mic Boost" to your needs<br />
<br />
3. Edit /etc/asound.state the following, change the 2 "false" to "true" like showing:<br />
<pre><br />
....snap.....<br />
control.11 {<br />
comment.access 'read write'<br />
comment.type BOOLEAN<br />
comment.count 2<br />
iface MIXER<br />
name 'Capture Switch'<br />
value.0 true<br />
value.1 true<br />
}<br />
....snap....</pre><br />
<br />
4. After editing run following as root<br />
<pre>alsactl restore</pre><br />
<br />
5. Now your internal microphone should be working.<br />
<br />
===Getting Hot Keys, Graphic Indicators and Shutdown with the Power Button Working===<br />
<br />
If you want to have working hot keys for changing brightness and volumes, graphic indicators working as well as shutdown when press the power button (just like in the stock Eee PC), then you should install ''''ighea's acpi-eee'''' or ''''dkite's acpid_eee'''' package.<br />
<br />
<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-8-1-i686.pkg.tar.gz<br />
<br />
See messages during installation for more details and don't forget to edit /etc/acpi/eee.conf to suit your tastes.<br />
<br />
<br />
==== dkite's acpid_eee ====<br />
<br />
Package can also be download form his [http://members.shaw.ca/dkite/ website]<br />
<br />
The package itself can be install with<br />
<br />
pacman -Uf acpid_eee-0.0.3-1-i686.pkg.tar.gz.tar<br />
<br />
<br />
With '''both''' packages don't forget to start asusosd if you want to have the Graphic Indicators from Xandros.<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 by adding the following line<br />
<br />
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind<br />
<br />
To your /etc/rc.local.shutdown should fix the problem.<br />
<br />
If this does not work, the module may not be able to be unloaded until after all services have finished. Do the above, then in /etc/rc.shutdown move <br />
<br />
if [ -x /etc/rc.local.shutdown ]; then<br />
/etc/rc.local.shutdown<br />
fi<br />
<br />
from where it was to directly above the line <br />
<br />
# Terminate all processes<br />
<br />
this will cause the rc.local.shutdown script to run after services have been exited. This fixed all issues for the person editing this note.<br />
<br />
==Additional Tips & Tweaks==<br />
<br />
===kernel26eee tweaks===<br />
<br />
* Toofishes's kernel, also known as kernel26eee, can be tweaked to include custom features. Simple insert a make menuconfig line into the PKGBUILD before the kernel's compilation.<br />
<br />
===Power down with the power button===<br />
<br />
*''If you use dkite's acpid_eee package then you should already be able to shutdown by pressing the power button and should not need to do this.''<br />
<br />
The two alternatives here are described in [[Allow_users_to_shutdown]].<br />
<br />
If you don't already or don't plan to use sudo, it may be simpler to use the setuid /sbin/halt method, otherwise using sudo is preferred.<br />
<br />
Below are all the steps required for the sudo method. If you want to use the setuid method, read the article linked above and perform the 'power' file step here, while omitting the 'sudo' in it.<br />
<br />
<pre>pacman -S sudo</pre><br />
<br />
As root, do the following:<br />
<br />
<pre>visudo</pre><br />
<br />
Add the following line to the file:<br />
<br />
<pre>USER HOST = NOPASSWD: /sbin/poweroff</pre><br />
<br />
Where USER = the user you want to be able to power down with and HOST = your hostname (from /etc/rc.conf).<br />
<br />
Now, create a file called /etc/acpi/events/power, containing:<br />
<br />
<pre># /etc/acpi/events/power<br />
# This is called when the user presses the power button<br />
<br />
event=button/power (PWR.||PBTN)<br />
action=sudo /sbin/poweroff</pre><br />
<br />
Make sure that you execute<br />
<br />
<pre>/etc/rc.d/acpid start</pre><br />
<br />
And/or add acpid to the daemons list in /etc/rc.conf:<br />
<br />
<pre>DAEMONS=(hal, acpid ...</pre><br />
<br />
===Compile the 'everything' Kernel===<br />
<br />
The 'everything' kernel has ath5k, which supports the Atheros chipset found on the EEE PC. Here are the [http://linuxwireless.org/en/users/Drivers/ath5k#Hackingath5k instructions on compiling the 'everthing' kernel] (thanks raymano!).<br />
<br />
===Use cpufreq for power saving===<br />
For scaling down the processor you have to load the p4_clockmod. Insert it into your /etc/rc.conf MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
Then proceed like [http://wiki.archlinux.org/index.php/SpeedStep#Alternative_Methods here]. <br />
Add the following into /etc/conf.d/cpufreq<br />
governor="ondemand"<br />
min_freq="113MHz"<br />
max_freq="900MHz"<br />
With enabled cpufreq it scales the processor between 113MHz up to max. frequency. That should save a lot on battery power. The stated 900MHz will be never reached by the eeePC, the p4_clockmod reports a wrong frequency here. But scaling works, you can feel it in the performance of eeePC that he slow down the processor.<br />
<br />
===More responsive system with ondemand governor===<br />
The default up_threshold (where it will bump to a faster speed) for the CPU governor is 80, which means it will increase the CPU speed when utilization is above 80%. This can make X applications have a bit of lag. <br />
Try changing this value:<br />
sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
With 40 it still leaves the majority of CPU cycles at the lowest available clock speed but increases responsiveness. You can add this line to one of your startup scripts if you wish to keep it, for example in /etc/rc.local.<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 />
===Update your BIOS without Xandros===<br />
'''Warning : you can break your system, do not update if you are not sure of what you are doing !'''<br />
<br />
First, you need to download the ''.rom'' file.<br />
*[http://update.eeepc.asus.com/bios/ Asus official's BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USBStick formated in fat32.<br />
To format an USBStick, use cfdisk tool :<br />
cfdisk /dev/sdc #could be something else than "c"<br />
Choose [delete], [type] : "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
cp /somewhere/blabla/.../thecurrentnameofthefile.rom /dev/sdc1/701.rom<br />
The name of the copy '''must''' be 701.rom<br />
<br />
Next step, reboot the eeepc with the USBStick pluged-in, and press<br />
Alt + F2<br />
It will launch the built-in tool. Everything should be Ok, you can make a coffee during the update. When it asks you to push the power-button it has finished.<br />
<br />
<br />
At the next boot, you'll be invited to configure the BIOS. Check if the everything is enable (my webcam and wireless were disable after the update) and if it displays the good version in the main screen. It's done !<br />
<br />
===More usuable font sizes===<br />
<br />
On a default installation with XFCE 4 my font sizes were too big, here is what I did to sort them out.<br />
<br />
First, I set the DPI by adding the following to ~/.Xdefaults:<br />
Xft*dpi: 134<br />
<br />
This then caused the fonts to be even bigger, so I set them all to be font-size 6 by adding the following into ~/.gtkrc-2.0 (note this will be overwritten if you use any tools to change GTK settings):<br />
style "user-font"<br />
{<br />
font_name="Bitstream Vera Sans 6"<br />
}<br />
widget_class "*" style "user-font"<br />
<br />
To do the same with KDE fonts (without KDE installed) you have to add the following to ~/.kde/share/config/kdeglobals:<br />
[General]<br />
StandardFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
activeFont=Bitstream Vera Sans,6,-1,5,75,0,0,0,0,0<br />
fixed=Bitstream Vera Sans Mono,6,-1,5,50,0,0,0,0,0<br />
font=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
menuFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
taskbarFont=Bitstream Vera Sans,6,-1,5,50,1,0,0,0,0<br />
toolBarFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
<br />
To make your fonts even prettier enable the [[Fonts#Fonts_with_LCD_filter_enabled|LCD Fonts]].<br />
<br />
==Known problems and their solutions==<br />
<br />
===Booting from card without initrd===<br />
<br />
Let's say you decided to install Arch Linux on a card and compiled your own kernel (or used the kernel26eee kernel) without initrd. Card reader on EeePC is connected as an USB device. Unfortunately, USB storage devices are detected with a delay, so we must tell the kernel to wait until this device becomes available. You do this with "rootwait" option passed to kernel at boot time.<br />
<br />
===Sleeping and waking system on a card===<br />
<br />
If you have Arch Linux on a card, waking up from sleeping state will most likely fail. The only solution is to enable the CONFIG_USB_PERSIST option in kernel. The kernel26eee package should have this option enabled.<br />
<br />
===Display doesn't wake up properly===<br />
<br />
If you encounter black display (but apparently working system) after suspend/resume, consider using the "uswsusp" package (available in AUR) and correcting suspend2ram script in /etc/acpi, where you use this line to make the machine go to sleep:<br />
<br />
<pre>/usr/sbin/s2ram --force --vbe_post --vbe_mode</pre></div>
Faelar
https://wiki.archlinux.org/index.php?title=AUR_Cleanup_Day/2010&diff=40716
AUR Cleanup Day/2010
2008-05-05T10:53:14Z
<p>Faelar: /* Package List */</p>
<hr />
<div>The AUR has a large number of obsolete packages which could use cleaning up. Examples of packages that may be cleaned up are:<br />
*packages that have been renamed or replaced<br />
*old and unmaintained developmental (cvs/svn/etc) packages<br />
<br />
Post suggestions of packages on this pages. Trusted Users will get together and go though the list in a couple of weeks and confirm which packages should be removed. '''Please DO NOT REMOVE suggestions from the wiki page but add a comment on why it should be kept instead.''' TUs will not delete any useful package.<br />
<br />
==Package List==<br />
* [http://aur.archlinux.org/packages.php?ID=12840 abraca-hg] - Replaced by abraca-git<br />
* [http://aur.archlinux.org/packages.php?ID=7086 alienarena2007] - Replaced by alienarena<br />
* [http://aur.archlinux.org/packages.php?ID=3194 azrael] - dead project, does not compile<br />
* [http://aur.archlinux.org/packages.php?ID=1790 fusesmb] or [http://aur.archlinux.org/packages.php?ID=14475 fusesmb2] - duplicate (and both outdated, version 8.7 is available)<br />
* [http://aur.archlinux.org/packages.php?ID=6823 gimp-resynth] or [http://aur.archlinux.org/packages.php?ID=12273 gimp-plugin-resynthesizer] - duplicate (best to keep latter)<br />
* [http://aur.archlinux.org/packages.php?ID=8231 kdelibs-noarts] - out-of-date, modified official package<br />
* [http://aur.archlinux.org/packages.php?ID=6296 kernel26thinkpad] - obsolete, out of date since 2006<br />
* [http://aur.archlinux.org/packages.php?ID=2700 mutt-cvs] - mutt switched to mercurial a while back; way outdated anyway.<br />
* [http://aur.archlinux.org/packages.php?ID=15312 openssh-snapshot] - Not needed anymore<br />
* [http://aur.archlinux.org/packages.php?ID=494 sonic-rainbow] - dead project, does not compile<br />
<br />
==Remove from Filesystem==<br />
<br />
This is a list of files on the AUR filesystem that have been created when poorly formed packages were uploaded. <br />
<br />
<pre><br />
/packages/0verkill-0.16.tar.gz/<br />
/packages/2007.02.17-2/<br />
/packages/abakus-0.91-1/<br />
/packages/abakus-0.91.tar.gz/<br />
/packages/abakus-0.91/<br />
/packages/akgregator/<br />
/packages/akregator/<br />
/packages/akregator1.0.2/<br />
/packages/akregator_1.0.2/<br />
/packages/amsn-0.97ec1/<br />
/packages/amsn-0.97rc1/<br />
/packages/amsn-097rc1-1/<br />
/packages/amsn-097rc1/<br />
/packages/amsn-cvs/<br />
/packages/amsn-svn_update/<br />
/packages/amsn096/<br />
/packages/amsn096rc1/<br />
/packages/bashstyle-5.0<br />
/packages/bashstyle-5.0rc1.tar.gz/<br />
/packages/bashstyle-5.0rc1.tar.gz1/<br />
/packages/bashstyle-5.0rc1/<br />
/packages/bashstyle.tar.gz/<br />
/packages/bashstyle-ng/<br />
/packages/bashstyle1/<br />
/packages/braero-svn<br />
/packages/braser-cvs/<br />
/packages/brasero-cvs/<br />
/packages/brasero.svn/<br />
/packages/brlcad-cvs/<br />
/packages/ccd2iso-0.3/<br />
/packages/cdcollect-0.6.0/<br />
/packages/centerim-4.22.2/<br />
/packages/centerim/<br />
/packages/ploticus-test/<br />
/packages/test-louipc/<br />
/packages/test/<br />
/packages/test_pkg/<br />
/packages/yacas-1.1.17-2/<br />
/packages/yacas-1.2.2/<br />
/packages/yacas-1.17-2/<br />
/packages/yacas-new/<br />
/packages/yacasnew/<br />
/packages/zzztest/<br />
/packages/zzzztest/<br />
</pre></div>
Faelar
https://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=39383
ASUS Eee PC 701
2008-03-30T11:23:18Z
<p>Faelar: /* Additional Tips & Tweaks */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
'''WARNING: THIS ARTICLE IS INCOMPLETE!''' Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum]. There is also a nice Arch Linux installation guide on the [http://wiki.eeeuser.com/installingarchlinux EeeUser Wiki].<br />
<br />
==Before You Begin==<br />
<br />
===Avoiding Pitfalls===<br />
<br />
The install is pretty normal, except that you'll need to [http://forum.eeeuser.com/viewtopic.php?id=890 avoid the pitfalls] of our alternative Linux install:<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
The rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]] (Recommended)<br />
<br />
Unfortunately, the kernel does not include drivers for a LAN or Wireless install.<br />
<br />
==Installing Arch Linux==<br />
<br />
Note: if you're using the USB pen drive as your media, then [[Install_from_USB_stick#After_booting_from_the_USB_stick:|follow these instructions]] to create the installation USB stick.<br />
<br />
===Download the necessary drivers/modules/patches===<br />
<br />
Since the stock kernel doesn't supports either the Eee ethernet or wireless network cards, you might want to download the ethernet or wireless drivers/modules that you need and copy them to the installation USB stick.<br />
<br />
*You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
*Wireless driver can be downloaded from [http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz here]. <br />
**The wireless driver requires a patch to make it work with the Eee PC. The patch can be download from [http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw here]<br />
<br />
*If you want to use dkite's eeemodules package, you should download the package from his [http://members.shaw.ca/dkite website] and put it on USB for ease of installing. Especially important is the '''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''', because we will need to install this package after installation for wireless and ethernet to work.<br />
<br />
*'''IMPORTANT''' The current, head and (at least) recent vanilla kernels (including the one currently used by archlinux) as of 03.13.08 have a bug in the drm source that causes any opengl application with vsync turned on (prevents page tearing) to randomly lock the entire system because of the eee's trusty intel 915 graphics chipset. This is somewhat nasty considering the ext2 filesystem used doesn't have quite the stability of it's ext3 counterpart. There is a patch released for the 2.6.24.3 kernel that eliminates this massive bug [http://bugs.freedesktop.org/show_bug.cgi?id=14937 here]. If you are using dkite's kernel module package, you can use the default kernel26 package recompiled by prurigro on an eee to include this patch [http://thepiratebay.org/tor/4078731 here]. I'm not editing the rest of this wiki entry in hopes the arch bug watchers get the patch inserted into the kernel (in which case I can take the torrent down and remove this entry). Until then, what you should do is- after updating the system and before installing dkite's package, upgrade the kernel with the package in the torrent: ''pacman -U kernel26-2.6.24.3-3-i686.pkg.tar.gz'' then reboot and compile dkite's eeemodules against this updated kernel.<br />
<br />
===Booting Arch the installation CD/USB===<br />
<br />
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 />
===Start the Installation===<br />
<br />
If you are installing from the USB, then issue<br />
<br />
mount /dev/sd[x] /src<br />
<br />
To mount the usb.<br />
<br />
Then just run<br />
<br />
/arch/setup<br />
<br />
To start the installation just like normal.<br />
<br />
===Prepare Hard Drive===<br />
<br />
The default Eee PC drive is split up into four partitions (here is [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* It is easiest to wipe the existing partitions and use one or two partitions for your install. One partition would be just '/', and two partitions would be '/boot' and '/'.<br />
* Choose "NONE" for swap (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
* Select "ext2" as your filesystem (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
<br />
===Select Packages===<br />
<br />
If you are installing from USB, then choose SRC as your source.<br />
<br />
In addition to the '''BASE''' category, we also need all the packages in the '''DEVEL''' category for compiling our ethernet/wireless drivers.<br />
<br />
If you intended to use wireless, then you'll also need the ''wireless_tools'' package from '''SUPPORT''' category.<br />
<br />
===Configure System===<br />
<br />
Edit /etc/rc.conf and add asus_acpi to the MODULES array:<br />
<br />
MODULES = (... asus_acpi ...) <br />
<br />
Arch will complain about this, pay no attention to the error message because once we install the patched version of asus_acpi module using dkite's package, the error message will disappear.<br />
<br />
Make these edits to "/etc/fstab":<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* '''(OPTIONAL)''' Add a new line: "tmpfs /var/log tmpfs size=1M 0 0" (WARNING: this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
** To save your startup/shutdown logs, look at the pitfalls link above.<br />
<br />
===Install Network Adapter Drivers===<br />
<br />
===== Build from sources =====<br />
<br />
After the installation, The first thing you will noticed after booting into your newly installed Arch Linux is that the network adapters (both ethernet and wireless) are not working. To install the drivers, mount the USB stick that contains the drivers by issues the following commands:<br />
<br />
mkdir /mnt/usb<br />
mount /dev/sd[x] /mnt/usb<br />
<br />
Then follow the following instructions to install your network driver.<br />
<br />
======Atl2 ethernet driver======<br />
<br />
You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
<br />
Extract the sources. You may need to modify the kernel version listed in the Makefile.<br />
<br />
make clean<br />
make<br />
cp atl2.ko /lib/modules/2.6.24-ARCH/kernel/drivers/net # Change 2.6.24 as needed<br />
depmod<br />
<br />
======Atheros wireless ethernet driver======<br />
<br />
Instructions from http://wiki.eeeuser.com/ubuntu#wireless_internet_using_native_madwifi_drivers to patch madwifi. This replaces the Arch madwifi packages.<br />
<br />
wget 'http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw'<br />
wget http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
If you have already downloaded both the driver source & the patch and have moved them into the USB, then both move the driver source & the patch into the same directory and issues the following command:<br />
<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
Working against stock kernel.<br />
<br />
=====Install wireless and ethernet drivers using dkite's eeemodules Package=====<br />
<br />
Another way to install both wireless and ethernet drivers/modules, instate of having to build and install the drivers/modules yourself, is to use dkite's eeemodules Package, which included both wireless and ethernet drivers/modules, among other things.<br />
<br />
Since Don't Panic installation CD comes with kernel version 2.6.22.9, we will need to use '''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' package, which you can get from [http://members.shaw.ca/dkite his website], if you haven't got it already.<br />
<br />
Mount the USB that contains the package and install it with this command:<br />
<br />
pacman -Uf eeemodules-2.6.22.9-1-i686.pkg.tar.gz<br />
<br />
Then load the modules with<br />
<br />
depmod<br />
<br />
Restart and now you should have a working wireless/ethernet connection.<br />
<br />
====Install All the Necessary Modules====<br />
<br />
After you have installed and configured the driver, proceed to upgrade the system with pacman -Syu command. After the upgrade is complete, it is the time to decide which methods you would like to use to install the modules:<br />
<br />
'''ATTENTION:''' Do ''NOT'' restart after upgrade the system and before you install the modules using one of the following methods, or your hardware (wifi, ethernet, etc.) ''WILL'' stop functioning.<br />
<br />
'''dkite''' have created a package that contains all the necessary modules for wifi, ethernet connection, acpi and video camera hardware that comes with the Eee PC. His package is to be use with the stock kernel. <br />
<br />
The following is the list of hardware/functions that are known to work with dkite's eeemodules Package:<br />
<br />
*Wireless <br />
*Ethernet <br />
*Webcam <br />
*Suspend/Resume<br />
<br />
You can get the package [http://members.shaw.ca/dkite from his website]. <br />
<br />
Currently there are three pre-complied package:<br />
<br />
#'''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' for use with Don't Panic kernel.<br />
#'''eeemodules-0.0.3-2.6.24.1.2-i686.pkg.tar.gz''' for the 2.6.24.14-2 kernel.<br />
<br />
If you have newer or other version of kernel26, then you will need to download '''eeemodules.tar.gz''', which contains PKGBUILD and all the necessary files, and build the package yourself. <br />
<br />
*'''ATTENTION:''' You will also need to rebuild the package, using eeemodules.tar.gz, every time you upgrade your kernel, or else your hardware (wifi, ethernet, etc.) will stop functioning.<br />
<br />
=====Installation Instructions=====<br />
<br />
Install the package with the following command:<br />
<br />
pacman -Uf eeemodules-<pkgver>.tar.gz<br />
<br />
Then run a depmod command:<br />
<br />
depmod<br />
<br />
'''Attention:''' Do ''not'' forget to run the depmod command after installing the package, otherwise the various hardware won't function! <br />
<br />
If you want to use the webcam then you might also need to load the asus_acpi module. Edit the /etc/rc.conf file and insert asus_acpi into MODULES array:<br />
<br />
MODULES = (... asus_acpi ...)<br />
<br />
====Eee repository from toofishes====<br />
toofishes created a repository for the eee. You can find some basic packages like Pentium-M-optimized kernel and needed modules. Add<br />
[eee]<br />
Server = http://code.toofishes.net/packages/eee<br />
to your /etc/pacman.conf to use the repository.<br />
<br />
=====Package List=====<br />
<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' <br />
customized kernel for Eee<br />
*'''linux-uvc-eee-svn''' <br />
webcam driver for Eee<br />
*'''luvcview''' <br />
webcam program for testing webcam driver<br />
*'''madwifi-ng-eee''' <br />
wifi driver for Eee<br />
*'''eeepc-linux''' <br />
kernel module to change Eee's FSB speed and fan control<br />
<br />
=====Installation Instruction=====<br />
<br />
Simply use pacman to install the package that you need. For a working system, you'll need at least 3 packages: kernel-eee (the kernel), linux-uvc-eee-svn (webcam driver) and madwifi-ng-eee (the wifi driver).<br />
<br />
Install the packages with this command:<br />
<br />
pacman -Sy kernel-eee linux-uvc-eee-svn madwifi-ng-eee<br />
<br />
'''ATTENTION:''' dkite's eeemodules package conflicts with the madwifi-ng-eee package. You need to remove dkite's eeemodules package before you can install toofishes madfwifi-ng-eee package.<br />
<br />
Then, add the following to /boot/grub/menu.lst; note that no initrd is needed:<br />
# (2) Arch Linux<br />
title Arch Linux EEE kernel<br />
root (hd0,0)<br />
kernel /boot/vmlinuzeee root=/dev/sda1 ro<br />
<br />
Restart and select Arch Linux EEE kernel from the grub boot menu.<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. The following is the guide on how to get the rest of your system working.<br />
<br />
===Xorg===<br />
<br />
You have two choices for video on the Eee- the newer <b>xf86-video-intel</b> driver, or the older <b>xf86-video-i810</b> driver paired with 915resolution. Unless there is a compelling reason to use the i810 driver, the intel driver is the focus upstream and is being actively developed so it is your best choice.<br />
<br />
You need these packages in addition to the Xorg's packages:<br />
<br />
pacman -Sy synaptics xf86-video-intel<br />
<br />
If you choose to use the older i180 video, you will have to install xf86-video-i810 and 915resolution as well. Note that the i180 driver and the intel driver cannot both be installed at the same time.<br />
<br />
Then, just drop in the following xorg.conf into your /etc/X11/ directory:<br />
<br />
<pre>Section "ServerLayout"<br />
Identifier "ArchLinux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "extmod"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail"<br />
Option "BlankTime" "5"<br />
Option "AIGLX" "false"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "keyboard"<br />
Driver "kbd"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbLayout" "us"<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "IMPS/2"<br />
Option "Emulate3Buttons" "yes"<br />
Option "ZAxisMapping" "4 5"<br />
Option "CorePointer"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "synaptics"<br />
Driver "synaptics"<br />
Option "Device" "/dev/psaux"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1000"<br />
Option "RightEdge" "5400"<br />
Option "TopEdge" "1000"<br />
Option "BottomEdge" "4900"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "HorizScrollDelta" "0" <br />
Option "RBCornerButton" "0"<br />
Option "RTCornerButtom" "0"<br />
Option "MaxSpeed" "0.1"<br />
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" "XAA"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</pre><br />
<br />
If you want to set up the i810 driver instead, you will also have to configure 915resolution and add it to your daemons line. This is not needed for the intel driver. Edit the /etc/conf.d/915resolution to look like this:<br />
<br />
<pre># Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
</pre><br />
<br />
Now put the 915resolution daemon into your /etc/rc.conf file:<br />
<br />
<pre>DAEMONS=(... 915resolution ...)</pre><br />
<br />
===Sound, Webcam & Microphone===<br />
<br />
====Sound====<br />
<br />
Some people have reported sound working right out of the box with no troubles. However, others might need to add the following line to /etc/modprobe.conf.<br />
<br />
<pre>options snd-hda-intel model=3stack-dig</pre><br />
<br />
If your internal microphone doesn't work, you probably have to turn the capture feature on. Simply fire up alsamixer, find your Capture control, and press spacebar to enable it.<br />
<br />
====Webcam====<br />
<br />
If you installed dkite eeemodules package or filoktetes's kernel, then you should already have webcam driver installed and don't need to install Linux UVC device driver. Just add: <br />
<br />
echo 1 > /proc/acpi/asus/camera<br />
<br />
to your /etc/rc.local file should be suffice to get your webcam working.<br />
<br />
If you don't use dkite eeemodules package or filoktetes's kernel or prefers to install the driver yourself, then follows the following instructions.<br />
<br />
First, install the Linux UVC device driver. Make sure you have the community repositories enabled, and run:<br />
<pre>pacman -S linux-uvc-svn</pre><br />
Then just turn on the webcam (This requires the asus_acpi module):<br />
<pre>echo 1 > /proc/acpi/asus/camera</pre><br />
If you want a simple application application to test it out with, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=7763 luvcview from the AUR], and run it with:<br />
<pre>luvcview -f yuv</pre><br />
<br />
Alternatively, 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 />
I have yet to get it working with vlc or any other software such as xawtv. If you know how, please update this.<br />
<br />
*'''NOTE:''' For anyone who has accidentally disabled Auto Exposure for their webcam in luvcview (making the image dark), and can't enable it again, do the following:<br />
<br />
Install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14468 libwebcam from the AUR].<br />
<br />
Issue the following command:<br />
<pre>uvcdynctrl --set "Exposure, Auto" 4</pre><br />
<br />
*'''NOTE:''' Be sure the "OS Installation" option is set to "finished" in the BIOS' "Advanced" tab or your camera may not work in some applications (like Skype).<br />
<br />
====Microphone====<br />
<br />
Solution for problems with the internal microphone.<br />
<br />
1. First of all set in alsamixer "Input Source" to "i-Mic"<br />
<br />
2. Increase "Capture" and "i-Mic Boost" to your needs<br />
<br />
3. Edit /etc/asound.state the following, change the 2 "false" to "true" like showing:<br />
<pre><br />
....snap.....<br />
control.11 {<br />
comment.access 'read write'<br />
comment.type BOOLEAN<br />
comment.count 2<br />
iface MIXER<br />
name 'Capture Switch'<br />
value.0 true<br />
value.1 true<br />
}<br />
....snap....</pre><br />
<br />
4. After editing run following as root<br />
<pre>alsactl restore</pre><br />
<br />
5. Now your internal microphone should be working.<br />
<br />
===Getting Hot Keys, Graphic Indicators and Shutdown with the Power Button Working===<br />
<br />
If you want to have working hot keys for changing brightness and volumes, graphic indicators working as well as shutdown when press the power button (just like in the stock Eee PC), then you should install ''''ighea's acpi-eee'''' or ''''dkite's acpid_eee'''' package.<br />
<br />
<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-8-1-i686.pkg.tar.gz<br />
<br />
See messages during installation for more details and don't forget to edit /etc/acpi/eee.conf to suit your tastes.<br />
<br />
<br />
==== dkite's acpid_eee ====<br />
<br />
Package can also be download form his [http://members.shaw.ca/dkite/ website]<br />
<br />
The package itself can be install with<br />
<br />
pacman -Uf acpid_eee-0.0.3-1-i686.pkg.tar.gz.tar<br />
<br />
<br />
With '''both''' packages don't forget to start asusosd if you want to have the Graphic Indicators from Xandros.<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 by adding the following line<br />
<br />
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind<br />
<br />
To your /etc/rc.local.shutdown should fix the problem.<br />
<br />
If this does not work, the module may not be able to be unloaded until after all services have finished. Do the above, then in /etc/rc.shutdown move <br />
<br />
if [ -x /etc/rc.local.shutdown ]; then<br />
/etc/rc.local.shutdown<br />
fi<br />
<br />
from where it was to directly above the line <br />
<br />
# Terminate all processes<br />
<br />
this will cause the rc.local.shutdown script to run after services have been exited. This fixed all issues for the person editing this note.<br />
<br />
==Additional Tips & Tweaks==<br />
===Power down with the power button===<br />
<br />
*''If you use dkite's acpid_eee package then you should already be able to shutdown by pressing the power button and should not need to do this.''<br />
<br />
The two alternatives here are described in [[Allow_users_to_shutdown]].<br />
<br />
If you don't already or don't plan to use sudo, it may be simpler to use the setuid /sbin/halt method, otherwise using sudo is preferred.<br />
<br />
Below are all the steps required for the sudo method. If you want to use the setuid method, read the article linked above and perform the 'power' file step here, while omitting the 'sudo' in it.<br />
<br />
<pre>pacman -S sudo</pre><br />
<br />
As root, do the following:<br />
<br />
<pre>visudo</pre><br />
<br />
Add the following line to the file:<br />
<br />
<pre>USER HOST = NOPASSWD: /sbin/poweroff</pre><br />
<br />
Where USER = the user you want to be able to power down with and HOST = your hostname (from /etc/rc.conf).<br />
<br />
Now, create a file called /etc/acpi/events/power, containing:<br />
<br />
<pre># /etc/acpi/events/power<br />
# This is called when the user presses the power button<br />
<br />
event=button/power (PWR.||PBTN)<br />
action=sudo /sbin/poweroff</pre><br />
<br />
Make sure that you execute<br />
<br />
<pre>/etc/rc.d/acpid start</pre><br />
<br />
And/or add acpid to the daemons list in /etc/rc.conf:<br />
<br />
<pre>DAEMONS=(hal, acpid ...</pre><br />
<br />
===Compile the 'everything' Kernel===<br />
<br />
The 'everything' kernel has ath5k, which supports the Atheros chipset found on the EEE PC. Here are the [http://linuxwireless.org/en/users/Drivers/ath5k#Hackingath5k instructions on compiling the 'everthing' kernel] (thanks raymano!).<br />
<br />
===Use cpufreq for power saving===<br />
For scaling down the processor you have to load the p4_clockmod. Insert it into your /etc/rc.conf MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
Then proceed like [http://wiki.archlinux.org/index.php/SpeedStep#Alternative_Methods here]. <br />
Add the following into /etc/conf.d/cpufreq<br />
governor="ondemand"<br />
min_freq="113MHz"<br />
max_freq="900MHz"<br />
With enabled cpufreq it scales the processor between 113MHz up to max. frequency. That should save a lot on battery power. The stated 900MHz will be never reached by the eeePC, the p4_clockmod reports a wrong frequency here. But scaling works, you can feel it in the performance of eeePC that he slow down the processor.<br />
<br />
===More responsive system with ondemand governor===<br />
The default up_threshold (where it will bump to a faster speed) for the CPU governor is 80, which means it will increase the CPU speed when utilization is above 80%. This can make X applications have a bit of lag. <br />
Try changing this value:<br />
sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
With 40 it still leaves the majority of CPU cycles at the lowest available clock speed but increases responsiveness. You can add this line to one of your startup scripts if you wish to keep it, for example in /etc/rc.local.<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 />
===Update your BIOS without Xandros===<br />
'''Warning : you can broke your system, do not update if you are not sure of what you are doing !'''<br />
<br />
First, you need to download the ''.rom'' file.<br />
*[http://update.eeepc.asus.com/bios/ Asus official's BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USBStick formated in fat32.<br />
To format an USBStick, use cfdick tool :<br />
cfdick /dev/sdc #could be something else than "c"<br />
Choose [delete], [type] : "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
cp /somewhere/blabla/.../thecurrentnameofthefile.rom /dev/sdc1/701.rom<br />
The name of the copy '''must''' be 701.rom<br />
<br />
Next step, reboot the eeepc with the USBStick pluged-in, and press<br />
Alt + F2<br />
It will launch the built-in tool. Everything should be Ok, you can make a coffee during the update. When it asks you to push the power-button it has finished.<br />
<br />
<br />
At the next boot, you'll be invited to configure the BIOS. Check if the everything is enable (my webcam and wireless were disable after the update) and if it displays the good version in the main screen. It's done !<br />
<br />
==Known problems and their solutions==<br />
<br />
===Booting from card without initrd===<br />
<br />
Let's say you decided to install Arch Linux on a card and compiled your own kernel (or used the kernel26eee kernel) without initrd. Card reader on EeePC is connected as an USB device. Unfortunately, USB storage devices are detected with a delay, so we must tell the kernel to wait until this device becomes available. You do this with "rootwait" option passed to kernel at boot time.<br />
<br />
===Sleeping and waking system on a card===<br />
<br />
If you have Arch Linux on a card, waking up from sleeping state will most likely fail. The only solution is to enable the CONFIG_USB_PERSIST option in kernel. The kernel26eee package should have this option enabled.<br />
<br />
===Display doesn't wake up properly===<br />
<br />
If you encounter black display (but apparently working system) after suspend/resume, consider using the "uswsusp" package (available in AUR) and correcting suspend2ram script in /etc/acpi, where you use this line to make the machine go to sleep:<br />
<br />
<pre>/usr/sbin/s2ram --force --vbe_post --vbe_mode</pre></div>
Faelar
https://wiki.archlinux.org/index.php?title=Openbox&diff=37617
Openbox
2008-02-24T12:38:04Z
<p>Faelar: /* Panels */</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Openbox}}<br />
{{i18n_entry|Русский|Openbox (Русский)}}<br />
{{i18n_links_end}}<br />
<br />
= Introduction =<br />
<br />
Openbox is a lightweight and highly configurable window manager with extensive standards support. Its features are well-documented at the [http://icculus.org/openbox/ official website]. This article will pertain to running Openbox under Arch Linux.<br />
<br />
<br />
= Installation =<br />
Openbox is available from the standard repositories:<br />
# pacman -S openbox<br />
<br />
Once installed, pacman will direct you to copy the default <tt>menu.xml</tt> & <tt>rc.xml</tt> configuration files to <tt>~/.config/openbox/</tt>, for example:<br />
<br />
$ mkdir -p ~/.config/openbox/<br />
$ cp /etc/xdg/openbox/rc.xml ~/.config/openbox/rc.xml<br />
$ cp /etc/xdg/openbox/menu.xml ~/.config/openbox/menu.xml<br />
$ cp /etc/xdg/openbox/autostart.sh ~/.config/openbox/autostart.sh<br />
'''''Note:''' do this as a regular user, not as root.''<br />
<br />
The rc.xml file is the core configuration file for Openbox. It is used to manage keyboard shortcuts, themes, virtual desktops and other features.<br />
<br />
The menu.xml file controls the Openbox application menu that appears when you right-click on your desktop. The default items are pretty sparse (if not entirely useless), but it's very easy to modify the menu structure to suit your needs. See the menu section below for more details, or visit the [http://icculus.org/openbox/ Openbox website].<br />
<br />
The [http://wiki.archlinux.org/index.php/Openbox#Startup_Programs autostart.sh file] controls what programs start up when you start the openbox-session.<br />
<br />
= Getting Started =<br />
<br />
== Using Openbox ==<br />
To run Openbox on its own, simply add the following to the bottom of ~/.xinitrc:<br />
exec openbox-session<br />
<br />
== Using Openbox with GNOME ==<br />
# If you use GDM, select the "GNOME/Openbox" login option<br />
# If you use startx, add '''exec openbox-gnome-session''' to ~/.xinitrc<br />
<br />
== Using Openbox with KDE ==<br />
# If you use KDM, select the "KDE/Openbox" login option<br />
# If you use startx, add '''exec openbox-kde-session''' to ~/.xinitrc<br />
<br />
= Configuration =<br />
<br />
== Preferences ==<br />
Currently, there are two options for configuring the core Openbox preferences; manually edit the '''rc.xml''', or use the ObConf tool.<br />
<br />
=== Setting Preferences Manually ===<br />
<br />
To configure Openbox manually, simply edit '''~/.config/openbox/rc.xml''' with your favourite text editor.<br />
<br />
=== Setting Preferences with ObConf ===<br />
<br />
[http://icculus.org/openbox/index.php/ObConf:About ObConf] is GUI-based Openbox configuration tool, which can be used to set most preferences including themes, virtual desktops, window properties and desktop margins.<br />
<br />
To install ObConf, run:<br />
# pacman -S obconf<br />
<br />
Currently, ObConf cannot be used to manage keyboard shortcuts and a few other advanced features. For these modifications, the user must resort to editing the '''rc.xml''' manually.<br />
<br />
== Menu Management ==<br />
<br />
The default Openbox menu is pretty basic and if you don't have any of the listed programs installed, it is downright useless. There are a number of ways to customize your menu.<br />
<br />
=== MenuMaker ===<br />
[http://menumaker.sourceforge.net/ MenuMaker] is a powerful tool that creates XML-based menus for a variety of Window Managers, including Openbox. MenuMaker will search your computer for executable programs and create an XML menu based on the results. It can be configured to exclude Legacy X, GNOME, KDE, or Xfce applications if the user desires.<br />
<br />
MenuMaker is available from the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10894&O=0&L=0&C=0&K=menumaker&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd AUR]. <br />
<br />
Once installed, you can generate a complete menu by running:<br />
$ mmaker -v OpenBox3<br />
<br />
By default, MenuMaker will not overwrite an existing menu.xml. To do so, run it with the -f (force) argument:<br />
<br />
$ mmaker -vf OpenBox3<br />
<br />
To see a full list of options, run '''mmaker --help'''<br />
<br />
This will give you a pretty thorough menu. Now you can modify the menu.xml by hand, or simply regenerate the list whenever you install new software.<br />
<br />
=== Obmenu ===<br />
Obmenu is a GUI-based menu editor for Openbox. For those who don't enjoy mucking about in XML source code, this is probably the best option for you.<br />
<br />
It's available in the standard repositories:<br />
# pacman -S obmenu<br />
<br />
Once installed, simply run '''obmenu''' and add or remove the desired applications.<br />
<br />
==== obm-xdg ====<br />
<tt>obm-xdg</tt> is a command-line tool that comes with Obmenu. It can generate a categorized sub-menu of installed GTK/GNOME applications.<br />
<br />
To use obm-xdg, add the following line to '''~/.config/openbox/menu.xml''':<br />
<br />
<menu execute="obm-xdg" id="xdg-menu" label="xdg"/><br />
<br />
Then run '''openbox --reconfigure''' to refresh the Openbox menu. You should now see a sub-menu labeled '''xdg''' in your menu.<br />
<br />
== Startup Programs ==<br />
Openbox 3.4+ features support for running programs at startup. This is provided by the "openbox-session" command.<br />
<br />
There are two ways to enable autostart:<br />
# If you use startx to log into your X session, change the line that executes ''openbox'' to execute '''openbox-session''' instead.<br />
# If you log in with GDM/KDM, then select the ''Openbox'' session and it will automatically use autostart.<br />
<br />
Startup programs are managed in '''~/.config/openbox/autostart.sh'''. Full instructions and best practices for how to do this are available at the [http://icculus.org/openbox/index.php/Help:Autostart Openbox website].<br />
<br />
== Theming and Appearance ==<br />
Aside from the Openbox Themes, the following section is intended for users who have configured Openbox to run as a standalone desktop, without the assistance of GNOME or KDE.<br />
<br />
=== Openbox Themes ===<br />
Openbox themes control the appearance of window borders, including the titlebar and titlebar buttons. <br />
<br />
Additional themes are available from the standard repositories:<br />
<br />
# pacman -S openbox-themes<br />
<br />
This package is by no means definitive. [http://www.box-look.org/index.php?xcontentmode=7402 box-look.org] is another great resource for Openbox themes.<br />
<br />
Downloaded themes should be extracted to '''~/.themes''' and can be installed or selected with the [[Openbox#Preferences|ObConf]] tool.<br />
<br />
Creating new themes is fairly easy and again [http://icculus.org/openbox/index.php/Help:Themes well-documented].<br />
<br />
=== Desktop Wallpaper ===<br />
<br />
Openbox itself does not include a way to change the wallpaper. This can be done easily with programs like [[Feh]] or [[Nitrogen]]. Other options include ImageMagick, hsetroot and xsetbg.<br />
<br />
=== GTK Themes ===<br />
GTK2 themes can be managed easily with gtk-chtheme:<br />
# pacman -S gtk-chtheme<br />
<br />
Simply run '''gtk-chtheme''' and set the desired theme.<br />
<br />
For legacy GTK1 themes, install the '''gtk-theme-switch''' package and run '''''switch'''''.<br />
<br />
=== GTK Fonts ===<br />
If you want to change the type and size of your fonts, add the following to '''~/.gtkrc.mine''':<br />
style "user-font"<br />
{<br />
font_name = "[font-name] [size]"<br />
}<br />
widget_class "*" style "user-font"<br />
gtk-font-name = "[font-name] [size]"<br />
<br />
where [font-name] [size] is the desired font and point size. For example:<br />
style "user-font"<br />
{<br />
font_name = "DejaVu Sans 8"<br />
}<br />
widget_class "*" style "user-font"<br />
gtk-font-name = "DejaVu Sans 8"<br />
<br />
Both <tt>font_name</tt> and <tt>gtk-font-name</tt> fields are required for backwards compatibility.<br />
<br />
=== GTK Icons ===<br />
Extract the desired icon theme to '''/usr/share/icons''' (system-wide access) or '''~/.icons''' (local user access).<br />
<br />
Add the following to ~/.gtkrc.mine: <br />
gtk-icon-theme-name = "[name-of-icon-theme]"<br />
<br />
where [name-of-icon-theme] is the name of the icon theme directory. For example:<br />
gtk-icon-theme-name = "Tango"<br />
<br />
=== Mouse cursor themes ===<br />
Extract the desired Xcursor theme to either '''/usr/share/icons''' (system-wide access) or '''~/.icons''' (local user access).<br />
<br />
Add this to ~/.Xdefaults:<br />
Xcursor.theme: [name-of-cursor-theme]<br />
where [name-of-cursor-theme] is the name of the cursor theme directory. For example:<br />
Xcursor.theme: Vanilla-DMZ-AA<br />
<br />
=== Desktop Icons ===<br />
Openbox does not provide a means to display icons on the desktop. [http://rox.sourceforge.net ROX], [http://idesk.sourceforge.net iDesk], or even Nautilus (and the gnome-settings-daemon) can provide this function. <br />
<br />
ROX has the additional advantage of being a lightweight file manager.<br />
<br />
= Tips & Tricks =<br />
<br />
== Recommended Programs == <br />
<br />
=== Login Managers ===<br />
[http://slim.berlios.de/ SLiM] provides a lightweight and elegant graphical login solution for standalone Openbox configurations. Refer to Arch's [[SLiM]] wiki for detailed instructions.<br />
<br />
=== Composite Desktop ===<br />
[[Xcompmgr]] is a lightweight composite manager capable of rendering drop shadows, fading and simple window transparency within Openbox and other window managers.<br />
<br />
=== Run dialog ===<br />
[http://sourceforge.net/projects/gmrun gmrun] provides an excellent Run dialog box, similar to the Alt+F2 features found in Gnome and KDE:<br />
pacman -S gmrun<br />
Add the following entry to the <keyboard> section '''~/.config/openbox/rc.xml''' to enable Alt+F2 functionality:<br />
<keybind key="A-F2"><br />
<action name="execute"><execute>gmrun</execute></action><br />
</keybind><br />
<br />
=== File managers ===<br />
<br />
There are many possibilities, but the most popular lightweight file managers are:<br />
* [http://thunar.xfce.org Thunar] (Supports auto-mount features and other plugins)<br />
* [http://rox.sourceforge.net ROX] (ROX can also provide desktop icons)<br />
* [http://pcmanfm.sourceforge.net PCMan] (pcmanfm)<br />
<br />
For even lighter options, consider [http://www.obsession.se/gentoo/ Gentoo] or [http://emelfm.sourceforge.net/ emelFM], both of which use the familiar 'Midnight Commander' two pane layout (these two require gtk 1.2.x).<br />
<br />
Of course, you can also use GNOME's Nautilus. Although slower than the above solutions, it has the additional advantage of VFS support (e.g. remote SSH, FTP and Samba connections).<br />
<br />
=== Panels ===<br />
<br />
There are quite a lot of panels you can install to provide a taskbar and pager to Openbox. The most common are:<br />
<br />
* [http://nsf.110mb.com/bmpanel/ bmpanel]<br />
* [http://wiki.archlinux.org/index.php/PyPanel PyPanel]<br />
* [http://code.google.com/p/ttm/ Tint]<br />
* [http://projects.l3ib.org/trac/visibility Visibility]<br />
* [http://sourceforge.net/projects/lxpanel LXPanel]<br />
* [http://fbpanel.sourceforge.net fbpanel]<br />
* [http://perlpanel.org/ PerlPanel]<br />
* [http://www.chatjunkies.org/fspanel/ fspanel]<br />
* [http://www.xfce.org/projects/xfce4-panel/ xfce4-panel]<br />
* [http://developer.gnome.org/arch/gnome/corecomponents/panel/ gnome-panel]<br />
* [http://bbtools.sourceforge.net/ bbpager]<br />
<br />
Make your choice and add it to your startup file.<br />
<br />
== Per-application settings ==<br />
Openbox has per-application settings since openbox 3.3<br />
These settings can be set in ~/.config/openbox/rc.xml by creating new XML element inside <openbox_config> called <applications>, which will contain the settings. Inside <applications> you will need <application name=""> which will determine which application this setting is going to affect. The ways to determine the application are name, class and role, eg.<br />
<application class="Firefox-bin"><br />
The class and name can be found by running<br />
xprop | grep WM_CLASS<br />
When you click the application you want to configure, it will return something like<br />
WM_CLASS(STRING) = "Gecko", "Thunderbird-bin"<br />
The first one is what you put inside name="" and the latter one is for class="", you can use either one, but I prefer the one which doesn't get mixed with anything.<br />
After this you need to set the settings you want, available settings are <br />
decor - whether window has borders, titlebar and so on, values yes or no, on or off <br />
shade - whether the window is shaded to the titlebar or not (doesn't work with decorations off), values yes, no, on, off and so on<br />
position - position of the window when started needs subsection<br />
<x>pos</x> - position on pixels reading from top left corner<br />
<y>pos</y> - center as value and such work too, you can also leave x or y out if you only want to adjust one value.<br />
focus - whether the window gets focused when starting it (not sure about this), values yes no and so on<br />
desktop - desktop (workspace) the application starts, value desktop number reading from 0 (if its opened to another desktop, it doesn't get focused)<br />
monitor - xinerama head the application starts (useful when you have 2 monitors and want the application to open in another, eg nvidia twinview uses xinerama), values 0 1 screennumber and such<br />
layer - layer the application starts on, values Bottom, Normal and Top<br />
iconic - whether the application is to be launched iconic, values yes, no, on, off and so on<br />
skip_pager - application skips pager, values yes, no, on, off and so on<br />
skip_taskbar - same as above, just taskbar, values yes, no, on, off and so on<br />
fullscreen - whether app should be started fullscreen, values yes, no, on, off and so on<br />
maximized - type of maximization, values Horizontal, Vertical, yes, no, on, off and so on.<br />
Example config showing firefox opening 30 pixels from top centered with horizontal maximization<br />
<applications><br />
<application class="Firefox-bin"><br />
<position><br />
<x>center</x><br />
<y>30</y><br />
</position><br />
<maximized>Horizontal</maximized><br />
</application><br />
</applications><br />
== Linking the menu to a command ==<br />
Some people would want to link the Openbox main menu, or any other, to a command. This is useful for creating a menu button in a panel, for example. Although Openbox doesn't supprt this, a very simple script , xdotool, can simulate a keypress by running a command. Xdotool is available on AUR [http://aur.archlinux.org/packages.php?do_Details=1&ID=14789&O=0&L=0&C=0&K=xdotool&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd here]. To use it, simply add the following code to the <keyboard> section of your rc.xml:<br />
<keybind key="A-C-q"><br />
<action name="ShowMenu"><br />
<menu>root-menu</menu><br />
</action><br />
</keybind><br />
Restart/reconfigure Openbox. You can now magically summon your menu at your cursor position by running the following command:<br />
# xdotool key ctrl+alt+q<br />
Of course, you can change the shortcup to your liking.<br />
<br />
= Additional Resources =<br />
* [http://icculus.org/openbox/ Openbox Website] - The official website<br />
* [http://planetob.openmonkey.com/ Planet Openbox] - Openbox news portal<br />
* [http://www.box-look.org/ Box-Look.org] - A good resource for themes and related artwork</div>
Faelar
https://wiki.archlinux.org/index.php?title=GRUB_Legacy&diff=32583
GRUB Legacy
2007-11-20T13:12:29Z
<p>Faelar: /* Dual boot Arch / Windows XP */</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|GRUB}}<br />
{{i18n_entry|עברית|GRUB (עברית)}}<br />
{{i18n_entry|简体中文|GRUB(简体中文)}}<br />
{{i18n_entry|Русский|GRUB (Русский)}}<br />
{{i18n_links_end}}<br />
GRand Unified Bootloader (GRUB)<br />
<br />
== Installing Grub package ==<br />
<br />
First install grub with pacman<br />
<br />
<br />
pacman -Sy grub<br />
<br />
<br />
Edit the menu.lst with your settings<br />
<br />
<br />
nano /boot/grub/menu.lst<br />
<br />
<br />
''Note: Use hd[a-z] for ide and sd[a-z] for scsi and sata''<br />
<br />
Here is mine for example:<br />
<br />
<br />
# Config file for GRUB - The GNU GRand Unified Bootloader<br />
# /boot/grub/menu.lst<br />
<br />
# DEVICE NAME CONVERSIONS <br />
#<br />
# Linux Grub<br />
# -------------------------<br />
# /dev/fd0 (fd0)<br />
# /dev/hda (hd0)<br />
# /dev/hdb2 (hd1,1)<br />
# /dev/hda3 (hd0,2)<br />
#<br />
<br />
# FRAMEBUFFER RESOLUTION SETTINGS<br />
# +-------------------------------------------------+<br />
# | 640x480 800x600 1024x768 1280x1024<br />
# ----+--------------------------------------------<br />
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775<br />
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793<br />
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794<br />
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795<br />
# +-------------------------------------------------+<br />
<br />
# general configuration:<br />
timeout 5<br />
default 1<br />
color light-blue/black light-cyan/blue<br />
<br />
# boot sections follow<br />
# each is implicitly numbered from 1 in the order of appearance below<br />
#<br />
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.<br />
#<br />
#-*<br />
<br />
# (0) Arch Linux<br />
title Arch Linux [cpio]<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda6 ro vga=773<br />
initrd /kernel26.img<br />
<br />
title Arch Linux [thinkpad]<br />
root (hd0,0)<br />
kernel /vmlinuz26thinkpad root=/dev/sda6 ro video=vesafb:off acpi_sleep=s3_bios<br />
resume2=swap:/dev/sda5<br />
initrd /kernel26thinkpad.img<br />
<br />
<br />
Copy the mounts to mtab<br />
<br />
<br />
grep -v rootfs /proc/mounts > /etc/mtab<br />
<br />
Install grub<br />
<br />
grub-install /dev/sda<br />
<br />
--[[User:Fk|Fk]] 06:26, 25 August 2006 (PDT)<br />
<br />
== Installing the boot loader into Master Boot Record ==<br />
<br />
grub-install -root-directory ''Mount-Point'' (hd''n'') <br />
<br />
Installs grub into the MBR of a hard disc. The option gives the path to the kernel-image, if it is not in <code>/</code>, f.e. in <code>/boot</code>.<br><br />
(hd''n'') is a disc, where n is the number of the disc, starting with 0.<br />
<br />
Example:<br />
grub-install --root-directory=/boot '(hd0)'<br />
<br />
grub-install /dev/sda<br />
<br />
== Boot loader configuration ==<br />
The grub configuration is done in this file:<br />
/boot/grub/menu.lst<br />
<br />
* <i>(hdn,m)</i> is the partition m on disc n, numbers starting with 0<br />
* <i>splashimage (hdn,m)/grub/Name.xpm.gz</i> is the splash-image-file<br />
* <i>default n</i> is the default boot entry, that is choosen after timout for user action<br />
* <i>timeout m</i> time m to wait in seconds for a user selection, before default is booted<br />
* <i>password -md5 str</i> encrypted boot password 'str'<br />
* <i>title str</i> title string 'str' for a boot entry<br />
* <i>root (hdn,m)</i> base partition, where the kernel is stored to<br />
* <i>kernel /path ro root=/dev/device initrd /initrd.img</i> use the root option, if the kernel not placed in /<br />
* <i>makeactive<br>chainloader +1</i> sets root active and gives booting procedure to its boot-loader (for Windows, f.e.)<br />
* <i>map (hd0) (hd1)<br>map (hd1) (hd0)</i> changes primary and secondary disc for a boot, necessary to boot Windows from a secondary disc<br />
* <i>root (hdn,m,z)<br>kernel /boot/loader</i> boots the FreeBSD-Partition x<br />
* <i>default saved</i> remembers each current boot selection and makes it the new default. Place "savedefault" at the end of each boot section, for that you want this feature shall be used.<br />
<br />
For those who like eye-candy, there is [[Graphical GRUB]].<br />
<br />
<br />
=== Dual boot Arch / Windows XP ===<br />
<br />
Just add this at the end of your /boot/grub/menu.lst<br />
<br />
# (2) Windows XP<br />
title Windows XP<br />
rootnoverify (hd0,0)<br />
makeactive<br />
chainloader +1<br />
<br />
=== LiLO and GRUB interaction ===<br />
<br />
If you once had used [[lilo]] Don't forget to remove it with <br />
pacman -R lilo<br />
as some tasks (f.e. kernel compilation using <code>make all</code>) will make a lilo call, and then lilo is installed over grub.<br />
Note that this will not remove lilo from the MBR, but it will be overwritten when you install another bootloader.<br />
<br />
* Read also [[Grub configure examples]]<br />
<br />
== Troubleshooting==<br />
<br />
* If you are having problems like grub freezing when you do a grub install, use the command abs to get the PKGBUILDS of the arch base packages and then use the command as root:<br />
<br />
cd /var/abs/base/grub/<br />
./install-grub<br />
<br />
== External Resources ==<br />
* [http://www.gnu.org/software/grub/ Grub Website]</div>
Faelar
https://wiki.archlinux.org/index.php?title=GRUB_Legacy&diff=32582
GRUB Legacy
2007-11-20T13:11:54Z
<p>Faelar: /* Dual boot Arch / Windows XP */</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|GRUB}}<br />
{{i18n_entry|עברית|GRUB (עברית)}}<br />
{{i18n_entry|简体中文|GRUB(简体中文)}}<br />
{{i18n_entry|Русский|GRUB (Русский)}}<br />
{{i18n_links_end}}<br />
GRand Unified Bootloader (GRUB)<br />
<br />
== Installing Grub package ==<br />
<br />
First install grub with pacman<br />
<br />
<br />
pacman -Sy grub<br />
<br />
<br />
Edit the menu.lst with your settings<br />
<br />
<br />
nano /boot/grub/menu.lst<br />
<br />
<br />
''Note: Use hd[a-z] for ide and sd[a-z] for scsi and sata''<br />
<br />
Here is mine for example:<br />
<br />
<br />
# Config file for GRUB - The GNU GRand Unified Bootloader<br />
# /boot/grub/menu.lst<br />
<br />
# DEVICE NAME CONVERSIONS <br />
#<br />
# Linux Grub<br />
# -------------------------<br />
# /dev/fd0 (fd0)<br />
# /dev/hda (hd0)<br />
# /dev/hdb2 (hd1,1)<br />
# /dev/hda3 (hd0,2)<br />
#<br />
<br />
# FRAMEBUFFER RESOLUTION SETTINGS<br />
# +-------------------------------------------------+<br />
# | 640x480 800x600 1024x768 1280x1024<br />
# ----+--------------------------------------------<br />
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775<br />
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793<br />
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794<br />
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795<br />
# +-------------------------------------------------+<br />
<br />
# general configuration:<br />
timeout 5<br />
default 1<br />
color light-blue/black light-cyan/blue<br />
<br />
# boot sections follow<br />
# each is implicitly numbered from 1 in the order of appearance below<br />
#<br />
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.<br />
#<br />
#-*<br />
<br />
# (0) Arch Linux<br />
title Arch Linux [cpio]<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda6 ro vga=773<br />
initrd /kernel26.img<br />
<br />
title Arch Linux [thinkpad]<br />
root (hd0,0)<br />
kernel /vmlinuz26thinkpad root=/dev/sda6 ro video=vesafb:off acpi_sleep=s3_bios<br />
resume2=swap:/dev/sda5<br />
initrd /kernel26thinkpad.img<br />
<br />
<br />
Copy the mounts to mtab<br />
<br />
<br />
grep -v rootfs /proc/mounts > /etc/mtab<br />
<br />
Install grub<br />
<br />
grub-install /dev/sda<br />
<br />
--[[User:Fk|Fk]] 06:26, 25 August 2006 (PDT)<br />
<br />
== Installing the boot loader into Master Boot Record ==<br />
<br />
grub-install -root-directory ''Mount-Point'' (hd''n'') <br />
<br />
Installs grub into the MBR of a hard disc. The option gives the path to the kernel-image, if it is not in <code>/</code>, f.e. in <code>/boot</code>.<br><br />
(hd''n'') is a disc, where n is the number of the disc, starting with 0.<br />
<br />
Example:<br />
grub-install --root-directory=/boot '(hd0)'<br />
<br />
grub-install /dev/sda<br />
<br />
== Boot loader configuration ==<br />
The grub configuration is done in this file:<br />
/boot/grub/menu.lst<br />
<br />
* <i>(hdn,m)</i> is the partition m on disc n, numbers starting with 0<br />
* <i>splashimage (hdn,m)/grub/Name.xpm.gz</i> is the splash-image-file<br />
* <i>default n</i> is the default boot entry, that is choosen after timout for user action<br />
* <i>timeout m</i> time m to wait in seconds for a user selection, before default is booted<br />
* <i>password -md5 str</i> encrypted boot password 'str'<br />
* <i>title str</i> title string 'str' for a boot entry<br />
* <i>root (hdn,m)</i> base partition, where the kernel is stored to<br />
* <i>kernel /path ro root=/dev/device initrd /initrd.img</i> use the root option, if the kernel not placed in /<br />
* <i>makeactive<br>chainloader +1</i> sets root active and gives booting procedure to its boot-loader (for Windows, f.e.)<br />
* <i>map (hd0) (hd1)<br>map (hd1) (hd0)</i> changes primary and secondary disc for a boot, necessary to boot Windows from a secondary disc<br />
* <i>root (hdn,m,z)<br>kernel /boot/loader</i> boots the FreeBSD-Partition x<br />
* <i>default saved</i> remembers each current boot selection and makes it the new default. Place "savedefault" at the end of each boot section, for that you want this feature shall be used.<br />
<br />
For those who like eye-candy, there is [[Graphical GRUB]].<br />
<br />
<br />
=== Dual boot Arch / Windows XP ===<br />
<br />
Just add this to your /boot/grub/menu.lst<br />
<br />
# (2) Windows XP<br />
title Windows XP<br />
rootnoverify (hd0,0)<br />
makeactive<br />
chainloader +1<br />
<br />
=== LiLO and GRUB interaction ===<br />
<br />
If you once had used [[lilo]] Don't forget to remove it with <br />
pacman -R lilo<br />
as some tasks (f.e. kernel compilation using <code>make all</code>) will make a lilo call, and then lilo is installed over grub.<br />
Note that this will not remove lilo from the MBR, but it will be overwritten when you install another bootloader.<br />
<br />
* Read also [[Grub configure examples]]<br />
<br />
== Troubleshooting==<br />
<br />
* If you are having problems like grub freezing when you do a grub install, use the command abs to get the PKGBUILDS of the arch base packages and then use the command as root:<br />
<br />
cd /var/abs/base/grub/<br />
./install-grub<br />
<br />
== External Resources ==<br />
* [http://www.gnu.org/software/grub/ Grub Website]</div>
Faelar
https://wiki.archlinux.org/index.php?title=GRUB_Legacy&diff=32581
GRUB Legacy
2007-11-20T13:10:46Z
<p>Faelar: </p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|GRUB}}<br />
{{i18n_entry|עברית|GRUB (עברית)}}<br />
{{i18n_entry|简体中文|GRUB(简体中文)}}<br />
{{i18n_entry|Русский|GRUB (Русский)}}<br />
{{i18n_links_end}}<br />
GRand Unified Bootloader (GRUB)<br />
<br />
== Installing Grub package ==<br />
<br />
First install grub with pacman<br />
<br />
<br />
pacman -Sy grub<br />
<br />
<br />
Edit the menu.lst with your settings<br />
<br />
<br />
nano /boot/grub/menu.lst<br />
<br />
<br />
''Note: Use hd[a-z] for ide and sd[a-z] for scsi and sata''<br />
<br />
Here is mine for example:<br />
<br />
<br />
# Config file for GRUB - The GNU GRand Unified Bootloader<br />
# /boot/grub/menu.lst<br />
<br />
# DEVICE NAME CONVERSIONS <br />
#<br />
# Linux Grub<br />
# -------------------------<br />
# /dev/fd0 (fd0)<br />
# /dev/hda (hd0)<br />
# /dev/hdb2 (hd1,1)<br />
# /dev/hda3 (hd0,2)<br />
#<br />
<br />
# FRAMEBUFFER RESOLUTION SETTINGS<br />
# +-------------------------------------------------+<br />
# | 640x480 800x600 1024x768 1280x1024<br />
# ----+--------------------------------------------<br />
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775<br />
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793<br />
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794<br />
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795<br />
# +-------------------------------------------------+<br />
<br />
# general configuration:<br />
timeout 5<br />
default 1<br />
color light-blue/black light-cyan/blue<br />
<br />
# boot sections follow<br />
# each is implicitly numbered from 1 in the order of appearance below<br />
#<br />
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.<br />
#<br />
#-*<br />
<br />
# (0) Arch Linux<br />
title Arch Linux [cpio]<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda6 ro vga=773<br />
initrd /kernel26.img<br />
<br />
title Arch Linux [thinkpad]<br />
root (hd0,0)<br />
kernel /vmlinuz26thinkpad root=/dev/sda6 ro video=vesafb:off acpi_sleep=s3_bios<br />
resume2=swap:/dev/sda5<br />
initrd /kernel26thinkpad.img<br />
<br />
<br />
Copy the mounts to mtab<br />
<br />
<br />
grep -v rootfs /proc/mounts > /etc/mtab<br />
<br />
Install grub<br />
<br />
grub-install /dev/sda<br />
<br />
--[[User:Fk|Fk]] 06:26, 25 August 2006 (PDT)<br />
<br />
== Installing the boot loader into Master Boot Record ==<br />
<br />
grub-install -root-directory ''Mount-Point'' (hd''n'') <br />
<br />
Installs grub into the MBR of a hard disc. The option gives the path to the kernel-image, if it is not in <code>/</code>, f.e. in <code>/boot</code>.<br><br />
(hd''n'') is a disc, where n is the number of the disc, starting with 0.<br />
<br />
Example:<br />
grub-install --root-directory=/boot '(hd0)'<br />
<br />
grub-install /dev/sda<br />
<br />
== Boot loader configuration ==<br />
The grub configuration is done in this file:<br />
/boot/grub/menu.lst<br />
<br />
* <i>(hdn,m)</i> is the partition m on disc n, numbers starting with 0<br />
* <i>splashimage (hdn,m)/grub/Name.xpm.gz</i> is the splash-image-file<br />
* <i>default n</i> is the default boot entry, that is choosen after timout for user action<br />
* <i>timeout m</i> time m to wait in seconds for a user selection, before default is booted<br />
* <i>password -md5 str</i> encrypted boot password 'str'<br />
* <i>title str</i> title string 'str' for a boot entry<br />
* <i>root (hdn,m)</i> base partition, where the kernel is stored to<br />
* <i>kernel /path ro root=/dev/device initrd /initrd.img</i> use the root option, if the kernel not placed in /<br />
* <i>makeactive<br>chainloader +1</i> sets root active and gives booting procedure to its boot-loader (for Windows, f.e.)<br />
* <i>map (hd0) (hd1)<br>map (hd1) (hd0)</i> changes primary and secondary disc for a boot, necessary to boot Windows from a secondary disc<br />
* <i>root (hdn,m,z)<br>kernel /boot/loader</i> boots the FreeBSD-Partition x<br />
* <i>default saved</i> remembers each current boot selection and makes it the new default. Place "savedefault" at the end of each boot section, for that you want this feature shall be used.<br />
<br />
For those who like eye-candy, there is [[Graphical GRUB]].<br />
<br />
<br />
=== Dual boot Arch / Windows XP ===<br />
<br />
Juste add this to your /boot/grub/menu.lst<br />
<br />
# (2) Windows XP<br />
title Windows XP<br />
rootnoverify (hd0,0)<br />
makeactive<br />
chainloader +1<br />
<br />
=== LiLO and GRUB interaction ===<br />
<br />
If you once had used [[lilo]] Don't forget to remove it with <br />
pacman -R lilo<br />
as some tasks (f.e. kernel compilation using <code>make all</code>) will make a lilo call, and then lilo is installed over grub.<br />
Note that this will not remove lilo from the MBR, but it will be overwritten when you install another bootloader.<br />
<br />
* Read also [[Grub configure examples]]<br />
<br />
== Troubleshooting==<br />
<br />
* If you are having problems like grub freezing when you do a grub install, use the command abs to get the PKGBUILDS of the arch base packages and then use the command as root:<br />
<br />
cd /var/abs/base/grub/<br />
./install-grub<br />
<br />
== External Resources ==<br />
* [http://www.gnu.org/software/grub/ Grub Website]</div>
Faelar