Anleitung für Einsteiger: Unterschied zwischen den Versionen

Aus wiki.archlinux.de
← Zum vorherigen VersionsunterschiedZum nächsten Versionsunterschied →
*>Doehni
KKeine Bearbeitungszusammenfassung
*>Doehni
further translation
Zeile 179: Zeile 179:
=====/etc/hosts=====
=====/etc/hosts=====


to be continued...
Füge den gewünschten ''hostname'' hinzu (welchen Du in /etc/rc.conf zuvor gesetzt hast), so dass es in etwa so ausschaut wie folgt:
127.0.0.1  localhost.localdomain  localhost ''dein-hostname''
''Dieses Format, '''inklusive den 'localhost'-Einträgen''' wird für Programmkompatibilität benötigt! Fehler in diesem Syntax führen dazu, dass sich Programme sehr langsam öffnen.<br>Die ist bei Anfängern ein ziemlich häufiger Fehler.''
 
Für die meisten Benutzer wird es reichen, einfach ''dein-hostname'' ans Ende der Standardlinie hinzuzufügen. Jedoch raten einige Nutzer dazu, folgenden Syntax zu benutzen:
127.0.0.1  ''dein-hostname''.domaene.org localhost.localdomain  localhost  ''dein-hostname''
Falls Du eine statische IP benutzt, füge eine weitere Linie mit folgendem Syntax hinzu: <static-ip> hostname.domainname.org  hostname
Beispiel:
192.168.1.100 dein-hostname.domaene.org  dein-hostname
 
===== /etc/fstab, mkinitcpio.conf und modprobe.conf=====
Zu diesem Zeitpunkt ist es nicht nötig, die Dateien mkinitcpio.conf und modprobe.conf zu bearbeiten. mkinitcpio konfiguriert den ramdisk (z.B. booten von RAID, verschlüsselte Festplatten) und modprobe can dazu verwendet werden, einige spezielle Konfigurationsoptionen für die Module zu bestimmen.
 
''Falls Du den hal daemon benutzen willst, um das Mounten von Festplatten, optischen Laufwerken, USB-Laufwerken usw. zu automatisieren, solltest Du /etc/fstab bearbeiten und die Einträge für cdrom, floppy und dvd auskommentieren.''
 
=====/etc/resolv.conf (für statische IP)=====
Falls Du eine statische IP benutzt, setze Deine DNS Server in /etc/resolv.conf  (namenserver <ip-adresse>). Du kannst so viele haben, wie Du willst.
 
Falls Du einen Router benutzt, wirst Du wahrscheinlich Deine DNS Server im Router selbst festlegen und bloß von Deinem 'resolv.conf' dorthin verweisen, indem Du die IP Deines Routers benutzt (Deine Gateway in /etc/rc.conf). Beispiel:
nameserver 192.168.1.1
Alternativ kannst Du Deine Lieblingsserver untereinander hinzufügen, z.B.:
nameserver 4.2.2.1
nameserver 4.2.2.2
 
=====/etc/locale.gen=====
 
Das Kommando '''locale-gen''' liest aus /etc/locale.gen und generiert spezielle Lokalisierungen. Diese können dann von glibc und jedem anderem lokaliesiertem Program oder Library zum Texterstellen benutzt werden. /etc/locale.gen ist standardmäßig eine leere Datei mit kommentierter Dokumentation. Wenn diese Datei einmal bearbeitet wurde, wird sie nie mehr berührt werden. Locale-gen wird bei jedem Update von glibc ausgeführt, wodurch alle Lokalisierungen aus /etc/locale.gen hergestellt werden.
 
