https://wiki.archlinux.org/api.php?action=feedcontributions&user=Bennylb0&feedformat=atomArchWiki - User contributions [en]2024-03-29T06:58:21ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=424509Dell XPS 13 (9343)2016-03-07T10:31:12Z<p>Bennylb0: Added kernel 4.5-rc7 to I2S note as it's also broken in this release.</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 13 (2015)]]<br />
{{Note|This page refers to the early 2015 model of XPS 13. For the late 2015 model, see [[Dell XPS 13 (2016)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<br />
|-<br />
| Wireless switch || {{Y|Works, but is [[#rfkill_issues_with_Broadcom_wireless|problematic]] with Broadcom WiFi}} || rfkill<br />
|}<br />
<br />
The [http://www.dell.com/us/p/xps-13-9343-laptop/pd 2015 Dell XPS 13 (9343)] is the second-generation model of the XPS 13 line, and like its predecessor, it has official Linux support courtesy of Dell's Project Sputnik team. They target Ubuntu 14.04 LTS, but the improvements and support from the Sputnik team are generally applicable to all distros.<br />
<br />
The installation process for Arch on the XPS 13 does not differ from any other PC. For installation help, please see the [[Installation guide]], [[Beginners' guide]] and [[UEFI]]. This page covers the current status of hardware support on Arch, as well as post-installation recommendations.<br />
<br />
As of kernel 4.1.3, a patched kernel is no longer necessary. However, some manual configuration is still recommended to get the best experience.<br />
<br />
== Model differences ==<br />
Although the XPS 13 is sold in a variety of configurations in most markets, those wanting to run Linux should pay special attention to display options (FHD/QHD+) and WiFi adapter differences (Dell DW1560 vs. Intel 7265). For users with the QHD+ model, you'll need to use a DE/WM that properly supports [[HiDPI]]. Regarding the WiFi adapter choices, both cards do work in Arch, but the Dell DW1560 requires a proprietary kernel module that is not well-supported, whereas the Intel 7265 is supported by the mainline kernel.<br />
<br />
There are no exclusive hardware differences between the Developer Edition and the Windows edition of this laptop; this guide is equally applicable to both models.<br />
<br />
== Configuration ==<br />
<br />
=== BIOS updates ===<br />
[http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=28M21 BIOS update A07] was released on 2015-11-26. With A02 or newer, almost everything should work out of the box, and the kernel boot parameters that were used in conjunction with earlier BIOS versions are no longer necessary. Store the update binary on your EFI partition ({{ic|/boot/EFI}}) or on a USB flash drive, reboot, and choose BIOS Update in the F12 boot menu.<br />
<br />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} to be installed. See the [[Broadcom wireless]] page for more details and/or assistance.<br />
<br />
Some higher-end models do not use the Dell-branded adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card, see {{AUR|linux-firmware-git-iwlwifi}}.}}<br />
<br />
=== Bluetooth ===<br />
{{Note|'''Intel WiFi users:''' If your WiFi card supports Bluetooth, then the BT interface should be available out-of-the-box, as the required firmware is included in {{pkg|linux-firmware}}.}}<br />
<br />
The Broadcom Bluetooth firmware is not available in the kernel ([http://tech.sybreon.com/2015/03/15/xps13-9343-ubuntu-linux/ source]), so you will have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. You need to extract the {{ic|.cab}} file with {{Pkg|cabextract}} and then convert it to a {{ic|.hcd}} file with ''hex2hcd'' from {{Pkg|bluez-utils}}:<br />
<br />
$ cabextract 20662520_6c535fbfa9dca0d07ab069e8918896086e2af0a7.cab<br />
$ hex2hcd BCM20702A1_001.002.014.1443.1572.hex<br />
# mv BCM20702A1_001.002.014.1443.1572.hcd /lib/firmware/brcm/BCM20702A1-0a5c-216f.hcd<br />
# ln -rs /lib/firmware/brcm/BCM20702A1-0a5c-216f.hcd /lib/firmware/brcm/BCM20702A0-0a5c-216f.hcd<br />
<br />
After reboot, the firmware should be available for your Bluetooth interface.<br />
<br />
=== Audio ===<br />
{{Note|Proper audio support is dependent on having the latest BIOS update. If you have not yet updated to BIOS A02 or newer, please do that first.}}<br />
<br />
The sound chipset in this laptop, a Realtek ALC3263, is described as "dual-mode", meaning it supports both the [[wikipedia:Intel_High_Definition_Audio|HDA standard]] and the [[wikipedia:I²S|I2S standard]]. The embedded controller in the XPS 13 uses the [[wikipedia:Advanced_Configuration_and_Power_Interface|ACPI]] _REV value provided by the OS you use to determine which mode the sound chipset should be initialized in at boot.<br />
<br />
==== HDA mode ====<br />
With BIOS A02+ and Arch kernel 4.3 or older, the sound card will be initialized in HDA mode.<br />
<br />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<br />
<br />
Note that if you are dual-booting with Windows, you will have to do a cold boot twice before HDA sound will work in Linux and vice-versa.<br />
<br />
==== I2S mode ====<br />
With BIOS A02+ and Arch kernel 4.4 or newer, the sound card will be initialized in I2S mode.<br />
{{Note|I2S regressed: in 4.5-rc6 and 4.5-rc7 'aplay -l' doesn't even show broadwell-rt286 anymore. Expect a regression when 4.5 hits stable.}}<br />
<br />
I2S support in Linux is quite nascent and wasn't up to par with HDA support until recently, so a quirk flag was enabled in the mainline kernel that would force HDA mode on.[http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039] This flag has been disabled in the stock Arch kernel as of 4.4.[https://bugs.archlinux.org/task/47710] Also note that I2S support is known to be broken with older versions of alsalib.[http://www.spinics.net/lists/linux-acpi/msg57457.html]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
==== ALSA configuration ====<br />
By default, ALSA doesn't output sound to the PCH card but to the HDMI card. This can be changed by following [[ALSA#Set the default sound card]]. In the current case, both cards use the {{ic|snd_hda_intel}} module. To set the proper order, create the following {{ic|.conf}} file in {{ic|/etc/modprobe.d/}} [https://bbs.archlinux.org/viewtopic.php?pid=1446773#p1446773]:<br />
<br />
{{hc|/etc/modprobe.d/alsa-base.conf|2=<br />
options snd_hda_intel index=1,0<br />
}}<br />
<br />
=== High quality ICC monitor profiles ===<br />
An ICC profile is a binary file which contains precise data regarding the color attributes of the monitor. It allows you to produce consistent and repeatable results for graphic and document editing and publishing. The following ICC profiles are made with DispcalGUI, ArgyllCMS and a spectrophotometer for absolute color accuracy. Since every monitor is different it is possible to achieve better results calibrating your own monitor, but if you don't have a colorimeter or a spectrophotometer you will get far better results with the following XYZ LUT + MATRIX profiles made with a ~3500 patches testchart instead of the canned ones. If you previously didn't install a canned profile you will notice a night and day difference in color accuracy. Do not use a profile made for the QHD+ version with the FHD one and vice versa.<br />
The profiles has been made with the spectrophotometer's high resolution spectral mode, with white and black level drift compensation, the high quality ArgyllCMS switch and 3440 patches. Dynamic Brightness Control has been disabled and the monitor has been turned on at least 30 minutes before commencing the calibration.<br />
<br />
* [https://mega.nz/#!nkNVQDCI!YYcS32HLWk1Aqry30dmOrt0wrfH9W_VczNesHQEpG_U QHD+, D65, Gamma 2.2, max luminance].<br />
<br />
{{Note|You should disable Dynamic Brightness Control to accurately calibrate the QHD+ display: https://github.com/advancingu/XPS13Linux/issues/2}}<br />
<br />
* FHD, D65, Gamma 2.2, max luminance: coming soon (I will get my hands on the FHD monitor in February.) However, it may not be possible to accurately calibrate the FHD display due to the dynamic contrast behaviour of the panel which cannot be disabled.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, you can use {{pkg|xf86-input-libinput}}. The libinput driver supports nearly all button layouts out of the box with few additional settings. <br />
<br />
{{hc|/etc/X11/xorg.conf.d/50-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
For kernel >= 4.4, the touchpad description is "DLL0665:01 06CB:76AD Touchpad".<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
At least since kernel 4.3.3 the flickering caused by {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} seems to have been fixed, and freezes happen significantly less often. However, heavy flickering may still occur with external monitors.<br />
<br />
Additionally, [[powertop]] may also be employed to tweak the performance and monitor power consumption.<br />
<br />
{{Note|<br />
* Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W. As of kernel version 4.3.3 it still causes occasional flickering but no longer so mch as to be unusable.<br />
* {{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").<br />
}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
<br />
{{Out of date|kept for users of other distros until the fix is released upstream.}}<br />
<br />
Update {{pkg|xf86-video-intel}} if you haven't already; this should fix the issue.<br />
<br />
=== Graphical artifacting/instability after S3 resume ===<br />
If you encounter some artifacts and/or an unusable graphical environment after resuming from a suspend, you may want to [[Intel_graphics#SNA_issues|switch your Intel graphics acceleration from SNA to UXA]]. Switching to UXA, however, will result in decreased performance. Switching to xf86-video-modesetting (glamor acceleration) should not decrease performance much, however it is still not known if will fix resume.<br />
<br />
=== Connection issues with Broadcom wireless ===<br />
If {{ic|wifi-menu}} and {{ic|iwlist scan}} fail after driver installation and reboot, try disabling "Wireless Switch" control in the BIOS.<br />
<br />
=== rfkill issues with Broadcom wireless ===<br />
With kernel 4.4 and Broadcom WiFi card, the wireless switch has no effect except freezing the pointer in the KDE desktop (to unfreeze it switch to another virtual console and back).<br />
<br />
With lower kernel versions it switches the wireless card on/off at the hardware level, but the Broadcom driver does not not react to it properly: it does not realise the card is off, and only sees a lost connection. It then fails to recover when the card is switched back on. You can work-around this issue by switching WiFi off and on again in the NetworkManager applet or by setting {{ic|/sys/class/rfkill/rfkill0/state}} to 0 and then 1. Alternatively, you can disable the "Wireless Switch" control in the firmware setup.<br />
<br />
=== EFISTUB does not boot ===<br />
As of version A07, the BIOS does not pass any boot parameters to the kernel. Use a [[Boot_loaders#UEFI-only boot loaders|UEFI boot loader]] instead.<br />
[[systemd-boot]] works with current kernels.<br />
<br />
=== Repeating keys issue === <br />
BIOS A07 should fix this.<br />
<br />
=== Random kernel hangs at boot ===<br />
See [https://bugzilla.kernel.org/show_bug.cgi?id=105251 here]. This issue seems to only affect those with touchscreens. The fix consists in removing "keyboard" from the HOOKS in /etc/mkinitcpio.conf and instead using MODULES="atkbd.ko usbhid hid-generic" (if you need the keyboard hook). Obviously you will have to run:<br />
<br />
# mkinitcpio -p linux<br />
<br />
=== Sound doesn't work after upgrading to kernel 4.4 ===<br />
You need to do two cold boots (''don't'' reboot; shutdown and turn back on again) to make sound work again. This is necessary because I2S support was enabled in the Arch 4.4 stock kernel, and the XPS 13's embedded controller requires two cold boots to recognize changes in the sound chipset mode. See the Audio section above for more information.<br />
<br />
It is reported that recompiling the kernel with the CONFIG_ACPI_REV_OVERRIDE_POSSIBLE option will re-enable the microphone. See the [https://bbs.archlinux.org/viewtopic.php?id=208674 BBS thread] and [https://bugs.archlinux.org/task/47989 bug report] for information.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
<br />
Project Sputnik:<br />
* [http://bartongeorge.net/2015/08/28/recent-fixes-for-xps-13-developer-edition/ Recent Fixes for XPS 13 developer edition]<br />
* [http://bartongeorge.net/2015/02/23/update-2-dell-xps-13-laptop-developer-edition-sputnik-gen-4/ Update 2: Dell XPS 13 laptop, developer edition – Sputnik Gen 4]<br />
* [http://bartongeorge.net/2015/02/05/update-dell-xps-13-laptop-developer-edition-sputnik-gen-4/ Update: Dell XPS 13 laptop, developer edition – Sputnik Gen 4]<br />
* [http://bartongeorge.net/2015/04/09/4th-gen-dell-xps-13-developer-edition-available/ 4th gen Dell XPS 13 developer edition available!]</div>Bennylb0https://wiki.archlinux.org/index.php?title=Beginners%27_guide&diff=224123Beginners' guide2012-09-20T13:59:21Z<p>Bennylb0: /* Wireless */ Added dialog package as wifi-menu is dependant on it.</p>
<hr />
<div><noinclude><br />
[[Category:Getting and installing Arch]]<br />
[[Category:About Arch]]<br />
[[da:Beginners' Guide/Installation]]<br />
[[es:Beginners' Guide/Installation]]<br />
[[hr:Beginners' Guide/Installation]]<br />
[[hu:Beginners' Guide/Installation]]<br />
[[it:Beginners' Guide/Installation]]<br />
[[ko:Beginners' Guide/Installation]]<br />
[[nl:Beginners' Guide/Installatie]]<br />
[[pt:Beginners' Guide/Installation]]<br />
[[ro:Ghidul începătorilor/Instalare]]<br />
[[ru:Beginners' Guide/Installation]]<br />
[[sr:Beginners' Guide/Installation]]<br />
[[zh-CN:Beginners' Guide/Installation]]<br />
{{Tip|This is part of a multi-page article for The Beginners' Guide. '''[[Beginners' Guide|Click here]]''' if you would rather read the guide in its entirety.}}<br />
</noinclude><br />
== Installation ==<br />
<br />
You are now presented with a shell prompt, automatically logged in as root.<br />
<br />
=== Change the language ===<br />
<br />
{{Tip|These are optional for the majority of users. Useful only if you plan on writing in your own language in any of the configuration files, if you use diacritical marks in the Wi-Fi password, or if you would like to receive system messages (e.g. possible errors) in your own language.}}<br />
<br />
By default, the keyboard layout is set to {{ic|us}}. If you have a non-[[Wikipedia:File:KB_United_States-NoAltGr.svg|US]] keyboard layout, run:<br />
<br />
# loadkeys ''layout''<br />
<br />
...where ''layout'' can be {{ic|fr}}, {{ic|uk}}, {{ic|be-latin1}}, etc. See [[KEYMAP#Keyboard_layouts|here]] for a comprehensive list.<br />
<br />
The font should also be changed, because most languages use more glyphs than the 26 letter [[Wikipedia:English_alphabet|English alphabet]]. Otherwise some foreign characters may show up as white squares or as other symbols. Note that the name is case-sensitive, so please type it ''exactly'' as you see it:<br />
<br />
# setfont Lat2-Terminus16<br />
<br />
By default, the language is set to English (US). If you would like to change the language for the install process ''(German, in this example)'', remove the {{ic|#}} in front of the [http://www.greendesktiny.com/support/knowledgebase_detail.php?ref=EUH-483 locale] you want from {{ic|/etc/locale.gen}}, along with English (US). Please choose the {{ic|UTF-8}} entry.<br />
<br />
Use {{Keypress|Ctrl+X}} to exit, and when prompted to save changes, press {{Keypress|Y}} and {{Keypress|Enter}} to use the same filename.<br />
<br />
{{hc|# nano /etc/locale.gen|<br />
en_US.UTF-8 UTF-8<br />
de_DE.UTF-8 UTF-8}}<br />
<br />
# locale-gen<br />
# export LANG=de_DE.UTF-8<br />
<br />
Remember, {{Keypress|LAlt+LShift}} activates and deactivates the keymap.<br />
<br />
=== Establish an internet connection ===<br />
<br />
The {{ic|dhcpcd}} network daemon is started automatically at boot and it will attempt to start a wired connection, if available. Try pinging a website to see if it was successful. And since Google is always on...<br />
<br />
{{hc|# ping -c 3 www.google.com|2=<br />
PING www.l.google.com (74.125.132.105) 56(84) bytes of data.<br />
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=1 ttl=50 time=17.0 ms<br />
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=2 ttl=50 time=18.2 ms<br />
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=3 ttl=50 time=16.6 ms<br />
<br />
--- www.l.google.com ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2003ms<br />
rtt min/avg/max/mdev = 16.660/17.320/18.254/0.678 ms}}<br />
<br />
If you get a {{ic|ping: unknown host}} error, you will need to set up the network manually, as explained below.<br />
<br />
Otherwise, move on to [[#Prepare_the_storage_drive|Prepare the storage drive]].<br />
<br />
==== Wired ====<br />
<br />
Follow this procedure if you need wired connectivity (Ethernet) during the installation process.<br />
<br />
If your computer is connected to an Ethernet network, in most cases, you will have one interface, called {{ic|eth0}}. If you have additional network cards (apart from the one integrated on the motherboard, for example), their name will follow the sequence {{ic|eth1}}, {{ic|eth2}}, etc.<br />
<br />
You need to know these settings:<br />
<br />
* Static IP address.<br />
* Subnet mask.<br />
* Gateway's IP address.<br />
* Name servers' (DNS) IP addresses.<br />
* Domain name (unless you're on a local LAN, in which case you can make it up).<br />
<br />
Activate the connected Ethernet interface, e.g. for {{ic|eth0}}:<br />
<br />
# ip link set eth0 up<br />
<br />
Add the address:<br />
<br />
# ip addr add <ip address>/<subnetmask> dev <interface><br />
<br />
For example:<br />
<br />
# ip addr add 192.168.1.2/24 dev eth0<br />
<br />
For more options, run {{ic|man ip}}.<br />
<br />
Add your gateway like this, substituting your own gateway's IP address:<br />
<br />
# ip route add default via <ip address><br />
<br />
For example:<br />
<br />
# ip route add default via 192.168.1.1<br />
<br />
Edit {{ic|resolv.conf}}, substituting your name servers' IP addresses and your local domain name:<br />
<br />
{{hc|# nano /etc/resolv.conf|<br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com}}<br />
<br />
{{Note|Currently, you may include a maximum of 3 {{ic|nameserver}} lines.}}<br />
<br />
You should now have a working network connection. If you do not, check the detailed [[Configuring Network]] page.<br />
<br />
==== Wireless ====<br />
<br />
Follow this procedure if you need wireless connectivity (Wi-Fi) during the installation process.<br />
<br />
The wireless drivers and utilities are now available to you in the live environment of the installation media. A good knowledge of your wireless hardware will be of key importance to successful configuration. Note that the following quick-start procedure ''executed at this point in the installation'' will initialize your wireless hardware for use ''in the live environment of the installation media''. These steps (or some other form of wireless management) '''must be repeated from the actual installed system after booting into it'''.<br />
<br />
Also note that these steps are optional if wireless connectivity is unnecessary at this point in the installation; wireless functionality may always be established later.<br />
<br />
{{Note|The following examples use {{ic|wlan0}} for the interface and {{ic|linksys}} for the ESSID. Remember to change these values according to your setup.}}<br />
<br />
The basic procedure will be:<br />
<br />
* (optional) Identify the wireless interface:<br />
<br />
# lspci | grep -i net<br />
<br />
Or, if using a USB adapter:<br />
<br />
# lsusb<br />
<br />
* Ensure udev has loaded the driver, and that the driver has created a usable wireless kernel interface with {{ic|iwconfig}}:<br />
<br />
{{Note|If you do not see output similar to this, then your wireless driver has not been loaded. If this is the case, you must load the driver yourself. Please see [[Wireless Setup]] for more detailed information.}}<br />
<br />
{{hc|# iwconfig|2=<br />
lo no wireless extensions.<br />
eth0 no wireless extensions.<br />
wlan0 unassociated ESSID:""<br />
Mode:Managed Channel=0 Access Point: Not-Associated<br />
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0<br />
Retry limit:7 RTS thr:off Fragment thr:off<br />
Power Management:off<br />
Link Quality:0 Signal level:0 Noise level:0<br />
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br />
Tx excessive retries:0 Invalid misc:0 Missed beacon:0}}<br />
<br />
In this example, {{ic|wlan0}} is the available wireless interface.<br />
<br />
* Bring the interface up with:<br />
<br />
# ip link set wlan0 up<br />
<br />
A small percentage of wireless chipsets also require firmware, in addition to a corresponding driver. If the wireless chipset requires firmware, you are likely to receive this error when bringing the interface up:<br />
<br />
{{hc|# ip link set wlan0 up|<br />
SIOCSIFFLAGS: No such file or directory}}<br />
<br />
If unsure, invoke {{ic|dmesg}} to query the kernel log for a firmware request from the wireless chipset.<br />
<br />
Example output from an Intel chipset which requires and has requested firmware from the kernel at boot:<br />
<br />
{{hc|# dmesg <nowiki>|</nowiki> grep firmware|<br />
firmware: requesting iwlwifi-5000-1.ucode}}<br />
<br />
If there is no output, it may be concluded that the system's wireless chipset does not require firmware.<br />
<br />
{{Warning|Wireless chipset firmware packages (for cards which require them) are pre-installed under {{ic|/usr/lib/firmware}} in the live environment (on CD/USB stick) '''but must be explicitly installed to your actual system to provide wireless functionality after you reboot into it!''' Package installation is covered later in this guide. Ensure installation of both your wireless module and firmware before rebooting! See [[Wireless Setup]] if you are unsure about the requirement of corresponding firmware installation for your particular chipset.}}<br />
<br />
Next, use {{pkg|netcfg}}'s wifi-menu to connect to a network:<br />
<br />
# wifi-menu wlan0<br />
<br />
You should now have a working network connection. If you do not, check the detailed [[Wireless Setup]] page.<br />
<br />
==== xDSL (PPPoE), analog modem or ISDN ====<br />
<br />
If you have a router in bridge mode, run:<br />
<br />
# pppoe-setup<br />
<br />
* Type in the username that the ISP provided you with.<br />
* Press {{Keypress|Enter}} for "eth0".<br />
* Press {{Keypress|Enter}} for "no", so that it stays up continuously.<br />
* Type {{ic|server}} (since this is usually the case).<br />
* Press {{Keypress|1}} for a firewall.<br />
* Type in the password that the ISP provided you with.<br />
* Press {{Keypress|y}} at the end.<br />
<br />
To use these settings and connect to your ISP, run:<br />
<br />
# pppoe-start<br />
<br />
For an analog modem (dial-up) and ISDN, see [[Direct Modem Connection]].<br />
<br />
==== Behind a proxy server ====<br />
<br />
If you are behind a proxy server, you will need to export the {{ic|http_proxy}} and {{ic|ftp_proxy}} environment variables. '''[[Proxy|Click here]]''' for more information.<br />
<br />
=== Prepare the storage drive ===<br />
<br />
{{Warning|Partitioning can destroy data. You are '''strongly''' cautioned and advised to backup any critical data before proceeding.}}<br />
<br />
Absolute beginners are encouraged to use a graphical partitioning tool. [http://gparted.sourceforge.net/download.php GParted] is a good example, ran from a "live" Linux distribution such as [[Wikipedia:Parted_Magic|Parted Magic]], [[Wikipedia:Ubuntu_(operating_system)|Ubuntu]], [[Wikipedia:Linux_Mint|Linux Mint]], etc. See [[Partitioning]] for some general tips and make sure to format the partitions with a filesystem (e.g. '''ext4''', '''btrfs''', etc) before rebooting.<br />
<br />
If you have already done so, proceed to [[#Mount_the_partitions|Mount the partitions]].<br />
<br />
Otherwise, see the following example.<br />
<br />
==== Example ====<br />
<br />
The Arch Linux install media includes the following partitioning tools:<br />
<br />
* [[Wikipedia:cfdisk|cfdisk]] – supports only [[MBR]] partition tables.<br />
<br />
* [[Wikipedia:gdisk|gdisk]] – supports only [[GPT]] partition tables.<br />
<br />
* [[Wikipedia:parted|parted]] – supports both.<br />
<br />
This example uses '''cfdisk''', but it can be easily followed using '''gdisk''', which will allow for GPT partitioning.<br />
<br />
{{Note|If you have a [[UEFI]] motherboard you will need to create an extra partition called UEFI System partition. Read [[Unified_Extensible_Firmware_Interface#Create_an_UEFI_System_Partition_in_Linux|this article]].}}<br />
<br />
{{Note|If you want to setup GRUB in BIOS-GPT mode, then you need to create a 2 MiB "BIOS Boot Partition". See [[GRUB#GPT_specific_instructions]] for more info.}}<br />
<br />
{{Note|If you are installing to a USB flash key, see [[Installing Arch Linux on a USB key]].}}<br />
<br />
{{Note|If you are not dual booting with Windows, then it is advisable to use [[GPT]] instead of [[MBR]]. GPT partitioning can only be done with '''gdisk''' or '''parted'''. Read [[GPT]] for the list of advantages.}}<br />
<br />
# cfdisk /dev/sda<br />
<br />
The example system will contain a 15 GB root ({{ic|/}}) partition, a 1 GB {{ic|swap}} partition, and a {{ic|/home}} partition for the remaining space.<br />
<br />
It should be emphasized that partitioning is a personal choice and that this example is only for illustrative purposes. See [[Partitioning]].<br />
<br />
'''Root:'''<br />
<br />
* Choose New (or press {{Keypress|N}}) – {{Keypress|Enter}} for Primary – type in "15360" – {{Keypress|Enter}} for Beginning – {{Keypress|Enter}} for Bootable.<br />
<br />
'''Swap:'''<br />
<br />
* Press the down arrow to move to the free space area.<br />
* Choose New (or press {{Keypress|N}}) – {{Keypress|Enter}} for Primary – type in "1024" – {{Keypress|Enter}} for Beginning.<br />
* Choose Type (or press {{Keypress|T}}) – press any key to scroll down the list – {{Keypress|Enter}} for 82.<br />
<br />
'''Home:'''<br />
<br />
* Press the down arrow to move to the free space area.<br />
* Choose New (or press {{Keypress|N}}) – {{Keypress|Enter}} for Primary – {{Keypress|Enter}} to use the rest of the drive (or you could type in the desired size).<br />
<br />
Here's how it should look like:<br />
<br />
Name Flags Part Type FS Type [Label] Size (MB)<br />
-----------------------------------------------------------------------<br />
sda1 Boot Primary Linux 15360<br />
sda2 Primary Linux swap / Solaris 1024<br />
sda3 Primary Linux 133000*<br />
<br />
Double check and make sure that you are happy with the partition sizes as well as the partition table layout before continuing.<br />
<br />
If you would like to start over, you can simply select Quit (or press {{Keypress|Q}}) to exit without saving changes and then restart cfdisk.<br />
<br />
If you are satisfied, choose Write (or press {{Keypress|Shift+W}}) to finalize and to write the partition table to the drive. Type "yes" and choose Quit (or press {{Keypress|Q}}) to exit cfdisk without making any more changes.<br />
<br />
Simply partitioning is not enough; the partitions also need a [[File Systems|filesystem]]. To format the partitions with an ext4 filesystem:<br />
<br />
{{Warning|Double check and triple check that it's actually {{ic|/dev/sda1}} that you want to format.}}<br />
<br />
# mkfs.ext4 /dev/sda1<br />
# mkfs.ext4 /dev/sda3<br />
<br />
Format and activate the swap partition:<br />
<br />
# mkswap /dev/sda2<br />
# swapon /dev/sda2<br />
<br />
=== Mount the partitions ===<br />
<br />
Each partition is identified with a number suffix. For example, {{ic|sda1}} specifies the first partition of the first drive, while {{ic|sda}} designates the entire drive.<br />
<br />
To see the current partition layout:<br />
<br />
# lsblk /dev/sda<br />
<br />
Pay attention, because the mounting order is important.<br />
<br />
First, mount the root partition on {{ic|/mnt}}. Following the example above (yours may be different), it would be:<br />
<br />
# mount /dev/sda1 /mnt<br />
<br />
Then mount the {{ic|/home}} partition and any other separate partition ({{ic|/boot}}, {{ic|/var}}, etc), if you have any:<br />
<br />
# mkdir /mnt/home<br />
# mount /dev/sda3 /mnt/home<br />
<br />
In case you have a separate {{ic|/boot}} partition:<br />
<br />
# mkdir /mnt/boot<br />
# mount /dev/sda''X'' /mnt/boot<br />
<br />
In case you have a UEFI motherboard, mount the UEFI partition:<br />
<br />
# mkdir /mnt/boot/efi<br />
# mount /dev/sda''X'' /mnt/boot/efi<br />
<br />
=== Select a mirror ===<br />
<br />
Before installing, you may want to edit the {{ic|mirrorlist}} file and place your preferred mirror first. A copy of this file will be installed on your new system by {{ic|pacstrap}} as well, so it's worth getting it right.<br />
<br />
{{hc|# nano /etc/pacman.d/mirrorlist|<br />
##<br />
## Arch Linux repository mirrorlist<br />
## Sorted by mirror score from mirror status page<br />
## Generated on 2012-MM-DD<br />
##<br />
<br />
<nowiki>Server = http://mirror.example.xyz/archlinux/$repo/os/$arch</nowiki><br />
...}}<br />
<br />
* {{Keypress|Alt+6}} to copy a {{ic|Server}} line.<br />
* {{Keypress|PageUp}} key to scroll up.<br />
* {{Keypress|Ctrl+U}} to paste it at the top of the list.<br />
* {{Keypress|Ctrl+X}} to exit, and when prompted to save changes, press {{Keypress|Y}} and {{Keypress|Enter}} to use the same filename.<br />
<br />
If you want, you can make it the ''only'' mirror available by getting rid of everything else (using {{Keypress|Ctrl+K}}), but it's usually a good idea to have a few more, in case the first one goes offline.<br />
<br />
{{Tip|Use the [http://www.archlinux.org/mirrorlist/ Mirrorlist Generator] to get an updated list for your country. HTTP mirrors are faster than FTP, because of something called [[Wikipedia:Keepalive|keepalive]]. With FTP, pacman has to send out a signal each time it downloads a package, resulting in a brief pause.}}<br />
<br />
=== Install the base system ===<br />
<br />
The base system is installed using the [https://github.com/falconindy/arch-install-scripts/blob/master/pacstrap.in pacstrap] script.<br />
<br />
# pacstrap /mnt base base-devel<br />
<br />
* {{Grp|base}}: Software packages from the [core] repo to provide the minimal base environment.<br />
<br />
* {{Grp|base-devel}}: Extra tools from [core] such as {{ic|make}}, and {{ic|automake}}. Most beginners should choose to install it, as it will likely be needed to expand the system. The ''base-devel'' group will be required to install software from the [[Arch User Repository]].<br />
<br />
This will give you a basic Arch system. Other packages can be installed later using [[pacman]].<br />
<br />
{{Note|If pacman fails to verify your packages, check your system time. If the system date is invalid (e.g. it shows year 2010), signing keys will be considered expired (or invalid), signature checks on packages will fail and installation will be interrupted. Make sure to correct the system time, either by doing so manually or with the {{Pkg|ntp}} client, and retry running the pacstrap command. Refer to [[Time]] page for more information on correcting system time.}}<br />
<br />
=== Generate an fstab ===<br />
<br />
Generate an [[fstab]] file with the following command. If you prefer to use UUIDs or labels, add the {{ic|-U}} or {{ic|-L}} option, respectively. It's also a good idea to check it before continuing:<br />
<br />
{{Note|If you encounter errors running genfstab or later in the install process, do '''not''' run genfstab again; just edit the fstab file.}}<br />
<br />
# genfstab -p /mnt >> /mnt/etc/fstab<br />
# nano /mnt/etc/fstab<br />
<br />
Only the root ({{ic|/}}) partition needs {{ic|1}} for the last field. Everything else should have either {{ic|2}} or {{ic|0}} (see [[fstab#Field_definitions]]).<br />
<br />
Also, {{ic|1=data=ordered}} should be removed. This option will be used automatically whether you specify it or not. No point cluttering up your fstab.<br />
<br />
=== Chroot and configure the base system ===<br />
<br />
Next, we [[chroot]] into our newly installed system:<br />
<br />
# arch-chroot /mnt<br />
<br />
At this stage of the installation, you will configure the primary configuration files of your Arch Linux base system. These can either be created if they do not exist, or edited if you wish to change the defaults.<br />
<br />
Closely following and understanding these steps is of key importance to ensure a properly configured system.<br />
<br />
==== Locale ====<br />
<br />
Locales are used by '''glibc''' and other locale-aware programs or libraries for rendering text, correctly displaying regional monetary values, time and date formats, alphabetic idiosyncrasies, and other locale-specific standards.<br />
<br />
There are two files that need editing: {{ic|locale.gen}} and {{ic|locale.conf}}.<br />
<br />
* The {{ic|locale.gen}} file is empty by default (everything is commented out) and you need to remove the {{ic|#}} in front of the line(s) you want. You may uncomment more lines than just English (US), as long as you choose their {{ic|UTF-8}} encoding:<br />
<br />
{{hc|# nano /etc/locale.gen|<br />
en_US.UTF-8 UTF-8<br />
de_DE.UTF-8 UTF-8}}<br />
<br />
# locale-gen<br />
<br />
This will run on every '''glibc''' upgrade, generating all the locales specified in {{ic|/etc/locale.gen}}.<br />
<br />
* The {{ic|locale.conf}} file doesn't exist by default. Setting only {{ic|LANG}} should be enough. It will act as the default value for all other variables.<br />
<br />
# echo LANG=en_US.UTF-8 > /etc/locale.conf<br />
# export LANG=en_US.UTF-8<br />
<br />
{{Note|If you set some other language than English at the beginning of the install, the above commands would be something like:<br />
# echo LANG<nowiki>=</nowiki>de_DE.UTF-8 > /etc/locale.conf<br />
# export LANG<nowiki>=</nowiki>de_DE.UTF-8<br />
}}<br />
<br />
To use other {{ic|LC_*}} variables, first run {{ic|locale}} to see the available options. An advanced example can be found [[Locale#Setting_system-wide_locale|here]].<br />
<br />
{{Warning|Using the {{ic|LC_ALL}} variable is strongly discouraged because it overrides everything.}}<br />
<br />
==== Console font and keymap ====<br />
<br />
If you set a keymap at [[#Change_the_language|the beginning]] of the install process, load it now, as well, because the environment has changed. For example:<br />
<br />
# loadkeys ''de-latin1''<br />
# setfont Lat2-Terminus16<br />
<br />
To make them available after reboot, edit {{ic|vconsole.conf}}:<br />
<br />
{{hc|# nano /etc/vconsole.conf|2=<br />
KEYMAP=de-latin1<br />
FONT=Lat2-Terminus16<br />
FONT_MAP=}}<br />
<br />
* {{ic|KEYMAP}} – Please note that this setting is only valid for your TTYs, not any graphical window managers or X.Org.<br />
<br />
* {{ic|FONT}} – Available alternate console fonts reside in {{ic|/usr/share/kbd/consolefonts/}}. The default (blank) is safe, but some foreign characters may show up as white squares or as other symbols. It's recommended that you change it to {{ic|Lat2-Terminus16}}, because according to {{ic|/usr/share/kbd/consolefonts/README.Lat2-Terminus16}}, it claims to support "about 110 language sets".<br />
<br />
* {{ic|FONT_MAP}} – Defines the console map to load at boot. Read {{ic|man setfont}}. The default (blank) is safe.<br />
<br />
See [[Fonts#Console_fonts|Console fonts]] and {{ic|man vconsole.conf}} for more information.<br />
<br />
==== Timezone ====<br />
<br />
Available time zones and subzones can be found in the {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} directories.<br />
<br />
To view the available <Zone>, check the directory {{ic|/usr/share/zoneinfo/}}:<br />
<br />
# ls /usr/share/zoneinfo/<br />
<br />
Similarly, you can check the contents of directories belonging to a <SubZone>:<br />
<br />
# ls /usr/share/zoneinfo/Europe<br />
<br />
Create a symbolic link {{ic|/etc/localtime}} to your zone file {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} using this command:<br />
<br />
# ln -s {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} /etc/localtime<br />
<br />
'''Example:'''<br />
<br />
# ln -s /usr/share/zoneinfo/Europe/Minsk /etc/localtime<br />
<br />
If you are using systemd's timedated, you might wish to also edit the file {{ic|/etc/timezone}} and write your {{ic|<Zone>}}/{{ic|<Subzone>}}.<br />
<br />
'''Example:'''<br />
<br />
{{hc|# nano /etc/timezone|<br />
Europe/Minsk}}<br />
<br />
Read {{ic|man tzset}} for more options.<br />
<br />
The need for {{ic|/etc/timezone}} might go away in the future (see [http://cgit.freedesktop.org/systemd/systemd/commit/?id=9cb48731b29f508178731b45b0643c816800c05e this] for details).<br />
<br />
==== Hardware clock ====<br />
<br />
Set the hardware clock mode uniformly between your operating systems. Otherwise, they may overwrite the hardware clock and cause time shifts.<br />
<br />
You can generate {{ic|/etc/adjtime}} automatically by using one of the following commands:<br />
<br />
* '''UTC''' (recommended)<br />
<br />
: {{Note|Using [[Wikipedia:Coordinated Universal Time|UTC]] for the hardware clock does not mean that software will display time in UTC.}}<br />
<br />
: {{bc|# hwclock --systohc --utc}}<br />
<br />
* '''localtime''' (discouraged; used by default in Windows)<br />
<br />
: {{Warning|Using ''localtime'' may lead to several known and unfixable bugs. However, there are no plans to drop support for ''localtime''.}}<br />
<br />
: {{bc|# hwclock --systohc --localtime}}<br />
<br />
If you have (or planning on having) a dual boot setup with Windows:<br />
<br />
* Recommended: Set both Arch Linux and Windows to use UTC. A quick [[Time#UTC_in_Windows|registry fix]] is needed. Also, be sure to prevent Windows from synchronizing the time on-line, because the hardware clock will default back to ''localtime''. If you want such functionality (NTP sync), you should use [[ntpd]] on your Arch Linux installation instead.<br />
<br />
* Not recommended: Set Arch Linux to ''localtime'' and remove any time-related daemons from {{ic|/etc/rc.conf}}. This will let Windows take care of hardware clock corrections and you will need to remember to boot into Windows at least two times a year (in Spring and Autumn) when [[Wikipedia:Daylight_savings_time|DST]] kicks in. So please don't ask on the forums why the clock is one hour behind or ahead if you usually go for days or weeks without booting into Windows.<br />
<br />
==== Kernel modules ====<br />
<br />
{{Tip|This is just an example, you do not need to set it. All needed modules are automatically loaded by udev, so you will rarely need to add something here. Only add modules that you know are missing.}}<br />
<br />
For kernel modules to load during boot, place a {{ic|*.conf}} file in {{ic|/etc/modules-load.d/}}, with a name based on the program that uses them.<br />
<br />
{{hc|# nano /etc/modules-load.d/virtio-net.conf|<br />
# Load 'virtio-net.ko' at boot.<br />
<br />
virtio-net}}<br />
<br />
If there are more modules to load per {{ic|*.conf}}, the module names can be separated by newlines. A good example are the [[VirtualBox#Arch_Linux_guests|VirtualBox Guest Additions]].<br />
<br />
Empty lines and lines starting with {{ic|#}} or {{ic|;}} are ignored.<br />
<br />
==== Daemons ====<br />
<br />
{{Tip|The {{ic|DAEMONS}} line need not be changed at this time, but it is useful to explain what daemons are, as they will be addressed later in this guide.}}<br />
<br />
[[Daemon|Daemons]] are programs that run in the background, waiting for events to occur and offering services. A few good examples are: a web server that waits for a request to deliver a page (e.g. {{ic|httpd}}), an SSH server waiting for a user to log in (e.g. {{ic|sshd}}), a daemon which writes system messages to a log file (e.g. {{ic|syslog-ng}}), a BitTorrent client (e.g. {{ic|rtorrent}}, {{ic|deluged}}), a music player (e.g. {{ic|mpd}}), a firewall (e.g. {{ic|iptables}}), etc. While these are full-featured applications, their work is usually not that visible. Their main advantage is that even if X.Org crashes (or is absent from the system), they will continue to work.<br />
<br />
Daemons can be added to the {{ic|DAEMONS}} line in {{ic|/etc/rc.conf}} and they will start when the system boots, in the order that they are placed. Their names are the equivalent scripts from {{ic|/etc/rc.d/}}.<br />
<br />
{{hc|# nano /etc/rc.conf|2=<br />
DAEMONS=(network @syslog-ng netfs @crond)}}<br />
<br />
* If a script name is prefixed with a bang ({{ic|!}}), it is not run.<br />
<br />
* If a script is prefixed with an "at" symbol ({{ic|@}}), it is run in the background; the startup sequence will not wait for successful completion of this daemon before continuing to the next (this may shorten system boot time). Do not background daemons that are needed by other daemons. For example, {{ic|mpd}} depends on {{ic|network}}, so backgrounding {{ic|network}} may cause {{ic|mpd}} to break.<br />
<br />
A list of available services (and their running status) can be found using the command:<br />
<br />
# rc.d list<br />
<br />
==== Hostname ====<br />
<br />
Add your ''hostname'' in {{ic|/etc/hostname}}:<br />
<br />
# echo '''myhostname''' > /etc/hostname<br />
<br />
Set it to your liking (e.g. ''arch''). This is the name of your computer. And add it to {{ic|/etc/hosts}}, as well:<br />
<br />
{{Warning|This format, including {{ic|localhost}} and your actual hostname, is required for program compatibility. Errors in these entries may cause poor network performance and/or certain programs to open very slowly, or not work at all.}}<br />
<br />
{{hc|# nano /etc/hosts|<br />
127.0.0.1 '''myhostname''' localhost<br />
::1 '''myhostname''' localhost<br />
<br />
#192.168.1.100 '''myhostname'''.domain.org '''myhostname''' #Uncomment if you use a static IP and remove this comment.}}<br />
<br />
{{Note|{{ic|::1}} is the IPv6 equivalent of {{ic|127.0.0.1}} and should be added.}}<br />
<br />
{{Tip|For convenience, you may also use {{ic|/etc/hosts}} aliases for hosts on your network, and/or on the Web.<br />
<br />
192.168.1.90 media<br />
192.168.1.88 data<br />
<br />
The above example would allow you access to a media and data server on your network by name and without the need for typing out their respective IP addresses.}}<br />
<br />
=== Configure the network ===<br />
<br />
You need to configure the network again, but this time for your newly installed environment. The procedure and prerequisites are very similar to the one described [[#Establish_an_internet_connection|above]], except we are going to make it persistent and automatically run at boot.<br />
<br />
{{Note|For more in-depth information on network configration, visit [[Configuring Network]] and [[Wireless Setup]].}}<br />
<br />
==== Wired ====<br />
<br />
If you only use a single fixed wired network connection, you can use the {{ic|network}} daemon, a simple solution for both dynamic and static IP addressing.<br />
<br />
First, ensure that the daemon is listed in the {{ic|DAEMONS}} array:<br />
<br />
{{hc|# nano /etc/rc.conf|2=<br />
DAEMONS=(... network ...)}}<br />
<br />
Then configure the {{ic|NETWORKING}} section of {{ic|/etc/rc.conf}} as follows, depending on your IP addressing type:<br />
<br />
; Dynamic IP<br />
<br />
Assuming the network interface to activate at start is {{ic|eth0}}, use this configuration:<br />
<br />
interface=eth0<br />
address=<br />
netmask=<br />
gateway=<br />
<br />
Your DNS server addresses will be automatically filled in by the {{ic|dhcpcd}} daemon.<br />
<br />
; Static IP<br />
<br />
If you have a static IP address, use this configuration:<br />
<br />
interface=eth0<br />
address=192.168.0.2<br />
netmask=255.255.255.0<br />
broadcast=192.168.0.255<br />
gateway=192.168.0.1<br />
<br />
You will also need to add your name servers' (DNS) IP addresses and your local domain name to your {{ic|/etc/resolv.conf}} like this:<br />
<br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com<br />
<br />
{{Tip|The {{ic|network}} daemon is suitable for systems connecting wired to a single network. For multiple network configurations (e.g. using a laptop), it is recommended to use a network manager program, such as [[netcfg]], which has been designed to manage both wired and wireless connections.}}<br />
<br />
==== Wireless ====<br />
<br />
The {{ic|network}} daemon is not sufficient to handle wireless networking. You will need to install other programs to configure and manage wireless network profiles, such as [[netcfg]].<br />
<br />
[[NetworkManager]] and [[Wicd]] are other popular alternatives.<br />
<br />
* Install the required packages:<br />
<br />
# pacman -S wireless_tools netcfg dialog<br />
<br />
If you use WPA/WPA2 encryption, install:<br />
<br />
# pacman -S wpa_supplicant wpa_actiond <br />
<br />
If your wireless adapter requires a firmware (as described in the above [[#Wireless|Establish an internet connection]] section and also [[Wireless_Setup#Drivers_and_firmware|here]]), install the package containing your firmware. For example:<br />
<br />
# pacman -S zd1211-firmware<br />
<br />
* Connect to the network with {{ic|wifi-menu}} (optionally checking the interface name with {{ic|ip link}}, but usually it's {{ic|wlan0}}), which will generate a profile file in {{ic|/etc/network.d}} named after the SSID. There are also templates available in {{ic|/etc/network.d/examples/}} for manual configuration.<br />
<br />
# wifi-menu<br />
<br />
* Add {{ic|net-auto-wireless}} to the {{ic|DAEMONS}} array in {{ic|/etc/rc.conf}}, daemon which will connect to known networks and gracefully handle roaming and disconnects:<br />
<br />
{{Note|[[Netcfg]] also provides {{ic|net-auto-wired}}, which can be used in conjunction with {{ic|net-auto-wireless}}.}}<br />
<br />
{{hc|# nano /etc/rc.conf|2=<br />
DAEMONS=(... net-auto-wireless ...)}}<br />
<br />
* Make sure that the correct wireless interface (usually {{ic|wlan0}}) is set in {{ic|/etc/conf.d/netcfg}}:<br />
<br />
{{hc|# nano /etc/conf.d/netcfg|2=<br />
WIRELESS_INTERFACE="wlan0"}}<br />
<br />
It is also possible to define a list of network profiles that should be automatically connected, using the {{ic|AUTO_PROFILES}} variable in {{ic|/etc/conf.d/netcfg}}. If {{ic|AUTO_PROFILES}} is not set, all known wireless networks will be tried.<br />
<br />
==== xDSL (PPPoE), analog modem or ISDN ====<br />
<br />
For xDSL, analog modem (dial-up) and ISDN, see [[Direct Modem Connection]].<br />
<br />
=== Create an initial ramdisk environment ===<br />
<br />
{{Tip|Most users can skip this step and use the defaults provided in {{ic|mkinitcpio.conf}}. The initramfs image (from the {{ic|/boot}} folder) has already been generated based on this file when the {{Pkg|linux}} package (the Linux kernel) was installed earlier with {{ic|pacstrap}}.}}<br />
<br />
Here you need to set the right [[Mkinitcpio#HOOKS|hooks]] if the root is on a USB drive, if you use RAID, LVM, or if {{ic|/usr}} is on a separate partition.<br />
<br />
Edit {{ic|/etc/mkinitcpio.conf}} as needed and re-generate the initramfs image with:<br />
<br />
# mkinitcpio -p linux<br />
<br />
=== Install and configure a bootloader ===<br />
<br />
==== For BIOS motherboards ====<br />
<br />
For BIOS systems, there are three bootloaders - Syslinux, GRUB, and [[LILO]]. Choose the bootloader as per your convenience. Below only Syslinux and GRUB are explained. <br />
<br />
* Syslinux is (currently) limited to loading only files from the partition where it was installed. Its configuration file is considered to be easier to understand. An example configuration can be found [https://bbs.archlinux.org/viewtopic.php?pid=1109328#p1109328 here].<br />
<br />
* GRUB is more feature-rich and supports more complex scenarios. Its configuration file(s) is similar more to a scripting language, which may be difficult for beginners to manually write. It is recommended that they automatically generate one.<br />
<br />
===== Syslinux =====<br />
<br />
Install the {{Pkg|syslinux}} package and then use the {{ic|syslinux-install_update}} script to automatically ''install'' the files ({{ic|-i}}), mark the partition ''active'' by setting the boot flag ({{ic|-a}}), and install the ''MBR'' boot code ({{ic|-m}}):<br />
<br />
{{Note|If you have partitioned the drive as GPT, install {{Pkg|gptfdisk}} package, as well ({{ic|pacman -S gptfdisk}}), because it contains {{ic|sgdisk}}, which will be used to set the GPT-specific boot flag.}}<br />
<br />
# pacman -S syslinux<br />
# syslinux-install_update -iam<br />
<br />
Configure {{ic|syslinux.cfg}} to point to the right root partition. This step is vital. If it points to the wrong partition, Arch Linux will not boot. Change {{ic|/dev/sda3}} to reflect your root partition ''(if you partitioned your drive as we did in [[#Prepare_the_storage_drive|the example]], your root partition is sda1)''. Do the same for the fallback entry.<br />
<br />
{{hc|# nano /boot/syslinux/syslinux.cfg|2=<br />
...<br />
LABEL arch<br />
...<br />
APPEND root=/dev/sda3 ro<br />
...}}<br />
<br />
For more information on configuring and using Syslinux, see [[Syslinux]].<br />
<br />
===== GRUB =====<br />
<br />
{{Note|For GPT-partitioned drives on BIOS motherboards, GRUB needs a 2 MiB "[[GRUB#GPT_specific_instructions|BIOS Boot Partition]]".}}<br />
<br />
{{Note|Please do not use {{ic|/dev/sda''X''}} in the below command. You may use {{ic|/dev/sdb}} if you installed Arch there, as long as you set that drive to boot first from the BIOS settings.}}<br />
<br />
# pacman -S grub-bios<br />
# grub-install --target=i386-pc --recheck /dev/sda<br />
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo<br />
<br />
While using a manually created {{ic|grub.cfg}} is absolutely fine, it's recommended that beginners automatically generate one:<br />
<br />
{{Tip|To automatically search for other operating systems on your computer, install {{Pkg|os-prober}} before generating it:<br />
# pacman -S os-prober<br />
}}<br />
<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
<br />
For more information on configuring and using GRUB, see [[GRUB]].<br />
<br />
==== For UEFI motherboards ====<br />
<br />
For UEFI boot, the drive needs to be GPT-partitioned, and a UEFI System Partition (512 MiB or higher, FAT32, type {{ic|EF00}}) must be present and mounted on {{ic|/boot/efi}}. If you have followed this guide from the beginning, you've already done all of these.<br />
<br />
While there are other [[UEFI_Bootloaders|UEFI bootloaders]] available, using EFISTUB is recommended. Below are instructions for setting up EFISTUB and GRUB.<br />
<br />
{{Note|Syslinux does not yet support UEFI.}}<br />
<br />
===== EFISTUB =====<br />
<br />
The Linux kernel can act as its own bootloader using EFISTUB. This is the UEFI boot method recommended by developers and simpler compared to {{ic|grub-efi-x86_64}}. The below steps set up rEFInd (a fork of rEFIt) to provide a menu for EFISTUB kernels, as well as for booting other UEFI bootloaders. You can also use [[UEFI_Bootloaders#Using_gummiboot|gummiboot]] (not tested) instead of rEFInd. Both rEFInd and gummiboot can detect Windows UEFI bootloader in case of dual-boot.<br />
<br />
1. Boot in UEFI mode and load {{ic|efivars}} kernel module before chrooting:<br />
<br />
# modprobe efivars # before chrooting<br />
<br />
2. Mount the UEFISYS partition at {{ic|/mnt/boot/efi}}, chroot and [[UEFI_Bootloaders#Setting_up_EFISTUB|copy the kernel and initramfs files]] to {{ic|/boot/efi}}.<br />
<br />
3. Every time the kernel and initramfs files are updated in {{ic|/boot}}, they need to be updated in {{ic|/boot/efi/EFI/arch}}. This can be automated either [[UEFI_Bootloaders#Sync_EFISTUB_Kernel_in_UEFISYS_partition_using_Systemd|using systemd]] or [[UEFI_Bootloaders#Sync_EFISTUB_Kernel_in_UEFISYS_partition_using_Incron|using incron]] (for non-systemd setups).<br />
<br />
4. Install the following packages:<br />
<br />
# pacman -S refind-efi-x86_64 efibootmgr<br />
<br />
5. Create a {{ic|refind_linux.conf}} file with the kernel parameters to be used by rEFInd:<br />
<br />
{{hc|# nano /boot/efi/EFI/arch/refind_linux.conf|2=<br />
"Boot to X" "root=/dev/sdaX ro rootfstype=ext4 systemd.unit=graphical.target"<br />
"Boot to console" "root=/dev/sdaX ro rootfstype=ext4 systemd.unit=multi-user.target"}}<br />
<br />
6. Add rEFInd to UEFI boot menu using [[UEFI#efibootmgr|efibootmgr]]. <br />
<br />
{{Warning|Using {{ic|efibootmgr}} on Apple Macs may brick the firmware and may need reflash of the motherboard ROM. For Macs, use {{AUR|mactel-boot}}, or "bless" from within Mac OS X.}}<br />
<br />
# efibootmgr -c -g -d /dev/sdX -p Y -w -L "Arch Linux (rEFInd)" -l '\\EFI\\arch\\refind\\refindx64.efi'<br />
<br />
{{Note|In the above command, X and Y denote the drive and partition of the UEFISYS partition. For example, in {{ic|/dev/sdc5}}, X is "c" and Y is "5".}}<br />
<br />
7. (Optional) As a fallback, in case {{ic|efibootmgr}} created boot entry does not work, copy {{ic|refindx64.efi}} to {{ic|/boot/efi/EFI/boot/bootx64.efi}} as follows:<br />
<br />
# cp -r /boot/efi/EFI/arch/refind/* /boot/efi/EFI/boot/<br />
# mv /boot/efi/EFI/boot/refindx64.efi to /boot/efi/EFI/boot/bootx64.efi<br />
<br />
===== GRUB =====<br />
<br />
{{Note|In case you have a system with 32-bit EFI, like pre-2008 Macs, install {{ic|grub-efi-i386}} instead, and use {{ic|1=--target=i386-efi}}.}}<br />
<br />
# pacman -S grub-efi-x86_64 efibootmgr<br />
# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck<br />
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo<br />
<br />
Run the next command to create a menu entry for GRUB in the UEFI boot menu. See [[UEFI#efibootmgr|efibootmgr]] for more info.<br />
<br />
# efibootmgr -c -g -d /dev/sdX -p Y -w -L "Arch Linux (GRUB)" -l '\\EFI\\arch_grub\\grubx64.efi'<br />
<br />
While using a manually created {{ic|grub.cfg}} is absolutely fine, it's recommended that beginners automatically generate one:<br />
<br />
{{Tip|To automatically search for other operating systems on your computer, install {{Pkg|os-prober}} before generating it:<br />
# pacman -S os-prober<br />
}}<br />
<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
<br />
For more information on configuring and using GRUB, see [[GRUB]].<br />
<br />
=== Set the root password ===<br />
<br />
You can set the root password with:<br />
<br />
# passwd<br />
<br />
=== Unmount the partitions and reboot ===<br />
<br />
Exit from the chroot environment:<br />
<br />
# exit<br />
<br />
Since the partitions are mounted under {{ic|/mnt}}, we use the following command to unmount them:<br />
<br />
# umount /mnt/{boot,home,}<br />
<br />
Reboot the computer:<br />
<br />
# reboot<br />
<br />
{{Tip|Be sure to remove the installation media, otherwise you will boot back into it.}}<noinclude><br />
{{Beginners' Guide navigation}}</noinclude></div>Bennylb0