Wähle alle Loalisierung(en), welche Du nutzen willst (lösche das # am Anfang der Zeile), z.B.:
en_US ISO-8859-1
en_US.UTF-8
('''Deine Lokalisierungen müssen mit denen in /etc/rc.conf von oben übereinstimmen.''')
 
Die Installation wird nun das '''locale-gen''' Skript ausführen, welches die gewünschten Lokalisierungen erstellt. Du kannst in Zukunft die Lokalisierung ändern, indem Du /etc/locale.gen bearbeitest und danach '''locale-gen''' als root ausführst.
 
''Beachte: falls Du Deine Lokalisierung nicht wählst, wird das zum "The current locale is invalid..." Fehler führen. Dies ist wahrscheinlich der häufigste Fehler unter neuen Arch Nutzern, und er führt auch zur am meisten gestellten Frage im Forum.''
 
=====Root Password=====
Setzte zum Schluß ein root-Passwort und vergewissere Dich, dass Du es später noch weißt. Kehre zum Hauptmenü zurück und fahre mit der Installation des Startmanagers (Bootloader) fort.
 
===Installation des Bootloaders===
Da wir in unserem Beispiel kein zweites Betreibssystem haben, werden wir einen Bootloader benötigen. [http://www.gnu.org/software/grub/ GNU GRUB] ist der empfolene Bootloader. Alternativ kannst Du [http://lilo.go.dyndns.org/ LILO] wählen. Die gezeigte GRUB Konfiguration (/boot/grub/menu.lst) sollte ausreichend sein. Das einzige, was Du ändern könntest, ist die Aufklösung der Konsole. Füge zur ersten Kernel-Linie eine vga=<number> hinzu. (A Tabelle mit Auflösungen und entsprechenden Nummern ist im menu.lst abgedruckt.)
title  Arch Linux (Main)
root  (hd0,0)
kernel /boot/vmlinuz26 root=/dev/sda1 ro vga=773
initrd /boot/kernel26.img
Das Argument "vga=773" wird einen 1024x768 framebuffer mit 256 Farbtiefe ergeben.
 
Verlasse die Installation und gebe reboot ein.
 
Wenn alles gut geht, wird Dein neues Arch Linux System nun starten und mit einer Login-Eingabe enden (Du solltest in Deinem BIOS die Startreihenfolge zurückstellen auf das Starten von Festplatte).
 
Herzlichen Glückwunsch und willkommen zu Deinem schönen neuen Arch Linux Basissystem!
 
==Konfiguration des Basis-Systems ==
Dein neues Arch Linux Basissystem ist nun eine funktionelle GNU/Linux-Umgebung, die auf die Anpassung wartet. Von hier aus kannst Du diese Installation in all das verwandeln, was Du wünscht oder für Deine Vorhaben brauchst.
 
Fangen wir an.
-----
Login mit Deinem root Account. Wir werden nun pacman konfigurieren, das System updaten und dann einen gewöhnlichen Benutzer hinzufügen.
 
 
===Einstellen des Netzwerkes (falls nötig)===
''Dieser Abschnitt wird Dir dabei helfen, die meisten Arten von Netzwerken zu konfigurieren, falls die Installations-Skriptemit den auto-Konfigurationen für Dich nicht funktionieren.''
-----
Falls alles gut verlief, solltest Du ein funktionierendes Netzwerk haben. Versuche www.google.com zu pingen, um es zu bestätigen:
ping -c 3 www.google.com
 
''Falls Du erfolgreich eine Netzwerkverbindung hergesstellt hast, fahre mit'' [http://wiki.archlinux.org/index.php/Beginners_Guide_%28Deutsch%29#Updaten.2C_Synchronisieren_und_Upgraden_des_Systems_mit_pacman ''Updaten, Synchronisieren und Upgraden des Systems mit pacman''] fort.
 
Falls nach dem Pingen ein "unknown host" Fehler auftrat, könntest Du schließen, dass Dein Netzwerk nicht konfiguriert ist. Du solltest zunächst die folgenden Dateien auf Integrität und saubere Einstellungen untersuchen:
 
'''/etc/rc.conf''' # Achte speziell in den HOSTNAME= und NETWORKING Abschnitten auf Tippfehler und Fehler.
 
'''/etc/hosts'''  # Checke nochmals das Format. (Siehe oben.)
 
'''/etc/resolv.conf''' # Falls Du eine statische IP benutzt. Falls Du DHCP benutzt, wird diese Datei dynamisch erstellt und standardmäßig zerstört. Aber sie kann für Deine Einstellungen geändert werden. (Siehe [[Network]].)
 
Fortgeschrittene Anweisungen, das Netzwerk einzustellen, kann im  [[Network]] Artikel gefunden werden.
 
====LAN über Kabel====
 
Überprüfe Dein Ethernet mit
ifconfig
Dort solltest Du einen Eintrag für eth0 sehen. Falls benötigt, kannst Du eine neue statische IP mit
ifconfig eth0 <ip address> netmask <netmask> up
und die Standard-Gateway mit
route add default gw <ip address of the gateway>
setzen.
Kontrolliere, ob /etc/resolv.conf Deinen DNS Server enthält und füge ihn hinzu, falls er fehlt.
Kontrolliere da Netzwerk nochmals mit ping www.google.de. Falls nun alles funktioniert, passe /etc/rc.conf wie in Abschnitt 2.6 besprochen an (statische IP). Falls Du einen DHCP Server/Router in Deinem  Netzwerk hast, versuche
dhcpcd eth0
Falls dies funktioniert, passe /etc/rc.conf an, wie es in Abschnitt 2.6 beschrieben wird (dynamische IP).
 
====Kabelloses LAN====
Detailiertes Setup-Wiki: [[Wireless Setup]]
 
====Analoges Modem====
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.
Tip: Read [[Dialup without a dialer HOWTO]].
 
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.
 
====ISDN====
 
Setting up ISDN is done in three steps:
# Install and configure hardware
# Install and configure the ISDN utilities
# Add settings for your ISP
 
The current Arch stock kernels include the necessary ISDN modules, meaning that you won't 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.
 
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:
 
modprobe hisax type=18 protocol=2
 
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.
 
Once you have confirmed that your card works with certain settings, you can add the module options to your /etc/modprobe.conf:
 
alias ippp0 hisax
options hisax type=18 protocol=2
 
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.
 
That being done, you should have working, supported hardware. Now you need the basic utilities to actually use it!
 
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.
 
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.
 
If you set up everything correctly, you should now be able to establish a dial-up connection with
isdnctrl dial ippp0
as root. If you have any problems, remember to check the logfiles!
 
====DSL (PPPoE)====
 
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.
 
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
 
/etc/rc.d/adsl start
 
and
 
/etc/rc.d/adsl stop
 
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.
 
==Updaten, Synchronisieren und Upgraden des Systems mit [[pacman]]==
Now we will update the system using [[pacman]].
 
=====What is pacman ?=====
[[Pacman]] is the '''pac'''kage '''man'''ager of Arch Linux. Pacman is written in C and is fast, simple, and extremely powerful. 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. We will use pacman to download software packages from remote repositories and install them onto your system.
 
Pacman is the most important tool in your Arch Linux toolbox for building the core system into whatsoever you please.
 
===Configuring pacman===
=====/etc/pacman.conf=====
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 repository that pacman can use when searching for packages. The exception  to  this  is the options section, which defines global options.
nano -w /etc/pacman.conf
Example:
[core]
# Add your preferred servers here, they will be used first
#Server = http://mirrors.easynews.com/linux/archlinux/current/os/i686
Include = /etc/pacman.d/core
[extra]
# Add your preferred servers here, they will be used first
#Server = http://mirrors.easynews.com/linux/archlinux/extra/os/i686
Include = /etc/pacman.d/extra
#[unstable]
# Add your preferred servers here, they will be used first
#Server = http://mirrors.easynews.com/linux/archlinux/unstable/os/i686
#Include = /etc/pacman.d/unstable
[community]
# Add your preferred servers here, they will be used first
#Server = http://mirrors.easynews.com/linux/archlinux/community/os/i686
Include = /etc/pacman.d/community
Ensure the [community] repo is enabled (remove the # in front of the "Include = /etc/pacman.d/community" and "[community]" lines). Arch's community repository offers many useful applications.
 
The "Server =" lines, if uncommented, will force the specified server to be searched first and foremost. Further configuration for repos are under /etc/pacman.d/
 
====/etc/pacman.d/====
Faster mirrors will dramatically improve pacman performance, and your overall Arch Linux experience.
 
Use the '''rankmirrors''' script supplied with the latest pacman package, which will rank the mirrors automatically by their speed. For example, to rank the mirrors in the ''core'' repository, you would have to run as root:
rankmirrors /etc/pacman.d/core
Repeat as necessary for all desired repositories.
 
Alternatively, you may choose to manually Edit the files in /etc/pacman.d/ (community, core, extra) and move the mirrors which are located nearest to you to the top of the list. (if you use nano, Alt+A starts selecting an area, cursor down marks the lines, Ctrl+K cuts the selected area and Ctrl+U uncuts it). Repeat this for all files in /etc/pacman.d/. You may want to return to these configuration files to experiment with various mirrors. Choose wisely.
 
==Update System==
Update, sync, and '''upgrade''' your entire new system with:
pacman -Syu
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.)
 
=====''Take note as to whether a major kernel upgrade is occurring.''=====
 
''If the kernel undergoes a major upgrade, modules such as''' nvidia''' and '''madwifi''', for instance, (to be installed later in the guide, if necessary) will be inoperable, since the new, upgraded package versions of such modules will have been built against the newer kernel, and your system is currently using an older one. A reboot will be necessary.''
 
=====The beauty of the rolling release=====
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.
 
=====Get familiar with pacman=====
Pacman is the Arch user's best friend. It is highly recommended to study and learn how to use the pacman tool. Try:
man pacman
Check out the bottom of this article, and look up the [[pacman]] wiki entries at your leisure.
 
 
 
===Add a user and setup groups===
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:
adduser
While most default options are safe to use, you may want to add storage, audio, video, optical, and wheel to your additional groups- especially if you are planning on having a full-featured desktop environment.
 
Groups and users thereof are defined in /etc/group.
 
They include:
 
*audio - for tasks involving sound card and related software
 
*wheel - for using sudo
 
*storage - for managing storage devices
 
*video - for  video tasks and 3d acceleration
 
*optical - for managing tasks pertaining to the optical drive(s)
 
*floppy - for access to a floppy if necessary
 
*lp - for managing printing tasks
 
See the [[Groups]] article to understand what groups you need to be a member of.
You may also add your user to the desired groups like so, (as root):
usermod -aG audio,video,floppy,lp,optical,network,storage,wheel USERNAME
Check the man pages for usermod and gpasswd for more information.
 
==Part II: Install X and configure ALSA==
===Installing and configuring X===
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 Unix-like operating systems.
 
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.
-----
*''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:''
pacman -S libgl
''(Proprietary video drivers provide their own gl library implementations.)''
----- 
Now we will install the base Xorg packages using pacman.  This is the first step in building a GUI.
 
pacman -S xorg
 
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.
 
If you need a list of all '''open-source''' video drivers, do:
pacman -Ss xf86-video | less
If you don't know what graphics card you are using, do:
lspci | grep VGA
Here is a list of '''open source''' drivers, and corresponding video chipsets.
*'''xf86-video-apm'''                  Alliance ProMotion video driver
*'''xf86-video-ark'''                    ark video driver
*'''xf86-video-ati'''                      ati video driver
*'''xf86-video-chips'''                  Chips and Technologies video driver
*'''xf86-video-cirrus'''                Cirrus Logic video driver
*'''xf86-video-dummy'''              dummy video driver
*'''xf86-video-fbdev'''                  framebuffer video driver
*'''xf86-video-glint'''                    GLINT/Permedia video driver
*'''xf86-video-i128'''                    Number 0 i128 video driver
*'''xf86-video-i740'''                    Intel i740 video driver
*'''xf86-video-i810'''                    Intel i810/i830/i9xx video drivers
*'''xf86-video-imstt'''                    Integrated Micro Solutions Twin Turbo vidoe driver
*'''xf86-video-mga'''                      mga video driver  (Matrox Graphics Adapter)
*'''xf86-video-neomagic'''            neomagic video driver
*'''xf86-video-nv'''                        nvidia nv video driver
*'''xf86-video-rendition'''            Rendition video driver
*'''xf86-video-s3'''                        S3 video driver
*'''xf86-video-s3virge'''                S3 Virge video driver
*'''xf86-video-savage'''                savage video driver
*'''xf86-video-siliconmotion'''      siliconmotion video driver
*'''xf86-video-sis'''                        SiS video driver
*'''xf86-video-sisusb'''                  SiS USB video driver
*'''xf86-video-tdfx'''                      tdfx video driver
*'''xf86-video-trident'''                Trident video driver
*'''xf86-video-tseng'''                  tseng video driver
*'''xf86-video-unichrome'''          Unichrome video drivers
*'''xf86-video-v4l'''                        v4l video driver
*'''xf86-video-vesa'''                    vesa video driver
*'''xf86-video-vga'''                      VGA 16 color video driver
*'''xf86-video-via'''                        via video driver
*'''xf86-video-vmware    '''              vmware video driver
*'''xf86-video-voodoo    '''              voodoo video driver
 
* 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.
 
*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 below''' under [http://wiki.archlinux.org/index.php/Beginners_Guide#Using_proprietary_Graphics_Driver_.28nVIDIA.2C_ATI.29 Using proprietary Graphics Driver (nVIDIA, ATI])
 
Use pacman to install the appropriate video driver for your video card/onboard video. e.g.:
pacman -S xf86-video-i810
(for the intel 810 chipset driver.)
 
* If you still don't know which video driver to install, you may install the whole video driver group package, and allow the Xorg -configure script to specify the driver in xorg.xonf:
pacman -S xorg-video-drivers
 
==Create /etc/X11/xorg.conf==
=====What is /etc/X11/xorg.conf?=====
/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, 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, say a video projector and an on board LCD of a notebook.
------
By default, you will not have an Xorg config file, and with the newest versions of Xorg, you don't need one ''if'' the autodetection ''works satisfactorily'' and you don't need to turn on features such as aiglx and so on.
 
''Most people will still find that they need to generate a config file, however.''
 
 
*Use the Xorg -configure script to make a basic config file:
Xorg -configure
Move the generated config file to /etc/X11:
mv /root/xorg.conf.new /etc/X11/xorg.conf
 
Inspect your config file:
 
nano /etc/X11/xorg.conf
 
Ensure the Xorg -configure script has correctly specified your video driver. e.g.:
Section "Device"
Driver  "i810"
 
Ensure there are horizontal sync and vertical refresh specs under section "Monitor". If not, add them:
Section "Monitor"
        Identifier  "Monitor0"
        VendorName  "Monitor Vendor"
        ModelName    "Monitor Model"
        HorizSync    30.0 - 130.0 # Safe for LCD's
        VertRefresh  50.0 - 100.0 # Safe for LCD's and most CRT's.
EndSection
(If you do not know these specs, consult your monitor's documentation.)
 
Specify your default color depth under section "Screen":
Section "Screen"
        Identifier "Screen0"
        Device    "Card0"
        Monitor    "Monitor0"
        DefaultDepth 24
(Typically, this will be set to 24 for true color.)
 
Also add your desired Modes to your "Display" subsection, at least under the Depth 24 header, e.g.:
  SubSection "Display"
                Viewport  0 0
                Depth    24
                Modes "1024x768" "800x600" "640x480"
Continue with [http://wiki.archlinux.org/index.php/Beginners_Guide#Simple_baseline_X_test Simple baseline X test], or refer to following sections for proprietary driver guidelines.
 
===Using proprietary Graphics Driver (nVIDIA, ATI)===
You may choose to use the proprietary video drivers from nVIDIA or ATI. 
====nVIDIA Graphic Cards====
The nVIDIA proprietary drivers are generally considered to be of excellent quality, and offer superior 3D performance.
 
Before you configure your Graphics Card you will need to know which driver fits. Arch currently has 3 different drivers that each match a certain subset of Cards:
 
'''1. nvidia-71xx''' ''for very old Cards like TNT and TNT2''
 
'''2. nvidia-96xx''' ''slightly newer cards up to the GF 4''
 
'''3. nvidia'''      ''newest GPUs after the GF 4''
 
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.
 
Install the appropriate nvidia driver, e.g.:
pacman -S nvidia
 
The nVIDIA package has a utility for updating your existing /etc/X11/xorg.conf for use with the nVIDIA driver:
nvidia-xconfig
 
It also has several options which will further specify the contents and options of the xorg.conf file.
For example,
nvidia-xconfig --composite --add-argb-glx-visuals
 
For more detailed information, see nvidia-xconfig(1).
 
Some useful tweaking options in the device section are (beware that these may not work on your system):
        Option          "RenderAccel" "true"
        Option          "NoLogo" "true"
        Option          "AGPFastWrite" "true"
        Option          "EnablePageFlip" "true"
Make sure all instances of DRI are commented out:
#    Load        "dri"
Double check your /etc/X11/xorg.conf to make sure your default depth, horizontal refresh, vertical refresh, and resolutions are acceptable.
 
Logout and login.
 
Start X server as normal user, to test your configuration:
startx
 
Advanced instructions for nvidia configuration can be found in the [[NVIDIA]] article.
 
====ATI Graphic Cards====
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.
 
Install the '''proprietary''' ATI Driver with
pacman -S catalyst
Use the aticonfig tool to modify the xorg.conf. Note: The proprietary driver does not support [[AIGLX]]. To use [[Compiz]] or [[Beryl]] with this driver you would need to use [[XGL]].
 
Install the '''open-source''' ATI Driver with
pacman -S xf86-video-ati
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.
 
Advanced instructions for ATI configuration can be found in the [[ATI | ATI wiki]].
 
===Simple baseline X test===
 
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, before installing a complete desktop environment, 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. Xterm will allow us to effectively test if your video driver and /etc/X11/xorg.conf are properly configured. (Alternatively, you may wish to test if the X autodetection works satisfactorily, in the absence of /etc/X11/xorg.conf.)
pacman -S xterm
===== ~/.xinitrc =====
Edit your /home/username/.xinitrc file, '''as normal user''', to dictate which X Server event is invoked with the 'startx' command:
 
su yourusername
 
nano ~/.xinitrc
 
and add (or uncomment)
exec xterm
 
So that it looks like this:
 
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#
exec xterm
# exec wmaker
# exec startkde
# exec icewm
# exec blackbox
# exec fluxbox
 
''Be sure to have only one uncommented '''exec''' line in your ~/.xinitrc''
 
If you do not have ~/.xinitrc, simply create one with the above information, or copy the sample file from /etc/skel/ to your home directory:
cp /etc/skel/.xinitrc ~/
*NOTE: ''In the absence of file ~/.xinitrc, /etc/X11/xinit/xinitrc will be used as a fallback, which defaults to using TWM and Xterm.''
 
Start X Server as normal user, with:
startx
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.
 
Advanced instructions for Xorg configuration can be found in the [[Xorg]] article.
 
===Configure the audio card with alsamixer===
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. 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.)
-----
Your audio card should already be working, but you can't hear anything because it is muted by default.
 
Install the alsa-utils package:
  pacman -S alsa-utils
Did you add your normal user to the audio group? If not, now would be a good time. As root do:
gpasswd -a yourusername audio
As normal user, do:
alsamixer
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.) Leave alsamixer by pressing ESC.
 
Then run alsactl as root. This will create '/etc/asound.state', saving the alsamixer settings.
alsactl store
 
Also, add the alsa ''daemon'' to your DAEMONS section in /etc/rc.conf to automatically restore the mixer settings on boot-up.
nano /etc/rc.conf
DAEMONS=(syslog-ng network crond '''alsa''')
''Note that the alsa daemon merely restores your volume mixer levels on bootup. It is separate from the alsa audio library (and kernel level API).''
 
Expanded information available in the [[ALSA]] wiki entry.
 
==Part III: Installing and configuring a Desktop Environment ==
If you ask two people what the best Desktop Environment or Window Manager is, you will get six different answers. Choose the best environment for ''your'' needs.
* If you want something  full-featured and similar to Windows and Mac OSX, '''KDE''' is a good choice
* If you want something more minimalist, which follows the K.I.S.S. principle more closely, '''GNOME''' is a good choice
* If you have an older machine or want something lighter, '''xfce4''' is a good choice, still giving you a complete environment
* If you need something even lighter, '''openbox, fluxbox or fvwm2''' may be right (not to mention all other lightweight window managers like '''windowmaker and twm''').
* If you need something completely different, try '''ion, wmii, or dwm'''.
 
===Install Fonts===
At this point, you may want to install some good-looking fonts, '''before''' installing a desktop environment/window manager. Dejavu and bitstream-vera are nice font sets. For websites, you may want to have the Microsoft fonts too. Install with:
pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera
 
===GNOME===
====About GNOME====
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.
 
====Installation====
Install the complete GNOME environment  with:
pacman -S gnome gnome-extra
It's safe to choose all packages shown.
Alternatively, you may wish to install a more basic, stripped-down GNOME:
pacman -S gnome
 
=====Useful DAEMONS for GNOME=====
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.
 
You may want to install a graphical login manager. For GNOME, the '''gdm''' daemon is a good choice. Install gdm with
pacman -S gdm
You will almost certainly want the '''hal''' and '''fam''' daemons.
 
Start hal and fam:
/etc/rc.d/hal start
 
/etc/rc.d/fam start
 
Add them to your /etc/rc.conf DAEMONS section, so they will be invoked on bootup:
nano /etc/rc.conf
 
DAEMONS=(syslog-ng network crond alsa '''hal fam gdm''')
(If you prefer to log into the console and manually start X in the 'Slackware tradition', leave out gdm.)
 
====~/.xinitrc====
 
This configuration file controls what occurs when you type 'startx'.
 
Edit your /home/username/.xinitrc to utilize GNOME:
 
nano ~/.xinitrc
 
Uncomment the 'exec gnome-session' line so that it looks like this:
 
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#
#exec xterm
#exec wmaker
# exec startkde
exec gnome-session
# exec icewm
# exec blackbox
# exec fluxbox
 
If you do not have ~/.xinitrc, simply create one with the above information, or copy the sample file from /etc/skel/ to your home directory:
cp /etc/skel/.xinitrc ~/
Remember to have only one uncommented '''exec''' line in your ~/.xinitrc.
 
Switch to normal user:
su username
 
And test it with:
startx
 
You may want to install a terminal and an editor. I would recommend gnome-terminal (part of the group gnome-extra) and geany:
pacman -S geany gnome-terminal
 
Advanced instructions for installing and configuring GNOME can be found in the [[Gnome]] article.
 
====Eye Candy====
You may find the default GNOME theme and icons not very attractive. A nice gtk theme is murrine. Install it with
pacman -S gtk-engine-murrine
and select it with System->Preferences->Theme. You can find more themes, icons, and wallpaper at [http://www.gnome-look.org Gnome Look].
 
===KDE===
====About KDE====
The '''K''' '''D'''esktop '''E'''nvironment. KDE is a powerful Free Software graphical desktop environment for GNU/Linux and UNIX workstations. It combines ease of use, contemporary functionality, and outstanding graphical design with the technological superiority of UNIX-like operating systems.
 
====Installation====
Arch offers several versions of kde: '''kde, kdebase, and KDEmod'''. Choose '''one''' of the following, and continue below with '''"Useful KDE DAEMONS"''':
 
'''1.)''' Package '''kde''' is the complete, vanilla KDE, ~300MB.
pacman -S kde
'''2.)''' Package '''kdebase''' is a slimmed-down version with less applications, ~80MB.
pacman -S kdebase
'''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.
 
====Useful KDE DAEMONS====
 
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.
 
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.
-----
Start hal and fam:
 
/etc/rc.d/hal start
 
/etc/rc.d/fam start
*'''NOTE:''' ''The hal daemon will automatically start the dbus daemon.''
Edit your DAEMONS section in /etc/rc.conf:
nano /etc/rc.conf
Add '''hal''' and '''fam''' to your DAEMONS section, to invoke them on bootup. If you prefer a graphical login, add '''kdm''' as well:
DAEMONS=(syslog-ng network crond alsa '''hal fam kdm''')
*This method will start the system at runlevel 3, (/etc/inittab default, multiuser mode), and then start KDM as a daemon.
 
*Some users prefer an alternative method of starting a display manager like KDM on bootup utilizing the /etc/inittab runlevel5. See [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]] for more.
 
*If you prefer to log into the '''console''' at runlevel 3, and manually start X in the 'Slackware tradition', leave out kdm, or comment it out with an exclamation. ( ! )
=====~/.xinitrc=====
This configuration file controls what occurs when you type 'startx'.
 
Edit your /home/username/.xinitrc to utilize KDE:
nano ~/.xinitrc
Uncomment the 'exec startkde' line so that it looks like this:
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#
#exec xterm
#exec wmaker
exec startkde
# exec gnome-session
# exec icewm
# exec blackbox
# exec fluxbox
If you do not have ~/.xinitrc, simply create one with the above information, or copy the sample file from /etc/skel/ to your home directory:
cp /etc/skel/.xinitrc ~/
''Remember to have only one uncommented '''exec''' line in your ~/.xinitrc.''
 
Switch to your normal user:
su username
Now try starting your X Server:
startx
Advanced instructions for installing and configuring KDE can be found in the [[KDE]] article.
 
Congratulations! Welcome to your KDE desktop environment on your new Arch Linux system! You may wish to continue by viewing [http://wiki.archlinux.org/index.php/Beginners_Guide#Tweaks.2FFinishing_touches Tweaks and finishing touches], or the rest of the information below. You may also be interested in the [[Post Installation Tips]] wiki article.
 
===Xfce===
====About Xfce====
Xfce is a Desktop Environment, like GNOME or KDE. It contains a suite of apps like a root window app, window manager, file manager, panel, etc. Xfce is written using the GTK2 toolkit 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.
 
====Installation====
Install xfce with
pacman -S xfce4 xfce4-goodies
 
If you use kdm or gdm a new xfce session should have appeared. Alternatively, you can use
startxfce4
Advanced instructions for installing and configuring Xfce can be found in the [[Xfce]] article.
 
===*box===
====Fluxbox====
Fluxbox © is yet another windowmanager for X.
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).
 
Install Fluxbox using
pacman -S fluxbox fluxconf
 
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:
exec startfluxbox
 
More information is available in the [[Fluxbox]] article.
 
====Openbox====
Openbox is a standards compliant, fast, light-weight, extensible window manager.
 
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.
 
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.
 
Install openbox using
pacman -S openbox obconf obmenu
 
Once openbox is installed you will get a message to move menu.xml & rc.xml to ~/.config/openbox/ in your home directory:
 
mkdir -p ~/.config/openbox/
cp /etc/xdg/openbox/rc.xml ~/.config/openbox/
cp /etc/xdg/openbox/menu.xml ~/.config/openbox/
 
In the file "rc.xml" you can change various settings for Openbox (or you can use OBconf). In "menu.xml" you can change your right-click menu.
 
To be able to log into openbox you can either go via graphical login using KDM/GDM or startx, in which case you will need to edit your ~/.xinitrc (as user) and add the following:
 
exec openbox
 
For KDM there is nothing left to do; openbox is listed in the sessions menu in KDM.
 
Useful programs for openbox are:
* PyPanel or LXpanel if you want a panel
* feh if you want to set the background
* ROX if you want a simple file manager and desktop icons
 
More information is available in the [[Openbox]] article.
 
===fvwm2===
FVWM is an extremely powerful ICCCM-compliant multiple virtual desktop window manager for the X Window system. Development is active, and support is excellent.
 
Install fvwm2 with
pacman -S fvwm
 
fvwm will automatically be listed in kdm/gdm in the sessions menu. Otherwise, add
exec fvwm
 
to your user's .xinitrc.
 
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.
 
==Tweaks/Finishing touches==
===HAL===
Since you have now installed a desktop environment, 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.
 
KDE, GNOME and XFCE uses HAL.
 
The installation procedure is described in the [[HAL]] article. Some information can also be found at  [http://en.wikipedia.org/wiki/HAL_(software) Wikipedia].
 
===Adjusting Mouse for scroll wheel===
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):
        Option      "ZAxisMapping" "4 5 6 7"
 
===evdev===
If you have a modern USB mouse with several thumb buttons and/or functions, you may want to install the evdev mouse driver, which will allow you to exploit the full functionality of your mouse:
 
pacman -S xf86-input-evdev
Load the driver:
modprobe evdev
Find your mouse name by entering the following, exactly:
cat /proc/bus/input/devices | egrep "Name"
Using the mouse name, configure your /etc/X11/xorg.conf InputDevice section accordingly, e.g.:
Section "InputDevice"
  Identifier      "Evdev Mouse"
  Driver          "evdev"
  Option          "Name" "Logitech USB-PS/2 Optical Mouse"
  Option          "CorePointer"
EndSection
You must have only '''one''' "CorePointer" device specified in /etc/X11/xorg.conf, so be sure to comment out any other mouse entries until you feel safe removing the old, unused entries.
 
Also edit the ServerLayout section to include Evdev Mouse as the CorePointer, e.g.:
Section "ServerLayout"
    Identifier    "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Evdev Mouse" "CorePointer"
 
===Adjusting Keyboard Layout===
You may want to change your keyboard layout. To do this edit your /etc/X11/xorg.conf and add these lines in the Input Section (keyboard0) (the example shows a German keyboard layout with no dead keys; alter this to fit your needs).
        Option          "XkbLayout"    "de"
        Option          "XkbVariant"    "nodeadkeys"
===Additional tweaks for laptops===
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 acpid
pacman -S acpid
and add it to the daemons in /etc/rc.conf (acpid). Start it with
/etc/rc.d/acpid start
 
More-specific information about Arch Linux on various Laptops can be found at [[:Category:Laptops (English)]]
===Configuring CPU frequency scaling===
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
pacman -S cpufrequtils
and add cpufreq to your daemons in /etc/rc.conf. Edit the config file /etc/conf.d/cpufreq and change
governor="conservative"
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 don't 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
modprobe <modulname>
and start cpufreq with
/etc/rc.d/cpufreq start
For more details, see [[Cpufrequtils]]
 
==Useful Applications==
This section will never be complete. It just shows some good applications for the everyday user. 
 
'''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.
===Internet===
 
=====Firefox=====
The ever-popular Firefox web browser is available through pacman. Install with:
 
pacman -S firefox
Be sure and install 'flashplugin', 'mplayer', 'mplayer-plugin', and the 'codecs' packages for a complete web experience:
pacman -S flashplugin mplayer mplayer-plugin codecs
(The codecs package contains codecs for Quicktime and Realplayer content.)
 
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.
 
===Office===
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.
 
==Multimedia ==
 
 
===Video Player===
====VLC====
VLC Player is a multimedia player for Linux.  To install it, simply type the code below.
 
pacman -S vlc
 
(TODO) Instructions for VLC mozilla plug-in
 
====Mplayer====
MPlayer is a multimedia player for Linux.  To install it, simply type the code below.
 
pacman -S mplayer
 
It also has a Mozilla plug-in for videos and streams embedded in web pages.  To install it, simply type the code below.
 
pacman -S mplayer-plugin
 
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.
 
pacman -S kmplayer
 
(TODO) GMPlayer instructions
 
====GNOME====
=====Totem=====
[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.
It comes with added functionality such as:
 
* Video thumbnailer for the file manager
* Nautilus properties tab
* Epiphany / Mozilla (Firefox) plugin to view movies inside your browser
* Webcam utility (in development)
 
Totem-xine is still the better choice if you want to watch DVDs.
 
Totem is part of the gnome-extra group; the Totem webbrowser plugin isn't.
 
To install separately:
pacman -S totem
 
To install the Totem webbrowser plugin:
pacman -S totem-plugin
 
====KDE====
=====Kaffeine=====
Kaffeine is a good option for KDE users.  To install it, simply type the code below.
 
pacman -S kaffeine
 
===Audio Player===
====Gnome/Xfce====
=====Exaile=====
[[Exaile]] is a music player written in Python that makes use of the GTK+ toolkit.
=====Rhythmbox=====
[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.
 
Rhythmbox has a number of features, including:
 
* Easy-to-use music browser
* Searching and sorting
* Comprehensive audio format support through GStreamer
* Internet radio support
* Playlists
 
To install rhythmbox:
pacman -S rhythmbox
 
Other good audio players are: Banshee, Quodlibet, and Listen. See [http://gnomefiles.org/ Gnomefiles] to compare them.
 
====KDE====
=====Amarok=====
[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.
 
pacman -S amarok-base
 
====Console====
[http://moc.daper.net/ Moc] is a ncurses-based audio player for the console; another good choice is [http://musicpd.org/ mpd].
 
Another excellent choice is [http://freshmeat.net/projects/cmus/ cmus].
 
====Other X-based====
(TODO) Xmms, audacious, bmpx.
 
===Codecs and other multimedia content types===
====DVD====
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.
 
====Flash====
Install the flash plugin using
pacman -S flashplugin
to enable Macromedia (now Adobe) Flash in your browser.
 
====Quicktime====
Quicktime codecs are contained in the codecs package. Just type
pacman -S codecs
to install them.
====Realplayer====
The codec for Realplayer 9 is contained in the codecs package. Just type
pacman -S codecs
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].
 
===CD and DVD Burning===
====GNOME====
=====Brasero=====
[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.
 
To install:
pacman -S brasero
 
====KDE====
=====K3b=====
K3b (from '''K'''DE '''B'''urn '''B'''aby '''B'''urn) is a free software CD and DVD authoring application for GNU/Linux and other Unix-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.
 
K3b was voted LinuxQuestions.org's Multimedia Utility of the Year (2006) by the majority (70%) of voters.
-----
To install:
pacman -S k3b
 
 
 
 
=====(Todo) cdrecord, graveman...=====
 
 
 
 
Most CD burners are wrappers for cdrecord:
 
pacman -S cdrkit
 
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.
 
A good command-line DVD-burning tool is growisofs:
 
pacman -S dvd+rw-tools
 
===TV-Cards===
 
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 bunch is 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.
 
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
modprobe bttv
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.
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:
modprobe bttv card=42 radio=0
Some cards need the following line to produce sound:
modprobe tvaudio
However, that varies. So just try it out. Some other cards demand the following line:
modprobe tuner
This is object to trial-and-error, too.
 
TODO: clarify the installation-procedure
 
To actually watch TV, install the xawtv-package with
pacman -S xawtv
and read its manpage.
 
TODO: clarify some possible problems and procedures. Introduction to XAWTV on another page?
 
===Digital Cameras===
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.
 
===USB Memory Sticks / Hard Disks===
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.
 
==Maintaining the system==
===Pacman===
[[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.
 
A more-detailed description of Pacman can be found in [[Pacman|its article]].
 
==== Useful commands ====
 
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):
pacman -Sy
 
To '''upgrade''' all packages on the system:
pacman -Su
 
To sync, update, and '''upgrade''' all the packages on the system with one command:
pacman -Syu
 
To install or upgrade a single package or list of packages (including dependencies):
pacman -S packageA packageB
 
You can also sync, update the package database, and install packages in one command:
pacman -Sy packageA packageB
 
To remove a single package, leaving all of its dependencies installed:
pacman -R package
 
To remove a package and all of the package's dependencies which aren't used by any other installed package:
pacman -Rs package
 
To remove all of the package's dependencies now unneeded and do not make any backup of settings:
pacman -Rsn package
 
To search the remote (repo) package database for a list of packages matching a given keyword:
pacman -Ss keyword
 
To list all packages on your system
pacman -Q
 
To search (query) the local (your machine) package database for a given package:
pacman -Q package
 
To search (query) the local (your machine) package database for a given package and list all pertinent information:
pacman -Qi package
 
To defragment pacman's cache database and optimize for speed:
pacman-optimize
 
To count how many packages are currently on your system:
pacman -Q | wc -l
 
To install a package compiled from source using ABS and makepkg:
pacman -U packagename.pkg.tar.gz
 
Note: There are countless additional pacman functions and commands. Try man pacman and consult the [[pacman]] wiki entries.
 
==Polishing & Further information==
For further information and support you can go to the [http://www.archlinux.org homepage], search the wiki, the [http://bbs.archlinux.org forums], the [http://wiki.archlinux.org/index.php/ArchChannel IRC channel], and the [http://www.archlinux.org/mailman/listinfo/ mailing lists].
 
Where to go from here? You may also be interested in:
 
[[Post Installation Tips]]
 
[[Get All Mouse Buttons Working]]
 
[[Improve Pacman Performance]]
 
[[Kernel Compilation]]
 
[[Pm-utils]]
 
[[Cpufrequtils]]
 
[http://wiki.archlinux.org/index.php/Category:Eye_candy_%28English%29 Eye Candy]

Version vom 11. Dezember 2007, 03:31 Uhr


Vorlage:Stub

Vorlage:Translateme

Vorlage:I18n links start Vorlage:I18n entry Vorlage:I18n entry Vorlage:I18n entry Vorlage:I18n entry Vorlage:I18n entry Vorlage:I18n entry Vorlage:I18n links end

Vorwort

Alles, was Du jemals über die Installation von Arch Linux wissen wolltest, aber niemals zu fragen wagtest

Dieses Dokument wird Dich durch den Prozess der Installation und Konfiguration von Arch Linux führen. Es ist an neue Arch Benutzer gerichtet, stellt aber auch eine gute Referenzquelle für alle dar. Obwohl diese Orientierungshife zeigen will, wie man ein voll konfiguriertes Arch Linux System erhält (mit Graphischer Oberfläche, DVD-Spieler, Internet-Browsen, Arbeiten mit E-Mails, Hören von Musik), können hier niemals alle Möglichkeiten aufgezeigt werden. Dieses Dokument konzentriert sich darauf, die wichtigsten und nützlichsten Schritte zu zeigen; mehr Informationen findest Du im englischen Arch Linux Wiki-en oder im Arch Linux' Forum, aber auch auf der deutschen Seite. Vielleicht bist Du auch am Arch-Weg interessiert, welcher die Prinzipien der Arch Linux Distribution erklärt.

Dieser Artikel ist in 3 Hauptteile getrennt:


DON'T PANIC!

Bitte sei Dir darüber im Klaren, dass die Installation von Arch Linux sehr unterschiedlich sein kann verglichen mit anderen Distributionen, die Du versucht hast, vor allem als Anfänger. Das Arch Linux System wird vom Benutzer geformt. Die Installation liefert ein Grundsystem mit lediglich einer 'bash-Konsole' (Kommandozeilen-Eingabe) und grundlegenden Systemprogrammen. Von der Kommandozeile wirst Du Pakete (Programme) mit Hilfe des pacman-Programmes von den Arch Servern herunterladen und installieren, bis das System nach Deinen Bedürfnissen eingerichtet ist. Dies erlaubt maximale Flexibilität, Entscheidungsfreiheit und Systemresourcen- Kontrolle. Weil Du es einrichtest, wirst Du das A und O Deines Systemskennen lernen, sowie, was unter der Haube des Systems liegt. Denke auch daran, dass sich Arch Linux sowohl an kompetente GNU/Linux Benutzer wie auch an Benutzer richtet, die bereit sind, Zeit zu investieren, um die Mechanismen des Systems kennen zu lernen

Die Entwicklungs-Prinzipien hinter Arch liegen darin, die Dinge einfach zu halten.

Bedenke, dass 'einfach' in diesem Zusammenhang nicht 'benutzerfreundlich' bedeutet, sondern eher 'ohne unnötige Zusätze, Änderungen oder Komplikationen'. Kurz gesagt: ein eleganter, minimalistischer Ansatz.

Falls Du denkst, dass etwas Wichtiges fehlt oder nicht funktioniert, schick mir eine Mitteilung an <freigeist [at] elfenbeinturm.cc>. Oder füge die Verbesserung, oder was auch immer Du anfangs gebraucht hast, ein (was die Hauptidee eines Wikis ist :)). Es gibt auch einen englischen Arch Forum Eintrag, der Anfängern gewidmet ist.
Oder gehe zum deutschen Arch Forum.

  • Falls Du zu diesem Wiki beitragen möchtest, füge bitte das 'Weshalb' und das 'Wie' ein, wenn es passend ist. Die beste Dokumentation lehrt uns das Wie sowie das Warum!


Willkommen zu Arch! Lass uns beginnen.

Teil 1: Installation des Grundsystems

Die neuste Core Iso beziehen

Du kannst die neuste Momentaufnahme von www.archlinux.org/download/ herunterladen.

Es wird empfohlen, die core-iso zu wählen, da dieses Wiki auf den core Installationsprozess ausgerichtet ist.

Das core-iso Image beinhaltet nur die nötigen Programme, um ein minimales GNU/Linux Grundsystem zu installieren. Bemerke, dass ein minimales Grundsystem keine graphische Oberfläche enthält. Der Rest des Arch Linux Systemes - einschließlich graphischer Oberfläche - wird von der Kommandozeile aus mit Hilfe von Binärpaketen und Konfigurationsdateien eingerichtet. Dieser Prozess wird detailiert weiter unten besprochen.

Brenne die ISO auf CD. Generell ist es ratsam, mit einer Maximalgeschwindigkeit von 16x zu brennen, um verlässliche CDs zu erhalten.


Starte die Arch Linux CD

Während Du diesen Anweisungen folgst, könnte auch der offizielle Installationsguide hilfreich sein. Zusätzlich findest Du hier eine Druckversion.

Setzte die CD in das Laufwerk und starte von ihr. Es kann sein, dass Du die Startreihenfolge Deines Computers im BIOS ändern musst, oder eine Taste (normalerweise F11 oder F12) während der BIOS-Phase drücken musst.
Einige nützliche Startoptionen der Arch Linux CD:

  • ide-legacy falls Du Probleme mit IDE-Laufwerken hast.
  • noapic acpi=off pci=routeirq nosmp wenn sich Dein System beim Starten aufhängt.
  • memtest86+ Wenn Du Deinen Speicher auf Fehler testen willst.
  • lowmem ist für ältere Maschinen nützlich. Dies braucht nur 96MB System-RAM entgegen 256MB bei normaler Installation.

Wähle "Arch Linux Installation / Rescue System". Falls Du die Startoptionen ändern musst, drücke 'e', um die Startlinien zu bearbeiten.
Das System startet nun von CD und präsentiert einen Willkommenstext mit einingen Erklärungen, wenn es bereit ist.

Ändern der 'keymap'

Drücke am Willkommensbild die Enter-Taste. Falls Du eine 'nicht-US' Tastatur hast, gib in die Befehlszeile 

km

ein und wähle die richtige 'keymap'.

Zum Beispiel für deutsche Tastatur:

In der Konsole 'keymap': 

de.map.gz

In der Konsole 'font screen' wähle: 

default8x16.psfu.gz

Diesen Standard für die Konsolen-Schriftart ist eine sichere Wahl.

Installation starten

Gib in die Kommandozeile 

/arch/setup

ein, um die Installation zu starten.

Eine Installationsquelle wählen

Du wirst nach einer Installationsquelle gefragt. Wähle CD, falls Du eine 'core-ISO' benutzt, oder entschiede Dich für 'FTP', falls Du die 'FTP-ISO' benutzt.

Vorbereiten der Festplatte

Wähle den ersten Eintrag "Prepare Hard Drive" (Festplatte vorbereiten). Bitte sei Dir im Klaren, dass 'Auto-Prepare' (automatisches Vorbereiten) keine sichere Wahl ist, da es die gesamte Festplatte löschen wird. Wir werden hier die Festplatte manuell partitionieren. Wähle '2. Partition Hard Drives' (Festplatten partitionieren), wähle die Festplatte, auf der Du Arch installieren willst (/dev/sdx), und erstelle einige Partitionen.

An dieser Stelle wird der erfahrenere GNU/Linux-Benutzer zum Pakete Wählen springen wollen.

Partitionierungs-Info

Eine Partition ist eine Sektion der Festplatte, die als separate Festplatte erschienen wird und zu Deinem Arch Linux Dateisystem hinzugefügt werden kann. Partitionan werden in 'primär', 'erweitert' oder 'logisch' eingeteilt. Primäre Partitionen können startfähig sein und sind auf die Anzahl von 4 beschränkt. Wenn Du zum Beispiel einen PC mit einer einzelnen SATA-Festplatte benutzt, wird die erste 'primäre' Partition 'sda1' genannt. Die zweite 'primäre' Partition nennt sich 'sda2', dann kommt sda3 und sda4. Bei mehr als 4 Partitionen müssen wir eine erweiterte Partition benutzen, welche die logischen Partitionen enthält.

Erweiterte Partitionen sind von sich aus nicht benutzbar; sie sind eher ein "Kontainer" für logische Partitionen. Logische Partitionen müssen in innerhalb der erweiterten Partition liegen. Wenn eine Festplatte partitioniert wird, kann man folgendes Nummernschema sehen: sda1-3 für die ersten drei primären Partitionen. Darauf folgt die erweiterte Partition sda4. Und innerhalb der erweiterten Partition werden logische Partitionen (sda5, sda6 usw.) erstellt.

Root, Home und Swap

Jeder hat eine andere Meinung, wie man seine Festplatte am besten einteilen sollte. Du wirst mindestens eine primäre Partition brauchen, welche das Dateisystem 'root' ( / ) enthält.Des weiteren brauchst Du eine Partition für 'swap'. Weitere Kandidaten für eigene Partitionen sind /boot (beinhaltet hauptsächlich den Kernel) und /home (beinhaltet die Benutzerdaten). Es ist gute Praxis, / und /home auf unterschiedlichen Partitionen zu haben. Dies macht es mögich, Arch Linux (oder eine andere Distribution) neu zu installieren, während der Benutzer seine Daten, Musik, Bilder und Einstellungen behalten kann.

In diesem Wiki werden wir eine Partition für /, eine Partition für /home und eine swap Partition anlegen.

Swap-Partition

Eine Swap-Partition ist der Platz einer Festplatte, wo der "virtuelle Speicher" beheimatet ist. Falls Deine Prozesse mehr RAM brauchen als physikalisch vorhanden, kann Linux die Anfrage nicht bearbeiten und ein Fehler tritt auf. Eine swap Partition hilft in dieser Situation, indem physikalischer RAM durch virtuellen RAM erweitert wird. Linux benutzt diesen Platz der Festplatte (die Swap-Partition), um die Informationen, welche nicht mehr in den physikalischen RAM passen, zu speichern (in Wahrheit ist es ein wenig komplizierter, da Linux versucht, Informationen ins Swap zu schreiben, die nicht oft benötigt werden). Da eine Festplatte im Vergleich zu physikalischem RAM sehr langsam ist, ist dies nur ein Behelf.

Wenn Du zwei Leute über eine Swap-Partition fragst, wirst Du 4 verschiedene Antworten bekommen. Falls Du viel RAM (mehr als 1024 MB) hast, kannst Du meiner Meinung nach die Swap-Größe gut zwischen 512 MB und 1 GB halten. Deshalb werden wir in unserem Beispiel eine Swap-Partition mit 1 GB erstellen.

Die Partitionierung

Lass uns damit starten, die primäre Partition zu erstellen, welche das root-Dateisystem beherbergt. Wähle New -> Primary und gib die Größe, welche Du willst, ein (etwas zwischen 4 und 8 GB ist eine gute Wahl füe ein voll ausgestattetes Linux-System). Stelle diese Partition an den Anfang der Festplatte. Wähle die neu erstellte Partition an und und wähle "Bootable" aus, damit man von ihr starten kann.

Füge eine weiterePartition für Deine Benutzer - /home hinzu. Wähle eine weitere primäre Partition und gib ihr die Größe, welche Du willst. Da die Größe wirklich davon abhängt, was Deine Benutzer in ihren Home-Ordnern speichern, kann ich Dir keine Vorschläge machen. Die Größe kann zwischen ein paar hundert Megabyte für einige Büro-Dokumente und hunderten von Gigabytes für Videos und MP3s variieren. Falls Du den gesamten Platz auf Deiner Festplatte nutzen möchtest, wähle den verbleibenden Pllatz minus 512 MB - 1 GB.

Am Schluss bilden wir eine dritte Partition für Swap. Wähle eine Größe zwischen 512 MB und 1 GB und ändere den typ zu 82 (Linux swap / Solaris).

So sollte Dein Layout aussehen (die Größe kann ja nach Deinen Entscheidungen variieren): 

Name    Flags  Part Type   FS Type         [Label]         Size (MB)
-------------------------------------------------------------------------
sda1    Boot   Primary     Linux                           (4096 - 8192)
sda2           Primary     Linux                           (> 100)
sda3           Primary     Linux swap / Solaris            (512 - 1024)

Wähle 'Write' und tippe 'yes' ein. Beachte, dass diese Operation Daten auf Deiner Festplatte zerstören kann, falls Du Partitionen gelöscht hast! Wähle Quit, um den Partitionierer zu verlassen. Dann wähle Done um dieses Menü zu verlassen und mit dem Setzen der Mountpunkte fortzufahren.

Setzen der Mountpunkte der Filesysteme

Ein Paar kurze Worte über Dateisysteme und "Datei Systeme":

Technisch und der Genauigkeit halber, ist ein Dateisystem ein Daten Format für Informationsfuß, während ein "Datei System" (beachte den Leerschlag) eine Bezeichnung ist, die sich auf das Layout aller Dateien und Ordner in einem bestimmten System bezieht. Wenn Du deshalb gefragt wirst, ob Du ein Dateisystem bilden willst, wirst Du eigentlich gefragt, ob Du eine bestimmte Partition formatieren willst.
Aber wenn Du nach Mountpunkten gefragt wirst, gibst Du die Informationen, wo sich die bestimmten Partitionen in Deinem Arch Linux Datei System befinden.

Lass uns beginnen.

Dateisystem-Typen

Zuerst wirst Du nach Deiner Swap-Partition gefragt. Wähle die passende Partition (sda3 in unserem Beispiel). Du wirst gefragt, ob Du ein swap-Dateisystem bilden willst. Wähle 'yes'.
Als nächstes musst Du wählen, wo das / (root) Verzeichnis aktiviert wird (sda1 im Beispiel). Du wirst nun gefragt, welche Art von DAteisystem Du willst.

Frage wiederum zwei Personen, welches Dateisystem Du wählen sollst, und Du wirst fünf unterschiedliche Antworten erhalten. Jedes hat seine Vor- und Nachteile. Dies ist ein kurzer Überblick über die unterstützten Dateisysteme:

  1. ext2 - Altes, verlässliches GNU/Linux Dateisystem. Sehr stabil, aber ohne Aufzeichnung. Könnte lästig sein wegen langen fsck's (Checken des Systems).
  2. ext3 - Eigntlich das ext2-System - aber mit Aufzeichnungs-Unterstützung. Generell anerkannt als ein wenig langsamer als ext2 und andere Dateisysteme, aber extrem stabil und das am weitesten verbreitete, unterstützte und entwickelte GNU/Linux Dateisystem.
  3. ReiserFS - Hans Reiser's hochperformace Dateisystem mit Aufzeichnung. Es benutzt eine sehr interessante Methode des DAtendurchlasses. ReiserFS ist schnell, vor allem bei der Behandlung vieler kleiner Dateien. ReiserFS ist sehr langsam beim mounten. Ziemlich gut etabliert und stabil. ReiserFS wird zur Zeit nicht aktiv entwickelt (Reiser4 ist das neue Reiser Dateisystem).
  4. JFS - Das Aufzeichnungs-Dateisystem von IBM. JFS ist sehr schnell und braucht die geringste CPU-Prozessorenergie aller Dateisysteme. Sehr schnell beim mounten. Auf der JFS-Mail-Liste wurde berichtet, dass es an Fragmentationsproblemen leiden könnte.
  5. XFS - Sehr schnelles Dateisystem mit Aufzeichnung. Es ist als bestes für große Dateien geeignet, während es mit kleinen Dateien langsamer (immer noch ziemlich schnell) ist. Sehr schnell beim mounten.

Ein großer Unterschied ist die Aufzeichnung (etwas Ähnliches wie Verschiebungs-Logs in Datenbanken-Umgebungen). Alle Dateisysteme außer ext2 benutzen die Aufzeichnung. ext3 ist zu ext2 komplett kompatibel, weshalb man sogar mit sehr alten Rettungs-CD's mounten kann. Eine sichere Wahl für die root- Partition ist ext3. ReiserFS, XFS und JFS sind auch OK, da GRUB (der Startmanager, den wir später installieren werden) auch von diesen Dateisystemen starten kann. Bilde das Dateisystem (formatiere die Partition), indem Du yes wählst. Nun wirst Du aufgefordert, weitere Partitionen inzuzufügen. In unserem Beispiel bleibt nur noch sda2. Wähle ein DAteisystem-Typ und mounte es als /home. Bilde wiederum das Dateisystem und wähle Done an. Gehe zurück zum Hauptmenü (main menu).

Wähle Pakete

Nun sollen wir die Pakete bzw Programme wählen, die wir in unserem System installieren. Wähle CD als Quelle und das richtige CD-Laufwerk, falls Du mehr als eines hast. Nimm die Kategorie 'base' (alle Grundpakete, die gewählt sind, zu lassen ist eine gute Wahl). Wenn Du sicher bist, dass Du gewisse Pakete nicht brauchst (z.B. ein Dateisystemtyp, den Du nicht brauchst, PCMCIA, ISDN oder PPPoE Unterstützung), sei so frei und entferne sie aus der Grundpakete- Auswahl.


Seit der Installations-CD Arch 2007.08-2 kannst Du nun Pakete von den Kategorien Lib, Devel und Support hinzufügen.

Alle, keines oder einige Pakete dieser Kategorien zu wählen, ist in jedem Fall eine sichere Wahl, aber überfliege sie trotzdem. Anfänger können einfach alles auswählen.

Pakete Installieren

Das Installationsskript wird nun die ausgewählten Pakete auf Deinem System installieren. Die Programme sind binär i686-optimiert und brauchen insgesamt etwa 100MB für das Grundsystem. Deshalb sind sie recht schnell installiert.

Systemkonfiguration

Du wirst gefragt, ob Du willst, dass hwdetect einige Informationen über Deine Konfiguration sammelt. Dies ist empfohlen, weshalb Du diese Option wählen solltest.
Nun wirst Du gefragt, ob Du Unterstützung brauchst, um von USB zu starten, für FireWire-Geräte, für PCMCIA-Geräte, NFS-Shares, Software RAID Arrays und verschlüsselte Partitionen. Wähle yes, falls Du etwas brauchst; in unserem Beispiel wird nichts benötigt.
Nun wirst Du gefragt, welchen Texteditor Du benutzen möchtest; wähle nano, falls Du nicht vertraut bist mit vi/vim.
Nun wird ein Menü erscheinen, welches die wichtigsten Konfigurationsdateien auf Deinem System zeigt. Wir werden diesmal nur einige kleinere Änderungen vornehmen. Falls Du die vorhandenen Optionen, wie in rc.conf erklärt, nachschauen willst, drücke Alt+F2 um zu einer Eingabeaufforderung zu gelangen. Schaue es dort nach und wechsle mirt Alt+F1 zurück zum Installationsprogramm

/etc/rc.conf
  • Ändere Dein LOCALE, falls Du es brauchst (z.B. "de_DE.utf8") (Dieses locale muss sich mit /etc/locale.gen decken (Deutsch)#/etc/locale.gen Siehe unten.)
  • Ändere Deine TIMEZONE, falls benötigt (z.B. "Europe/Berlin")
  • Ändere Dein KEYMAP, falls nötig (z.B. "de-latin1-nodeadkesy")
  • Gib in MODULES an, falls Du weisst, dass ein wichtiges Modul fehlt ('hwdetect' sollte die wichtigsten Module eingetragen haben)
  • Gib Deinen HOSTNAME an.
  • Ändere Deine Netzwerkeinstellungen:
    • Ändere nicht die lo-Linie
    • Passe die IP-Adresse, die Netzmaske (netmask) und die Sende-Adresse (broadcast address) an, falls Du statische IP verwendest, ansonsten lass diese Information auskommentiert.
    • Setze eth0="dhcp" falls Du DHCP nutzen willst.
    • Falls Du statische IP nutzt, setzte die Gateway Adresse auf den Deines Routers und entferne des '!' vor der ROUTES Eintragung. (Lass diesen Eintrag wie er ist, falls Du DHCP nutzt.)
Über DAEMONS

Du musst diesmal die daemons-Linie (Daemons) nicht bearbeiten; es ist jedoch sinnvoll zu erklären, was Daemons sind, weil wir sie später in diesem Wiki brauchen. Analog zu einem Windows Service ist ein Daemon ein Programm, das im Hintergrund läuft, auf ein Ereignis wartet und einen Service erbringt.Ein gutes Beispiel ist ein Webserver, der auf eine Anfrage wartet, eine Seite zu liefern, oder ein SSH-Server wartet auf jemanden, der versucht sich einzuloggen. Während dies vollumfängliche Anwendungen sind, gibt es Daemons, deren Arbeit nicht so sichtbar ist. Beispiele sind ein Daemon, der Mitteilungen in eine log-Datei schreibt (z.B. syslog, metalog), ein Daemon, der die Frequenz Deines CPU absenkt, wenn er nichts zu tun hat (z.B. cpufreq) und ein Daemon, der einen graphischen Login bereitstellt (wie gdn, kdm). All diese Programme können zur Daemons-Linie hinzugefügt werden und werden dann bei Systemstart gestartet. Nützliche Daemons werden im Laufe dieses Wikis präsentiert.

Verlasse mit Ctrl+X den Editor.

/etc/hosts

Füge den gewünschten hostname hinzu (welchen Du in /etc/rc.conf zuvor gesetzt hast), so dass es in etwa so ausschaut wie folgt: 

127.0.0.1   localhost.localdomain   localhost dein-hostname

Dieses Format, inklusive den 'localhost'-Einträgen wird für Programmkompatibilität benötigt! Fehler in diesem Syntax führen dazu, dass sich Programme sehr langsam öffnen.
Die ist bei Anfängern ein ziemlich häufiger Fehler.

Für die meisten Benutzer wird es reichen, einfach dein-hostname ans Ende der Standardlinie hinzuzufügen. Jedoch raten einige Nutzer dazu, folgenden Syntax zu benutzen: 

127.0.0.1  dein-hostname.domaene.org localhost.localdomain   localhost  dein-hostname

Falls Du eine statische IP benutzt, füge eine weitere Linie mit folgendem Syntax hinzu: <static-ip> hostname.domainname.org hostname Beispiel: 

192.168.1.100 dein-hostname.domaene.org  dein-hostname
/etc/fstab, mkinitcpio.conf und modprobe.conf

Zu diesem Zeitpunkt ist es nicht nötig, die Dateien mkinitcpio.conf und modprobe.conf zu bearbeiten. mkinitcpio konfiguriert den ramdisk (z.B. booten von RAID, verschlüsselte Festplatten) und modprobe can dazu verwendet werden, einige spezielle Konfigurationsoptionen für die Module zu bestimmen.

Falls Du den hal daemon benutzen willst, um das Mounten von Festplatten, optischen Laufwerken, USB-Laufwerken usw. zu automatisieren, solltest Du /etc/fstab bearbeiten und die Einträge für cdrom, floppy und dvd auskommentieren.

/etc/resolv.conf (für statische IP)

Falls Du eine statische IP benutzt, setze Deine DNS Server in /etc/resolv.conf (namenserver <ip-adresse>). Du kannst so viele haben, wie Du willst.

Falls Du einen Router benutzt, wirst Du wahrscheinlich Deine DNS Server im Router selbst festlegen und bloß von Deinem 'resolv.conf' dorthin verweisen, indem Du die IP Deines Routers benutzt (Deine Gateway in /etc/rc.conf). Beispiel: 

nameserver 192.168.1.1

Alternativ kannst Du Deine Lieblingsserver untereinander hinzufügen, z.B.: 

nameserver 4.2.2.1
nameserver 4.2.2.2
/etc/locale.gen

Das Kommando locale-gen liest aus /etc/locale.gen und generiert spezielle Lokalisierungen. Diese können dann von glibc und jedem anderem lokaliesiertem Program oder Library zum Texterstellen benutzt werden. /etc/locale.gen ist standardmäßig eine leere Datei mit kommentierter Dokumentation. Wenn diese Datei einmal bearbeitet wurde, wird sie nie mehr berührt werden. Locale-gen wird bei jedem Update von glibc ausgeführt, wodurch alle Lokalisierungen aus /etc/locale.gen hergestellt werden.

Wähle alle Loalisierung(en), welche Du nutzen willst (lösche das # am Anfang der Zeile), z.B.: 

en_US ISO-8859-1
en_US.UTF-8

(Deine Lokalisierungen müssen mit denen in /etc/rc.conf von oben übereinstimmen.)

Die Installation wird nun das locale-gen Skript ausführen, welches die gewünschten Lokalisierungen erstellt. Du kannst in Zukunft die Lokalisierung ändern, indem Du /etc/locale.gen bearbeitest und danach locale-gen als root ausführst.

Beachte: falls Du Deine Lokalisierung nicht wählst, wird das zum "The current locale is invalid..." Fehler führen. Dies ist wahrscheinlich der häufigste Fehler unter neuen Arch Nutzern, und er führt auch zur am meisten gestellten Frage im Forum.

Root Password

Setzte zum Schluß ein root-Passwort und vergewissere Dich, dass Du es später noch weißt. Kehre zum Hauptmenü zurück und fahre mit der Installation des Startmanagers (Bootloader) fort.

Installation des Bootloaders

Da wir in unserem Beispiel kein zweites Betreibssystem haben, werden wir einen Bootloader benötigen. GNU GRUB ist der empfolene Bootloader. Alternativ kannst Du LILO wählen. Die gezeigte GRUB Konfiguration (/boot/grub/menu.lst) sollte ausreichend sein. Das einzige, was Du ändern könntest, ist die Aufklösung der Konsole. Füge zur ersten Kernel-Linie eine vga=<number> hinzu. (A Tabelle mit Auflösungen und entsprechenden Nummern ist im menu.lst abgedruckt.) 

title  Arch Linux (Main)
root   (hd0,0)
kernel /boot/vmlinuz26 root=/dev/sda1 ro vga=773
initrd /boot/kernel26.img

Das Argument "vga=773" wird einen 1024x768 framebuffer mit 256 Farbtiefe ergeben.

Verlasse die Installation und gebe reboot ein.

Wenn alles gut geht, wird Dein neues Arch Linux System nun starten und mit einer Login-Eingabe enden (Du solltest in Deinem BIOS die Startreihenfolge zurückstellen auf das Starten von Festplatte).

Herzlichen Glückwunsch und willkommen zu Deinem schönen neuen Arch Linux Basissystem!

Konfiguration des Basis-Systems

Dein neues Arch Linux Basissystem ist nun eine funktionelle GNU/Linux-Umgebung, die auf die Anpassung wartet. Von hier aus kannst Du diese Installation in all das verwandeln, was Du wünscht oder für Deine Vorhaben brauchst.

Fangen wir an.

Login mit Deinem root Account. Wir werden nun pacman konfigurieren, das System updaten und dann einen gewöhnlichen Benutzer hinzufügen.


Einstellen des Netzwerkes (falls nötig)

Dieser Abschnitt wird Dir dabei helfen, die meisten Arten von Netzwerken zu konfigurieren, falls die Installations-Skriptemit den auto-Konfigurationen für Dich nicht funktionieren.

Falls alles gut verlief, solltest Du ein funktionierendes Netzwerk haben. Versuche www.google.com zu pingen, um es zu bestätigen: 

ping -c 3 www.google.com

Falls Du erfolgreich eine Netzwerkverbindung hergesstellt hast, fahre mit Updaten, Synchronisieren und Upgraden des Systems mit pacman fort.

Falls nach dem Pingen ein "unknown host" Fehler auftrat, könntest Du schließen, dass Dein Netzwerk nicht konfiguriert ist. Du solltest zunächst die folgenden Dateien auf Integrität und saubere Einstellungen untersuchen:

/etc/rc.conf # Achte speziell in den HOSTNAME= und NETWORKING Abschnitten auf Tippfehler und Fehler.

/etc/hosts # Checke nochmals das Format. (Siehe oben.)

/etc/resolv.conf # Falls Du eine statische IP benutzt. Falls Du DHCP benutzt, wird diese Datei dynamisch erstellt und standardmäßig zerstört. Aber sie kann für Deine Einstellungen geändert werden. (Siehe Network.)

Fortgeschrittene Anweisungen, das Netzwerk einzustellen, kann im Network Artikel gefunden werden.

LAN über Kabel

Überprüfe Dein Ethernet mit 

ifconfig

Dort solltest Du einen Eintrag für eth0 sehen. Falls benötigt, kannst Du eine neue statische IP mit 

ifconfig eth0 <ip address> netmask <netmask> up

und die Standard-Gateway mit 

route add default gw <ip address of the gateway>

setzen. Kontrolliere, ob /etc/resolv.conf Deinen DNS Server enthält und füge ihn hinzu, falls er fehlt. Kontrolliere da Netzwerk nochmals mit ping www.google.de. Falls nun alles funktioniert, passe /etc/rc.conf wie in Abschnitt 2.6 besprochen an (statische IP). Falls Du einen DHCP Server/Router in Deinem Netzwerk hast, versuche 

dhcpcd eth0

Falls dies funktioniert, passe /etc/rc.conf an, wie es in Abschnitt 2.6 beschrieben wird (dynamische IP).

Kabelloses LAN

Detailiertes Setup-Wiki: Wireless Setup

Analoges Modem

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. Tip: Read Dialup without a dialer HOWTO.

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 LinModem homepage.

ISDN

Setting up ISDN is done in three steps:

  1. Install and configure hardware
  2. Install and configure the ISDN utilities
  3. Add settings for your ISP

The current Arch stock kernels include the necessary ISDN modules, meaning that you won't 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.

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: 

modprobe hisax type=18 protocol=2

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.

Once you have confirmed that your card works with certain settings, you can add the module options to your /etc/modprobe.conf: 

alias ippp0 hisax
options hisax type=18 protocol=2

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.

That being done, you should have working, supported hardware. Now you need the basic utilities to actually use it!

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.

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.

If you set up everything correctly, you should now be able to establish a dial-up connection with 

isdnctrl dial ippp0

as root. If you have any problems, remember to check the logfiles!

DSL (PPPoE)

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.

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 

/etc/rc.d/adsl start

and 

/etc/rc.d/adsl stop

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.

Updaten, Synchronisieren und Upgraden des Systems mit pacman

Now we will update the system using pacman.

What is pacman ?

Pacman is the package manager of Arch Linux. Pacman is written in C and is fast, simple, and extremely powerful. 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. We will use pacman to download software packages from remote repositories and install them onto your system.

Pacman is the most important tool in your Arch Linux toolbox for building the core system into whatsoever you please.

Configuring pacman

/etc/pacman.conf

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 repository that pacman can use when searching for packages. The exception to this is the options section, which defines global options. 

nano -w /etc/pacman.conf

Example: 

[core]
# Add your preferred servers here, they will be used first
#Server = http://mirrors.easynews.com/linux/archlinux/current/os/i686
Include = /etc/pacman.d/core
[extra]
# Add your preferred servers here, they will be used first
#Server = http://mirrors.easynews.com/linux/archlinux/extra/os/i686
Include = /etc/pacman.d/extra
#[unstable]
# Add your preferred servers here, they will be used first
#Server = http://mirrors.easynews.com/linux/archlinux/unstable/os/i686
#Include = /etc/pacman.d/unstable
[community]
# Add your preferred servers here, they will be used first
#Server = http://mirrors.easynews.com/linux/archlinux/community/os/i686
Include = /etc/pacman.d/community

Ensure the [community] repo is enabled (remove the # in front of the "Include = /etc/pacman.d/community" and "[community]" lines). Arch's community repository offers many useful applications.

The "Server =" lines, if uncommented, will force the specified server to be searched first and foremost. Further configuration for repos are under /etc/pacman.d/

/etc/pacman.d/

Faster mirrors will dramatically improve pacman performance, and your overall Arch Linux experience.

Use the rankmirrors script supplied with the latest pacman package, which will rank the mirrors automatically by their speed. For example, to rank the mirrors in the core repository, you would have to run as root: 

rankmirrors /etc/pacman.d/core

Repeat as necessary for all desired repositories.

Alternatively, you may choose to manually Edit the files in /etc/pacman.d/ (community, core, extra) and move the mirrors which are located nearest to you to the top of the list. (if you use nano, Alt+A starts selecting an area, cursor down marks the lines, Ctrl+K cuts the selected area and Ctrl+U uncuts it). Repeat this for all files in /etc/pacman.d/. You may want to return to these configuration files to experiment with various mirrors. Choose wisely.

Update System

Update, sync, and upgrade your entire new system with: 

pacman -Syu

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.)

Take note as to whether a major kernel upgrade is occurring.

If the kernel undergoes a major upgrade, modules such as nvidia and madwifi, for instance, (to be installed later in the guide, if necessary) will be inoperable, since the new, upgraded package versions of such modules will have been built against the newer kernel, and your system is currently using an older one. A reboot will be necessary.

The beauty of the rolling release

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.

Get familiar with pacman

Pacman is the Arch user's best friend. It is highly recommended to study and learn how to use the pacman tool. Try: 

man pacman

Check out the bottom of this article, and look up the pacman wiki entries at your leisure.


Add a user and setup groups

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: 

adduser

While most default options are safe to use, you may want to add storage, audio, video, optical, and wheel to your additional groups- especially if you are planning on having a full-featured desktop environment.

Groups and users thereof are defined in /etc/group.

They include:

  • audio - for tasks involving sound card and related software
  • wheel - for using sudo
  • storage - for managing storage devices
  • video - for video tasks and 3d acceleration
  • optical - for managing tasks pertaining to the optical drive(s)
  • floppy - for access to a floppy if necessary
  • lp - for managing printing tasks

See the Groups article to understand what groups you need to be a member of. You may also add your user to the desired groups like so, (as root): 

usermod -aG audio,video,floppy,lp,optical,network,storage,wheel USERNAME

Check the man pages for usermod and gpasswd for more information.

Part II: Install X and configure ALSA

Installing and configuring X

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 Unix-like operating systems.

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.

  • 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:
pacman -S libgl

(Proprietary video drivers provide their own gl library implementations.)

Now we will install the base Xorg packages using pacman. This is the first step in building a GUI. 

pacman -S xorg

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.

If you need a list of all open-source video drivers, do: 

pacman -Ss xf86-video | less

If you don't know what graphics card you are using, do: 

lspci | grep VGA

Here is a list of open source drivers, and corresponding video chipsets.

  • xf86-video-apm Alliance ProMotion video driver
  • xf86-video-ark ark video driver
  • xf86-video-ati ati video driver
  • xf86-video-chips Chips and Technologies video driver
  • xf86-video-cirrus Cirrus Logic video driver
  • xf86-video-dummy dummy video driver
  • xf86-video-fbdev framebuffer video driver
  • xf86-video-glint GLINT/Permedia video driver
  • xf86-video-i128 Number 0 i128 video driver
  • xf86-video-i740 Intel i740 video driver
  • xf86-video-i810 Intel i810/i830/i9xx video drivers
  • xf86-video-imstt Integrated Micro Solutions Twin Turbo vidoe driver
  • xf86-video-mga mga video driver (Matrox Graphics Adapter)
  • xf86-video-neomagic neomagic video driver
  • xf86-video-nv nvidia nv video driver
  • xf86-video-rendition Rendition video driver
  • xf86-video-s3 S3 video driver
  • xf86-video-s3virge S3 Virge video driver
  • xf86-video-savage savage video driver
  • xf86-video-siliconmotion siliconmotion video driver
  • xf86-video-sis SiS video driver
  • xf86-video-sisusb SiS USB video driver
  • xf86-video-tdfx tdfx video driver
  • xf86-video-trident Trident video driver
  • xf86-video-tseng tseng video driver
  • xf86-video-unichrome Unichrome video drivers
  • xf86-video-v4l v4l video driver
  • xf86-video-vesa vesa video driver
  • xf86-video-vga VGA 16 color video driver
  • xf86-video-via via video driver
  • xf86-video-vmware vmware video driver
  • xf86-video-voodoo voodoo video driver
  • 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.

Use pacman to install the appropriate video driver for your video card/onboard video. e.g.: 

pacman -S xf86-video-i810

(for the intel 810 chipset driver.)

  • If you still don't know which video driver to install, you may install the whole video driver group package, and allow the Xorg -configure script to specify the driver in xorg.xonf:
pacman -S xorg-video-drivers

Create /etc/X11/xorg.conf

What is /etc/X11/xorg.conf?

/etc/X11/xorg.conf is the main configuration file for your X Window System, the foundation of your Graphical User Interface. It is a plain text file ordered into sections and subsections. Important sections are Files, InputDevice, 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, say a video projector and an on board LCD of a notebook.

By default, you will not have an Xorg config file, and with the newest versions of Xorg, you don't need one if the autodetection works satisfactorily and you don't need to turn on features such as aiglx and so on.

Most people will still find that they need to generate a config file, however.


  • Use the Xorg -configure script to make a basic config file:
Xorg -configure

Move the generated config file to /etc/X11: 

mv /root/xorg.conf.new /etc/X11/xorg.conf

Inspect your config file: 

nano /etc/X11/xorg.conf

Ensure the Xorg -configure script has correctly specified your video driver. e.g.: 

Section "Device"
Driver  "i810"

Ensure there are horizontal sync and vertical refresh specs under section "Monitor". If not, add them: 

Section "Monitor"
       Identifier   "Monitor0"
       VendorName   "Monitor Vendor"
       ModelName    "Monitor Model"
       HorizSync     30.0 - 130.0 # Safe for LCD's
       VertRefresh   50.0 - 100.0 # Safe for LCD's and most CRT's.
EndSection

(If you do not know these specs, consult your monitor's documentation.)

Specify your default color depth under section "Screen": 

Section "Screen"
       Identifier "Screen0"
       Device     "Card0"
       Monitor    "Monitor0"
       DefaultDepth 24

(Typically, this will be set to 24 for true color.)

Also add your desired Modes to your "Display" subsection, at least under the Depth 24 header, e.g.: 

 SubSection "Display"
               Viewport   0 0
               Depth     24
               Modes "1024x768" "800x600" "640x480"

Continue with Simple baseline X test, or refer to following sections for proprietary driver guidelines.

Using proprietary Graphics Driver (nVIDIA, ATI)

You may choose to use the proprietary video drivers from nVIDIA or ATI.

nVIDIA Graphic Cards

The nVIDIA proprietary drivers are generally considered to be of excellent quality, and offer superior 3D performance.

Before you configure your Graphics Card you will need to know which driver fits. Arch currently has 3 different drivers that each match a certain subset of Cards:

1. nvidia-71xx for very old Cards like TNT and TNT2

2. nvidia-96xx slightly newer cards up to the GF 4

3. nvidia newest GPUs after the GF 4

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.

Install the appropriate nvidia driver, e.g.: 

pacman -S nvidia

The nVIDIA package has a utility for updating your existing /etc/X11/xorg.conf for use with the nVIDIA driver: 

nvidia-xconfig

It also has several options which will further specify the contents and options of the xorg.conf file. For example, 

nvidia-xconfig --composite --add-argb-glx-visuals

For more detailed information, see nvidia-xconfig(1).

Some useful tweaking options in the device section are (beware that these may not work on your system): 

       Option          "RenderAccel" "true"
       Option          "NoLogo" "true"
       Option          "AGPFastWrite" "true"
       Option          "EnablePageFlip" "true"

Make sure all instances of DRI are commented out: 

#    Load        "dri"

Double check your /etc/X11/xorg.conf to make sure your default depth, horizontal refresh, vertical refresh, and resolutions are acceptable.

Logout and login.

Start X server as normal user, to test your configuration: 

startx

Advanced instructions for nvidia configuration can be found in the NVIDIA article.

ATI Graphic Cards

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.

Install the proprietary ATI Driver with 

pacman -S catalyst

Use the aticonfig tool to modify the xorg.conf. Note: The proprietary driver does not support AIGLX. To use Compiz or Beryl with this driver you would need to use XGL.

Install the open-source ATI Driver with 

pacman -S xf86-video-ati

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.

Advanced instructions for ATI configuration can be found in the ATI wiki.

Simple baseline X test

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, before installing a complete desktop environment, 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. Xterm will allow us to effectively test if your video driver and /etc/X11/xorg.conf are properly configured. (Alternatively, you may wish to test if the X autodetection works satisfactorily, in the absence of /etc/X11/xorg.conf.) 

pacman -S xterm
~/.xinitrc

Edit your /home/username/.xinitrc file, as normal user, to dictate which X Server event is invoked with the 'startx' command: 

su yourusername

nano ~/.xinitrc

and add (or uncomment) 

exec xterm

So that it looks like this: 

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#
exec xterm
# exec wmaker
# exec startkde
# exec icewm
# exec blackbox
# exec fluxbox

Be sure to have only one uncommented exec line in your ~/.xinitrc

If you do not have ~/.xinitrc, simply create one with the above information, or copy the sample file from /etc/skel/ to your home directory: 

cp /etc/skel/.xinitrc ~/
  • NOTE: In the absence of file ~/.xinitrc, /etc/X11/xinit/xinitrc will be used as a fallback, which defaults to using TWM and Xterm.

Start X Server as normal user, with: 

startx

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.

Advanced instructions for Xorg configuration can be found in the Xorg article.

Configure the audio card with alsamixer

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. 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.)

Your audio card should already be working, but you can't hear anything because it is muted by default.

Install the alsa-utils package: 

 pacman -S alsa-utils

Did you add your normal user to the audio group? If not, now would be a good time. As root do: 

gpasswd -a yourusername audio

As normal user, do: 

alsamixer

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.) Leave alsamixer by pressing ESC.

Then run alsactl as root. This will create '/etc/asound.state', saving the alsamixer settings. 

alsactl store

Also, add the alsa daemon to your DAEMONS section in /etc/rc.conf to automatically restore the mixer settings on boot-up. 

nano /etc/rc.conf
DAEMONS=(syslog-ng network crond alsa)

Note that the alsa daemon merely restores your volume mixer levels on bootup. It is separate from the alsa audio library (and kernel level API).

Expanded information available in the ALSA wiki entry.

Part III: Installing and configuring a Desktop Environment

If you ask two people what the best Desktop Environment or Window Manager is, you will get six different answers. Choose the best environment for your needs.

  • If you want something full-featured and similar to Windows and Mac OSX, KDE is a good choice
  • If you want something more minimalist, which follows the K.I.S.S. principle more closely, GNOME is a good choice
  • If you have an older machine or want something lighter, xfce4 is a good choice, still giving you a complete environment
  • If you need something even lighter, openbox, fluxbox or fvwm2 may be right (not to mention all other lightweight window managers like windowmaker and twm).
  • If you need something completely different, try ion, wmii, or dwm.

Install Fonts

At this point, you may want to install some good-looking fonts, before installing a desktop environment/window manager. Dejavu and bitstream-vera are nice font sets. For websites, you may want to have the Microsoft fonts too. Install with: 

pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera

GNOME

About GNOME

The GNU Network Object Model Environment. 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.

Installation

Install the complete GNOME environment with: 

pacman -S gnome gnome-extra

It's safe to choose all packages shown. Alternatively, you may wish to install a more basic, stripped-down GNOME: 

pacman -S gnome
Useful DAEMONS for GNOME

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.

You may want to install a graphical login manager. For GNOME, the gdm daemon is a good choice. Install gdm with 

pacman -S gdm

You will almost certainly want the hal and fam daemons.

Start hal and fam: 

/etc/rc.d/hal start

/etc/rc.d/fam start

Add them to your /etc/rc.conf DAEMONS section, so they will be invoked on bootup: 

nano /etc/rc.conf

DAEMONS=(syslog-ng network crond alsa hal fam gdm)

(If you prefer to log into the console and manually start X in the 'Slackware tradition', leave out gdm.)

~/.xinitrc

This configuration file controls what occurs when you type 'startx'.

Edit your /home/username/.xinitrc to utilize GNOME: 

nano ~/.xinitrc

Uncomment the 'exec gnome-session' line so that it looks like this: 

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#
#exec xterm
#exec wmaker
# exec startkde
exec gnome-session
# exec icewm
# exec blackbox
# exec fluxbox

If you do not have ~/.xinitrc, simply create one with the above information, or copy the sample file from /etc/skel/ to your home directory: 

cp /etc/skel/.xinitrc ~/

Remember to have only one uncommented exec line in your ~/.xinitrc.

Switch to normal user: 

su username

And test it with: 

startx

You may want to install a terminal and an editor. I would recommend gnome-terminal (part of the group gnome-extra) and geany: 

pacman -S geany gnome-terminal

Advanced instructions for installing and configuring GNOME can be found in the Gnome article.

Eye Candy

You may find the default GNOME theme and icons not very attractive. A nice gtk theme is murrine. Install it with 

pacman -S gtk-engine-murrine

and select it with System->Preferences->Theme. You can find more themes, icons, and wallpaper at Gnome Look.

KDE

About KDE

The K Desktop Environment. KDE is a powerful Free Software graphical desktop environment for GNU/Linux and UNIX workstations. It combines ease of use, contemporary functionality, and outstanding graphical design with the technological superiority of UNIX-like operating systems.

Installation

Arch offers several versions of kde: kde, kdebase, and KDEmod. Choose one of the following, and continue below with "Useful KDE DAEMONS":

1.) Package kde is the complete, vanilla KDE, ~300MB. 

pacman -S kde

2.) Package kdebase is a slimmed-down version with less applications, ~80MB. 

pacman -S kdebase

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/. KDEmod is extremely fast, lightweight and responsive, with a pleasing, customized theme.

Useful KDE DAEMONS

KDE will require the hal (Hardware Abstraction Layer) and fam (File Alteration Monitor) daemons. The kdm daemon is the K Display Manager, which provides a graphical login, if desired.

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.

Start hal and fam: 

/etc/rc.d/hal start

/etc/rc.d/fam start
  • NOTE: The hal daemon will automatically start the dbus daemon.

Edit your DAEMONS section in /etc/rc.conf: 

nano /etc/rc.conf

Add hal and fam to your DAEMONS section, to invoke them on bootup. If you prefer a graphical login, add kdm as well: 

DAEMONS=(syslog-ng network crond alsa hal fam kdm)
  • This method will start the system at runlevel 3, (/etc/inittab default, multiuser mode), and then start KDM as a daemon.
  • If you prefer to log into the console at runlevel 3, and manually start X in the 'Slackware tradition', leave out kdm, or comment it out with an exclamation. ( ! )
~/.xinitrc

This configuration file controls what occurs when you type 'startx'.

Edit your /home/username/.xinitrc to utilize KDE: 

nano ~/.xinitrc

Uncomment the 'exec startkde' line so that it looks like this: 

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#
#exec xterm
#exec wmaker
exec startkde
# exec gnome-session
# exec icewm
# exec blackbox
# exec fluxbox

If you do not have ~/.xinitrc, simply create one with the above information, or copy the sample file from /etc/skel/ to your home directory: 

cp /etc/skel/.xinitrc ~/

Remember to have only one uncommented exec line in your ~/.xinitrc.

Switch to your normal user: 

su username

Now try starting your X Server: 

startx

Advanced instructions for installing and configuring KDE can be found in the KDE article.

Congratulations! Welcome to your KDE desktop environment on your new Arch Linux system! You may wish to continue by viewing Tweaks and finishing touches, or the rest of the information below. You may also be interested in the Post Installation Tips wiki article.

Xfce

About Xfce

Xfce is a Desktop Environment, like GNOME or KDE. It contains a suite of apps like a root window app, window manager, file manager, panel, etc. Xfce is written using the GTK2 toolkit 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.

Installation

Install xfce with 

pacman -S xfce4 xfce4-goodies

If you use kdm or gdm a new xfce session should have appeared. Alternatively, you can use 

startxfce4

Advanced instructions for installing and configuring Xfce can be found in the Xfce article.

*box

Fluxbox

Fluxbox © is yet another windowmanager for X. 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).

Install Fluxbox using 

pacman -S fluxbox fluxconf

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: 

exec startfluxbox

More information is available in the Fluxbox article.

Openbox

Openbox is a standards compliant, fast, light-weight, extensible window manager.

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.

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.

Install openbox using 

pacman -S openbox obconf obmenu

Once openbox is installed you will get a message to move menu.xml & rc.xml to ~/.config/openbox/ in your home directory: 

mkdir -p ~/.config/openbox/
cp /etc/xdg/openbox/rc.xml ~/.config/openbox/
cp /etc/xdg/openbox/menu.xml ~/.config/openbox/

In the file "rc.xml" you can change various settings for Openbox (or you can use OBconf). In "menu.xml" you can change your right-click menu.

To be able to log into openbox you can either go via graphical login using KDM/GDM or startx, in which case you will need to edit your ~/.xinitrc (as user) and add the following: 

exec openbox

For KDM there is nothing left to do; openbox is listed in the sessions menu in KDM.

Useful programs for openbox are:

  • PyPanel or LXpanel if you want a panel
  • feh if you want to set the background
  • ROX if you want a simple file manager and desktop icons

More information is available in the Openbox article.

fvwm2

FVWM is an extremely powerful ICCCM-compliant multiple virtual desktop window manager for the X Window system. Development is active, and support is excellent.

Install fvwm2 with 

pacman -S fvwm

fvwm will automatically be listed in kdm/gdm in the sessions menu. Otherwise, add 

exec fvwm

to your user's .xinitrc.

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.

Tweaks/Finishing touches

HAL

Since you have now installed a desktop environment, 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.

KDE, GNOME and XFCE uses HAL.

The installation procedure is described in the HAL article. Some information can also be found at Wikipedia.

Adjusting Mouse for scroll wheel

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): 

       Option      "ZAxisMapping" "4 5 6 7"

evdev

If you have a modern USB mouse with several thumb buttons and/or functions, you may want to install the evdev mouse driver, which will allow you to exploit the full functionality of your mouse: 

pacman -S xf86-input-evdev

Load the driver: 

modprobe evdev

Find your mouse name by entering the following, exactly: 

cat /proc/bus/input/devices | egrep "Name"

Using the mouse name, configure your /etc/X11/xorg.conf InputDevice section accordingly, e.g.: 

Section "InputDevice"
 Identifier      "Evdev Mouse"
 Driver          "evdev"
 Option          "Name" "Logitech USB-PS/2 Optical Mouse"
 Option          "CorePointer"
EndSection

You must have only one "CorePointer" device specified in /etc/X11/xorg.conf, so be sure to comment out any other mouse entries until you feel safe removing the old, unused entries.

Also edit the ServerLayout section to include Evdev Mouse as the CorePointer, e.g.: 

Section "ServerLayout"
   Identifier     "Layout0"
   Screen      0  "Screen0"
   InputDevice    "Keyboard0" "CoreKeyboard"
   InputDevice    "Evdev Mouse" "CorePointer"

Adjusting Keyboard Layout

You may want to change your keyboard layout. To do this edit your /etc/X11/xorg.conf and add these lines in the Input Section (keyboard0) (the example shows a German keyboard layout with no dead keys; alter this to fit your needs). 

       Option          "XkbLayout"     "de"
       Option          "XkbVariant"    "nodeadkeys"

Additional tweaks for laptops

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 acpid 

pacman -S acpid

and add it to the daemons in /etc/rc.conf (acpid). Start it with 

/etc/rc.d/acpid start

More-specific information about Arch Linux on various Laptops can be found at Category:Laptops (English)

Configuring CPU frequency scaling

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 

pacman -S cpufrequtils

and add cpufreq to your daemons in /etc/rc.conf. Edit the config file /etc/conf.d/cpufreq and change 

governor="conservative"

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 don't 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 

modprobe <modulname>

and start cpufreq with 

/etc/rc.d/cpufreq start

For more details, see Cpufrequtils

Useful Applications

This section will never be complete. It just shows some good applications for the everyday user.

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.

Internet

Firefox

The ever-popular Firefox web browser is available through pacman. Install with: 

pacman -S firefox

Be sure and install 'flashplugin', 'mplayer', 'mplayer-plugin', and the 'codecs' packages for a complete web experience: 

pacman -S flashplugin mplayer mplayer-plugin codecs

(The codecs package contains codecs for Quicktime and Realplayer content.)

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.

Office

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.

Multimedia

Video Player

VLC

VLC Player is a multimedia player for Linux. To install it, simply type the code below. 

pacman -S vlc

(TODO) Instructions for VLC mozilla plug-in

Mplayer

MPlayer is a multimedia player for Linux. To install it, simply type the code below. 

pacman -S mplayer

It also has a Mozilla plug-in for videos and streams embedded in web pages. To install it, simply type the code below. 

pacman -S mplayer-plugin

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. 

pacman -S kmplayer

(TODO) GMPlayer instructions

GNOME

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. It comes with added functionality such as:

  • Video thumbnailer for the file manager
  • Nautilus properties tab
  • Epiphany / Mozilla (Firefox) plugin to view movies inside your browser
  • Webcam utility (in development)

Totem-xine is still the better choice if you want to watch DVDs.

Totem is part of the gnome-extra group; the Totem webbrowser plugin isn't.

To install separately: 

pacman -S totem

To install the Totem webbrowser plugin: 

pacman -S totem-plugin

KDE

Kaffeine

Kaffeine is a good option for KDE users. To install it, simply type the code below. 

pacman -S kaffeine

Audio Player

Gnome/Xfce

Exaile

Exaile is a music player written in Python that makes use of the GTK+ toolkit.

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.

Rhythmbox has a number of features, including:

  • Easy-to-use music browser
  • Searching and sorting
  • Comprehensive audio format support through GStreamer
  • Internet radio support
  • Playlists

To install rhythmbox: 

pacman -S rhythmbox

Other good audio players are: Banshee, Quodlibet, and Listen. See Gnomefiles to compare them.

KDE

Amarok

Amarok is one of the best audio players and music library systems available for KDE. To install it, simply type the code below. 

pacman -S amarok-base

Console

Moc is a ncurses-based audio player for the console; another good choice is mpd.

Another excellent choice is cmus.

Other X-based

(TODO) Xmms, audacious, bmpx.

Codecs and other multimedia content types

DVD

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.

Flash

Install the flash plugin using 

pacman -S flashplugin

to enable Macromedia (now Adobe) Flash in your browser.

Quicktime

Quicktime codecs are contained in the codecs package. Just type 

pacman -S codecs

to install them.

Realplayer

The codec for Realplayer 9 is contained in the codecs package. Just type 

pacman -S codecs

to install them. Realplayer 10 is available as a binary package for Linux. You can get it from AUR here.

CD and DVD Burning

GNOME

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.

To install: 

pacman -S brasero

KDE

K3b

K3b (from KDE Burn Baby Burn) is a free software CD and DVD authoring application for GNU/Linux and other Unix-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.

K3b was voted LinuxQuestions.org's Multimedia Utility of the Year (2006) by the majority (70%) of voters.

To install: 

pacman -S k3b



(Todo) cdrecord, graveman...

Most CD burners are wrappers for cdrecord: 

pacman -S cdrkit

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.

A good command-line DVD-burning tool is growisofs: 

pacman -S dvd+rw-tools

TV-Cards

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 bunch is supported. Be sure to check at a Hardware Database to be sure (see this list, for example). Once you know your Model, there are just a few steps ahead to get you going.

In most cases, you will need to use the bttv-drivers (other drivers exist, like V4L) together with the I2C-modules. Configuring those is the hardest task. If you are lucky, a 

modprobe bttv

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. If the autodetection did not work, you will need to check the file CARDLIST, which is included in the tarball of bttv to find out the right parameters for your card. A PV951 without radio support would need this line: 

modprobe bttv card=42 radio=0

Some cards need the following line to produce sound: 

modprobe tvaudio

However, that varies. So just try it out. Some other cards demand the following line: 

modprobe tuner

This is object to trial-and-error, too.

TODO: clarify the installation-procedure

To actually watch TV, install the xawtv-package with 

pacman -S xawtv

and read its manpage.

TODO: clarify some possible problems and procedures. Introduction to XAWTV on another page?

Digital Cameras

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.

USB Memory Sticks / Hard Disks

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.

Maintaining the system

Pacman

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.

A more-detailed description of Pacman can be found in its article.

Useful commands

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): 

pacman -Sy

To upgrade all packages on the system: 

pacman -Su

To sync, update, and upgrade all the packages on the system with one command: 

pacman -Syu

To install or upgrade a single package or list of packages (including dependencies): 

pacman -S packageA packageB

You can also sync, update the package database, and install packages in one command: 

pacman -Sy packageA packageB

To remove a single package, leaving all of its dependencies installed: 

pacman -R package

To remove a package and all of the package's dependencies which aren't used by any other installed package: 

pacman -Rs package

To remove all of the package's dependencies now unneeded and do not make any backup of settings: 

pacman -Rsn package

To search the remote (repo) package database for a list of packages matching a given keyword: 

pacman -Ss keyword

To list all packages on your system 

pacman -Q

To search (query) the local (your machine) package database for a given package: 

pacman -Q package

To search (query) the local (your machine) package database for a given package and list all pertinent information: 

pacman -Qi package

To defragment pacman's cache database and optimize for speed: 

pacman-optimize

To count how many packages are currently on your system: 

pacman -Q | wc -l

To install a package compiled from source using ABS and makepkg: 

pacman -U packagename.pkg.tar.gz

Note: There are countless additional pacman functions and commands. Try man pacman and consult the pacman wiki entries.

Polishing & Further information

For further information and support you can go to the homepage, search the wiki, the forums, the IRC channel, and the mailing lists.

Where to go from here? You may also be interested in:

Post Installation Tips

Get All Mouse Buttons Working

Improve Pacman Performance

Kernel Compilation

Pm-utils

Cpufrequtils

Eye Candy

Abgerufen von „https://wiki.archlinux.de/index.php?title=Anleitung_für_Einsteiger&oldid=9960“